| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP8075E: Error when creating ConfigurationManager |
« View previous topic :: View next topic » |
| Author |
Message
|
| roband |
 Posted: Fri Nov 12, 2010 3:15 am Post subject: BIP8075E: Error when creating ConfigurationManager |
 |
|
Newbie
Joined: 12 Nov 2010
Posts: 5
|
Hi,
I know it's a problem that's been discussed on here, but it appears the threads have either gone dead or a classpath fix solved the issue.
Here's the error I'm getting and the command I'm running;
Command:
mqsicreateconfigmgr BROKER1_CONFIG -i (myusername) -a (mypassword) -q QUEUE_MANAGER1
Error:
BIP8075E: A Java exception was caught from class 'ConfigurationData.initialize'.
The text is 'java.lang.ExceptionInInitializerError'.
A Java exception was caught via the JNI.
Check preceding messages for related errors and retry the operation. If the exce
ption still occurs, contact your IBM support center.
When searching for a solution, most results lead to an IBM support page about "BIP1002E At Configuration Manager Startup" - I've updated the classpath and also tried creating the cmd batch file within the common/profiles directory - neither of which have made a difference.
I get the same error if I run this command or attempt to create the default config from the broker toolkit
Version info:
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20080315 (SR7))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-2008031
5 (JIT enabled)
J9VM - 20080314_17962_lHdSMr
JIT - 20080130_0718ifx2_r8
GC - 200802_08)
JCL - 20080314
G:\Program Files\IBM\MQSI\6.1>mqsiservice -v
BIPv610 en GB
ucnv Console CCSID 850 dft ucnv CCSID 5348
ICUW ibm-5348_P100-1997 ICUA ibm-5348_P100-1997
BIP8996I: Version: 6102
BIP8997I: Product: WebSphere Message Brokers
BIP8998I: CMVC Level: S610-FP02 DH610-FP02
BIP8999I: Build Type: Production
Version 7 of MQ
DB version 8.1.7.445
Running all of this on Windows XP
Not sure quite what happened, I previously used this set up perfectly fine, played around with other stuff for a few months and I've started receiving this error. I've attempted removing everything and starting a-fresh, and still getting the same error at the same point! Any help would be appreciated
Last edited by roband on Mon Nov 15, 2010 1:09 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Nov 12, 2010 3:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I don't know where that java version is coming from. 6.1.0.2 doesn't use Java 1.6 AFAIK, only 1.5.
Are you sure you have fully and correctly applied mqsiprofile to the current shell?
Also, really. Apply 6.1.0.8. |
|
| Back to top |
|
|
| roband |
| Posted: Fri Nov 12, 2010 6:06 am Post subject: |
|
|
Newbie
Joined: 12 Nov 2010
Posts: 5
|
Hi Jeff, sorry - clever old me ran the java -version command in the wrong command window, and not the Message Broker Command Console;
Java version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20080315 (SR7))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-2008031
5 (JIT enabled)
J9VM - 20080314_17962_lHdSMr
JIT - 20080130_0718ifx2_r8
GC - 200802_08)
JCL - 20080314
It definitely appears to be correctly applying the mqsiprofile, I've even tried checking all the additional/required classpath/path jars/locations exist, so far nothing's missing |
|
| Back to top |
|
|
| roband |
| Posted: Mon Nov 15, 2010 1:10 am Post subject: |
|
|
Newbie
Joined: 12 Nov 2010
Posts: 5
|
| Updated original post to reflect the correct java version; still receiving the same errors, any other thoughts? |
|
| Back to top |
|
|
| roband |
| Posted: Tue Nov 16, 2010 3:16 am Post subject: |
|
|
Newbie
Joined: 12 Nov 2010
Posts: 5
|
Ran a service trace - and found the last line ran before it abended whilst creating a configmgr was as follows:
2010-11-16 10:37:20.176275 10160 { com.ibm.broker.config.ConfigurationData@1b5e1b5e.initialize BROKER_CONFIG BROKER_CONFIG , BROKER_CONFIG
2010-11-16 10:37:20.192869 10160 { com.ibm.broker.config.DBManager@31ea31ea.constructor BROKER_CONFIG BROKER_CONFIG , 'initData={ConfigManagerUserId=dptsar, ComponentName=BROKER_CONFIG, DataBaseName=, DataBasePassword=******, DataBaseUserId=dptsar, FilePath=G:\Program Files\IBM\MQSI\6.1, FileSeparator=/, JDBCConnectionName=db2, JDBCDriverName=COM.ibm.db2.jdbc.app.DB2Driver, NTSecurityDomainName=, PutApplicationName=null, QueueManagerName=QUEUE_MANAGER, UNSQueueManagerName=, SuppressMigration=null, WorkPath=C:\Documents and Settings\All Users\Application Data\IBM\MQSI}', BROKER_CONFIG
2010-11-16 10:37:20.380619 10160 { ImbCmdJava::expandJavaException
A working version (on a colleague's laptop) looks like...
2010-11-16 10:27:07.507936 2972 { com.ibm.broker.config.ConfigurationData@5c3c5c3c.initialize DELETEME DELETEME , DELETEME
2010-11-16 10:27:07.540953 2972 { com.ibm.broker.config.DBManager@744c744c.constructor DELETEME DELETEME , 'initData={ConfigManagerUserId=dpdvmm, ComponentName=DELETEME, DataBaseName=, DataBasePassword=******, DataBaseUserId=dpdvmm, FilePath=G:\Program Files\IBM\MQSI\6.1, FileSeparator=/, JDBCConnectionName=db2, JDBCDriverName=COM.ibm.db2.jdbc.app.DB2Driver, NTSecurityDomainName=, PutApplicationName=null, QueueManagerName=DELETEME, UNSQueueManagerName=, SuppressMigration=null, WorkPath=C:\Documents and Settings\All Users\Application Data\IBM\MQSI}', DELETEME
2010-11-16 10:27:18.824544 2972 { com.ibm.broker.config.DBManager@744c744c.setDatabaseAttributes DELETEME DELETEME , 'databaseType=DB2 CLOUDSCAPE', DELETEME
2010-11-16 10:27:18.824905 2972 com.ibm.broker.config.DBManager@744c744c.setDatabaseAttributes DELETEME DELETEME 'Database type: ' , 'type=DB2 CLOUDSCAPE', DELETEME
2010-11-16 10:27:18.825069 2972 } com.ibm.broker.config.DBManager@744c744c.setDatabaseAttributes DELETEME DELETEME , DELETEME
2010-11-16 10:27:18.825141 2972 } com.ibm.broker.config.DBManager@744c744c.constructor DELETEME DELETEME , DELETEME
2010-11-16 10:27:18.825260 2972 com.ibm.broker.config.ConfigurationData@5c3c5c3c.initialize DELETEME DELETEME 'returnCode is : ' , '0', DELETEME
2010-11-16 10:27:18.826164 2972 } com.ibm.broker.config.ConfigurationData@5c3c5c3c.initialize DELETEME DELETEME , DELETEME
Anyone make anything from this?
Thanks |
|
| Back to top |
|
|
| savfaire |
| Posted: Mon Feb 07, 2011 9:07 am Post subject: BIP8075E creating config mgr |
|
|
Newbie
Joined: 10 Jun 2003
Posts: 7
|
Did you ever find out what the problem was? I have a co-worker that is running into the exact same issue. We are running WMB 6.1. I was able to create a configuration manager and message broker without any problems. My co-worker, however, is getting the following error when he tries to either create the default configuration from the toolkit or if he tries to create the configuration manager and message broker within the command console:
BIP8075E: A Java exception was caught from class 'ConfigurationData.initialize'.
The text is 'java.lang.ExceptionInInitializerError'.
A Java exception was caught via the JNI.
Check preceding messages for related errors and retry the operation. If the exception still occurs, contact your IBM support center.
I am suspecting that it probably has something to do with either the classpath on his machine but wanted to see if you ever found the cause of your problem before I call IBM. |
|
| Back to top |
|
|
| roband |
| Posted: Tue Feb 08, 2011 2:22 am Post subject: |
|
|
Newbie
Joined: 12 Nov 2010
Posts: 5
|
Hi there, never found a solution - I suspect that I'll have to go ahead and get my laptop rebuilt and start from scratch, ended up having to use another computer, with no issues..
If IBM give you any solutions, please let me know |
|
| Back to top |
|
|
| savfaire |
| Posted: Tue Feb 08, 2011 8:59 am Post subject: Found the problem |
|
|
Newbie
Joined: 10 Jun 2003
Posts: 7
|
| We ended up figuring out the problem after a bunch of trial and error. Since I had no problems creating a configuration manager while my co-worker did, we had him mirror his classpath after mine. After doing that, he was able to successfully create a broker and configuration manager. We looked into the classpath differences and found that he had a jar file in his class path that was causing the issue. Unfortunately we do not know the exact cause of the issue other than a potential class resolution problem. Removing that problem jar file from the classpath fixed it for him. You may want to try the same. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
