Weblogic server 5.1 startup error
I am using weblogic 5.1 on Solaris 8 (intel) for testing
when I start up the server, the following error prompt out
java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Error.<init>(Error.java:50)
at java.lang.LinkageError.<init>(LinkageError.java:43)
at
java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:42)
at java.lang.ClassLoader.loadLibrary(Compiled Code)
at java.lang.Runtime.loadLibrary0(Runtime.java:473)
at java.lang.System.loadLibrary(Compiled Code)
at COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(Compiled
Code)
at
COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
at COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(Compiled Code)
at weblogic.security.RSA.performOPJSafe(Compiled Code)
at weblogic.security.RSA.performOp(RSA.java:104)
at weblogic.security.RSApkcs1.decrypt(Compiled Code)
at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
at weblogic.security.X509.verifySignature(X509.java:223)
at
weblogic.t3.srvr.SSLListenThread.insertIntoCAChain(SSLListenThread.java:192)
at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Compiled Code)
at weblogic.Server.main(Server.java:58)
The java.library.path is
/usr/java/bin/../jre/bin/../lib/i386:/opt/weblogic/lib/solaris/oci815_8:/opt
/weblogic/lib/solaris:/usr/lib
and i am using JSK 1.2.2_07a
Please help
Fannie
That's JVM crash, which is not supposed to happen ;-) You can try to search
www.javasoft.com for answers, but it looks like Intel Solaris is not terribly
popular or supported. Did you try to run WebLogic on Linux instead ?
Fannie <[email protected]> wrote:
After I add the command to startWebLogic.sh, the server can start up
properly.
When I try to test the jsp page through the browser
The following error message prompt and the server shutdown
Please help!
Fannie
SIGSEGV 11 segmentation violation
si_signo [11]: SEGV
si_errno [0]:
si_code [1]: SEGV_MAPERR [addr: 0x2]
stackpointer=D639E440
"SSLListenThread" (TID:0x91a7d28, sys_thread_t:0x91a7c70, state:R, thread_t:
t@30, threadID:0xd5f50d74, stack_bottom:0xd5f51000, stack_size:0x20000)
prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
[4] java.net.ServerSocket.accept(ServerSocket.java:223)
[5]
weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
:121)
[6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
[7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"ListenThread" (TID:0x9171528, sys_thread_t:0x9171470, state:R, thread_t:
t@29, threadID:0xd5f80d74, stack_bottom:0xd5f81000, stack_size:0x20000)
prio=5
[1] java.net.PlainSocketImpl.socketAccept(Native Method)
[2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:413)
[3] java.net.ServerSocket.implAccept(ServerSocket.java:241)
[4] java.net.ServerSocket.accept(ServerSocket.java:223)
[5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
"ExecuteThread-14" (TID:0x867b8e8, sys_thread_t:0x867b830, state:CW,
thread_t: t@24, threadID:0xd6320d74, stack_bottom:0xd6321000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-13" (TID:0x86810e8, sys_thread_t:0x8681030, state:CW,
thread_t: t@23, threadID:0xd6370d74, stack_bottom:0xd6371000,
stack_size:0x20000) prio=5
[1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
[2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:177)
[3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
[4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-12" (TID:0x872cd20, sys_thread_t:0x872cc68, state:R,
thread_t: t@22, threadID:0xd63a0d74, stack_bottom:0xd63a1000,
stack_size:0x20000) prio=5 current thread
[1] weblogic.servlet.jsp.JspLexer.mPAGE_DIRECTIVE(JspLexer.java:3344)
[2] weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3174)
[3] weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1636)
[4] weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1477)
[5] weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1356)
[6] weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:786)
[7] weblogic.servlet.jsp.JspParser.doit(JspParser.java:57)
[8] weblogic.servlet.jsp.JspParser.parse(JspParser.java:109)
[9] weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
[10] weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:235)
[11] weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:198)
[12] weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:174)
[13]
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:16
4)
[14]
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:99)
[15]
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:123)
[16]
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:742)
[17]
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
l.java:686)
[18]
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
Manager.java:247)
[19]
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
[20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
[21] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-11" (TID:0x86c80e8, sys_thread_t:0x86c8030, state:CW,
thread_t: t@21, threadID:0xd63f0d74, stack_bottom:0xd63f1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-10" (TID:0x8745218, sys_thread_t:0x8745160, state:CW,
thread_t: t@20, threadID:0xd6fb0d74, stack_bottom:0xd6fb1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-9" (TID:0x867bce8, sys_thread_t:0x867bc30, state:CW,
thread_t: t@19, threadID:0xd6ff0d74, stack_bottom:0xd6ff1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-8" (TID:0x8742098, sys_thread_t:0x8741fe0, state:CW,
thread_t: t@18, threadID:0xd7920d74, stack_bottom:0xd7921000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-7" (TID:0x8740ed8, sys_thread_t:0x8740e20, state:CW,
thread_t: t@17, threadID:0xd7970d74, stack_bottom:0xd7971000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-6" (TID:0x86f40e8, sys_thread_t:0x86f4030, state:CW,
thread_t: t@16, threadID:0xd79a0d74, stack_bottom:0xd79a1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-5" (TID:0x873dd58, sys_thread_t:0x873dca0, state:CW,
thread_t: t@15, threadID:0xd79e0d74, stack_bottom:0xd79e1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-4" (TID:0x86ff4e8, sys_thread_t:0x86ff430, state:CW,
thread_t: t@14, threadID:0xd86b0d74, stack_bottom:0xd86b1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-3" (TID:0x86ffce8, sys_thread_t:0x86ffc30, state:CW,
thread_t: t@13, threadID:0xd8700d74, stack_bottom:0xd8701000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-2" (TID:0x87134e8, sys_thread_t:0x8713430, state:CW,
thread_t: t@12, threadID:0xd8730d74, stack_bottom:0xd8731000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-1" (TID:0x8739c70, sys_thread_t:0x8739bb8, state:CW,
thread_t: t@11, threadID:0xd8760d74, stack_bottom:0xd8761000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"ExecuteThread-0" (TID:0x8739a68, sys_thread_t:0x87399b0, state:CW,
thread_t: t@10, threadID:0xd8790d74, stack_bottom:0xd8791000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:88)
[3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:96)
"TimeEventGenerator" (TID:0x869a220, sys_thread_t:0x869a168, state:CW,
thread_t: t@9, threadID:0xd87c0d74, stack_bottom:0xd87c1000,
stack_size:0x20000) prio=5
[1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:249)
[2]
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:131)
[3] java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" (TID:0x86e8218, sys_thread_t:0x86e8160, state:CW,
thread_t: t@8, threadID:0xd87f0d74, stack_bottom:0xd87f1000,
stack_size:0x20000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2]
weblogic.security.SpinnerThread.stopSpinning(SpinnerRandomBitsSource.java:10
2)
[3] weblogic.security.SpinnerThread.run(SpinnerRandomBitsSource.java:116)
Exiting Thread (sys_thread_t:0xdfb7c29c) : no stack
"Finalizer" (TID:0x81e3940, sys_thread_t:0x81e3888, state:CW, thread_t: t@6,
threadID:0xdf4e0d74, stack_bottom:0xdf4e1000, stack_size:0x20000) prio=8
[1] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:146)
[2] java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:168)
[3]
java.lang.ref.Finalizer$FinalizerWorker$FinalizerThread.run(Finalizer.java:1
24)
"Reference Handler" (TID:0x81da690, sys_thread_t:0x81da5d8, state:CW,
thread_t: t@5, threadID:0xdf510d74, stack_bottom:0xdf511000,
stack_size:0x20000) prio=10
[1] java.lang.Object.wait(Object.java:424)
[2] java.lang.ref.Reference$ReferenceHandler.run(Reference.java:130)
"Signal dispatcher" (TID:0x81a0ea8, sys_thread_t:0x81a0df0, state:MW,
thread_t: t@4, threadID:0xdf670d74, stack_bottom:0xdf671000,
stack_size:0x20000) prio=10
"main" (TID:0x8061728, sys_thread_t:0x8061670, state:CW, thread_t: t@1,
threadID:0x804c178, stack_bottom:0x8048000, stack_size:0x848000) prio=5
[1] java.lang.Object.wait(Object.java:424)
[2] weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1784)
[3] java.lang.reflect.Method.invoke(Native Method)
[4] weblogic.Server.startServerDynamically(Server.java:148)
[5] weblogic.Server.main(Server.java:66)
[6] weblogic.Server.main(Server.java:58)
"Dimitri Rakitine" <[email protected]> ¼¶¼g©ó¶l¥ó
news:[email protected]...
I do not think there are shared libs for WebLogic on Solaris/Intel.
You can try disabling native SSL by adding this to WebLogic startup
command line: -Dweblogic.security.SSL.useJava=true
Fannie <[email protected]> wrote:
I am using weblogic 5.1 on Solaris 8 (intel) for testing
when I start up the server, the following error prompt out
java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Error.<init>(Error.java:50)
at java.lang.LinkageError.<init>(LinkageError.java:43)
at
java.lang.UnsatisfiedLinkError.<init>(UnsatisfiedLinkError.java:42)
at java.lang.ClassLoader.loadLibrary(Compiled Code)
at java.lang.Runtime.loadLibrary0(Runtime.java:473)
at java.lang.System.loadLibrary(Compiled Code)
at COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(Compiled
Code)
at
COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
at COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(CompiledCode)
at weblogic.security.RSA.performOPJSafe(Compiled Code)
at weblogic.security.RSA.performOp(RSA.java:104)
at weblogic.security.RSApkcs1.decrypt(Compiled Code)
atweblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
at weblogic.security.X509.verifySignature(X509.java:223)
at
weblogic.t3.srvr.SSLListenThread.insertIntoCAChain(SSLListenThread.java:192)
at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
at weblogic.t3.srvr.SSLListenThread.<init>(Compiled Code)
at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:825)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Compiled Code)
at weblogic.Server.main(Server.java:58)
The java.library.path is
/usr/java/bin/../jre/bin/../lib/i386:/opt/weblogic/lib/solaris/oci815_8:/opt
/weblogic/lib/solaris:/usr/lib
and i am using JSK 1.2.2_07a
Please help
Fannie--
Dimitri
Dimitri
Similar Messages
-
Weblogic Server 2008 Service Startup Error
Hello
When setting up weblogic on server 2008 R2, I can start weblogic using the startWeblogic.cmd file manually, but when configuring to run as a service, I am getting the below error and the service does not start. Do you know what could be causing this?
####<Jun 13, 2012 10:48:02 AM EDT> <Info> <JDBC> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598882511> <BEA-001155> <The following exception has occurred:
weblogic.common.ResourceException: Unknown Data Source EPMSystemRegistry-rac0
at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownConnectionPool(ConnectionPoolManager.java:563)
at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:535)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:295)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Jun 13, 2012 10:48:02 AM EDT> <Error> <Deployer> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598882527> <BEA-149205> <Failed to initialize the application 'EPMSystemRegistry-rac0' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: weblogic.common.resourcepool.ResourceSystemException: Could not create pool connection. The DBMS driver exception was: PermGen space
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:388)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:236)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1154)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:154)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:454)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:372)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:255)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Jun 13, 2012 10:48:02 AM EDT> <Info> <WorkManager> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598882527> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "EPMSystemRegistry-rac1">
####<Jun 13, 2012 10:48:14 AM EDT> <Error> <Deployer> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598894524> <BEA-149205> <Failed to initialize the application 'EPMSystemRegistry-rac1' due to error weblogic.management.DeploymentException: Unexpected error encountered.
weblogic.management.DeploymentException: Unexpected error encountered
at weblogic.deploy.internal.targetserver.AppContainerInvoker.getOrCreateDeploymentException(AppContainerInvoker.java:299)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:65)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.OutOfMemoryError: PermGen space
>
####<Jun 13, 2012 10:48:15 AM EDT> <Info> <WorkManager> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598895148> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bip_datasource-rac0">
####<Jun 13, 2012 10:48:31 AM EDT> <Info> <JDBC> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598911871> <BEA-001177> <Creating Connection Pool named bip_datasource-rac0, URL = jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=)(INSTANCE_NAME=))), Properties = user=BIP_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
####<Jun 13, 2012 10:48:32 AM EDT> <Info> <Common> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598912495> <BEA-000626> <Free resources in pool "bip_datasource-rac0" will be tested every "300" seconds.>
####<Jun 13, 2012 10:48:34 AM EDT> <Info> <JDBC> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598914382> <BEA-001508> <Destroying Connection Pool bip_datasource-rac0.>
####<Jun 13, 2012 10:48:34 AM EDT> <Info> <JDBC> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598914382> <BEA-001155> <The following exception has occurred:
weblogic.common.ResourceException: Unknown Data Source bip_datasource-rac0
at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownConnectionPool(ConnectionPoolManager.java:563)
at weblogic.jdbc.common.internal.ConnectionPoolManager.shutdownAndDestroyPool(ConnectionPoolManager.java:535)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:295)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Jun 13, 2012 10:48:37 AM EDT> <Error> <Deployer> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598917518> <BEA-149205> <Failed to initialize the application 'bip_datasource-rac0' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: weblogic.common.resourcepool.ResourceSystemException: Could not create pool connection. The DBMS driver exception was: (class: oracle/jdbc/OracleConnectionWrapper, method: proxyFor signature: (Ljava/lang/Object;Ljava/lang/Class;)Ljava/lang/Object;) Illegal type in constant pool
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:388)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:236)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1154)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:154)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:454)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:372)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:255)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Jun 13, 2012 10:48:38 AM EDT> <Info> <WorkManager> <bmiorabip1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1339598918750> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bip_datasource-rac1">
Thanks
NickHi Nick,
Open the register editor and look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<your beasvc service>\Parameters
Look what is in CmdLine, those are the actual parameters that the service's using, look for all -X arguments.
I have this on my service here:
-Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m
Your problem is probably on the -XX:PermSize part...
Modify your installSvc.cmd script so you can have the right parameters for the service, you can also try and call setDomainEnv.cmd from inside installSvc.cmd then you will guarantee that the arguments are the same for startWeblogic.cmd and the service.
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question. If you think this is helpful, please consider giving points -
Weblogic server failed to start errors BEA-000362 & BEA-000365
Hi Friends,
I'm trying to start weblogic server after starting admin server.I'm getting the below error after
running the command:
$ ./startManagedWebLogic.sh
<Jul 29, 2011 10:09:54 AM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Jul 29, 2011 10:09:55 AM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Jul 29, 2011 10:09:57 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.1.3-11-141760-1.6.0_24-20110301-1430-linux-ia32 from Oracle Corporation>
<Jul 29, 2011 10:09:58 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Jul 29, 2011 10:09:58 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141247]The configuration directory /Middleware/SOASuite11gR1/wlserver_10.3/common/bin/config does not exist and the admin server is not available.
at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:200)
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:115)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:42)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:882)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:572)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
>
<Jul 29, 2011 10:09:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jul 29, 2011 10:09:58 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jul 29, 2011 10:09:58 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Do you have any idea how to resolve this error and start weblogic server succesfuly.
Best regards,
Edited by: user13311731 on Jul 28, 2011 10:45 PMHi,
Try starting the managed server with parameters:
./startManagedWebLogic.sh myManagedServerName http://serverName:7001
Does that make a difference?
Regards Peter -
Weblogic Portal 9.2 Startup Error - Linux
Hi all, Thanks in advance for help in resolving this critical situation.
Installed is Weblogic Portal 9.2 on a Ubuntu [Debian] Linux workstation. When I create a portal environment using default Configuration Wizard settings, ./startWeblogic.sh executes and I am able to reach the cosole without problems.
As soon as I try to customize the configuration using Oracle drivers and corresponding username/password, I see an alert that reads:
<b>This domain is configured to use the SQL authenticator security provider. You must load database tables in the "Run Database Scripts" panel or load the tables manually after completing the wizard using the SQL file located at ~/bea920/user_projects/domains/pDomain/security/SQLAuthenticator.sql</b>
I click 'OK'. And 'Done'.
When I attempt to start Weblogic, it fails with the following stacktraces:
<b>
JAVA Memory arguments: -Xms256m -Xmx768m
WLS Start Mode=Development
CLASSPATH=:/home/toszter/bea920/patch_weblogic920/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/toszter/bea920/jrockit90_150_04/lib/tools.jar:/home/toszter/bea920/weblogic92/server/lib/weblogic_sp.jar:/home/toszter/bea920/weblogic92/server/lib/weblogic.jar:/home/toszter/bea920/weblogic92/server/lib/webservices.jar::/home/toszter/bea920/weblogic92/common/eval/pointbase/lib/pbclient51.jar:/home/toszter/bea920/weblogic92/server/lib/xqrl.jar:/home/toszter/bea920/weblogic92/server/lib/xquery.jar:/home/toszter/bea920/weblogic92/server/lib/binxml.jar:
PATH=/home/toszter/bea920/weblogic92/server/bin:/home/toszter/bea920/jrockit90_150_04/jre/bin:/home/toszter/bea920/jrockit90_150_04/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
Cleaning up license and uid files
Starting linux-intel/IDOLserver/DiSH/AutonomyDiSH.exe
Autonomy engine started.
Listening for transport dt_socket at address: 8453
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
BEA JRockit(R) (build R26.0.0-189_CR269406-59389-1.5.0_04-20060322-1126-linux-ia32, )
Starting WLS with line:
/home/toszter/bea920/jrockit90_150_04/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx768m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/home/toszter/bea920/weblogic92 -Dwls.home=/home/toszter/bea920/weblogic92/server -Dwli.home=/home/toszter/bea920/weblogic92/integration -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.http.descriptor.merge=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/home/toszter/bea920/patch_weblogic920/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/toszter/bea920/weblogic92/server/lib/weblogic.policy weblogic.Server
Listening for transport dt_socket at address: 8453
<Sep 26, 2006 10:37:30 AM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/home/toszter/bea920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/home/toszter/bea920/weblogic92/platform/lib/p13n/p13n_common.jar:/home/toszter/bea920/weblogic92/platform/lib/p13n/p13n_system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/commerce_system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/content_system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/groupspace_system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/netuix_common.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/netuix_system-full.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/netuix_system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/nf-jspcmods.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/nf-system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/wlp-schemas.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/wps_system.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/wsrp-client.jar:/home/toszter/bea920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<Sep 26, 2006 10:37:32 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R26.0.0-189_CR269406-59389-1.5.0_04-20060322-1126-linux-ia32 from BEA Systems, Inc.>
<Sep 26, 2006 10:37:33 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 2006 783464 >
<Sep 26, 2006 10:37:36 AM EDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:system
Enter password to boot WebLogic server:
<Sep 26, 2006 10:37:48 AM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /home/toszter/bea920/license.bea>
<Sep 26, 2006 10:37:48 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Sep 26, 2006 10:37:48 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Sep 26, 2006 10:37:48 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /home/toszter/bea920/user_projects/domains/pDomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
<Sep 26, 2006 10:37:52 AM EDT> <Error> <com.bea.weblogic.kernel> <000000> <[Security:090737]An exception occured while getting connection to validate the configuration settings
java.sql.SQLException: [Security:090735]The DBMS connection was not usable
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.getManageableConnection(DBMSSQLAuthenticatorDelegateImpl.java:857)
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.validateConfiguration(DBMSSQLAuthenticatorDelegateImpl.java:163)
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.<init>(DBMSSQLAuthenticatorDelegateImpl.java:89)
at weblogic.security.providers.authentication.DBMSAuthenticatorDelegateImpl.getInstance(DBMSAuthenticatorDelegateImpl.java:445)
at weblogic.security.providers.authentication.DBMSSQLAuthenticationProviderImpl.initialize(DBMSSQLAuthenticationProviderImpl.java:52)
Truncated. see log file for complete stacktrace
>
<Sep 26, 2006 10:37:53 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 26, 2006 10:37:53 AM EDT> <Error> <com.bea.weblogic.kernel> <000000> <[Security:090735]The DBMS connection was not usable>
<Sep 26, 2006 10:37:53 AM EDT> <Critical> <Security> <BEA-090403> <Authentication for user system denied>
<Sep 26, 2006 10:37:53 AM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user system denied
weblogic.security.SecurityInitializationException: Authentication for user system denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:947)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:849)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Sep 26, 2006 10:37:53 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 26, 2006 10:37:53 AM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 26, 2006 10:37:53 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Autonomy engine processes stopped
</b>
Here is what i have tried:
1. altered the username and password in boot.properties
2. deleted boot.properties and manually entered the username and password at WLS startup [as seen in the stacktrace].
3. created a default-settings portal environment that started weblogic, then used the console to chenge the settings to my customized values. Restarted the server and it failed with the same stacktraces.
Please please help. Our team has exhausted its knowledge of trouble shooting this situation. This forum is my next to last result.
Thanks again.
BartoszI too was facing this problem initially but on windows machine. This problem occurs because p13nDataSource is not configured and its still pointing to the POINTBASE data base. Point it to Oracle database and then test the connection. Once the Connection Test is sucessful go to Run Database Script. Select the correct version of Oracle i.e. 8i, 9i or 10g. Then select on DataSource from in the top left corner. Only two DataSource needs to be configured. cgDataSource-nonXA and p13nDataSource.Select these Data Source one after another and Run the scripts once this is done u can configure the WLI Domain.
This is done once configuring the WLI Domain.
I would post the corrective measure for the Domain which has been already created. If the issue is blocking u can create a new domain:-) -
Weblogic server 10.3.5 error during SSL handshake
Please some one help to figure the issue with following logs.
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 33092690>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 33095418>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <33092490 SSL Version data invalid>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Connection to SSL port from Sa-PC - 150.1.104.124 appears to be either unknown SSL version or maybe is plaintext>
<16-Jan-2013 18:40:40 o'clock GMT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer Sa-PC - 150.1.104.124 during SSL handshake.>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 70
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33092490>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33092490>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 33092690>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <33095215 SSL Version data invalid>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <Connection to SSL port from Sa-PC - 150.1.104.124 appears to be either unknown SSL version or maybe is plaintext>
<16-Jan-2013 18:40:40 o'clock GMT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer Sa-PC - 150.1.104.124 during SSL handshake.>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 70
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:130)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33095215>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <close(): 33095215>
<16-Jan-2013 18:40:40 o'clock GMT> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 33095418>
I just created domain with http and https ports. I installed an web app. When I am trying to access the app from browser through https the above error is occurring.
Please somebody help me.
Thanks in advance.
SKThis message indicates that the SSL connection is closed successfully. It is a warning message and normal to see in the logs when you enable the SSL debug flags. This is an expected behavior. If you see alerts when SSL debug is NOT ENABLED then it is a real alert and we need to take care of those issues. Also, it is not a real alert, it is a caught and handled exception from the certicom code which is not harmful and should be ignored, just because you have enabled the SSL debug flag. Once you turn it off, you won't see it in the logs.
Edited by: sharmela on Jan 22, 2013 4:55 AM -
WebLogic Server 10.0 MP1: Error in resource adapter deployment
When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
An error occurred during activation of changes, please see the log for details.
weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
java.util.logging.LoggingPermission.(java.lang.String)
The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
permission javax.management.MBeanTrustPermission "register";
permission java.util.logging.LoggingPermission "control";
When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
For me this seems to be a bug in WebLogic 10.0MP1.
Best,
ManfredRe: Installation error: Weblogic Server 10.0 MP2
-
Oracle Weblogic Server 10.3 startup stuck at 84% in Eclipse
Hi,
I am trying to start my Oracle Weblogic Server 10.3 in the Eclipse environment and the status bar freezes after progressing upto 84%.
Although the server is the RUNNING mode and I can login to the Admin console, I cannot auto-deploy or debug my apps in Eclipse because
it is waiting for the startup task to finish (or reach 100%).
I get following message after it times out.
"Server Oracle WebLogic Server v10.3 at localhost was unable to start within 480 seconds. If the server requires more time, try increasing the timeout in the server editor."
Any help to fix this issue will be very much appreciated.
Regards,
Amitoj.
Edited by: Amitoj on Apr 16, 2009 5:03 AMHi Ram,
I have checked everything.
There is nothing else in the progress view
Only the following message in the .log file over and over again
!ENTRY oracle.eclipse.tools.weblogic 4 4000 2009-04-16 14:11:12.452
!MESSAGE The server cannot be launched within timeout.
!ENTRY org.eclipse.wst.server.core 4 0 2009-04-16 14:11:13.872
!MESSAGE Server Oracle WebLogic Server v10.3 at localhost was unable to start within 480 seconds. If the server requires more time, try increasing the timeout in the server editor.
!ENTRY oracle.eclipse.tools.weblogic 4 4000 2009-04-16 16:10:02.827
!MESSAGE The user action is cancelled when the server is starting. The server cannot be stopped now. Please wait until the server is started and then stop it.
Tried restarting the eclipse and the machine. Killed all eclipse and jave processes in the task manager.
Downloaded a new copy eclipse, installed Weblogic server from scratch and created a brand new workspace.
Still I get the same problem.
I have exhausted every other option and now I am going to the extreme of rebuilding my whole PC again.
Regards,
Amitoj. -
I can't install weblogic server 10.3 found error
I have install to 65% and found error.
i want to know why i can't install weblogic server 10.3 (may be error was create by jdk or anything else Please tell me! )
and how many problem that can happen when install weblogic server 10.3
ps. - OS that i install is windowsXP sp2Without giving us any details about what error you got, or any circumstances of your environment (just the OS isn't enough), there is no way anyone could give you any help.
-
WebLogic Server 5.1 giving errors of code 500
Hi,
We have a system consisting of WebLogic Server 5.1 running on Sparc Solaris and
JDK 1.2.2 that is going to go into production soon. It houses JSPs and some
servlets (some of the servlets are JMS clients). The EJBs are kept on another
Sparc Solaris machine with the same version of WebLogic Server and JDK.
So far, the EJBs are running fine. However, it is noticed that after running for
one or two days, the instance of WebLogic Server that houses JSPs would give
the HTTP error code of 500 whenever it was contacted through a browser. The JMS
clients in the instance appeared to have stopped, as they did not print out
texts that were supposed to be shown whenver a message is received. The error
code of 500 was given for both JSP and HTML accesses. The system would not
recover from that condition even if it was left running for a few more hours.
Attaching the WebLogic Server Console to the instance of WebLogic Server
concerned did not reveal any possible cause, and the console appeared to
function correctly by providing information on system threads and JSP names
etc. weblogic.log, access.log and the console output (the messages written by
WebLogic Server to the terminal where it was started) did not reveal anything
unusual.
Wondering if anyone has encountered the same problem. Will appreciate any
help.
Thanks in advance.
Hann Wei
Hann
Before upgrading to service pack 6 for WebLogic Server 5.1. After first
starting up the WLS, a user would see our index.html, but then would see
error code 500 when trying to access the first JSP. A user would have to
hit the browser back button and try again and the first JSP page would come
up.
I would suggest that you see if service pack 6 will have any impact on your
problem, and see if that helps your situation.
John J. Feigal Voice (651)766-8787 (main)
Sr. Technical Consultant (651)766-7249 (direct)
Ensodex, Inc. Fax (651)766-8792
4105 N. Lexington Ave., Suite 150 email [email protected]
Arden Hills, MN 55126 WebSite http://www.ensodex.com
"Hann Wei Toh" <[email protected]> wrote in message
news:[email protected]..
> The systems have service pack 5 applied.
>
> Hann Wei
-
Weblogic server node start up error: java.lang.ClassCastException
Can anyone please help me with the below error?
I am trying to deploy a custom authorization provider, while weblogic is already configured with other custom authorization providers. I set my provider on high precedence and tried restarting all the nodes...
Adminserver started successfully but one of the node failed to start with the below error.. can anyone assist me here?
####<Aug 5, 2010 10:23:10 AM CDT> <Error> <Deployer> <cas5s033z3> <node_gfw_c_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281021790177> <BEA-149231> <Unable to set the activation state to true for the application 'memrApp'.
java.lang.ClassCastException: $Proxy37
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:290)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:273)
at com.bea.p13n.entitlements.management.internal.RDBMSSecurityPolicyManager.getSecurityPolicy(RDBMSSecurityPolicyManager.java:204)
at com.bea.p13n.entitlements.management.SecurityPolicyManager.getSecurityPolicy(SecurityPolicyManager.java:119)
at com.bea.content.manager.internal.ContentUpgradeListener.hasUpgradeBeenDone(ContentUpgradeListener.java:105)
at com.bea.content.manager.internal.ContentUpgradeListener.postStart(ContentUpgradeListener.java:58)
at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:209)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:95)
at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.lang.ClassCastException: $Proxy37
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:290)
at com.bea.p13n.entitlements.management.internal.SecurityPolicyDelegate.policyExists(SecurityPolicyDelegate.java:273)
at com.bea.p13n.entitlements.management.internal.RDBMSSecurityPolicyManager.getSecurityPolicy(RDBMSSecurityPolicyManager.java:204)
at com.bea.p13n.entitlements.management.SecurityPolicyManager.getSecurityPolicy(SecurityPolicyManager.java:119)
at com.bea.content.manager.internal.ContentUpgradeListener.hasUpgradeBeenDone(ContentUpgradeListener.java:105)
at com.bea.content.manager.internal.ContentUpgradeListener.postStart(ContentUpgradeListener.java:58)
at weblogic.application.internal.flow.BaseLifecycleFlow$PostStartAction.run(BaseLifecycleFlow.java:209)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:95)
at weblogic.application.internal.flow.BaseLifecycleFlow.postStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.TailLifecycleFlow.activate(TailLifecycleFlow.java:33)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)Thanks Sharat. Can you please specify more details about the class / jar you are talking about? What Jar do you think is duplicated? I verified the classpath and the jars in the server/lib and web-inf/lib. Everything seems ok to me.
Your input will be highly appreciated. -
Weblogic server log has null0 error
Hi all,
Is anyone know the problem for null0? Why it will write into weblogic admin log and how to get rid of it.
Thank in advance!
<Nov 30, 2010 3:24:12 PM EST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WLSServerControlTablePage.>
null0
null0
null0
null0
null0
null0
null0
null0
<Nov 30, 2010 3:32:08 PM EST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerConfigGeneralTabPage&handle=com.bea.console.handles.JMXHandle%28%22com.bea%3AName%3Dsmp_node1_svr%2CType%3DServer%22%29.>
<Nov 30, 2010 3:32:28 PM EST> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.management.logging.DomainLogHandlerImpl.ping()
java.lang.NullPointerException.
java.lang.NullPointerException
at weblogic.management.logging.DomainLogHandlerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)Hi,
Try to check server log which will available under Domain_Home / servers / <required server > / logs
check log file to get more details.
also check access log whether you HTTP 500 error or not.
Regards,
Kal -
I'm getting the following error on startup of the app server. It doesn't appear to affect the app server running, its just annoying. Any ideas?
[18/Dec/2003 11:26:08:8] info: PROT-006: new connection established
[18/Dec/2003 11:26:11:2] info: PROT-006: new connection established
priority not set in the registry for driver 16
priority not set in the registry for driver 32
priority not set in the registry for driver 128
priority not set in the registry for driver 256
JTS Error: Unexpected exception com.sun.jts.CosTransactions.LogException: Log exception at point 3:
LOG-002: Open failure from log..
java.lang.Exception
at com.sun.jts.CosTransactions.ErrorLog.error(Unknown Source)
at com.sun.jts.CosTransactions.Log.open(Unknown Source)
at com.sun.jts.CosTransactions.CoordinatorLog.openLog(Unknown Source)
at com.sun.jts.CosTransactions.CoordinatorLog.getLogged(Unknown Source)
at com.sun.jts.CosTransactions.RecoveryManager.recover(Unknown Source)
at com.sun.jts.CosTransactions.ResyncThread.run(Unknown Source)
[18/Dec/2003 11:26:12:0] error: DATA-100: priority not set in the registry for driver 16
[18/Dec/2003 11:26:12:0] error: DATA-100: priority not set in the registry for driver 32
[18/Dec/2003 11:26:12:0] error: DATA-100: priority not set in the registry for driver 128
[18/Dec/2003 11:26:12:0] error: DATA-100: priority not set in the registry for driver 256
org.omg.CORBA.INTERNAL: 18-Dec-03 11:26:12 : compass,P30921 : JTS021F Unexpected exception com.sun.jts.CosTransactions.LogException: Log exce
ption at point 3:
LOG-002: Open failure from log.
minor code: 0 completed: No
at com.sun.jts.CosTransactions.ErrorLog.error(Unknown Source)
at com.sun.jts.CosTransactions.Log.open(Unknown Source)
at com.sun.jts.CosTransactions.CoordinatorLog.openLog(Unknown Source)
at com.sun.jts.CosTransactions.CoordinatorLog.getLogged(Unknown Source)
at com.sun.jts.CosTransactions.RecoveryManager.recover(Unknown Source)
at com.sun.jts.CosTransactions.ResyncThread.run(Unknown Source)
[18/Dec/2003 11:26:12:4] info: EXTMGR-006: GXExtensionManager: Extension service ExtensionData successfully loaded
[18/Dec/2003 11:26:12:6] info: EXTMGR-006: GXExtensionManager: Extension service JavaExtData successfully loaded
[18/Dec/2003 11:26:12:6] info: EXTMGR-006: GXExtensionManager: Extension service LockManager successfully loaded
[18/Dec/2003 11:26:12:6] info: EXTMGR-006: GXExtensionManager: Extension service RLOPManager successfully loadedKen,
I took over looking at the problem.
It turns out that there's a directory under
../ias/logs/jts
called <hostname>,Pxxxxxx.ld
This was owned by root. (We've noticed that the install script starts up iAS as root the first time - regardless of which account you give it)
chown -R owner:group jts
did the trick.
Regards,
Alan -
Weblogic Server 8.1 startup problem
We are trying to install Weblogic 8.1 server in a isolated lab with no internet
access. The opearting system is Solaris 8.
The problem we are experiencing is that during start up it will attempts to contact
jakarta.apache.org and time out after ~ 25 minutes. I am hoping someone can direct
me to a web page with inforamtion on how to remove the need to contact the website
or reduce the timeout period. I hae looked all over e-docs.bea.com for the information
and I could not find an answer. Thanks in advance.
Felixstart ur admin first as ./startweblogic.sh or double click on startweblogic.cmd if in windows OS
Then modify ur startmanagedweblogic file with admin url and port and also server name as ur managed servers name
Save that file as (save as option) startManagedWeblogic_M1.cmd and startManagedWeblogic_M2.cmd to start them
the admin url and port would be the same form M1 and M2
only the server_name will be different, M1 for M1 and M2 for M2
Next start ur managed servers and let me know -
Cannot run PAPI in Weblogic Server 10g - Error 500--Internal Server Error
I use Jdev 11g to create an ADF (PAPI) and deploy it to Weblogic 10g.
The code is copied from Jdev 10g. The PAPI works fine in when running in Jdev 10g
However, after I deploy the ADF (PAPI) created using Jdev 11g to the Weblogic server. The following error appears.
How to modify the code? Should I add the fuego lib to the weblogic domain?
I try to add the fuegopapi-client.jar to Weblogic Server. But it shows error: Unable to access the selected application. java.lang.NullPointerException
BPM is running in BPM standalone. I do not use PAPI webservice
Sincerely
Error 500--Internal Server Error
javax.faces.el.EvaluationException: fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:51)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:458)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:763)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:640)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:275)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:175)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:61)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:279)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:239)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:196)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:139)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
at fuego.directory.exception.DirectoryNotAvailableException.wrapDNAException(DirectoryNotAvailableException.java:33)
at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:81)
at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:34)
at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:437)
at fuego.directory.provider.jdbc.JDBCPersistenceManager.checkConnectivity(JDBCPersistenceManager.java:91)
at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:242)
at fuego.directory.provider.Factory.startSession(Factory.java:405)
at fuego.directory.Directory.startAnonymousSession(Directory.java:214)
at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:193)
at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
at fuego.papi.ProcessService.create(ProcessService.java:335)
at hypapai2.view.backing.P1.commandButton1_action(P1.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:46)
... 32 more
Caused by: fuego.connector.ConnectorException: External resource [fuego] of type [SQL] is not initialized.
Detail:External resource [fuego] cannot be used because it failed to initialize correctly at service startup.
That failure generated a warning in the server log.
Check the logs for the details on the failure.
at fuego.connector.ConnectorException.connectorNotInitialized(ConnectorException.java:60)
at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:527)
at fuego.connector.CompositeConnectorService.getDirectoryConnectorInterface(CompositeConnectorService.java:446)
at fuego.connector.CompositeConnectorService.getConnectorInterface(CompositeConnectorService.java:293)
at fuego.connector.ConnectorTransaction.registerConnectorInterfaceCoordinator(ConnectorTransaction.java:656)
at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:315)
at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:68)
... 50 moreWhile still using PAPI, try also adding b1oracle.jar, b1base.jar and b1util.jar to your ADF project.
These jars could be found from your BPM Studio installation.
HTH -
EJB deployment error for Weblogic server 9.2 mp4
Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
VinodHi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod
Maybe you are looking for
-
S_ALR_87012177 - Customer Payment History
Hi, For a particular cusotmer, the payments are recieved in company code currency (CHF - Swiss Franc) and some custmer payments are done in USD, when i am executing the transaction code S_ALR_87012177, the report is shwoing only the transactions of c
-
Inheriting table data and constraints
hi When i do a create table t1 as select * from t2 ,t1 does not inherit the constraints indexes etc of t2 but only the data. Is there any way we can achieve this. Or is there any way to replicate a table into another one? Thanks, Ashok
-
Select last line item from VBAP
Dear SAP experts, This might sound very silly question but I am new to SAP world. is there a simple select statement to select only higest line item. Say for example in VBAP, I have 9 line items. then my select statement should find the last line ite
-
Open .doc file in java on Windows 98/2000
Hi all, I need to open a .doc file on Windows 98/2000 PC thriugh java.I have used the command Runtime.getRuntime().exec(new String[] {"cmd", "/C", "start", "\"\"", filename}); This command works fine on Window 2000 but gives IO Exception: CreateProce
-
My iMac will not install flash player
It has downloaded the installer but will not instal the flash player. My Safari system is 6.0.3