Hide Forgot
project_key: SOA To recreate: 1) Start ER4 server 2) Deploy bpel_simple_correlation quickstart, execute the quickstart, undeploy the quickstart 3) Shutdown the server (check the log) 4) Startup the server (check the log) server.log is attached - the exception raised is: 2011-09-20 15:20:09,420 ERROR [org.jboss.ws.core.CommonClient] (Timer-2) Exception caught while (preparing for) performing the invocation: java.io.IOException: Could not transmit message at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:267) at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:360) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:232) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:171) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:157) at $Proxy437.notifySubscriptionListener(Unknown Source) at org.apache.juddi.subscription.notify.HTTPNotifier.notifySubscriptionListener(HTTPNotifier.java:54) at org.apache.juddi.subscription.SubscriptionNotifier.notify(SubscriptionNotifier.java:332) at org.apache.juddi.subscription.SubscriptionNotifier.run(SubscriptionNotifier.java:147) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s) at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:271) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:176) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169) at org.jboss.remoting.Client.invoke(Client.java:2070) at org.jboss.remoting.Client.invoke(Client.java:879) at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:246) ... 11 more Caused by: org.jboss.ws.WSException: Invalid HTTP server response [404] - Not Found at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:608) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:402) at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:253) ... 16 more
Attachment: Added: server.log
Is the endpoint not undeployed?
Attachment: Added: SOA-3395-Screenshot.png
Hi Len - I believe this is the same issue as the stack trace you recently added to SOA-3068. Not sure if you want to close this one as a duplicate? If not, can you assign to Kurt.
Candidate for 5.2
I grabbed it. Please let's close SOA-3068 and let's track this issue here.
I opened https://issues.apache.org/jira/browse/JUDDI-531 for this.
jUDDI now handles the "can't connect case" gracefully, however the JBossWS stack logs and error, see http://www.docjar.com/html/api/org/jboss/ws/core/CommonClient.java.html, line 404 (no pun intended): log.error("Exception caught while (preparing for) performing the invocation: ", ex); I think this may need to be debug level since it is part of 'normal' operating circumstances!
So unfortunately at the moment we may still see these kind of log messages: 23:29:27,877 INFO [SubscriptionNotifier] Sending out notification to http://localhost:8080///subscriptionlistener_riftsaw-manager 23:29:28,887 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation: java.io.IOException: Could not transmit message at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:267) at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:360) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:232) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:171) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:157) at $Proxy418.notifySubscriptionListener(Unknown Source) at org.apache.juddi.subscription.notify.HTTPNotifier.notifySubscriptionListener(HTTPNotifier.java:54) at org.apache.juddi.subscription.SubscriptionNotifier.notify(SubscriptionNotifier.java:347) at org.apache.juddi.subscription.SubscriptionNotifier.run(SubscriptionNotifier.java:161) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s) at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:271) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:176) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169) at org.jboss.remoting.Client.invoke(Client.java:2070) at org.jboss.remoting.Client.invoke(Client.java:879) at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:246) ... 11 more Caused by: org.jboss.ws.WSException: Invalid HTTP server response [404] - Not Found at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:608) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:402) at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:253) ... 16 more
Some already opened a jira for it: https://issues.jboss.org/browse/JBWS-3299
Fixed in juddi 3.1.2, will be included in ER5.
Release Notes Docs Status: Added: Not Required Writer: Added: dlesage
Verified in 5.2.0.ER5