Warning message at managed server start up for an EAR application
Hi all, I have an wli <b>cluster 8.1 sp3 running on AIX</b> machines. When i deploy an <u>webservice application</u> (ear) i get an exception in the node which does not host admin server. The strange thing is that the application seems to be deployed correctly. My suspicion, about the exception, is the it's caused by the different directory structure of the two nodes. As you can see at bold words, weblogic tries to create ear at a directory that does not exist at this node. It finds the latter webbus from the path of admin server at the other machine. My question is straightforwad, Can we have different paths at cluster nodes ? In this case, Should we deploy ear (webservice application) in a different way ? <Feb 22, 2005 12:33:26 PM EET> <Info> <Deployer> <BEA-149060> <Module faxManWeb of application faxManAppl successfully transitioned from prepared to active on server wliBusServerPatmosDevel.> <b>javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear</b> at weblogic.management.internal.BootStrap.apply(BootStrap.java:580) at weblogic.management.internal.BootStrap.apply(BootStrap.java:474) at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3476) at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code)) at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code)) at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code)) at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543) at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71) at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999) at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094) at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976) at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361) at weblogic.Server.main(Server.java:32) --------------- nested within: ------------------ weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception: [javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear] at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3479) at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code)) at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code)) at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code)) at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543) at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71) at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999) at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094) at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976) at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361) at weblogic.Server.main(Server.java:32)
Hi,
The problem is that the <b>directory /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/</b> does not exist at the node, because we have move it to <b>/appl/webdbus/</b> instead of <b>/appl/webbus/</b>. The question is why applications need to create adminServerDevel/upload directory and how can override it.
Thanks in advanced
Similar Messages
-
Warning message at the time of GR for a material with Batch Management
Dear All,
I am new to MM,
We are using batch at plant level. For some materials user dont want maintain
Batch classification in Material Master. At the time of Goods Receipt posting with ref-to PO user getting warning message like <b>For batch 0000000139 of material 212030602400000 4F10, no class could</b>. I check system messages setting transaction code OCHS for batch management, but I didnt found this type of message in the list.
Plzz can any one help me where I need to change system settings?
Thanks in advance.
Meeravali shaik.HI,
Check in the IMG node Logistics general > Batch Management > Define attributes of system messages.
Regards,
RitiG -
Managed Server started but reflected as Shutdown in Admin Console
Hi,
Our managed server is running as service (but the error log shows it is unable to contact the Admin server, thus running in independence mode). On our admin console, it shows the managed server as shutdown. How can we resolve this issue?
We have tried to clear all the folders under \servers\<managedserver> except the security folder containing boot.properties. However it kept prompting that invalid username/password has been entered. If we restore the original folders, the managed server was able to startup, although in independence mode. Is it because of some ldap ldift file which we find in the managed server's subfolder? How can we resolve this??
Please help, as this is a production environment and this issue just suddenly happened. It was running fine earlierHi
1) 10gR3
2) The log for managed server shows it is started and running. However, it has the following lines of error:
####<Dec 28, 2012 6:43:42 PM SGT> <Emergency> <Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422536> <BEA-141151> <The admin server could not be reached at https://kimprddmapp:9002.>
####<Dec 28, 2012 6:43:42 PM SGT> <Info> <Configuration Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422552> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
It is also unable to deploy our application:
####<Dec 28, 2012 6:43:51 PM SGT> <Error> <Deployer> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356691431398> <BEA-149205> <Failed to initialize the application 'da' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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: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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.net.SocketException: Network is unreachable: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at java.net.Socket.connect(Socket.java:475)
at java.net.Socket.<init>(Socket.java:372)
at java.net.Socket.<init>(Socket.java:273)
at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:195)
at javax.net.ssl.impl.SSLSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLSocketFactoryImpl.createSocket(Unknown Source)
at weblogic.socket.ChannelSSLSocketFactory.createSocket(ChannelSSLSocketFactory.java:78)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:274)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:502)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:566)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:242)
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
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: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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Dec 28, 2012 6:43:51 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691431991> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Dec 28, 2012 6:43:52 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691432085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
Noticed that on my Admin Server, it has the following error message, could this be the cause? How can I fix it?
####<Dec 28, 2012 6:35:45 PM SGT> <Warning> <Security> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356690945499> <BEA-090482> <BAD_CERTIFICATE alert was received from KIMPRDDMAPP.pubnet.sg - 10.206.12.30. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
####<Dec 28, 2012 6:35:45 PM SGT> <Error> <Console> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <kimdmweblogic> <> <> <1356690945499> <BEA-240003> <Console encountered the following error javax.help.HelpSetException: Could not parse
Got an IOException ([Security:090477]Certificate chain received from docs.kim.pubnet.sg - 10.206.12.30 was not trusted causing SSL handshake failure.)
Parsing failed for null
at javax.help.HelpSet.<init>(HelpSet.java:146)
at com.bea.help.utils.HelpSetHelper.getExtensionHelpSetMap(Unknown Source)
at com.bea.help.utils.HelpSetHelper.mergeExtensionHelpSet(Unknown Source)
at com.bea.help.utils.HelpSetHelper.createHelpSet(Unknown Source)
at com.bea.help.utils.HelpSetHelper.getHelpSet(Unknown Source)
at com.bea.help.utils.HelpSetHelper.ensureHelpSet(Unknown Source)
at jsp_servlet._jsp.__tocview._jspService(__tocview.java:110)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
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.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
at jsp_servlet._framework._skeletons._console.__nolayout._jspService(__nolayout.java:119)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
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.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
at jsp_servlet._framework._skeletons._console.__twocollayout._jspService(__twocollayout.java:246)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
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.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:211)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
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.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
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(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
3) Both Admin and managed servers are running on same host -
Manage Server Start Problem (weblogic.store.io.jdbc.JDBCStoreException)
I have a problem, when i start manage server.
Could you please help me about this problem?
Thanks
Orhan YENER
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "p13nJMSPersistenceStore" failed to open table "P13N_MESSAGING_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "p13nJMSPersistenceStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSPersistenceStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="p13nJMSPersistenceStore" table="P13N_MESSAGING_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:37 PM EEST> <Warning> <Store> <BEA-280076> <Database table "PF_PROLIFERATION_WLStore" for store "pfProliferationJMSStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102728280]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:57 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "pfProliferationJMSStore" in this server is not the owner of database table "PF_PROLIFERATION_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=1226318586891229532:timestamp=1340102748300]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=pfProliferationJMSStore!table=PF_PROLIFERATION_WLStore}:random=3276936988962983628:timestamp=1340102737578]".>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280072> <JDBC store "pfProliferationJMSStore" failed to open table "PF_PROLIFERATION_WLStore".
weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Store> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.io.jdbc.JDBCStoreException: open failed
weblogic.store.io.jdbc.JDBCStoreException: open failed
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:445)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:135)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:138)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:66)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
Caused By: weblogic.store.io.jdbc.JDBCStoreException: [Store:280064]280077 (server="ManagedServer2" store="pfProliferationJMSStore" table="PF_PROLIFERATION_WLStore")
at weblogic.store.io.jdbc.JDBCStoreIO.checkTableOwnership(JDBCStoreIO.java:2046)
at weblogic.store.io.jdbc.JDBCStoreIO.getTableOwnershipLogical(JDBCStoreIO.java:2159)
at weblogic.store.io.jdbc.JDBCStoreIO.open(JDBCStoreIO.java:379)
at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:332)
at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:323)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "p13nJMSServer" due to weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist.
weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of p13nJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server p13nJMSServer: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "p13nJMSPersistenceStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <JMS> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Warning> <Management> <BEA-141197> <The deployment of pfJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:492)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:304)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:192)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'p13n-security-jms'.
weblogic.application.ModuleException: ERROR: Could not activate p13n-security-jms!p13n.security.RDBMSSecurityStoreTopic
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.backend.BETopicRuntimeDelegate.activate(BETopicRuntimeDelegate.java:100)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel p13nJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.TopicImpl.activate(TopicImpl.java:97)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:627)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
Truncated. see log file for complete stacktrace
Caused By: weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1696)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1872)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 19, 2012 1:45:58 PM EEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log00054. Log messages will continue to be logged in /weblogic/Oracle/Middleware/user_projects/domains/base_domain/servers/ManagedServer2/logs/ManagedServer2.log.>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerportal. Error - weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerportal' due to error weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear.
weblogic.management.DeploymentException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: error in opening zip file with : /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.app-01.01.00.ear
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:114)
at java.util.jar.JarFile.<init>(JarFile.java:133)
at java.util.jar.JarFile.<init>(JarFile.java:97)
at weblogic.utils.jars.JarFileDelegate.<init>(JarFileDelegate.java:32)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean partnerstaticweb. Error - weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
<Jun 19, 2012 1:46:04 PM EEST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'partnerstaticweb' due to error weblogic.management.DeploymentException: .
weblogic.management.DeploymentException:
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:69)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
Truncated. see log file for complete stacktrace
Caused By: java.util.zip.ZipException: Error opening file - /weblogic/Oracle/Middleware/user_projects/domains/base_domain/yukler/Build04/com.oksijen.capex.portal.staticweb-01.01.00.war Message - error in opening zip file
at weblogic.servlet.utils.WarUtils.existsInWar(WarUtils.java:78)
at weblogic.servlet.utils.WarUtils.isWebServices(WarUtils.java:67)
at weblogic.servlet.internal.WarDeploymentFactory.findOrCreateComponentMBeans(WarDeploymentFactory.java:61)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
Truncated. see log file for complete stacktrace
>
>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 19, 2012 1:46:13 PM EEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 19, 2012 1:46:13 PM EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jun 19, 2012 1:46:14 PM EEST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 172.25.23.238:80 was shutdown.>It's the first couple of bits that are key here
<Jun 19, 2012 1:45:17 PM EEST> <Warning> <Store> <BEA-280076> <Database table "P13N_MESSAGING_WLStore" for store "p13nJMSPersistenceStore" is currently owned by "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102710950]". Trying to wait for ownership.>
<Jun 19, 2012 1:45:37 PM EEST> <Error> <Store> <BEA-280077> <JDBC store "p13nJMSPersistenceStore" in this server is not the owner of database table "P13N_MESSAGING_WLStore". Unexpected current owner is "[name={server=ManagedServer1!host=172.25.23.237!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=7010169693931783666:timestamp=1340102730980]", expected current owner is "[name={server=ManagedServer2!host=172.25.23.238!domain=base_domain!store=p13nJMSPersistenceStore!table=P13N_MESSAGING_WLStore}:random=-8739910915764232623:timestamp=1340102716802]".>
It looks to me that your stores are incorrectly configured, targetted or or just simply messed up. First thing I would do here is check the configuration and targetting of the JDBC Stores and make sure that each JMS server is using it own store and database tables. You may find that it's a really simple thing like creating two sets of tables on the same database, but making sure that they have different prefixes ... -
Messaging Bridge & Managed Server
Hi,
I am trying to use the messaging bridge in a cluster
(WLS61SP3 with CR081404_61sp3.jar + CR081511_61sp3.jar),
but I am getting the following error on startup of one
of my managed servers (error attached).
What am I doing wrong here?
Regards,
-Per
[error.txt]
Hi,
Came up with the idea of putting the jmsadapter.jar archive (included in the jms-xa-adp.rar
archive) in the system classpath,
of my managed servers.
This was mentioned in a previous posting I found, and now it seems to be working...
-Per
####<12.sep.02 09:34:18 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! creating bridge
bridgeOne>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne's
source properties are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://localhost:7011
DestinationType = Queue
DestinationJNDIName = XmlQueue2
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = connFac>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne's
target properties are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://localhost:8011
DestinationType = Queue
DestinationJNDIName = queue
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = connFac>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne
is successfully initialized>
####<12.sep.02 09:34:21 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200004> <Messaging Bridge "bridgeOne" has been successfully
deployed.>
####<12.sep.02 09:34:25 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200012> <Bridge
"bridgeOne" suceesfully found the two adapters configured for it.>
####<12.sep.02 09:34:25 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging STARTUP! BridgeBridge bridgeOne forwarding policy is AUTO>
####<12.sep.02 09:34:25 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200033> <Bridge
"bridgeOne" is getting the connections to the two adapters.>
####<12.sep.02 09:34:25 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Getting source connection>
####<12.sep.02 09:34:26 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<ListenThread> <system> <> <000202> <ListenThread listening on port 7011>
####<12.sep.02 09:34:26 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<SSLListenThread> <system> <> <000202> <SSLListenThread listening on port 7012>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:28 CEST> <Info> <Management> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'1' for queue: '__weblogic_admin_rmi_queue'> <system> <> <141060> <Reconnected
to Admin Server running at http://6S19FHGZN2CM:7001 from Managed Server - serverone.>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190035> <There was/were 1 physical
connection(s) created with the following Meta Data: Product name of EIS instance:
Java Messaging Service Product version of EIS instance: 1.0.2 Maximum number of
connections supported from different processes: 0 User name for connection: system>
####<12.sep.02 09:34:29 CEST> <Notice> <Cluster> <6S19FHGZN2CM> <serverone> <main>
<system> <> <000102> <Listening for multicast messages (cluster MyCluster) on
port 7011 at address 224.0.0.1>
####<12.sep.02 09:34:29 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Successfully got connection to the
source destination>
####<12.sep.02 09:34:29 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Getting target connection>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:29 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<main> <system> <> <000330> <Started WebLogic Managed Server "serverone" for domain
"dmsdomain" running in Production Mode>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:30 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190035> <There was/were 1 physical
connection(s) created with the following Meta Data: Product name of EIS instance:
Java Messaging Service Product version of EIS instance: 1.0.2 Maximum number of
connections supported from different processes: 0 User name for connection: system>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Successfully got connection to the
target destination>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne: both source and target adapters support
XA = true>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200032> <Bridge
"bridgeOne" is configured not to allow degradation of its quality of service in
cases where the configured quality of service is not reachable.>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne supportsMDBTX = true supportsXA = true
async = true>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne WorkMode = Exactly-once>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200030> <Bridge
"bridgeOne" is configured to work in "Exactly-once" mode and it is actually working
in "Exactly-once" mode.>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200028> <Bridge
"bridgeOne" starts transferring messages.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200027> <Bridge "bridgeOne"
works in asynchronous mode and has not received messages for the predefined maximum
idle time. The connections to the adapters will be interrupted and re-established.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200020> <Bridge "bridgeOne"
is stopped.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200033> <Bridge "bridgeOne"
is getting the connections to the two adapters.>
"Per Mengshoel" <[email protected]> wrote:
>
>Hi,
>
>I got the patch, but didn't quite succeed in configuring
>it... I am getting exceptions in the managed server's log.
>
>Ideas?
>-Per
>
>####<12.sep.02 08:44:58 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! creating
>bridge
>bridgeOne>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne's
>source properties are:
> AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
> Classpath=null
> ConnectionURL = t3://localhost:7011
> DestinationType = Queue
> DestinationJNDIName = XmlQueue2
> InitialContextFactory = weblogic.jndi.WLInitialContextFactory
> ConnectionFactoryJNDIName = connFac>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne's
>target properties are:
> AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
> Classpath=null
> ConnectionURL = t3://localhost:8011
> DestinationType = Queue
> DestinationJNDIName = queue
> InitialContextFactory = weblogic.jndi.WLInitialContextFactory
> ConnectionFactoryJNDIName = connFac>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne
>is successfully initialized>
>####<12.sep.02 08:44:59 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200004> <Messaging Bridge "bridgeOne" has been successfully
>deployed.>
>####<12.sep.02 08:44:59 CEST> <Info> <HTTP> <6S19FHGZN2CM> <serverone>
><main>
><system> <> <101133> <Initializing WEB server serverone>
>####<12.sep.02 08:45:01 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200012>
><Bridge
>"bridgeOne" suceesfully found the two adapters configured for it.>
>####<12.sep.02 08:45:02 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006>
><Messaging
>Bridge Debugging STARTUP! BridgeBridge bridgeOne forwarding policy is
>AUTO>
>####<12.sep.02 08:45:02 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200033>
><Bridge
>"bridgeOne" is getting the connections to the two adapters.>
>####<12.sep.02 08:45:02 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006>
><Messaging
>Bridge Debugging RUNTIME! Bridge bridgeOne Getting source connection>
>
>####<12.sep.02 08:45:02 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200042>
><Bridge
>"bridgeOne" failed to connect to the source destination and will try
>again in
>20 seconds. (java.lang.Exception: javax.resource.ResourceException: Problem
>granting
>connection request to a ManagedConnectionFactory which does not exist
>in connection
>pool. Check your MCF's hashcode()
> at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:149)
> at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:20)
> at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:97)
> at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:696)
> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:901)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>)>
>
>
>"Dongbo Xiao" <[email protected]> wrote:
>>This is a known problem in the adapter deployment area.
>>Contact BEA customer support and ask about CR083563.
>>
>>Dongbo
>>
>>"Per Mengshoel" <[email protected]> wrote in message
>>news:[email protected]...
>>>
>>> Hi,
>>>
>>> I am trying to use the messaging bridge in a cluster
>>> (WLS61SP3 with CR081404_61sp3.jar + CR081511_61sp3.jar),
>>> but I am getting the following error on startup of one
>>> of my managed servers (error attached).
>>>
>>> What am I doing wrong here?
>>>
>>> Regards,
>>> -Per
>>>
>>>
>>
>>
>
-
WSM Managed server starts in ADMIN Mode after upgrade to 11.1.1.7
We have just upgraded our 11g SOA Cluster environment from 11.1.1.4 to 11.1.1.7. The issue is after the upgrade, our WSM servers are starting to ADMIN state with following error.
<Sep 25, 2013 7:14:35 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@381802823[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
Our cluster environment has one Admin Server, and two of each OSB, WSM and SOA managed servers. As our WSM servers are not coming up, we are not able to start our SOA servers too.
Thank YouSame issue here :-)), Just playing around with policies configuration, the server was running just fine, I wanted to check if the policies are applicable during runtime even the WSM managed server is down. After restart, it started in ADMIN mode, well the solution is straight. It is exactly telling that the dms application is missing the jstl library reference
<Error> <Deployer> <iwpdcdevsoaa.iwater.ie> <WLS_WSM1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <bcfaf10ec8fbdfc2:-26d85d29:1429ffae24c:-8000-0000000000000003> <1385663491675> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error weblogic.application.ModuleException: Failed to load webapp: 'dms.war'.
weblogic.application.ModuleException: Failed to load webapp: 'dms.war'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:395)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
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:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Library references for "ServletContext@384044243[app:DMS Application module:dms.war path:/dms spec-version:2.5 version:11.1.1.1.0]", defined in weblogic.xml [Extension-Name: jstl, Specification-Version: 1.2, Implementation-Version: 1.2, exact-match: false]
at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries(WebAppServletContext.java:2750)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:416)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:494)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:384)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
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:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:144)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:40)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
So search for "jstl" within the weblogic console in search bar, it is type of library, click on it and target it to the managed server where OWSM is running as weel. It was root cause in my case, somehow the library was not targeted to our WLS_WMS1 managed server. Now the server is back in RUNNING mode. Of course apply this in case of problem with SOA servers, target it to the cluster or exact nodes and it should work.
Still I don't know how the issue has been crated, I don't think that somebody removed it from deployment. Rather I think that somebody was applying patch or some artifacts to OSB or SOA managed server and this library was required as well, but as soon as we have separated WSM cluster, it was maybe assuming that it is running within OSB or SOA clusters and therefore didn't target the WSM cluster automatically. But this is just the idea :-))
Ladislav -
Warning Messages related to Reconstruct Availability Control for Project
Hi Gurus,
In Transaction IM52 - Change Original Budget for Investment Management Program, after changing the Budget Values of Investment Management Position and when we check the transaction for error, we get Warning Messages, the warning message is as follows:
You Must reconstruct the availability control for Project P.000XXX.
We tried to reconstruct the Availability Control in Transaction CJBN and again checked for errors in IM52, then also we get Warning Messages.
As these are only Warning Messages we can ignore and save the modified budget values for the Investment Management Program. But we want to know whey these Warning Messages are keep on cropping up inspite of reconstructing the Availability Control for Project.
You inputs on this will help us immensly.
Thanks,
KRNhi KRN!
I am also facing the same issue.
Even if i am having enough budget, while making a PO, the system says " Budget exceeded".
i could processs the PO, after performing CJBW (deactivate), CJEN (refresh) and then performing CJBV ( activate availabilty control) for that project.
This is repeating everytime i make a PO. is there any permanent solution?
Even after performing all the above, if i check in IM52, and check for budgets (perform from menu), the error is " You Must reconstruct the availability control for Project P.000XXX" -
Weblogic Server does not show managed server started when I used the Windows service to start it.
I created a windows service to start a managed server and the services was created successfully and stated. WHen I go to the Weblogic Server Admn console, the server is still showing shutdown. Whenm I try to start it, it returns with error that the the service is not able to start. Has anyone ran into anything similar. I am running on Windows Server 2008R2 and running Weblogic Server 10.3.6 and Fusion Middleware 11.1.6.
CHi,
For starting managed server as windows service there is no need of nodemanager .
Please follow the steps given in the below doc:
How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
Thanks,
Sharmela -
Managed server start very slowly
Hi All,
We are currently facing issues in starting a managed weblogic server.
We have 2 machines, say MAC1 and MAC2.
MAC1 contains the admin server and 5 managed servers.
MAC2 contains only 5 managed servers with the same name as that of the 5 managed servers which are on MAC1.
We faced some issues starting the managed servers on MAC2.
So we decided to use pack and unpack.
We were able to start the managed servers on MAC2 however each server tooks about 25 minutes to start.
This is some what unexpected behaviour.
I had a look at the logs of one of the managed server.
It appears that its waits most of its time on :
<Log Management> <BEA-170019> <The server log file xyz.log is opened. All server side log events will be written to this file.>
The next log after this appears after about 20 minutes.
So i feel that its stuck reading or writing the logs.
Any pointers!!
Regards,
Stacey.Hi All,
After taking the thread dumps , I am suspecting the following two threads which might be causing the issue :
"Thread-3" daemon prio=10 tid=0x73939800 nid=0x6784 waiting on condition [0x72530000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x76610450> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1735)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:452)
at weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:19)
at weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
at weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:175)
at weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java233)
"ExecuteThread: '7' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=0x7391ec00 nid=0x6789 waiting for monitor entry [0x73344000]
java.lang.Thread.State: BLOCKED (on object monitor)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:95)
- waiting to lock <0x765902f0> (a weblogic.socket.PosixSocketMuxer$1)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Any pointers !!
Regards,
Stacey. -
Managed Server Monitoring tools for WLS 8.1 on linux
Our organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
When a managed server is started, the command line resembles the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameOfMgdServer
The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
It now appears similar to the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameO
This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
Each managed server is monitored by the WLS administration server and the local node manager.
Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
Any feedback is appreciatedOur organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
When a managed server is started, the command line resembles the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameOfMgdServer
The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
It now appears similar to the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameO
This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
Each managed server is monitored by the WLS administration server and the local node manager.
Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
Any feedback is appreciated -
Weblogic 10.3.5 Managed Server 추가 후 start 할 때 에러 나요...
Windows 7(로컬 환경)에서 weblogic 10.3.5를 사용하고 있고, 관리자 콘솔(http://localhost:7001/)에서 Managed Server(서버 이름 :test_server)를 등록해주었습니다.
그리고 배치에 디플로이 할 소스 경로를 체크하고 test_server targetting 한 후 start 했는데 에러가 납니다...ㅠㅠ
두 가지 방법으로 start 했었는데..
1. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin>startManagedWebLogic.cmd test_server http://localhost:8001
이렇게 입력하면, 로그가 잘 찍히다가
Enter username to boot WebLogic server: test_name
이게 표시됩니다. weblogic 처음 설치 할 때 설정한 username(어드민 콘솔 아이디)를 입력하니 password를 입력하라고 나오는게 아니라 아래와 같이 에러가 납니다. ㅠㅠ
*<Error> <Security> <BEA-090783> <Server is Running in Development Mode and Native Library(terminalio) to read the password securely from commandline is not found.>*
*<Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>*
*<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
두번 째 방법은
2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic.cmd*
여기서 startManagedWebLogic.cmd 를 카피하여 startManagedWebLogic_test.cmd 를 만든 후 if "%1"=="" ( 바로 아래
set SERVER_NAME=test
set ADMIN_URL=http://localhost:8001
set WLS_USER=test_name
set WLS_PW=test_password
이렇게 만든 후 2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic_test.cmd* 로 Start 하였습니다.
그러니 아주 크리티컬한 에러가............... ㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠ
<Critical> <WebLogicServer> <BEA-000362> *<Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already* exists>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
저 에러로그로 구글링을 엄청나게 해봤는데 별다른 성과가 없습니다..
제발 아시는 분 도와주세요..ㅠㅠ
글 수정: 889513 -
This is my app.config file
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="IntelBrandFX.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
</sectionGroup>
</configSections>
<appSettings>
<add key="connStr" value="Data Source=tmvnasql1.tmvn.com;Initial Catalog=brandplan;Integrated Security=True"/>
</appSettings>
<applicationSettings>
<IntelBrandFX.Properties.Settings>
<setting name="IntelBrandFX_rollupViewerService_extract" serializeAs="String">
<value>https://viewer.rollup.com/omdsp2008/extract.asmx</value>
</setting>
</IntelBrandFX.Properties.Settings>
</applicationSettings>
</configuration>
And the Warning messages are
Message 1 Could not find schema information for the element 'applicationSettings'.
Message 2 Could not find schema information for the element 'IntelBrandFX.Properties.Settings'.
Message 3 Could not find schema information for the element 'setting'.
Message 4 Could not find schema information for the attribute 'name'.
Message 5 Could not find schema information for the attribute 'serializeAs'.
Message 6 Could not find schema information for the element 'value'.
Althought they do no hinder me from successfully running the project. these messages are annoying. I have seen many articles on the web but could nowhere find the exact schemas for that the above elements that I could add to the DotNetConfig.xsd file.
Could somebody give me an idea how to create xsds for the elements above and include in the dotnetConfig.xsd.
I understand what needs to be done but not sure of the exact way to do it.
Thanks,You don't need to modify the dotnetconfig.xsd. All you need to do is generate an XSD for your section and let VS know where it is at.
1) Create your XSD using any of the various tools available or by hand.
2) Copy your XSD into the <VSDir>\Xml\Schemas directory.
3) Create a catalog file for your schema.
4) Restart VS and it'll load the XSD and give you Intellisense.
Here's the MSDN documentation for it: http://msdn.microsoft.com/en-us/library/ms255821.aspx
Michael Taylor - 8/18/09
http://p3net.mvps.org -
SQL Server Enterprise support for Offline / Online Application development
Hi,
We have suggested to use the SQL Server 2012 as Database for our Enterprise application. We have the Offline/Online two set of application. Can you suggest any offline database to sync the Online SQL Server database.
Thanks,
SethuWhat is an offline database?
One can setup an "online" database and an "offline" database using SQL Server 2012 Enterprise Edition.
SSIS packages can be used to synch data between the databases:
http://blogs.msdn.com/b/jorgepc/archive/2010/12/07/synchronize-two-tables-using-sql-server-integration-services-ssis-part-i-of-ii.aspx?Redirected=true
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012 -
Null argument for startup classes when managered server starts
Hi Everyone,
We have a Weblogic 10.3.5 clustering environment. the environment seems to work fine. I am able to have the servers (both Admin and Managed) and deployed applications running without any problems. However, I just notice that, every time when I start the Managered servers, I got the following information in the system log. It appears that they are start-up classes, but with null argument. Are they normal or not?
Thanks in advance,
John
####<Feb 22, 2012 11:28:27 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928107258> <BEA-000256> <Invoking oracle.dms.wls.DMSShutdown.main(null)>
####<Feb 22, 2012 11:28:27 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928107769> <BEA-000256> <Invoking oracle.ias.cache.Shutdown.main(null)>
####<Feb 22, 2012 11:40:08 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928808600> <BEA-000256> <Invoking oracle.jrf.wls.JRFStartup.main(null)>
####<Feb 22, 2012 11:40:08 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928808682> <BEA-000256> <Invoking oracle.security.jps.wls.JpsWlsStartupClass.main(null)>
####<Feb 22, 2012 11:40:08 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928808790> <BEA-000256> <Invoking oracle.core.ojdl.weblogic.ODLConfiguration.main(null)>
####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817314> <BEA-000256> <Invoking oracle.jrf.AppContextStartup.main(null)>
####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817318> <BEA-000256> <Invoking oracle.as.jmx.framework.wls.spi.StartupListener.main(null)>
####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817432> <BEA-000256> <Invoking oracle.j2ee.ws.server.WebServiceServerStartup.main(null)>
####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817492> <BEA-000256> <Invoking oracle.ias.cache.Startup.main(null)>
####<Feb 22, 2012 11:40:17 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928817493> <BEA-000256> <Invoking oracle.dms.wls.DMSStartup.main(null)>
####<Feb 22, 2012 11:40:18 AM EST> <Info> <Management> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928818207> <BEA-141278> <Java entropy configuration is: System property "java.security.egd= null"; JRE's java.security file property "securerandom.source= file:/dev/urandom"; Blocking Config= false; JDK version= 1.6.0_26; Operating System= Linux.>
####<Feb 22, 2012 11:40:48 AM EST> <Info> <WebLogicServer> <entwl2u-vm.co.pinellas.fl.us> <Pinellas1uCluster1MS2> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329928848987> <BEA-000256> <Invoking oracle.security.audit.ajl.loader.JEEAuditLoader.main(null)>Hi John,
This is Ok. Those are just info messages. Thery are not warnings or errors, so nothing to worry about.
If the classes are invoked with null arguments and no exception is thrown, then is means that the class is able to have a null argument, so nothing to worry about again.
Regards,
Cris -
Error Message on cluster server start
Hi all,
I'm trying to install a cluster with two Windows 2000 machines, and every
time I try to start my
server I get the same message from the output of the server:
It's about the weblogic.properties located in the installation directory and
the cluster directory.
java.lang.IlegalArgumentException : Malformed \uxxxx encoding
Any hint?
The only place I've seen that exception is from the JSP compiler
with -encoding utf-8 is set and it comes across some invalid utf-8 characters.
If it is really referring to the weblogic.properties file, you
may wish to look for strange characters in it.
It's always nice to post the stack-trace.
Mike
"Miquel Taberner" <[email protected]> wrote:
> Hi all,
>
>I'm trying to install a cluster with two Windows 2000 machines, and every
>time I try to start my
>server I get the same message from the output of the server:
>
>It's about the weblogic.properties located in the installation directory and
>the cluster directory.
>
>java.lang.IlegalArgumentException : Malformed \uxxxx encoding
>
>
>Any hint?
>
>
>
>
Maybe you are looking for
-
Product costing by sales order configuration steps
hi plz send me product costing by sales order configuration steps. sir, i know manufacturing order configuration step but i do not sales order configuration. in the sales order also is same as manufacturing order like first we have to make planning c
-
Accessing DataGrid currentTarget from a dataGridColumn button
I am trying to access the row item clicked from within a datagrib button. Any thoughts? It seems to only accept event or mouseevent... public function onDeleteItem(e:Event):void{ trace(e.currentTarget.parent);
-
Help - How to get our PF keys working on the web?
We just successfully built a 9iAS server on a W2K platform - it was quick, easy and works perfectly with simple FORMS. However, the main FORM product we want to move from client/server to the web uses function keys -i.e F8, and these just don't funct
-
Looking for way to get value inside xmlelement that includes xmlattribute
Thank you ! Edited by: 876684 on Aug 2, 2011 11:35 AM
-
How do I retrieve a site that I uploaded to the temporary Business Catalyst Host?
How do I retrieve a site that I uploaded to the temporary Business Catalyst Host after losing the site on my system?