error 60002 wen running webapp via agile

when trying to load a webapp with agile api (on tomcat). getting the following error 

Error code : 60002

Error message : You have not logged in.

Root Cause exception : java.lang.NoClassDefFoundError: weblogic/rjvm/PeerGoneEvent

 

        com.agile.api.AgileSessionFactory.createSession(AgileSessionFactory.java:1042)

        utils.webUtils.getAgileSession(webUtils.java:116)

        org.apache.jsp.InputForm_jsp._jspService(InputForm_jsp.java:101)

        org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:728)

        org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)

        org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)

        org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)

        javax.servlet.http.HttpServlet.service(HttpServlet.java:728)

        org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java

it worked when i changed one of the jar files at the weblogic temp folder classpath (maybe it was a different version) . not sure if that was the solution

the question is:
in addition to the tomcat’s web/web-inf/lib folder,
where else should the class jar files be ? in the agile managed server or somewhereelse? how can i know which jar is the problem?

Hi,
How are you creating the IAgileSession? Can you please share the code?
Are you using the FileManager tomcat installed with Agile or another one?
Thank You

on August 9, 2016.
Add Comment
3 Answer(s)

seems like the issue happens when the admin/managed services of Agile are restarted after the tomcat started.

a workaround will be to restart the tomcat after every Agile restart

Agile User Answered on December 24, 2019.
Add Comment

Did you find resolution on this?  Can you share how if ‘yes’ please.

Agile Angel Answered on December 7, 2016.
Add Comment

All of sudden faced same exception today while executing the Web-App which was in use for last year or so.

In order to resolve this, restarted the Apache tomcat services and killed the stale ids and things came back to normal.

Agile Angel Answered on February 28, 2019.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.