You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Christian Posta (JIRA)" <ji...@apache.org> on 2012/09/28 13:37:07 UTC
[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails
to start
[ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465526#comment-13465526 ]
Christian Posta commented on APLO-264:
--------------------------------------
Is this something you're reproducing with a fresh install of Apollo? I can't seem to reproduce it, unless there's something else in your apollo.xml....
If you can turn up your logging around jetty (org.eclipse.jetty) and let me know more about your apollo.xml, I can try to help out.
> NPE in latest snapshot - broker fails to start
> ----------------------------------------------
>
> Key: APLO-264
> URL: https://issues.apache.org/jira/browse/APLO-264
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120927.002700-118
> Reporter: Lionel Cons
>
> Using apollo-99-trunk-20120927.002700-118, the broker failed to (re)start:
> 2012-09-28 07:27:03,344 | INFO | Opening the log file took: 97.85 ms |
> 2012-09-28 07:27:03,517 | INFO | Accepting connections at: tls://0.0.0.0:61133 |
> 2012-09-28 07:27:03,517 | INFO | Accepting connections at: tcp://0.0.0.0:61123 |
> 2012-09-28 07:27:03,550 | WARN | java.lang.NullPointerException | 13a0b579cf2
> 2012-09-28 07:27:03,550 | WARN | java.lang.NullPointerException | 13a0b579cf3
> 2012-09-28 07:27:03,550 | WARN | java.lang.NullPointerException | 13a0b579cf1
> 2012-09-28 07:27:03,563 | INFO | Accepting connections at: udp://0.0.0.0:6123 |
> 2012-09-28 07:27:08,142 | INFO | broker startup is waiting on start connector: websocket, start jetty webserver, start connector: websocket+ssl |
> And in stacktrace.log I see:
> 2012-09-28 07:27:03,551 | WARN | stackref=13a0b579cf2
> java.lang.NullPointerException
> at org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed(AbstractLifeCycle.java:199)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at org.apache.activemq.apollo.broker.jetty.WebSocketTransportFactory$WsTransportServer$$anonfun$_start$1.apply$mcV$sp(WebSocketTransportFactory.scala:146)
> at org.fusesource.hawtdispatch.package$$anon$3.run(hawtdispatch.scala:357)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> 2012-09-28 07:27:03,551 | WARN | stackref=13a0b579cf1
> java.lang.NullPointerException
> at org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed(AbstractLifeCycle.java:199)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at org.apache.activemq.apollo.broker.jetty.JettyWebServer$$anonfun$_start$1.apply$mcV$sp(JettyWebServer.scala:254)
> at org.fusesource.hawtdispatch.package$$anon$3.run(hawtdispatch.scala:357)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> 2012-09-28 07:27:03,551 | WARN | stackref=13a0b579cf3
> java.lang.NullPointerException
> at org.eclipse.jetty.util.component.AbstractLifeCycle.setFailed(AbstractLifeCycle.java:199)
> at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
> at org.apache.activemq.apollo.broker.jetty.WebSocketTransportFactory$WsTransportServer$$anonfun$_start$1.apply$mcV$sp(WebSocketTransportFactory.scala:146)
> at org.fusesource.hawtdispatch.package$$anon$3.run(hawtdispatch.scala:357)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
--
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