Author |
Message
|
sleon807 |
Posted: Fri Mar 17, 2006 4:15 pm Post subject: BIP1106S: code 2102 Insufficient Java Virtual Machine |
|
|
Novice
Joined: 17 Mar 2006 Posts: 11
|
Someone can help me with this problem, I've followed this steps in my server but doesn't work, any suggestion is accept, thanks
Problem
when I add a new message set and try to deploy it in the broker. The deploy generates error message BIP1106S. This seems to be isolated to deploying just message sets.
Cause
Insufficient Java Virtual Machine (JVM) heap size.
Solution
Increased the Java Virtual Machine (JVM) heap size for the Control Center and Configuration Manager.
**Changing the Configuration Manager's JVM heap size.
1. Run the mqsistop command to stop the Configuration Manger
2. Run the mqsichangeconfigmgr command to change the Configuration
Manager's JVM heap size:
mqsichangeconfigmgr -a <ServicePassword> -i <ServiceUserID> -j <MaxJVMHeapSize>
Where:
<ServicePassword> is the password for the ServiceUserID.
<ServiceUserID> is the user ID under which the Windows NT service must run.
<MaxJVMHeapSize> The maximum Java virtual machine (JVM) heap size, in megabytes. The smallest value that can be set is 64. If this parameter is not set, the default size of 128 MB is used.
3. Run the mqsistart command to restart the Configuration Manager.
**Changing the Control Center's JVM heap size.
1. Stop the Control Center.
2. Edit the mqsilcc.bat file (which is located in the \Tool sub-directory of your installation) .
3. Find the string NODEBUG. You should see a start javaw.exe command like the one shown below.
:NODEBUG
start bin\javaw.exe -cp "%MQSI_CLASSPATH%" -mx200M com.ibm.ivm.mqitool.app.MQIToolkit
4. Change the JVM heap size setting (-mx200M). Save your changes.
5. Restart the Control Center. |
|
Back to top |
|
 |
JT |
Posted: Fri Mar 17, 2006 5:53 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
What was the new heapsize that you specified?
Have you considered migrating to a newer message broker version ? |
|
Back to top |
|
 |
sleon807 |
Posted: Wed Mar 22, 2006 11:24 am Post subject: |
|
|
Novice
Joined: 17 Mar 2006 Posts: 11
|
The new heap size now is 400Mb and I'm working with Broker Version 6.0 |
|
Back to top |
|
 |
wschutz |
Posted: Wed Mar 22, 2006 12:12 pm Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Can you paste the actual error message text for BIP1106S? I see other related topics on the broker support pages (like mqrc=20303's). _________________ -wayne |
|
Back to top |
|
 |
JT |
Posted: Wed Mar 22, 2006 12:14 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
Quote: |
......I'm working with Broker Version 6.0 |
Are you sure?
My skepticism lies in the terms that you're referencing, like 'Control Center' and 'mqsilcc.bat ', which I associate with WMQI v2.1 |
|
Back to top |
|
 |
wschutz |
Posted: Wed Mar 22, 2006 12:24 pm Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
|
Back to top |
|
 |
sleon807 |
Posted: Wed Mar 22, 2006 4:24 pm Post subject: |
|
|
Novice
Joined: 17 Mar 2006 Posts: 11
|
In fact that was I did it only I cut and pasted. The error when I try to deploy is this:
BIP1106S: WebSphere MQ error detected, reason code 2102.
An error has occurred while making a WebSphere MQ call from the Configuration Manager. The WebSphere MQ reason code is 2102. The Configuration Manager will continue processing if it is possible to do so.
For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2102. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Mar 22, 2006 4:29 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
sleon807 wrote: |
For more information on this error see the WebSphere MQ Application Programming Reference manual, code 2102. |
Quote: |
2102 (X'0836')MQRC_RESOURCE_PROBLEM
Explanation:
There are insufficient system resources to complete the call successfully.
Completion Code:
MQCC_FAILED
Programmer Response:
Run the application when the machine is less heavily loaded.
On z/OS, check the operator console for messages that may provide additional information.
On HP OpenVMS, OS/2, i5/OS, Compaq NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem. |
my emphasis. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
wschutz |
Posted: Wed Mar 22, 2006 4:44 pm Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
As Jeff says, paste the top of the FDC here for us (or use ffstsummary in the errors directory), and search here for 2102, there are quite a few hits .... _________________ -wayne |
|
Back to top |
|
 |
sleon807 |
Posted: Wed Mar 22, 2006 4:45 pm Post subject: |
|
|
Novice
Joined: 17 Mar 2006 Posts: 11
|
Thanks but I'm using Windows NT 2003 |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Mar 22, 2006 4:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Look for files ending with FDC in your Config Mgr queue manager errors directory (<mq-install>\qmgrs\<configmgr qmgr>\errors). _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
wschutz |
Posted: Wed Mar 22, 2006 4:58 pm Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
sleon807 wrote: |
Thanks but I'm using Windows NT 2003 |
Sorry? is that in response to my post? I didn't think I said anything windows specific. _________________ -wayne |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Mar 22, 2006 5:00 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
wschutz wrote: |
Sorry? is that in response to my post? I didn't think I said anything windows specific. |
The response for 2102 doesn't mention Windows.
It's likely a bug in the docs. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sleon807 |
Posted: Wed Mar 22, 2006 5:44 pm Post subject: |
|
|
Novice
Joined: 17 Mar 2006 Posts: 11
|
this is the content of the FDC file
WebSphere MQ First Failure Symptom Report
========================================
Date/Time :- Wed March 22 19:20:45 Mexico Standard Time 2006
Host Name :- BAMPLT (Windows Ver 5.2 Build 3790: Service Pack 1)
| PIDS :- 5724H7200
| LVLS :- 6.0.0.0
| Product Long Name :- WebSphere MQ for Windows
| Vendor :- IBM
| Application Name :- MQM
| Component :- hlgReserveLogSpace
| SCCS Info :- lib/logger/amqhlge0.c, 1.26
| Line Number :- 246
| Build Date :- May 19 2005
| CMVC level :- p000-L050519
| Build Type :- IKAP - (Production)
| Process :- 00009204
| Thread :- 00000013
| QueueManager :- BROKER_QMD01
| ConnId(1) IPCC :- 151
| ConnId(2) QM :- 39
| Major Errorcode :- hrcE_LOG_FULL
| Minor Errorcode :- OK
| Probe Type :- MSGAMQ6709
| Probe Severity :- 2
| Probe Description :- AMQ6709: The log for the Queue manager is full.
| FDCSequenceNumber :- 0 |
|
Back to top |
|
 |
wschutz |
Posted: Wed Mar 22, 2006 5:52 pm Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Quote: |
AMQ6709: The log for the Queue manager is full |
Well...that pretty much says it all.... yo uneed to increase the number of logs that you have and restart the qmgr:
Quote: |
The log for the Queue manager is full.
Severity:
20 : Error
Explanation:
This message is issued when an attempt to write a log record is rejected because the log is full. The queue manager will attempt to resolve the problem.
Response:
This situation may be encountered during a period of unusually high message traffic. However, if you persistently fill the log, you may have to consider enlarging the size of the log. You can either increase the number of log files by changing the values in the queue manager configuration file. You will then have to stop and restart the queue manager. Alternatively, if you need to make the log files themselves bigger, you will have to delete and recreate the queue manager. |
_________________ -wayne |
|
Back to top |
|
 |
|