Hallo and Thank you!!

Now I see: The problem has nothing to do with TomEE.

It is a problem on the client side and how I mange the connection.

Ingo





> Gesendet: Montag, 02. Mai 2016 um 09:09 Uhr
> Von: "Romain Manni-Bucau" <[email protected]>
> An: "[email protected]" <[email protected]>
> Betreff: Re: Container has suffered a SystemException
>
> Hi
> 
> did you tune tomee.security.identity.schedule and
> tomee.security.identity.timeout? Defaults are 1mn (60000 - value in ms) and
> 30mn (1800000 - value in ms) and can lead to that if second value is
> reached without interactions with the logged in session (remote ejb).
> 
> 
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
> <http://www.tomitribe.com> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
> 
> 2016-05-01 22:29 GMT+02:00 Ingo Mahnke <[email protected]>:
> 
> > Hallo,
> > maybe anybody can help me. Today we try to to use tomee in real productiv
> > usage.
> > After two hours of online the folling exection occurs:
> >
> >
> >
> > javax.ejb.EJBException: Container has suffered a SystemException
> >
> > org.apache.openejb.client.EJBObjectHandler._invoke(EJBObjectHandler.java:224)
> >
> > org.apache.openejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:136)
> >
> > org.apache.openejb.client.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49)
> >         com.sun.proxy.$Proxy37.readUser(Unknown Source)
> >
> > com.quvion.webclient.portal.CheckInFilter.doFilter(CheckInFilter.java)
> > root cause
> >
> > java.rmi.RemoteException: Client identity is not valid -
> > EJBRequest{deploymentId='QuvionEMXBean', type=EJB_OBJECT_BUSINESS_METHOD,
> > Body{ejb=null, orb=null, methodInstance=null, interfaceClass=null,
> > methodName='null', methodParamTypes=null, methodParameters=null,
> > primaryKey=null, requestId='null', version=2}}; nested exception is:
> >         javax.security.auth.login.LoginException: Identity is not
> > currently logged in: 26abe643-472c-4d77-b9ea-bc174b9ceb46
> >
> > org.apache.openejb.server.ejbd.EjbRequestHandler.setResponseError(EjbRequestHandler.java:591)
> >
> > org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:115)
> >
> > org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:344)
> >
> > org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:240)
> >
> > org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:104)
> >
> > org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58)
> >         javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> > root cause
> >
> > javax.security.auth.login.LoginException: Identity is not currently logged
> > in: 26abe643-472c-4d77-b9ea-bc174b9ceb46
> >
> > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:265)
> >
> > org.apache.openejb.core.security.AbstractSecurityService.associate(AbstractSecurityService.java:64)
> >
> > org.apache.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:111)
> >
> > org.apache.openejb.server.ejbd.EjbDaemon.processEjbRequest(EjbDaemon.java:344)
> >
> > org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:240)
> >
> > org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:104)
> >
> > org.apache.openejb.server.httpd.ServerServlet.service(ServerServlet.java:58)
> >         javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> >
> > We are using Tomee 1.7.4. Atfer restart everything runs fine for about 2
> > hours, then this exception occurs again.
> >
> >
> >
> > Thank you
> > Ingo
> >
> >
> >
> 

Reply via email to