| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Help on issue with Wesphre MQ default trigger. |
« View previous topic :: View next topic » |
| Author |
Message
|
| lauda |
 Posted: Thu Jun 12, 2008 11:02 pm Post subject: Help on issue with Wesphre MQ default trigger. |
 |
|
Newbie
Joined: 12 Jun 2008
Posts: 3
|
please I need help... 
I work on a solution based on MQ trigger (runmq) which launch a complex java batch on AIX server and JRE 1.4. When I launch batch with same user as MQ trigger, it run successfully. When MQ trigger launch batch, it stay on SAXParser (native method form JRE), used lot of CPU and don't do nothing else...
I checked acces right and system env. The only difference is on the EXTSHM=ON variable. I checked xml files: ok. I changed java code to show xml file content: ok. Batch do the same on every xml files...
I really don't know what i can do... |
|
| Back to top |
|
 |
| sidharth_bora |
| Posted: Thu Jun 12, 2008 11:54 pm Post subject: |
|
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
what type of triggering you are using .. if its trigger -depth triggering then check the trigger control after first successful transaction
Sid |
|
| Back to top |
|
|
| AkankshA |
| Posted: Fri Jun 13, 2008 12:15 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
in second case... is ur initiation queue receiving message ??
what does runmqtrm prompt show ??
_________________
Cheers |
|
| Back to top |
|
|
| lauda |
| Posted: Fri Jun 13, 2008 12:39 am Post subject: |
|
|
Newbie
Joined: 12 Jun 2008
Posts: 3
|
It use runmqtrm... Trigger work successfully, batch is launched correctly... Batch doesn't have time to be connected on a queue. It stay on init step.
I changed code to add more debug information... Java Batch seems to parse successfully xml file included in jar files. It is not the same about XML file included in batch repositories. Java code stay locked on org.apache.xerces.parsers.SAXParser.parse(XML filestream). No error catched! and process run undefinitly... really strange... i never see that before... normally we must have a stack over flow exception!?!
I check the content of XML file in debug mode and no issues in it.
I think it is a deployment issue... maybe an encoding issue or a mystake with extension memory used by MQ?!?
Below runmqtrm prompt...
...................Nouvel execution du shell.....................
.......Variables d'environnements avant modification du classpath.......
_=/usr/bin/env
LANG=en_US
LOGIN=cmut100
PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:/busapps/cmut/100/_lgi/home/bin:/usr/bin/X11:/sbin:.
LIB=/busapps/cmut/100/_lgi/cyrs/lib
LC__FASTMSG=true
LOGNAME=cmut100
MAIL=/usr/spool/mail/cmut100
EXTSHM=ON
LOCPATH=/usr/lib/nls/loc
BIB_sys=/BIB_sys
USER=cmut100
AUTHSTATE=files
DSM_LOG=/usr/tivoli/tsm/client/ba/bin
DSMDATA=/busdata/rdsm/xxx/_lgi
SHELL=/usr/bin/ksh
ODMDIR=/etc/objrepos
BIB_bibsys=/BIB_sys
JAVA_HOME=/usr/java14/bin
DSMI_LOG=/usr/tivoli/tsm/client/api/bin
HOME=/busapps/cmut/100/_lgi/home
DSMAPPS=/busapps/rdsm/100/eneu
TERM=ansi
DSM_DIR=/usr/tivoli/tsm/client/ba/bin
MAILMSG=[YOU HAVE NEW MAIL]
PWD=/busapps/cmut/100/_lgi/cyrs/bin
BATCH_ROOT=/busapps/cmut/100/_lgi/cyrs
TZ=NFT-1DFT,M3.5.0,M10.5.0
BIB_exec_profile=OK
ENV=/BIB_sys/shell/alias.sh
DSMI_DIR=/usr/tivoli/tsm/client/api/bin
A__z=! LOGNAME
NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
.......Variables d'environnements après modification du classpath.......
_=/usr/bin/env
LANG=en_US
LOGIN=cmut100
PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:/busapps/cmut/100/_lgi/home/bin:/usr/bin/X11:/sbin:.
HOME_MQ=/usr/mqm/java/lib
LIB=/busapps/cmut/100/_lgi/cyrs/lib
LC__FASTMSG=true
CLASSPATH=:/busapps/cmut/100/_lgi/cyrs:/busapps/cmut/100/_lgi/cyrs/bin/yrsCommons.jar:/busapps/cmut/100/_lgi/cyrs/bin/yrsBatch.jar:/busapps/cmut/100/_lgi/cyrs/lib/castor-0.9.7-fix22112006-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/log4j-1.2.8-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/avalon-framework-4.2.0-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/batik-1.5b2-bin-fix05_16_2005.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-beanutils-1.7.0-bin-fix01_05_2005.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-collections-3.1-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-lang-2.0-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-logging-1.0.4-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/jcommon-0.9.6-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/jfor-0.7.1-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/jms-1.02b-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/javassist-3.4-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/saxon-6.5.3-bin-fix05_16_2005.jar:/busapps/cmut/100/_lgi/cyrs/lib/xor-codec-1.0.0-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/xnet-foundation-2.4.2-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/xnet-batch-2.4.2-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/xapool.jar:/busapps/cmut/100/_lgi/cyrs/lib/velocity-1.4-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/sync4j-ext-1.0.7.jar:/busapps/cmut/100/_lgi/cyrs/lib/struts-1.2.8-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/poi-2.5.1-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/syncserver-4.0.9-xnetfix20050901-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/objectweb-datasource.jar:/busapps/cmut/100/_lgi/cyrs/lib/jfreechart-0.9.21-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/jotm-2.0.10-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/jotm_iiop_stubs.jar:/busapps/cmut/100/_lgi/cyrs/lib/jotm_jrmp_stubs.jar:/busapps/cmut/100/_lgi/cyrs/lib/jta-spec1_0_1.jar:/busapps/cmut/100/_lgi/cyrs/lib/howl.jar:/busapps/cmut/100/_lgi/cyrs/lib/connector-1_5.jar:/busapps/cmut/100/_lgi/cyrs/lib/jts1_0.jar:/busapps/cmut/100/_lgi/cyrs/lib/fop-0.20.5-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-cli-1.0.jar:/busapps/cmut/100/_lgi/cyrs/lib/contact admin-1.4.3-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/jms-1.02b-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-logging-1.0.4-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-digester-1.7-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/commons-beanutils-1.7.0-bin-fix01_05_2005.jar:/busapps/cmut/100/_lgi/cyrs/lib/classes12.zip:/busapps/cmut/100/_lgi/cyrs/lib/carol-1.5.2-bin.jar:/busapps/cmut/100/_lgi/cyrs/lib/ow_carol.jar:/busapps/cmut/100/_lgi/cyrs/lib/activation.jar:/busapps/cmut/100/_lgi/cyrs/lib/xml-commons-1.0b2-bin.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/com.ibm.mqbind.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/jms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/fscontext.jar:/usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jta.jar
LOGNAME=cmut100
MAIL=/usr/spool/mail/cmut100
EXTSHM=ON
LOCPATH=/usr/lib/nls/loc
BIB_sys=/BIB_sys
USER=cmut100
AUTHSTATE=files
DSM_LOG=/usr/tivoli/tsm/client/ba/bin
DSMDATA=/busdata/rdsm/xxx/_lgi
SHELL=/usr/bin/ksh
ODMDIR=/etc/objrepos
BIB_bibsys=/BIB_sys
JAVA_HOME=/usr/java14/bin
DSMI_LOG=/usr/tivoli/tsm/client/api/bin
HOME=/busapps/cmut/100/_lgi/home
DSMAPPS=/busapps/rdsm/100/eneu
TERM=ansi
DSM_DIR=/usr/tivoli/tsm/client/ba/bin
MAILMSG=[YOU HAVE NEW MAIL]
PWD=/busapps/cmut/100/_lgi/cyrs/bin
BATCH_ROOT=/busapps/cmut/100/_lgi/cyrs
TZ=NFT-1DFT,M3.5.0,M10.5.0
BIB_exec_profile=OK
ENV=/BIB_sys/shell/alias.sh
DSMI_DIR=/usr/tivoli/tsm/client/api/bin
A__z=! LOGNAME
LIBPATH=:/usr/mqm/java/lib
NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
Xnet Log System: initializing
Xnet Log System: config filename is /busapps/cmut/100/_lgi/cyrs/bin/config/log4j.xml
Xnet Log System: initialization done
12 Jun 2008 13:18:57,986 [main] INFO com.XXX.xnet.logging.Log4jWatchdog - The logging system was correctly configured.
12 Jun 2008 13:18:58,009 [main] INFO com.XXX.xnet.logging.XnetLogFactory - Use a com.XXX.xnet.logging.Log4jWatchdog instance
12 Jun 2008 13:18:58,010 [main] INFO com.XXX.xnet.logging.XnetLogFactory - Xnet LogWatchdog started
12 Jun 2008 13:18:58,011 [main] INFO com.XXX.xnet.logging.XnetLogFactory - Log service started
12 Jun 2008 13:18:58,032 [main] INFO n.xnet.batch.init.BatchXnetInitialisator - Xnet version: 2.4.2
12 Jun 2008 13:18:58,147 [main] INFO helin.xnet.batch.digester.BatchResources - Loading resources from config/resources.xml
12 Jun 2008 13:18:58,766 [main] INFO org.objectweb.jotm - JOTM started with a local transaction factory which is not bound.
12 Jun 2008 13:18:58,766 [main] INFO org.objectweb.jotm - CAROL initialization
12 Jun 2008 13:18:59,459 [main] INFO org.objectweb.jotm.jta - JOTM 2.0.10
12 Jun 2008 13:18:59,522 [main] ERROR n.xnet.batch.init.BatchXnetInitialisator - ServiceManager.init() put in comment!!!
12 Jun 2008 13:18:59,539 [main] ERROR elin.xnet.persistence.PersistenceManager - ??????? BEGIN of PersistanceManager initialisation....
12 Jun 2008 13:18:59,540 [main] ERROR elin.xnet.persistence.PersistenceManager - ??????? initXmlPersistenceFile= /config/persistence/persistence.xml
12 Jun 2008 13:18:59,540 [main] ERROR elin.xnet.persistence.PersistenceManager - ??????? xmlMappingPersistenceFileURL= /com/XXX/xnet/persistence/mapping-persistence.xml
12 Jun 2008 13:18:59,687 [main] WARN com.XXX.xnet.bo.RelationManager - No model file found, Enhanced BP layer is disabled
_class: class org.exolab.castor.mapping.xml.MappingRoot
_loader: sun.misc.Launcher$AppClassLoader@17018f16
@@@@@@@@@ Begin of method unmarshall
@@@@@@@@@ XMLReader class= class org.apache.xerces.parsers.SAXParser
@@@@@@@@@ Succesfull end of parsing with XmlReader
@@@@@@@@@ Fin de la method unmarshal
_class: class java.util.Vector
@@@@@@@@@ Begin of method unmarshall
@@@@@@@@@ XMLReader class= class org.apache.xerces.parsers.SAXParser
12 Jun 2008 13:19:00,210 [main] ERROR com.XXX.xnet.xml.DTDEntityResolver - ######## DTDEntityResolver.resolveEntity for dtd: com/XXX/xnet/persistence/persistence_1_1.dtd
...................Fin d'execution du shell..................... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 13, 2008 8:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
you should probably check out this presentation from the User group.
Pay attention to the environment stuff in which MQ and the trigger monitor are being started. You may need some environment variables to be set. (see slide 10)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lauda |
| Posted: Sun Jun 15, 2008 11:48 pm Post subject: |
|
|
Newbie
Joined: 12 Jun 2008
Posts: 3
|
Thanks a lot!!! It is working well now...
Solution: .ppt, page 10. JAVA_COMPILER=NONE
I didn't understand why JIT compiler generate issues in case of MQ triggering but i get the solution.
I will be back on this forum...  |
|
| 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
|
|
|
|
