Support #10259

[SCP ID :##5119##] : ecustody SIT_UAT - cash enquiry error

Added by Zahir Abd Latif about 5 years ago. Updated almost 5 years ago.

Status:Closed - End of life cycleStart date:September 19, 2019
Priority:NormalDue date:
Assignee:Zahir Abd Latif% Done:

100%

Category:-Spent time:-
Target version:-

Description

Hi,
Kindly attend below request:

hit error when do cas enquiry in ecustody SIT and UAT

History

#1 Updated by Najmi Pasarudin about 5 years ago

  • Status changed from New - Begin Life Cycle to Development / Work In Progress

#2 Updated by Najmi Pasarudin about 5 years ago

Current Finding:
Staging Weblogic log shows that there is missing library. Based on IBM website, already checked the default library location but both Staging and Production library location is empty. Probably JMS in Weblogic use different library location.

Solution:
Currently no solution

Log:
2019/09/19 09:10:14:304 INFO services.integration.mq.EscsMessageBrokerBean: Start EscsMessageBrokerBean send
2019/09/19 09:10:14:323 INFO services.integration.mq.EscsMessageBrokerBean: Lookup initial context
2019/09/19 09:10:14:381 INFO services.integration.mq.EscsMessageBrokerBean: Lookup connection factory ESCS.INQ.01.CF
2019/09/19 09:10:19:143 INFO services.integration.mq.EscsMessageBrokerBean: Create and start the connection
2019/09/19 09:10:19:534 ERROR services.integration.mq.EscsMessageBrokerBean: caught JMSException: com.ibm.msg.client.jms.DetailedJMSException: JMSFMQ6312: An exception occurred in the Java(tm) MQI. The Java(tm) MQI has thrown an exception describing the problem. See the linked exception for further information.
2019/09/19 09:10:19:559 ERROR services.integration.mq.EscsMessageBrokerBean: linked exception: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
2019/09/19 09:10:19:577 INFO services.integration.mq.EscsMessageBrokerBean: Response: null
2019/09/19 09:10:19:596 INFO services.integration.mq.EscsMessageBrokerBean: Finish EscsMessageBrokerBean send

#3 Updated by Najmi Pasarudin almost 5 years ago

Will be onsite at Maybank to support this issue.

#4 Updated by Najmi Pasarudin almost 5 years ago

Will be onsite again on 17/10/2019.

Finding so far:
Still have not found what cause the missing library issue. The physical file for the library exist.
Also, cannot find who and how the connection variable name is managed.

Solution suggested by Maybank middleware team:
Try to do new Weblogic installation.

#5 Updated by Najmi Pasarudin almost 5 years ago

  • % Done changed from 0 to 10

Finding on 18/10/2019:
Found note in startWeblogic.sh. Need to copy 2 library files from opt/mqm/java/lib64 to weblogic/Oracle/Middleware/wlserver_10.3/server/native/solaris/sparc64.

Suspected Staging Weblogic did something like restore or revert activity and cause Weblogic library to reset.

#6 Updated by Najmi Pasarudin almost 5 years ago

  • % Done changed from 10 to 50

Finding on 21/10/2019:
Old server: MQ version 8
New server: MQ version 7

The files copied from opt/mqm/java/lib64 need to be the correct version.

#7 Updated by Najmi Pasarudin almost 5 years ago

  • Status changed from Development / Work In Progress to Pending Customer Feedback
  • Assignee changed from Najmi Pasarudin to Zahir Abd Latif
  • % Done changed from 50 to 90

Hi Zahir,
Can email customer and close ticket. Finding details as below.

Cause:
  1. Missing MQ library files in Weblogic server directory.
  2. MQ does not work because both old and new MQ server is online.
Solution:
  1. Copy MQ library files from MQ directory to Weblogic server directory.
  2. Bring down MQ on old server. Only keep new MQ server online.

#8 Updated by Zahir Abd Latif almost 5 years ago

  • Status changed from Pending Customer Feedback to Closed - End of life cycle
  • % Done changed from 90 to 100

Issue closed in SCP.

Also available in: Atom PDF