javax.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request


Solutions on the web51

Solution icon of github
via GitHub by Fraid
, 9 months ago
RESTEASY004655: Unable to invoke request

Solution icon of stackoverflow
RESTEASY004655: Unable to invoke request

Solution icon of github
via GitHub by samskiter
, 1 year ago
RESTEASY004655: Unable to invoke request

Solution icon of github
RESTEASY004655: Unable to invoke request

Solution icon of github
RESTEASY004655: Unable to invoke request

Solution icon of googlegroups
via Google Groups by Emory Penney, 7 months ago
RESTEASY004655: Unable to invoke request

Solution icon of web
via nabble.com by Unknown author, 6 months ago
RESTEASY004655: Unable to invoke request

Solution icon of github
RESTEASY004655: Unable to invoke request

Solution icon of github
RESTEASY004655: Unable to invoke request

Solution icon of jboss
via JBoss Issue Tracker by Gary Brown, 4 months ago
RESTEASY004655: Unable to invoke request

Stack trace

javax.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:287)
	at org.jboss.resteasy.client.jaxrs.internal.ClientInvocation.invoke(ClientInvocation.java:436)
	at org.jboss.resteasy.client.jaxrs.internal.proxy.ClientInvoker.invoke(ClientInvoker.java:102)
	at org.jboss.resteasy.client.jaxrs.internal.proxy.ClientProxy.invoke(ClientProxy.java:64)
	at com.sun.proxy.$Proxy31.getAll(Unknown Source)
	at org.mycontroller.restclient.philips.hue.clients.DefaultLightsClient.listAll(DefaultLightsClient.java:54)
	at org.mycontroller.standalone.gateway.philipshue.PhilipsHueGatewayPoller.run(PhilipsHueGatewayPoller.java:76)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketException: Network is unreachable
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
	at org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine.invoke(ApacheHttpClient4Engine.java:283)
	... 7 more

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Once, 1 year ago
4 times, 3 months ago
2 times, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
108 more bugmates