Session expired in Servlet, JasperException, NullPointerException

Hi,
I get an exception on line "rd.forward(request,response);" when session is expired and so null as you can see in the stack trace. First time, session is null and I don't get an exception. if my session is not expired, it's going in the "else" block and it's works. However, as soon as my session expires, I get the exception as described in my first sentence and as you can see just bellow.
I really don't understand why and hope someone could help me.
I'm using jdk1.5 with Tomcat 5.5
Thanks in advance
Etienne.
public void doPost(HttpServletRequest request,HttpServletResponse response) throws ServletException, IOException
     try
          HttpSession session = request.getSession(false);
          int action = Integer.parseInt(request.getParameter(ATTR_ACTION));
          String url = urlLogin;
          if(session == null)
               session = request.getSession(true);
               session.setAttribute(ATTR_ERROR,"true");
               session.setAttribute(ATTR_MESSAGE,MESSAGE_SESSION_EXPIRED);
          else
               // my code
          RequestDispatcher rd = request.getRequestDispatcher(url);
          rd.forward(request,response);
     catch(Exception ex)
          ex.printStackTrace();
3 mai 2005 15:27:11 org.apache.catalina.core.ApplicationDispatcher invoke
GRAVE: "Servlet.service()" pour la servlet jsp a lanc� une exception
java.lang.NullPointerException
     at org.apache.jsp.webcose_jsp._jspService(org.apache.jsp.webcose_jsp:96)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:673)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:464)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:399)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
     at controller.WebcoseController.doPost(WebcoseController.java:2771)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)
3 mai 2005 15:27:11 org.apache.catalina.core.StandardWrapperValve invoke
GRAVE: "Servlet.service()" pour la servlet jsp a g�n�r� une exception
java.lang.NullPointerException
     at org.apache.jsp.webcose_jsp._jspService(org.apache.jsp.webcose_jsp:96)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:99)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:325)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:245)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)

The error happens in your JSP file that you forwarded the request to, not in the code you posted.
java.lang.NullPointerException
at org.apache.jsp.webcose_jsp._jspService(org.apache.jsp.webcose_jsp:96)
You need to go diagnose the code there and see where you're using an object whose value is null.

Similar Messages

  • Session expires when servlets are reloaded

    Hi
    I'm using Sun Java System Web server 7.0 on Windows 2003 server. When I update my servlets the session expires. I update the .reload filen and the servlets reloads perfect, but my users session expires.
    Is it posible to reload servlets without session expires ? And how do I do that ?
    Regards,
    Stian Martinsen
    Norway
    Edited by: StianNorway on Sep 14, 2007 3:59 AM

    I don't know about Sun's server but with Tomcat, if you are careful to make sure that every object bound to session (directly or indirectly) implements java.io.Serializable, Tomcat will save all your session information to disk when the application restarts so they are all live when it comes back up.
    Read the documentation for your server and see if it has a similar feature.

  • Tomcat session expires after compiling servlet/ class

    Hi,
    Does anybody know why tomcat(4.1) session expires if you modify a serlvet or class and compile it.
    After compiling I refresh the page and I get session invalidated page. And every time I compile I have to relogin.
    Any ideas ? Is there a work around ?

    In serverl.xml, if you have set the reloadable="true" attribute in your <Context/> tag for your web application then each time one of the servlet classes is modified, tomcat will reload the web application. Set reloadable="false" and this will stop.
    tobes

  • SJSAS 9 and JSF - session expiration

    Hi
    I'm developing JSF (1.2) application. I'm using SJSAS 9, EJB 3.0 and toplink. My problem is session expiration. When user session expires and then user click for example on Save button on JSF form, application goes to login page, but after login user receive Internal server Error screen. As I see, session expires but after login, POST request is resend but all related objects don't exist any more (NullPointerException occurs in prerender method). Currently I'm redirecting to main page using following code:
    public static ExternalContext getExternalContext() {
            return FacesContext.getCurrentInstance().getExternalContext();
    getExternalContext().redirect(MAINPAGESTR);
    ...in try catch block ,in prerender method (JSF). Does anybody knows what should I do?

    Have you tried to set a servlet filter to catch the error and build a nicer page?
    If you can tell me how to set up a short session expiration time on Tomcat,
    I can do the tests.
    I am interrested in this issue as I will have to solve it for a project in the
    next 2 weeks.

  • PROBLEM USING FILTER TO KNOW SESSION EXPIRATION

    Hi, i'm using a filter to know when the session expires but it appeasr not to work, so i am a bit confuse because the filter always executes well but when the session gets the timeout and the user send a request it isnt executed, the server redirects the user to the login page.
    I am not sure about it, but is it possible that the reason of why the filter is not executed, is becuase i am using the apache form-authentication????
    filter's code:
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
    HttpServletRequest req;
    RequestDispatcher disp;
    HttpServletResponse res;
    boolean userInSession;
    String forward = getConfig().getInitParameter("sessionClosed");
    req = (HttpServletRequest) request;
    res = (HttpServletResponse) response;
    System.out.println("InFilter");
    userInSession = req.getUserPrincipal() != null;
    if(userInSession) {
    chain.doFilter(request, response);
    System.out.println("Session: " + req.getSession(false).getId());
    System.out.println("Session: " + req.getSession(false).getMaxInactiveInterval());
    System.out.println("getSessionTime: " + req.getSession(false).getCreationTime());
    } else {
    disp = req.getRequestDispatcher(forward);
    disp.forward(request, response);
         res.sendRedirect("http://www.google.com");
    System.out.println("outFilter");
    tnks
    CERR

    Hi Robert,
    thanks very much for ur pointers on the AuthFilter class.. will try that out.
    Robert Greig <[email protected]> wrote:
    Stephen wrote:
    I am using WLS 6.1 and tried using a custom filter to intercept theauthentication
    request submitted from a FORM BASE jsp (using the j_security_checkform).
    However, no matter what i've tried, it is always the authenticationpart that
    gets executed before the filter.
    Any idea how could I intercept the request before the j_security_checkservlet
    calls the security provider for authentication?There is a (now deprecated) class weblogic.servlet.security.AuthFilter.
    I haven't used it because it is deprecated but I think it does what
    you're after.
    In my apps, I make the FORM auth submit to my own servlet which can then
    do what j_security_check does (most although not all is accessible
    through public APIs).
    Robert

  • Session expired with StreamingAMFChannel

    Blaze 4.0
    I have a flex desktop app which has only one consumer using a streaming amfChannel. So there is no producer.
    After 30 minutes my channel gets disconnected, because the httpsession on the server expired. The connection was not idle, because every second 2 messages are streamed.
    I also defined a heartbeatInterval on the channelset, but still the session expires.
    This is the Logging:
    BlazeDS :07/02/2012 19:09:49.165 [DEBUG] [Client.MessageClient] MessageClient created with clientId '696A7855-841D-ABE3-505A-AE5699DF4B4A' for destination 'messages-feed'.
    BlazeDS :07/02/2012 19:39:06.434 [DEBUG] [Client.MessageClient] MessageClient with clientId '696A7855-841D-ABE3-505A-AE5699DF4B4A' for destination 'messages-feed' has been invalidated.
    BlazeDS :07/02/2012 19:39:06.435 [DEBUG] [Client.FlexClient] FlexClient with id '696A75CE-8B0E-949A-47CC-9F8256CC96F7' has been invalidated.
    Consumer:
    <mx:Consumer id="consumer"
                                                       destination="messages-feed"
                                                       channelSet="{channelSet}"
                                                       resubscribeInterval="5000"
                                                       resubscribeAttempts="-1"
                                                       message="messageHandler(event)"
                                                       channelDisconnect="consumerDisconnectHandler(event)"
                                                       />
    Why is the HTTP session expiring? Is that because only messages are pushed in the direction from server to client?

    Thanks for your reply, but I already had defined <server-to-client-heartbeat-millis> on my server and the heartbeatInterval on my Client ChannelSet.
    This is really annoying and I can't imagine I'm the only one seeing this behaviour. I'm just doing common things with BlazeDS.
    Does anyone knows what is causing this?
    Here is my channel definition:
    <channel-definition id="my-streaming-amf" class="mx.messaging.channels.StreamingAMFChannel">
                <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/streamingamf" class="flex.messaging.endpoints.StreamingAMFEndpoint"/>
            <properties>
                     <idle-timeout-minutes>0</idle-timeout-minutes>
                     <max-streaming-clients>10</max-streaming-clients>
                    <invalidate-session-on-disconnect>true</invalidate-session-on-disconnect>
                    <server-to-client-heartbeat-millis>5000</server-to-client-heartbeat-millis>
              </properties>
    </channel-definition>
    And here is the logging again:
    03-07-2012 09:54:04 INFO  org.springframework.flex.servlet.MessageBrokerHandlerAdapter-107 - Channel endpoint my-streaming-amf received request.
    BlazeDS :07/03/2012 09:54:04.815 [DEBUG] [Client.FlexClient] FlexClient created with id '7122F2D2-AE08-F56F-5847-5F35278C72F2'.
    03-07-2012 09:54:05 INFO  org.springframework.flex.servlet.MessageBrokerHandlerAdapter-107 - Channel endpoint my-streaming-amf received request.
    03-07-2012 09:54:06 INFO  org.springframework.flex.servlet.MessageBrokerHandlerAdapter-107 - Channel endpoint my-streaming-amf received request.
    BlazeDS :07/03/2012 09:54:06.029 [DEBUG] [Client.MessageClient] MessageClient created with clientId '7122FE3D-0B0C-D456-3DC4-10FC2244F99D' for destination 'messages-feed'.
    BlazeDS :07/03/2012 10:27:04.383 [DEBUG] [Client.MessageClient] MessageClient with clientId '7122FE3D-0B0C-D456-3DC4-10FC2244F99D' for destination 'messages-feed' has been invalidated.
    BlazeDS :07/03/2012 10:27:04.384 [DEBUG] [Client.FlexClient] FlexClient with id '7122F2D2-AE08-F56F-5847-5F35278C72F2' has been invalidated.

  • Checking for session expiration

    We're using JSPs and Servlets in our application. Looking for a way in code to check if the session has expired. We will need to do this from a jsp as well as a servlet (sometimes a jsp is pointed to by a link and sometimes a servlet). Can someone point me in the right direction?
    Thanks all.
    jl

    I like the idea of a session verifier. We have about 25 jsps, 15 servlets, and at least 80 components (beans) in the app. How would the verifier component work? How could we intagrate it with all the other existing components? Ideally it would be integrated with minimal modifications...
    Is the following what you had in mind with your suggestion to check for session data:
    HttpSession session = request.getSession();
    //or could this be used too: HttpSession session = pageContext.getSession();
    String valid = session.getAttribute( KEY );
    if ( null != valid ) {
    //then the session is still active
    jl
    >
    If the session has expired and you current have a new
    session, then use the isNew() method to check the
    session object. Or, you could check the session
    object for the data you are looking for. If it is
    missing, then the session expired and has been newly
    created. You should build into your design a session
    verifier so that you don't expierence NullPointers or
    missing data.

  • Frank session expiration sample - Does it work with a Custom JAAS Module ?

    I configured the sample as described in "Detecting and handling user session expiry" - http://thepeninsulasedge.com/frank_nimphius/2007/08/22/adf-faces-detecting-and-handling-user-session-expiry/
    I also have a custom database JAAS login module as described in http://www.oracle.com/technology/products/jdev/howtos/1013/oc4jjaas/oc4j_jaas_login_module.htm
    Thing is that when the session expires (timeout) I am redirected to the Login.jsp page of the JAAS Login Module instead of the SessionHasExpired.jspx page.
    Is there any way to say that the filter should go before the JAAS module ?
    Am I missing something ?
    Thanks,
    Claudio.

    Claudio,
    no, unfortunately not. The servlet filter is executed after the container checked for user authentication. This is less a problem for BASIC and cerificate based authentication because in both cases users are authenticated automatically (even if using custom LoginModules) by the brower or cerificate.
    Form based authentication is different because the browser doesn't re-establish the authentication and the container checks for security before the servlet is called.
    Frank

  • Maintain session when calling servlet from form in a JSP

    I have the following set up:
    index.jsp calls login servlet from the action tag in a form.
    Login servlet handles the login, stores the user info and db connection in the session and uses forward(req,res) to call another jsp.
    That jsp has a form where user enters search info and in that form's action tag there is a search servlet. In the search servlet I am unable to access the session.
    Is there any way to pass the session to the servlet from that jsp using a form/action?

    I've read elsewhere that if you go from a jsp to a servlet that the >request object is cleared of any attributes from the previous request.which is correct. But arent we speaking about session object here? A request object is valid for a request - ie the phase from where the server receieves a hit for a resource upto the point it sends the output for that request.
    A session spans multiple requests.
    it doesn't retrieve the session info and gives me a null pointer >exception when I try to use the connection object stored in the session.Bad bad bad . Why do you store Connection objects in session? Create them when necessary or use a connection pool. Do you for example clean up the connections when the session expires. What if its a 30 minute session and the user hits every say 15 minutes with a request. Why do you need to hold on to the Connection in the intervening interval when the user's session is inactive?
    gives me a null pointer exception when I try to use the connection object stored in the session.which means that the Connection object is null - not the session object.
    That last line is where I get the null pointer exception. And that is
    Statement stmt = con.createStatement();?
    Same answer as above.
    If the session object was null,
    userSession.getAttribute("connection");would have thrown a NPE.
    ram.

  • Session Expired OAS 4.0.8.1

    Hi,
    we are struggling to get the HttpSession to work. We took the example from the OAS Servlet guide (Example 4-1 Creating a JServlet session). It consistently leads to the 'Session Expired' OAS message when called more than once.
    What are we doing wrong? Is there any patch we should apply?
    Thankx, Jan

    My experience with wrksf, on Mandrake 7.0 (RH 6.1+) is that wrksf starts at first, then bails after about a second.
    I have a couple cartridges installed, C and Perl, and it starts those cartridges up and then fails. I don't get the same error message that you do, but there is an error in the wrb.log:
    `OWS-10911: Throwing exception for reason: wrkpGetProperty 2 `
    `OWS-04793: Operation oracle_OAS_System_CartridgeServerFactory_create_nwreturns exception IDL:omg.org/CORBA/UNKNOWN:1.0 `
    I'm not sure what this is all about, but it does start up my cartridges at first, because I specified a mininum number to start up initially, and a minimum number of instances.
    They just don't come back if terminated, since wrksf isn't there.
    BTW, this is the same error I encountered when, on NT, I compiled a c cartridge with Metroworks CodeWarrior instead of MS Visual C++ v6.0. So I wonder if this has something to do with compiler incompatibility, if wrksf was compiled with a different compiler from the rest of OAS. While compilers don't usually matter for C, they do for C++, and all binaries and libraries must be compiled with the same compiler/linker to work together.
    Just a stab in the dark.
    rob

  • What is session tracking in servlets?

    Hi ,
    I'm studying servlets I don't have the clear idea about session tracking and Why and where we need to use it. Can any one say about this.....
    Thanks in advance,
    Maheshwaran Devaraj

    Well Mheshpmr session tracking in servlets is very important...There are a number of problems that arise from the fact that HTTP is a "stateless" protocol. In particular, when you are doing on-line shopping, it is a real annoyance that the Web server can't easily remember previous transactions. This makes applications like shopping carts very problematic: when you add an entry to your cart, how does the server know what's already in your cart? Even if servers did retain contextual information, you'd still have problems with e-commerce. When you move from the page where you specify what you want to buy (hosted on the regular Web server) to the page that takes your credit card number and shipping address (hosted on the secure server that uses SSL), now let me tell you, how does the server remember what you were buying?
    Well There are three typical solutions to this problem.
    1. Cookies. You can use HTTP cookies to store information about a shopping session, and each subsequent connection can look up the current session and then extract information about that session from some location on the server machine. This is an excellent alternative, and is the most widely used approach. However, even though servlets have a high-level and easy-to-use interface to cookies, there are still a number of relatively tedious details that need to be handled:
    * Extracting the cookie that stores the session identifier from the other cookies (there may be many, after all),
    * Setting an appropriate expiration time for the cookie (sessions interrupted by 24 hours probably should be reset), and
    * Associating information on the server with the session identifier (there may be far too much information to actually store it in the cookie, plus sensitive data like credit card numbers should never go in cookies).
    2. URL Rewriting. You can append some extra data on the end of each URL that identifies the session, and the server can associate that session identifier with data it has stored about that session. This is also an excellent solution, and even has the advantage that it works with browsers that don't support cookies or where the user has disabled cookies. However, it has most of the same problems as cookies, namely that the server-side program has a lot of straightforward but tedious processing to do. In addition, you have to be very careful that every URL returned to the user (even via indirect means like Location fields in server redirects) has the extra information appended. And, if the user leaves the session and comes back via a bookmark or link, the session information can be lost.
    3. Hidden form fields. HTML forms have an entry that looks like the following: <INPUT TYPE="HIDDEN" NAME="session" VALUE="...">. This means that, when the form is submitted, the specified name and value are included in the GET or POST data. This can be used to store information about the session. However, it has the major disadvantage that it only works if every page is dynamically generated, since the whole point is that each session has a unique identifier.
    Servlets provide an outstanding technical solution: the HttpSession API. This is a high-level interface built on top of cookies or URL-rewriting. In fact, on many servers, they use cookies if the browser supports them, but automatically revert to URL-rewriting when cookies are unsupported or explicitly disabled. But the servlet author doesn't need to bother with many of the details, doesn't have to explicitly manipulate cookies or information appended to the URL, and is automatically given a convenient place to store data that is associated with each session.

  • Session expired, no logout page displayed

    Hi, everyone:
    I have been stuck here for a long time. I try to detect session expires and display a logout page.
    I tried in the servlet if session.get("username") == null) then forward to logout.jsp, it never reach that page
    I also tried using javascript:
    <SCRIPT LANGUAGE="JavaScript">
    var username = <%=session.getAttribute("username")%>
    if (nickname == null)
    location.href = 'logout.jsp';
    if (parent.frames.length != 0) {
    top.location.href = 'logout.jsp';
    </SCRIPT>
    I never reach the logout page, it display a login page by default. I think the session.getAttribute or value is not working because the session is already expired.
    It's such a headache, does anyone has the same problem and find the solution.
    I guess it may talke more code either in javascript to detect the session or in a servlet, but how to do it especially if the current pages are in a framesets.
    Appreciated any code!!
    ann

    1)Are the managed servers part of a Cluster? If they are not part of a cluster, then the session replication will not work.
    2)Deploy the application to cluster NOT to two managed servers
    3)Check the cookie settings - name and domain

  • Session expired (timeout) without ADF Security using.

    Hello!
    I have a problem with my application in which i use own security realization without ADF Security using. I realized custom implementation of javax.servlet.http.HttpSessionListener interface, in which i log session creation and expiration events. On WebLogic I realized customDBMS authentification class. Session timeout defined in web.xml (<session-timeout>5</session-timeout>), in weblogic.xml session timeout not define.
    Problem description: when session expired (popup warning displayed before this) and press OK button in popup with session expired warning, I see what no any log about session destroying from my HttpSessionListener implementation, so I cant understand, what session expired and process this event in my servlet filter. So I stay at same page (but without data in tables, coz binding variables in VO queries is not defined). If I am not click OK in the popup and wait about minute, then appear a log message about the destroying the session from my HttpSessionListener implementation. Why is the delay between the appearance of warning session expired and the actual destroying of the session in WebLogic?
    I use JDeveloper 11.1.1.6.0, application deployed in integrated WebLogic 10.3.5.0

    Hi,
    Why is the delay between the appearance of warning session expired and the actual destroying of the session in WebLogic?Because warning is given about 2-3 min before session expire
    That is why
    If I am not click OK in the popup and wait about minute, then appear a log message about the destroying the session from my HttpSessionListener implementation.

  • Session Expired in Visual Admin

    Dears,
    I am using netweaver 2004s on windows 2003 server with SQL server.
    Upto Some days back my visual admin was working fine but now when i am logging after loging its showing session expired.
    I have not made any changes in its properties.
    Please suggest.
    Shivam

    Hi,
    Visual Admin Logs:
    predecessor system -
    com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:178)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
         at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
         at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Authentication did not succeed.
         at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:175)
         ... 13 more
    #1.5#C000ACA8010F0001000000000166C11400045DC1F5E60370#1228987542406#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###Could not add subtree of cluster element Server 0 1_34778: java.lang.NullPointerException#
    #1.5#C000ACA8010F0001000000020166C11400045DC1F5E60370#1228987542406#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Could not add subtree of cluster element Server 0 1_34778: null#
    #1.5#C000ACA8010F00000000000001D144A400045DC24EBD3D10#1228989032890#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F00010000000001D144A400045DC24EBD3D10#1228989032890#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F00000000000001A4EB5600045DC2595BED70#1228989211031#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F000000000000014562C500045DC2611EAAE8#1228989341265#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###Could not add subtree of cluster element Server 0 1_34778: java.lang.NullPointerException#
    #1.5#C000ACA8010F000000000002014562C500045DC2611EAAE8#1228989341281#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Could not add subtree of cluster element Server 0 1_34778: null#
    #1.5#C000ACA8010F0001000000000144E85800045DC279667900#1228989748640#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F0000000000000144E85800045DC279667900#1228989748640#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F00000000000000913C5600045DC29532CA58#1228990215015#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F0000000000000179C7CF00045DC34D61E208#1228993305109#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.net.SocketException: socket closed#
    #1.5#C000ACA8010F00000000000000C3E96700045DC39B2429D8#1228994609687#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error##Plain###Could not add subtree of cluster element Server 0 1_34778: java.lang.NullPointerException#
    #1.5#C000ACA8010F00000000000200C3E96700045DC39B2429D8#1228994609687#com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread##com.sap.engine.services.adminadapter.gui.ClusterNodeRetrievingThread#######Thread[Cluster node collector thread,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Plain###Could not add subtree of cluster element Server 0 1_34778: null#
    Checked that Username and Password is correct.
    Shivam

  • Session Expired - SessionManager Problem?

    This is a OAS4.0.8.1 problem.
    Session Expired message comes when the cartridge times out and exited. However, my servlet have no means to process this exception.
    By enabling the logging, the problems seems to be from oracle.oas.session.SessionManager.resumeSession(). Can't find documentation on SessionManager object. How can I control this from my servlet or OAS admin?
    The log file shows that resumeSession() causes a SessionNotFoundException under log level 3.
    This error can be easily repeated if you access a servlet page, shutdown your servlet cartridge using admin, and refresh the servlet page.
    Please help if you know.
    THanks :)
    null

    Hi,
    OAS has a limitation of 300 seconds. This value cannot be changed. See the release notes.
    One possible way to get around this is to use the Oracle Supplied Session class and use the time feature in that.
    This a big limitation and I am not sure why Oracle designed the product this way.
    null

Maybe you are looking for

  • OBIEE - Use CURRENT_DATE in where condition

    Hello All, I want to use CURRENT_DATE in one column named "Incident Date/System"."Submit Date(GMT)". I just want to extract CURRENT_DATE(06-02-2013) data. I want to use that field like "Incident Date/System"."Submit Date(GMT)" = CURRENT_DATE. But i a

  • Can't see the podcast picture and episodes on iTunes

    Hi, My podcast feed was added to iTunes store about a week ago. It was working well for a couple of days, and now, I can't see my episodes and my podcast picture on iTunes catalogue. I was wondering what might be the problem? Here's the XML file crea

  • IPad2 with 4.3 software that won't erase & reset

    I've been trying to erase & reset my iPad2 for 3 hours with no progress. The percentage bar hasn't even started. It's just the blank spot waiting to show how much is completed. It won't let me manually turn it off or restart it. Any ideas of why or w

  • How to highlight in Reader

    Hi, I cannot seem to highlight texts in my document. I have a PC with windows 8.0 (i think). What i have been doing is hitting "comments", then "annotations" then "highlight text". However, when I try to highlight a text it never works. Please assist

  • Display one video source as two views?

    Hey all. I'm  looking for a way to have an OSMF based player playback a single video  instance but represent it in the interface as two seperate views. The  source video has composited elements in it that I need to pick out for  display independantly