| Author |
Message
|
| rajasri |
 Posted: Mon Sep 18, 2006 11:56 pm Post subject: problem after installing latest fixpack |
 |
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
Hi all, i am facing problem in connecting to Config Mgr after installing Latest Tool Kit fixpack. there are sequence of error reports in event viewer. executions groups are tried to start but then stopped abruptly. one of the error is as follows.
( CITCO_BRK.TestHarness_SF_EAIINPUT ) Failed to create Java VM -1.
The broker creates a Java Virtual Machine to support internal operations, but in this case has been unable to do so. There may have been a problem with the way the product was installed, or something has subsequently affected the installation.
This is an internal error and you should contact your IBM support center.
Java 1.5 is already installed in the system. and after that broker was installed, then i dint face any problems. but after installing the fixpack these errors are coming. should i set any thing in class path. i have removed all the values in the PATH variable which point to java 1.5 that was installed previously. but no progress. what else should i edit. any king of suggestion is appreciated. |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Sep 19, 2006 12:51 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi rajasri,
The toolkit does not use Java 1.5....the Java.exe used is within the installed directory...and I would suggest you dont play with that 
Uninstall the v1.5 just to make sure....shutdown and start your system again...try opening the toolkit with -clean
I dont think these are concrete solutions, but you could try these before having to reinstall everything 
Regards. |
|
| Back to top |
|
|
| rajasri |
| Posted: Tue Sep 19, 2006 12:58 am Post subject: installing fixpack |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| Hi Elvis, thanks for the response, but i am still worried about uninstalling java 1.5. what if i also need java 1.5 for some other purposes. is there any way to spefify the broker what java it has to use, like the one presnt in the broker instaled directory. i think there should be some way. And then i have removed the java_home variable from the environment variables, now i think broker is no way connected with the java 1.5. should i set any environment variable? |
|
| Back to top |
|
|
| rajasri |
| Posted: Tue Sep 19, 2006 1:01 am Post subject: fixpack |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| And, if broker is very strict about the java version, then why was it working properly before i installed the fixpack? |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Sep 19, 2006 1:04 am Post subject: Re: installing fixpack |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi rajasri,
| rajasri wrote: |
| but i am still worried about uninstalling java 1.5. what if i also need java 1.5 for some other purposes |
I did not mean that u should not have v1.5 running in the system...that was only to make sure that u have not made the toolkit already point to v1.5...remove it for now, fix your toolkit, then install it again.
| rajasri wrote: |
| is there any way to spefify the broker what java it has to use, like the one presnt in the broker instaled directory. i think there should be some way. And then i have removed the java_home variable from the environment variables, now i think broker is no way connected with the java 1.5. should i set any environment variable? |
You should not, actually never be making the toolkit point to any other java version....especially not v1.5....v1.5 is a leap ahead of the older versions...
You do not have to make any entries in the Environment variables, but then saying so, u are not supposed to delete any also  I hope you know what u have deleted....revert back the changes...
Regards. |
|
| Back to top |
|
|
| rajasri |
| Posted: Tue Sep 19, 2006 1:07 am Post subject: fixpack |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| thank Elvis, i will do it and let u know |
|
| Back to top |
|
|
| rajasri |
| Posted: Tue Sep 19, 2006 1:59 am Post subject: fixpack |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
| Hi Elvis, i have uninstalled java 1.5 run time environment and also development kit. i have restarted my system but all in vain. it still shows me the same error, what to do?. while uninstalling jre 1.5, it has asked me to close broker toolkit, so it is confirmed that broker was using jre 1.5. then i closed the toolkit and uninstalled jre, ans then resstarted. but no progress. any thing else to be done by me? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 19, 2006 2:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, let's be clear.
You applied fixes to your Toolkit.
You're seeing errors with your execution groups?
Then the two things are unreleated. EGs are runtime.
Let's start from scratch, as it were.
Stop everything - Toolkit, broker, configmgr. Start Broker. Look for log entries. Start configmgr, look for log entries.
Start Toolkit - look for log entries, both in system log and in eclipse log.
Attempt to connect to configmgr - look for log entries in eclipse log and system log...
Where does the first error occur?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rajasri |
| Posted: Tue Sep 19, 2006 2:31 am Post subject: fixpack |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
Hi Jeff, as u said i stoped everything and closed toolkit. first started broker. These were th error in th event viewer. and these are repeating in cycles.
1) ( CITCO_BRK ) Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/CITCO_BRK.3324.3924.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 3324, on thread 0xF54.
Type: EXCEPTION_UNKNOWN_TYPE: E06D7363 (E06D7363).
Address: 001B:7C812A5B.
Exception Parameters: 3
Param#0: 0x19930520
Param#1: 0x0012f3a8
Param#2: 0x2fc292b8
'.
A broker process is terminating abnormally.
Contact your IBM support center.
2) ( CITCO_BRK ) Message broker internal error: diagnostic information 'As a result of a Severe Abend Error, a MiniDump has been written to: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/CITCO_BRK.3324.3924.dmp'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: 'As a result of a Severe Abend Error, a MiniDump has been written to: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/CITCO_BRK.3324.3924.dmp'.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
3) ( CITCO_BRK.TestHarness_SF_EAIINPUT ) An execution group has encountered a problem whilst starting.
An execution group has encountered a problem whilst starting and is unable to continue.
Check the following error messages to try to identify the cause of the problem. If it is unclear what the cause is, and the problem occurs continually after restarting the message broker contact your IBM support center.
3)
( CITCO_BRK.TestHarness_SF_EAIINPUT ) Failed to create Java VM -1.
The broker creates a Java Virtual Machine to support internal operations, but in this case has been unable to do so. There may have been a problem with the way the product was installed, or something has subsequently affected the installation.
This is an internal error and you should contact your IBM support center.
------------------------------------------------------------------------------------
Then i started configmgr. these were the errors in th event viewer
1) ( ConfigManager ) Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/ConfigManager.2640.2684.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 2640, on thread 0xA7C.
Type: EXCEPTION_UNKNOWN_TYPE: E06D7363 (E06D7363).
Address: 001B:7C812A5B.
Exception Parameters: 3
Param#0: 0x19930520
Param#1: 0x0012f554
Param#2: 0x2fc292b8
'.
A broker process is terminating abnormally.
Contact your IBM support center.
2) ( ConfigManager ) Message broker internal error: diagnostic information 'As a result of a Severe Abend Error, a MiniDump has been written to: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/ConfigManager.2640.2684.dmp'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: 'As a result of a Severe Abend Error, a MiniDump has been written to: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/ConfigManager.2640.2684.dmp'.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
3) ( ConfigManager ) The WebSphere Message Brokers service detected that executable 'bipconfigmgr.exe' terminated, exit code 1.
An executable terminated unexpectedly.
The WebSphere Message Brokers service will restart the executable automatically unless the broker is currently shutting down. Determine the reason for the unexpected termination of this executable.
hope this has made clear. is this error not related to JVM version? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 19, 2006 3:09 am Post subject: Re: fixpack |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| rajasri wrote: |
| Contact your IBM support center. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 19, 2006 3:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also, it's not very likely that this is related to applying service to the Toolkit, unless you also applied service to the runtime - or someone has badly mangled the Toolkit service...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 19, 2006 3:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The JAVA_HOME env variable should be pointing to the broker's JVM.
You may have to create batch files for your other applications to start so that the JAVA_HOME variable points to the 1.5 JVM for them.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 19, 2006 3:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| The JAVA_HOME env variable should be pointing to the broker's JVM. |
That would be set in mqsiprofile.cmd. rajasri should not have changed that file.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rajasri |
| Posted: Tue Sep 19, 2006 3:38 am Post subject: fixpack |
|
|
Centurion
Joined: 11 Jun 2006
Posts: 114
|
Hi all for the support. I have fixed the problem. in mqsiprofile.cmd, when i typed java -version it was telling that there was no public jre version. when i compared the size of the jre folder with the peers, i noticed a vast diff in the size of the folder and also the number of files in bin folder. i just copied and pasted them into my directory and now every thing is working fine.
But one thing iam not clear is i have not seen any java_home variable when i typed "set" in mqsiprofile. and then as some one told, no changes shd be made to environment variables, why should my java_home variable point to brokers'jvm. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Sep 19, 2006 2:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Because that's where mqsiprofile points it to see:
| jefflowrey wrote: |
| fjb_saper wrote: |
| The JAVA_HOME env variable should be pointing to the broker's JVM. |
That would be set in mqsiprofile.cmd. rajasri should not have changed that file. |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
