Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Timeout error message

 4 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
mark.cook
Veteran Member
Posts: 444
Veteran Member
12/14/2009 1:30 PM

    We are getting one timeout message that I wanted to see if anyone has seen before. We have LBI running within the portal window and when a user is idle in Lawson and times out the following message appears.

    Invalid XML string:

    Reason a semicolon is expected.

    Source:  urlArr[0] =http://LBIserver:9080/sso/SSOServlet? _action=timeout&relyingURI=http://appserve:80/sso/SSOServlet;

    Line :30 Line position 114 File position 1330

    SSOObjectFactory.getDomFromString() - sso.js

    Any ideas where I should be looking to resolve.

     

     

    fran
    New Member
    Posts: 2
    New Member
    12/14/2009 4:31 PM
      I know this is something totally different but do you know where I can go in lawson to set up a reason code to do a write off for AR? AR 15.1 CAN NOT DO IT
      Jimmy Chiu
      Veteran Member
      Posts: 641
      Veteran Member
      12/14/2009 4:55 PM
        You would want to set the LBI timeout value greater than your portal timeout value. This prevent user seeing LBI timeout while they are in lawson portal. I am assuming you are using DSSO/EFS for portal integration.

        goto your EFS install directory\whatever.ear\efs-war-x.x.x.xwar\WEB-INF

        open up the WEB.XML

        do a find on SESSION-CONFIG

        under that, you should see SESSIOn-TIMEOUT, increase the value as you see fit (it's minutes) set it to 180 for example for 3 hours.
        mark.cook
        Veteran Member
        Posts: 444
        Veteran Member
        12/16/2009 6:03 PM
          Thanks Jimmy,

          We made the change this morning and so far everyone just gets the normal log on screen and no error message. Just what we were looking for!
          ram32bo
          Basic Member
          Posts: 10
          Basic Member
          12/16/2009 7:34 PM

            Once this change was made, do we have to reboot the server for this to take place?