| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Symbol resolution failed warning - |
« View previous topic :: View next topic » |
| Author |
Message
|
| nukalas2010 |
 Posted: Sun Jul 12, 2020 3:35 am Post subject: Symbol resolution failed warning - |
 |
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
Dears,
Recently we upgraded IIB from 10.0.0.11 to 10.0.0.18 in AIX environment. everything went fine and services are also working normally.
But we observed the below error in broker logs for any activity like start of Integration node or reload of EG causing these warnings..
| Quote: |
user:err|error IIB[4981146]: IBM Integration Bus v100011 (NODEXXX1.EG1) [Thread 1] (Msg 1/1) BIP2308E: File '/opt/IBM/mqsi/iib
-10.0.0.18/server/SecurityProviders/wstrustSecurityProvider.lsl' could not be loaded; operating system return code 'Symbol resolution failed for /opt
/IBM/mqsi/iib-10.0.0.18/server/SecurityProviders/wstrustSecurityProvider.lsl because: Symbol __ct__19ImbExceptionDetailsFPC12ImbLogSourcePCciT2RC10
ImbWstringN23 (number 104) is not exported from dependent module /opt/IBM/mqsi/iib-10.0.0.11/server/lib/libCommonServices.a[libCommonServices
.a.so]. Symbol __ct__25ImbConfigurationExceptionFRC19ImbExceptionDetailsQ3_6ImbLog4Item4Type (number 112) is not exported from dependent
module /opt/IBM/mqsi/iib-10.0.0.11/server/lib/libCommonServices.a[libCommonServices.a.so]. Symbol __ct__20ImbSecurityExceptionFRC19ImbEx
ceptionDetailsQ3_6ImbLog4Item4Type (number 115) is not exported from dependent module /opt/IBM/mqsi/iib-10.0.0.11/server/lib/libCommonServices.a[l
ibCommonServices.a.so]. |
Can anyone have come through this error anytime.. please throw some light on this.
Thanks, |
|
| Back to top |
|
 |
| abhi_thri |
| Posted: Mon Jul 13, 2020 12:57 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi...
| Quote: |
| IBM Integration Bus v100011 (NODEXXX1.EG1) |
| Quote: |
| /opt/IBM/mqsi/iib-10.0.0.11/server/lib/libCommonServices.a |
why is the integration node process still showing as fixpack 11 instead of 18, also it is still trying to access fixpack11 files...can you please crosscheck whether the service and the node indeed got upgraded completely to fixpack 18,
'mqsiservice -v' and 'mqsiservice <nodename>' should help |
|
| Back to top |
|
|
| nukalas2010 |
| Posted: Mon Jul 13, 2020 6:22 am Post subject: |
|
|
Master
Joined: 04 Oct 2010
Posts: 220
Location: Somewhere in the World....
|
Yeah.. version details matching with 10.0.0.18
also mqsireportbroker returns path of 10.0.0.18
Opened PMR, will wait for the feedback. |
|
| Back to top |
|
|
| cbruemmer |
| Posted: Wed Nov 25, 2020 2:26 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2017
Posts: 8
|
Hello nukalas2010,
did you got any feedback? I have a similar problem. After upgrading from 10.0.0.13 to 10.0.0.22 I can see, IIB is trying to do somehting with the old installation.
IBM Integration Bus v100022 (IN.IS) [Thread 18687] (Msg 1/1) BIP2308E: File '/opt/mqsi/iib-10.0.0.13/server/SecurityProviders/ldapSecurityProvider.lsl' could not be loaded; operating system return code '/opt/mqsi/iib-10.0.0.13/server/SecurityProviders/ldapSecurityProvider.lsl: undefined symbol: _ZN12ImbJniReturn25processRootKnownExceptionER23ImbRecoverableException'.
I did a
mqsichangebroker IN -f all
because I thought, it might be related to the enabled version, but it wasn't.
When I check the environment, it says:
MQSI_SECURITY_PROVIDER_PATH=/opt/mqsi/iib-10.0.0.22/server/SecurityProviders
The IN is configured as MQ-Service. Might it be, because I havent't rebooted MQ after the upgrade? I only used mqsistop and mqsistart after the upgrade. MQ has configured iib-current, which is symbolic link to the fixpack we want to use.
Thanks
Christian |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Feb 09, 2021 12:18 pm Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
Hi,
Did anyone of you get a fix for the "undefined symbol: _ZN17ImbFatalExceptionC1ERK19ImbExceptionDetailsN6ImbLog4Item4TypeE'"
I was applying fixpack 10.0.0.22 and teh version before fixpack was 10.0.0.15.
Thanks
Ganesh |
|
| Back to top |
|
|
| ganesh |
| Posted: Thu Feb 18, 2021 11:13 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
The issue was resolved, it had to do with the older fixpack libraries been loaded.
We have IIB as MQ service and even after undefining, applying fixpack to node and defining the node back using mqsichangebroker command the older libraries were loaded by MQ upon restart.
The solution was install fixpack, undefine, applyfixpack to node, define, leave the nodes stopped, log out of session.
logbackin as mqm, stop queue managers, start queue managers which will also start the IIB nodes.
Check the logs and you shouldn't see those errors again.
Hope this helps. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
