Topic
2 replies Latest Post - ‏2013-02-07T13:45:05Z by R_Simons
T2G6_kobi_lavi
T2G6_kobi_lavi
3 Posts
ACCEPTED ANSWER

Pinned topic Configuring FTE Logger for MQ 7.5

‏2013-02-07T08:31:37Z |
Hi,
I'm using MQ V7.5.
I have installed Managed File transfer package.

I'm trying to create a test environment for FTE,
I'm using single-QMgr topology, QM-name: COORDQM.

Currently I'm having one agent which performs one File-To-File monitor - So far so good, everything works fine.

The next step I'm trying to do is to setup logger,
I'm using a DB-type logger with DB2.

I have created the schemas as described using the sql file supplied by IBM.

I have created a new logger and the required queues, the logger is set to run as windows-service.

the problem is that when I'm starting the logger it's crashes in few seconds.

stderr.log says:

Exception in thread 
"main" java.lang.NoClassDefFoundError: com.ibm.mq.jmqi.JmqiException   at java.lang.J9VMInternals.verifyImpl(Native Method)   at java.lang.J9VMInternals.verify(J9VMInternals.java:72)   at java.lang.J9VMInternals.verify(J9VMInternals.java:70)   at java.lang.J9VMInternals.verify(J9VMInternals.java:70)   at java.lang.J9VMInternals.initialize(J9VMInternals.java:134)   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)   at java.lang.reflect.Method.invoke(Method.java:600)   at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.run(BootstrapMain.java:271)   at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.main(BootstrapMain.java:117)   Caused by: java.lang.ClassNotFoundException: com.ibm.mq.jmqi.JmqiException   at java.net.URLClassLoader.findClass(URLClassLoader.java:423)   at java.lang.ClassLoader.loadClass(ClassLoader.java:660)   at java.lang.ClassLoader.loadClass(ClassLoader.java:626)   ... 11 more

service0.log says:

[06/02/2013 15:56:49 GMT] Service ftelogger starting [06/02/2013 15:56:49 GMT] logDirectory is: C:\Program Files\IBM\WebSphere MQ\mqft\logs\COORDQM\loggers\FTELOGGER\logs [06/02/2013 15:56:49 GMT] logLevel is: Info [06/02/2013 15:56:49 GMT] service arguments: [06/02/2013 15:56:49 GMT] arg[0] : C:\Program Files\IBM\WebSphere MQ\bin\mqmftpcservice.exe [06/02/2013 15:56:49 GMT] arg[1] : ftelogger [06/02/2013 15:56:49 GMT] arg[2] : C:\Program Files\IBM\WebSphere MQ\mqft\logs\COORDQM\loggers\FTELOGGER [06/02/2013 15:56:49 GMT] arg[3] : Info [06/02/2013 15:56:49 GMT] arg[4] : -appId=ftelogger@COORDQM [06/02/2013 15:56:49 GMT] arg[5] : -directory=C:\Program Files\IBM\WebSphere MQ\mqft\logs\COORDQM\loggers\FTELOGGER [06/02/2013 15:56:49 GMT] arg[6] : -properties=C:\Program Files\IBM\WebSphere MQ\mqft\config\COORDQM\loggers\FTELOGGER\logger.properties [06/02/2013 15:56:49 GMT] arg[7] : C:\Program Files\IBM\WebSphere MQ\java\jre\bin\java [06/02/2013 15:56:49 GMT] arg[8] : -classpath [06/02/2013 15:56:49 GMT] arg[9] : C:\Program Files\IBM\WebSphere MQ\mqft\lib\com.ibm.wmqfte.daemon.jar;C:\Program Files\IBM\WebSphere MQ\mqft\lib\com.ibm.wmqfte.bootstrap.jar;C:\Program Files\IBM\WebSphere MQ\mqft\lib\com.ibm.wmqfte.exitroutines.api.jar [06/02/2013 15:56:49 GMT] arg[10] : -Djava.util.logging.config.file=C:\Program Files\IBM\WebSphere MQ\mqft\lib\logging.properties [06/02/2013 15:56:49 GMT] arg[11] : -Dcom.ibm.wmqfte.product.root=C:\Program Files\IBM\WebSphere MQ\mqft [06/02/2013 15:56:49 GMT] arg[12] : -Duser.home= [06/02/2013 15:56:49 GMT] arg[13] : -Dcom.ibm.tools.attach.enable=no [06/02/2013 15:56:49 GMT] arg[14] : -Dcom.ibm.wmqfte.excludeListFilename=config/databaseLoggerJarList.properties [06/02/2013 15:56:49 GMT] arg[15] : com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain [06/02/2013 15:56:49 GMT] arg[16] : com.ibm.wmqfte.api.StartLogger [06/02/2013 15:56:49 GMT] arg[17] : -F [06/02/2013 15:56:49 GMT] arg[18] : -co [06/02/2013 15:56:49 GMT] arg[19] : 

false [06/02/2013 15:56:49 GMT] arg[20] : -p [06/02/2013 15:56:49 GMT] arg[21] : COORDQM [06/02/2013 15:56:49 GMT] arg[22] : ftelogger [06/02/2013 15:56:49 GMT] ProcessController starting [06/02/2013 15:56:52 GMT] ProcessController shutdown requested [06/02/2013 15:56:52 GMT] ProcessController shutdown, exit status: 1 [06/02/2013 15:56:52 GMT] Service ftelogger exiting

The logger.properties file is:

# #Thu Feb 07 09:36:33 IST 2013 javaCoreTriggerFile=C\:\\Program Files\\IBM\\WebSphere MQ\\mqft\\logs\\COORDQM\\loggers\\FTELOGGER\\javaCoreTriggerFile wmqfte.database.type=DB2 wmqfte.database.native.library.path=/Program Files/IBM/SQLLIB/bin wmqfte.queue.manager=COORDQM windowsService=FTELOGGER wmqfte.logger.type=DATABASE wmqfte.database.driver=/Program Files/IBM/SQLLIB/java/db2jcc.jar wmqfte.database.name=FTELOGDB windowsServiceVersion=2.00 wmqfte.logger.name=FTELOGGER wmqfte.database.credentials.file=/Program Files/IBM/WebSphere MQ/mqft/config/COORDQM/MQMFTCredentials.xml


The MQMFTCredentials.xml file lokk like that:

<?xml version=
"1.0" encoding=
"UTF-8"?> <tns:mqmftCredentials xmlns:tns=
"http://wmqfte.ibm.com/MQMFTCredentials" xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=
"http://wmqfte.ibm.com/MQMFTCredentials MQMFTCredentials.xsd">   <tns:logger name=
"ftelogger" user=
"db2admin" password=
"db2admin"/>   </tns:mqmftCredentials>


What am I doing wrong?
Updated on 2013-02-07T13:45:05Z at 2013-02-07T13:45:05Z by R_Simons
  • T2G6_kobi_lavi
    T2G6_kobi_lavi
    3 Posts
    ACCEPTED ANSWER

    Re: Configuring FTE Logger for MQ 7.5

    ‏2013-02-07T13:05:34Z  in response to T2G6_kobi_lavi
    Important note:

    when running the logger in normal mode (=not a service mode),it's works fine.
    Also when running it in Foreground (fteStartLogger -F <loggerName>), it's works fine (but the service is not getting in started status).
  • R_Simons
    R_Simons
    11 Posts
    ACCEPTED ANSWER

    Re: Configuring FTE Logger for MQ 7.5

    ‏2013-02-07T13:45:05Z  in response to T2G6_kobi_lavi
    Check you environment variables, CLASSPATH.

    Caused by: java.lang.ClassNotFoundException: com.ibm.mq.jmqi.JmqiException

    This error tells me that you may have additional environment variables set for your ID when you are running the logger in foreground than those that are set for the base OS when running the logger as a service.