JR48563: PROCESS DESIGNER THROWS EXCEPTION UPON LOGIN: JAVAX.JMS.JMSEXCEPTION: CWSIA0241E: AN EXCEPTI

Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products

APAR status

• Closed as fixed if next.

Error description

• When we logged to BPM 8.5 Process Designer; we get pop up
  message:
  ====
  javax.jms.JMSException: CWSIA0241E: An exception was received
  during the call to the method
  JmsManagedConnectionFactoryImpl.createConnection:
  com.ibm.websphere.sib.exception.SIResourceException:
  CWSIT0006E: It was not possible to contact any of the specified
  bootstrap servers. Please see the linked exception for further
  details. Bootstrap connections were attempted to:
  [localhost:7286:BootstrapSecureMessaging].
  ====
  
  This error occurs because the BPM Express configuration tries
  to set the ProviderEndpoints, but it does so in the wrong place
  when no connection factories exist yet. Therefore, no
  ProviderEndpoints will be set for BPM Express DEs and so it
  only works if the SI secure port has its default value.
  

Local fix

• Log on the admin console, go to Resources->JMS->Topic
  connection factories -> TWClientConnectionFactory, and check
  the value  of "Provider endpoints" field? The value of it
  should be something like
  "255.255.255.255:7286:BootstrapSecureMessaging", except with
  the correct IP address and port number for your installation
  instead of 255.255.255.255:7286. If this field is blank, you
  are experiencing this defect and can work around it by manually
  updating the value of this field as needed.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM BPM Express V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Process Designer throws an exception    *
  *                      when a user tries to log                *
  *                      in.                                     *
  *                      For more information, see "Connection   *
  *                      Factories are not properly              *
  *                      configured, by default, in IBM          *
  *                      Business Process Manager (BPM)          *
  *                      Express V8.5 and V8.5.0 fix pack 1      *
  *                      (8.5.0.1)"                              *
  *                      (http://www.ibm.com/support/docview.wss *
  *                      ?uid=swg21662071).                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a user logged in to IBM BPM V8.5 Process Designer, he or
  she received the following message:
  javax.jms.JMSException: CWSIA0241E: An exception was received
  during the call to the method
  JmsManagedConnectionFactoryImpl.createConnection:
  com.ibm.websphere.sib.exception.SIResourceException:
  CWSIT0006E: It was not possible to contact any of the
  specified bootstrap servers. Please see the linked exception
  for further details. Bootstrap connections were attempted to:
  [localhost:7286:BootstrapSecureMessaging].
  This error occurs because Process Center is not using the
  default SIB_ENDPOINT_SECURE_ADDRESS port, which is 7286. In
  this situation, the correct ProviderEndpoints property of the
  connection factories is not set the in stand-alone profiles;
  therefore, Process Designer is trying to contact port 7286 and
  failing.
  =================WORKAROUND=================
  Log in to the administrative console, go to Resources > JMS >
  Topic connection factories > TWClientConnectionFactory and
  correct the value in the Provider endpoints field. For
  example, enter pc.sample.com:7288:BootstrapSecureMessaging,
  where pc.sample.com is the host name of Process Center and
  7288 is the corresponding SIB_ENDPOINT_SECURE_ADDRESS port.
  

Problem conclusion

Temporary fix

Comments

• Follow the instructions in the workaround section. This
  problem will be fixed in a future release.
  

APAR Information

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

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

Fix information

Applicable component levels

• R800 PSY

     UP