Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
2696 views

SOAP Failure - Max Sessions Exceeded.

Hello.

 

Did any one exprerienced this kinds of problems ?

 

ERROR TP-Processor1124 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:10 CET [ERROR] SOAP Failure - Max Sessions Exceeded.
ERROR TP-Processor1124 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:10 CET [ERROR] SOAP Failure - Max Sessions Exceeded.

 
Users are kicked of - sessions time out.
 
Please advise.
WD
0 Likes
13 Replies
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

ERROR TP-Processor1118 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:40 CET [ERROR] SOAP Failure - Max Sessions Exceeded.
ERROR TP-Processor1118 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:40 CET [ERROR] SOAP Failure - Max Sessions Exceeded.
ERROR TP-Processor1118 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:40 CET [ERROR] request:
<stop />
ERROR TP-Processor1118 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:40 CET [ERROR] request:
<stop />
ERROR TP-Processor1118 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:40 CET [ERROR] response:
<Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>Max Sessions Exceeded.</faultstring>
 <faultactor>Server</faultactor>
</Fault>
ERROR TP-Processor1118 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 09:00:40 CET [ERROR] response:
<Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>Max Sessions Exceeded.</faultstring>
 <faultactor>Server</faultactor>
</Fault>

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

I found the similar issue here:

 

http://community.hpe.com/t5/HPE-Service-Manager-Service/MAX-SESSIONS-EXCEEDED/td-p/5277367

 

 

We have

threadsperprocess:80 in sm.ini.
 
Curently we have 1000 float and 300 Named licenses.
 
Our infrastructure is
- web layer : 3 apache - 8 tomcats
- application layer is 6 servlets.
 
Is 6 servlets to small for it ?
Should we extend the infrastructure or this paramater
threadsperprocess:80
 
?
 
please advice
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: SOAP Failure - Max Sessions Exceeded.

Is this for a single user or for everyone who logs in thru web?

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

ERROR Timer-6228 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 12:41:23 CET [ERROR] response:
<Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>Session no longer valid</faultstring>
 <faultactor>Server</faultactor>
</Fault>
ERROR Timer-6228 com.hp.ov.sm.client.webtier.SCLogging - Feb 09, 2016 12:41:23 CET [ERROR] response:
<Fault>
 <faultcode>SOAP-ENV:Server</faultcode>
 <faultstring>Session no longer valid</faultstring>
 <faultactor>Server</faultactor>

also this error appears .

Please help/advise.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

it's happening randomly.

50/50

Some of the works withour a problem - some of the are often kicked out during work with tickets.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SOAP Failure - Max Sessions Exceeded.

If you have 6 servlets with threadsperprocess:80 you can support 480 sessions ( 6 * 80 ).

You need many more servlets to support the number of sessions you are licensed for.

The threadsperprocess:80 is on the high side so I would not recommend increasing that value.  Typical values are in the 30-60 range.

Steve Hirschfeld

HPE Support

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

Thank you very much for your answer.

Daily we have about 700 sessions opened.

We are planning to add 4 more servlets (application layer), than more in the next future.

 

We have 3 apaches and 8 tomcats (web layer). Should we also extend it ?

Is it possible to make 2 loadbalancers (application layer) Curently we have 1 loadbalancer and 6 servlets. ?

 

thx.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SOAP Failure - Max Sessions Exceeded.

Number of Tomcats is fine.

It is not possible to have 700 concurrent sessions on the configuration you described. The math does not work.

It is possible to have multiple load balancers but in general does not provide any capacity benefit.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

Sorry, my information is wrong. I told wrong servlet/server/port naming.

We have 6 servers with 4 servlets per each.

server 1 = > with port 13081 13082 13083 13084

server 2= > with port 13081 13082 13083 13084

server 3= > with port 13081 13082 13083 13084

server 4= > with port 13081 13082 13083 13084

server 5 = > with port 13081 13082 13083 13084

server 6 = > with port 13081 13082 13083 13084

 

each port has threadsperprocess:30

 

So it seems we have 120 sessions per server (4 servlets) ?

And still have those errors

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: SOAP Failure - Max Sessions Exceeded.

ERROR Timer-7934 com.hp.ov.sm.client.webtier.SCLogging - Feb 11, 2016 11:25:31 CET [ERROR] The exception is :
Feb 11, 2016 11:25:31 CET [ERROR] invalidate: Session already invalidated
java.lang.IllegalStateException: invalidate: Session already invalidated
        at org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1139)
        at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:150)
        at com.hp.ov.sm.client.webtier.WebClient.notifySoapFailure(WebClient.java:389)
        at com.hp.ov.sm.client.common.soap.BaseSoapClient.handleCriticalFault(BaseSoapClient.java:344)
        at com.hp.ov.sm.client.common.soap.BaseSoapClient.internalDoSoapTransact(BaseSoapClient.java:312)
        at com.hp.ov.sm.client.common.communications.SOAPClient.internalDoSoapTransact(SOAPClient.java:1086)
        at com.hp.ov.sm.client.common.soap.SoapReq.run(SoapReq.java:263)
        at com.hp.ov.sm.client.common.soap.BaseSoapClient.syncExecInCurrentThread(BaseSoapClient.java:401)
        at com.hp.ov.sm.client.common.soap.BaseSoapClient.doSyncRequest(BaseSoapClient.java:421)
        at com.hp.ov.sm.client.common.soap.SoapReq.syncExec(SoapReq.java:113)
        at com.hp.ov.sm.client.common.communications.SOAPClient.doRequest(SOAPClient.java:1065)
        at com.hp.ov.sm.client.common.communications.SOAPClient.getMessages(SOAPClient.java:1307)
        at com.hp.ov.sm.client.common.communications.HeartBeat$HeartBeatTask.run(HeartBeat.java:51)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)

and additionally today TOMCAT errors...

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SOAP Failure - Max Sessions Exceeded.

With three apache webservers load balancing eight tomcats do you have a hardware load balancer fronting the three apache webservers?

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.