I'm not using SessionSynchonization. The bean doesn't do anything special. Unfortunately, I wasn't able to reproduce it, either. It definitely ocurred, though, I guess 50 times out of 500 tries. Might the client be the cause? Because I tried to reduce the size of the jeremie_jonas.jar. I put only those classes into a jar-file which the client really needs. (I figured it out by using the verbose option of the java-interpreter). But as I said, the error The server did not crash after that error. That was my mistake. Torsten -----Ursprüngliche Nachricht----- Von: Philippe Durieux [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 9. Februar 2001 09:53 An: Blumreiter, Fa. Westernacher, IIPS, B; [EMAIL PROTECTED] Betreff: Re: unexpected exception Philippe Durieux wrote: > > "Blumreiter, Fa. Westernacher, IIPS, B" wrote: > > > > Hello folks, > > > > since I have upgraded to jonas 2.2.6 from jonas 2.2.1 I get sometimes the > > following exception: > > > > java.rmi.ServerException: RemoteException occurred in server thread; nested > > exception is: > > java.rmi.server.ExportException: object already exported > > java.rmi.server.ExportException: object already exported > > 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 > > dpag.ass.application.dispatcher.JOnASdispatcherHome_Stub.create(classes\dpag > > \ass\application\dispatcher\JOnASdispatcherHome_Stub.java:42) > > at > > dpag.ass.connector.CSConnectorThread.<init>(CSConnectorThread.java:116) > > at > > dpag.ass.presentation.RunASSClient.initConnection(RunASSClient.java:260) > > at > > dpag.ass.presentation.RunASSClient.initJECallBack(RunASSClient.java:210) > > at dpag.ass.presentation.ASSClient.start(ASSClient.java:136) > > at dpag.ass.presentation.ASSClient.main(ASSClient.java:59) > > > > I am not yet able to reproduce it. When this error occurs no client can > > connect to the server anymore and the server has to be restarted. Then, the > > error is gone. > > > > Can anyone explain this phenomenon? > Not yet, but I'm working on it. > I need more information. What kind of bean are you calling when the > error > occurs ? (session stateless, statefull, ??) > What kind of methods do you use (create + method + remove, no explicit > remove) ? > Any other useful information appreciated... > > > > Thanks > > > > Torsten > > > > P.S. Transaction attribute as usual: required, stateful session bean OK. Sorry, I didn't notice this line... In fact, I tried to reproduce the problem, but I was not able to do it. Does your bean implement SessionSynchronization ? Is your bean doing something special ? > > ---- > > 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". > > -- > Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Bull - 1 rue de Provence - 38432 Echirolles Cedex France > [EMAIL PROTECTED] > -> Download our EJBServer at http://www.evidian.com/ejb <- > ---- > 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". -- Philippe Durieux ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bull - 1 rue de Provence - 38432 Echirolles Cedex France [EMAIL PROTECTED] -> Download our EJBServer at http://www.evidian.com/ejb <- ---- 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". ---- 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".
