activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "RK G (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-4346) Activemq-5.8.0 Shutdown failing when using NIO + LevelDB
Date Tue, 26 Feb 2013 15:58:13 GMT

     [ https://issues.apache.org/jira/browse/AMQ-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

RK G closed AMQ-4346.
---------------------

    Resolution: Fixed

Duplicate 
                
> Activemq-5.8.0 Shutdown failing when using NIO + LevelDB
> --------------------------------------------------------
>
>                 Key: AMQ-4346
>                 URL: https://issues.apache.org/jira/browse/AMQ-4346
>             Project: ActiveMQ
>          Issue Type: Bug
>            Reporter: RK G
>
> I configured activemq 5.8.0 with nio connector and leveldb. When ./activemq stop is issued
shutdown process is throwing an exception. Its a standalone installation.
> Here is the exception.
> 2013-02-25 12:15:07,431 | INFO  | Connector amqp Stopped | org.apache.activemq.broker.TransportConnector
| ActiveMQ ShutdownHook
> 2013-02-25 12:15:07,549 | INFO  | Stopped LevelDB[/opt/activemq/data/leveldb] | org.apache.activemq.leveldb.LevelDBStore
| ActiveMQ Sh
> utdownHook
> 2013-02-25 12:15:07,550 | ERROR | Could not stop service: QueueRegion: destinations=1,
subscriptions=0, memory=0%. Reason: java.lang.N
> ullPointerException | org.apache.activemq.broker.jmx.ManagedQueueRegion | ActiveMQ ShutdownHook
> java.lang.NullPointerException
>         at org.fusesource.hawtdispatch.package$RichExecutor.execute(hawtdispatch.scala:171)
>         at org.fusesource.hawtdispatch.package$RichExecutorTrait$class.apply(hawtdispatch.scala:68)
>         at org.fusesource.hawtdispatch.package$RichExecutor.apply(hawtdispatch.scala:169)
>         at org.fusesource.hawtdispatch.package$RichExecutorTrait$class.future(hawtdispatch.scala:116)
>         at org.fusesource.hawtdispatch.package$RichExecutor.future(hawtdispatch.scala:169)
>         at org.fusesource.hawtdispatch.package$RichExecutorTrait$class.sync(hawtdispatch.scala:107)
>         at org.fusesource.hawtdispatch.package$RichExecutor.sync(hawtdispatch.scala:169)
>         at org.apache.activemq.leveldb.DBManager.destroyPList(DBManager.scala:773)
>         at org.apache.activemq.leveldb.LevelDBStore.removePList(LevelDBStore.scala:454)
>         at org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.destroyDiskList(FilePendingMessageCursor.java:168)
>         at org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.destroy(FilePendingMessageCursor.java:163)
>         at org.apache.activemq.broker.region.cursors.StoreQueueCursor.stop(StoreQueueCursor.java:82)
>         at org.apache.activemq.broker.region.Queue.stop(Queue.java:910)
>         at org.apache.activemq.broker.region.AbstractRegion.stop(AbstractRegion.java:117)
>         at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
>         at org.apache.activemq.broker.region.RegionBroker.doStop(RegionBroker.java:574)
>         at org.apache.activemq.broker.jmx.ManagedRegionBroker.doStop(ManagedRegionBroker.java:126)
>         at org.apache.activemq.broker.region.RegionBroker.stop(RegionBroker.java:194)
>         at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
>         at org.apache.activemq.broker.BrokerFilter.stop(BrokerFilter.java:161)
>         at org.apache.activemq.broker.TransactionBroker.stop(TransactionBroker.java:204)
>         at org.apache.activemq.broker.BrokerService$5.stop(BrokerService.java:2070)
>         at org.apache.activemq.util.ServiceStopper.stop(ServiceStopper.java:41)
>         at org.apache.activemq.broker.BrokerService.stop(BrokerService.java:715)
>         at org.apache.activemq.xbean.XBeanBrokerService.stop(XBeanBrokerService.java:96)
>         at org.apache.activemq.broker.BrokerService.containerShutdown(BrokerService.java:2282)
>         at org.apache.activemq.broker.BrokerService$6.run(BrokerService.java:2249)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message