[
https://issues.apache.org/jira/browse/QPID-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123527#comment-15123527
]
Keith Wall commented on QPID-6992:
----------------------------------
It looks to me like this issue still exists. QPID-6972 delegated the handling
of the exception back to the facade, but the handling is the same. In the case
of non-HA, the environment will be closed, but then the exception will be
swallowed. The next persistent messaging operation will shutdown the broker
(as the store will be closed), so the Broker shutdown might not be as timely as
it ought to be, but it will go down.
> [Java Broker] ServerScopedRuntimeException thrown in CommitterThread does not
> shutdown the broker
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-6992
> URL: https://issues.apache.org/jira/browse/QPID-6992
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.22, 0.24, 0.26, 0.28, 0.30, 0.32, qpid-java-6.0
> Reporter: Alex Rudyy
>
> ServerScopedRuntimeException thrown in CommitterThread do not shutdown the
> broker:
> {noformat}
> 2016-01-10 23:04:44,688 ERROR [Commit-Thread-default]
> (o.a.q.s.u.ServerScopedRuntimeException) - Exception whilst syncing data to
> disk
> com.sleepycat.je.EnvironmentFailureException: (JE 5.0.104) Environment must
> be closed, caused by: com.sleepycat.je.EnvironmentFailureException:
> Environment invalid because of previous exception: (JE 5.0.104)
> /apps/qpid/jenkins/workspace/Qpid-Perftests-StartBroker/qpid-broker/6.0.0-SNAPSHOT/work/default/messages
> java.nio.BufferOverflowException UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must be
> closed.
> at
> com.sleepycat.je.EnvironmentFailureException.wrapSelf(EnvironmentFailureException.java:246)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.dbi.EnvironmentImpl.checkIfInvalid(EnvironmentImpl.java:1618)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.FileManager.writeLogBuffer(FileManager.java:1589)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.LogBufferPool.writeBufferToFile(LogBufferPool.java:411)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.LogBufferPool.writeDirty(LogBufferPool.java:370)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.LogManager.flushInternal(LogManager.java:1306)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.flush(LogManager.java:1256)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.dbi.EnvironmentImpl.flushLog(EnvironmentImpl.java:2084)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.Environment.flushLog(Environment.java:1593)
> ~[je-5.0.104.jar:5.0.104]
> at
> org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.flushLog(StandardEnvironmentFacade.java:212)
> ~[qpid-bdbstore-6.0.0.jar:6.0.0]
> at
> org.apache.qpid.server.store.berkeleydb.CoalescingCommiter$CommitThread.processJobs(CoalescingCommiter.java:198)
> [qpid-bdbstore-6.0.0.jar:6.0.0]
> at
> org.apache.qpid.server.store.berkeleydb.CoalescingCommiter$CommitThread.run(CoalescingCommiter.java:177)
> [qpid-bdbstore-6.0.0.jar:6.0.0]
> Caused by: com.sleepycat.je.EnvironmentFailureException: Environment invalid
> because of previous exception: (JE 5.0.104)
> /apps/qpid/jenkins/workspace/Qpid-Perftests-StartBroker/qpid-broker/6.0.0-SNAPSHOT/work/default/messages
> java.nio.BufferOverflowException UNEXPECTED_EXCEPTION_FATAL: Unexpected
> internal Exception, unable to continue. Environment is invalid and must be
> closed.
> at
> com.sleepycat.je.EnvironmentFailureException.unexpectedException(EnvironmentFailureException.java:351)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.serialLog(LogManager.java:574)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.logItems(LogManager.java:508)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.multiLog(LogManager.java:410)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.log(LogManager.java:350)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.tree.LN.logInternal(LN.java:556)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.tree.LN.log(LN.java:411) ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.cleaner.FileProcessor.processFoundLN(FileProcessor.java:1084)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.cleaner.FileProcessor.processLN(FileProcessor.java:881)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.cleaner.FileProcessor.processFile(FileProcessor.java:677)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.cleaner.FileProcessor.doClean(FileProcessor.java:290)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.cleaner.FileProcessor.onWakeup(FileProcessor.java:148)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.utilint.DaemonThread.run(DaemonThread.java:148)
> ~[je-5.0.104.jar:5.0.104]
> at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_67]
> Caused by: java.nio.BufferOverflowException: null
> at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:183) ~[na:1.7.0_67]
> at java.nio.ByteBuffer.put(ByteBuffer.java:832) ~[na:1.7.0_67]
> at
> com.sleepycat.je.log.LogUtils.writeBytesNoLength(LogUtils.java:349)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.entry.LNLogEntry.writeBaseLNEntry(LNLogEntry.java:403)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.entry.LNLogEntry.writeEntry(LNLogEntry.java:365)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.entry.BaseReplicableEntry.writeEntry(BaseReplicableEntry.java:51)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.entry.LNLogEntry.writeEntry(LNLogEntry.java:52)
> ~[je-5.0.104.jar:5.0.104]
> at
> com.sleepycat.je.log.LogManager.marshallIntoBuffer(LogManager.java:841)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.serialLogWork(LogManager.java:708)
> ~[je-5.0.104.jar:5.0.104]
> at com.sleepycat.je.log.LogManager.serialLog(LogManager.java:555)
> ~[je-5.0.104.jar:5.0.104]
> ... 12 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]