[Remoting] - JBoss-4.2.3 Web Service exception
by riveradon
Hey all.
I have been trying to move to JBoss-4.2.3 with no luck. Everything thing works great with the JBoss-4.2.1 libraries but not JBoss-4.2.3. The below exception is being thrown from the version of JBoss-remoting.jar that comes with JBoss- 4.2.3. The code works as expected running with the version that comes with JBoss-4.2.1. I have started to debug the issue, but was wondering if anyone has any ideas on what could cause this:
Exception
| 03:47:45 ERROR [TestClient] registerService : Exception:
| 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 $Proxy6.isWorking(Unknown Source)
| at TestClient.registerService(TestClient.java:73)
| at TestClient.main(TestClient.java:91)
| 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)
| ... 5 more
| 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:239)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:151)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:160)
| at org.jboss.remoting.Client.invoke(Client.java:1708)
| at org.jboss.remoting.Client.invoke(Client.java:612)
| at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:233)
| ... 8 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.util.SecurityUtility.getOutputStream(SecurityUtility.java:1446)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:324)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:221)
| ... 13 more
|
Simple Test Code :
| URL url = new URL("http://ssdr_server:8080/ssdi-ssdr/test?wsdl");
| QName qName = new QName("http://bla.com/", "TestService");
| Service service = Service.create(url, qName);
| Test servicePort = service.getPort(Test.class);
| servicePort.isWorking();
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173817#4173817
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173817
17 years, 7 months
[Installation, Configuration & DEPLOYMENT] - Starting JAS in Debug mode
by cdiggins
I am having a problem starting JAS in debug mode, and don't know what could be causing it since I got the error using 4.2.2GA and then did a clean install of 4.2.3GA and still have the same error.
What happens is when I try to start my server in debug mode through myEclipse, It stops after
16:04:38,213 INFO [Server] Starting JBoss (MX MicroKernel)...
16:04:38,213 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
16:04:38,213 INFO [Server] Home Dir: C:\jboss-4.2.3.GA
16:04:38,213 INFO [Server] Home URL: file:/C:/jboss-4.2.3.GA/
16:04:38,213 INFO [Server] Patch URL: null
16:04:38,213 INFO [Server] Server Name: default
16:04:38,213 INFO [Server] Server Home Dir: C:\jboss-4.2.3.GA\server\default
16:04:38,213 INFO [Server] Server Home URL: file:/C:/jboss-4.2.3.GA/server/default/
16:04:38,213 INFO [Server] Server Log Dir: C:\jboss-4.2.3.GA\server\default\log
16:04:38,213 INFO [Server] Server Temp Dir: C:\jboss-4.2.3.GA\server\default\tmp
16:04:38,213 INFO [Server] Root Deployment Filename: jboss-service.xml
16:04:38,464 INFO [ServerInfo] Java version: 1.6.0_03,Sun Microsystems Inc.
16:04:38,464 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0_03-b05,Sun Microsystems Inc.
16:04:38,464 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
as if it has hit a breakpoint, and in the development window I get the message 'Source not found for XMLEntityScanner.load(int, boolean) line: not available'
Pressing the continue execution button just brings up more of the same error. If anyone has an idea of what could be causing this, or anything else I can check, please share.
Thanks,
CDiggins
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173813#4173813
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173813
17 years, 7 months