Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: Medium
Fix Version/s: 3.10.0
Affects Version/s: 3.2.0
Component/s: None
Labels:
- da-error_handling
- hazelcast

Bug Fix Policy:
View Atlassian Server bug fix policy

Description

When an OutOfMemoryError occurs in certain contexts, the Hazelcast instance is terminated which prevents Stash on that cluster node from potentially recovering from the error.

OutOfMemoryErrors are not always recoverable anyway, but this behaviour of Hazelcast when it is caught in these contexts should be made more robust. This will remove some occurrences of the following log error:

2015-01-05 01:36:21,091 ERROR [threadpool:thread-36072]  c.a.s.i.c.StateTransferringExecutor Error while processing asynchronous task
com.atlassian.cache.CacheException: com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!
        at com.atlassian.cache.hazelcast.HazelcastCachedReference.get(HazelcastCachedReference.java:95) ~[HazelcastCachedReference.class:na]
        at com.atlassian.stash.internal.license.LicenseServiceImpl.get(LicenseServiceImpl.java:101) ~[LicenseServiceImpl.class:na]

Attachments

Issue Links

mentioned in: Page Loading...

Activity

People

Assignee:: Cristan Szmajda (Inactive)

Reporter:: Daniel R

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 20/May/2015 10:28 PM

Updated:: 24/Oct/2017 8:22 AM

Resolved:: 20/May/2015 10:32 PM