Ceki, I believe you are right. I am trying to wrap an exception with a new custom exception, and I believe this is where the error is occuring. I can get basic logging to work fine over the JMS bus. I will look into this more tomorrow, and keep you up to date. Thanks for the help so far... -Alex [EMAIL PROTECTED] on 07/31/2001 05:38:12 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Alex X Benke) Subject: Re: Upgrading to 1.1.3 and JMS
Alex, Vow. Although I do not think it is a log4j problem, I'll double check and let you know. Regards, Ceki At 15:52 31.07.2001 -0400, you wrote: >I checked my classpath to make sure the old jar is out and have changed my code >that that I'm publishing a message and then pulling it down in the same method >(1 process) and it still gives the same error... anyone have other ideas? > >thanks >Alex > > > > > >[EMAIL PROTECTED] on 07/31/2001 12:55:33 PM > >Please respond to [EMAIL PROTECTED] > >To: [EMAIL PROTECTED] >cc: (bcc: Alex X Benke) >Subject: Re: Upgrading to 1.1.3 and JMS > > > > >Alex, > > >You probably have different versions on log4j running on the client side and the >server side. HTH, Ceki > >At 10:30 31.07.2001 -0400, Alex X Benke wrote: >>I've just upgraded to 1.1.3 and for some reason I'm having a problem with my >JMS >>publish/subscribe. The publish works fine, but when I pull the message off the >>bus (type LoggingEvent) it gives the following message: >> >>------------------------------ >>log4j:WARN Priority deserialization failed, reverting to default. >> >>java.lang.NoSuchMethodException >> >> at java.lang.Class.getMethod0(Native Method) >> >> at java.lang.Class.getDeclaredMethod(Class.java:1156) >> >> at org.apache.log4j.spi.LoggingEvent.readPriority(LoggingEvent.java:234) >> >> at org.apache.log4j.spi.LoggingEvent.readObject(LoggingEvent.java:249) >> >> at java.lang.reflect.Method.invoke(Native Method) >> >> at >>java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2213) >> >> at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1410) >> >> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386) >> >> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236) >> >> at com.ibm.jms.JMSObjectMessage.getObject(JMSObjectMessage.java:216) >> >> at >>com.jpmorgan.u2.infrastructure.logging.jms.U2LoggingMainJMSSubscriber.onMessage(U2LoggingMainJMSSubscriber.java:260) > >> >> at >>com.ibm.mq.jms.MQTopicSubscriber.receiveAsync(MQTopicSubscriber.java:681) >>-------------------------------- >> >>Any ideas what could be causing this? >> >>thanks, >>Alex -- Ceki Gülcü - http://qos.ch --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
