Can't start WLS7 console after changing configuration

Question

Hi,
Do you have similar situation using WebLogic v7 ?
We can’t start our weblogic server after changing JMS configuration
a bit. Our consultant and I discussed about the solution - one of
them was to re-install weblogic domain. However, this method is not
good for production since all applications will have to be re-installed
again although this WLS is for internal testing.
Using your production mind, what is the better approach while you can't
even start weblogic console after an incomplete configuration.
Consultant's description:
"Our web application needs to configure WebLogic 7.0 JMS service via
wls console. After I did configure a new Connection Factory and a
Destination Keys (actually I should configure a new JMS server and
queue here), the WLS couldn’t reboot so that there is no way to logon
console to modify JMS configuration."
Thanks,
Alex Lin

Answer 1

If WLS through the console is creating an unbootable config.xml this is a
bug.
When you start WLS it makes a copy of its bootable configuration by renaming
config.xml to config.xml.booted. If this corruption occurs as you not with
the console, then you have to back up to config.xml.booted and start over.
You should open a case with support describing:
a) the exact version of wls
b) copy of "bad xml"
c) the exact steps you took to cause the problem
To work around the problem I would try following the exact steps listed
here:
http://edocs.bea.com/wls/docs70/ConsoleHelp/jms.html
Cheers
mbg
"Alex Lin" <[email protected]> wrote in message
news:[email protected]..
Hi,
Do you have similar situation using WebLogic v7 ?
We can't start our weblogic server after changing JMS configuration
a bit. Our consultant and I discussed about the solution - one of
them was to re-install weblogic domain. However, this method is not
good for production since all applications will have to be re-installed
again although this WLS is for internal testing.
Using your production mind, what is the better approach while you can't
even start weblogic console after an incomplete configuration.
Consultant's description:
"Our web application needs to configure WebLogic 7.0 JMS service via
wls console. After I did configure a new Connection Factory and a
Destination Keys (actually I should configure a new JMS server and
queue here), the WLS couldn't reboot so that there is no way to logon
console to modify JMS configuration."
Thanks,
Alex Lin