[JBossWS] - Issues with WS-Eventing and JBoss-4.2.3
by riveradon
Hey all,
I am having issues running under JBoss-4.2.3 with regards to WS-Eventing. The same code and configuration worked between JBoss-4.2.1 and JBoss-4.2.2. Now I am hitting a snag trying to execute the same code either standalone or within the JBoss environment. Listed below is the stack trace.
| javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
| 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:172)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
| at $Proxy13.registerService(Unknown Source)
| at com.issinc.atd.situationadvisory.eventing.Test.registerService(Test.java:102)
| at com.issinc.atd.situationadvisory.eventing.Test.main(Test.java:120)
| 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:585)
| at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
| Caused by: java.io.IOException: Could not transmit message
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:255)
| at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:73)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:339)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
| ... 10 more
| Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused: connect.
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:233)
| ... 13 more
| Caused by: java.net.ConnectException: Connection refused: connect
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
| at java.net.Socket.connect(Socket.java:520)
| at sun.net.NetworkClient.doConnect(NetworkClient.java:152)
| at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
| at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
| at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
| at sun.net.www.http.HttpClient.New(HttpClient.java:304)
| at sun.net.www.http.HttpClient.New(HttpClient.java:321)
| at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
| at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
| at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
| at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:857)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:277)
| ... 18 more
|
Any ideas on what the cause for the above exception would be greatly appreciated.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173121#4173121
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173121
17 years, 1 month
[JBossWS] - Interoperability issue between JBoss service and gSOAP clien
by navinbhat
Environment:
JBOSS AS 4.2.3,JBoss-native-3.0.3,JDK 5 update 15,Windows XP SP2,Eclipse 3.3.x.
Description:
I generated service code from wsdl using wsconsume (contract first approach). I wrote the service skeleton code as a stateless EJB, where in i have a operation which recieves and sends back an MTOM attachment. I have enabled MTOM using the following annotation.
@BindingType(value="http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true").I deployed the service in JBoss Application server 4.2.3.
The SOAP 1.2 client is written in gSOAP framework (Running on linux) generated from the same wsdl file.When the gSOAP client sends an MTOM attachment the JBoss service throws an exception, the stack trace is shown below.
NOTE: The same JBoss service works fine with JBoss client.
Stack trace
12:11:27,705 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.soap.SOAPException: Cannot decode multipart related message
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:253)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:457)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.mail.internet.ParseException: Expected ';', got "/"
at javax.mail.internet.ParameterList.(ParameterList.java:179)
at javax.mail.internet.ContentType.(ContentType.java:100)
at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.isValidRootType(MultipartRelatedDecoder.java:80)
at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:160)
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:241)
... 25 more
Let me know if more detail is required,
Thanks in advance,
Navin Bhat
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173014#4173014
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173014
17 years, 1 month
[JBossWS] - Native WS-Reliable Messaging Error - The RM Destination requ
by kerryrward
I am trying to implement a web service that does both MTOM-XOP and reliable messaging. I have the service running with MTOM-XOP and patterned it after the MTOMEndPoint EJB3 example provided in the jboss native ws 3.0.2. I am running JBoss 4.2.2.
I then tried to implement the steps from the Reliable Messaging Tutorial at
http://jbws.dyndns.org/mediawiki/index.php?title=Native_WS-ReliableMessag...
I had problems with the wsdl I modified, so I added the following annotations to the endpoint and let JBOSS build the wsdl instead
@WebService(
| name = "EflexServiceEndpoint",
| serviceName = "EflexService",
| endpointInterface = "com.eflex.webservice.EflexServiceEndpoint"
| // wsdlLocation = "WEB-INF/wsdl/EflexService.wsdl"
| )
| @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
| @BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true")
| @EndpointConfig
| (
| configFile = "META-INF/wsrm-jaxws-endpoint-config.xml",
| configName = "Standard WSRM Endpoint"
| )
| @PolicyAttachment(@Policy(
| policyFileLocation = "META-INF/wsrm-exactly-once-in-order-policy.xml",
| scope = PolicyScopeLevel.WSDL_BINDING)
| )
|
| public class EflexServiceEndpointBean implements EflexServiceEndpoint
| {
|
|
Here is the exception I get:
anonymous wrote : org.jboss.ws.extensions.wsrm.RMFault: The RM Destination requires the use of WSRM
| at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.prepareResponseContext(RMInvocationHandler.java:134)
| at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.invoke(RMInvocationHandler.java:306)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:221)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
| at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
|
Which seems to say that my service is expecting WSRM, but that the client has not implemented it.
Here is my client code.
| public final class EflexServiceClient
| {
|
| private static final String serviceURL = "http://localhost:80/wseflex/EflexService";
|
| public static void main(String[] args) throws Exception
| {
| InputStream is = null;
| if (args.length != 0)
| {
| is = new FileInputStream(args[0]);
| } else {
| is = new ByteArrayInputStream("<test>reqest</test>".getBytes());
| }
|
| QName serviceName = new QName("http://webservice.eflex.com/", "EflexService");
| URL wsdlURL = new URL(serviceURL + "?wsdl");
| Service service = Service.create(wsdlURL, serviceName);
| EflexServiceEndpoint port = (EflexServiceEndpoint)service.getPort(EflexServiceEndpoint.class);
| SOAPBinding binding = (SOAPBinding)((BindingProvider)port).getBinding();
| binding.setMTOMEnabled(true);
| ((StubExt)port).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
|
| Source src = new StreamSource(is);
| SourceRequest request = new SourceRequest();
| request.setData(src);
|
| SourceResponse response = port.echoSource(request);
| Source respSource = response.getData();
|
| ((RMProvider)port).closeSequence();
| ...
|
|
Any help on this is greatly appreciated. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172930#4172930
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172930
17 years, 1 month