You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2012/09/28 08:49:07 UTC

[jira] [Created] (APLO-264) NPE in latest snapshot - broker fails to start

Lionel Cons created APLO-264:
--------------------------------

             Summary: 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

[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Christian Posta (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465546#comment-13465546 ] 

Lionel Cons commented on APLO-264:
----------------------------------

No, I cannot reproduce it. I killed the broker (only kill -9 worked) and then could restart it without an error. So it does not come from apollo.xml.

I'll try to restart it in a loop to see if this comes up again. Otherwise, we're only left with the stack traces...
                
> 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

[jira] [Resolved] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved APLO-264.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

Explicitly setting the Jetty log implementation so that the NPE can never occur.
                
> 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
>          Components: apollo-broker
>         Environment: apollo-99-trunk-20120927.002700-118
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>
> 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

[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465543#comment-13465543 ] 

Hiram Chirino commented on APLO-264:
------------------------------------

Weird.  Stacktrace is leading me to think the LOG variable used by jetty is the one which is null.  But I have not been touching the Jetty bits at all so that should not have changed.

I just downloaded that build and ti started up fine on my machine.  Does that build give you trouble on other machines or is it specific to one?
                
> 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

[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465747#comment-13465747 ] 

Hiram Chirino commented on APLO-264:
------------------------------------

Hi Christian!  Thanks for the research.  I'll apply the change suggested on the mailing list.
                
> 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

[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Christian Posta (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465692#comment-13465692 ] 

Christian Posta commented on APLO-264:
--------------------------------------

I asked on the jetty mailing list

here's the link for ref:

http://jetty.4.n6.nabble.com/Baffling-nullpointer-on-a-LOG-statement-td4959249.html


                
> 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

[jira] [Commented] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465547#comment-13465547 ] 

Lionel Cons commented on APLO-264:
----------------------------------

Hiram, I installed this build on 4 machines the exact same way (stop + rpm upgrade + start), only one machine had this problem and it went away after kill -9 + start.
                
> 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

[jira] [Updated] (APLO-264) NPE in latest snapshot - broker fails to start

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/APLO-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-264:
-------------------------------

    Component/s: apollo-broker
       Assignee: Hiram Chirino
    
> 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
>          Components: apollo-broker
>         Environment: apollo-99-trunk-20120927.002700-118
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>
> 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