JdkDynamicAopProxy.invoke() has thrown a RemoteAccessException

org.springframework.remoting.RemoteAccessException
Javadoc
Generic remote access exception. A service proxy for any remoting protocol should throw this exception or subclasses of it, in order to transparently expose a plain Java business interface.

When using conforming proxies, switching the actual remoting protocol e.g. from Hessian does not affect client code. Clients work with a plain natural Java business interface that the service exposes. A client object simply receives an implementation for the interface that it needs via a bean reference, like it does for a local bean as well.

A client may catch RemoteAccessException if it wants to, but as remote access errors are typically unrecoverable, it will probably let such exceptions propagate to a higher level that handles them generically. In this case, the client code doesn't show any signs of being involved in remote access, as there aren't any remoting-specific dependencies.

Even when switching from a remote service proxy to a local implementation of the same interface, this amounts to just a matter of configuration. Obviously, the client code should be somewhat aware that it might be working against a remote service, for example in terms of repeated method calls that cause unnecessary roundtrips etc. However, it doesn't have to be aware whether it is actually working against a remote service or a local implementation, or with which remoting protocol it is working under the hood. @author Juergen Hoeller @since 14.05.2003

at org.springframework.remoting.rmi.RmiClientInterceptorUtils.convertRmiAccessException
(source)
at org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.handleRemoteException
(source)
at org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.doInvoke
(source)
at org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.invoke
(source)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed
(source)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke
(source)
5 frames hidden

Typical Exception Messages

  1. Could not access remote service [SomeServicePort]; nested exception is java.net.MalformedURLException
  2. Could not access remote service [{http://com.dimg.poll.ws}ReportAPISoap12]; nested exception is No client transport named 'null' found!

External results for this pattern (2)

  1. Unknown authorvia spring.io4 months ago
    Could not access remote service [{http://com.dimg.poll.ws}ReportAPISoap12]; nested exception is No client transport named 'null' found!
    Show stack trace
  2. Chrispievia Stack Overflow4 months ago
    Could not access remote service [SomeServicePort]; nested exception is java.net.MalformedURLException
    Show stack trace