| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with IBM trigger monitor and jdk 1.6 |
View previous topic :: View next topic |
| Author |
Message
|
| RB |
 Posted: Thu May 07, 2009 1:12 pm Post subject: Problem with IBM trigger monitor and jdk 1.6 |
 |
|
Acolyte
Joined: 23 May 2006
Posts: 56
|
We are using IBM trigger monitor in our project for checking the availability of messages in a queue. Whenever there is a message coming in the queue, we invoke a java program which reads the message off the queue and does some business processing.
This configuration was working fine with java 1.5.X. But the same configuration is giving an exception with java 1.6.0.3. The error message is “/usr/lib/hpux32/dld.so: Unable to find library 'libjli.so”.
We could find the specified library under "jre/lib/IA64N/jli/libjli.so" and "jre/lib/IA64W/jli/libjli.so". And an attempt to add this file manually to the library variable also resulted in the same exception. Do we need any specific patch (MQ or JDK) in this case?
I would appreciate if any of you can provide me some inputs on this! We are using MQ 6.0.2.5 and the operating system is HP – Unix B.11.23.
Regards,
RB |
|
| Back to top |
|
 |
| vol |
| Posted: Thu May 07, 2009 9:29 pm Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009
Posts: 69
|
| Quote: |
| This configuration was working fine with java 1.5.X. But the same configuration is giving an exception with java 1.6.0.3. |
looks like the error is in the java upgrade.
the trigger monitor i a setuid app, and when such an app execs a new shell, the LIBPATH is set to the standard libs. probably the library is new in java 1.6, and is not in any of the standard lib dirs.
as for the solution..
link the library which cannot be found to a dir which can be found |
|
| Back to top |
|
|
| RB |
| Posted: Thu Jun 25, 2009 9:45 am Post subject: |
|
|
Acolyte
Joined: 23 May 2006
Posts: 56
|
We have changed the file permissions of runmqtmc in /opt/mqm/bin to 775 and now it is working fine! Though the doesnt look logical, moving from 1.5 to 1.6 needs a different access permission, this seems to be working. Just updating the thread to keep the solution so that it might be useful to someone...
Regards,
RB |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 25, 2009 9:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| RB wrote: |
| Just updating the thread to keep the solution so that it might be useful to someone... |
And we thank you for it! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vol |
| Posted: Thu Jun 25, 2009 11:02 pm Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009
Posts: 69
|
| Quote: |
runmqtmc in /opt/mqm/bin to 775 |
That is the solution, although it can of course cause other problems later if the apps being triggered do not have sufficient authority to access WMQ objects.
The cause of the problem is that SUID apps reset the LIBPATH to only the standard dirs, i.e. /lib /usr/lib, so if new apps are started they might not find dependent libs if they are in non-standard locations. This is a UNIX security feature. |
|
| 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
|
|
|
|
