Weblogic 10.3.0 managed server + Spring Framework slow startup
Hello
Iam running weblogic 10.3.0 plus an application using spring framework on this:
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.6.0_20-b02
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.6
java.vendor = Oracle Corporation
java.version = 1.6.0_20
java.vm.info = compiled mode
java.vm.name = Oracle JRockit(R)
os.arch = amd64
os.name = Windows 2003
os.version = 5.2
sun.arch.data.model = 64
sun.io.unicode.encoding = UnicodeLittle
sun.jnu.encoding = Cp1252
sun.management.compiler = Oracle JRockit(R) Optimizing Compiler
sun.os.patch.level = Service Pack 2
Problem Description: A weblogic managed server is taking more than an hour to start, the delay is due to the deployments during startup, passing from STATE_PREPARED to STATE_ADMIN and to the initialization of the Spring root WebApplicationContex, which takes an avg of 7 mins per module deployed.
I have a development server with the same application which starts in a few minutes, the only difference between the environments are tha the development server runs in 32bits.
Any help will be appreciated
-luis
Server log file:
####<Feb 17, 2011 5:09:06 PM VET> <Info> <ServletContext-/Micropago/ServiciosOperacionTransferencia> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1297978746371> <BEA-000000> <Initializing Spring root WebApplicationContext>
####<Feb 17, 2011 5:19:16 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979356364> <BEA-149059> <Module operaciondispatcher-ws-1.0-SNAPSHOT.war of application operaciondispatcher-ws-1 is transitioning from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
####<Feb 17, 2011 5:19:16 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979356411> <BEA-149060> <Module operaciondispatcher-ws-1.0-SNAPSHOT.war of application operaciondispatcher-ws-1 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
####<Feb 17, 2011 5:19:24 PM VET> <Info> <ServletContext-/Micropago/ServiciosOperacionD> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1297979364083> <BEA-000000> <Initializing Spring root WebApplicationContext>
####<Feb 17, 2011 5:23:35 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979615333> <BEA-149059> <Module operacionutil-ws-1.0-SNAPSHOT.war of application operacionutil-ws-1 is transitioning from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
####<Feb 17, 2011 5:23:35 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297979615333> <BEA-149060> <Module operacionutil-ws-1.0-SNAPSHOT.war of application operacionutil-ws-1 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
####<Feb 17, 2011 5:23:40 PM VET> <Info> <ServletContext-/Micropago/ServiciosUtilidad> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1297979620318> <BEA-000000> <Initializing Spring root WebApplicationContext>
####<Feb 17, 2011 5:30:10 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297980010468> <BEA-149059> <Module securitymanager-ws-1.0-SNAPSHOT.war of application securitymanager-ws-1 is transitioning from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
####<Feb 17, 2011 5:30:10 PM VET> <Info> <Deployer> <SAPL734> <micropago_server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297980010515> <BEA-149060> <Module securitymanager-ws-1.0-SNAPSHOT.war of application securitymanager-ws-1 successfully transitioned from STATE_PREPARED to STATE_ADMIN on server micropago_server.>
Hi, thanks for your answer.
How can I do a Thread Dump snapshot in a windows server starting as a service (no console)?
Admin_server Thread Stack Trace
Dump 1/3
"Main Thread" waiting for lock weblogic.t3.srvr.T3Srvr@f14693 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:811)
weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:459)
weblogic.Server.main(Server.java:67)
"(Signal Handler)" RUNNABLE
null
"(OC Main Thread)" RUNNABLE
null
"(Code Generation Thread 1)" RUNNABLE
null
"(Code Optimization Thread 1)" RUNNABLE
null
"(VM Periodic Task)" RUNNABLE
null
"(Attach Listener)" RUNNABLE
null
"Finalizer" RUNNABLE
jrockit.memory.Finalizer.waitForFinalizees(Native Method)
jrockit.memory.Finalizer.access$700(Finalizer.java:12)
jrockit.memory.Finalizer$4.run(Finalizer.java:189)
java.lang.Thread.run(Thread.java:619)
"Reference Handler" RUNNABLE
java.lang.ref.Reference.waitForActivatedQueue(Native Method)
java.lang.ref.Reference.access$100(Reference.java:11)
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:82)
"(Sensor Event Thread)" RUNNABLE
null
"VM JFR Buffer Thread" RUNNABLE native
null
"Timer-0" waiting for lock java.util.TaskQueue@e259a7 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)
"Timer-1" waiting for lock java.util.TaskQueue@10ad080 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE
DUMP 2/3
"Main Thread" waiting for lock weblogic.t3.srvr.T3Srvr@f14693 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:811)
weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:459)
weblogic.Server.main(Server.java:67)
"(Signal Handler)" RUNNABLE
null
"(OC Main Thread)" RUNNABLE
null
"(Code Generation Thread 1)" RUNNABLE
null
"(Code Optimization Thread 1)" RUNNABLE
null
"(VM Periodic Task)" RUNNABLE
null
"(Attach Listener)" RUNNABLE
null
"Finalizer" RUNNABLE
jrockit.memory.Finalizer.waitForFinalizees(Native Method)
jrockit.memory.Finalizer.access$700(Finalizer.java:12)
jrockit.memory.Finalizer$4.run(Finalizer.java:189)
java.lang.Thread.run(Thread.java:619)
"Reference Handler" RUNNABLE
java.lang.ref.Reference.waitForActivatedQueue(Native Method)
java.lang.ref.Reference.access$100(Reference.java:11)
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:82)
"(Sensor Event Thread)" RUNNABLE
null
"VM JFR Buffer Thread" RUNNABLE native
null
"Timer-0" waiting for lock java.util.TaskQueue@e259a7 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)
"Timer-1" waiting for lock java.util.TaskQueue@10ad080 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"[STANDBY] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad1bd WAITING
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
"weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@10aff60 TIMED_WAITING
weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
java.lang.Thread.run(Thread.java:619)
"weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@11216cb TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
"[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad3e0 WAITING
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
"Thread-7" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@10ad595 WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:615)
weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
"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)
"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: '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)
"VDE Transaction Processor Thread" waiting for lock [email protected] 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)
"VDE Replication Thread" waiting for lock com.octetstring.vde.replication.Replication@10ad426 TIMED_WAITING
com.octetstring.vde.replication.Replication.wait30sec(Replication.java:384)
com.octetstring.vde.replication.Replication.run(Replication.java:350)
"DoSManager" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
com.octetstring.vde.DoSManager.run(DoSManager.java:433)
"Thread-11" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4f576f WAITING
sun.misc.Unsafe.park(Native Method)
DUMP 3/3
"Main Thread" waiting for lock weblogic.t3.srvr.T3Srvr@f14693 WAITING
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:811)
weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:459)
weblogic.Server.main(Server.java:67)
"(Signal Handler)" RUNNABLE
null
"(OC Main Thread)" RUNNABLE
null
"(Code Generation Thread 1)" RUNNABLE
null
"(Code Optimization Thread 1)" RUNNABLE
null
"(VM Periodic Task)" RUNNABLE
null
"(Attach Listener)" RUNNABLE
null
"Finalizer" RUNNABLE
jrockit.memory.Finalizer.waitForFinalizees(Native Method)
jrockit.memory.Finalizer.access$700(Finalizer.java:12)
jrockit.memory.Finalizer$4.run(Finalizer.java:189)
java.lang.Thread.run(Thread.java:619)
"Reference Handler" RUNNABLE
java.lang.ref.Reference.waitForActivatedQueue(Native Method)
java.lang.ref.Reference.access$100(Reference.java:11)
java.lang.ref.Reference$ReferenceHandler.run(Reference.java:82)
"(Sensor Event Thread)" RUNNABLE
null
"VM JFR Buffer Thread" RUNNABLE native
null
"Timer-0" waiting for lock java.util.TaskQueue@e259a7 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)
"Timer-1" waiting for lock java.util.TaskQueue@10ad080 TIMED_WAITING
java.lang.Object.wait(Native Method)
java.util.TimerThread.mainLoop(Timer.java:509)
java.util.TimerThread.run(Timer.java:462)
"[STANDBY] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad1bd WAITING
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
"weblogic.time.TimeEventGenerator" waiting for lock weblogic.time.common.internal.TimeTable@10aff60 TIMED_WAITING
weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:286)
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:117)
java.lang.Thread.run(Thread.java:619)
"weblogic.timers.TimerThread" waiting for lock weblogic.timers.internal.TimerThread@11216cb TIMED_WAITING
java.lang.Object.wait(Native Method)
weblogic.timers.internal.TimerThread$Thread.run(TimerThread.java:267)
"[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@10ad3e0 WAITING
java.lang.Object.wait(Object.java:485)
weblogic.work.ExecuteThread.waitForRequest(ExecuteThread.java:157)
weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
"Thread-7" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@10ad595 WAITING
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
weblogic.utils.concurrent.JDK15ConcurrentBlockingQueue.take(JDK15ConcurrentBlockingQueue.java:89)
weblogic.store.internal.PersistentStoreImpl.getOutstandingWork(PersistentStoreImpl.java:567)
weblogic.store.internal.PersistentStoreImpl.run(PersistentStoreImpl.java:615)
weblogic.store.internal.PersistentStoreImpl$2.run(PersistentStoreImpl.java:383)
"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)
"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: '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)
"VDE Transaction Processor Thread" waiting for lock [email protected] 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)
"VDE Replication Thread" waiting for lock com.octetstring.vde.replication.Replication@10ad426 TIMED_WAITING
com.octetstring.vde.replication.Replication.wait30sec(Replication.java:384)
com.octetstring.vde.replication.Replication.run(Replication.java:350)
"DoSManager" TIMED_WAITING
java.lang.Thread.sleep(Native Method)
com.octetstring.vde.DoSManager.run(DoSManager.java:433)
"Thread-11" waiting for lock java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@4f576f WAITING
sun.misc.Unsafe.park(Native Method)
Similar Messages
-
WebLogic 10.3.2 managed server startup failed : ''31' could not be found'
Dears: I ran my managed server using script but failed , the weblogic version is 10.3.2 (11g R1) , on Solaris 10 sparc 64bit.:
ports=( 7001 7003 7005 7007 )
instances=( instance1 instance2 instance3 )
adminip=192.168.11.174
"startManagedWebLogic.sh ${instances[1]} http://$adminip:${ports[0]}"&
Does anyone get jammed into this situation?
The Managed Server instance2 is going to running
JAVA Memory arguments: -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m
WLS Start Mode=Production
CLASSPATH=/wls11g/patch_wls1032/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/wls11g/jdk1.6.0_18/lib/tools.jar:/wls11g/utils/config/10.3/config-launch.jar:/wls11g/wlserver_10.3/server/lib/weblogic_sp.jar:/wls11g/wlserver_10.3/server/lib/weblogic.jar:/wls11g/modules/features/weblogic.server.modules_10.3.2.0.jar:/wls11g/wlserver_10.3/server/lib/webservices.jar:/wls11g/modules/org.apache.ant_1.7.0/lib/ant-all.jar:/wls11g/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/wls11g/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/wls11g/wlserver_10.3/server/lib/xqrl.jar
PATH=/wls11g/wlserver_10.3/server/bin:/wls11g/modules/org.apache.ant_1.7.0/bin:/wls11g/jdk1.6.0_18/jre/bin:/wls11g/jdk1.6.0_18/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/wls11g/user_projects/domains/base_domain:/wls11g/user_projects/domains/base_domain/bin:/wls11g/wlserver_10.3/server/bin:/usr/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
-bash-3.00$ java version "1.6.0_18-ea"
Java(TM) SE Runtime Environment (build 1.6.0_18-ea-b05)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b12, mixed mode)
Starting WLS with line:
/wls11g/jdk1.6.0_18/bin/java -server -d64 -Xms768m -Xmx2048m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=6 -XX:+DisableExplicitGC -XX:MaxPermSize=2048m -Dweblogic.Name=instance2 -Djava.security.policy=/wls11g/wlserver_10.3/server/lib/weblogic.policy -da -Dplatform.home=/wls11g/wlserver_10.3 -Dwls.home=/wls11g/wlserver_10.3/server -Dweblogic.home=/wls11g/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=http://140.126.24.25:6001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/wls11g/patch_wls1032/profiles/default/sysext_manifest_classpath weblogic.Server
<Jan 20, 2010 6:02:46 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 16.0-b12 from Sun Microsystems Inc.>
<Jan 20, 2010 6:02:49 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
<Jan 20, 2010 6:03:00 PM CST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
<Jan 20, 2010 6:03:00 PM CST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Jan 20, 2010 6:03:00 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jan 20, 2010 6:03:00 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jan 20, 2010 6:03:01 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log00026. Log messages will continue to be logged in /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log.>
<Jan 20, 2010 6:03:01 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /wls11g/user_projects/domains/base_domain/servers/instance2/logs/instance2.log is opened. All server side log events will be written to this file.>
<Jan 20, 2010 6:03:16 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
Truncated. see log file for complete stacktrace
Caused By: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
Truncated. see log file for complete stacktrace
>
<Jan 20, 2010 6:03:19 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:70)
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:32)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:430)
at weblogic.jndi.Environment.getInitialReference(Environment.java:245)
at weblogic.server.channels.RemoteChannelServiceImpl.registerInternal(RemoteChannelServiceImpl.java:173)
at weblogic.server.channels.RemoteChannelServiceImpl.registerForever(RemoteChannelServiceImpl.java:146)
at weblogic.protocol.ConnectMonitorFactory.registerForever(ConnectMonitorFactory.java:88)
at weblogic.management.provider.MSIService.registerForReconnectToAdminServer(MSIService.java:174)
at weblogic.management.mbeanservers.compatibility.internal.CompatibilityMBeanServerService.start(CompatibilityMBeanServerService.java:154)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.
at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:251)
at weblogic.rmi.extensions.server.ServerHelper.getLocalInitialReference(ServerHelper.java:429)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:131)
at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:124)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialReference(WLInitialContextFactoryDelegate.java:426)
... 9 more
>
<Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jan 20, 2010 6:03:19 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jan 20, 2010 6:03:19 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
-bash-3.00$
Edited by: user7322888 on 2010/2/4 下午 11:41Hi,
Reproducing this issue is very easy.....
1). Just Create a Admin and Managed Server
2). Start AdminServer then from Admin Console Disable the normal listen-port for admin Server (suppose it was 7001 disable it)....AND enable only the SSL port for Admin Server (example 7002).
Managed Server (Listen Port=7003 and SSL ListenPort=7004)
3). Now Try Start Managed Server.
you wil get the Exact same exception
<Jan 20, 2010 6:03:19 PM CST> <Error> <Configuration Management> <BEA-150000> <An error occurred while establishing a connection back to the adminstration server t3://140.126.24.25:6001 during startup. Since bootstrap succeeded check that t3://140.126.24.25:6001 uniquely identifies the administration server.
javax.naming.ServiceUnavailableException [Root exception is java.rmi.NoSuchObjectException: The object identified by: '31' could not be found. Either it was has not been exported or it has been collected by the distributed garbage collector.]
And
<Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://140.126.24.25:6001.>
Now it will be easy for us to find out where is the issue actually.
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 24, 2010 4:15 PM -
Weblogic 10.3.5 Managed Server 추가 후 start 할 때 에러 나요...
Windows 7(로컬 환경)에서 weblogic 10.3.5를 사용하고 있고, 관리자 콘솔(http://localhost:7001/)에서 Managed Server(서버 이름 :test_server)를 등록해주었습니다.
그리고 배치에 디플로이 할 소스 경로를 체크하고 test_server targetting 한 후 start 했는데 에러가 납니다...ㅠㅠ
두 가지 방법으로 start 했었는데..
1. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin>startManagedWebLogic.cmd test_server http://localhost:8001
이렇게 입력하면, 로그가 잘 찍히다가
Enter username to boot WebLogic server: test_name
이게 표시됩니다. weblogic 처음 설치 할 때 설정한 username(어드민 콘솔 아이디)를 입력하니 password를 입력하라고 나오는게 아니라 아래와 같이 에러가 납니다. ㅠㅠ
*<Error> <Security> <BEA-090783> <Server is Running in Development Mode and Native Library(terminalio) to read the password securely from commandline is not found.>*
*<Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>*
*<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
두번 째 방법은
2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic.cmd*
여기서 startManagedWebLogic.cmd 를 카피하여 startManagedWebLogic_test.cmd 를 만든 후 if "%1"=="" ( 바로 아래
set SERVER_NAME=test
set ADMIN_URL=http://localhost:8001
set WLS_USER=test_name
set WLS_PW=test_password
이렇게 만든 후 2. C:\weblogic1035_dev\user_projects\domains\tiw_project\bin\*startManagedWebLogic_test.cmd* 로 Start 하였습니다.
그러니 아주 크리티컬한 에러가............... ㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠㅠ
<Critical> <WebLogicServer> <BEA-000362> *<Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already* exists>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
저 에러로그로 구글링을 엄청나게 해봤는데 별다른 성과가 없습니다..
제발 아시는 분 도와주세요..ㅠㅠ
글 수정: 889513 -
How to start Weblogic 10.3.5 managed server on port 80
Hello,
We're trying to understand how to start Weblogic as root so we can start on port 80 on Linux. We understand that we'll use the post bind UID to run as a non-priv user. Right now in the Admin console under the managed server, Server Start properties (node manager) we have the weblogic user as the user to start the server, which works. Is this where we'd put the root user? We tried that but it fails complaining about root user didn't have permission to start the server. Can someone shed some light?
ThanksHi
1. You are asking for 2 things here:
a) Start Weblogic as root user ?
Before I answer this question, who (Which User) installed Weblogic Software and who created Domain. I hope its NOT root user. Usually its not preferable to use root account for this. Instead create a new user account like for example oracle or some xyz. Then login with that account. Install Weblogic and create any Domain. I would NOT prefer/recommend using root account to install weblogic. This means, I would not recommend/support to start weblogic as root user. The thing is when you install weblogic, it stores/creates lots of files/scripts. Now when you start, it has to be same user. Because at the startup, we need to read files and also CREATE lots of temp files under domain root folder. So on unix, this becomes very complex. Simple answer is if you install weblogic and domain with user say "xyz" and try to start domain with "root", you corrupted your entire domain. Some files gets changed to root user and some files just FAIL saying you do not have permissions. So its just gone. If you are a Unix Geek, do some magic and restore all permissions back.
b) Start Weblogic at Port 80
Very Simple. Forget about above thing. Install Weblogic and create domain say with user "xyz". Just go to domain root folder, open config/config.xml file and edit the localport to 80. By default at time of domain creation if you used all the defaults like port 7001, then you will NOT see this entry in config.xml file. But still you can edit config.xml file manually. Stop the servers. Add a section with listen-port as 80. Just refer docs for the steps. After this change, your weblogic server is now running at port 80. NOW, the main precautions is make sure that you do NOT have any other stuff running at the same port 80. Otherwise, Weblogic server startup will fail saying port 80 is already is in use.
Now if you want both a) and b), still it is possible. But I would NOT want/recommend a), which is use "root" account to install weblogic server and create and start the Domain. Nope, totally not recommending and supporting this. Yes, port 80 can be used, but not the "root" account.
Thanks
Ravi Jegga -
Weblogic deployment ( admin and managed server)
I have one AdminServer and One ManageServer running on the same IP Address with
different ports,
AdminServer and ManagedServer is coming up without any errors, I able to access
the index.jsp using the following URLs
http://hostname:7001/index.jsp (Admin Server)
http://hostname:8001/index.jsp (Managed Server)
my index.jsp I have several other hperlinks ( say contacts, help etc)
Once my servers ( admin and managed ) are started successfully, I'm able to browse
thru my application using the first URL.
but if I accessed the application using the second URL the index.jsp is coming
from port no (8001), which I observed thru the access.log and if I click any other
links(contacts, help) in the index.jsp, it is access the jsps from (7001) instead
of 8001.
I think in my Jsp I'm using a wrong mechanism to read the URL, what is the proper
way to read the correct URL?
Please help me to sort out this issueTested and got it worked.
-
Re: How to start Weblogic 10.3.5 managed server on port 80
I can start managed server at port 80 but root permission make some deployments of managed server cannot cooperate with adminserver which is run by oracle user, in my case is oam_server1. Server is run but access server is down.
I can start managed server at port 80 but root permission make some deployments of managed server cannot cooperate with adminserver which is run by oracle user, in my case is oam_server1. Server is run but access server is down.
-
Weblogic 9.2 error when using spring framework and taglibs.
I am getting the following error when using spring binding for a command form class.
Class ExCommandForm
private String firmCode;
public String getFirmCode ()
public void setFirmCode ()
In my jsp I have the following
<spring:bind path="exCommandForm.firmCode">
<input name="<c:out value="${status.expression}"/>" type="text" value="<c:out value="${status.value}"/>" >
</spring:bind>
Ps. exCommandForm is the commandForm declaration in my SiimpleFormController.
When I deploy the application to weblogic 9.2 I get the following error :
<Apr 26, 2007 4:34:44 PM BST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.int
ernal.WebAppServletContext@1f601c6 - appName: 'BDRui', name: 'BDRui', context-pa
th: '/BDRui'] Root cause of ServletException.
java.lang.ClassCastException: javax.servlet.jsp.jstl.core.LoopTagSupport$1Status
at jsp_servlet._web_45_inf._jsp.__tradesearch._jspService(__tradesearch.
java:1075)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
tyHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:283)
Ps. Deploying application on Tomcat 5.23 works.
Can anyone help on this ?
cheers in advance.
More Info - Using Weblogic 9.2 on UNIX, servlet 2.4, jstl 1.1
regards
Edited by kings_citi at 04/26/2007 9:03 AM
Edited by kings_citi at 04/26/2007 10:35 AM
Edited by kings_citi at 04/26/2007 10:36 AMThe problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
Regards,
tom
Edited by: TomB on Sep 17, 2010 2:33 PM -
Bea 9.2 : deployment to managed server failed (J2EE:160149)
Hi,
I am trying to deploy portal application to managed server instance. When i am deploying it to an admin server, deployment is fine but when i am deploying to managed server instance, it fails with following error:
********* log start ************
[J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: wlp-groupspace-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-collab-portlets-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-framework-full-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-commerce-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-support-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-webdav-app-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-admin-app-lib, Specification-Version: 9.2, Implementation
********* log end **************
Can you note that the it was fine when deployment was done to admin server.
I am not sure whether i have set up the managed server instance in the proper way. This is what i did to set up managed server instance before deployment
(1) create weblogic domain
(2) create managed server listening at port 8001. (admin is at 7001)
(3) created machine and in the node manager added the managed server to the machine just created.
(4) started node manager through script, started admin server and started managed server by
startManagedWebLogic.cmd managedserver admin_url
=> No errors so far. but now when i try to deploy portal application to managed server instance, it fails.
Any pointers???
(ps : can a moderator help me to move this message to the portal forum instead of here..thanx)
Edited by tamugrg13 at 03/25/2007 8:09 PMdon't worry about this. i have resolved this by deploying into a cluster. looks like BEA doesn't support non-clustered deployment to managed server instances.
-
Managed Server can not connect to Database
I have a WebLogic cluster with three managed Server on 3 different machines.
ManagedServer_1, ManagedServer_2, ManagedServer_3 (on Machine 3)
Firstly, everything is ok. But when we changed some configuration on Firewall and make the WebLogic cluster could not connect to database. 3 servers change status from Running to Warning. Then, we undo all the changes to the Firewall configuration. 3 Servers could connect to Database again but still in warning state.
It is strange that when I tried to restart ManagedServer_3. That server could not be up normally. It went to Admin state and all the datasources and connection pool could not be created. I tried to restart the machine 3 and start the server but it still failed to make server running normally.
( I made the test connecting to Database from Machine 3, everything is okie, I can got data from database, port 1521 opened )
Has anyone got the same problem and how to fix it? Is that the problem with the admin server?JDBC DataSources/Connection pools are all at Domain Level. All we do is just target the datasources to AdminServer and Entire cluster (this will take care of all managed servers in the cluster). From Weblogic Console, TEST the data sources for any firewall issues. If this works from console, check from where you are accessing the Console like within the Firewall, that can access the database server. Even though the actual application is deployed only on cluster, still I would recommend targetting the datasources to both AdminServer and Cluster.
Ravi Jegga -
Not able to startup managed server on remote machine -- Please advice
Hi All,
We have one admin server and two managed server in one domain. The admin server and a managed server are in one machine(say machineA) and another managed server is on a different machine(say machineB). I changed the weblogic admin console password and in boot.properties file also. Now when i am restarting the managed server on machineB, i am getting below error message.
<May 12, 2009 12:26:37 PM PDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://123.23.4.56:7071 to retrieve th
e initial configuration.>
<May 12, 2009 12:26:38 PM PDT> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user weblogic star
ting the managed server. The reason for the error is .>
<May 12, 2009 12:26:38 PM PDT> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through UR
L: http://123.23.4.56:7071/wl_management_internal2/Bootstrap, user: weblogic
weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the identity of the user we
blogic starting the managed server. The reason for the error is .
at weblogic.management.ManagedServerAdmin.retrieveMBeansFromAdminServer(ManagedServerAdmin.java:513)
at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:150)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:753)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the iden
tity of the user weblogic starting the managed server. The reason for the error is .'
Reason: weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the identity of the
user weblogic starting the managed server. The reason for the error is .
Kindly help me on this.
Any suggestion is appreciated.
Thanks & Regards,
RajHi Raj,
Which version of weblogic are you using? Try to delete the cache directory of the managed server and try to restart it again and see if the problem goes away.
From Weblogic 9 version onwards by default when Managed server starts for the first time it will read boot.properties file inside domain directory and makes a copy of it inside its cache directory domain/servers/ManagedServername/Security folder. I think boot.properties file inside cache directory of managed server might be using old credentials.
The best way is to delete cache directory of managed server inside domain/servers you will see directory by managed server name, delete it and restart the managed server.
Hope this helps!!
- - Tarun -
Troubling Managed server (unable to start)
Hi
I use WebLogic Server Version: 10.3.5.0,
I want to setup both my ADMINISTRATION SERVER and MANAGED SERVER as windows service so as to start automatically when the system is switched on.... After configuring the scripts and installing them, only the Admin server works and functions well... but the Managed server doesnt work or startup. I have tried all solutions i could find in the OTN FORUM but the problem still persists.....Below are the contents of the script for the two servers. Please any one with any suggestion should help me out.
ADMIN SERVER
SETLOCAL
set DOMAIN_NAME=OBYYSDOMAIN
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAIN
set SERVER_NAME=OBYYSADMIN
set WL_HOME=C:\Oracle\Middleware\wlserver_10.3
set PRODUCTION_MODE=true
set –Dweblogic.client.socket.ConnectTimeout=500
set MEM_ARGS=-Xms512m –Xmx512m
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc1.cmd"
ENDLOCAL
MANAGED SERVER
echo off
SETLOCAL
set DOMAIN_NAME=OBYYSDOMAIN
set USERDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAIN
set SERVER_NAME=OBYYSMAN
set PRODUCTION_MODE=true
set –Dweblogic.client.socket.ConnectTimeout=500
set WL_HOME=C:\Oracle\Middleware\wlserver_10.3
set ADMIN_URL=http://OBI-PC:7001
set MEM_ARGS=-Xms40m -Xmx250m
call "C:\Oracle\Middleware\wlserver_10.3\server\bin\installSvc2.cmd"
ENDLOCAL
I created two backup copies of the WL_HOME\server\bin\installSvc.cmd master script, of which installSvc1.cmd (for Admin server) i included -delay:120000,
while installSvc2.cmd (for Managed server) i included -depend:"beasvc OBYYS_DOMAIN_OBYYSADMIN" -delay:120000Hi,
I have done evrything the webpage u directed me says perfectly alright.. i can now access the console automatically after system booting (The Admin server is started as windows service)… but in the console the Node Manager/Machine configured for it remains inactive… I don’t really knw the reason for this…. I viewed the log from Node Manager directory and this is what I get
<Mar 3, 2013 9:29:57 AM> <INFO> <Loading domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
<Mar 3, 2013 9:30:24 AM> <INFO> <Loading identity key store: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Mar 3, 2013 9:30:25 AM> <INFO> <Loaded node manager configuration properties from 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Mar 3, 2013 9:30:28 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Automatically restarting server process as part of crash recovery>
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAINS\servers\OBYYSADMINS\logs\OBYYSADMINS.out00032">
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Server error log also redirected to server log>
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAINS\bin\startWebLogic.cmd >
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAINS'>
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAINS\servers\OBYYSADMINS\logs\OBYYSADMINS.out00033">
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Server error log also redirected to server log>
<Mar 3, 2013 9:30:29 AM> <INFO> <OBYYSDOMAINS> <OBYYSADMINS> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\OBYYSDOMAINS\servers\OBYYSADMINS\logs\OBYYSADMINS.out'>
<Mar 3, 2013 9:39:39 AM> <INFO> <Secure socket listener started on port 5556, host OBI-PC/127.0.0.1>
<Mar 3, 2013 9:44:28 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from OBI-PC - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from OBI-PC - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
I am running a production environment and already set these in the Nodemanager.properties file,
Keystores=CustomIdentityandCustomTrust
CustomIdentityAlias=mykey
CustomIdentityKeystoreFileName=C:/Oracle/Middleware/user_projects/domains/mydomain/cert/myidentity.jks
CustomIdentityKeystorePassPhrase=******
CustomIdentityKeystoreType=jks
CustomIdentityPrivateKeyPassPhrase=******
but still I keep getting the error and the Machine in the console shows Inactive.
Please any solution…
Edited by: OBYYS on Mar 3, 2013 11:53 AM -
Install window services for managed server
hi all, i wanted to install window services for managed server. Can anyone advice me how to do it? My weblogic version is 10. Thanks in advance.
Hi,
Please refer to the following link....it might be helpful: http://weblogic-wonders.com/weblogic/2010/03/13/managed-server-as-windows-service/ -
Different service packs in admin server and managed server
Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack traceHi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace -
Changing Managed Server Startup
hi experts,
I am trying to change the JAVA HOME for my managed server via the Server --> Configuration --> Server Start tab on the weblogic console of the managed server. I am starting this Managed Server via NodeManager and I don't want the managed server to start with the Java Version specified on the Node Manager.
As per the note on this page it is stated as follows
+"Node Manager is a WebLogic Server utility that you can use to start, suspend, shut down, and restart servers in normal or unexpected conditions. *Use this page to configure the startup settings that Node Manager will use to start this server on a remote machine*"+
I have changed the JAVA_HOME, Java Vendor, Bea Home, and Root directory to the new JRocket version, but still when I restart the server via Nodemanager, the Managed Server is started with the Java Home set on the Nodemanager.
Can anybody let me know what is the correct way to start the Manager Server with a JVM that is different from the JVM set on the Nodemanager?
Cheers,hi,
If your using Linux,then try setting JAVA_HOME parameter in .profile and try excuting the .profile
If windows then trying setting environment parameters
then go to weblogic
open a command prompt....run "setWLSEnv.sh/cmd"
Can your please attach startup.properties file on your next post
Location
$ORACLE_HOME/user_projects/domains/base_domain/servers/<managed_server>/data/nodemanager
as well as
nodemanager.properties
This link will provide you more light
http://middlewaremagic.com/weblogic/?p=780
Regards
Fabian -
Managed Server started but reflected as Shutdown in Admin Console
Hi,
Our managed server is running as service (but the error log shows it is unable to contact the Admin server, thus running in independence mode). On our admin console, it shows the managed server as shutdown. How can we resolve this issue?
We have tried to clear all the folders under \servers\<managedserver> except the security folder containing boot.properties. However it kept prompting that invalid username/password has been entered. If we restore the original folders, the managed server was able to startup, although in independence mode. Is it because of some ldap ldift file which we find in the managed server's subfolder? How can we resolve this??
Please help, as this is a production environment and this issue just suddenly happened. It was running fine earlierHi
1) 10gR3
2) The log for managed server shows it is started and running. However, it has the following lines of error:
####<Dec 28, 2012 6:43:42 PM SGT> <Emergency> <Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422536> <BEA-141151> <The admin server could not be reached at https://kimprddmapp:9002.>
####<Dec 28, 2012 6:43:42 PM SGT> <Info> <Configuration Management> <KIMPRDDMAPP> <> <main> <> <> <> <1356691422552> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
It is also unable to deploy our application:
####<Dec 28, 2012 6:43:51 PM SGT> <Error> <Deployer> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356691431398> <BEA-149205> <Failed to initialize the application 'da' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.net.SocketException: Network is unreachable: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at java.net.Socket.connect(Socket.java:475)
at java.net.Socket.<init>(Socket.java:372)
at java.net.Socket.<init>(Socket.java:273)
at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:195)
at javax.net.ssl.impl.SSLSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLSocketFactoryImpl.createSocket(Unknown Source)
at weblogic.socket.ChannelSSLSocketFactory.createSocket(ChannelSSLSocketFactory.java:78)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:274)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:502)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:566)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:242)
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Dec 28, 2012 6:43:51 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691431991> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceHttps for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
####<Dec 28, 2012 6:43:52 PM SGT> <Info> <WebService> <KIMPRDDMAPP> <KIMServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1356691432085> <BEA-220103> <Async web service support is not fully configured. The async response web service /AsyncResponseServiceJms for this server was not fully deployed because the JMS reliability queue was not defined/deployed: weblogic.wsee.DefaultQueue. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async web service applications. To completely disable async web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.>
Noticed that on my Admin Server, it has the following error message, could this be the cause? How can I fix it?
####<Dec 28, 2012 6:35:45 PM SGT> <Warning> <Security> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356690945499> <BEA-090482> <BAD_CERTIFICATE alert was received from KIMPRDDMAPP.pubnet.sg - 10.206.12.30. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
####<Dec 28, 2012 6:35:45 PM SGT> <Error> <Console> <KIMPRDDMAPP> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <kimdmweblogic> <> <> <1356690945499> <BEA-240003> <Console encountered the following error javax.help.HelpSetException: Could not parse
Got an IOException ([Security:090477]Certificate chain received from docs.kim.pubnet.sg - 10.206.12.30 was not trusted causing SSL handshake failure.)
Parsing failed for null
at javax.help.HelpSet.<init>(HelpSet.java:146)
at com.bea.help.utils.HelpSetHelper.getExtensionHelpSetMap(Unknown Source)
at com.bea.help.utils.HelpSetHelper.mergeExtensionHelpSet(Unknown Source)
at com.bea.help.utils.HelpSetHelper.createHelpSet(Unknown Source)
at com.bea.help.utils.HelpSetHelper.getHelpSet(Unknown Source)
at com.bea.help.utils.HelpSetHelper.ensureHelpSet(Unknown Source)
at jsp_servlet._jsp.__tocview._jspService(__tocview.java:110)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
at jsp_servlet._framework._skeletons._console.__nolayout._jspService(__nolayout.java:119)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326)
at com.bea.netuix.nf.UIControl.render(UIControl.java:582)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.skeleton.Child.doTag(Child.java:63)
at jsp_servlet._framework._skeletons._console.__twocollayout._jspService(__twocollayout.java:246)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:505)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:432)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:211)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
3) Both Admin and managed servers are running on same host
Maybe you are looking for
-
Catching an error in SUBMIT Statement
Hi, I am using SUBMIT (REPORT) and RETURN. How to catch an error when there is one in the REPORT Program that i am calling.
-
Can't kill hung process in Leopard
I am having very annoying issue with Leopard. Time to time some applications get stuck and I can't kill them using "force quit" or command line "kill -9". Most of the times when this happens, I can't log out and start new applications. I cannot even
-
Help setting up automatic discount and loyalty benifits
HI, Iu2019m wondering how I could configure B1 to record the sales so that every 11u2019th sale of a certain product is free. Also, how configure B1 so that if of one product when sold together with a specific product group will automatically get a 5
-
How to block JInternalFrame deactivation
Hi friends. My question may seem to be very simple but i have not got any resonable answer yet. how can I prevent JInternalFrame deactivation programmatically basing on some conditions? Say if a user has started a transaction from within an internal
-
Rman restore and database size
I am testing a production database backup from tape. Our test machine does not have the same disk space as our production machine. Right now, here is the production size info: Allocated (GB) 137.16 Used (GB) 60.71 All