httpclient.LHCInvalidSessionException: Invalid session

 7 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
TimC
Veteran Member Send Private Message
Posts: 84
Veteran Member

MISSION CRITICAL!!

We have an InvoiceApproval flow with a Lawson S# query that was running successfully. Now, without any changes to the environment, it's now failing with the following error:

S3 query com.lawson.security.authen.httpclient.LHCInvalidSessionException: Invalid session

 

HELP!

Infor is taking their sweet time.

 

TimC
Veteran Member Send Private Message
Posts: 84
Veteran Member
Has anyone came across this error?
S3 query com.lawson.security.authen.httpclient.LHCInvalidSessionException: Invalid session
JimY
Veteran Member Send Private Message
Posts: 510
Veteran Member
Have you opened a ticket with Infor Support? The only thing I can think of is that a password changed or some additional security was put in place. We have had problems in the past when our security team started locking things down with McAfee.
TimC
Veteran Member Send Private Message
Posts: 84
Veteran Member
Odd thing is it runs "sometime"... We restarted the Grid and ran all the backed up workunits and it ran successfully.
Then this morning, there were 198 EDI invoice records to be processed. An Invoice Approval flow execs for each row read. The MaxConnectionPool is set at 10. We monitored the grid in TEST and the pool felt no stress.
TimC
Veteran Member Send Private Message
Posts: 84
Veteran Member
Yes, we did open a ticket w Infor. They thought it was the MaxConnectionPool size. That didn't fix it. I would have thought that an error message may have indicated the pool rather than the authSession.

S3 query com.lawson.security.authen.httpclient.LHCInvalidSessionException: Invalid session
John Henley
Send Private Message
Posts: 3351
Is this v9 ProcessFlow or v10 IPA?
Thanks for using the LawsonGuru.com forums!
John
TimC
Veteran Member Send Private Message
Posts: 84
Veteran Member
v10 IPA
TimC
Veteran Member Send Private Message
Posts: 84
Veteran Member
SOLVED:
Many of the parameters like ConnectionPooling weren't copied over from test. Once those were done, problem solved.