Hi David, If you turn the SOAP tracing on for subscriptions, you can see the SOAP message that went out just prior to the exception. The wsa:To SOAP header will have the address of the consumer that is not responding. The info on this setting is at the bottom of this page:
http://ws.apache.org/muse/docs/2.0.0/manual/capabilities/wsn-sub.html That said, a custom message would be better than the terse java.net message. If you open a JIRA item for it, I will add some subscription data to the log message so you don't have to compare against the SOAP. Dan [EMAIL PROTECTED] wrote on 10/23/2006 10:47:19 AM: > Hi everyone, > > I was using pubscribe1.1. and now I've started to try muse-2.0. For both > distributions I got the same question: when a consumer goes down I can > read in the producer log the next exception (muse-2.0 log): > > INFO: There was an error while processing a request: > > Connection refused > > > org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254) > > org.apache.muse.ws.notification.remote.NotificationConsumerClient. > notify(NotificationConsumerClient.java:95) > > org.apache.muse.ws.notification.impl.SimpleSubscriptionManager. > publish(SimpleSubscriptionManager.java:204) > > org.apache.muse.ws.notification.impl.SimpleNotificationProducer. > publish(SimpleNotificationProducer.java:435) > org.apache.ws.muse.test.wsrf.MyCapability$1.run(Unknown Source) > > > If there are some consumers subscribed to the same topic, is it possible > to know in the producer side which consumer is exactly causing the > error? How can I do it? > Thanks, > > David > > > --------------------------------------------------------------------- > 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]
