Thanks for the response! Yes I've used OpenJMS with Caucho Resin the past without a problem, however I did write my own session management class - it was very messy though - which is the reason messenger looks so appealing :)
I'll look into writing my own SessionFactory implementation which at least gives me a more organized structure to do it in. What is weird is it's talking to OpenJMS in some way now, if my OpenJMS isn't running it tells me so in the debug log. I'm not sure how to get a better stack trace out of the debug stuff. It doesn't look hard to make my own session factory anyways. Ryan -----Original Message----- From: James Strachan [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 09, 2003 8:35 AM To: Jakarta Commons Users List Subject: Re: messenger: running on caucho resin Knowing the stack trace of the underlying NotSerializableException would help some. From what you've given it looks like Messenger is trying to lookup a JMS TopicConnectionFactory from JNDI and failing with a Resin-generated NotSerializableException message. First off; can you get OpenJMS to work with Resin at all? i.e. lookup an OpenJMS TopicConnectionFactory in Resin's JNDI? What could well be easier for you is to write a plugin for Messenger, a SessionFactory implementation... http://jakarta.apache.org/commons/sandbox/messenger/apidocs/org/apache/c ommons/messenger/SessionFactory.html which explicitly creates OpenJMS connections. Then you don't need to worry about JNDI. All you need to do is implement the createConnectionFactory() method to create an OpenJMS specific ConnectionFactory and you're away. FWIW SpiritWave comes with its own Messenger factory to avoid the need to use JNDI to create JMS connections with Messenger; I'm sure the same could be done for OpenJMS. James ------- http://radio.weblogs.com/0112098/ ----- Original Message ----- From: Ryan Vanderwerf To: [EMAIL PROTECTED] Sent: Wednesday, January 08, 2003 10:20 PM Subject: messenger: running on caucho resin Hi, I'm a newbie to the messenger sandbox project, and had a couple questions on getting it running with Cacho Resin 2.1.6. I'm running the latest OpenJMS server, running with the default queue in rmi_jms.xml and the pre-packaged Messenger.xml that comes with messenger for OpenJMS. My problem is when I start the managerServlet everything seems to run fine except for an NotSerializable error I get on startup - this is the debug info it spits out: [2003-01-08 16:05:32,739] DEBUG [main] [digester.Digester] [SetNextRule]{manager /messenger} Call org.apache.commons.messenger.MessengerManager.addMessenger(org. apache.commons.messenger.DefaultMessenger@7fc686 session: javax.jms.JMSException : Failed to lookup: JmsTopicConnectionFactory using JNDI. javax.naming.NamingExc eption: error marshalling arguments; nested exception is: java.io.NotSerializableException: com.caucho.util.ClassLoaderLocal [Root exception is java.rmi.MarshalException: error marshalling arguments; nested exc eption is: java.io.NotSerializableException: com.caucho.util.ClassLoaderLocal]) Does anyone that uses messenger lead me in the right direction? It looks like a very slick app, in the past I've had to write all the connection management stuff for JMS manually which was plenty of work - messenger seems to take care of all that. I'm just wondering what I am missing here, or if it just doesn't work on resin (I don't see why it wouldn't) especially if I am using the build in JNDI server in OpenJMS. Ryan More debug info that it spat out attached: ------------------------------------------------------------------------ ------ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
