ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Unsatisfied Linker error connecting in Binding mode

Post new topic  Reply to topic
 Unsatisfied Linker error connecting in Binding mode « View previous topic :: View next topic » 
Author Message
anujpant
PostPosted: Tue Apr 29, 2008 8:45 pm    Post subject: Unsatisfied Linker error connecting in Binding mode Reply with quote

Newbie

Joined: 29 Apr 2008
Posts: 3
I am using Windows Server 2003 SP2 Installed on C:\windows, Documentum 5.3 SP4 with JRE 1.4 D:\Program Files\Documentum and IBM MQ v6.0 90 day trial version Installed in D:\Program Files\IBM\

My environment variables are as follows
CLASSPATH
D:\Program Files\Documentum\dctm.jar;D:\Documentum\config;D:\Documentum\product\5.3\dctm-server.jar;D:\Program Files\Documentum\java\1.4.2_11\lib\tools.jar;D:\Program Files\Documentum\java\1.4.2_11\lib;D:\Program Files\IBM\WebSphere MQ\Tools\Java\base;D:\Program Files\IBM\WebSphere MQ\java\lib\com.ibm.mq.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\com.mqjms.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\connector.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\jta.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\jms.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\providerutil.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\fscontext.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\commonservices.jar;D:\Program Files\IBM\WebSphere MQ\java\lib\rmm.jar;D:\Program Files\IBM\WebSphere MQ\Java\lib;

DM_HOME
D:\Documentum\product\5.3

DOCUMENTUM
D:\Documentum

JAVA_HOME
D:\Program Files\Documentum\java\1.4.2_11;

Lib
D:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\;

MQ_ JAVA _DATA_PATH
D:\Program Files\IBM\WebSphere MQ

MQ_JAVA_INSTALL_PATH
D:\Program Files\IBM\WebSphere MQ\Java

MQ_JAVA_LIB_PATH
D:\Program Files\IBM\WebSphere MQ\Java\lib

PATH
D:\Program Files\Documentum\Shared;D:\Documentum\product\5.3\bin;D:\Documentum\fulltext\fast40;C:\Program Files\Java\j2re1.4.2_06\bin;D:\Program Files\Documentum\java\1.4.2_11\bin;D:\Program Files\Documentum\java\1.4.2_11\jre\bin;D:\oracle\product\10.2.0\db_1\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;D:\Documentum\product\5.3\fusion;D:\Program Files\IBM\WebSphere MQ\Java\lib;D:\Program Files\IBM\WebSphere MQ\bin;

PATHEXT
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.DLL
(I added a DLL to this pathext)

All the sample programs including MQIVP sample run fine.

I wrote a simple code to open and put a message in Queue which ran fine from both command line and eclipse (after including com.ibm.mq.jar and other lib in the build path)

However, in DOCUMENTUM, in a simple component that I have coded, when I try to open a queue manager or do any other MQ specific operation, I get the following error

invokeMethod() failed while calling: FireMLI
no mqjbnd05 in java.library.path : no mqjbnd05 in java.library.path
no mqjbnd05 in java.library.path
Stack Trace:
java.lang.UnsatisfiedLinkError: no mqjbnd05 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1517)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at com.ibm.mq.MQSESSION.loadLib(MQSESSION.java:872)
at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:228)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:222)
at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:70)
at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:492)
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:168)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnection(MQBindingsManagedConnectionFactoryJ11.java:179)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnection(MQBindingsManagedConnectionFactoryJ11.java:215)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:84)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:168)
at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:772)
at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:697)
at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:657)
at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:153)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:451)
at com.citibank.northstar.components.testmq.testmq.FireMLI(testmq.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.documentum.web.form.FormProcessor.invokeMethod(FormProcessor.java:1442)
at com.documentum.web.form.FormProcessor.fireActionEvent(FormProcessor.java:1151)
at com.documentum.web.form.RecallOperation.execute(RecallOperation.java:101)
at com.documentum.web.form.FormProcessor.processAction(FormProcessor.java:111)
at com.documentum.web.form.FormAction.processAction(FormAction.java:86)
at com.documentum.web.env.WDKController.doStartRequest(WDKController.java:190)
at com.documentum.web.env.WDKController.processRequest(WDKController.java:91)
at com.documentum.web.env.WDKController.doFilter(WDKController.java:82)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)

I have tried copying all the files including the dll files in the WEB_INF\lib folder.

The code for the java class of the component is below.
import java.io.IOException;
import java.util.ArrayList;

import com.documentum.web.common.ArgumentList;
import com.documentum.web.form.Control;
import com.documentum.web.form.control.Text;
import com.documentum.web.formext.component.Component;
import com.ibm.mq.MQException;
import com.ibm.mq.MQMessage;
import com.ibm.mq.MQQueueManager;
import com.citibank.northstar.util.*;

public class testmq extends Component
{
private static final long serialVersionUID = 1L;
public MQMessage putMsg;

public MQMessage getMsg;
private MQQueueManager qMgr;

public void FireMLI(Control ctrl, ArgumentList arg)
{
String strQManager="SGTEST";
try {
qMgr = new MQQueueManager(strQManager);
} catch (MQException e) {}

}

}

I can not use client connection. We HAVE to use bindings mode. Also the binding connection works correctly when called from a simple java program.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Apr 30, 2008 6:45 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
You can only connect in bindings mode to a qmgr residing on the same box. Otherwise you need to run the etc client, not the normal client (enables XA same cost as server license).

Obviously you are running in an appserver (apache, tomcat) and possibly in a J2EE container... if that is the case why are you using java base and not JMS?

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed Apr 30, 2008 7:17 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
fjb_saper wrote:
You can only connect in bindings mode to a qmgr residing on the same box.


That clearly has nothing to do with the error message, which is discussing a problem with java.library.path.

http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj10340_.htm
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Apr 30, 2008 8:27 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
I learn everyday... I would have thought of setting LIBPATH for this.... I guess using the java.library.path allows you to mix the 64 bit OS commands with a 32 bit java setup...

Thanks
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed Apr 30, 2008 8:48 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981
LIBPATH goes into java.library.path... as far as I know.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
anujpant
PostPosted: Thu May 01, 2008 7:02 pm    Post subject: Reply with quote

Newbie

Joined: 29 Apr 2008
Posts: 3
I am using Tomcat 5.28

Can you please tell me how to add the path to the server.

The funny thing is, when i uninstall Webtop and do a print og System.getProperty("java.library.path") is shows me to total classpath and the code to open the queue manager also runs fine.

However the moment i install Webtop, the classpath only shows \Program Files\Documentum\Shared and the code stops working from both simple jsp file and webtop components.

Thanks for your help
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Unsatisfied Linker error connecting in Binding mode
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.