Managed server logs
When you fire up the NodeManager, and start up managed servers from the web
console, where do the logs of the respective servers go? I couldn't seem to
find anything telling in my domain directory when I looked.
Thanx!
Regards,
Will Hartung
([email protected])
Will,
You're going to actually see three different types of logs when you use the
NM:
1. The Node Manager log files which contain NM specific entries.
2. The Managed Server log files which contain the managed server specific
info such as you're used to seeing from stdout, stderr when you start the
server from the command line. Also you'll find additional info such as the
server's PID, and copy of the server's configuration called
nodemanager.config
3. Node Manger client logs which reside on the admin server and contain
subdirectories for each managed server issued a NM command.
You won't see these last two log file types or their subdirectories until
you actually use the NM to start the managed servers. All of these logs
however, are stored in a parent subdirectory called NodeManagerLogs. By
default this directory is created in the directory where you called
startNodeManager[.cmd .sh] from. So if I ran . startNodeManager.sh from
mydomain then I would see
$BEA_HOME/user_projects/domains/mydomain/NodeManagerLogs
The easiest way I have found to deal with this is to ensure that
$WL_HOME/server/bin is in your PATH and simply call . startNodeManager.sh
from the directory you want the logs to be created in --of course with the
appropriate arguments or values in nodemanger.properties--
but remember the NM defaults to $WL_HOME/common/nodemanager so you may see
the logs under their initially.
//provide a follow up if any of that didn't make sense :)
~RU
"Will Hartung" <[email protected]> wrote in message
news:[email protected]...
> When you fire up the NodeManager, and start up managed servers from the
web
> console, where do the logs of the respective servers go? I couldn't seem
to
> find anything telling in my domain directory when I looked.
>
> Thanx!
>
> Regards,
>
> Will Hartung
> ([email protected])
>
>
Similar Messages
-
Hello All,
Can someone point me to where the log(s) may be?Found them, so please disregard.
-
Error while starting the managed server using nodemanager
HI ,
I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
Below is the error in the managed server log,
startWebLogic.sh: grep: not found
startWebLogic.sh: uname: not found
startWebLogic.sh: test: argument expected
can you help me to solve the problem please. i am using weblogic 10.3.3
thanks
ArunI think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?
-
Unable to start Manager server using Node Manager
Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager. -
Error when starting managed server
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, PerHi Per
I have problems in creating managed server in the default mydomain .Do i need
to configure a new machine if the managed server and admin server are going to be
in the same machine.
I created a new machine that has the following parameters
listen address :localhost
Listen port :7001
As the next step i created a server with the machine name pointing to new one, when
i tried to start this as a managed server it gives an Error
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: java
.security.acl.NotOwnerException - with nested exception:
[java.lang.IllegalAccessError: java.security.acl.NotOwnerException]
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:12
5)
could you please help me on creating a managed server
thanks in advance
karthik
[email protected] (Per Olesen) wrote:
Hi,
I have a setup with a admin-server and a managed server. Everything
worked fine, until one day, an exception started occurring in the logs
when starting the managed server.
The setup is:
- WLS6.1SP2
- Solaris 8, SPARC
The exception is:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
I've taken a look in the admin-servers JNDI-tree, and it is correct,
it only has "weblogic.transaction.resources", and is missing the
unresolved "atserver1" part.
Why is it suddenly referencing this, and what can/should I do about
it.
The server seems to be running even with this exception.
Full stack trace at managed server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
oid: '9', implementation: 'weblogic.jndi.interna
l.RootNamingNode@6fb3d6''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.atserver1. Resolved:
'weblogic.transaction.resources'
Unresolved:'atserver1' ; remaining name ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy6.list(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Full server stack trace in admin server log:
<10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
oid: '267', implementation: 'weblogic.management.inte
rnal.AdminMBeanHomeImpl@46cc9c''
javax.management.InstanceNotFoundException:
atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help appreciated!
Regards, Per -
Exception in Server Logs : JMSCC0033 While using Weblogic 10.3.X and MQ 7
Following exception is contuniously occuring in Weblogic Managed Server Logs after migrating to IBM MQ 7.
com.ibm.msg.client.jms.DetailedIllegalStateException: JMSCC0033: A synchronous method call is not permitted when a session is being used asynchronously: 'acknowledge' The JMS specification does not permit the use of a session for synchronous methods when asynchronous message delivery is running. Create a separate session if you wish to use both synchronous methods and asynchronous delivery simultaneously.
at sun.reflect.GeneratedConstructorAccessor43.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:516)
at com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NLSServices.java:313)
at com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLSServices.java:388)
at com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErrorUtils.java:104)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.checkSynchronousUsage(JmsSessionImpl.java:2375)
at com.ibm.msg.client.jms.internal.JmsMessageImpl.acknowledge(JmsMessageImpl.java:1559)
at com.ibm.jms.JMSMessage.acknowledge(JMSMessage.java:351)
at weblogic.ejb.container.internal.MDListener$MDMessage.acknowledge(MDListener.java:802)
at weblogic.ejb.container.internal.MDListener$1.run(MDListener.java:237)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2473)
at weblogic.ejb.container.internal.MDListener.putListener(MDListener.java:234)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:687)
at weblogic.ejb.container.internal.MDListener.run(MDListener.java:744)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)You should check with IBM Support.
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ73363
-Akshay -
Management console fails connecting to Management server.
I have installed Oracle 9.2 on Red Hat Advanced Server V2.1.
Also installed Management server and client software on the system.
Started everything up: oemctl start oms, agentctl start agent, apachectl start...
Run Manager Console on Linux machine (i.e. locally)
Runs successfully - connecting stand-alone
Runs successfully - connecting to management sever
Installed client software on a Windows NT PC.
Runs successfully - connecting stand-alone
FAILS - connecting to Management server
On another NT PC, try running web interface to Management server
FAILS - Same error as when using thick client.
Failure is the same in both cases: The exception (java.lang.NullPointerException) occured.
Failure of both of these suggested a server issue...
Don't know where to find management server logs?
Looking at $ORACLE_HOME/Apache/Apache/logs/error_log seems unable to find files, e.g.:
[Mon Nov 25 10:01:46 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/readme/emreadme.htm
[Mon Nov 25 10:01:57 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/java/awt/KeyboardFocusManager.class
[Mon Nov 25 10:02:11 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/ewt/alert/resource/AlertBundle_en
_GB.class
[Mon Nov 25 10:02:11 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/ewt/alert/resource/AlertBundle_en
_GB.properties
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/sysman/vt/console/app/ConsoleBean
Info.class
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/sun/beans/infos/ConsoleBeanInfo.class
[Mon Nov 25 10:02:15 2002] [error] [client 192.0.0.120] File does not exist: /u0
1/app/oracle/product/9.2.0/oem_webstage/oracle/sysman/emSDK/client/appContainer/
WebApplicationBeanInfo.class
I have tried reinstalling Oracle website, however this made no difference.Can you ping the server which is running OEM from the client NT machine?
Are you trying to connect using DNS or IP?
Verify that this works first. -
Server start arguments ignored when starting managed server
Hi
We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
However those arguments are not picked up when we are starting the managed server.
We are using a shell script to start the managed server using the weblogic.Admin class functionality.
If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
This is the scenario in Weblogic 10.0.0.
Can anybody please explain why the arguments are not picked up?
We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
Is the difference in behavior because of the difference in versions?
Edited by: user1030647 on Aug 29, 2010 12:26 AMThanks Jay for the immediate responses.
The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
Do you have any info which points to this discrepancy? -
Start Managed Server from Another Machine
Hello,
In a two machines cluster starting a managed on the secondary machine not the
one hosting the admin server, I keep getting the following error:
Managed server log error:
The WebLogic Server did not start up properly.
Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
not found for MBean orsus:Name=orsus,Type=Domain'
Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
not found for MBean orsus:Name=orsus,Type=Domain
Admin Server log:
<Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error
occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain.
Method: null. Exception: javax.management.AttributeNotFoundException: Attribute
AdministrationMBeanAuditingEnabled
not found for MBean orsus:Name=orsus,Type=Domain.
javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
not found for MBean orsus:Name=orsus,Type=Domain
at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
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(AuthenticatedSubject.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:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed
Server orsusClusterNode_2 is disconnected from the admin server. This may be either
due to a managed server getting temporarily partitioned or the managed server
process exiting.>
<Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest
failed
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException].
weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
Source)
at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Caused by: weblogic.utils.net.SocketResetException
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
... 2 more
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
exception:
[weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException]
at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
Source)
at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
Any ideas?
Regards.
Eran
[wlerrlog.txt]
Do both the machines have the same weblogic server installation? Looks
like there is a conflict, the machine where the managed server is
running has a weblogic server version lesser than the admin server.
Check the versions on both machines.
java weblogic.version
should print the version information.
Thanks,
-satya
eran wrote:
>
> Hello,
>
> In a two machines cluster starting a managed on the secondary machine not the
> one hosting the admin server, I keep getting the following error:
>
> Managed server log error:
> ***************************************************************************
> The WebLogic Server did not start up properly.
> Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
> not found for MBean orsus:Name=orsus,Type=Domain'
> Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
> not found for MBean orsus:Name=orsus,Type=Domain
>
>
> Admin Server log:
> <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error
> occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain.
> Method: null. Exception: javax.management.AttributeNotFoundException: Attribute
> AdministrationMBeanAuditingEnabled
> not found for MBean orsus:Name=orsus,Type=Domain.
> javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
> not found for MBean orsus:Name=orsus,Type=Domain
> at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
> at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
> at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
> at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
> at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
> at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
> 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(AuthenticatedSubject.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:30)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
> <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed
> Server orsusClusterNode_2 is disconnected from the admin server. This may be either
> due to a managed server getting temporarily partitioned or the managed server
> process exiting.>
> <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest
> failed
> weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
> exception:
> [weblogic.rjvm.PeerGoneException: ; nested exception is:
> weblogic.utils.net.SocketResetException].
> weblogic.rjvm.PeerGoneException: ; nested exception is:
> weblogic.utils.net.SocketResetException
> at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
> at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
> at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
> Source)
> at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
> at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
> at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> Caused by: weblogic.utils.net.SocketResetException
> at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
> at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
> ... 2 more
> --------------- nested within: ------------------
> weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
> exception:
> [weblogic.rjvm.PeerGoneException: ; nested exception is:
> weblogic.utils.net.SocketResetException]
> at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
> Source)
> at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
> at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
> at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
>
> Any ideas?
>
> Regards.
> Eran
>
>
>
>
> ------------------------------------------------------------------------
>
> Managed server log error:
> ***************************************************************************
> The WebLogic Server did not start up properly.
> Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain'
> Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain
> ***************************************************************************
>
>
> Admin Server log:
> <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain. Method: null. Exception: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
> not found for MBean orsus:Name=orsus,Type=Domain.
> javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain
> at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
> at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
> at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
> at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
> at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
> at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
> 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(AuthenticatedSubject.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:30)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
> <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed Server orsusClusterNode_2 is disconnected from the admin server. This may be either due to a managed server getting temporarily partitioned or the managed server process exiting.>
> <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
> weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
> [weblogic.rjvm.PeerGoneException: ; nested exception is:
> weblogic.utils.net.SocketResetException].
> weblogic.rjvm.PeerGoneException: ; nested exception is:
> weblogic.utils.net.SocketResetException
> at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
> at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
> at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown Source)
> at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
> at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
> at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
> Caused by: weblogic.utils.net.SocketResetException
> at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
> at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
> ... 2 more
> --------------- nested within: ------------------
> weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
> [weblogic.rjvm.PeerGoneException: ; nested exception is:
> weblogic.utils.net.SocketResetException]
> at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown Source)
> at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
> at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
> at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
>
-
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..... -
Starting Managed Server using Node Manager Command Line
Hi,
I've configured the Node Manager and it is connected to the Admin Server without problem. Now I wanted to start the Managed Server through the console but it is failing and my guess is the command line used syntax is not correct.
My question is, how do I change the command line that Node Manager uses to start the Managed Server? I've try using the Server Start tab configuration and it seems like not working. I've also try to update the .properties file for the Managed Server as well.
Each time I look at the Managed Server logs, it is giving me this line...
NodeManager> <Starting WebLogic server with command line: <....>
The command line shown in the logs are not what I've put in the .properties file or the Server Start tab. It is taken from somewhere and I'm not sure where. I just want to configure the command line that Node Manager uses to start a Managed Server.
Hopefully, I'm clear with my problem and someone might be able to assist. Thanks.Great stuff!!
It actually solved my problem. Thanks.
Am just wondering why it didn't work using option 1)? If anyone somehow knows the reason, if not at least it did work for me now. -
Stopping Managed Server took hours
Hi all,
I have an issue stopping the one of our managed servers (say MNG_SVR_1). It took almost 5 hrs to stop. There was no issue stopping another managed server.
In the managed server logs, I could see the following messages;
>
####<Jul 5, 2010 5:08:02 AM XXX> <Error> <Cluster> <XXXX10> <MNG_SVR_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1278364082350> <BEA-000110> <Multicast socket receive error: java.lang.ClassNotFoundException: com.bea.p13n.cache.internal.system.CacheClusterMessage: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
java.lang.ClassNotFoundException: com.bea.p13n.cache.internal.system.CacheClusterMessage: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.common.internal.WLObjectInputStream.readObjectWL(WLObjectInputStream.java:98)
at weblogic.cluster.MulticastReceiver.getNextMessage(MulticastReceiver.java:259)
at weblogic.cluster.MulticastReceiver.dispatch(MulticastReceiver.java:109)
at weblogic.cluster.MulticastManager.run(MulticastManager.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
I didn't have such issues previously. So, I am seeking some experts' advices on what went wrong.
Thanks in advance,
StephenHow was the managed server tried to be brought down. Forceful or Graceful? In case of a graceful shutdown, the managed server would be brought down only after all the active requests are processed and completed. Moreover, there's something unusual that is seen in the logs that you pasted. Is some application component deployed on only one managed server of the cluster as the logs suggest??Few logs lines previous and after to the one that you have pasted would be giving more pointers...
-
Unable to deploy artifact file to Managed Server.
In 3.0, I can deploy artifact file to Admin Server but not to an managed server. This happens with any artifact file.
Am I doing some thing wrong?
I get the following exception on the managed server log file:
java.lang.NullPointerException
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCancelCallback(DeploymentReceiverCallbackDeliverer.java:214)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$200(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$3.run(DeploymentReceiverCallbackDeliverer.java:80)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)I found an existing CR - CR345563 for this issue. It says it is a "User Error"
From someone who knows :
"There is no support to deploying artifacts from IDE to a multi-server setup. The recommended way is to export the artifacts from IDE and import them from admin console of ALDSP."
Edited by mreiche at 05/29/2008 12:23 PM -
Hi,
I am monitoring AD server from SCOM 2012 R2. My management server goes into waning state. When i run Health explorer then it come back in the healthy state but after some time it again goes into warning state. After seeing alert i found that a alert is coming
again and again i.e. Operations Manager Failed to Access the Windows Event Log.The description of alert is mention below
The Windows Event Log Provider is still unable to open the DhcpAdminEvents event log on computer 'nc2vws12ad5.corp.nathcorp.com'.
The Provider has been unable to open the DhcpAdminEvents event log for 64080 seconds.
Most recent error details: The RPC server is unavailable.
Please suggest me how to resolve this so that my management server will again come back in healthy state.
Thanks
AbhishekHi Abhishek,
As i mentioned earlier the Alert resolution says the same points.
Can you give details on the below ?
Is there really a log named "Dhcpadminevents" in the MS's Event viewer ?
Did you recently configure any new alert where you mentioned "Dhcpadminevents"
as a event log location ?
If yes then what is the target you selected for the rule / monitor there ?
Can you post the results for analysis ?
Gautam.75801 -
Error in server.log , while starting soa managed server - B2B not running
Hi All
After starting SOA managed server , we found following error in the server.log , we are successfully able to access em and admin console , but while trying to access B2B console getting no response.
Please help us in understaning this error.
[ServletContext@15501276[app:b2bui module:/b2bconsole path:/b2bconsole spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@4e8b8[ GET /b2bconsole/faces/login.jspx HTTP/1.1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Referer: http://172.16.130.34:7001/console/console.portal?_pageLabel=WebAppModuleTestingPage&_nfpb=true&WebAppModuleTestingPortletexpandNode=ROOTCHILDNODE1 Cookie: JSESSIONID=8R1ZM24XMQDs1Z22QNJ4YM1cMrGlKbd77nCTLkTW62Bkvw2nG6vx!-1614137459; ADMINCONSOLESESSION=LKZJM23fPzQQsM2GyHDHWtJ2L8nNNzmB3gNQG1n1phMwv41mJMVN!-145877631 ]] Root cause of ServletException. java.lang.NoClassDefFoundError: Could not initialize class org.apache.myfaces.trinidadinternal.convert.ColorConverter 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:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.sun.faces.application.ApplicationImpl.newConverter(ApplicationImpl.java:1114) at com.sun.faces.application.ApplicationImpl.createConverter(ApplicationImpl.java:770) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.addConverterByTargetClass(ConverterValidatorRegistrationUtils.java:164) at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.register(ConverterValidatorRegistrationUtils.java:84) at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:77) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:400) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:206) at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:329) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.<init>(FacesContextFactoryImpl.java:86) at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:64) at oracle.adfinternal.controller.application.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:56) at oracle.adfinternal.controller.application.model.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:70) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:260) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.tip.b2b.ui.util.SessionTimeoutFilter.doFilter(SessionTimeoutFilter.java:240) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:143) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
Satendra PareWhich version of weblogic and SOA suite have you installed? Which OS are you using? Check on em whether soa-infra is up?
BTW, for Oracle B2B related questions, you should raise threads in Oracle B2B forum -
Integration - B2B
Regards,
Anuj
Maybe you are looking for
-
Configure: error: cannot run C compiled programs.
Hi, I am new to Solaris. I have installed Solaris 10 and compiled packages without any error. I have tried to compile Wireshark 1.7.1 and it was exist indicating '/usr/include/sys/feature_tests.h no such file or directory'. So I have download feature
-
HT2506 How can I turn off editing feature for all pdf files?
The editing feature is annoying because when I read pdfs, I select randomly with mouse on the file, which creates "editing behavior". What' s more annoying is it saves to the pdf file directly without asking me, which causes sync services like dropbo
-
Hi sap gurus plz spare few minutues with this What is Activity type in CO how will u give link with cost center plz look into this rgds prasad
-
Creating Coherence Servers from the Admin Console
We have recently purchased and installed Coherence 12c (12.1.2) and we are having a heck of a time figuring out where to create a Coherence Server in the Admin Console. Under Environment, there is an option to for Servers, Clusters, and Coherence Cl
-
How to read text file with big5 into db
hi, how can i use UTL_FILE package to read a text file with big5 characters and insert into db? my oracle charset is AL32UTF8. thx a lot!