IC99924: NEED RRCONTAINER FOR JMS 1.1 REQUEST REPLY SERVICE TO BE PERSISTED IN INSTANCE DATA.

si_52_build_5020500_hotfix_7

APAR status

• Closed as program error.

Error description

• Each business process (BP) using the JMS 1.1 Request Reply
  service differs in its configuration, such as how
  QUEUEs,MESSAGE_SELECTOR creates
  one container that must be deleted manually using the JMX
  console or JMS 1.1 Release Connection service (with SHUTDOWN_RR
  option). But locating the RRcontainer that corresponds to
  a BP is challenging as it is generated with a random number
  (for example, Q2_tcp://n.n.n.n.n:2506_1_11_147740634). We
  couldn't release those containers with this recommended approach
  and eventually the production system started running out of
  resources.
  

Local fix

• Workaround:
  Close the RR containers from the JMX console.
  

Problem summary

• USERS AFFECTED:
  All JMS 1.1 Request Reply service users who also use non-JNDI
  mode transfers.
  
  PROBLEM DESCRIPTION:
  Steady memory growth was occuring due to many
  RR containers being generated as part of running the JMS 1.1
  Request Reply service.
  
  The customer wants to release RR_Container inline
  in the same BP. As there is no persistent value in Request Reply
  Service (RR) in the workflow, they are unable to do this.
  
  PLATFORMS AFFECTED:
  All
  

Problem conclusion

• RESOLUTION SUMMARY:
  A new API has been added which allows the
  "containerValue" in the wfc to persist. To use this, add
  "NeedRRValuePersistence" as part of the JMS connection
  operation.
  
  Make these BP assign statements as part of
  <operation name="JMS1.1 Request Reply Service">:
  
  <assign to="NeedRRValuePersistence">Yes</assign>
  
  On the <operation name="JMS 1.1 Release Connection and
  Session Service"> add:
  
  <assign to="RR_LIST" from="listenerContainer/text()"></assign>
   <assign to="RELEASE_ACTION">SHUTDOWN_RR</assign>
  
  This allows the BP to clear the container value as part of
  the BP execution.
  
  DELIVERED IN:
  5020500_7
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels

• R525 PSY

     UP