[jbossws-issues] [JBoss JIRA] (JBWS-3599) ServiceDelegate failed even after service back available

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754355#comment-12754355 ] 

Alessio Soldano commented on JBWS-3599:
---------------------------------------

The jbossws-native stack has reached EOL and is hence not supported anymore in community versions. Please check if this is an outstanding issue with current jbossws-cxf stack, otherwise this will simply be closed. Thanks.
                
> ServiceDelegate failed even after service back available 
> ---------------------------------------------------------
>
>                 Key: JBWS-3599
>                 URL: https://issues.jboss.org/browse/JBWS-3599
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions: jbossws-native-3.3.1
>            Reporter: Jay Liu
>
> Criteria :
> service down => client request => client fail => service up => client request
> Expected Result :
> Client success when service back up and running.
> Actual :
> client will still throw exception "Target endpoint address not set".
> JDK6's jaxws implementation acts correctly on this.
> update
> ----
> stacktrace 
> {code}
> javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
> 	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:181)
> 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:161)
> 	at $Proxy31.event(Unknown Source)
> 	at com.evenex.ws.test.TestJbosswsClient.testEventLog(TestJbosswsClient.java:64)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> 	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> 	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> 	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> 	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: org.jboss.ws.WSException: Target endpoint address not set
> 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:358)
> 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> 	... 27 more
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira