SOAP Over JMS Protocol - exception : javax.jms.IllegalStateException: Session is closed javax.jms.IllegalStateException
580 views
Skip to first unread message
Maddy
May 25, 2012, 2:24:48 PM5/25/12
to LoadRunner
Hi,
I'm running 6 Webservices scripts (SOAP Over JMS) and while doing so
I'm facing issue with after running for 20 min. The issue is after 20
min in to test my scripts starts failing with below error details
Error details:
------------------
Failed to send message <soapenv:Envelope
-----------------------------------------------------------------------------------------------------------------------------------------------------------
< I removed request XML as I can not share that
info>------------------------------------------------------------------------------
</soapenv:Body></soapenv:Envelope> to {Request Queue Name} and receive
from {Response Queue Name} due to the following exception :
javax.jms.IllegalStateException: Session is closed
javax.jms.IllegalStateException: Session is closed at
com.tibco.tibjms.TibjmsxSessionImp._createProducer(TibjmsxSessionImp.java:
964) at
com.tibco.tibjms.TibjmsQueueSession.createSender(TibjmsQueueSession.java:
92) at
com.mercury.ws.jms.WorkflowManagerImpl.sendReceiveMessage(WorkflowManagerImpl.java:
417) at
com.mercury.ws.jms.JMSSupportImpl.sendReceiveMessageQueue(JMSSupportImpl.java:
78) at
com.mercury.ws.jms.JMSBridge.send_receive_message_queue(JMSBridge.java:
24)
Here are couple of things I tried before reaching out to our
LoadRunner group
--------------------------------------------------------------------------------------------------------------
1. I checked with the application team and checked at their end and
evrything looks good, except one thing that they noticed that the
Loadgenerator machine is getting disconnected & connected frequently
with the server where the Queues to which I'm posting this Messages
reside - (Single LG used)...I have given them the transaction ID to
check for failed messages and they don't see it in their logs since
the JMS call execution itself had an issue
2.Earlier I ran same kind of SOAP Over JMS scripts for but diff
component with 34 users and never had an issue with it ( However the
current component for which I'm testing is loaded with 170 users and I
sence this has to do something with the issue as I'm using Vuser as a
Process which eats up more heap memory since it has to invoke JVM on
LG's to send messages over JMS) ( Single LG used)
3. I reduced load to 80 users and it went fine with out any issue and
for this I used 2 physical LG's (will update LG capacity details
later) and checked with application team and this time connection is
maintained constantly by LG's
4.As mentioned in point-3 before reducing to 80 users I started off
with 100 users ( 2 LG's) and faced diff error for one script ||||||||||
Error Message: Failed to send message <soapenv-------------- --------
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space 24-May-2012 4:14:33 PM
{Script Name}.c(67): Error: JMS call execution failed|||||||||||| -----
This is where I sensed this might be some issue with Load generator
and reduced user count to 80 and it went fine with out any issue
5. In addition to all the above I can see that the error which I
mentioned earlier is due to "a session being used by script which is
already closed", and for SOAP JMS the connections will be taken care
by the API so we don't have any explicit control over them, so if this
reuse of closed session is causing the error then it migth be probably
due to connection being lost from LG to server
*LG- Load Generator
Please let me know your thoughts and if any one faced similar kind of
situation please let me know your suggestions
I'm running 6 Webservices scripts (SOAP Over JMS) and while doing so
I'm facing issue with after running for 20 min. The issue is after 20
min in to test my scripts starts failing with below error details
Error details:
------------------
Failed to send message <soapenv:Envelope
-----------------------------------------------------------------------------------------------------------------------------------------------------------
< I removed request XML as I can not share that
info>------------------------------------------------------------------------------
</soapenv:Body></soapenv:Envelope> to {Request Queue Name} and receive
from {Response Queue Name} due to the following exception :
javax.jms.IllegalStateException: Session is closed
javax.jms.IllegalStateException: Session is closed at
com.tibco.tibjms.TibjmsxSessionImp._createProducer(TibjmsxSessionImp.java:
964) at
com.tibco.tibjms.TibjmsQueueSession.createSender(TibjmsQueueSession.java:
92) at
com.mercury.ws.jms.WorkflowManagerImpl.sendReceiveMessage(WorkflowManagerImpl.java:
417) at
com.mercury.ws.jms.JMSSupportImpl.sendReceiveMessageQueue(JMSSupportImpl.java:
78) at
com.mercury.ws.jms.JMSBridge.send_receive_message_queue(JMSBridge.java:
24)
Here are couple of things I tried before reaching out to our
LoadRunner group
--------------------------------------------------------------------------------------------------------------
1. I checked with the application team and checked at their end and
evrything looks good, except one thing that they noticed that the
Loadgenerator machine is getting disconnected & connected frequently
with the server where the Queues to which I'm posting this Messages
reside - (Single LG used)...I have given them the transaction ID to
check for failed messages and they don't see it in their logs since
the JMS call execution itself had an issue
2.Earlier I ran same kind of SOAP Over JMS scripts for but diff
component with 34 users and never had an issue with it ( However the
current component for which I'm testing is loaded with 170 users and I
sence this has to do something with the issue as I'm using Vuser as a
Process which eats up more heap memory since it has to invoke JVM on
LG's to send messages over JMS) ( Single LG used)
3. I reduced load to 80 users and it went fine with out any issue and
for this I used 2 physical LG's (will update LG capacity details
later) and checked with application team and this time connection is
maintained constantly by LG's
4.As mentioned in point-3 before reducing to 80 users I started off
with 100 users ( 2 LG's) and faced diff error for one script ||||||||||
Error Message: Failed to send message <soapenv-------------- --------
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space 24-May-2012 4:14:33 PM
{Script Name}.c(67): Error: JMS call execution failed|||||||||||| -----
This is where I sensed this might be some issue with Load generator
and reduced user count to 80 and it went fine with out any issue
5. In addition to all the above I can see that the error which I
mentioned earlier is due to "a session being used by script which is
already closed", and for SOAP JMS the connections will be taken care
by the API so we don't have any explicit control over them, so if this
reuse of closed session is causing the error then it migth be probably
due to connection being lost from LG to server
*LG- Load Generator
Please let me know your thoughts and if any one faced similar kind of
situation please let me know your suggestions
Selvakr
May 26, 2012, 9:03:47 AM5/26/12
to LR-Loa...@googlegroups.com
Looks to me like a load distribution problem. Try to increase the number of load generators and run the service as a thread instead of process.
Maddy
May 27, 2012, 12:45:30 AM5/27/12
to LoadRunner
Thanks for reply Selvakr, I have planned this option for my next
window to run the test, other than that do you think is there any
other possible way?
window to run the test, other than that do you think is there any
other possible way?
Maddy
Jun 1, 2012, 5:41:06 PM6/1/12
to LoadRunner
do any one have any suggestions on this?...James can you help here?
> > > situation please let me know your suggestions- Hide quoted text -
>
> - Show quoted text -
>
> - Show quoted text -
Reply all
Reply to author
Forward
0 new messages