| Author |
Message
|
| spazy |
 Posted: Fri Jun 12, 2009 6:43 am Post subject: Fixpack WMB 6.1.0.4 and JRE problem |
 |
|
Newbie
Joined: 02 Sep 2008
Posts: 8
|
Hello dear colleagues ,
i tried to install new fixpack for WMB on windows 2k3. Everything looks fine, but mqsiservice version check returns -> 
| Code: |
C:\Program Files\IBM\MQSI\6.1\bin>mqsiservice.exe -v
BIP8996I: Version: 6104
BIP8997I: Product: WebSphere Message Brokers
BIP7064S: 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. Th
ere may have been a problem with the way the product was installed, or something has subsequently affected the installat
ion.
This is an internal error and you should contact your IBM support center.
BIP8081E: An error occurred while processing the command.
|
I checked path and classpath, but i quess it fine.
I am sad, because i look forward to sftp node.  |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Jun 15, 2009 3:49 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Quote: |
When you try to start the Toolkit a "JVM terminated Exit Code = 1" error is displayed, or the javaw.exe process takes 100% of the CPU and stops.
The problem might be due to the -Xshareclasses:singleJVM, keep switch in the eclipse.ini file. This switch creates a cache that provides a means of sharing all loaded classes, and places no restrictions on the JVMs that are sharing the class data. If the cache becomes corrupted, no new JVMs are allowed to connect to the cache. Existing JVMs can continue to function, but cannot update the cache.
Solution:
To resolve the problem, delete the corrupted cache. The cache is rebuilt the next time the product is launched. To delete the cache:
1. Open a command prompt.
2. Navigate to Message Broker Toolkit Directory/jdk/jre/bin.
3. Enter the following command:
On Microsoft Windows:
javaw.exe -Xshareclasses:destroy
On Linux:
./javaw -Xshareclasses:destroy
The product will now start successfully.
|
I can't see any reference to SFTP in the release notes or readme.
Does it now exist (I haven't tried FP4 yet)?
It would be our main reason to upgrade (new bugs for old?). |
|
| Back to top |
|
|
| spazy |
| Posted: Mon Jun 15, 2009 5:52 am Post subject: |
|
|
Newbie
Joined: 02 Sep 2008
Posts: 8
|
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 15, 2009 6:35 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Can the toolkit 6.1.04 be used for development with runtime 6.1.03 (new sftp function excepted of course)?
Or would this run the risk of deploying BAR files that would not work? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 15, 2009 7:39 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I just opened a PMR asking if there is any particular order that the TK, CM and Broker need to be upgraded. They said it did not matter. We will be upgrading our CMs first, then the Brokers a couple of weeks later and finally all the TKs.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fazz |
| Posted: Thu Jul 16, 2009 6:19 am Post subject: |
|
|
Centurion
Joined: 20 Feb 2004
Posts: 144
Location: England
|
Hello,
I am having the same problem since installing fixpack 4.
I also cannot start the config mgr or broker services, they report the following error:
| Quote: |
( ConfigMgr ) Verification failed. Unable to verify Java level.
Unable to verify the installed Java level. This error is typically caused by Java not being installed, or a file permissions error.
Ensure Java has been correctly installed, by running the command java -version.
If Java has been correctly installed, see the preceding messages for further information about the cause of this failure, and the actions that you can take to resolve it. |
Did you manage to resolve the issue?
I am running broker on Windows 2003 Server SP1 64bit.
Thanks |
|
| Back to top |
|
|
| ovasquez |
| Posted: Fri Jul 17, 2009 10:49 pm Post subject: |
|
|
Centurion
Joined: 09 Dec 2005
Posts: 141
Location: Lima, Peru
|
| fazz wrote: |
Hello,
I am having the same problem since installing fixpack 4.
I also cannot start the config mgr or broker services, they report the following error:
| Quote: |
( ConfigMgr ) Verification failed. Unable to verify Java level.
Unable to verify the installed Java level. This error is typically caused by Java not being installed, or a file permissions error.
Ensure Java has been correctly installed, by running the command java -version.
If Java has been correctly installed, see the preceding messages for further information about the cause of this failure, and the actions that you can take to resolve it. |
Did you manage to resolve the issue?
I am running broker on Windows 2003 Server SP1 64bit.
Thanks |
Yes..i have same problem...first a install FIx 4 for TK is sucessful, but next day i install fix 4 for CM an BK same time..and isnot posibled start CM and BK..so i resintall 6.1.0.3....
Environment:
TK+CM+BK in Win XP professional SP2
_________________
Oscar Vásquez Flores |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Aug 25, 2009 11:41 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Just applied 6.1.04 on AIX without this problem.
Anyone else have issues with 6.1.04 runtime? |
|
| Back to top |
|
|
|
|
