| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue while using MQ MFT Stand-alone database logger |
« View previous topic :: View next topic » |
| Author |
Message
|
| bkiran2020 |
 Posted: Fri Sep 06, 2013 7:42 am Post subject: Issue while using MQ MFT Stand-alone database logger |
 |
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
Hi Guys,
I'm new to MQ MFT.
I'm able to successfully create stand-alone logger using the fteCreateLogger command. But when I'm trying to start the logger using fteStartLogger I'm getting the below error.
| Code: |
--======================================================================================================
Build level: V7.5.0.2 f750-FP-20130619-1001
Java runtime version:
JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr13fp2-20130423_146146 (JIT enabled, AOT enabled)
J9VM - 20130423_146146
JIT - r9_20130108_31100ifx1
GC - 20121212_AA
The maximum amount of memory that the Java virtual machine will attempt to use is: '1639'MB
ICU4J version: 49.1.0.0
Properties:
coordinationQMgr=MFT_TEST_QM, coordinationQMgrChannel=SYSTEM.DEF.SVRCONN
coordinationQMgrHost=172.17.3.249, coordinationQMgrPort=8989, defaultProperties=MFT_TEST_QM
wmqfte.database.driver=C:\IBM\SQLLIB\java\db2jcc4.jar, wmqfte.database.name=DSNV
wmqfte.database.type=DB2, wmqfte.logger.name=SAMPLEDBLOGGER1, wmqfte.logger.type=DATABASE
wmqfte.queue.manager=MFT_TEST_QM
Install Locations:
com.ibm.wmqfte.product.root=C:\IBM\WebSphere_MQ\mqft
com.ibm.wmqfte.product.config=C:\IBM\WebSphere_MQ\mqft\config
WebSphere MQ Components:
Java Message Service Client / 7.5.0.2 / p750-002-130627
WebSphere MQ classes for Java Message Service / 7.5.0.2 / p750-002-130627
IBM WebSphere MQ JMS Provider / 7.5.0.2 / p750-002-130627
Common Services for Java Platform, Standard Edition / 7.5.0.2 / p750-002-130627
************* End Display Current Environment *************
[06/09/2013 09:11:47:031 CDT] 00000001 Logger I BFGDB0051I: The logger is running as a 32-bit process.
[06/09/2013 09:11:48:723 CDT] 00000001 StdOut I com.ibm.db2.jcc.am.SqlException: [jcc][10389][12245][4.11.77] Failure in loading native library db2jcct2, java.lang.UnsatisfiedLinkError: db2jcct2 (Not found in java.library.path): ERRORCODE=-4472, SQLSTATE=null
[06/09/2013 09:11:48:725 CDT] 00000001 StdOut I at com.ibm.db2.jcc.am.gd.a(gd.java:660)
[06/09/2013 09:11:48:725 CDT] 00000001 StdOut I at com.ibm.db2.jcc.am.gd.a(gd.java:60)
[06/09/2013 09:11:48:725 CDT] 00000001 StdOut I at com.ibm.db2.jcc.am.gd.a(gd.java:94)
[06/09/2013 09:11:48:725 CDT] 00000001 StdOut I at com.ibm.db2.jcc.t2.a.a(a.java:37)
[06/09/2013 09:11:48:726 CDT] 00000001 StdOut I at com.ibm.db2.jcc.t2.T2Configuration.<clinit>(T2Configuration.java:95)
[06/09/2013 09:11:48:726 CDT] 00000001 StdOut I at java.lang.J9VMInternals.initializeImpl(Native Method)
[06/09/2013 09:11:48:726 CDT] 00000001 StdOut I at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
[06/09/2013 09:11:48:726 CDT] 00000001 StdOut I at com.ibm.db2.jcc.DB2BaseDataSource.instantiateLogWriter(DB2BaseDataSource.java:10434)
[06/09/2013 09:11:48:727 CDT] 00000001 StdOut I at com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriterForNewConnection(DB2BaseDataSource.java:10355)
[06/09/2013 09:11:48:727 CDT] 00000001 StdOut I at com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriterForNewConnection(DB2BaseDataSource.java:10311)
[06/09/2013 09:11:48:727 CDT] 00000001 StdOut I at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:205)
[06/09/2013 09:11:48:727 CDT] 00000001 StdOut I at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[06/09/2013 09:11:48:728 CDT] 00000001 StdOut I at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
[06/09/2013 09:11:48:728 CDT] 00000001 StdOut I at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[06/09/2013 09:11:48:728 CDT] 00000001 StdOut I at java.lang.reflect.Method.invoke(Method.java:600)
[06/09/2013 09:11:48:728 CDT] 00000001 StdOut I at com.ibm.wmqfte.databaselogger.DB2DataStore1PC.prepareConnection(DB2DataStore1PC.java:125)
[06/09/2013 09:11:48:729 CDT] 00000001 StdOut I at com.ibm.wmqfte.databaselogger.DB2DataStore1PC.<init>(DB2DataStore1PC.java:53)
[06/09/2013 09:11:48:729 CDT] 00000001 StdOut I at com.ibm.wmqfte.databaselogger.DataStoreFactory.newInstance(DataStoreFactory.java:95)
[06/09/2013 09:11:48:729 CDT] 00000001 StdOut I at com.ibm.wmqfte.databaselogger.Logger.doRetryLoop(Logger.java:286)
[06/09/2013 09:11:48:729 CDT] 00000001 StdOut I at com.ibm.wmqfte.databaselogger.Logger.main(Logger.java:218)
[06/09/2013 09:11:48:730 CDT] 00000001 StdOut I at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[06/09/2013 09:11:48:730 CDT] 00000001 StdOut I at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
[06/09/2013 09:11:48:730 CDT] 00000001 StdOut I at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[06/09/2013 09:11:48:730 CDT] 00000001 StdOut I at java.lang.reflect.Method.invoke(Method.java:600)
[06/09/2013 09:11:48:731 CDT] 00000001 StdOut I at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.run(BootstrapMain.java:290)
[06/09/2013 09:11:48:731 CDT] 00000001 StdOut I at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.main(BootstrapMain.java:131)
[06/09/2013 09:11:48:731 CDT] 00000001 StdErr E com.ibm.db2.jcc.am.SqlException: [jcc][10389][12245][4.11.77] Failure in loading native library db2jcct2, java.lang.UnsatisfiedLinkError: db2jcct2 (Not found in java.library.path): ERRORCODE=-4472, SQLSTATE=null
[06/09/2013 09:11:48:732 CDT] 00000001 StdErr E at com.ibm.db2.jcc.am.gd.a(gd.java:660)
[06/09/2013 09:11:48:732 CDT] 00000001 StdErr E at com.ibm.db2.jcc.am.gd.a(gd.java:60)
[06/09/2013 09:11:48:732 CDT] 00000001 StdErr E at com.ibm.db2.jcc.am.gd.a(gd.java:94)
[06/09/2013 09:11:48:732 CDT] 00000001 StdErr E at com.ibm.db2.jcc.t2.a.a(a.java:37)
[06/09/2013 09:11:48:732 CDT] 00000001 StdErr E at com.ibm.db2.jcc.t2.T2Configuration.<clinit>(T2Configuration.java:95)
[06/09/2013 09:11:48:733 CDT] 00000001 StdErr E at java.lang.J9VMInternals.initializeImpl(Native Method)
[06/09/2013 09:11:48:733 CDT] 00000001 StdErr E at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
[06/09/2013 09:11:48:733 CDT] 00000001 StdErr E at com.ibm.db2.jcc.DB2BaseDataSource.instantiateLogWriter(DB2BaseDataSource.java:10434)
[06/09/2013 09:11:48:734 CDT] 00000001 StdErr E at com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriterForNewConnection(DB2BaseDataSource.java:10355)
[06/09/2013 09:11:48:734 CDT] 00000001 StdErr E at com.ibm.db2.jcc.DB2BaseDataSource.computeJccLogWriterForNewConnection(DB2BaseDataSource.java:10311)
[06/09/2013 09:11:48:734 CDT] 00000001 StdErr E at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:205)
[06/09/2013 09:11:48:734 CDT] 00000001 StdErr E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[06/09/2013 09:11:48:735 CDT] 00000001 StdErr E at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
[06/09/2013 09:11:48:735 CDT] 00000001 StdErr E at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[06/09/2013 09:11:48:735 CDT] 00000001 StdErr E at java.lang.reflect.Method.invoke(Method.java:600)
[06/09/2013 09:11:48:735 CDT] 00000001 StdErr E at com.ibm.wmqfte.databaselogger.DB2DataStore1PC.prepareConnection(DB2DataStore1PC.java:125)
[06/09/2013 09:11:48:736 CDT] 00000001 StdErr E at com.ibm.wmqfte.databaselogger.DB2DataStore1PC.<init>(DB2DataStore1PC.java:53)
[06/09/2013 09:11:48:736 CDT] 00000001 StdErr E at com.ibm.wmqfte.databaselogger.DataStoreFactory.newInstance(DataStoreFactory.java:95)
[06/09/2013 09:11:48:736 CDT] 00000001 StdErr E at com.ibm.wmqfte.databaselogger.Logger.doRetryLoop(Logger.java:286)
[06/09/2013 09:11:48:736 CDT] 00000001 StdErr E at com.ibm.wmqfte.databaselogger.Logger.main(Logger.java:218)
[06/09/2013 09:11:48:736 CDT] 00000001 StdErr E at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[06/09/2013 09:11:48:737 CDT] 00000001 StdErr E at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
[06/09/2013 09:11:48:737 CDT] 00000001 StdErr E at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[06/09/2013 09:11:48:737 CDT] 00000001 StdErr E at java.lang.reflect.Method.invoke(Method.java:600)
[06/09/2013 09:11:48:737 CDT] 00000001 StdErr E at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.run(BootstrapMain.java:290)
[06/09/2013 09:11:48:738 CDT] 00000001 StdErr E at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.main(BootstrapMain.java:131)
[06/09/2013 09:11:48:741 CDT] 00000001 Logger E BFGDB0003E: A problem occurred with the database. The database driver reported the following details: SQL State [null], Error Code [-4472], Message [[jcc][10389][12245][4.11.77] Failure in loading native library db2jcct2, java.lang.UnsatisfiedLinkError: db2jcct2 (Not found in java.library.path): ERRORCODE=-4472, SQLSTATE=null]
[06/09/2013 09:11:48:741 CDT] 00000001 Logger E BFGDB0005E: A serious error has occurred, and the logger will stop. Messages in progress will be rolled back to the queue manager. See the preceding log entry for details.
[06/09/2013 09:11:48:744 CDT] 00000001 Logger E BFGDB0073E: The logger has ended abnormally with return code 70.
--====================================================================================================== |
From the error I could clearly understand that "The application environment is not configured correctly for loading the DB2 native library"
The Java runtime I'm having is 32-bit and it is trying to connect to a 64bit DB2 client I have.
I'm using MQ V7.5.0.1 and with fix pack 2 installed(V 7.5.0.2).
The version I downloaded from Partner World clearly says it is compatible for WINDOWS 7 Professional 64 bit.
When I'm running dspmqver command it is showing the mode as 32-bit. I did not find any option while installing the product asking for 32 bit or 64 bit installation. Not sure why it is installing in 32 bit mode.
Any help or suggestion is appreciated.
Below are the details I could find when I run dspmqver -a command
| Code: |
dspmqver -a
Name: WebSphere MQ
Version: 7.5.0.2
Level: p750-002-130627
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Windows
Mode: 32-bit
O/S: Windows 7 Professional x64 Edition, Build 7600
InstName: Installation1
InstDesc:
Primary: Yes
InstPath: C:\IBM\WebSphere_MQ
DataPath: C:\IBM\WebSphere_MQ
MaxCmdLevel: 750
Name: WebSphere MQ classes for Java
Version: 7.5.0.2
Level: p750-002-130627
Build Type: Production
Name: Java Message Service Client
Version: 7.5.0.2
Level: p750-002-130627
Build Type: Production
Name: WebSphere MQ classes for Java Message Service
Version: 7.5.0.2
Level: p750-002-130627
Build Type: Production
Name: IBM WebSphere MQ Telemetry
Version: 7.5.0.2
Level: p750-002-130627
Build Type: Production
Name: IBM WebSphere MQ JMS Provider
Version: 7.5.0.2
Level: p750-002-130627 mqjbnd=p750-002-130627
Build Type: Production
Name: Common Services for Java Platform, Standard Edition
Version: 7.5.0.2
Level: p750-002-130627
Build Type: Production
DistHub Build Type:
DistHub Build Level: DH000-L50930
Webscale Distribution Hub Core
Name: WebSphere MQ Advanced Message Security
Version: 7.5.0.2
Level: p750-002-130627
BuildType: IKAP - (Production)
Name: IBM WebSphere MQ custom channel for Windows Communication Foundatin
Version: 7.5.0.2
Level: wn750-002-130611_P
Build Type: Production
Name: IBM Message Service Client for .NET (XMS .NET)
Version: 2.5.0.2
Level: nn250-002-130627
Build Type: Production
Name: IBM Global Security Kit for WebSphere MQ
Version: 8.0.14.28
Build Type: Production
Mode: 32-bit
Name: IBM Global Security Kit for WebSphere MQ
Version: 8.0.14.28
Build Type: Production
Mode: 64-bit |
Note: I'm using MQ V7.5.0.2, DB2 V9.7 Client, WINDOWS 7 Professional 64 bit.
EDIT by exerk: code tags inserted |
|
| Back to top |
|
 |
| bkiran2020 |
| Posted: Thu Sep 12, 2013 4:30 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
|
| Back to top |
|
|
| exerk |
| Posted: Thu Sep 12, 2013 4:41 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bkiran2020 wrote: |
| please help on it...... |
Was it so difficult amongst all the clutter that you posted that you did not see this?
| Code: |
| The database driver reported the following details: SQL State [null], Error Code [-4472], Message [[jcc][10389][12245][4.11.77] Failure in loading native library db2jcct2, java.lang.UnsatisfiedLinkError: db2jcct2 (Not found in java.library.path) |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Tue Sep 17, 2013 4:06 am Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
Yes, you are right.
I'm able to figure out that I'm missing the native libraries of 32 bit to have a connection with the DB2.
As the MQ 7.5.0.2 installed in my machine is 64 bit compatible and after installing on my machine it shows from the logs that it is installed in 32 bit mode. So while searching for the driver libraries it is searching for a 32 bit libraries, but I have 64 bit libraries present with me as I'm using DB2 64 bit.
My concern is why the MQ is installed in 32 bit mode instead of 64 bit mode. And is there any option or installation procedure to make it 64 bit compatible?? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 17, 2013 4:08 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Please edit your post above and wrap ]code[ tags around your log output.
As for 32 v 64 issue, did you download the right executable ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Sep 17, 2013 4:20 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bkiran2020 wrote: |
As the MQ 7.5.0.2 installed in my machine is 64 bit compatible and after installing on my machine it shows from the logs that it is installed in 32 bit mode. So while searching for the driver libraries it is searching for a 32 bit libraries, but I have 64 bit libraries present with me as I'm using DB2 64 bit.
My concern is why the MQ is installed in 32 bit mode instead of 64 bit mode. And is there any option or installation procedure to make it 64 bit compatible?? |
Try THIS for an explanation...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| 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
|
|
|
|
