Cluster server startup order
Is there any way to control which managed server gets an application deployed first? In other words, I have an application that starts our server on the managed servers but I need to start a particular managed server first before starting any of the the other managed servers.
Hi,
How are you doing?
One alternative would be to restart the managed servers in the order you want...
I do have some questions:
o Are you doing an exploded deployment?
o Are you just re-deploying the application from the console?
o If re-deploying, have you run into issues / problems?
Best regards,
-Bart Simpson
Gino Relampagos <[email protected]> wrote:
>Is there any way to control which managed server gets an application
>deployed first? In other words, I have an application that starts our
>server on the managed servers but I need to start a particular managed
>server first before starting any of the the other managed servers.
Similar Messages
-
Pending message redelivery wait period after server startup
Hi, I have seen an strange behaviour in the way pending JMS messages are
redelivered to MDBs at server startup.
In my unit test I have seen that, killing Weblogic during an MDB code
execution as expected makes the container to redelivery unconfirmed message
at server startup. I have also seen that it's redelivered about 4 minutes
after server is started (more info of this in thread: "Problem with
persistent messages and MDBs" 25 October 2002)
After a recent crash we have had on the system in wich there were a lot of
messages pending to deliver to an MDB we saw that they were being
redelivered just after the MDBs were deployed while system was starting. Of
course due to the fact that some components needed by the MDB were not
deployed by that time, a lot of exceptions were raised making messages to be
queued again and promptly delivered wich caused more exceptions. Just a big
mess!
I'm tring to figure a good work-around about this, what I wanted to know is
how is implemented the "delay" to send messages after server startup. Is it
done by comparing timestamp of message (when did it enter the queue and
thereby persisted on the store) with current system time?. That approach of
course will fail if any of the messages were sent before that "delay" time.
If this is the case and there isn't a fix for it this is what I have in
mind:
Each MDB will have a private attribute wich will be used to detect when
system has completely started. By default it will be false and after a
message is sent to the MDB the first line of the onMessage method will test
wether system has started or not (by checking weblogic connection port i.e.
7001. Btw. is there any better way of checking server has finished start-up)
if not, a runtime exception will be launched that will force message to be
redelivered (without trying to execute any MDB code), I think setting a
proper redelivery delay i.e. 30-60 secs. will allow server to startup with
less problems (in the situation I described above JVM crashed with an 11
system signal)
Any other ideas to deal with this?
Thanks in advance.
Regards.
Ignacio.
Hi Ignacio,
I think you can usually control the order in which ejb's are booted,
through a combination of console settings and
meta file entries. I suggest posting to the ejb newsgroup
to find out how.
The four minute delay you see is normal for resolving
interrupted transactions, but I believe that an enhancement
was put into a 7.0 SP to reduce or eliminate this interval,
and that 8.1 has no interval. Post to the transaction
newsgroup for more info, or contact customer support.
Given that you referenced earlier posts on this issue, you
probably already know how to tune the interval down to one
minute even without the enhancements.
There is no other delay for sending messages at system startup,
as soon as the MDB is booted it attaches to JMS, and JMS
starts delivering messages whose transactional state is known.
Tom
P.S. I suppose one way to detect end-of-boot is to
place a startup class last in the boot order.
P.P.S. For MDBs one alternative is to code a "sleep" in the onMessage if
an unavailable resource is detected - this
is hokey, but works as long as you have made sure that
max-beans-in-free-pool totals do not come near or exceed
available thread pool size.
Ignacio G. Dupont wrote:
> Hi, I have seen an strange behaviour in the way pending JMS messages are
> redelivered to MDBs at server startup.
>
> In my unit test I have seen that, killing Weblogic during an MDB code
> execution as expected makes the container to redelivery unconfirmed message
> at server startup. I have also seen that it's redelivered about 4 minutes
> after server is started (more info of this in thread: "Problem with
> persistent messages and MDBs" 25 October 2002)
>
> After a recent crash we have had on the system in wich there were a lot of
> messages pending to deliver to an MDB we saw that they were being
> redelivered just after the MDBs were deployed while system was starting. Of
> course due to the fact that some components needed by the MDB were not
> deployed by that time, a lot of exceptions were raised making messages to be
> queued again and promptly delivered wich caused more exceptions. Just a big
> mess!
>
> I'm tring to figure a good work-around about this, what I wanted to know is
> how is implemented the "delay" to send messages after server startup. Is it
> done by comparing timestamp of message (when did it enter the queue and
> thereby persisted on the store) with current system time?. That approach of
> course will fail if any of the messages were sent before that "delay" time.
>
> If this is the case and there isn't a fix for it this is what I have in
> mind:
>
> Each MDB will have a private attribute wich will be used to detect when
> system has completely started. By default it will be false and after a
> message is sent to the MDB the first line of the onMessage method will test
> wether system has started or not (by checking weblogic connection port i.e.
> 7001. Btw. is there any better way of checking server has finished start-up)
> if not, a runtime exception will be launched that will force message to be
> redelivered (without trying to execute any MDB code), I think setting a
> proper redelivery delay i.e. 30-60 secs. will allow server to startup with
> less problems (in the situation I described above JVM crashed with an 11
> system signal)
>
> Any other ideas to deal with this?
>
> Thanks in advance.
>
> Regards.
>
> Ignacio.
>
>
-
Is there any way of controlling the startup order of bpel processes when the Application server is restarted? We are facing a problem where processA calls processB on server startup (timer has expired), but processB has not yet been started by the application server. We get error "Failed to read wsdl" as processB wsdl has not yet been loaded. We want to make sure that processB is always started before processA.
We are using Oracle Soa Suite 10.1.3.1.I have no experience with it but there is possibility to catch exception and repeat invoke until processB is not loaded.
-
Specify OC4J containers startup order
Hi,
we have defined several OC4j containers and we are now looking for a way to specifiy the startup order. Is there a way to specify in what order the OC4J containers must be started?
Thanks!
StevenAre these OC4J containers all in the same Oracle Application Server Instance or different instances? If in the same instance, do you really want to specify your own order of startup or do you just want these to be started in sequence (vs. in parallel by default)?
To start components of an instance in sequence you can use "sequential=true" with opmnctl startproc command. Refer this for details:
http://download.oracle.com/docs/cd/B32110_01/core.1013/b28944/opmnctl.htm#CEGEJDBA
You can also specify your own order of startup by setting <dependencies> in opmn.xml. Refer this for details:
http://download.oracle.com/docs/cd/B32110_01/core.1013/b28944/common.htm#CJHCJECF
For example, if you have three OC4Js - oc4j1, oc4j2 and oc4j3 and you want these to start in that order, then:
- Within <process-type id="oc4j2" ...> block, add following after </module-data> and before <start ...>:
<dependencies>
<managed-process ias-component="OC4J" process-type="oc4j1" process-set="default_group"/>
</dependencies>
- Within <process-type id="oc4j3" ...> block, add following after </module-data> and before <start ...>:
<dependencies>
<managed-process ias-component="OC4J" process-type="oc4j2" process-set="default_group"/>
</dependencies>
Reload OPMN (opmnctl reload) and start your components. OC4Js now should start in defined order.
Hope this helps.
Thanks
Shail -
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 ?
ThanksHi,
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 -
Message bean does not start automatically during application server startup
I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructor0(Class.java:1930)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:379)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve -
How to install & confgiure Oracle9i on Veritas Cluster Server
Hi,
I want to know how to install oracle9i on Veritas Cluster Server having OS as Solaris 9. Also How to configure oracle in VCS so that it can be failover.
I really appreciate the replies.
Thanks,
ShrikantI want to install following component
Oracle 9i form server & report server
Oracle HTTP Server in SSL mode
Oracle As Web Cache
Regards
Arvind -
Hi,
New to 2012 and implementing a clustered environment for our File Services role. Have got to a point where I have successfully configured the Shadow copy settings.
Have a large (15tb) disk. S:
Have a VSS drive (volume shadow copy drive) V:
Have successfully configured through Windows Explorer the Shadow copy settings.
Created dependencies in Failcover Cluster Server console whereby S: depends on V:
However, when I failover the resource and browse the Client Access Point share there are no entries under the "Previous Versions" tab.
When I visit the S: drive in windows explorer and open the Shadow copy dialogue box, there are entries showing the times and dates of the shadow copies ran when on the original node. So the disk knows about the shadow copies that were ran on the
original node but the "previous versions" tab has no entries to display.
This is in a 2012 server (NOT R2 version).
Can anyone explain what might be the reason? Do I have an "issue" or is this by design?
All help apprecieated!
Kathy
Kathleen Hayhurst Senior IT Support AnalystHi,
Please first check the requirements in following article:
Using Shadow Copies of Shared Folders in a server cluster
http://technet.microsoft.com/en-us/library/cc779378(v=ws.10).aspx
Cluster-managed shadow copies can only be created in a single quorum device cluster on a disk with a Physical Disk resource. In a single node cluster or majority node set cluster without a shared cluster disk, shadow copies can only be created and managed
locally.
You cannot enable Shadow Copies of Shared Folders for the quorum resource, although you can enable Shadow Copies of Shared Folders for a File Share resource.
The recurring scheduled task that generates volume shadow copies must run on the same node that currently owns the storage volume.
The cluster resource that manages the scheduled task must be able to fail over with the Physical Disk resource that manages the storage volume.
If you have any feedback on our support, please send to [email protected] -
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,
PreethiNot 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 -
How do I uninstall SyncMate Server, Activity Monitor shows it still there after appzapper uninstall of SyncMate app? Killing in AM proceeds with a SyncMate Server startup again??
Mavricks, MacbookPro, typical config of everything and standard business user, no heavy graphics, animation or media editing. MS Office, web apps, etc.
I have the same issue with Logmein, which I installed a trial, uninstalled with appzapper, which I thought does a good job of untangling the components of apps but for these 2 it doesn't. Any help would be greatly appreciated.
Thx,Usually applications like these have their own uninstallers, either build into the installer ( ! ) itself or as a separate uninstaller app. Check the site of the software provider for instructions.
Here's the instructions for SyncMate: http://wiki.eltima.com/user-guides/syncmate-mac-os/uninstall.html
And LogMeIn: http://help.logmein.com/SelfServiceKnowledgeRenderer?type=FAQ&id=kA030000000DGF1 CAO&kw= -
The cluster server element 441305751 is not added in the EP cluster context
Hello Experts,
We are using load balancer to distribute the load across of our four portal servers nodes. Lately, two of our nodes are behavior very strangely; it continuously stopped working momentarily and it started back up again automatically by it self. And the users usually received a message u201C500 internal server erroru201D.
#1.5 #001372559B8800280000000200002D940004692BC78C988A#1241536659228#com.sap.engine.services.prtbridge##com.sap.engine.services.prtbridge####n/a##defe75c0398711debfb1001372559b88#SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#/System/Server#Plain###
The cluster server element 441305751 is not added in the EP cluster context,
because prtbridge on 441305751 is stopped or not yet started (maybe the server is starting or shuting down).
Any helps would be appreciated,
davidnHI David,
Did you figure out why it happened? we have same exact problem and same log was written, could you please share your solution.
Thanks -
Deploy jw webservice to cluster server, always point to 9081
i have cluster server(9081, 9082, 9083), when i deploy the helloword webservice generated by jwsc http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv/use_cases.html,
the dynamical wsdl always point to 9081,<s2:address location="http://localhost:9081/HelloWorldImpl/HelloWorldService" /> even when i invoke the service on 9082, http://localhost:9082/HelloWorldImpl/HelloWorldService?WSDL
i tried generate webservice by axis it works fine. i gooled, couldn't find solution. thx.Thanks for looking into it. Clean cache doesn't work for me. Since it works fine for you. I think the issue might related to create/deploy ear file. i don't have cluster setup on my local, so i created ear file and deployed to our DEV(unix) server thru admin console. the web-uri in application.xml generated by the jwsc contains the path examples/webservices/hello_world/HelloWorldImpl.war, instead of HelloWorldImpl.war. i have to manually updated the uri, otherwise i got "not be able to identifiy application path ......war" during install. Since Axis works fine cluster config should be ok. Do you mind share how you config the cluster and how to generate the ear file? this are the two possible places i can think of. i also tried set FrontEnd HTTP Port for each server, still didn't work.
May i know are you tech support from weblogic? i am trying to find way to create ticket for weblogic tech support for this issue. thx. -
Server startup error logs EP 60 Sp2 patch4 Solaris
I have the following logs:
under /usr/sap/JDB1/j2ee/j2ee_00/cluster/server/managers/log...ERROR.log shows the following
Would this stop the server from starting? I have change the settings for loading to 10000 to preclude the timeout issues when starting the server....however I still get the server timing out.....
2004-08-09 09:44:42 | R3StartupManager | ERROR | unknown | unknown | The runtime
.properties of the r3startup service could not be found. The servers won't be st
arted. |
2004-08-09 09:44:44 | ClassLoaderManager | ERROR | unknown | unknown | class com
.inqmy.core.classloader.impl0.LibraryReferencedLoader at openJar(additional-lib/
iaik_jce_full.jar) : java.util.zip.ZipException: No such file or directory |
2004-08-09 09:45:20 | ClassLoaderManager | ERROR | unknown | unknown | class com
.inqmy.core.classloader.impl0.LibraryReferencedLoader at openJar(additional-lib/
com/sap/jdbc_driver_references/Opta2000.jar) : java.util.zip.ZipException: error
in opening zip file |Nicholas,
You are correct that some of the files are missing.
The r3startup service is gone. it was there and now gone after the PL 24 upgrade. This service per SAP was set to manual anyway.
The additional-lib/iaik_jce_full.jar was never part of the install, this file doesn;t exist either. The OSS note recommended the following be installed:
iaik_ssl.jar, iaik_jsse.jar and iaik_jce.jar
and the com/sap/jdbc_driver_references/Opta2000.jar...
the Opta200.jar file exist but is zero....
What do other Solaris EP 60 SP2 Patch4 folks have one there machines?
Thanks
John -
Can I run a .bat, .cmd, or .ps1 on SBS 2011 server startup, without login.... like a service.
Hi all,
I'm running Windows SBS 2011. I need to run a script at server startup, prior to login to any user account (like a service does...). This short script will check the status of another service. Because this
service depends on Exchange & SQL, it sometimes fails to start at reboot if Exchange and or SQL Server haven't finished initializing.
I was also thinking of using sc.exe to change the config of the service in question (adding dependencies), but this is a third-party software from Reuters, and I am somewhat reluctant to edit the configuration of someone else's code (and possibly break something).
This is a production server at a law firm.
here's the script:
start of listing
=============================================
@echo off
rem Look for ProLaw Groupware Agent in running Services.
rem check to see if ProLaw Groupware Agent is running. If it IS
rem running, jump to exit-program label, else run the Agent after
rem waiting for Microsoft Exchange & Microsoft SQL Server to start.
rem =======================================
:start
C:\Windows\system32\sc query "ProLawGroupwareAgent" | find "RUNNING" >> c:\temp\plgwagentstatus.txt
if errorlevel 0 goto :end
rem wait 10 min after server startup,
rem to (Allow Exchange & SQL to start)
rem THEN, start ProLawGroupwareAgent
rem ========================
echo "Service not started.... Let's wait 10 minutes, and retry." >> c:\temp\plgwagentstatus.txt
c:\
timeout /t 600 > nul
cd "\Program Files (x86)\ThomsonElite\ProLaw GroupwareAgent"
net start AgentHostService.exe
timeout /t 20 > nul
goto :start
:end
=============================================
end of listingWhat I do in this case (I don't have access to exact script I use) is a similar script scheduled via windows task scheduler every five minutes to check if service running, if not start it but you can have the IF-THEN-ELSE do whatever is required.
http://gallery.technet.microsoft.com/scriptcenter/01fcf945-ad73-44e0-8cb5-152432bc6bcf
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Maybe you are looking for
-
Adobe 9 pro portfolio print order
I am trying to make it easy for our customers to print out our catalog. I created a pdf portfolio. I want the portfolio to print top to bottom, left to right. It seems Acrobat 9 pro prints in alphabetical order according to the names. Is there an
-
New Windows update created issues in Flash 8
I installed some updates for Windows today and suddenly I cannot export .swf files in flash. I can't test movie, test scene or export anything. If I attempt to test movie several times in a row, it causes flash to crash. I already tried uninstalling
-
HT202351 extended display & switching videos
I have a MB Air connected to an LCD projector. I want to run a video on one display while at the same time, preparing another video to play a bit later. I hate the idea of the audience "watching the cursor pull the screen over" as I move the finished
-
Confused about Source/Project File Conversion Sizes
Which means.... I drop a 34MB .mov file into iDVD and it shows up in the Project Info window as 430 MB. Is this the way it has to work? Second (related) question: I now have 26 minutes of files loaded into the iDVD project (showing 1.47 GB in iDVD).
-
HT4436 What happens to my iCloud photos if I turn photo stream off?
Will the photos just disappear? Will they remain as they are - just with no updates? Other?