| Author |
Message
|
| santy |
 Posted: Fri Aug 07, 2009 6:00 am Post subject: Broker deployment timeout problem |
 |
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi,
I'm deploying one bar file on WMB 6.1 which contains 5 message flows on 4 ex. groups.
It worked fine for first ex. group, but thrown an error for second ex. group -
I'm getting this error when the message flow contains Java Compute node.
BIP1100E: Broker LOCALBR had not responded before the timeout occurred.
BIP4502E: An unexpected
error occurred during the deployment of a Java resource. : BMUSIS18.e6004c1b-2001-0000-0080-d6bd5ca84872: /build/S610_P/src/
DataFlowEngine/JavaComputeNode/ImbJavaComputeResource.cpp: 295: ImbJavaComputeResource::rollback: JAR: JAR
Is there any way to find out what was happened at that time for that ex. group, because no other request was getting processed by config. manager at that time ?
Broker, Config Manager and Queue Manager are created on UNIX system. and I connect to it through toolkit. |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Mon Aug 10, 2009 9:19 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Service trace will tell you what's going on, but that's quite internal.
However I can think of two possibilities of what the problem might be:
1) you're not including all the relevant JAR files inside the broker archive
2) the broker user doesn't have authority to, or the broker can't for some reason, write to the directory where the JAR files are placed (some place off $MQSI_REGISTRY). |
|
| Back to top |
|
|
| santy |
| Posted: Thu Aug 13, 2009 6:40 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi,
Is this happening due to memory leak problem in execution group? |
|
| Back to top |
|
|
| santy |
| Posted: Thu Aug 13, 2009 8:50 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
| Does anybody know about this ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Aug 13, 2009 9:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santy wrote: |
| Does anybody know about this ? |
mqmatt had a few thoughts.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| santy |
| Posted: Thu Aug 13, 2009 9:37 am Post subject: |
|
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi Vitor,
As per mqmatt....
1) all JAR files are pleace in bar file
2) this bar file which contains jar files gets deployed to some execution groups and some not.
It is not possible for me to take trace as I don't have access to service trace. |
|
| Back to top |
|
|
| dilse |
| Posted: Thu Aug 13, 2009 10:28 am Post subject: |
|
|
Master
Joined: 24 Jun 2004
Posts: 270
|
Sometimes if the BAR file is too big to deploy to an execution group a timeout could occur. Try putting the Jar files in "Shared-classes" folder and reference these as external Jars on your Java project. If it still fails, try to do increase the heap zise of the exec group and see if it works.
Good luck... |
|
| Back to top |
|
|
|
|
