Question
NewCorp / Asurion
US
Last activity: 2 May 2016 5:15 EDT
What is the config setting/DSS that control soap over JMS time out?
What is the config setting/DSS that control soap over JMS time out?
The setting on the connector rule form doesn't work with SOAP over JMS calls.
Accepted Solution
Pegasystems Inc.
US
just examine the invokeaxis2 activity, you will see all the logic regarding JMS setup and the related classes (part of 3rd party jar praxis2JMSTransport.jar shipped OOTB). In theory, if you modify invokeaxis2 to set the SOJSpecConstants.JMS_WAIT_REPLY option in the client setup step (for 7.2 step 7), it should work.
Pegasystems Inc.
US
not aware of any DSS. Your endpoint url needs to start with "jms:". And you need to define a Data-Admin-Connect-Transport-JMS defined in the Connect-SOAP JMS Transport field.
Pegasystems Inc.
US
This appears to be matching the JMS default timeout (30 secs). Let's wait for SMEs comment if that is expected behavior or not. Another question is, where to specify JMS timeout? I saw that in the code the default value is 30 seconds.
Pegasystems Inc.
JP
Hi Kevin Zheng / SME
We have a reported instance of Connect-Soap timeout after 30 seconds [even when higher value is set in the rule], for 6.2 SP2 [A14781].
Could you kindly elaborate about the default JMS timeout 30 in the code, where you are seeing it.
Regards and Thanks,
Tarun Sipani
Pegasystems Inc.
US
I was referring to this constant:
SOJSpecConstants.DEFAULT_JMS_TIMEOUT;
which has the value of 30 secs. This is used by SOJSpecSender class. In the code, this will be overridden by the value of SOJSpecConstants.JMS_WAIT_REPLY if that is set. Otherwise, the default value will be used.
Pegasystems Inc.
JP
Hi Kevin Zheng
Thank you for the reply.
1) Could you kindly share the fully qualified [with package name] of this class you are referring to . [is it in a contained jar file?]
2) Also https://community.pega.com/support/support-articles/how-change-response-timeout-connect-soap-rule-runtime mentions about updating timeout in step 7 , would it be useful in this case.
Regards and Thanks,
Tarun
Accepted Solution
Pegasystems Inc.
US
just examine the invokeaxis2 activity, you will see all the logic regarding JMS setup and the related classes (part of 3rd party jar praxis2JMSTransport.jar shipped OOTB). In theory, if you modify invokeaxis2 to set the SOJSpecConstants.JMS_WAIT_REPLY option in the client setup step (for 7.2 step 7), it should work.
Pegasystems Inc.
JP
Hi Kevin,
Thank you for the reply.
I get the below error and multiple warnings when making the change into the invokeAxis2, could you kindly share the missing details to add this parameter and check the default timeout in 62SP2.
Regards,
Tarun
