weblogic not starting

Hi Ranchers,

Our j2EE application is running live. I have added some functionalities and updated in production machine. web.xml is changed. One more application specific xml file also is changed apart from jsp files, css, js, proerpties files. After updating, i tried to start my weblogic server, but it just crashes before it starts up completely.

If anybody can throw light on it, I would appreciate.

Rgds,
Sankar

It is weblogic 8.1

"sankar sv",

There aren't many rules that you need to worry about here on the Ranch, but one that we take very seriously regards the use of proper names. Please take a look at the JavaRanch Naming Policy and adjust your display name to match it.

In particular, your display name must be a first and a last name separated by a space character, and must not be obviously fictitious.

Thanks!
bear
Forum Bartender

Check the server log.

w/o changing code, weblogic server started up in production...GOK :-)

But, problems did not end there.

####<19-Dec-2005 08:34:56 o'clock GST> <Error> <Deployer> <ae01qws010ema27> <emirates> <main> <<WLS Kernel>> <> <BEA-149206> <Failed to stage the component null of the application certificate.>
####<19-Dec-2005 08:34:56 o'clock GST> <Error> <Deployer> <ae01qws010ema27> <emirates> <main> <<WLS Kernel>> <> <BEA-149205> <Failed to initialize the application certificate due to error weblogic.management.DeploymentException: [Deployer:149206]Failed to stage the component null of the application certificate..
java.lang.Throwable: [Deployer:149206]Failed to stage the component null of the application certificate.
at weblogic.management.deploy.slave.SlaveDeployer.getApplicationInputStream(SlaveDeployer.java:1881)
at weblogic.management.deploy.slave.SlaveDeployer.access$1700(SlaveDeployer.java:116)
at weblogic.management.deploy.slave.SlaveDeployer$Application.restage(SlaveDeployer.java:2841)
at weblogic.management.deploy.slave.SlaveDeployer$StagingOrder.execute(SlaveDeployer.java:3379)
at weblogic.management.deploy.slave.SlaveDeployer$Application.stageFromOrder(SlaveDeployer.java:2799)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3019)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:984)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:341)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)

Greatly apperciated for any help.
Sankar

Originally posted by enperu sollamaatene:
w/o changing code, weblogic server started up in production...GOK :-)

But, problems did not end there.

####<19-Dec-2005 08:34:56 o'clock GST> <Error> <Deployer> <ae01qws010ema27> <emirates> <main> <<WLS Kernel>> <> <BEA-149206> <Failed to stage the component null of the application certificate.>
Sankar

possible reseon

1.you need to clean the deployed application before redeploying it.
2. make sure that WLS is deploying the application properly. (if you are using the ant task to deploy)

I also got the same error when I tried to deploy application using the ANT task. then after redeploying properly it works fine for me

Thanks,
Santosh

Thanks santosh for your reply.

Now, I am stuck in web of problems.. When my servlet calls sendredirect of a jsp file, it is throwing 500 error. It shows 883 also. See the below log.

10.152.242.27 - - [19/Dec/2005:09:04:34 +0400] "GET /rabsearch.jsp;jsessionid=Dm1fRFBkGkVKbBSLSyNhjJ2Q1Rt7y5jdn61dQ6fQ5hzqSYwf0wXc!-1650829779 HTTP/1.1" 500 883

What is the meaning of 883 within the context http 500 error?

Sankar

I dont know about the 883

here is the what 500 means( may be you also aware of this status code)
HTTP Status Code - 500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Hi Santosh,

Cracked down the problem.

rabsearch.jsp file is having a include and that file is missing in production. <%@include file="MYBBranding.jsp"%>. It created 500 error.

In development and testing machines, both (MYBBranding.jsp and rabBranding.jsp) files are available. So no error.

In production, rabBranding.jsp (latest file) is available but name is not changed in rabsearch.jsp.

Thanks for your support,
Regards,
Sankar

Feel relieved

Thats great you resolved it.