OK, so my client manages to connect to the server and
successfully call a method on a session bean, get some
data back, and display it. Then, on some client action, another
object within the same client program gets a reference to
another session bean, and when it calls a method, this is returned:
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.ServerException: Transaction rolled back; nested exception is:
java.lang.IllegalStateException: No security context set
java.rmi.ServerException: Transaction rolled back; nested exception is:
java.lang.IllegalStateException: No security context set
java.lang.IllegalStateException: No security context set
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker_Stub.invoke(Unknown Source)
at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:357)
at org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(StatelessSessionProxy.java:123)
Ideas, anybody? I haven't been using JBoss for particularly long,
so this could be a trivial newbie problem, but it certainly doesn't
come up in Google or the documentation search.
It's a pretty standard bean, in fact, it's the same bean that gets
called the first time around. The is no jboss.xml, JBoss 2.4.4,
Blackdown JDK 1.3.1.
Thanks...
Yes, I was being an idiot. The code was querying the principle,
but it's an anonymous connection.
Sorry for wasting the bandwidth...