Author |
Message
|
anuppc |
Posted: Tue Feb 15, 2005 8:17 pm Post subject: Trigger Connection broken while putting a message to a UPES |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
Hi,
The trigger monitor seem to fail as soon as i put a message into the UPES queue.
My workflow server is running on an AIX box.
I am able to start the execution server, sheduling server and query for existing templates.
The moment i try to createandstart an instance.... of template, it fails...
Yes , i tried the create and start seperately... create succeeded but start failed....
Any suggestions what could go wrong? Is there any special settings for the UPES queue.....?
Thanx _________________ BlowFish |
|
Back to top |
|
 |
jmac |
Posted: Wed Feb 16, 2005 5:17 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
I would guess that your message is mal-formed somehow. Althogugh I am not sure why that would kill the trigger monitor.
Perhaps if you post the message someone will be able to spot something _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
vennela |
Posted: Wed Feb 16, 2005 10:19 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
The trigger monitor seem to fail as soon as i put a message into the UPES queue. |
Why would you put a message to a UPES queue. Let's assme that you are putting to EXEXMLINPUTQ. But I am still at a loss to what is happening. Is the first activity in your workflow a UPES activity?If so, is the UPES queue defined? |
|
Back to top |
|
 |
anuppc |
Posted: Thu Feb 17, 2005 6:04 am Post subject: |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
Yes the first activity throws a message to UPES.
My environment is AIX, MQWF 3.4 with fix pack 6 (just installed the fix pack as per some suggestion in wf forum)
This is the trace.......
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM ' &
Error starting triggered application.
__________________________________________________
Waiting for a trigger message
FMC10200I Execution server for system FMCSYS started.
FMC31050E An error has occurred which has terminated processing.
FMC31050E An error has occurred which has terminated processing.
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM ' &
Error starting triggered application.
__________________________________________________
Waiting for a trigger message
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM ' &
Error starting triggered application.
__________________________________________________
Waiting for a trigger message
FMC10200I Execution server for system FMCSYS started.
FMC31050E An error has occurred which has terminated processing.
FMC10200I Execution server for system FMCSYS started.
FMC31050E An error has occurred which has terminated processing.
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM ' &
Error starting triggered application.
__________________________________________________
Waiting for a trigger message
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM ' &
Error starting triggered application.
__________________________________________________
Waiting for a trigger message
FMC10200I Execution server for system FMCSYS started.
FMC10200I Execution server for system FMCSYS started.
FMC31050E An error has occurred which has terminated processing.
/var/fmc/cfgs/FMC/bin/fmczemst 'TMC 2 FMC.FMCGRP.FMCSYS.PROC.EXE /var/fmc/cfgs/FMC/bin/fmczemst & -i:ExeSvr -y:FMC FMCQM ' &
Error starting triggered application.
__________________________________________________
Waiting for a trigger message
FMC10200I Execution server for system FMCSYS started.
02/16/05 17:01:1802/16/05 17:01:1802/16/05 17:01:1802/16/05 17:01:18 FMC31050E An error has occurred which has terminated processing.
FMC31050E An error has occurred which has terminated processing.
FMC31050E An error has occurred which has terminated processing.
FMC31050E An error has occurred which has terminated processing.
WebSphere MQ trigger monitor connection broken.
WebSphere MQ trigger monitor ended.
02/16/05 17:01:18 FMC31050E An error has occurred which has terminated processing.
02/16/05 17:01:18 FMC31050E An error has occurred which has terminated processing.
02/16/05 17:01:18 FMC31050E An error has occurred which has terminated processing. _________________ BlowFish |
|
Back to top |
|
 |
jmac |
Posted: Thu Feb 17, 2005 6:23 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
1. Are you logging to MQ?
2. How did you define the UPES Queue for your first activity?
3. Where is this "trace" being written? Is this going to fmcsys? or are you running a trace? _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
anuppc |
Posted: Thu Feb 17, 2005 9:33 am Post subject: |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
1. Are you logging to MQ?
Can you elaborate?
2. How did you define the UPES Queue for your first activity?
runmqsc
DEFINE QLOCAL(UPES1QUEUE)
definition from my fdl:
SERVER 'UPES1'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "UPES1QUEUE"
QUEUE_MANAGER_NAME "FMCQM"
VERSION 3
RELEASE 4
LEVEL 0
END 'UPES1'
3. Where is this "trace" being written? Is this going to fmcsys? or are you running a trace?
im running a trace....
the trace file has messages from the trigger
runmqtrm -m FMCQM -q FMCTRIGGER &
and from fmcamain -cy & _________________ BlowFish |
|
Back to top |
|
 |
jmac |
Posted: Thu Feb 17, 2005 10:07 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
anuppc wrote: |
1. Are you logging to MQ?
Can you elaborate?
|
Are you specifying AUDIT TO MQ in your FDL? _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
anuppc |
Posted: Thu Feb 17, 2005 10:45 am Post subject: |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
No audit to mq but i do audit to db _________________ BlowFish |
|
Back to top |
|
 |
jmac |
Posted: Thu Feb 17, 2005 10:50 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
I would open a PMR on this. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
hos |
Posted: Thu Feb 17, 2005 11:25 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
Hi,
have you ever looked into the system and error log files of MQWF?
Have you checked the error log of MQ?
If that doesn't help, have you checked the DB log?
In addition: did you run the configuration checker fmczchk? |
|
Back to top |
|
 |
anuppc |
Posted: Fri Feb 18, 2005 9:32 am Post subject: |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
Trace from the fmcerr.log
--------------------------------------
Error location = File=/projects/fmc/drvp/lbld/v340/src/fmckdbg.cxx, Line=199, F
unction=fmckAssert(const char *, const char *, unsigned int)
Error data = FmcAssertionException, Condition=*** Assertion failed in /proj
ects/fmc/drvp/lbld/v340/src/fmcscbrg.cxx(101): false
WebSphere MQ Workflow 3.4 Error Report
Report creation = 02/18/05 11:55:05
Related message = FMC31050E An error has occurred which has terminated processin
g.
Error location = File=/projects/fmc/drvp/lbld/v340/src/fmckdbg.cxx, Line=199, F
unction=fmckAssert(const char *, const char *, unsigned int)
Error data = FmcAssertionException, Condition=*** Assertion failed in /proj
ects/fmc/drvp/lbld/v340/src/fmcscbrg.cxx(101): false
WebSphere MQ Workflow 3.4 Error Report
fmcsys.log
----------------------------------------------------------------------------
02/18/05 11:41:09 FMC10200I Execution server for system FMCSYS started.
02/18/05 11:41:09 FMC10500I Execution server instance started.
02/18/05 11:41:13 FMC10000I System startup complete. System FMCSYS in system gro
up FMCGRP is now running.
02/18/05 11:55:05 FMC31050E An error has occurred which has terminated processin
g.
02/18/05 11:55:05 FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectNa
me=FMC.FMCGRP.FMCSYS.ADM, severe error02/18/05 11:55:05 FMC31050E An error has o
ccurred which has terminated processing.
02/18/05 11:55:05 FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectNa
me=FMC.FMCGRP.FMCSYS.SCH, severe error02/18/05 11:55:05 FMC31050E An error has o
ccurred which has terminated processing.
02/18/05 11:55:05 FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectNa
me=FMC.FMCGRP.FMCSYS.EXE, severe error02/18/05 11:55:05 FMC31050E An error has o
ccurred which has terminated processing.
02/18/05 11:55:05 FmcFMLException, MQReturnCode=2, MQReasonCode=2161, MQObjectNa
me=FMC.FMCGRP.FMCSYS.EXE, severe error02/18/05 11:55:05 FMC31050E An error has o
ccurred which has terminated processing.
:q _________________ BlowFish |
|
Back to top |
|
 |
anuppc |
Posted: Fri Feb 18, 2005 9:33 am Post subject: |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
This is the fmczchk trace.... i see a warning about MQ port is that a prob?
---------------------------------------------------------------------------------
FMC34010I: Configuration checker version 3.4.0.110 started.
FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.4.0 checks.
FMC34013I: ===> Admin Server found, checks started.
FMC34500I: ==> Database Manager configuration for db2adm.
FMC34501I: ==> Database configuration for FMCDB.
FMC34502I: ==> Database connection to FMCDB.
FMC34013I: ===> Server message device found, checks started.
FMC34nnnW: No MQSeries TCP port found at default number 5010
FMC34013I: ===> Execution Server found, checks started.
FMC34013I: ===> Client message layer (server API) found, checks started.
FMC34013I: ===> Client message layer (client API) found, checks started.
FMC34013I: ===> WebSphere MQ Workflow C/C++ API found, checks started.
FMC34013I: ===> Java Agent found, checks started.
FMC34100I: Messages have been written to /var/mqm/log/FMCQM/fmczchk.log.
FMC34999I: Configuration checker ended: 0 error(s), 1 warning(s), rc = 0. _________________ BlowFish |
|
Back to top |
|
 |
vennela |
Posted: Fri Feb 18, 2005 10:14 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
This is the fmczchk trace.... i see a warning about MQ port is that a prob? |
For sure: NO |
|
Back to top |
|
 |
hos |
Posted: Mon Feb 21, 2005 12:10 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
Quote: |
My environment is AIX, MQWF 3.4 with fix pack 6 (just installed the fix pack as per some suggestion in wf forum) |
What about your MQ Series service level? You should have SP7. I would open a PMR on this. |
|
Back to top |
|
 |
anuppc |
Posted: Mon Feb 21, 2005 11:41 am Post subject: |
|
|
 Voyager
Joined: 22 Oct 2002 Posts: 93 Location: Montreal
|
May be this is related.... Version and Level
What is the significance of
SERVER 'UPES2'
RELATED_GROUP 'FMCGRP'
RELATED_SYSTEM 'FMCSYS'
TYPE USER_DEFINED_PROGRAM_EXECUTION_SERVER
MQSYSTEM MQSERIES
MESSAGE_FORMAT XML
PHYSICAL_QUEUE_NAME "UPES2QUEUE"
QUEUE_MANAGER_NAME "FMCQM"
VERSION 3
RELEASE 3 LEVEL 0
END 'UPES2'
Is this my definitions are with an old version of MQWF? Does Version and release correspond to MQWF 3.3?? _________________ BlowFish |
|
Back to top |
|
 |
|