ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JVM probelm after applying Fix pack to runtime environment

Post new topic  Reply to topic
 JVM probelm after applying Fix pack to runtime environment « View previous topic :: View next topic » 
Author Message
aditya.aggarwal
PostPosted: Fri Dec 04, 2009 3:16 am    Post subject: JVM probelm after applying Fix pack to runtime environment Reply with quote

Master

Joined: 13 Jan 2009
Posts: 252

Hi,

I have upgraded the Broker runtime environment from 6.1.0.3 to 6.1.0.5.

After upgrading i am getting the below error :

C:\Program Files\IBM\MQSI\6.1>mqsiservice -v
BIP8996I: Version: 6103
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. There 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.
An error has occurred while the command was running. The command has cleaned up
and terminated.
Use messages prior to this one to determine the cause of the error. Correct the
problem and retry the command. Check for some common problems :- Does the user
id have the correct authorities (for example a member of the mqbrkrs group)? Is
the broker database started and operating correctly? Is any operating system l
imit set too low to allow the command to run? Is the environment correctly set
up? Contact your IBM support center if you are unable to resolve the problem.


I checked the mqsi6_install.log file in home directory..and it shows that installation is successfully done:

(Dec 3, 2009 8:50:20 PM), mqsi.Setup, com.installshield.wizard.platform.win32.Win32PPKRegistryServiceImpl, dbg.registry, writing VPD to C:\WINDOWS\vpd.properties
(Dec 3, 2009 8:51:01 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, Checking status of install
(Dec 3, 2009 8:51:01 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, install not cancelled
(Dec 3, 2009 8:51:04 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, (Install status = 3)
(Dec 3, 2009 8:51:04 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windows XP" version="5.1" arch="x86"
(Dec 3, 2009 8:51:04 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Dec 3, 2009 8:51:09 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windows XP" version="5.1" arch="x86"
(Dec 3, 2009 8:51:09 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Dec 3, 2009 8:51:09 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windows XP" version="5.1" arch="x86"
(Dec 3, 2009 8:51:09 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Dec 3, 2009 8:51:15 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windows XP" version="5.1" arch="x86"
(Dec 3, 2009 8:51:15 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."
(Dec 3, 2009 8:51:49 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.actions.WriteToLogWizardAction, dbg,
BIP8622: Install of IBM WebSphere Message Broker 6.1 has finished successfully
(Dec 3, 2009 8:51:49 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, Checking status of install
(Dec 3, 2009 8:51:49 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, install not cancelled
(Dec 3, 2009 8:51:51 PM), mqsi.Setup, com.ibm.ismp.beans.wizard.conditions.WizardActionSuccessfulWizardBeanCondition, dbg, (Install status = 3)
(Dec 3, 2009 8:51:59 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Windows XP" version="5.1" arch="x86"
(Dec 3, 2009 8:51:59 PM), mqsi.Setup, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."

What may be the reason for this issue?


Cheers,
Aditya
Back to top
View user's profile Send private message
mqmatt
PostPosted: Fri Dec 04, 2009 3:32 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

What happens when you try and start a broker?
When you do this, the broker will perform a complete environment check and tell you in the system log if anything's wrong.
Back to top
View user's profile Send private message
aditya.aggarwal
PostPosted: Fri Dec 04, 2009 3:43 am    Post subject: Reply with quote

Master

Joined: 13 Jan 2009
Posts: 252

While Starting the Broker below error reported:

mqsistart ESQLBROKER
WebSphere MQ queue manager running.
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

in System logs i found this error repeatedly:

The description for Event ID ( 2080 ) in Source ( WebSphere Broker v6103 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ESQLBROKER, '$SYS_mqsi', 'Start', 60.
Back to top
View user's profile Send private message
AkankshA
PostPosted: Fri Dec 04, 2009 3:52 am    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore

it might be an installable and OS mismatch....

can u recheck....
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
student
PostPosted: Fri Dec 04, 2009 4:04 am    Post subject: Reply with quote

Apprentice

Joined: 17 Mar 2009
Posts: 31
Location: UK

Hi ,

Please check your registry entry, it should have entries of broker

Type regedit in run prompt
goto - HKEY_LOCAL_MACHINE - SOFTWARE -IBM- Message broker -- services--
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Dec 04, 2009 4:21 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Since you are on windows, please reboot.
Back to top
View user's profile Send private message
aditya.aggarwal
PostPosted: Fri Dec 04, 2009 4:25 am    Post subject: Reply with quote

Master

Joined: 13 Jan 2009
Posts: 252

Quote:

it might be an installable and OS mismatch....

can u recheck....


For Windows there is only one Fix pack..

6.1.0-WS-MB-WinIA32-FP0005.exe

and I have installed the same...

Quote:
Hi ,

Please check your registry entry, it should have entries of broker

Type regedit in run prompt
goto - HKEY_LOCAL_MACHINE - SOFTWARE -IBM- Message broker -- services--



Broker registry entries are present.

Quote:
Since you are on windows, please reboot.


it is already done..but we are facing the same issue...
Back to top
View user's profile Send private message
mqmatt
PostPosted: Fri Dec 04, 2009 4:30 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

The fact that the BIP message catalog can't be found (specifically, BIP2080 in the system log), does suggest an installation failure.
Make sure that you installed the fixpack with administrative privileges, and to a locally hosted filesystem.
Try reinstalling if you can. If the problem persists, raise a PMR.
Back to top
View user's profile Send private message
aditya.aggarwal
PostPosted: Fri Dec 04, 2009 5:14 am    Post subject: Reply with quote

Master

Joined: 13 Jan 2009
Posts: 252

yes i agree..but this is the last resort for me....
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JVM probelm after applying Fix pack to runtime environment
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.