Author |
Message
|
narayankumarpr |
Posted: Thu Feb 06, 2003 1:56 am Post subject: CSD 4 - Javaw.exe Application error |
|
|
Newbie
Joined: 01 Jul 2002 Posts: 9
|
Hi
We have recently applied CSD 4 for WMQSI 2.1 and CSD 5 for MQ 5.2.1 in our environment (windows 2000). I am facing a typical problem ever since the up gradation.
When ever we do a copy & past operation in compute node, I am getting a JAVAW. exe application error and the control center gets closed. Of course the changes done are gone.
The following is the window system error captured
---------------------------------------------------------
Application popup: javaw.exe - Application Error : The instruction at "0x7098512f" referenced memory at "0x00004288". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
Can any one help me in fixing this problem .Is it CSD 4 bug ?
Thanks & Regards
Narayan Kumar PR |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Feb 19, 2003 7:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
This appears to be a bug in CSD04 for WMQI. It seems to happen when editing ESQL.
It only affects Control Center. There are a couple of viable workarounds:
1) Edit your ESQL outside the Control Center (in Notepad or something), and copy and paste the code into the appropriate node.
2) Roll back *just* your control center to CSD03 - this only works if you're using the Control Center remotely and not on the ConfigMgr machine.
I have opened a PMR on this issue. |
|
Back to top |
|
 |
philip.baker |
Posted: Thu Feb 20, 2003 12:34 pm Post subject: |
|
|
 Voyager
Joined: 21 Mar 2002 Posts: 77 Location: Baker Systems Consulting, Inc. - Tampa
|
This 'bug' has also been seen using WindowsXP with WMQIV2.1 CSD4 and WMQV5.3(CSD1). _________________ Regards,
Phil |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Feb 21, 2003 9:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I have been provided an efix that appears to correct the problem.
There seem to be two versions of this efix. I was originally given the efix and told "if you are not using ASBITSTREAM function in your ESQL, please apply the following e-fix". Since in some cases I am using ASBITSTREAM, I asked for one that did not affect ASBITSTREAM. I was then given a different version of the efix.
Please keep this in mind if you request this efix from IBM. I was told this would be rolled into CSD05. |
|
Back to top |
|
 |
jfluitsm |
Posted: Mon Feb 24, 2003 5:56 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002 Posts: 160 Location: The Netherlands
|
You can try to delete and create the configmgr, this worked ok for me on one computer but had no effect on another (both with cc, configmgr and broker on the same computer). _________________ Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
Back to top |
|
 |
|