After running our JOnAS 2.2.6 EJB server (on Solaris w/JDK1.3.0) for several
days or even weeks, we get a flurry of exceptions, rendering the server
unusable. This has happened on 10-Jul-2001, 25-Jul-2001, and again today
30-Jul-2001. The sever has not been shut down for any reason other than
this.
Stack trace is:
2001.07.30 10:05:39.297 PDT RMI TCP Connection(51171)-10.32.56.168
kovair.trace:err - java.lang.NullPointerException
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteC
all.java:245)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:354)
at
org.objectweb.jonas.rmifilters.RemoteStub.invoke(RemoteStub.java:87)
at
com.kovair.webdialog.manager.authorization.JOnASAuthorizationManagerRemote_S
tub.createPermission(JOnASAuthorizationManagerRemote_Stub.java:233)
at
com.kovair.webdialog.manager.feature.FeatureManagerBean.canAccess(FeatureMan
agerBean.java:931)
at
com.kovair.webdialog.manager.feature.FeatureManagerBean.getComponents(Featur
eManagerBean.java:1046)
at
com.kovair.webdialog.manager.feature.JOnASFeatureManagerRemote.getComponents
(JOnASFeatureManagerRemote.java:133)
at
com.kovair.webdialog.manager.feature.JOnASFeatureManagerRemote_Skel.dispatch
(JOnASFeatureManagerRemote_Skel.java:274)
at
sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:319)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:187)
at sun.rmi.transport.Transport$1.run(Transport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:6
43)
Note that the FeatureManagerBean.canAccess() method in the above stack trace
is invoked very frequently.
The AuthorizationManagerBean.createPermission() method simply constructs a
very simple Object and returns it.
We are sure the problem is not in our applicaiton code surrounding this
call. The code could not be any simpler.
Why would this start happening suddenly after running for days or even
weeks?
BTW, I am aware of earlier postings that suggest the file referenced in
java.security.policy property is invalid.
Our contains:
grant {
// Allow everything for now
permission java.security.AllPermission;
};
Any ideas about what is causing this???
Ralph Harnden
Kovair, Inc.
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
