| Author |
Message
|
| jeasterl |
 Posted: Thu Apr 04, 2002 10:33 am Post subject: |
 |
|
Acolyte
Joined: 24 Jun 2001
Posts: 65
|
I am trying to import one of the message sets used in the WA02 support pac. When I attempt to, I receive a BIP8165E error, indicating that there may be insufficient memory to complete this operation. I increased my page size to the max, and I still receive the error. I am running Windows 2000 Professional, and WMQI 2.1
Wonder if anyone else out there has experienced the same problem...... |
|
| Back to top |
|
 |
| CodeCraft |
| Posted: Sat May 18, 2002 1:12 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
| Did you resolve this issue? |
|
| Back to top |
|
|
| zpat |
| Posted: Sun May 19, 2002 11:24 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
You may need to increase the JVM memory heap size for the CM to 256 MB. If you ask the support center they can tell you how. Or try this at own risk (these instructions relate to MQSI 2.0.2):
· Stop the Configuration Manager if it is running:
· Via Services (Start -> Settings -> Control Panel -> Services) OR
· Using the mqsistop configmgr command
· Update the NT registry to set the JVM max heap size:
· Start the NT registry (enter regedit at a command line)
· Select HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeriesIntegrator\2\ConfigMgr
· Add new string value MaxJVMHeapSize:
· Edit -> New -> String Value
· Rename to MaxJVMHeapSize
· Right click and select Modify:
· Enter 268435456 in Value data and click OK
Restart CM. |
|
| Back to top |
|
|
| mapa |
| Posted: Mon May 20, 2002 10:46 pm Post subject: MaxJVMHeapSize |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Why not issue the mqsichangeconfigmgr and use the -j option there, instead of editing the registry.?
Best regards Mapa |
|
| Back to top |
|
|
| michaelpatton |
| Posted: Tue May 21, 2002 7:42 pm Post subject: |
|
|
Apprentice
Joined: 21 May 2002
Posts: 25
Location: East Coast USA
|
| The memory in your system in NOT the issue here. It is an incorrect message that is being issued. The problem is with the exported message set that is being imported. Try reexporting the message set from the original configuration manager, making sure that none of the elements are checked out, and reimport to the new configuration manager. |
|
| Back to top |
|
|
| kirani |
| Posted: Tue May 21, 2002 8:38 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Michaelpatoon,
I don't think there is a problem with the exported messagesets. WA02 is a support pac, so i guess someone at IBM has exported them (after lots of testing).
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| anuppc |
| Posted: Tue Oct 22, 2002 11:57 am Post subject: |
|
|
Voyager
Joined: 22 Oct 2002
Posts: 93
Location: Montreal
|
Does anyone have a solution for this?
_________________
BlowFish |
|
| Back to top |
|
|
| anuppc |
| Posted: Tue Oct 22, 2002 12:13 pm Post subject: |
|
|
Voyager
Joined: 22 Oct 2002
Posts: 93
Location: Montreal
|
| anuppc wrote: |
| Does anyone have a solution for this? |
i found the solution for this problem.. The error displayed while running the command is misleading.
The problem is with the message set mismatch in wa02 pack.
Replace MQSWFXML_Order21.mrp for message set MQSWFXML_Order2 to support 'WebSphere MQ Integrator Version 2.1'
Hope this solves the problem!
_________________
BlowFish |
|
| Back to top |
|
|
|
|
