| Author |
Message
|
| mangoMan |
 Posted: Mon Mar 19, 2007 3:42 pm Post subject: Error Deploying MsgFlow BIP0915E |
 |
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
I have a fairly big (25 Meg) bar file that I am trying to deploy. When I deploy it from the toolkit I get the BIP0915E error.
http://home.att.net/~mangoman/error.bmp
It says:
| Quote: |
| Could not put a message to the Configuration Manager queue |
I have no errors in the event log. I can put a 30 Meg message on a queue that I created on the same QMgr. Can anyone help? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Mar 19, 2007 3:48 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Check all the SYSTEM.BROKER.* queues on the ConfigMgr qmgr for the MAXMSGLN.
Check SYSTEM.BKR.CONFIG channel for MAXMSGLN.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Mon Mar 19, 2007 5:39 pm Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
MAXMSGLN for SYSTEM.BROKER.* queues on the ConfigMgr qmgr = 104857600 bytes
MAXMSGLN for SYSTEM.BKR.CONFIG is 4194304
But is SYSTEM.BKR.CONFIG channel being used since everything is running on my laptop? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Mar 19, 2007 6:59 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Toolkit always connects through SYSTEM.BKR.CONFIG.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Mar 20, 2007 8:05 am Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
This is a wicked problem.
I just changed the MAXMSGLN for SYSTEM.BKR.CONFIG to 104857600 bytes .
Stopped and started the channel and I get the exact same error when I try to deploy the bar file..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 20, 2007 8:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay.
It's telling you that the ConfigMgr queue manager does not have a route to the Broker queue manager.
Do you have any messages in the DLQs?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Mar 20, 2007 9:30 am Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
I still hold that this is a wicked problem.
I restarted the QMgr after changing the MAXMSGLN for SYSTEM.BKR.CONFIG .
So now I can deploy the bar file but I don't get a message and the flow does not show up in the execution group. When I look in the event log I see the following:
| Quote: |
( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) java.lang.OutOfMemoryError in Configuration Manager MQProcessor class 'run' method.
A java.lang.OutOfMemoryError was caught by the Configuration Manager MQProcessor class 'run' method. This means the Java Virtual Machine has exhausted its available memory heap.
Stop the Configuration Manager using the mqsistop command. Increase the maximum size of the Java Virtual Machine memory heap using the mqsichangeconfigmgr command, specifying the -j option. Refer to the WebSphere Message Brokers online documentation for guidance. Then restart the Configuration Manager and retry the operation. Repeat if necessary until the error no longer occurs. |
I have increased the heap size to 2048 MB using the following command but that has not helped, I keep getting the same error. Does it make sense to increase the heap size to 3000 or 4000 MB?
| Quote: |
| mqsichangeconfigmgr WBRK6_DEFAULT_CONFIGURATION_MANAGER -a db2admin -i db2admin -j 2048 |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 20, 2007 10:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe 2048 is not big enough.
Why exactly is the bar file so big? Have you tried creating a brand new bar file with the same resources, and seeing if that comes out a smaller size?
Are you able to put different things into different bar files? Like put the flows in one bar file and the sets in another, and put as many JAR files as you can into shared-classes, rather than the BAR...
You could enable service trace, and try and figure out what's going on from that, although service trace is really only supposed to be run under the guidance of IBM Support...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mangoMan |
| Posted: Tue Mar 20, 2007 10:46 am Post subject: |
|
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
I have tried deleting the bar file and creating a new one. No difference.
The bar file is big because of the JAR files. We use them in the Java Compute Node.
Not familiar with the shard-classes or the service trace concepts. Where can I learn more about this? |
|
| Back to top |
|
|
| jon |
| Posted: Tue Nov 03, 2009 5:27 pm Post subject: |
|
|
Apprentice
Joined: 17 May 2009
Posts: 32
|
Hi All,
I am also facing the exact same problem, is there any solution out there, the DLQ is not showing anything 
_________________
When you have a dream, you've got to grab it and never let go. - Carol Burnett |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Nov 03, 2009 11:51 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| mangoMan wrote: |
I have tried deleting the bar file and creating a new one. No difference.
The bar file is big because of the JAR files. We use them in the Java Compute Node.
Not familiar with the shard-classes or the service trace concepts. Where can I learn more about this? |
always keep all the jar files in shared-classes directory.. do not build them in bar
does your broker and configuration manager share same queue manager ?? if not then what is MAXMSGLEN on those send rcvr pair ?
_________________
Cheers |
|
| Back to top |
|
|
|
|
