[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjms-developer
Subject:    [openjms-developer] [ openjms-Bugs-1689845 ] Client shutdown problem
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2007-03-28 12:46:41
Message-ID: E1HWXY1-0001PI-6W () sc8-sf-web22 ! sourceforge ! net
[Download RAW message or body]

Bugs item #1689845, was opened at 2007-03-28 14:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1689845&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: client
Group: v0.7.7-alpha-3
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jan Dittberner (jandd)
Assigned to: Jim Alateras (jalateras)
Summary: Client shutdown problem

Initial Comment:
We have an OpenJMS-Client integrated in a web application. The OpenJMS connection is \
created and closed in an own JMSManager class which is started and stopped in a \
ServletContextListener. When starting the ServletContext we perform:

// initialize JNDI-Context
context = new InitialContext(cxtEnv);
// get connection
topicConnection = ((TopicConnectionFactory) \
context.lookup(factoryKeyTopic)).createTopicConnection(); topicConnection.start();
// create a QueueSession
topicSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);

on shutdown we do:

topicSession.close();
topicConnection.close();
context.close();

If the servlet container (Tomcat 5.5) is shut down the ClockDaemon from \
DefaultConnectionPool stays alive. After some seconds a NullPointerException is \
thrown. The tomcat process never stops. The following Stacktrace is logged:

Exception in thread "ManagedConnectionReaper1" java.lang.NullPointerException
	at org.apache.log4j.LogManager.getLogger(LogManager.java:188)
	at org.apache.log4j.Logger.getLogger(Logger.java:104)
	at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:229)
	at org.apache.commons.logging.impl.Log4JLogger.error(Log4JLogger.java:193)
	at org.exolab.jms.net.connector.DefaultConnectionPool$IdleReaper.run(DefaultConnectionPool.java:644)
  at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Log4J may not be available after the ServletContext is shutdown.

The following threads keep running:

org.apache.catalina.startup.Bootstrap at localhost:2738	
	Thread [Clock Daemon] (Running)	
	Thread [Timer-1] (Running)	
	Thread [http-8080-Processor25] (Running)	
	Thread [TP-Processor4] (Running)	
	Thread [DestroyJavaVM] (Running)	


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1689845&group_id=54559

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
openjms-developer mailing list
openjms-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openjms-developer


[prev in list] [next in list] [prev in thread] [next in thread]