Server Hangs while compiling some EJB in Weblogic 6.1 SP5 on AIX 4.3.3

Question

Hi,
Iam not able to deploy a J2EE application in WebLogic 6.1 SP5 on an AIX 4.3.3
box.
CMP is being used and my EJBs are not being compiled( though there are no errors
thrown).
Iam using IBM DB2 ver 8.0 DB as client and server.
While compiling, the server Hangs, displaying the message "<Info> <Management>
<Configuration changes for domain saved to the repository.>"
Is there any configuration Issues with weblogic 6.1 SP5 and AIX 4.3.3?
Because the same EAR works in SP3.
Please help ASAP.
Thanks in advance.
Nagesh

Answer 1

The only thing to do again with "hangs" is to take thread dumps. As for why
things are going wrong...... I am at a loss other than some AIX weirdness.
Cheers
mbg
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
>
Hi Mark,
I tried it out ....I ran EJBC on all my EJB's and then tried to deploy myapplication.
Application got deployed and the server was up, but JSP's dosent getcompiled(
i.e when I want to run my application, my server hangs again).
I tried one more option.. I pointed my JAVAHOME in startweblogic.sh to anSP3
JDK .. and it worked!! Now with this JDK Iam able to deploy my entireapplication
( with out precompiled) also run through the application without anyproblems.
I then over wrote the existing JDK ( of SP5 ) with that of SP3 and thentried.
Which also works fentastically!!!
I can feel something fishy here ....
Any help in this regard is most welcome.
Thanks and Regards...
Nagesh
"Mark Griffith" <[email protected]> wrote:
Deshpande:
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
Thanks again.
For
Q1> How much time was between the two dumps?
A1> There was a minute gap B/w the two dumps. ( since it took so longto
write
the Core)
Q2> How long have you waited with no progress seeming to be made?
A1> Over a whole night. ( appx 14 hours).
Now I believe you would have figured out what the problem is.Not sure if this is a statement saying you think I have figured it out,
or a
statement saying you think I should have figured it out but I haven't.
Anyway... Did you try running ejbc on the "app" first?
Meanwhile also it would be great, if you would tell me the proceduresto
get support
form the BEA and AIX to solve the Issue.
http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/services/custome
r_support/contacts/
>>
I would suggest sending as much detail as possible, including zips of
the
thread dumps and pointers to this newsgroup conversation [email protected]
>>
I do however suggest you first try running ejbc.
Cheers
mbg
Thanks in advance.
R
Deshpande.
"Mark Griffith" <[email protected]> wrote:
Nagesh:
Wow, AXI outputs some interesting thread dumps. ;)
So the interesting thread (and the problem) is:
"main" (TID:0x300C41D8, sys_thread_t:0x30010A60, state:CW, native
ID:0x1)
prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:429)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:130)
at weblogic.utils.Executable.exec(Executable.java(Compiled Code))
at weblogic.utils.Executable.exec(Executable.java(Inlined CompiledCode))
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.j
a
v
a(Compiled Code))
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java(Inlin
e
d
Compiled Code))
at
weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java(Compiled
Code))
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java(InlinedCompiled
Code))
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java(Compiled
Code))
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java(CompiledCode))
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
at weblogic.j2ee.Application.addComponent(Application.java:176)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploymen
t
T
arget.java(Compiled Code))
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployme
n
t
Target.java:286)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments
D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deplo
y
m
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
l
..java(Compiled Code))
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
C
ompiled Code))
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
a
nImpl.java:374)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployment
s
ServerMBean_CachingStub.java:3015)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Ap
p
l
icationManager.java:376)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMana
g
e
r.java:164)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
p
l
..java(Compiled Code))
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
C
ompiled Code))
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
e
a
nImpl.java:374)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java(Compiled
Code))
at $Proxy48.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.star
t
ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1309)
at weblogic.management.Admin.finish(Admin.java:650)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:547)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:214)
at weblogic.Server.main(Server.java:35)
So the Server never gets out of the Main thread to run, because theEJBC
compilation is "stuck", ejbc is running because either the EJB being
deployed was previously deployed on a different version of WLS orejbc
had
never been run on those beans. Either there is a problem on the AIX
VM
where execing processes are not returning, OR the ejb that ejbc isrunning
on is huge and is taking a REALLY long time. How much time was
between
the
two dumps? How long have you waited with no progress seeming to bemade?
Depending on the answers to these questions it maybe that there isa
VM bug
and you will need to contact BEA support to see the procedure forworking
with AIX to resolve the issue.
You maybe able to work around the problem by running EJBC on the ejb
in
question prior to starting the server.
http://edocs.bea.com/wls/docs61/ejb/EJB_utilities.html#1075296
Cheers
mbg
"deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi, Mark,
Thanks for the early reply.
I have attached two consecutive dumps Zipped.
Pls look into the same and helpme out.
Thanks in advance.
Regards,
Nagesh
"Mark Griffith" <[email protected]> wrote:
When it hangs, you need to get thread dumps.
"kill -3 PID" is how this works on Solaris. Additionally if the
terminal/shell has focus that started the process you can do "CTRL
Break"
as
well. The thread dumps will go to std-out/err, so you'll have
to
redierect
std-out and err of the shell. (Make sure you don't nohup the
process
(if
AIX even supports that) since this prevents sigquits). When thehang
occurs
take a thread dump, wait 10 seconds and take another one, thenplease
zip
and attach the file in a post.
Cheers
mbg
"Deshpande" <[email protected]> wrote in message
news:[email protected]...
Hi,
Iam not able to deploy a J2EE application in WebLogic 6.1 SP5
on
an
AIX
4.3.3
box.
CMP is being used and my EJBs are not being compiled( though
there
are no
errors
thrown).
Iam using IBM DB2 ver 8.0 DB as client and server.
While compiling, the server Hangs, displaying the message "<Info><Management>
<Configuration changes for domain saved to the repository.>"
Is there any configuration Issues with weblogic 6.1 SP5 and AIX
4.3.3?
Because the same EAR works in SP3.
Please help ASAP.
Thanks in advance.
Nagesh