Weblogic.management.configuration.ConfigurationException

Dear All,
I am using Weblogic 6.1 with Service Pack 2 it was working fine.
I tried to upgrade it by installing Service Pack 7, but it was giving some exception when I tried to deploy the ejbs on server.
Now I revert back to service pack 2 by uninstalling the service pack 7, but when I tried to start the server it is giving following error.
How to solve this problem? It's very urgent. Pls help me out.
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException: Unknown attribute StagedTargets for MyWebApp, type Application
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHan
dler.parseMBeanAttributes(ConfigurationParser.java:308)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHan
dler.startElement(ConfigurationParser.java:188)
at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:
1340)
at weblogic.apache.xerces.validators.common.XMLValidator.callStartElemen
t(XMLValidator.java:1183)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDo
cumentScanner.java:1876)
at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher
.dispatch(XMLDocumentScanner.java:1252)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:381)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
at weblogic.management.internal.xml.ConfigurationParser.parse(Configurat
ionParser.java:105)
at weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
Repository.java:261)
at weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
Repository.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy1.loadDomain(Unknown Source)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.j
ava:188)
at weblogic.management.AdminServer.configure(AdminServer.java:173)
at weblogic.management.Admin.initialize(Admin.java:239)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance
regards,
ritu

Dear All,
I am using Weblogic 6.1 with Service Pack 2 it was
working fine.
I tried to upgrade it by installing Service Pack 7,
but it was giving some exception when I tried to
deploy the ejbs on server.
Now I revert back to service pack 2 by uninstalling
the service pack 7, but when I tried to start the
server it is giving following error.
How to solve this problem? It's very urgent. Pls help
me out.
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationExcepti
on: Unknown attribute StagedTargets for MyWebApp,
type Application
at
weblogic.management.internal.xml.ConfigurationParser$C
onfigurationHan
dler.parseMBeanAttributes(ConfigurationParser.java:308
at
weblogic.management.internal.xml.ConfigurationParser$C
onfigurationHan
dler.startElement(ConfigurationParser.java:188)
at
weblogic.apache.xerces.parsers.SAXParser.startElement(
SAXParser.java:
1340)
at
weblogic.apache.xerces.validators.common.XMLValidator.
callStartElemen
t(XMLValidator.java:1183)
at
weblogic.apache.xerces.framework.XMLDocumentScanner.sc
anElement(XMLDo
cumentScanner.java:1876)
at
weblogic.apache.xerces.framework.XMLDocumentScanner$Co
ntentDispatcher
.dispatch(XMLDocumentScanner.java:1252)
at
weblogic.apache.xerces.framework.XMLDocumentScanner.pa
rseSome(XMLDocu
mentScanner.java:381)
at
weblogic.apache.xerces.framework.XMLParser.parse(XMLPa
rser.java:967)
at
weblogic.management.internal.xml.ConfigurationParser.p
arse(Configurat
ionParser.java:105)
at
weblogic.management.internal.xml.XmlFileRepository.loa
dDomain(XmlFile
Repository.java:261)
at
weblogic.management.internal.xml.XmlFileRepository.loa
dDomain(XmlFile
Repository.java:223)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLo
cally(DynamicMB
eanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(D
ynamicMBeanImpl
.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.in
voke(Configurat
ionMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSer
verImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSer
verImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanPr
oxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanPr
oxy.java:209)
at $Proxy1.loadDomain(Unknown Source)
at
weblogic.management.AdminServer.configureFromRepositor
y(AdminServer.j
ava:188)
at
weblogic.management.AdminServer.configure(AdminServer.
java:173)
at
weblogic.management.Admin.initialize(Admin.java:239)
at
weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Thanks in advance
regards,
rituHi,
As mentioned in your error message ("Unknown attribute StagedTargets for MyWebApp"), the attribute StagedTargets is added to your config.xml file in domain MyWebApp when service pack 7 was installed. Un-installing service pack 7 does not remove this attribute nor restores your Weblogic6.1 service pack 2 config.xml file. Hence delete or backup the current config.xml file in domain MyWebApp, copy the config.xml file you have been using with service pack 2 and restart WebLogic. It should start successfully.
Note: Upon un-installing service pack 7 restart your system.
Regards,
HP

Similar Messages

  • Weblogic.management.configuration.ConfigurationException: Unknown attribute

    Dear All,
    I am using Weblogic 6.1 with Service Pack 2 it was working fine.
    I tried to upgrade it by installing Service Pack 7, but it was giving some exception when I tried to deploy the ejbs on server.
    Now I revert back to service pack 2 by uninstalling the service pack 7, but when I tried to start the server it is giving following error.
    How to solve this problem? It's very urgent. Pls help me out.
    The WebLogic Server did not start up properly.
    Exception raised:
    weblogic.management.configuration.ConfigurationException: Unknown attribute StagedTargets for MyWebApp, type Application
    at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHan
    dler.parseMBeanAttributes(ConfigurationParser.java:308)
    at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHan
    dler.startElement(ConfigurationParser.java:188)
    at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:
    1340)
    at weblogic.apache.xerces.validators.common.XMLValidator.callStartElemen
    t(XMLValidator.java:1183)
    at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDo
    cumentScanner.java:1876)
    at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher
    .dispatch(XMLDocumentScanner.java:1252)
    at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
    mentScanner.java:381)
    at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
    at weblogic.management.internal.xml.ConfigurationParser.parse(Configurat
    ionParser.java:105)
    at weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
    Repository.java:261)
    at weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
    Repository.java:223)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
    eanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
    .java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
    ionMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    55)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
    23)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy1.loadDomain(Unknown Source)
    at weblogic.management.AdminServer.configureFromRepository(AdminServer.j
    ava:188)
    at weblogic.management.AdminServer.configure(AdminServer.java:173)
    at weblogic.management.Admin.initialize(Admin.java:239)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance
    regards,
    rspi:-(

    looking for StagedTargets into config.xml and delete this attribute.
    StagedTargets means that one application was deployed over one (or more) server in mode stage.
    I think that this attribute is not allow sp2 and is not very important.

  • NoClassDefFoundError: weblogic/management/configuration/KernelDebugMBean

    NoClassDefFoundError: weblogic/management/configuration/KernelDebugMBean : weblogic/management/configuration/DebugMBean
    I'm getting this error when trying to run a test of a web service developed with Axis outside of WLP.
    weblogic.jar is in my classpath, and contains that class. So, I suspect there is some other class that might be missing. I've tried adding every .jar I can find from WLP to my classpath to no avail.
    Here is the full trace:
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/management/configuration/KernelDebugMBean : weblogic/management/configuration/DebugMBean
         at java.lang.ClassLoader.findBootstrapClass(Native Method)
         at java.lang.ClassLoader.findBootstrapClass0(ClassLoader.java:891)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:301)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
         at weblogic.xml.jaxp.RegistryDocumentBuilderFactory.<clinit>(RegistryDocumentBuilderFactory.java:28)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at java.lang.Class.newInstance0(Class.java:350)
         at java.lang.Class.newInstance(Class.java:303)
         at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:100)
         at javax.xml.parsers.FactoryFinder.findJarServiceProvider(FactoryFinder.java:278)
         at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:185)
         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:98)
         at org.apache.axis.utils.XMLUtils.getDOMFactory(XMLUtils.java:221)
         at org.apache.axis.utils.XMLUtils.<clinit>(XMLUtils.java:83)
         at org.apache.axis.configuration.FileProvider.configureEngine(FileProvider.java:179)
         at org.apache.axis.AxisEngine.init(AxisEngine.java:172)
         at org.apache.axis.AxisEngine.<init>(AxisEngine.java:156)

    Hi Tim,
    Pls always mention WLP version for a question.
    Looks like there has been a change in the class "KernelDebugMBean" between WLP 9.2 and WLP 10.0
    9.2: public interface KernelDebugMBean extends weblogic.management.configuration.DebugMBean
    "http://edocs.bea.com/wls/docs92/javadocs_mhome/index.html"
    10.0
    public interface KernelDebugMBean
    "http://edocs.beasys.co.jp/e-docs/wls/docs100/javadocs_mhome/index.html?weblogic/management/configuration/KernelDebugMBean.html"
    Not really sure. Something is messy about DebugMBean superclass.
    Might a BEA support question
    Thanks
    Vishnu

  • Getting weblogic management exception.

    Hi gurus...
    I'm trying to add a JMSTopic through Mbean.
    When i'm trying to add it i'm getting this exception
    weblogic.management.configuration.ConfigurationException
    <Sep 25, 2003 11:45:13 AM GMT+06:00> <Error> <Management> <BEA-141022>
    <Management exception: Saving domain zodiac, info:
    zodiac:JMSServer=ZIPServer,Name=ZODIACtoZIP,Type=JMSTopic.
    weblogic.management.configuration.ConfigurationException: Can't add MBean
    because parent node does not exist
    at
    weblogic.management.internal.xml.ConfigurationRepositoryImpl.getParentNode(C
    onfigurationRepositoryImpl.java:815)
    at
    weblogic.management.internal.xml.ConfigurationRepositoryImpl.add(Configurati
    onRepositoryImpl.java:562)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.makeNewPersistObject(Con
    figurationMBeanImpl.java:807)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.postRegister(Configurati
    onMBeanImpl.java:433)
    at
    weblogic.management.mbeans.custom.JMSTopic.postRegister(JMSTopic.java:67)
    at
    com.sun.management.jmx.MBeanServerImpl.postRegisterInvoker(MBeanServerImpl.j
    ava:2293)
    at
    com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:88
    4)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBean
    ServerImpl.java:457)
    at
    weblogic.management.internal.DynamicMBeanImpl.setParent(DynamicMBeanImpl.jav
    a:264)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
    .java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.
    java:1651)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.
    java:1101)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Configurati
    onMBeanImpl.java:311)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:135
    8)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:133
    3)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanS
    erverImpl.java:367)
    at
    weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
    t.java:353)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
    0)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    This is how i'm trying to add it.
    here i'm creating the JMS Topic
    java weblogic.Admin -url %ADMIN_URL% -username %WLS_USER% -password %WLS_PW%
    CREATE -mbean %WLS_DOMAIN%:Name=%JMSTopic%,Type=JMSTopic
    Exception is thrown while trying to execute this code
    @ECHO Setting Properties
    java weblogic.Admin -url %ADMIN_URL% -username %WLS_USER% -password %WLS_PW%
    SET -mbean
    %WLS_DOMAIN%:Location=%WLS_SERVER%,Name=%JMSTopic%,Type=JMSTopic -property
    Parent %WLS_DOMAIN%:Name=%JMSServer%,Type=JMSServer
    can anyboy point me where i'm missing some entries??
    Thanks and regards
    sasi

    Hello Sasi,
    parent name ( JMSServer in this case) has to be part of object name when u
    create JMSTopic mbean. Something like
    java weblogic.Admin -url %ADMIN_URL% -username %WLS_USER% -password
    %WLS_PW%
    CREATE -mbean
    %WLS_DOMAIN%:Name=%JMSTopic%,Type=JMSTopic,JMSServer=%JMSServer%
    Cheers
    Ali
    "T. Sasi Dharma" <[email protected]> wrote in message
    news:[email protected]...
    Hi gurus...
    I'm trying to add a JMSTopic through Mbean.
    When i'm trying to add it i'm getting this exception
    weblogic.management.configuration.ConfigurationException
    <Sep 25, 2003 11:45:13 AM GMT+06:00> <Error> <Management> <BEA-141022>
    <Management exception: Saving domain zodiac, info:
    zodiac:JMSServer=ZIPServer,Name=ZODIACtoZIP,Type=JMSTopic.
    weblogic.management.configuration.ConfigurationException: Can't add MBean
    because parent node does not exist
    at
    weblogic.management.internal.xml.ConfigurationRepositoryImpl.getParentNode(C
    onfigurationRepositoryImpl.java:815)
    at
    weblogic.management.internal.xml.ConfigurationRepositoryImpl.add(Configurati
    onRepositoryImpl.java:562)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.makeNewPersistObject(Con
    figurationMBeanImpl.java:807)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.postRegister(Configurati
    onMBeanImpl.java:433)
    at
    weblogic.management.mbeans.custom.JMSTopic.postRegister(JMSTopic.java:67)
    at
    com.sun.management.jmx.MBeanServerImpl.postRegisterInvoker(MBeanServerImpl.j
    ava:2293)
    at
    com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:88
    4)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBean
    ServerImpl.java:457)
    at
    weblogic.management.internal.DynamicMBeanImpl.setParent(DynamicMBeanImpl.jav
    a:264)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
    .java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.
    java:1651)
    at
    weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.
    java:1101)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Configurati
    onMBeanImpl.java:311)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:135
    8)
    at
    com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:133
    3)
    at
    weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanS
    erverImpl.java:367)
    at
    weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
    at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
    t.java:353)
    at
    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
    0)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    This is how i'm trying to add it.
    here i'm creating the JMS Topic
    java weblogic.Admin -url %ADMIN_URL% -username %WLS_USER% -password%WLS_PW%
    CREATE -mbean %WLS_DOMAIN%:Name=%JMSTopic%,Type=JMSTopic
    Exception is thrown while trying to execute this code
    @ECHO Setting Properties
    java weblogic.Admin -url %ADMIN_URL% -username %WLS_USER% -password%WLS_PW%
    SET -mbean
    %WLS_DOMAIN%:Location=%WLS_SERVER%,Name=%JMSTopic%,Type=JMSTopic -property
    Parent %WLS_DOMAIN%:Name=%JMSServer%,Type=JMSServer
    can anyboy point me where i'm missing some entries??
    Thanks and regards
    sasi

  • Weblogic.management.NoAccessRuntimeException: Cannot perform the requested

    Hi,
    I am using WLES 4.2 with WebLogic 8.1 SP4 Portal domain.
    Managed Servers are not running, Admin server starts normally, when i try to access WebLogic Admin Console i get below exception. Any idea what could be the root cause?????
    weblogic.management.NoAccessRuntimeException: Cannot perform the requested operation, the request was from an anonymous user (Principal)
    at weblogic.management.mbeans.custom.Cluster.getServers(Cluster.java:76)
    at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:604)
    at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:179)
    at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1186)
    at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1156)
    at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:288)
    at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:610)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:442)
    at weblogic.management.configuration.ClusterMBean_Stub.getServers(ClusterMBean_Stub.java:1168)
    at weblogic.management.console.utils.MBeans.getServersFor(MBeans.java:692)
    at weblogic.management.console.webapp._domain.__nav._jspService(__nav.java:1507)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:322)
    at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:150)
    at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
    at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6718)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >

    Did you ever find resolution to this? We are encountering the listed exception every 10 minutes in the logs and have yet to identify the source.

  • Weblogic.management.NoAccessRuntimeException in wl 8.1 sp1

    I am trying to deploy my application ear file and I get the above exception. Here
    is the traceback:
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
    pr
    incipals=[], on ResourceType: WebAppComponent Action: execute, Target: addActiva
    tedTarget
    at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.j
    ava:108)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at weblogic.management.internal.RemoteMBeanServerImpl_811_WLStub.invoke(
    Unknown Source)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    at weblogic.management.configuration.WebAppComponentMBean_Stub.addActiva
    tedTarget(WebAppComponentMBean_Stub.java:3348)
    at weblogic.management.deploy.slave.CallbackHandler.updateActivatedTarge
    t(CallbackHandler.java:282)
    at weblogic.management.deploy.slave.CallbackHandler.setStatus(CallbackHa
    ndler.java:255)
    at weblogic.management.deploy.slave.CallbackHandler.endTransition(Callba
    ckHandler.java:119)
    at weblogic.j2ee.J2EEApplicationContainer.invokeCallback(J2EEApplication
    Container.java:2809)
    at weblogic.j2ee.J2EEApplicationContainer.invokeCallbacks(J2EEApplicatio
    nContainer.java:2820)
    at weblogic.j2ee.J2EEApplicationContainer.endCallbacks(J2EEApplicationCo
    ntainer.java:2828)
    at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplication
    Container.java:3025)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
    ner.java:2076)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
    ner.java:2057)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
    ner.java:2005)
    Thanks in advance.
    Mahendra Gharpuray

    Hi,
    This exception indicates that a permission check is failing because
    someone is connecting anonymously to a resource that is protected.
    Are you running into this problem when someone tries to
    use your application or when you initially try to deploy your
    application?
    If it's a problem when some tries to use your application,
    you need to properly setup the permissions for your application.
    For example, if you want to allow anonymous access, you
    need to grant permission to "everyone".
    See http://e-docs.bea.com/wls/docs81/secwlres/index.html
    If it's a problem when you initally try to deploy your
    application (vs. use your application), what mechanism are
    you using to deploy your application? The console?
    Also, when you deploy your application, you do it as
    some user. What groups is that user in? Adminstator? Deployer?
    Thanks, -tm
    "Mahendra" <[email protected]> wrote in message
    news:[email protected]...
    >
    I am trying to deploy my application ear file and I get the aboveexception. Here
    is the traceback:
    weblogic.management.NoAccessRuntimeException: Access not allowed forsubject:
    pr
    incipals=[], on ResourceType: WebAppComponent Action: execute, Target:addActiva
    tedTarget
    atweblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.j
    ava:108)
    atweblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
    at weblogic.management.internal.RemoteMBeanServerImpl_811_WLStub.invoke(
    Unknown Source)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    atweblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
    xy.java:481)
    atweblogic.management.configuration.WebAppComponentMBean_Stub.addActiva
    tedTarget(WebAppComponentMBean_Stub.java:3348)
    atweblogic.management.deploy.slave.CallbackHandler.updateActivatedTarge
    t(CallbackHandler.java:282)
    at weblogic.management.deploy.slave.CallbackHandler.setStatus(CallbackHa
    ndler.java:255)
    atweblogic.management.deploy.slave.CallbackHandler.endTransition(Callba
    ckHandler.java:119)
    atweblogic.j2ee.J2EEApplicationContainer.invokeCallback(J2EEApplication
    Container.java:2809)
    atweblogic.j2ee.J2EEApplicationContainer.invokeCallbacks(J2EEApplicatio
    nContainer.java:2820)
    atweblogic.j2ee.J2EEApplicationContainer.endCallbacks(J2EEApplicationCo
    ntainer.java:2828)
    atweblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplication
    Container.java:3025)
    atweblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
    ner.java:2076)
    atweblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
    ner.java:2057)
    atweblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
    ner.java:2005)
    Thanks in advance.
    Mahendra Gharpuray

  • EJB 3.0, BC4J and weblogic managed server

    Hi, I've got a problem using EJB 3.0 with a BC4J Application module in a weblogic managed server.
    My bean is a stateless session bean that use BC4J for database transaction.
    When I call the bean the first time, It returns de values I need, without problem. If I do the same call again, I always get "null". I deployed the same bean on the AdminServer, linking to the same DataSource, It works fine and I never got a null result.
    My application module is created insid my EJB abstract class by :
    _am = (BaseServiceImpl)Configuration.createRootApplicationModule(adfModel, adfConfiguration);*
    Where adfModel and adfConfiguration are configured through annotations in my EJB Implementation.
    In my abstract EJB, I have a methode with a +@PreDestroy+ method like that :
    +@PreDestroy+
    *protected void releaseModele() {*
    *if (_am != null) {*
    Configuration.releaseRootApplicationModule(_am, false);
    _am = null;*
    My Data Source on the server is defined as Supporting Global Transaction, one-phase commit. I activated the BC4J Logs on the server to see what was going on and I see that the JDBC seems to close after the first call :
    *** closing jdbc connection now **** (weblogic.jdbc.wrapper.JTSConnection_oracle_jdbc_driver_T4CConnection@0)
    And that is when I've got the error on the server :
    oracle.jbo.InvalidObjAccessException: JBO-25036: An invalid object operation was invoked on type View Object with name AppModAD
    So, my JDBC connection seems to close somewhere beetween the first and the second call, but only on a managed server... Someone has ever encountered a problem like that?
    Maybe there is something with the configuration of a datasource on a managed server? Or with the lifecycle of an

    The solution was to NOT have glabal transaction checked in the configuration of the data-source and "Failover Transaction State Upon Managed Release" uncked in the configuration of the Business component configuration.

  • Oracle Identity Manager Configuration Error

    Versions I have used for the Installation:
    Software Version
    Oracle Database 11.2.0
    Repository Creation Utility 11.1.1.5.0
    Web logic 10.3.6
    SOA Suite 11.1.1.6.0
    Fusion Middle ware Installer 11.1.1.5.0
    JDK Oracle Web-logic JRockit JDK or Sun JDK 1.6.0_29
    Error : Config Action Oracle Identity Manager Configuration failed
    Exception waring occurs in web logic Server :
    <Aug 14, 2012 11:57:53 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Ser
    ver started in RUNNING mode>
    <Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141239> <The no
    n-dynamic attribute AuthenticationProviders on weblogic.management.security.Real
    mMBeanImpl@581c390c([OIDM]/SecurityConfiguration[OIDM]/Realms[myrealm]) has been
    changed. This may require redeploying or rebooting configured entities>
    <Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141238> <A non-
    dynamic change has been made which affects the server AdminServer. This server m
    ust be rebooted in order to consume this change.>
    <Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141239> <The no
    n-dynamic attribute ControlFlag on weblogic.security.providers.authentication.De
    faultAuthenticatorMBeanImpl@80d076be([OIDM]/SecurityConfiguration[OIDM]/Realms[m
    yrealm]/AuthenticationProviders[DefaultAuthenticator]) has been changed. This ma
    y require redeploying or rebooting configured entities>
    <Aug 14, 2012 12:03:49 PM GMT+05:30> <Warning> <Management> <BEA-141238> <A non-
    dynamic change has been made which affects the server AdminServer. This server m
    ust be rebooted in order to consume this change.>
    Please give me a solution to resolve the issue

    Each version has its won libraries and certain bug fixes. It's always good to see certification matrix first for any software and proceed with installation as per certified components. Also, vendor support your project only if you are using their certified versions. :)
    regards,
    GP

  • Why 2 floating IP's are used to Weblogic managed servers?

    In the configuration example discussed in this guide, two floating addresses
    are used to each of the WebLogic Managed Servers and to the Administration
    Server. The first type of floating IP address uses the IPoIB (BOND0) interface,
    and the second type of floating IP uses the EoIB (BOND1) interface.
    The above are excerpts from this document: http://docs.oracle.com/cd/E18476_01/doc.220/e18479.pdf page 3-10
    My question is, why do I have to use 2 floating IP's, one uses bond0 and the other uses bond1? can I just create one floating on bond1 and for all purposes, for instance? For what reasons, do I have to use 2 floating IP's?
    Thanks!
    Edited by: 943714 on Jan 29, 2013 12:01 PM

    Hi,
    Two floating IP's should be used because on an Exalogic machine there are multiple network interfaces. As it says on that document, bond0 is for IPoIB and bond1 is EoIB.
    bond1 is the interface available outside the Exalogic machine. But, for example, if you need to connect to an Exadata machine (using Weblogic with JDBC/GridLink) that must be done through InfiniBand (IPoIB - bond0 interface).
    Hope this helps.
    -Cris

  • Weblogic managed service not starting up after Windows restart

    Hi All
    I have an issue with start up of Managed instances configured as windows service. When we reboot the machine the services which are configured to be automatically start are not starting up. When I manually start them they would just run fine. I have no clue why this is happening. We have our applications running on Weblogic Server 8.1 SP6
    I already tried the following method stated in this URL http://www.javagalaxy.com/forum/viewtopic.php?f=8&t=188? and had no luck with the service start up.
    Can someone please guide me through what I can do to fix this issue.
    Thanks in advance for help.
    Edited by: user4970372 on May 7, 2010 7:28 AM

    I did enable the log and see the same error
    <May 19, 2010 1:07:00 PM CDT> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.security.internal.encryption.EncryptionServiceException - with nested exception:
    [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
    com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
         at com.rsa.jsafe.JA_PKCS5Padding.a([BIILjava.lang.Object;)I(Unknown Source)
         at com.rsa.jsafe.JG_BlockCipher.decryptFinal([BI)I(Unknown Source)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
         at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:56)
         at weblogic.management.EncryptionHelper.decryptString(EncryptionHelper.java:45)
         at weblogic.ldap.EmbeddedLDAP.initServerConfig(EmbeddedLDAP.java:1147)
         at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:231)
         at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:815)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
         at weblogic.Server.main(Server.java:32)
    --------------- nested within: ------------------
    weblogic.security.internal.encryption.EncryptionServiceException - with nested exception:
    [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:77)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
         at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:56)
         at weblogic.management.EncryptionHelper.decryptString(EncryptionHelper.java:45)
         at weblogic.ldap.EmbeddedLDAP.initServerConfig(EmbeddedLDAP.java:1147)
         at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:231)
         at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:815)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
         at weblogic.Server.main(Server.java:32)
    >
    <May 19, 2010 1:07:00 PM CDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.security.internal.encryption.EncryptionServiceException - with nested exception:
    [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]>
    The WebLogic Server did not start up properly.
    com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
         at com.rsa.jsafe.JA_PKCS5Padding.a([BIILjava.lang.Object;)I(Unknown Source)
         at com.rsa.jsafe.JG_BlockCipher.decryptFinal([BI)I(Unknown Source)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:67)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
         at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:56)
         at weblogic.management.EncryptionHelper.decryptString(EncryptionHelper.java:45)
         at weblogic.ldap.EmbeddedLDAP.initServerConfig(EmbeddedLDAP.java:1147)
         at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:231)
         at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:815)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
         at weblogic.Server.main(Server.java:32)
    --------------- nested within: ------------------
    weblogic.security.internal.encryption.EncryptionServiceException - with nested exception:
    [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:77)
         at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:93)
         at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:56)
         at weblogic.management.EncryptionHelper.decryptString(EncryptionHelper.java:45)
         at weblogic.ldap.EmbeddedLDAP.initServerConfig(EmbeddedLDAP.java:1147)
         at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:231)
         at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:815)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
         at weblogic.Server.main(Server.java:32)
    Reason: weblogic.security.internal.encryption.EncryptionServiceException - with nested exception:
    [com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.]
    ***************************************************************************

  • Weblogic Managed Server not starting from the ./startManagedWebLogic.sh

    We have installed weblogic 9.2 in unix environment, and created one admin server and a managed server
    My admin server is in running state, while starting the managed server, the folllowing message is showing
    <Jun 18, 2010 1:30:45 PM BST> <Info> <MessagingBridge> <BEA-200001> <The messaging bridge service has successfully shut down.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JMS> <BEA-040308> <JMS service is suspending.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JMS> <BEA-040107> <Undeployed 8 default connection factories.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JMS> <BEA-040015> <JMS shutdown is complete.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001144> <Force Suspending the JDBC service.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001146> <Force suspend of the JDBC service completed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001147> <Shutting down the JDBC service.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001149> <Shutdown of the JDBC service completed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <Cluster> <BEA-000103> <Disconnecting fromcluster dcsCLSv1>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <WebLogicServer> <BEA-000236> <Stopping execute threads.>
    I have started my server in the following ways.
    from the weblogic/user_projects/V1.3.0/dsDOMv/bin directory
    bash-3.00$ ./startManagedWebLogic.sh dREGv1
    bash-3.00$ tail -f /weblogic/user_projects/V1.3.0/dsDOMv/logs/dREGv1startWeblogic.sh
    We have configured commomn user name for all admin and managed servers.
    Please reply.........

    The following is the managed server logs. i have stoped the server manually from weblogic console( from control tab and click on shutdown by force) om 18th June at 1:30:37. The following is the managed servers log
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Server> <BEA-002640> <A request has been received to force shut down of the server.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Server> <BEA-002638> <Force shutdown was issued remotely from 127.0.0.1>
    <Jun 18, 2010 1:30:37 PM BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
    <Jun 18, 2010 1:30:37 PM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Cluster> <BEA-000158> <Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module scheduler.jar of application scheduler is transitioning from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149060> <Module scheduler.jar of application scheduler successfully transitioned from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module /edcsschedulerapp of application scheduler is transitioning from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149060> <Module /edcsschedulerapp of application scheduler successfully transitioned from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module edcsejb.jar of application coreedcs is transitioning from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149060> <Module edcsejb.jar of application coreedcs successfully transitioned from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module /edcsapp of application coreedcs is transitioning from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149060> <Module /edcsapp of application coreedcs successfully transitioned from STATE_ACTIVE to STATE_ADMIN on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jun 18, 2010 1:30:37 PM BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Jun 18, 2010 1:30:37 PM BST> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 10.235.3.40:7221 was shutdown.>
    <Jun 18, 2010 1:30:37 PM BST> <Notice> <Server> <BEA-002607> <Channel "Default[1]" listening on 156.150.200.190:7221 was shutdown.>
    <Jun 18, 2010 1:30:37 PM BST> <Notice> <Server> <BEA-002607> <Channel "Default[2]" listening on 127.0.0.1:7221 was shutdown.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <WebLogicServer> <BEA-000256> <Invoking bea.jolt.pool.servlet.weblogic.PoolManagerShutDown.main(null)>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Diagnostics> <BEA-320002> <The Diagnostics subsystem is stopping on Server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <JMX> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://10.235.3.40:7221/jndi/weblogic.management.mbeanservers.runtime .>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <WebService> <BEA-220028> <Web Service reliable agents are suspended.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <WebService> <BEA-220029> <Web Service reliable agents are shut down.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <SAFService> <BEA-281004> <SAF Service has been suspended.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <SAFService> <BEA-281005> <SAF Service has been shut down.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module scheduler.jar of application scheduler is transitioning from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149060> <Module scheduler.jar of application scheduler successfully transitioned from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module /edcsschedulerapp of application scheduler is transitioning from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <ServletContext-/edcsschedulerapp> <000000> <Closing Spring root WebApplicationContext>
    <Jun 18, 2010 1:30:37 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/webapp/edcsschedulerapp/17126420/comp). Unbinding it.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149060> <Module /edcsschedulerapp of application scheduler successfully transitioned from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:37 PM BST> <Info> <Deployer> <BEA-149059> <Module edcsejb.jar of application coreedcs is transitioning from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <Deployer> <BEA-149060> <Module edcsejb.jar of application coreedcs successfully transitioned from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <Deployer> <BEA-149059> <Module /edcsapp of application coreedcs is transitioning from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <ServletContext-/edcsapp> <000000> <Closing Spring root WebApplicationContext>
    <Jun 18, 2010 1:30:43 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/webapp/edcsapp/14679463/comp). Unbinding it.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <Deployer> <BEA-149060> <Module /edcsapp of application coreedcs successfully transitioned from STATE_ADMIN to STATE_PREPARED on server dcsREGv1.>
    <Jun 18, 2010 1:30:43 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/ejb/scheduler.jar#EDCSSchedulerTransManagerBean/comp). Unbinding it.>
    <Jun 18, 2010 1:30:43 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/ejb/edcsejb.jar#EDCSREFMessageListenerBean/comp). Unbinding it.>
    <Jun 18, 2010 1:30:43 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/ejb/edcsejb.jar#EDCSEventTransManagerBean/comp). Unbinding it.>
    <Jun 18, 2010 1:30:43 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/ejb/edcsejb.jar#EDCSERSMessageListenerBean/comp). Unbinding it.>
    <Jun 18, 2010 1:30:43 PM BST> <Debug> <J2EE> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/ejb/edcsejb.jar#EDCSReportMessageListenerBean/comp). Unbinding it.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JMS> <BEA-040324> <JMSServer "InMemoryObjectJMSServerREGv1" is suspending.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JMS> <BEA-040325> <JMSServer "InMemoryObjectJMSServerREGv1" is suspended.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JMS> <BEA-040324> <JMSServer "ERSJMSServer" is suspending.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JMS> <BEA-040325> <JMSServer "ERSJMSServer" is suspended.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001514> <Destroying Data Source dcsDSdiagReadOnly.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001515> <Data Source dcsDSdiagReadOnly has been successfully destroyed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001508> <Destroying Connection Pool dcsDSdiagReadOnly.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:43 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiagReadOnly" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001126> <Destroyed Connection Pool named dcsDSdiagReadOnly.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001514> <Destroying Data Source dcsDSdiag.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001515> <Data Source dcsDSdiag has been successfully destroyed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001508> <Destroying Connection Pool dcsDSdiag.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "dcsDSdiag" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001126> <Destroyed Connection Pool named dcsDSdiag.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001514> <Destroying Data Source InMemoryJDBCDataSource.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001515> <Data Source InMemoryJDBCDataSource has been successfully destroyed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001508> <Destroying Connection Pool InMemoryJDBCDataSource.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:44 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001128> <Connection for pool "InMemoryJDBCDataSource" closed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001126> <Destroyed Connection Pool named InMemoryJDBCDataSource.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <MessagingBridge> <BEA-200001> <The messaging bridge service has successfully shut down.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JMS> <BEA-040308> <JMS service is suspending.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JMS> <BEA-040107> <Undeployed 8 default connection factories.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JMS> <BEA-040015> <JMS shutdown is complete.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001144> <Force Suspending the JDBC service.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001146> <Force suspend of the JDBC service completed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001147> <Shutting down the JDBC service.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <JDBC> <BEA-001149> <Shutdown of the JDBC service completed.>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <Cluster> <BEA-000103> <Disconnecting from cluster dcsCLSv1>
    <Jun 18, 2010 1:30:45 PM BST> <Info> <WebLogicServer> <BEA-000236> <Stopping execute threads.>
    But i tried to restart the server today(21st may).
    From the admin server log says the following.
    [JMSMigrate] : Current hosting server dcsREGv1 is down
    [JMSMigrate] : Try to migrate...
    [JMSMigrate] : Candidate server dcsREGv1 is not runing
    [JMSMigrate] : Start Sleeping.......... End Sleeping
    Yes, Managed Server and AdminServer resides on the Same Physical Box.
    Thansk in advance.....

  • Weblogic.management.ApplicationException

    I am trying to deploy a .war file , which use to work perfectly fine in weblogic
    6.1 . While deploying it in weblogic7.0 i am getting following error
    weblogic.management.ApplicationException: No modules to prepare on ahfServerfor
    application named antAhf1
    Start server side stack trace:
    weblogic.management.ApplicationException: No modules to prepare on ahfServerfor
    application named antAhf1
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:536)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    End server side stack trace
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:536)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

    Your application is configured for session replication in weblogic.xml. See http://e-docs.bea.com/wls/docs81/webapp/sessions.html for more information.
    From the error message, it appears that you don't have a cluster. You'll either have to build a cluster or remove the session persistence stuff from weblogic.xml.
    Mike
    Weblogic/J2EE Security Blog: http://monduke.com

  • Error deploying EAR - weblogic.management.ApplicationException:None

    Hello,
    When deploying a EAR, I get the following exception:
    [Deployer:149033]preparing application esb on <xxx-admin>
    [Deployer:149033]failed application esb on <xxx-admin>
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application esb on <xxx-admin>.: Exception:weblogic.management.ApplicationException: None
    Nested Exception:
    java.lang.RuntimeException: Failed to deploy process <ProcessName.jpd>. Internal error.
    at com.bea.wli.management.WLIAppListener.checkProject(WLIAppListener.java:194)
    at com.bea.wli.management.WLIAppListener.initializingApplication(WLIAppListener.java:130)
    at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:42)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    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.prepare(J2EEApplicationContainer.java:986)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    I am not able to get anything out this. Can someone help me please?
    Thanks.
    Prabhu

    HI prabhusethuraman,
    We have an error than seems the same error that you has before, the stack trace when we deploy the whorkshop application that is this one:
    [java] Initiated Task: [7] [Deployer:149026]Deploy application q99j on integracion.
    [java] Task 7 failed: [Deployer:149026]Deploy application q99j on integracion.
    [java] Deployment failed on Cluster integracion
    [java] Exception:weblogic.management.ApplicationException: None
    [java] Nested Exception:
    [java] java.lang.RuntimeException: Failed to deploy process /q99jdummyDynamicRouterProcess/com/ejie/notifications/Q99jNotificationsP.jpd. Internal error.
    [java]      at com.bea.wli.management.WLIAppListener.checkProject(Lcom.bea.wli.management.processmanifest.ProcessManifestDocument$ProcessManifest$Project;Lweblogic.application.ApplicationLifecycleEvent;)Z(WLIAppListener.java:194)
    [java]      at com.bea.wli.management.WLIAppListener.initializingApplication(Lweblogic.application.ApplicationLifecycleEvent;)V(WLIAppListener.java:130)
    [java]      at weblogic.j2ee.ListenerInvocationAction.run()Ljava.lang.Object;(ListenerInvocationAction.java:42)
    [java]      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Optimized Method)
    [java]      at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
    [java]      at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(ILweblogic.application.ApplicationLifecycleListener;)V(J2EEApplicationContainer.java:4721)
    [java]      at weblogic.j2ee.J2EEApplicationContainer.notify(I)V(J2EEApplicationContainer.java:4706)
    [java]      at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1006)
    [java]      at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2444)
    [java]      at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2394)
    [java]      at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2310)
    [java]      at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
    [java]      at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
    [java]      at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
    [java]      at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
    [java]      at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
    [java]      at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
    [java]      at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
    [java] java.lang.Exception: Delta :26 ErrorMessage :
    Can you say us the solution that you found in your case ?
    Thanks,
    Carmel.

  • Weblogic.management.descriptors.ejb11.BackendLogMBean

    Hello people,
    When I start WL 6.1sp2 on NT, I get this exception. It worked before, and I'm not
    aware of any change. The class is not in my weblogic.jar -- should it be?
    There's no .wlnotdelete/ in applications/
    Starting WebLogic Server ....
    <29.05.2002 07:20:14 CEST> <Notice> <Management> <Loading configuration file .\config\ffpDomain\config.xml
    ..>
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.reflect.InvocationTargetException: java.lang.ClassNotFoundException: weblogic.management.descriptors.ejb11.BackendLogMBean
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:195)
    at weblogic.management.internal.Helper.findClass(Helper.java:812)
    at weblogic.management.internal.Helper.getAdminOrConfigMBeanInfo(Helper.java:103)
    at weblogic.management.internal.ConfigurationMBeanImpl.<init>(ConfigurationMBeanImpl.java:108)
    at java.lang.reflect.Constructor.newInstance(Native Method)
    at weblogic.management.internal.Helper.createMBean(Helper.java:366)
    at weblogic.management.internal.Helper.createAdminMBean(Helper.java:291)
    at weblogic.management.internal.RemoteMBeanServerImpl.createAdminMBean(RemoteMBeanServerImpl.java:278)
    at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.createAdminMBean(ConfigurationParse
    r.java:262)
    at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.startElement(ConfigurationParser.ja
    va:183)
    at weblogic.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1340)
    at weblogic.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1183)
    at weblogic.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1876)
    at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1252)

    Sorry, I miss the right the subject.
    Look for the same message but with the following subject:
    error deploying ejb on wl8.1sp2: trace not help
    regards,
    pedro salazar.

  • SAP Solution Manager : Incident Management Configuration

    Hi All,
    Can you please help me out in Incident Management Configuration in Solution Manager?
    Please give me the process flow in the incident management in SolMan.
    Regards,
    Shyjith.K

    Hi,
    /people/bruyneel.guillaume/blog/2008/05/02/service-desk-implementation-guide-part-i
    /people/bruyneel.guillaume/blog/2008/06/13/service-desk-implementation-guide-part-ii
    /people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
    https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000722612&_OBJECT=011000358700000122472008E
    /people/dolores.correa/blog/2007/10/06/service-desk-support-team-determination
    Weblogs related to SolMan
    https://wiki.sdn.sap.com/wiki/display/SM/Weblogs%20related%20to%20Solution%20Manager
    Regards,
    Shyam

Maybe you are looking for