[
https://jira.jboss.org/jira/browse/JBESB-2811?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2811:
-------------------------------------
Can you attach the logs to see if there is other information that may shed light on the
source of this?
At present it would appear to be an error with the interaction between JBoss Remoting and
JBoss Messaging.
Quickstarts: notifications - NullPointerException after undeploying
-------------------------------------------------------------------
Key: JBESB-2811
URL:
https://jira.jboss.org/jira/browse/JBESB-2811
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.4 CP3
Reporter: Boris Belovic
Priority: Minor
There is NullPointerException after undeploying this quickstart.
I ran the sequence (as described in readme.txt):
1. ant deploy
2. ant receive-from-queue
3. ant receive-from-topic
4. ant runtest
5. then there was an expected result from ESB
6. I stopped the processes listening on queue and topic by CTRL-C
7. ant undeploy
After this I got NPE in server console:
10:59:06,756 INFO [STDOUT] ConsoleNotifier 2009/09/01 10:59:06.756<Hello from
ESB-unaware JMS Client>
10:59:55,547 INFO [TopicService] Topic[/topic/quickstart_notifications_topic] stopped
10:59:55,549 INFO [QueueService] Queue[/queue/quickstart_notifications_queue] stopped
10:59:55,551 INFO [QueueService] Queue[/queue/quickstart_notifications_gw] stopped
10:59:55,553 INFO [QueueService] Queue[/queue/quickstart_notifications_esb] stopped
10:59:55,554 WARN [ServiceMessageCounterLifecycleResource] Calling cleanup on existing
service message counters for identity ID-11
11:00:08,049 ERROR [ExceptionUtil]
ConnectionEndpoint[d6-36jqe2zf-1-xihnb2zf-xxpxao-100j3] close
[a7-iu8se2zf-1-xihnb2zf-xxpxao-100j3]
java.lang.NullPointerException
at
org.jboss.jms.server.endpoint.ServerConsumerEndpoint.localClose(ServerConsumerEndpoint.java:542)
at
org.jboss.jms.server.endpoint.ServerSessionEndpoint.localClose(ServerSessionEndpoint.java:1159)
at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.close(ServerConnectionEndpoint.java:395)
at
org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$close$aop(ConnectionAdvised.java:63)
at
org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeNext(ConnectionAdvised$close_N4742752445160157748.java)
at
org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at
org.jboss.jms.server.endpoint.advised.ConnectionAdvised$close_N4742752445160157748.invokeNext(ConnectionAdvised$close_N4742752445160157748.java)
at
org.jboss.jms.server.endpoint.advised.ConnectionAdvised.close(ConnectionAdvised.java)
at
org.jboss.jms.server.connectionmanager.SimpleConnectionManager.cleanupForSessionID(SimpleConnectionManager.java:488)
at
org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleClientFailure(SimpleConnectionManager.java:201)
at
org.jboss.jms.server.connectionmanager.SimpleConnectionManager.handleConnectionException(SimpleConnectionManager.java:241)
at org.jboss.remoting.ConnectionNotifier.connectionLost(ConnectionNotifier.java:60)
at org.jboss.remoting.Lease.notifyClientLost(Lease.java:338)
at org.jboss.remoting.Lease.access$600(Lease.java:40)
at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:404)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira