| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 5 matches |
| Author |
Message |
 Topic: BIP8075E: Error when creating ConfigurationManager |
roband
Replies: 7
Views: 3529
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 08, 2011 2:22 am Subject: BIP8075E: Error when creating ConfigurationManager |
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 a ... |
| Topic: BIP8075E: Error when creating ConfigurationManager |
roband
Replies: 7
Views: 3529
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 16, 2010 3:16 am Subject: BIP8075E: Error when creating ConfigurationManager |
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.Configura ... |
| Topic: BIP8075E: Error when creating ConfigurationManager |
roband
Replies: 7
Views: 3529
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 15, 2010 1:10 am Subject: BIP8075E: Error when creating ConfigurationManager |
| Updated original post to reflect the correct java version; still receiving the same errors, any other thoughts? |
| Topic: BIP8075E: Error when creating ConfigurationManager |
roband
Replies: 7
Views: 3529
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Nov 12, 2010 6:06 am Subject: BIP8075E: Error when creating ConfigurationManager |
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 Runt ... |
| Topic: BIP8075E: Error when creating ConfigurationManager |
roband
Replies: 7
Views: 3529
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Nov 12, 2010 3:15 am Subject: BIP8075E: Error when creating ConfigurationManager |
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 ru ... |
|
|
|
