I've run into the same problem, too. My notifications in 2.0.0 no longer work in 2.1.0. The problem seems to be that the publisher can't find the the consumer, even though the consumer resource was properly initialized at startup by Muse. I get the following stack trace:
Dec 20, 2006 12:17:29 PM com.cisco.musebox.simplewsnproducer.WsnProducerCapability generateMessages INFO: Waiting 10 seconds before sending message... Dec 20, 2006 12:17:39 PM com.cisco.musebox.simplewsnproducer.WsnProducerCapability generateMessages INFO: Sending messages to consumers... (Count 0) Dec 20, 2006 12:17:40 PM org.apache.muse.util.LoggingUtils logError INFO: There was an error while processing a request: Server returned HTTP response code: 500 for URL: http://171.69.154.232:8080/MuseBox/services/SimpleWsnConsumer org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien t.java:279) org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien t.java:235) org.apache.muse.ws.notification.remote.NotificationConsumerClient.notify (NotificationConsumerClient.java:95) org.apache.muse.ws.notification.impl.SimpleSubscriptionManager.publish(S impleSubscriptionManager.java:205) org.apache.muse.ws.notification.impl.SimpleNotificationProducer.publish( SimpleNotificationProducer.java:434) com.cisco.musebox.simplewsnproducer.WsnProducerCapability.generateMessag es(Unknown Source) com.cisco.musebox.simplewsnproducer.WsnProducerCapability.access$000(Unk nown Source) com.cisco.musebox.simplewsnproducer.WsnProducerCapability$1.run(Unknown Source) ------------------------------------------ Dec 20, 2006 12:17:40 PM org.apache.muse.ws.notification.impl.SimpleSubscriptionManager publish INFO: [ID = 'LastPublishFailed'] The last notification published via wsnt:Notify failed to reach its destination. The consumer may be unavailable. The original error was: Server returned HTTP response code: 500 for URL: http://171.69.154.232:8080/MuseBox/services/SimpleWsnConsumer I've also tested the 2.1.0 wsn-producer/consumer samples (which I believe is just a copy from 2.0.0) in a Tomcat/Axis2 environment, and they have the same problem, too. -Vinh -----Original Message----- From: Scandelli Francesco [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 20, 2006 7:45 AM To: [email protected] Subject: problem with WS-N producer/consumer when switching from Muse 2.0.0. to 2.1.0 Hi Some weeks ago I successfully developed two services with Muse 2.0.0: a WS-N Producer and a related WS-N Consumer. Yesterday I downloaded Muse 2.1.0 and, after * having substituted the old jars with the new ones * having modified the deployment schema in accordance with the the new Muse 2.1.0 rules (muse.xml, router-entries/, wsdl/ in WEB-INF/classes) * having substituted the old axis2.xml with the new one * having replaced the old .mar files with the new ones in WEB-INF/modules ,the producer still works well (I can make WS-N subscriptions) whereas I got an error when the producer tries to notify an event to the consumer: INFO: There was an error while processing a request: Server returned HTTP response code: 500 for URL: http://localhost:8080/EventBrowser/services/consumer org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien t.java:279) org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien t.java:235) org.apache.muse.ws.notification.remote.NotificationConsumerClient.notify (NotificationConsumerClient.java:95) org.apache.muse.ws.notification.impl.SimpleSubscriptionManager.publish(S impleSubscriptionManager.java:205) org.apache.muse.ws.notification.impl.SimpleNotificationProducer.publish( SimpleNotificationProducer.java:434) com.italtel.X733AlarmProducer.ThreadPublisher.run(ThreadPublisher.java:4 7) To be noted that the consumer service is active in the axis2 framework and that the action used within the notify message is present in WEB-INF/services/muse/META-INF/services.xml, does anybody has an idea about this issue? Thanks Francesco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
