| Author |
Message
|
| kordi |
 Posted: Mon Jan 25, 2016 5:58 am Post subject: MQFB_APPL_CANNOT_BE_STARTED |
 |
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
Hi there,
We send files using spazio put tool across MQ network and offload them from queues on destination server with use of trigger monitor + spazio get tool (kind of home made MQ FTE). Everything goes smoothly and working really well however on one server, from time to time, we receive alert that messages arrived to DLQ. When I check the reason I got this: MQFB_APPL_CANNOT_BE_STARTED.
This is strange because we use the same application in the same way on all queue managers/clients and it works. There is also nothing in error logs, nothing specific in windows logs either. Can anybody has idea what may cause this problem?
Thanks |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Jan 25, 2016 6:07 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
What's in stderr and stdout, assuming you pipe out anything to it?
_________________
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 |
|
|
| kordi |
| Posted: Wed Jan 27, 2016 1:37 am Post subject: |
|
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
Sorry for delayed answer.
It looks like the tool which is being started by a triggered process is not writing anything to logs :/ |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 27, 2016 4:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
On the failing server - what mq version? What o/s version?
On the failing server, anything written to the mq error logs? To the o/s system error logs?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| kordi |
| Posted: Wed Jan 27, 2016 5:15 am Post subject: |
|
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
| MQ v7.5.0.4 is running on Windows server. I could not find anything neither in EventViewer nor in MQ error logs :/ |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 27, 2016 5:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could this be because a trigger gets written while the application is processing?
What is the trigger definition: trigger first ?
How many processes are running in parallel?
Any entries in the system log?
Are there any resource restrictions? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tczielke |
| Posted: Wed Jan 27, 2016 7:46 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
When I see the MQFB_APPL_CANNOT_BE_STARTED error intermittently, it usually has to do with some kind of operating system resource limit being hit, so the new triggered process can not be started.
One way to get more information is run a trace like below on the runmqtrm trigger monitor process:
NOTE: use the -l switch to put a cap on the max size of the trace
strmqtrc -m qmgr -t all -p runmqtrm -l 20
When you see the issue again, stop the trace and look for where the triggered process was being started. You will probably see the underlying error that the operating system returned if/when that failed on the start command.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 27, 2016 8:25 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
On the receiver end server, are any resource warning errors issued when the qmgr is re-started?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| kordi |
| Posted: Fri Jan 29, 2016 12:29 am Post subject: |
|
|
Centurion
Joined: 28 May 2012
Posts: 146
Location: PL
|
Yes, Trigger type is first, so there should be no concurrent processes running at the same time.
There is absolutely nothing neither in mq logs nor in system. Enabling trace is a good idea, I will enable it to see what is going on there in the background.
I dont see resources problem. Server has 16GB while only 6GB in use and planty of processors not utilized havily, |
|
| Back to top |
|
|
|
|
