Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

FATAL ERROR in WAS 3.5.3. Help me, please!!

3 views
Skip to first unread message

Josefa Perez Melgarejo

unread,
May 5, 2001, 8:13:06 AM5/5/01
to
Hello:

My plataform is the following

AIX 4.3.3
Oracle 8i
WAS 3.5.2

I've just installed FixPack 3 without errors, but when I start up
WAS 3.5.3 I get the following error in tracefile:

[01.05.05 13:24:59:833 CEST] a46cb524 AdminServer A ADMS0002I:
Initializing WebSphere Administration server
[01.05.05 13:24:59:844 CEST] bdfe3522 DrAdminServer A SMTL0018I: DrAdmin
available on port 32,872
[01.05.05 13:25:08:475 CEST] a46cb524 AdminServer F Encountered an
exception in the main method com.ibm.ejs.s
m.exception.ActiveObjectInitException
at
com.ibm.ejs.sm.active.ActiveObject.startSuccess(ActiveObject.java:231)
at
com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:688)
at
com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.startContainers(AdminServer.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1048)

at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360)
----- Begin backtrace for subexception[0]
java.lang.VerifyError: (class: com/ibm/ejs/container/WrapperManager,
method: register signature: (Lcom/ibm/ejs/
container/EJSWrapper;Z)V) Incompatible argument to function
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.startContainers(AdminServer.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1048)

at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360)
FATAL Encountered an exception in the main method {0}
com.ibm.ejs.sm.exception.ActiveObjectInitException
at
com.ibm.ejs.sm.active.ActiveObject.startSuccess(ActiveObject.java:231)
at
com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:688)
at
com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.startContainers(AdminServer.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1048)

at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360)
----- Begin backtrace for subexception[0]
java.lang.VerifyError: (class: com/ibm/ejs/container/WrapperManager,
method: register signature: (Lcom/ibm/ejs/
container/EJSWrapper;Z)V) Incompatible argument to function
at java.lang.reflect.Method.invoke(Native Method)
at
com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.startContainers(AdminServer.java(Compiled
Code))
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1048)

at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360)

java.lang.Throwable
at
com.ibm.ejs.ras.CBuffLogger.fatalEvent(CBuffLogger.java(Compiled Code))
at com.ibm.ejs.ras.Tr.fireTraceEvent(Tr.java(Compiled Code))
at com.ibm.ejs.ras.Tr.fatal(Tr.java:685)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:372)


Could you help me, please ?
Thanks.


Mattias

unread,
May 5, 2001, 4:37:28 PM5/5/01
to
Check if you have any e-fixes deployed for your 3.5.2 installation. This is
done by checking your admin.config for "strange things" at the start of your
classpath. I've had similar problems when applying 3.5.3 without removing
e-fixes for previous versions.

/Mattias

"Josefa Perez Melgarejo" <jpme...@um.es> wrote in message
news:3AF3EE52...@um.es...

Josefa Perez Melgarejo

unread,
May 8, 2001, 12:13:07 PM5/8/01
to

Hello Mattias:.

I have removed one e-fix for leak memory from admin.config. After that I have
re-installed fixpack 3, and it has started up correctly.

Thank you, very much.
Bye.

0 new messages