| Author |
Message
|
| leo> |
 Posted: Thu Jan 17, 2008 11:24 pm Post subject: BIP8075E: error when creating config manager |
 |
|
Apprentice
Joined: 06 Oct 2004
Posts: 42
|
We are currently having WBIMB V5 and we just installed WBIMB 6.1 to a different location to run it concurrently with V5.
I had to upgrade DB2 from 8.1 to 9.1 as a part of this, and I am not sure what I did wrong, the V5 configmgr and broker database wont migrate successfully. I couldnt connect to those databases, so I decided to drop it, and recreate the db and configmgr again on V5.
I created configmgr db, and when I create the configmgr, I am getting this error:
| Quote: |
C:\>mqsicreateconfigmgr -i wmqiadmn -a wmqiadmn -q WINDEV01 -n MCMDB001 -u wmqiadmn -p wmqiadmn
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
Warning: JIT compiler "none" not found. Will use interpreter.
BIP8075E: A Java exception was caught from class 'ConfigurationData.initialize'. The text is 'java.lang.NoSuchMethodError: java.ne
t.URLDecoder: method decode(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String; not found'.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 cente
r.
|
JAVA_HOME is set, CLASSPATH contains db2java.zip, and all the MQ jars. Any idea? Please help.
Thanks
_________________
IBM Certified System Administrator - Websphere MQ V5.3 |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Fri Jan 18, 2008 5:24 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Looks like the JVM is not installed correctly.
Do you get the same error if you create the Config Manager from scratch (i.e. don't use the -n flag)? |
|
| Back to top |
|
|
| leo> |
| Posted: Fri Jan 18, 2008 7:02 am Post subject: |
|
|
Apprentice
Joined: 06 Oct 2004
Posts: 42
|
-n is a mandatory parameter for mqsicreateconfigmgr command right?
Is there other ways of creating configmgr?
What do I need to check to ensure JVM is fine..? I have all MQ jars in the CLASSPATH. Do I need to set any other jars in the classpath?
I also tried adding rt.jar from V5 jre\lib directory, as well as the one from
other JVM (one used by websphere adaptors).. both of them didnt work..
_________________
IBM Certified System Administrator - Websphere MQ V5.3 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 18, 2008 2:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I know of a java.lang.String
I don't know of Ljava.lang.String ... bad install media??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Sat Jan 19, 2008 4:16 pm Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
In V5 -n was a mandatory parameter, but since there is no Config Manager database in V6 and above, the flag should now only be used if you want to migrate an existing database - check the docs for more info.
fjb_saper - don't worry about the L in Ljava.lang.String; it's not relevant to this problem. The L is used when describing a method signature across the JNI... see http://java.sun.com/j2se/1.3/docs/guide/jni/spec/types.doc.html |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Jan 19, 2008 5:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think this is a problem with connecting WMB v5.0 with DB2 v9.
Which I'm pretty sure is an unsupported configuration, and was only needed because of the desire to co-exist WMB v6.1, and keep a local DB2 instance for both versions.
I think Db2 should be rolled back to v8 on the local machine, and a remote v9 put up for v6.1 broker to connect to.
Or the configmgr should be migrated entirely to v6.1. But I don't know that v5.0 Broker is going to be much happier with DB2 v9.x as it's Broker DB.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 19, 2008 11:09 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
With the ability in 6.1 of the configmgr to "acquire" the information on a broker is it even needed anymore to migrate a configmgr to 6.1?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jan 20, 2008 3:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't know if one can acquire/adopt back level brokers... It might only be possible to do with v6.1 brokers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jan 20, 2008 1:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
| I don't know if one can acquire/adopt back level brokers... It might only be possible to do with v6.1 brokers. |
According to the fact that the 6.1 toolkit does not allow you to deploy to back level brokers, I would have expected that the configmgr would be the last component you would migrate/create ? (Just before installing the 6.1 toolkit)...
IIRC the manual advises to use the 6.0 toolkit to deploy to forward 6.1 brokers... as long as your whole domain has not been migrated... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Jan 21, 2008 4:50 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| fjb_saper wrote: |
| jefflowrey wrote: |
| I don't know if one can acquire/adopt back level brokers... It might only be possible to do with v6.1 brokers. |
According to the fact that the 6.1 toolkit does not allow you to deploy to back level brokers, I would have expected that the configmgr would be the last component you would migrate/create ? (Just before installing the 6.1 toolkit)...
IIRC the manual advises to use the 6.0 toolkit to deploy to forward 6.1 brokers... as long as your whole domain has not been migrated... |
A few points that may help or hinder:
1) The V6.1 tools can deploy unchanged BARs to a V6.0 broker. As soon as a BAR is recompiled in the V6.1 tools, it can then only be deployed to a V6.1 broker.
2) A V(5.0, 6.0, 6.1) Config Manager can manage V(6.1, 6.0, 5.0) brokers. The V(5.0, 5.1, 6.0, V6.1) Admin Perspective can connect to V(5.0, 6.0, 6.1) Config Managers. In other words, there is full interop at the admin/CMP level, so long as you're not using new capability.
(N.B. I think this point means that you can migrate the CM whenever appropriate.)
3) It's often easiest to have a V6.1 domain (tools+CM+broker) logically separate from 6.0/5.0 domains; it helps prevent confusion. Though use the same hardware by all means, as multiple versions co-exist on the same machine quite nicely. |
|
| Back to top |
|
|
| rhe |
| Posted: Wed Feb 06, 2008 8:13 am Post subject: help |
|
|
Newbie
Joined: 06 Feb 2008
Posts: 1
|
Leo,
I have exactly same problem as yours, do you find solutions for that? |
|
| Back to top |
|
|
|
|
