Server startup from console?

Hi,
I'm trying to start the weblogic server from the weblogic console. But when I
do that,
the arguments for the commandline to start the server does not match that
configured
by wlconfig. Where does the weblogic console get its settings to start a server
instance
(ie. wlconfig, startWebLogic.cmd, etc.)?
Also, I get the following exception (weblogic console message window):
The WebLogic Server did not start up properly.
Exception raised: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException:
java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(RecursiveReloadOnModifyClassLoader.java:59)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<init>(RecursiveReloadOnModifyClassLoader.java:154)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextImpl.java:1593)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:544)
at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled
Code)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:442)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:832)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(RecursiveReloadOnModifyClassLoader.java:59)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<init>(RecursiveReloadOnModifyClassLoader.java:154)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextImpl.java:1593)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:544)
at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled
Code)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:442)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:832)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
Thanx in advance,
anthony

Actually, 51sp9.
Viresh Garg wrote:
What version are you using 60 or 61 Beta?
Viresh Garg
BEA Systems
"anthony t. daga" wrote:
Hi,
I'm trying to start the weblogic server from the weblogic console. But when I
do that,
the arguments for the commandline to start the server does not match that
configured
by wlconfig. Where does the weblogic console get its settings to start a server
instance
(ie. wlconfig, startWebLogic.cmd, etc.)?
Also, I get the following exception (weblogic console message window):
The WebLogic Server did not start up properly.
Exception raised: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException:
java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(RecursiveReloadOnModifyClassLoader.java:59)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<init>(RecursiveReloadOnModifyClassLoader.java:154)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextImpl.java:1593)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:544)
at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled
Code)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:442)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:832)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method
getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:141)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:113)
at
weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:105)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(RecursiveReloadOnModifyClassLoader.java:59)
at
weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<init>(RecursiveReloadOnModifyClassLoader.java:154)
at
weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextImpl.java:1593)
at
weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:544)
at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled
Code)
at weblogic.t3.srvr.HttpServer.start(HttpServer.java:442)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:832)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:99)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
Thanx in advance,
anthony

Similar Messages

Running WL Server Instance From Console

I tried asking this under another newsgroup and haven't gotten a response.
It's been a couple of weeks, so I thought I'd try again here.
I have been working with Weblogic 5.1 for a couple of weeks now and have
gone through most of the examples without any major hickups. One problem
I'm hitting though. My weblogic.properties file is configured to deploy two
EJBs. If I start the server from the Windows start menu (I'm running on
Windows 2K), the server starts fine (the beans are deployed). Likewise, if
I use the startWeblogic.cmd, the beans are deployed correctly and the server
starts successfully. However, if I attempt to start the server from the
console, I get an error in bean deployment. The error is similar to one I
was getting a while back after I installed SP4 (I ran WLConfig and modified
startWeblogic.cmd as described in the instructions, but originally had the
SP4 boot jar in the wrong spot - I fixed this). However, when I try to
start the server from the console, I don't see the SP4 jars under classpath
and weblogic.class.path, the beans don't deploy properly and the server
startup fails. Where does the console get this information / how does it
start the server instance? I'm going to keep looking, but if this rings a
bell to anyone, I'd appreciate it.
Thanks in advance for any input.
Jim

I tried asking this under another newsgroup and haven't gotten a response.
It's been a couple of weeks, so I thought I'd try again here.
I have been working with Weblogic 5.1 for a couple of weeks now and have
gone through most of the examples without any major hickups. One problem
I'm hitting though. My weblogic.properties file is configured to deploy two
EJBs. If I start the server from the Windows start menu (I'm running on
Windows 2K), the server starts fine (the beans are deployed). Likewise, if
I use the startWeblogic.cmd, the beans are deployed correctly and the server
starts successfully. However, if I attempt to start the server from the
console, I get an error in bean deployment. The error is similar to one I
was getting a while back after I installed SP4 (I ran WLConfig and modified
startWeblogic.cmd as described in the instructions, but originally had the
SP4 boot jar in the wrong spot - I fixed this). However, when I try to
start the server from the console, I don't see the SP4 jars under classpath
and weblogic.class.path, the beans don't deploy properly and the server
startup fails. Where does the console get this information / how does it
start the server instance? I'm going to keep looking, but if this rings a
bell to anyone, I'd appreciate it.
Thanks in advance for any input.
Jim

Is there any way to clear Managed Server tmp from console or automatically?

When we undeploy, and then install a new version of a web application (Managed Server on Weblogic 12.1.2, using a deployment plan and default staging, which is copy to server), the web application still behaves like the old version. If we clear the tmp directory of the managed server beforehand, the changes are correctly reflected, which is fine if you have access.
But the issue is: We want to give developers deployment access to the admin Server (so they test their application in a representive environment), but we do not want them doing anything on the underlying OS.
I have googled, checked in books and searched in the console, but I have not yet found any way to force Weblogic to clear its temporary space automatically with every restart or deployment, nor any option to do this manually from the console (which a deployer could then do himself).
Am I overlooking something obvious? How would you get around this issue?
Thanks for any hints or answers & Cheers!
Bogoy

Thanks all,
"nostage" isn't really a current option, as it requires the deployment to be deployed to the filesystem - which again means the user needs access to the OS, or then some deployment staging area needs to be set up having some script distribute the deployment to all the machines it needs to be located on, respectivley to a shared mount.
Appearantly the tmp directory is not cleaned up in all situations.
Oracle Support is trying to tell me, that this not a bug.
If that where so, this somehow invalidates the purpose of the default "deployer" role in weblogic, with which a admin console user can only monitor and deploy applications, but does not have admin access, as this user will always also need access to the OS. I fail to see how this would be by design, if clearing tmp or giving the option to do so in weblogic, would allow for console only deployer functionality.
Scripting deletion of the directoy may be a workaround, but due to different setups it might be a hassle and such a script would also still not be invokable for the deployer on the console as long as we are running nodemanager in java-based mode. (changing this to script-mode is not possible short term)
But much appreciated input - thanks

Start managed server from console?

If I try to start a new weblogic 10.3 managed server from the console then i get this error:
"The server myserver does not have a machine associated with it.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?

Hi,
To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
Following are the steps:
1) Create a Managed Server (MS-1)
2) Create a Machines (MachineA)
3) In the above created MachineA add the MS-1 which can be done from the below console path
Console Path:
Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
Path:
wlserver_10.3/server/bin/
5) Now you can try to start your MS-1 using the Admin Console.
Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
Topic: NodeManager is not reachable
http://middlewaremagic.com/weblogic/?p=5205
Topic: Common NodeManager Issues in WebLogic
http://middlewaremagic.com/weblogic/?p=2887
Regards,
Ravish Mody

Restarting J2EE server nodes from Developer Studio Vs SAP Management Consol

Hi,
What makes the difference between restarting server nodes from Dev Studio and SAP Management console.
Please let me know if any documents related to this.
Thanks

Thanks for your quick reply.
I observed that options for restarting services from Dev Studio are disabled.
Could you please let me know where we need to configure to enable these options when right click on server instances.
Thanks

Upgrading a 10.3.2 portal application to 10.3.6 - server startup error

Hi,
I have upgraded from weblogic portal 10.3.2 to 10.3.6. I have followed the necessary steps required for this upgrade. However, I am facing issue in server startup after this. The stack trace reads :
Dec 10, 2013 5:13:11 AM EST> <Notice> <DeploymentRequestTimeoutLogger> <BEA-000000> <[DeploymentService:290051]The commit message for the deployment '1,386,670,091,597' could not be completed because the deployment timed out. : Targets to respond : [AdminServer]>
<Dec 10, 2013 5:13:11 AM EST> <Notice> <DeploymentRequestTimeoutLogger> <BEA-000000> <ThreadDumps on servers [AdminServer]{
ThreadDump for AdminServer<
"Store opaCache Spool Thread" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
net.sf.ehcache.store.DiskStore.spoolThreadMain(DiskStore.java:556)
net.sf.ehcache.store.DiskStore.access$600(DiskStore.java:59)
net.sf.ehcache.store.DiskStore$SpoolThread.run(DiskStore.java:990)
"Store userCache Expiry Thread" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
net.sf.ehcache.store.DiskStore.expiryThreadMain(DiskStore.java:831)
net.sf.ehcache.store.DiskStore.access$700(DiskStore.java:59)
net.sf.ehcache.store.DiskStore$ExpiryThread.run(DiskStore.java:1008)
"Store userCache Spool Thread" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
net.sf.ehcache.store.DiskStore.spoolThreadMain(DiskStore.java:556)
net.sf.ehcache.store.DiskStore.access$600(DiskStore.java:59)
net.sf.ehcache.store.DiskStore$SpoolThread.run(DiskStore.java:990)
"Timer-7" waiting for lock java.util.TaskQueue@13f02d4 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
java.util.TimerThread.mainLoop(Timer.java:483)
java.util.TimerThread.run(Timer.java:462)
"GC Daemon" waiting for lock sun.misc.GC$LatencyLock@1d2e34d TIMED_WAITING
java.lang.Object.wait(Native Method)
sun.misc.GC$Daemon.run(GC.java:100)
"Timer-6" waiting for lock java.util.TaskQueue@4910a9 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-5" waiting for lock java.util.TaskQueue@e4fcbc TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-4" waiting for lock java.util.TaskQueue@18ca55b TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@8c1627 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1b9a044 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1c21cbf WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@14a117f WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@59fb35 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@6de8b3 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@34ba01 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1216186 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@a1aeaa WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1e6f458 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@9e2d71 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock com.sun.jmx.remote.internal.ArrayNotificationBuffer@bc1d09 TIMED_WAITING
java.lang.Object.wait(Native Method)
com.sun.jmx.remote.internal.ArrayNotificationBuffer.fetchNotifications(ArrayNotificationBuffer.java:417)
com.sun.jmx.remote.internal.ArrayNotificationBuffer$ShareBuffer.fetchNotifications(ArrayNotificationBuffer.java:209)
com.sun.jmx.remote.internal.ServerNotifForwarder.fetchNotifs(ServerNotifForwarder.java:258)
javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1227)
javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1225)
java.security.AccessController.doPrivileged(Native Method)
javax.management.remote.rmi.RMIConnectionImpl.fetchNotifications(RMIConnectionImpl.java:1233)
javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:129)
oracle.net.ns.Packet.receive(Packet.java:300)
oracle.net.ns.DataPacket.receive(DataPacket.java:106)
oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:315)
oracle.net.ns.NetInputStream.read(NetInputStream.java:260)
oracle.net.ns.NetInputStream.read(NetInputStream.java:185)
oracle.net.ns.NetInputStream.read(NetInputStream.java:102)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:124)
oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:80)
oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1137)
oracle.jdbc.driver.T4CMAREngine.unmarshalCLR(T4CMAREngine.java:1755)
oracle.jdbc.driver.T4CMAREngine.unmarshalCLR(T4CMAREngine.java:1718)
oracle.jdbc.driver.T4CMAREngine.unmarshalCLR(T4CMAREngine.java:1711)
oracle.jdbc.driver.T4CVarcharAccessor.unmarshalOneRow(T4CVarcharAccessor.java:206)
oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:933)
oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:853)
oracle.jdbc.driver.T4C8Oall.readRXD(T4C8Oall.java:712)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:340)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884)
oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289)
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3593)
oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3637)
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1495)
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1868)
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@825b20 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock java.util.concurrent.CountDownLatch$Sync@164481 TIMED_WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:196)
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1011)
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1303)
java.util.concurrent.CountDownLatch.await(CountDownLatch.java:253)
weblogic.deploy.internal.targetserver.DeploymentManager.configCommitCompleted(DeploymentManager.java:664)
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commitCompleted(DeploymentServiceDispatcher.java:180)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCompletedCallback(DeploymentReceiverCallbackDeliverer.java:266)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$400(DeploymentReceiverCallbackDeliverer.java:13)
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$5.run(DeploymentReceiverCallbackDeliverer.java:111)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1feab6f WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"DynamicListenThread[Default[1]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[4]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[3]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[2]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[5]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"DynamicListenThread[Default[6]]" RUNNABLE native
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
java.net.ServerSocket.implAccept(ServerSocket.java:462)
java.net.ServerSocket.accept(ServerSocket.java:430)
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:38)
weblogic.server.channels.DynamicListenThread$SocketAccepter.accept(DynamicListenThread.java:535)
weblogic.server.channels.DynamicListenThread$SocketAccepter.access$200(DynamicListenThread.java:417)
weblogic.server.channels.DynamicListenThread.run(DynamicListenThread.java:173)
java.lang.Thread.run(Thread.java:662)
"weblogic.GCMonitor" waiting for lock java.lang.ref.ReferenceQueue$Lock@1eb9726 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
weblogic.platform.GCMonitorThread.waitForNotification(GCMonitorThread.java:88)
weblogic.platform.GCMonitorThread.run(GCMonitorThread.java:64)
"[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@159fb5c WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"Thread-16" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@107f59 WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE
sun.management.ThreadImpl.getThreadInfo1(Native Method)
sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:154)
weblogic.platform.VM15.threadDumpAsString(VM15.java:22)
weblogic.platform.VM.threadDumpAsString(VM.java:137)
weblogic.t3.srvr.JVMRuntime.getThreadStackDump(JVMRuntime.java:114)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
weblogic.management.jmx.modelmbean.WLSModelMBean.getAttribute(WLSModelMBean.java:525)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:666)
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
java.security.AccessController.doPrivileged(Native Method)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
weblogic.management.mbeanservers.internal.JMXContextInterceptor.getAttribute(JMXContextInterceptor.java:157)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$12.run(WLSMBeanServerInterceptorBase.java:326)
java.security.AccessController.doPrivileged(Native Method)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.getAttribute(WLSMBeanServerInterceptorBase.java:324)
weblogic.management.mbeanservers.internal.SecurityInterceptor.getAttribute(SecurityInterceptor.java:299)
weblogic.management.jmx.mbeanserver.WLSMBeanServer.getAttribute(WLSMBeanServer.java:279)
weblogic.management.mbeanservers.domainruntime.internal.ManagedMBeanServerConnection.getAttribute(ManagedMBeanServerConnection.java:304)
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:263)
weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:504)
weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:380)
$Proxy682.getThreadStackDump(Unknown Source)
weblogic.deploy.service.internal.adminserver.AdminRequestStatus.getThreadDumpsOnServers(AdminRequestStatus.java:2093)
weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCommitFailed(AdminRequestStatus.java:1002)
weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCommitResponses.requestTimedOut(AwaitingCommitResponses.java:42)
weblogic.deploy.service.internal.adminserver.AdminRequestImpl.requestTimedout(AdminRequestImpl.java:354)
weblogic.deploy.service.internal.RequestImpl$TimeoutMonitor.timerExpired(RequestImpl.java:242)
weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
"[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@c0dc01 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1077c9d WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@46530 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"Thread-15" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@118c09b WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"Thread-14" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@d2abb WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"Thread-13" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@709ba4 WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:676)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:751)
java.lang.Thread.run(Thread.java:662)
"Timer-3" waiting for lock java.util.TaskQueue@fa3571 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-2" waiting for lock java.util.TaskQueue@ca9d9a TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"DoSManager" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
com.octetstring.vde.DoSManager.run(DoSManager.java:433)
"VDE Transaction Processor Thread" waiting for lock com.octetstring.vde.backend.standard.TransactionProcessor@3108a4 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:367)
com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:212)
"ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" RUNNABLE native
weblogic.socket.NTSocketMuxer.getIoCompletionResult(Native Method)
weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:81)
weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@57828d WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@12e546b TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:262)
"weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@a84182 TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
java.lang.Thread.run(Thread.java:662)
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@1ab5dae WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:205)
weblogic.work.ExecuteThread.run(ExecuteThread.java:226)
"Timer-1" waiting for lock java.util.TaskQueue@64def7 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Timer-0" waiting for lock java.util.TaskQueue@6a5ea5 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"Attach Listener" RUNNABLE
null
"Signal Dispatcher" RUNNABLE
null
"Finalizer" waiting for lock java.lang.ref.ReferenceQueue$Lock@16bd831 WAITING
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" waiting for lock java.lang.ref.Reference$Lock@13e8914 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
"main" waiting for lock weblogic.t3.srvr.T3Srvr@99b1ec WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:981)
weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:490)
weblogic.Server.main(Server.java:71)
>
>
<Dec 10, 2013 5:13:11 AM EST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application xyz-ear'.>
<Dec 10, 2013 5:13:11 AM EST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
java.lang.Exception: [DeploymentService:290051]The commit message for the deployment '1,386,670,091,597' could not be completed because the deployment timed out.
at weblogic.deploy.service.internal.adminserver.AdminRequestStatus.signalCommitFailed(AdminRequestStatus.java:1007)
at weblogic.deploy.service.internal.statemachines.adminserver.AwaitingCommitResponses.requestTimedOut(AwaitingCommitResponses.java:42)
at weblogic.deploy.service.internal.adminserver.AdminRequestImpl.requestTimedout(AdminRequestImpl.java:354)
at weblogic.deploy.service.internal.RequestImpl$TimeoutMonitor.timerExpired(RequestImpl.java:242)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
Truncated. see log file for complete stacktrace
>
java.lang.NullPointerException
at com.bea.p13n.jobmanager.config.JobManagerConfigHelper.shouldStartJobManager(JobManagerConfigHelper.java:124)
at com.bea.p13n.jobmanager.internal.JobManagerImpl.shouldStartJobManager(JobManagerImpl.java:1345)
at com.bea.p13n.jobmanager.internal.JobManagerImpl.getInstance(JobManagerImpl.java:624)
at com.bea.p13n.jobmanager.internal.JobServlet.init(JobServlet.java:30)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
WARN: The method class org.apache.commons.logging.impl.SLF4JLogFactory#release() was invoked.
WARN: Please see http://www.slf4j.org/codes.html#release for an explanation.
<Dec 10, 2013 5:14:24 AM EST> <Warning> <J2EE> <BEA-160181> <An error was encountered and ignored during undeployment. The error was: weblogic.utils.ErrorCollectionException:
There are 1 nested errors:
There are 11 nested errors:
java.lang.NullPointerException
at com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory.deactivate(ConfigModuleFactory.java:185)
at weblogic.application.config.DefaultModule.deactivate(DefaultModule.java:319)
at weblogic.application.internal.flow.ModuleStateDriver$2.previous(ModuleStateDriver.java:387)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.ModuleStateDriver.deactivate(ModuleStateDriver.java:141)
at weblogic.application.internal.flow.ScopedModuleDriver.deactivate(ScopedModuleDriver.java:206)
at weblogic.application.internal.flow.ModuleListenerInvoker.deactivate(ModuleListenerInvoker.java:261)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.previous(DeploymentCallbackFlow.java:547)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:215)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:192)
at weblogic.application.internal.flow.DeploymentCallbackFlow.deactivate(DeploymentCallbackFlow.java:184)
at weblogic.application.internal.BaseDeployment$2.previous(BaseDeployment.java:677)
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:63)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
Can anyone help on this ?
Thanks

Hi,
it seems that you try to deploy your application but it's taking a very long time that exceeds the timeout.
Are you deploying your application from Eclipse (oepe) or from the admin console ?
Emmanuel

Managed Server Startup - Part Duex

Hello:
Is it possible to auto-start managed servers on WLS 10.3.5 under Solaris 10?
I read the thread "managed server startup" and did not want to hijack the thread. In my case, I have an init script that starts up Node Manager and one that starts up the Admin Server.
So, once those two processes are up, is there a way for the defined managed servers to auto-start without any manual intervention on a user's part? Yes, I do have CrashRecoveryEnabled=true but as I understand it, that is for when a managed server goes down. In my case, the Solaris server is booting up.
Thank you,
Perry

Unless you have 50 managed servers then I can't understand why you would want that. Just start them all up at the same time from the admin console under 'control' tab of server page. What if you have a server or two that you don't want on for some reason? This would power it up regardless. I would think you would want to control that from node manager lifecycle. There may be a way to do that through scripting but it's probably not a best practice. We'll see if someone else chimes in on the subject. I am curious as well...

Coherence 3.6 server startup issue weblogic 11gR1sp5

Hi All,
I had managed to startup my weblogic server monitored by node manager. It is a single server domain. I have a coherence cluster setup and a single coherence server listing to the unicast address/port of the coherence cluster. I had the setup running. I had shut down my machine and next day when I tried starting it up, I started getting this error in coherence server out log --
2012-02-08 10:28:06.734/3.672 Oracle Coherence GE 3.6.0.4 <Error> (thread=Main Thread, member=n/a): Error while starting cluster: java.lang.NullPointerException
     at com.tangosol.coherence.component.net.TcpRing.ensureSelector(TcpRing.CDB:7)
     at com.tangosol.coherence.component.net.TcpRing.setServerSocketChannel(TcpRing.CDB:20)
     at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:510)
     at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
     at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
     at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)
     at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:26)
Another error is coming up in the weblogic server output log which says:
<Feb 8, 2012 10:37:55 AM EST> <Warning> <OSB Kernel> <BEA-398306> <The Result Cache /osb/service/ResultCache was not found: com.bea.alsb.coherence.CacheNotFoundException: Cache /osb/service/ResultCache not found:
com.tangosol.net.RequestPolicyException: No storage-enabled nodes exist for service ORA-OSB-deployments
com.tangosol.net.RequestPolicyException: No storage-enabled nodes exist for service ORA-OSB-deployments
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$BinaryMap.onMissingStorage(PartitionedCache.CDB:23)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$BinaryMap.sendStorageRequest(PartitionedCache.CDB:15)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$BinaryMap.addIndex(PartitionedCache.CDB:11)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.addIndex(PartitionedCache.CDB:1)
I have added the additional cmd line args for OSB to use coherence client :
-Dtangosol.coherence.distributed.localstorage=false -DOSB.coherence.cluster=ip-dev-coh-cluster -DOSB.coherence.localhost=windows -DOSB.coherence.localport=1111
And here is my override xml:
<!DOCTYPE coherence SYSTEM "coherence.dtd">
<coherence>
<cluster-config>
<unicast-listener>
<well-known-addresses>
<socket-address id="1">
<address>windows</address>
<port>1111</port>
</socket-address>
</well-known-addresses>
<address system-property="OSB.coherence.wka1">windows</address>
<port system-property="OSB.coherence.wka1.port">1111</port>
</unicast-listener>
</cluster-config>
</coherence>
I am not sure what has gone wrong in terms of my shutting down of the machine? All I did was
1. shut down the coherence server (from console)
2. shut down the admin server (from console)
3. paused my vm!
Any help would be appreciated!
Regards,
Souvik Mukherjee

Hi,
I have the same concern.I have a single server topology. The coherence cluster is targeted to admin server. I am not able to start the coherence server before starting the admin server. Is there any way by which I can start the coherence server without connecting to the admin server?
What I usually do is:
1. Run wlst
2. connect to node manager
3. nmStart('AdminServer')
4. start coherence server from the console
This setup works fine when the coherence server is up and running. When ever I shut down my coherence server, the setup doesnt work. Can you please help me doing this? I did not find any documentation as well which shows how to start coherence server from commandline or node manager. Everywhere it shows how to start coherence server from console!
Regards,
Souvik Mukherjee

I am trying to remote into a Windows Server 2003 from a Windows 7 machine and having issues

I am trying to remote into a Windows Server 2003 from a Windows 7 machine. It says "The terminal server has exceeded the maximum number of allowed connections".
My first stop in trying to solve this problem was here:
[URL="http://www.howtogeek.com/howto/windows/command-line-hack-for-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"]howtogeek.com[/URL]
And it says:
[I]
[INDENT]This problem happens because Windows only allows two remote terminal services connections when you are in administrative mode, and you’ve either got two people already on that server, or more likely, you’ve got a disconnected session that still thinks
it is active.
The problem with this error is that you have to actually get on the server console to fix the problem if the server isn’t in a domain. ([B]If you are in a domain, then just open Terminal Services Manager and log off or disconnect the sessions[/B])[/INDENT][/I]
So it seems to suggest that all I have to do really is to run the Terminal Services Manager but I cannot find it.
This web site from mssqltips.com [URL="http://www.mssqltips.com/sqlservertip/1981/remote-desktop-error-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"](click here)[/URL] says all I need to do is first execute "mstsc /
admin" from the command line. But, when I do that, I get a message when I try to remote to the server, that says this: "To log on to this remote console session, you must have administrative permissions on this computer".
So, what now? What do you suggest?

Hi Bobby,
Yes, it is by design. By default, Windows Server only accepts two concurrent administrative sessions (Administrative Mode). It means that only two administrators can work on the server at
the same time.
If you would like more concurrent sessions, you need to purchase RDS CALs, install Terminal Services related server roles with proper configurations on the server.
Remote Desktop for Administration (server 2003)
http://technet.microsoft.com/en-us/library/cc785186(v=ws.10).aspx
What Is Terminal Services?
http://technet.microsoft.com/en-us/library/cc782486(v=ws.10).aspx
Terminal Services Configuration
http://technet.microsoft.com/en-us/library/cc787078(v=ws.10).aspx
Purchase client access licenses
http://technet.microsoft.com/en-us/library/3660ac5a-7468-48d3-b7e8-5529de8fb6c5
Thanks.
Jeremy Wu
TechNet Community Support

How to create the user on Internet Application Server(IAS) control console

Hi All,
My Client is asking me for How to create the user on Internet Application Server(IAS) control console 10.1.2( 10g release 2).
If anyone have the document for How to Create the User on Internet Application Server (IAS) console 10g release 2 , then please send me the document and help me out from this Concern.
Regards,
Yadav@intelli.
Edited by: 851080 on Apr 8, 2011 6:31 PM

Are you using OID? Can you provide more details about your iAS environment?

Window Server communications from outside of session allowed for root

Hi ,
When I am running the following program, i got the exception as
49:wasp.corp.apple.com_kevinli:/ngs/app/giat/src/java/chart> java MyFrame
kCGErrorRangeCheck : Window Server communications from outside of session allowed for root and console user only
Exception in thread "main" java.lang.InternalError: Can't connect to window server - not enough permissions.
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1503)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
at java.security.AccessController.doPrivileged(Native Method)
at sun.awt.NativeLibLoader.loadLibraries(NativeLibLoader.java:38)
at sun.awt.DebugHelper.<clinit>(DebugHelper.java:29)
at java.awt.Component.<clinit>(Component.java:506)
at MyFrame.<clinit>(MyFrame.java:6)
import java.awt.*;
import javax.swing.*;
public class MyFrame
public static JFrame f = new JFrame();
public static void main(String[] args)
JFrame.setDefaultLookAndFeelDecorated(true);
f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
//Add the ubiquitous "Hello World" label.
JLabel label = new JLabel("Hello World");
f.getContentPane().add(label);
//Display the window.
f.pack();
f.setVisible(true);
Please send a reply on this.
with regards,
Mohan

Seth,
you may also install the latest update (10.4.6) using the combo file from apple.com.
Mihalis.
Dual G5 @ 2GHz Mac OS X (10.4.6)

Sun Oner Application Server 7 Admin Console doesn't start

When I start the Admin Console for Sun One Application Server 7, and after I login, the admin console doesn't display in the browser. I have tried starting the admin console with IE and Netscape browser, but the admin console has failed to start in either IE or netscape.

-Type this in your IE
http://localhost:4848
-IF it does not work type the following
http://kishan:4848 ("kishan" is your machine name)
-IF it does not work do the following
Forgot the Admin Server Port Number? If you do not remember the HTTP server port number of the administrative server, you can inspect the administrative server's configuration file to determine the HTTP server port number.
1. Navigate to the <domain_config_dir>/domain1/admin-server/config/ directory.
2. Open the server.xml file in your favorite editor. Look for the element:
<http-listener id="http-listener-1" address="0.0.0.0" port="4848"...
In this case, port 4848 is the HTTP port number in use.
Forgot the Username or Password? If you do not remember the administrative user name that was supplied during installation, try the user name "admin". This is the default user name specified in the server configuration dialog during installation. If you still cannot determine the user name, look in the following file:
<domain_config_dir>/domain1/admin-server/config/admpw
This file contains the administrator's user name followed by the encrypted form of the administrative user's password.
If you do not remember the administrator's password, then you can delete the administrative domain using the delete-domain subcommand of asadmin and create a new domain with a new administrative password.
Port Not Accessible? If the connection was refused when attempting to contact the administrative server's admin console application, it is likely that the administrative server is not running. Go back to the beginning of this section and double check the your startup procedures and the content of the administrative server's log file to determine the reason why the server is not running.

Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Hello Experts.
I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.
It has been installed successfully and does start up, however I get some annoying error messages during start up.
It seems that the server is running - I can succesfully synchronize to an ATE client.
Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.
Port issues - SMP and Agentry
Errors from the startup.log:
13:26:00 05/05/2014: HTTP-XML Back End Back End: Started
13:26:00 05/05/2014: Server: Starting threads.
13:26:00 05/05/2014: 1 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3
13:26:00 05/05/2014: Starting front ends
13:26:00 05/05/2014: ANGEL Front End: Starting threads.
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: 3 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open
13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546
13:26:00 05/05/2014: Event: 0, 23, 4
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.
13:26:01 05/05/2014: Agentry Application startup complete
Can anybody help with the meaning and implications of these errors ?
Thank you.
Søren Hansen.

Damn... I missed one port
You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.
Thanks Steve.
For others:
Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.
Now the server starts without errors.
[ANGEL Front End Ports]
1=7523
[TCP Front End]
listenOn=7521
[Java-1]
nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n
[HTTPXML-2]
baseURL=http://localhost:7522
listenOn=7525
Søren Hansen.

To exit the command window after weblogic app server startup

Hi,
The startWeblogic.cmd starts the weblogic V 10.0 server without exiting the prompt. Since our requirement wanted the startWeblogic script to exit the window after server startup, we set the parameter SET doExitFlag=true in startweblogic.cmd file , but the result was same as earlier the server started without exiting the window. Also we tried Redirecting the server starup output to a file , but even this did not exit the window.
My query is
1. What parameter options one should use to start the server so that it exits the command window in which it was started?
2. Is there an alternate way to do the same,something like to start it as a background process in Windows?
Any help in this regard would be great.
Thanks in Advance.
Best Regards,
Preethi

Not sure about parameters to startWeblogic.cmd, but from Windows you could
try
start /b startWebLogic.cmd > start.log 2 >& 1
<Preethi Ghalke> wrote in message news:[email protected]..
Hi,
The startWeblogic.cmd starts the weblogic V 10.0 server without exiting the
prompt. Since our requirement wanted the startWeblogic script to exit the
window after server startup, we set the parameter SET doExitFlag=true in
startweblogic.cmd file , but the result was same as earlier the server
started without exiting the window. Also we tried Redirecting the server
starup output to a file , but even this did not exit the window.
My query is
1. What parameter options one should use to start the server so that it
exits the command window in which it was started?
2. Is there an alternate way to do the same,something like to start it as a
background process in Windows?
Any help in this regard would be great.
Thanks in Advance.
Best Regards,
Preethi

Can't access my Directory Server using the Console installed on a machine

can't access my Directory Server using the Console installed on a remote server, lookied into knowledge base article 4693, but still same any idea ?

I too am having problems accessing Directory server from Netscape Console installed on Winxp.
If I try to open Directory server it doesn't give any error. No windows nothing.
If I try th same from the machine on which it is installed everything is fine. What is strange is that it did open a couple of times. But at the same time I can open the admin server, Netscape Messaging server from the xp box. Searching all over for a solution. Any help/pointers would be greatly appreciated.
Config details:
iDS4.13, iMS 5.0, running on Sol 8 box
Netscape Console 4.2 on WinXP.
Thanks

Server startup from console?

Similar Messages

Maybe you are looking for