Running weblogic with Vcafe 3
Hello,
Using visual cafe 3 (enterprise), I've got a class which run Weblogic in
order to debug EJB, so I had to insert weblogic classes in VC classpath
(sc.ini) to debug EJB (which uses weblogic classes like weblogic.rmi,...)
and run WL.
It works fine with weblogic 3.1 (no java and wl distinct classpaths) but
not with newer versions (4.5.2, 5.1) because WL refuse to run coz of
weblogicaux.jar in java classpath !!!!
So how can I do ?
Thx,
Matt
You should upgrade to VCafe Enterprise 3.1a. I believe there's no charge. Check out the WebGain
website.
WebLogic 4.5.x and 5.1.x use dynamic class loading to enable runtime replacement of servlets, jsps,
and ejbs.
The server should be started with the standard class libraries and directories given by -classpath
and the weblogic\classes and weblogicaux.jar on the -Dweblogic.class.path.
The Server can be started with everthing on the classpath in what's called static mode. In this
case, the important thing is to make sure that weblogic\classes\boot appears BEFORE
weblogic\classes.
For 5.1.x, also make sure that the parameter -Dweblogic.system.disableWeblogicClassPath=true is
added.
But the automated EJB features in VCafe 3.1a won't work with 5.1.x. For that you'll need to update
to VCafe 4.0 Enterprise (and I believe there is an upgrade cost there.)
-dana
Matt wrote:
>
Hello,
Using visual cafe 3 (enterprise), I've got a class which run Weblogic in
order to debug EJB, so I had to insert weblogic classes in VC classpath
(sc.ini) to debug EJB (which uses weblogic classes like weblogic.rmi,...)
and run WL.
It works fine with weblogic 3.1 (no java and wl distinct classpaths) but
not with newer versions (4.5.2, 5.1) because WL refuse to run coz of
weblogicaux.jar in java classpath !!!!
So how can I do ?
Thx,
Matt
Similar Messages
-
{Q} Debuging Servlets with VCafe 4.0 using WebLogic as WEB server
Hi,
I am trying to set up VCafe 4.0 to debug servlets deployed on WebLogic 5.1.
I don't have any problem with default servlet debugging, but I don't know
how to tell VCafe that my WEB Server isWebLogic. Any ideas?
Greg Mirsky
What edition of VCafe is required?
Enterprise, Professional or standard. I am now using JBuilder and anyone has
experience comparing it with VCafe.
Jonathan
Don Reamey wrote:
> Start the EJB Server from within Cafe ( you must have an EJB project open),
> also have your servlet project open.
>
> Once the EJB server has been started from with in Cafe, select attach to
> process from the file menu.
>
> Attach to your server and set a break point in your sevlet.
>
> Go to the browser of your choice and run your application as normal.
>
> The break point should get hit and you can start stepping.
>
> The same procedure works for JSP's as long as you have the
> keepgenerated=true.
>
> Don Reamey
> www.ibexone.com
>
> "Greg Mirsky" <[email protected]> wrote in message
> news:[email protected]..
> > Hi,
> > I am trying to set up VCafe 4.0 to debug servlets deployed on WebLogic
> 5.1.
> > I don't have any problem with default servlet debugging, but I don't know
> > how to tell VCafe that my WEB Server isWebLogic. Any ideas?
> > Greg Mirsky
> >
> >
> >
-
Running weblogic 5.1 with HotSpot 2.0
Hi people ,
I just want to run my weblogic with hotspot server VM 2.0 on
weblogic 5.1 . can any place a pointer on how to start weblogic with
hotspot .
thanks a lot in advance
regards
Hari KrishnaHari Krishna,
First http://www.weblogic.com/platforms/index.html
Then change the .cmd or .sh that you are using to start WebLogic to use the
JVM of your choice.
Peace.
Cameron Purdy
[email protected]
http://www.tangosol.com
WebLogic Consulting Available
"Hari Krishna" <[email protected]> wrote in message
news:[email protected]..
Hi people ,
I just want to run my weblogic with hotspot server VM 2.0 on
weblogic 5.1 . can any place a pointer on how to start weblogic with
hotspot .
thanks a lot in advance
regards
Hari Krishna -
Problems running Weblogic 6.1 Server on Pentium 4 with Windows XP
Hi everyone.
I've got a problem. I'm trying to run Weblogic 6.1 Server on Pentium 4 with Windows
XP as OS, and when I try to work with the console the system restarts and get
an error message in which I can read something like "big error on the system".
Does anybody know if there is any problem between WebLogic Server and Pentium
4 or Windows XP?
Thank youWe're you ever able to install WLS 6.1 sp4 in XP in a working fashion?
WLS 6.1 sp3 works just fine on XP.
Steve...
"Hiroaki Nakamura" <[email protected]> wrote:
>
I had a problem installing WebLogic6.1SP4 on Windows XP.
SP3 was OK. The problem seems to be in the installer.
When I ran the installer, I saw these weird behaviors:
- The default value of BEA Home was "\\bea" (should be "C:\bea").
- The dialog for inputting system password was skipped.
- After the installer "finished", some directories like
C:\bea\jdk131, C:\bea\wlserver6.1\bin were missing.
OTOH, "C:\BEA WebLogic E-Business Platform" was created.
- In the control panel, add/remove program section, the
entry for WebLogic6.1SP4 was not created.
The installer runs fine on Windows 2000. And I copied
the installed files to my Windows XP machine, and I ran
startWebLogic.cmd in myserver directory, it seems OK. -
Error when run page with EJB + ADF
hello
when i run one page with EJB+ ADF give me this error:
<15/Set/2009 17H35m WEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1253032513131' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class valtex.java.ejb.entities.Team] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
at org.eclipse.persistence.exceptions.ValidationException.noPrimaryKeyAnnotationsFound(ValidationException.java:1245)
at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.validatePrimaryKey(EntityAccessor.java:1173)
at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:486)
at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:443)
at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:303)
Truncated. see log file for complete stacktrace
>
<15/Set/2009 17H35m WEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'Application'.>
<15/Set/2009 17H35m WEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class valtex.java.ejb.entities.Team] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
at org.eclipse.persistence.exceptions.ValidationException.noPrimaryKeyAnnotationsFound(ValidationException.java:1245)
at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.validatePrimaryKey(EntityAccessor.java:1173)
at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:486)
at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:443)
at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:303)
Truncated. see log file for complete stacktrace
>
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application-EJBModel-ejb)
#### Deployment incomplete. #### Sep 15, 2009 5:35:14 PM
oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:247)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:157)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
at oracle.jdevimpl.runner.adrs.AdrsStarter$5$1.run(AdrsStarter.java:1365)
Caused by: oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:413)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:238)
... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:395)
... 12 more
#### Cannot run application Application due to error deploying to DefaultServer.
[Application Application stopped and undeployed from Server Instance DefaultServer]
<15/Set/2009 17H43m WEST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=HomePage1.>
what's means this error???
thanks
Miguel TeixeiraI have a problem when running
the following is the error report
*** Using port 7101 ***
C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\patch_wls1031\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\utils\config\10.3.1.0\config-launch.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.1.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar
PATH=C:\Oracle\MIDDLE~1\patch_wls1031\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Common Files\Nero\Lib\;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
* 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:
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.07\DEFAUL~1 -Doracle.home=C:\Oracle\MIDDLE~1\JDEVEL~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.security.jps.config=C:\Users\ADMINI~1\AppData\Roaming\JDEVEL~1\SYSTEM~1.07\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\JDEVEL~1\modules\oracle.oamprovider_11.1.1 -Dsso.filter.enable=true -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1031\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
<23/09/2009 05:20:57 PM COT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ja.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ko.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_CN.jar;C:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_TW.jar>
<23/09/2009 05:20:58 PM COT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b16 from Sun Microsystems Inc.>
<23/09/2009 05:20:59 PM COT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.1.0 Wed Jun 10 22:24:41 MDT 2009 1227385 >
<23/09/2009 05:21:03 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<23/09/2009 05:21:03 PM COT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<23/09/2009 05:21:03 PM COT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<23/09/2009 05:21:03 PM COT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log00007. Log messages will continue to be logged in C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log.>
<23/09/2009 05:21:03 PM COT> <Notice> <Log Management> <BEA-170019> <The server log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<23/09/2009 05:21:11 PM COT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<23/09/2009 05:21:13 PM COT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<23/09/2009 05:21:13 PM COT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\access.log00003. Log messages will continue to be logged in C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\access.log.>
<23/09/2009 05:21:17 PM COT> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.>
<23/09/2009 05:21:17 PM COT> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.>
<23/09/2009 05:21:20 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<23/09/2009 05:21:20 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<23/09/2009 05:21:23 PM COT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application HR_EJB_JPA_App is not versioned.>
23/09/2009 05:21:23 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: Identificador de Aplicación : HR_EJB_JPA_App
23/09/2009 05:21:23 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: "Servicios de Metadatos: Archivo de metadatos (MAR) no encontrado."
23/09/2009 05:21:23 PM JpsApplicationLifecycleListener Migrate Application Credential Store
ADVERTENCIA: Overwriting credentials is allowed in application credential store migration with Weblogic server running in Development Mode and system property 'jps.app.credential.overwrite.allowed' set to true
[EL Finer]: 2009-09-23 17:21:26.427--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Searching for default mapping file in file:/C:/Users/Administrador/AppData/Roaming/JDeveloper/system11.1.1.1.33.54.07/o.j2ee/drs/HR_EJB_JPA_App/HR_EJB_JPA_App-EJBModel-ejb/
[EL Finer]: 2009-09-23 17:21:26.481--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Searching for default mapping file in file:/C:/Users/Administrador/AppData/Roaming/JDeveloper/system11.1.1.1.33.54.07/o.j2ee/drs/HR_EJB_JPA_App/HR_EJB_JPA_App-EJBModel-ejb/
[EL Config]: 2009-09-23 17:21:26.53--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The access type for the persistent class [class oracle.Departments] is set to [FIELD].
[EL Config]: 2009-09-23 17:21:26.531--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The alias name for the entity class [class oracle.Departments] is being defaulted to: Departments.
[EL Config]: 2009-09-23 17:21:26.531--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The table name for entity [class oracle.Departments] is being defaulted to: DEPARTMENTS.
[EL Config]: 2009-09-23 17:21:26.534--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The access type for the persistent class [class oracle.Employees] is set to [FIELD].
[EL Config]: 2009-09-23 17:21:26.535--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The alias name for the entity class [class oracle.Employees] is being defaulted to: Employees.
[EL Config]: 2009-09-23 17:21:26.535--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The table name for entity [class oracle.Employees] is being defaulted to: EMPLOYEES.
[EL Config]: 2009-09-23 17:21:26.543--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The column name for element [private java.lang.String oracle.Employees.email] is being defaulted to: EMAIL.
[EL Config]: 2009-09-23 17:21:26.544--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The column name for element [private java.lang.Double oracle.Employees.salary] is being defaulted to: SALARY.
[EL Config]: 2009-09-23 17:21:26.544--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the one to many mapping element [private java.util.List oracle.Departments.employeesList] is being defaulted to: class oracle.Employees.
[EL Config]: 2009-09-23 17:21:26.544--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the many to one mapping element [private oracle.Departments oracle.Employees.departments] is being defaulted to: class oracle.Departments.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The primary key column name for the mapping element [private oracle.Departments oracle.Employees.departments] is being defaulted to: DEPARTMENT_ID.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the many to one mapping element [private oracle.Employees oracle.Departments.employees] is being defaulted to: class oracle.Employees.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The primary key column name for the mapping element [private oracle.Employees oracle.Departments.employees] is being defaulted to: EMPLOYEE_ID.
[EL Config]: 2009-09-23 17:21:26.545--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the one to many mapping element [private java.util.List oracle.Employees.departmentsList] is being defaulted to: class oracle.Departments.
[EL Config]: 2009-09-23 17:21:26.546--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the many to one mapping element [private oracle.Employees oracle.Employees.employees] is being defaulted to: class oracle.Employees.
[EL Config]: 2009-09-23 17:21:26.546--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The primary key column name for the mapping element [private oracle.Employees oracle.Employees.employees] is being defaulted to: EMPLOYEE_ID.
[EL Config]: 2009-09-23 17:21:26.546--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The target entity (reference) class for the one to many mapping element [private java.util.List oracle.Employees.employeesList] is being defaulted to: class oracle.Employees.
[EL Finer]: 2009-09-23 17:21:26.547--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Class [oracle.Departments] registered to be processed by weaver.
[EL Finer]: 2009-09-23 17:21:26.547--ServerSession(30842787)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Class [oracle.Employees] registered to be processed by weaver.
23/09/2009 05:21:34 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: Identificador de Aplicación : wsm-pm
23/09/2009 05:21:34 PM oracle.mds.internal.lcm.logging.MDSLCMLogger info
INFO: "Servicios de Metadatos: Archivo de metadatos (MAR) no encontrado."
23/09/2009 05:21:38 PM oracle.adf.share.config.ADFConfigFactory getInstance
INFO: ADF Config instance implementation in use is : oracle.adf.share.config.MDSConfigFactory
23/09/2009 05:21:46 PM oracle.adf.mbean.share.connection.ConnectionsRuntimeMXBeanImpl getNonCachedConnectionsContext
INFO: Registering Connection Runtime MBean
23/09/2009 05:21:46 PM oracle.adf.share.jndi.MDSBackingStore isReadOnlyMDSStore
INFO: Read only backing store
23/09/2009 05:21:47 PM oracle.adf.share.jndi.MDSBackingStore isReadOnlyMDSStore
INFO: Read only backing store
23/09/2009 05:21:47 PM oracle.adf.share.jndi.MDSBackingStore isReadOnlyMDSStore
INFO: Read only backing store
<23/09/2009 05:21:50 PM COT> <Notice> <LoggingService> <BEA-320400> <The log file C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<23/09/2009 05:21:50 PM COT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log00006. Log messages will continue to be logged in C:\Users\Administrador\AppData\Roaming\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\servers\DefaultServer\logs\DefaultDomain.log.>
<23/09/2009 05:21:50 PM COT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
23/09/2009 05:21:51 PM oracle.wsm.audit.Auditor <init>
INFO: Created J2EE application auditor for componentType=oracle.security.jps.internal.audit.AuditServiceImpl$Auditor@213b6e
23/09/2009 05:21:55 PM oracle.adf.share.config.ADFMDSConfig parseADFConfiguration
INFO: Configuration file:/META-INF/adf-config.xmlcannot not be read by MDS. Reading directly from the classpath
<23/09/2009 05:21:55 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<23/09/2009 05:21:55 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:246d:98bd:32fc:bf08:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:790b:d0ee:a329:57db:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:28a5:117:3611:5367:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:c0a8:66:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.0.102:7101 for protocols iiop, t3, ldap, snmp, http.>
<23/09/2009 05:21:55 PM COT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<23/09/2009 05:21:55 PM COT> <Warning> <Server> <BEA-002611> <Hostname "Crht-PC", maps to multiple IP addresses: 192.168.0.102, fe80:0:0:0:246d:98bd:32fc:bf08%12, fe80:0:0:0:28a5:117:3611:5367%13>
<23/09/2009 05:21:56 PM COT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<23/09/2009 05:21:56 PM COT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
[Running application Application9 on Server Instance DefaultServer...]
DefaultServer startup time: 64580 ms.
DefaultServer started.
<23/09/2009 05:22:08 PM COT> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Application9 is not versioned.>
23/09/2009 05:22:08 PM JpsApplicationLifecycleListener Migrate Application Credential Store
ADVERTENCIA: Overwriting credentials is allowed in application credential store migration with Weblogic server running in Development Mode and system property 'jps.app.credential.overwrite.allowed' set to true
<23/09/2009 05:22:09 PM COT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1253744528059' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.1.1.v20090430-r4097): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo Project1 has transactionType JTA, but doesnt have jtaDataSource.
at org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:798)
at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:216)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:343)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:323)
Truncated. see log file for complete stacktrace
>
<23/09/2009 05:22:09 PM COT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'Application9'.>
<23/09/2009 05:22:09 PM COT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.1.1.v20090430-r4097): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo Project1 has transactionType JTA, but doesnt have jtaDataSource.
at org.eclipse.persistence.exceptions.EntityManagerSetupException.jtaPersistenceUnitInfoMissingJtaDataSource(EntityManagerSetupException.java:154)
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:798)
at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:216)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:343)
at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:323)
Truncated. see log file for complete stacktrace
>
[05:22:09 PM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(Application9-Project1-ejb)
[05:22:09 PM] Caused by: java.lang.Throwable: Substituted for missing class Exception [EclipseLink-28010] (Eclipse Persistence Services - 1.1.1.v20090430-r4097) - org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: PersistenceUnitInfo Project1 has transactionType JTA, but doesnt have jtaDataSource.
[05:22:09 PM] See server logs or server console for more details.
oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: Deployment Failed[05:22:10 PM] #### Deployment incomplete. ####
oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: Deployment Failed
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:341)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:235)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:442)
at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
at oracle.jdevimpl.runner.adrs.AdrsStarter$6$1.run(AdrsStarter.java:1469)
Caused by: oracle.jdeveloper.deploy.DeployException: oracle.jdeveloper.deploy.DeployException: Deployment Failed
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:483)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:332)
... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:465)
... 12 more
#### Cannot run application Application9 due to error deploying to DefaultServer.
[Application Application9 stopped and undeployed from Server Instance DefaultServer]
Please help me!!
thnks!! -
Error when running weblogic 10 in cluster
I am testing out weblogic 10 and when I run it with a single managed server and an admin server then everything works fine. When I run it in a cluster with a valid test cluster license, I get the following error. Does anyone know what the cause of this error is and how to fix it? Thanks for the help.
<Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>We solved this by increasing the number of open files, by adding the following in the /etc/security/limits.conf
* soft nofile 50000
* hard nofile 50000 -
Rogue cpu hog while running WebLogic
Hello,
My application is a servlet/EJB/Oracle application running on
WebLogic.
During stress test, I am seeing a java thread that is taking up 50% of
available cpu on a dual cpu machine. The thread remains at 100% even
after the load is over.
Here are some data and observations:
0. I am running WebLogic 7.0.1 on RedHat 7.2 (kernel 2.4.9-31), dual
cpu. My application consists of a few servlets talking to some 20
stateless session beans which uses CMP 2.0 entity beans to talk to
Oracle 9.0.1. We are using the oci jdbc driver.
1. After the load was over, I used ps and saw that the thread was
still running. I tracked its parent to the weblogic root process.
2. I ran top and saw the thread taking up 50% of available cpu
(sometimes it is 100% of a cpu, but it may also be 60% of cpu1 and 40%
of cpu2, etc).
3. I did a full thread dump, all but one thread are weblogic's or the
jvm's internal threads. My application did have one thread remaining,
but it is a periodic cleanup thread that wakes up every 30 secs and I
believe it is benign. I am not able to quickly point out which thread
is the rogue thread.
4. Using vmstat, I believe the rogue thread kicked in about 10 minutes
into the load (but this number varies from load to load, there was one
that kicked in after an hour). After that point, I saw the number of
runnable process remained at least one, and the idle cpu never goes
above 50 (remember it is a dual cpu machine). After I stopped the
load, the number of runnable process stayed at 1 and the idle cpu
stayed at 50.
5. This thread does not always kicked in, sometimes I would be able to
complete a 24-hour load and did not see the evidence of the thread.
6. The presence of the thread caused a 30% performance degradation.
So here is the question, what is this thread and how can I stop it
from kicking in?
I have attached a full thread dump and the outputs of top and vmstat.
I have also searched previous posts and apparently this has been seen
before by other users of weblogic, but in those threads of discussions
I never saw a resolution.
Thanks in advance,
Chishun Kwong
=================
Full thread dump:
"Thread-11" daemon prio=1 tid=0x9b793138 nid=0xc59 waiting on monitor
[0xa7153000..0xa7153870]
at java.lang.Thread.sleep(Native Method)
at com.mycompany.myapp.SomeCleanupThread.run(SomeCleanupThread.java:234)
"ListenThread.Default" prio=1 tid=0x9fad0578 nid=0xb58 runnable
[0xa694f000..0xa694f870]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:256)
"ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon
prio=1 tid=0x9fa0b438 nid=0xb27 waiting on monitor
[0xa674f000..0xa674f870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon
prio=1 tid=0x9fa0b2d0 nid=0xb26 waiting on monitor
[0xa5dec000..0xa5dec870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
tid=0x8527000 nid=0xb21 waiting on monitor [0xa5bec000..0xa5bec870]
at java.lang.Object.wait(Native Method)
at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x83bec38 nid=0xb20 waiting on monitor [0xa37eb000..0xa37eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x83beae8 nid=0xb1f waiting on monitor [0xa35eb000..0xa35eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x85198f8 nid=0xb1e waiting on monitor [0xa33eb000..0xa33eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
tid=0x85d8368 nid=0xb1d waiting on monitor [0xa31eb000..0xa31eb870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"CoreHealthMonitor" daemon prio=1 tid=0x8138938 nid=0xa97 waiting on
monitor [0xa2cff000..0xa2cff870]
at java.lang.Thread.sleep(Native Method)
at weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:114)
"ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x83be530 nid=0xa96 waiting on monitor [0xa29ff000..0xa29ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8246120 nid=0xa95 waiting on monitor [0xa27ff000..0xa27ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x834e868 nid=0xa94 waiting on monitor [0xa25ff000..0xa25ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x85813f8 nid=0xa93 waiting on monitor [0xa23ff000..0xa23ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x83be860 nid=0xa92 waiting on monitor [0xa21ff000..0xa21ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8504748 nid=0xa91 waiting on monitor [0xa1fff000..0xa1fff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x82f2908 nid=0xa90 waiting on monitor [0xa1dff000..0xa1dff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8396dd0 nid=0xa8f waiting on monitor [0xa1bff000..0xa1bff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8588b78 nid=0xa8e waiting on monitor [0xa19ff000..0xa19ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x858e000 nid=0xa8d waiting on monitor [0xa17ff000..0xa17ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x844c6b0 nid=0xa8c waiting on monitor [0xa15ff000..0xa15ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x837b8b0 nid=0xa8b waiting on monitor [0xa13ff000..0xa13ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x82158f0 nid=0xa8a waiting on monitor [0xa11ff000..0xa11ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x840a6f8 nid=0xa89 waiting on monitor [0xa0fff000..0xa0fff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
tid=0x8398578 nid=0xa88 waiting on monitor [0xa0dff000..0xa0dff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x8222408 nid=0xa87 waiting on monitor
[0xa0bff000..0xa0bff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x847df98 nid=0xa86 waiting on monitor
[0xa09ff000..0xa09ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'"
daemon prio=1 tid=0x856cd28 nid=0xa85 waiting on monitor
[0xa07ff000..0xa07ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"Thread-4" prio=1 tid=0x8523528 nid=0xa84 waiting on monitor
[0xa05ff000..0xa05ff870]
at java.lang.Object.wait(Native Method)
at java.util.TimerThread.mainLoop(Timer.java:427)
at java.util.TimerThread.run(Timer.java:380)
"ExecuteThread: '1' for queue: 'DRS'" daemon prio=1 tid=0x8582bc0
nid=0xa83 waiting on monitor [0x9feff000..0x9feff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'DRS'" daemon prio=1 tid=0x85640d8
nid=0xa82 waiting on monitor [0x9fcff000..0x9fcff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"VDE Transaction Processor Thread" prio=1 tid=0xa021c060 nid=0xa53
waiting on monitor [0x9f9ff000..0x9f9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(TransactionProcessor.java:306)
at com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionProcessor.java:192)
"ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030f218 nid=0xa52 waiting on monitor
[0x9f7ff000..0x9f7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030e7d0 nid=0xa51 waiting on monitor
[0x9f5ff000..0x9f5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030dd88 nid=0xa50 waiting on monitor
[0x9f3ff000..0x9f3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030d340 nid=0xa4f waiting on monitor
[0x9f1ff000..0x9f1ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030c8f8 nid=0xa4e waiting on monitor
[0x9edff000..0x9edff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030beb0 nid=0xa4d waiting on monitor
[0x9ebff000..0x9ebff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030b468 nid=0xa4c waiting on monitor
[0x9e9ff000..0x9e9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa030aa20 nid=0xa4b waiting on monitor
[0x9e7ff000..0x9e7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa0309fd8 nid=0xa4a waiting on monitor
[0x9e5ff000..0x9e5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
prio=1 tid=0xa0309990 nid=0xa49 waiting on monitor
[0x9e3ff000..0x9e3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
prio=1 tid=0xa0309748 nid=0xa48 waiting on monitor
[0x9e1ff000..0x9e1ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
prio=1 tid=0xa0309530 nid=0xa47 waiting on monitor
[0x9dfff000..0x9dfff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"TimeEventGenerator" daemon prio=1 tid=0x9ef68d50 nid=0xa46 waiting on
monitor [0x9ddff000..0x9ddff870]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=1
tid=0x9b77b5e0 nid=0xa45 waiting on monitor [0x9dbff000..0x9dbff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=1
tid=0x9b77b3c8 nid=0xa44 waiting on monitor [0x9d9ff000..0x9d9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"HighPriority TimeEventGenerator" daemon prio=1 tid=0x9b77b1d8
nid=0xa43 waiting on monitor [0x9d7ff000..0x9d7ff870]
at java.lang.Object.wait(Native Method)
at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:139)
at java.lang.Thread.run(Thread.java:479)
"SpinnerRandomSource" daemon prio=1 tid=0x9bfc1e48 nid=0xa41 waiting
on monitor [0x9d5ff000..0x9d5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:60)
at java.lang.Thread.run(Thread.java:479)
"ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x9ef45218
nid=0xa40 waiting for monitor entry [0x9d3ff000..0x9d3ff870]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x9ef460f8
nid=0xa3f runnable [0x9d1ff000..0x9d1ff870]
at weblogic.socket.PosixSocketMuxer.poll(Native Method)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:612)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x9ef64588
nid=0xa3e waiting for monitor entry [0x9cfff000..0x9cfff870]
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
"ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x9ef69070
nid=0xa3d waiting on monitor [0x9cdff000..0x9cdff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x9ef6abb8
nid=0xa3c waiting on monitor [0x9cbff000..0x9cbff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x9ef6a5d8
nid=0xa3b waiting on monitor [0x9c9ff000..0x9c9ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x9ef69be8
nid=0xa3a waiting on monitor [0x9c7ff000..0x9c7ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '1' for queue: 'lookup_servlet'" daemon prio=1
tid=0x9ef699f8 nid=0xa39 waiting on monitor [0x9c5ff000..0x9c5ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread: '0' for queue: 'lookup_servlet'" daemon prio=1
tid=0x9b705c18 nid=0xa38 waiting on monitor [0x9c3ff000..0x9c3ff870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"Thread-0" daemon prio=1 tid=0x9effaea8 nid=0xa34 waiting on monitor
[0x9c1ff000..0x9c1ff870]
at java.lang.Thread.sleep(Native Method)
at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1660)
at java.lang.Thread.run(Thread.java:479)
"Signal Dispatcher" daemon prio=1 tid=0x80be850 nid=0x9fe waiting on
monitor [0..0]
"Finalizer" daemon prio=1 tid=0x80b69e8 nid=0x9fb waiting on monitor
[0x983ae000..0x983ae870]
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
"Reference Handler" daemon prio=1 tid=0x80b6618 nid=0x9fa waiting on
monitor [0x981ae000..0x981ae870]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
"main" prio=1 tid=0x804f3d0 nid=0x9e0 waiting on monitor
[0xbfffb000..0xbfffb8b4]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:415)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1042)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:313)
at weblogic.Server.main(Server.java:32)
"VM Thread" prio=1 tid=0x80b3d68 nid=0x9f9 runnable
"VM Periodic Task Thread" prio=1 tid=0x80bd4a0 nid=0x9fc waiting on
monitor
"Suspend Checker Thread" prio=1 tid=0x80bde78 nid=0x9fd runnable
==============
Output of top:
11:17am up 20:14, 2 users, load average: 1.16, 1.28, 1.50
185 processes: 183 sleeping, 2 running, 0 zombie, 0 stopped
CPU0 states: 0.1% user, 65.1% system, 0.0% nice, 34.0% idle
CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle
Mem: 2316784K av, 2306924K used, 9860K free, 72K shrd,
90844K buff
Swap: 2097112K av, 0K used, 2097112K free
1178236K cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
COMMAND
2560 root 14 0 943M 943M 42492 R 99.9 41.7 1155m java
30119 wf 11 0 1288 1284 832 R 66.0 0.0 0:03 top
1 root 8 0 520 520 452 S 0.0 0.0 0:04 init
2 root 9 0 0 0 0 SW 0.0 0.0 0:00
keventd
===========================================================
Output of vmstat (when I believe the rogue thread started):
procs memory swap io system
cpu
r b w swpd free buff cache si so bi bo in cs
us sy id
0 0 0 0 1556812 15476 274440 0 0 0 212 445 845
17 1 82
0 0 0 0 1556780 15476 274476 0 0 0 0 400 667
6 0 93
0 0 0 0 1556736 15476 274484 0 0 0 0 175 361
1 1 98
4 0 1 0 1554032 15480 274564 0 0 0 94 651 2769
25 3 72
1 0 0 0 1553936 15480 274672 0 0 0 0 826 3072
33 4 63
0 0 0 0 1553804 15484 274772 0 0 0 208 836 1898
25 4 72
0 0 0 0 1553764 15484 274816 0 0 0 0 424 1510
8 1 91
4 0 0 0 1553564 15484 275144 0 0 0 0 1479 7049
64 10 26
4 0 2 0 1553484 15496 275464 0 0 0 342 1471 8538
57 7 36
1 0 0 0 1553368 15496 275632 0 0 0 0 940 3199
55 5 40
1 0 0 0 1553308 15496 275720 0 0 0 316 580 1437
63 3 34
1 0 0 0 1553304 15496 275776 0 0 0 0 606 1108
71 1 28
1 0 0 0 1553288 15496 275912 0 0 0 0 683 1740
68 3 29
2 0 1 0 1543236 15500 275980 0 0 0 180 383 3191
66 2 33"laxman" <[email protected]> wrote in message
news:[email protected]...
|
| I have had the exact same problem! It took us a long time to find the
resolution.
| I had a BEA engineer and a SUN engineer on site and finally we discovered
it
| to be a problem with the SUN JVM JDK1.3.1
|
| The BEA contact who resolved this for us is Richard Wallace.
|
| -- Laxman
|
|
| Rob Woollen <[email protected]> wrote:
| >Interesting. I think we'll need even more information to know for sure
| >
| >what's going on here. WLS (almost) never creates threads after it
| >starts. However, it does fork a process to compile JSPs. I'm
| >suspicious this could be a spinning javac process. If you cat
| >/proc/<pid>/cmdline then we should be able to tell whether it's a server
| >
| >thread or a javac process.
| >
| >Does your app start any threads or processes? The thread dump you
| >showed appeared to be idle.
| >
| >-- Rob
| >
| >Chishun Kwong wrote:
| >> Hello,
| >>
| >> My application is a servlet/EJB/Oracle application running on
| >> WebLogic.
| >> During stress test, I am seeing a java thread that is taking up 50%
| >of
| >> available cpu on a dual cpu machine. The thread remains at 100% even
| >> after the load is over.
| >> Here are some data and observations:
| >>
| >> 0. I am running WebLogic 7.0.1 on RedHat 7.2 (kernel 2.4.9-31), dual
| >> cpu. My application consists of a few servlets talking to some 20
| >> stateless session beans which uses CMP 2.0 entity beans to talk to
| >> Oracle 9.0.1. We are using the oci jdbc driver.
| >>
| >> 1. After the load was over, I used ps and saw that the thread was
| >> still running. I tracked its parent to the weblogic root process.
| >>
| >> 2. I ran top and saw the thread taking up 50% of available cpu
| >> (sometimes it is 100% of a cpu, but it may also be 60% of cpu1 and
| >40%
| >> of cpu2, etc).
| >>
| >> 3. I did a full thread dump, all but one thread are weblogic's or the
| >> jvm's internal threads. My application did have one thread remaining,
| >> but it is a periodic cleanup thread that wakes up every 30 secs and
| >I
| >> believe it is benign. I am not able to quickly point out which thread
| >> is the rogue thread.
| >>
| >> 4. Using vmstat, I believe the rogue thread kicked in about 10 minutes
| >> into the load (but this number varies from load to load, there was
| >one
| >> that kicked in after an hour). After that point, I saw the number of
| >> runnable process remained at least one, and the idle cpu never goes
| >> above 50 (remember it is a dual cpu machine). After I stopped the
| >> load, the number of runnable process stayed at 1 and the idle cpu
| >> stayed at 50.
| >>
| >> 5. This thread does not always kicked in, sometimes I would be able
| >to
| >> complete a 24-hour load and did not see the evidence of the thread.
| >>
| >> 6. The presence of the thread caused a 30% performance degradation.
| >>
| >> So here is the question, what is this thread and how can I stop it
| >> from kicking in?
| >>
| >> I have attached a full thread dump and the outputs of top and vmstat.
| >> I have also searched previous posts and apparently this has been seen
| >> before by other users of weblogic, but in those threads of discussions
| >> I never saw a resolution.
| >>
| >> Thanks in advance,
| >> Chishun Kwong
| >>
| >> =================
| >>
| >> Full thread dump:
| >>
| >> "Thread-11" daemon prio=1 tid=0x9b793138 nid=0xc59 waiting on monitor
| >> [0xa7153000..0xa7153870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
com.mycompany.myapp.SomeCleanupThread.run(SomeCleanupThread.java:234)
| >>
| >> "ListenThread.Default" prio=1 tid=0x9fad0578 nid=0xb58 runnable
| >> [0xa694f000..0xa694f870]
| >> at java.net.PlainSocketImpl.socketAccept(Native Method)
| >> at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
| >> at java.net.ServerSocket.implAccept(ServerSocket.java:238)
| >> at java.net.ServerSocket.accept(ServerSocket.java:217)
| >> at
weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
| >> at weblogic.t3.srvr.ListenThread.run(ListenThread.java:256)
| >>
| >> "ExecuteThread: '1' for queue: 'JMSStore<null>.ioThreadPool'" daemon
| >> prio=1 tid=0x9fa0b438 nid=0xb27 waiting on monitor
| >> [0xa674f000..0xa674f870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMSStore<null>.ioThreadPool'" daemon
| >> prio=1 tid=0x9fa0b2d0 nid=0xb26 waiting on monitor
| >> [0xa5dec000..0xa5dec870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon prio=1
| >> tid=0x8527000 nid=0xb21 waiting on monitor [0xa5bec000..0xa5bec870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.jms.backend.BETimerTree.execute(BETimerTree.java:140)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x83bec38 nid=0xb20 waiting on monitor [0xa37eb000..0xa37eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x83beae8 nid=0xb1f waiting on monitor [0xa35eb000..0xa35eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x85198f8 nid=0xb1e waiting on monitor [0xa33eb000..0xa33eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon prio=1
| >> tid=0x85d8368 nid=0xb1d waiting on monitor [0xa31eb000..0xa31eb870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "CoreHealthMonitor" daemon prio=1 tid=0x8138938 nid=0xa97 waiting on
| >> monitor [0xa2cff000..0xa2cff870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
weblogic.t3.srvr.CoreHealthMonitorThread.run(CoreHealthMonitorThread.java:11
4)
| >>
| >> "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x83be530 nid=0xa96 waiting on monitor [0xa29ff000..0xa29ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8246120 nid=0xa95 waiting on monitor [0xa27ff000..0xa27ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x834e868 nid=0xa94 waiting on monitor [0xa25ff000..0xa25ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x85813f8 nid=0xa93 waiting on monitor [0xa23ff000..0xa23ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x83be860 nid=0xa92 waiting on monitor [0xa21ff000..0xa21ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8504748 nid=0xa91 waiting on monitor [0xa1fff000..0xa1fff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x82f2908 nid=0xa90 waiting on monitor [0xa1dff000..0xa1dff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8396dd0 nid=0xa8f waiting on monitor [0xa1bff000..0xa1bff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8588b78 nid=0xa8e waiting on monitor [0xa19ff000..0xa19ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x858e000 nid=0xa8d waiting on monitor [0xa17ff000..0xa17ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x844c6b0 nid=0xa8c waiting on monitor [0xa15ff000..0xa15ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x837b8b0 nid=0xa8b waiting on monitor [0xa13ff000..0xa13ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x82158f0 nid=0xa8a waiting on monitor [0xa11ff000..0xa11ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x840a6f8 nid=0xa89 waiting on monitor [0xa0fff000..0xa0fff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=1
| >> tid=0x8398578 nid=0xa88 waiting on monitor [0xa0dff000..0xa0dff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x8222408 nid=0xa87 waiting on monitor
| >> [0xa0bff000..0xa0bff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x847df98 nid=0xa86 waiting on monitor
| >> [0xa09ff000..0xa09ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'"
| >> daemon prio=1 tid=0x856cd28 nid=0xa85 waiting on monitor
| >> [0xa07ff000..0xa07ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "Thread-4" prio=1 tid=0x8523528 nid=0xa84 waiting on monitor
| >> [0xa05ff000..0xa05ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.util.TimerThread.mainLoop(Timer.java:427)
| >> at java.util.TimerThread.run(Timer.java:380)
| >>
| >> "ExecuteThread: '1' for queue: 'DRS'" daemon prio=1 tid=0x8582bc0
| >> nid=0xa83 waiting on monitor [0x9feff000..0x9feff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'DRS'" daemon prio=1 tid=0x85640d8
| >> nid=0xa82 waiting on monitor [0x9fcff000..0x9fcff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "VDE Transaction Processor Thread" prio=1 tid=0xa021c060 nid=0xa53
| >> waiting on monitor [0x9f9ff000..0x9f9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at
com.octetstring.vde.backend.standard.TransactionProcessor.waitChange(Transac
tionProcessor.java:306)
| >> at
com.octetstring.vde.backend.standard.TransactionProcessor.run(TransactionPro
cessor.java:192)
| >>
| >> "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030f218 nid=0xa52 waiting on monitor
| >> [0x9f7ff000..0x9f7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030e7d0 nid=0xa51 waiting on monitor
| >> [0x9f5ff000..0x9f5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030dd88 nid=0xa50 waiting on monitor
| >> [0x9f3ff000..0x9f3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030d340 nid=0xa4f waiting on monitor
| >> [0x9f1ff000..0x9f1ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030c8f8 nid=0xa4e waiting on monitor
| >> [0x9edff000..0x9edff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030beb0 nid=0xa4d waiting on monitor
| >> [0x9ebff000..0x9ebff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030b468 nid=0xa4c waiting on monitor
| >> [0x9e9ff000..0x9e9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa030aa20 nid=0xa4b waiting on monitor
| >> [0x9e7ff000..0x9e7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa0309fd8 nid=0xa4a waiting on monitor
| >> [0x9e5ff000..0x9e5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon
| >> prio=1 tid=0xa0309990 nid=0xa49 waiting on monitor
| >> [0x9e3ff000..0x9e3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon
| >> prio=1 tid=0xa0309748 nid=0xa48 waiting on monitor
| >> [0x9e1ff000..0x9e1ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon
| >> prio=1 tid=0xa0309530 nid=0xa47 waiting on monitor
| >> [0x9dfff000..0x9dfff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "TimeEventGenerator" daemon prio=1 tid=0x9ef68d50 nid=0xa46 waiting
| >on
| >> monitor [0x9ddff000..0x9ddff870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
| >> at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:139)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=1
| >> tid=0x9b77b5e0 nid=0xa45 waiting on monitor [0x9dbff000..0x9dbff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=1
| >> tid=0x9b77b3c8 nid=0xa44 waiting on monitor [0x9d9ff000..0x9d9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "HighPriority TimeEventGenerator" daemon prio=1 tid=0x9b77b1d8
| >> nid=0xa43 waiting on monitor [0x9d7ff000..0x9d7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:272)
| >> at
weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
:139)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "SpinnerRandomSource" daemon prio=1 tid=0x9bfc1e48 nid=0xa41 waiting
| >> on monitor [0x9d5ff000..0x9d5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at
weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:6
0)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "ExecuteThread: '6' for queue: 'default'" daemon prio=1 tid=0x9ef45218
| >> nid=0xa40 waiting for monitor entry [0x9d3ff000..0x9d3ff870]
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '5' for queue: 'default'" daemon prio=1 tid=0x9ef460f8
| >> nid=0xa3f runnable [0x9d1ff000..0x9d1ff870]
| >> at weblogic.socket.PosixSocketMuxer.poll(Native Method)
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:612)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '4' for queue: 'default'" daemon prio=1 tid=0x9ef64588
| >> nid=0xa3e waiting for monitor entry [0x9cfff000..0x9cfff870]
| >> at
weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:607)
| >> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
| >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
| >>
| >> "ExecuteThread: '3' for queue: 'default'" daemon prio=1 tid=0x9ef69070
| >> nid=0xa3d waiting on monitor [0x9cdff000..0x9cdff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '2' for queue: 'default'" daemon prio=1 tid=0x9ef6abb8
| >> nid=0xa3c waiting on monitor [0x9cbff000..0x9cbff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'default'" daemon prio=1 tid=0x9ef6a5d8
| >> nid=0xa3b waiting on monitor [0x9c9ff000..0x9c9ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'default'" daemon prio=1 tid=0x9ef69be8
| >> nid=0xa3a waiting on monitor [0x9c7ff000..0x9c7ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '1' for queue: 'lookup_servlet'" daemon prio=1
| >> tid=0x9ef699f8 nid=0xa39 waiting on monitor [0x9c5ff000..0x9c5ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "ExecuteThread: '0' for queue: 'lookup_servlet'" daemon prio=1
| >> tid=0x9b705c18 nid=0xa38 waiting on monitor [0x9c3ff000..0x9c3ff870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:105)
| >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
| >>
| >> "Thread-0" daemon prio=1 tid=0x9effaea8 nid=0xa34 waiting on monitor
| >> [0x9c1ff000..0x9c1ff870]
| >> at java.lang.Thread.sleep(Native Method)
| >> at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1660)
| >> at java.lang.Thread.run(Thread.java:479)
| >>
| >> "Signal Dispatcher" daemon prio=1 tid=0x80be850 nid=0x9fe waiting on
| >> monitor [0..0]
| >>
| >> "Finalizer" daemon prio=1 tid=0x80b69e8 nid=0x9fb waiting on monitor
| >> [0x983ae000..0x983ae870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:103)
| >> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
| >> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:157)
| >>
| >> "Reference Handler" daemon prio=1 tid=0x80b6618 nid=0x9fa waiting on
| >> monitor [0x981ae000..0x981ae870]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:105)
| >>
| >> "main" prio=1 tid=0x804f3d0 nid=0x9e0 waiting on monitor
| >> [0xbfffb000..0xbfffb8b4]
| >> at java.lang.Object.wait(Native Method)
| >> at java.lang.Object.wait(Object.java:415)
| >> at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1042)
| >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:313)
| >> at weblogic.Server.main(Server.java:32)
| >>
| >> "VM Thread" prio=1 tid=0x80b3d68 nid=0x9f9 runnable
| >>
| >> "VM Periodic Task Thread" prio=1 tid=0x80bd4a0 nid=0x9fc waiting on
| >> monitor
| >> "Suspend Checker Thread" prio=1 tid=0x80bde78 nid=0x9fd runnable
| >>
| >> ==============
| >>
| >> Output of top:
| >>
| >> 11:17am up 20:14, 2 users, load average: 1.16, 1.28, 1.50
| >> 185 processes: 183 sleeping, 2 running, 0 zombie, 0 stopped
| >> CPU0 states: 0.1% user, 65.1% system, 0.0% nice, 34.0% idle
| >> CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle
| >> Mem: 2316784K av, 2306924K used, 9860K free, 72K shrd,
| >
| >> 90844K buff
| >> Swap: 2097112K av, 0K used, 2097112K free
| >> 1178236K cached
| >>
| >> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME
| >> COMMAND
| >> 2560 root 14 0 943M 943M 42492 R 99.9 41.7 1155m java
| >> 30119 wf 11 0 1288 1284 832 R 66.0 0.0 0:03 top
| >> 1 root 8 0 520 520 452 S 0.0 0.0 0:04 init
| >> 2 root 9 0 0 0 0 SW 0.0 0.0 0:00
| >> keventd
| >>
| >> ===========================================================
| >>
| >> Output of vmstat (when I believe the rogue thread started):
| >>
| >> procs memory swap io system
| >
| >> cpu
| >> r b w swpd free buff cache si so bi bo in cs
| >
| >> us sy id
| >> 0 0 0 0 1556812 15476 274440 0 0 0 212 445 845
| >
| >> 17 1 82
| >> 0 0 0 0 1556780 15476 274476 0 0 0 0 400 667
| >
| >> 6 0 93
| >> 0 0 0 0 1556736 15476 274484 0 0 0 0 175 361
| >
| >> 1 1 98
| >> 4 0 1 0 1554032 15480 274564 0 0 0 94 651 2769
| >
| >> 25 3 72
| >> 1 0 0 0 1553936 15480 274672 0 0 0 0 826 3072
| >
| >> 33 4 63
| >> 0 0 0 0 1553804 15484 274772 0 0 0 208 836 1898
| >
| >> 25 4 72
| >> 0 0 0 0 1553764 15484 274816 0 0 0 0 424 1510
| >
| >> 8 1 91
| >> 4 0 0 0 1553564 15484 275144 0 0 0 0 1479 7049
| >
| >> 64 10 26
| >> 4 0 2 0 1553484 15496 275464 0 0 0 342 1471 8538
| >
| >> 57 7 36
| >> 1 0 0 0 1553368 15496 275632 0 0 0 0 940 3199
| >
| >> 55 5 40
| >> 1 0 0 0 1553308 15496 275720 0 0 0 316 580 1437
| >
| >> 63 3 34
| >> 1 0 0 0 1553304 15496 275776 0 0 0 0 606 1108
| >
| >> 71 1 28
| >> 1 0 0 0 1553288 15496 275912 0 0 0 0 683 1740
| >
| >> 68 3 29
| >> 2 0 1 0 1543236 15500 275980 0 0 0 180 383 3191
| >
| >> 66 2 33
| >
|
|
Is this specific to a version of the 1.3.1 JVM? (1.3.1_x)?
k -
Memory maxed out when running weblogic 4.5
I am the tech support guy for my office, but I am WebLogic illiterate. I have a user who is running WebLogic, but when he runs it, his RAM and virtual memory max out. Are there any settings in WebLogic for memory allocation? Or is there a known problem with memory?
Please see my reply in misc.
Michael Girdley
Product Manager, WebLogic Server
BEA Systems Inc.
Jay A. Fulks <[email protected]> wrote in message
news:89gt0e$91a$[email protected]..
Hi.
I am running WebLogic 4.5.1.5 under Solaris 2.6. I am using JDK 1.2.2
with HotSpot. When we shutdown our server, it essentially crashes with
the following error:
# HotSpot Virtual Machine Error, Unexpected Signal 11
# Error happened during: mark sweep
# Error ID: 4F533F534F4C415249530E4350500BC2 01
After looking into the problem, we found that it is easily recreatable,
simply
by (1) starting the server, (2) hitting any web page (which causes
FileServlet
to be loaded), and (3) shutting down the server.
I have attached a tail of my log file as evidence.
Anybody else seen this problem? Is it a Weblogic/HotSpot compatibility
problem?
Thanks. -
Unable to start weblogic with JRockit
i am using a 32 bit machine to start weblogic server on JRockit JVM. Doing this in order to have already installed Oracle SOA suite and when I start weblogic using JRockit it is Running out of memory. Tried the solutions given in the forum but not able to resolve this issue.
Also when using jdk getting permgen error. Tried with resetting the maxPermSize value etc in the startweblogic server but not able to do so.
For JRockit OOM has any one faced a similar issue?
Can any one help me with same ?Thanks Carlos. The value was getting overridden in startweblogic.cmd for Sun jdk but was not sufficient for my problem as I was using Jrockit and with JRockit there is no Permsize issue inturn there was OOM.
I followed these steps:
1. changed maxpermsize in startweblogic.
2. Tried increasing system swap space.
3. Used a profiler which controls JVM running, tried reduce memory leaks, but none worked.
I switched to JRockit for weblogic
1. tried increasing memory etc. Finally I switched to 64 bit machine as suggested in one of the forums for JRockit oom.
Now both jdk and JRockit weblogic with all SOA components working successfully.
Thanks,
Dipti Karnataki -
Running Weblogic Server 7.0 SP4 using JDK 1.4
Is it possible to run Weblogic Server 7.0 SP4 with a different JRE than the one
that ships with 7.0 SP4. I am having issues with a bug in JDK 1.3.1 which when
I run under JBuilder X using 1.4 is not there. ANy help as to how I go about
doing this would be welcomed.
Thanks
JustinYes,
The JDK is just the Sun JDK...nothing special. You may upgrade minor versions quite safely by dowloading later one at Sun website and pointting your "JAVA_HOME" at it.
I would not jump to 1.4, as changes in java language may impact. -
Running Weblogic Server 10.3.3 in Debug mode
Hi to all,
Here i got a problem after installing Oracle Identity Manager 11g R3,to solve the issue i need to run WebLogic Server 10.3.3 in Debug mode.
Can any suggest how to run WebLogic Server 10.3.3 in Debug mode.
Here i find a solution to run in debug mode,but no difference in log files before and after changing debug mode.
Enable Debugging on the WebLogic Server
To start WebLogic Server in debug mode, you will need to modify the startWebLogic.cmd script in the <WLS-root>\wlserver_10.0\samples\domains\wl_server directory. <WLS-root> is the directory in which WebLogic 10.0.1 was installed into.
In the startWebLogic.cmd script, specify the JAVA OPTIONS with:
set JAVA_OPTIONS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=n
Let me know if u have any questions,
Thanks and Ragards,
SatishGreg,
I cam across this issue too. It looks like there is a bug in sample script provided by weblogic documentation. We should not use ADMIN_URL as they mentioned in the script.
Remove it and try. For more info. please see this link helps:
http://ananthkannan.blogspot.com/2009/10/weblogic-server-instance-as-window.html
Thanks.
Ananth -
Running weblogic as a service on NT
We are currently trying to run weblogic as a service on Windows NT. Yet the service
has hung once and run out of memory once. The hardware and software specification
is listed below.
Hardware
System Intel
CPU: Dual 866 MHz or faster
Memory: 500 MB
Hard Drives: 2 x 10 GB RAID-1 System Drive
Network: Static IP allocation and TCP/IP network protocolTwo Fast Ethernet 10/100
Software
Windows NT 4.0 Option Pack Typical InstallBEA WebLogic Version 5.1 with Service Pack
8 and JDBC drivers for MSSQL ServerJava 2 SDK Version 1.3.1 RC 2
The WebLogic server has been using the srvany.exe and instsrv.ex utilities (part
of the NT Resource Kit) . Note that it is necessary to use the srvany utility rather
than the custom BEA service utilities in order to allow the passing of command line
parameters to the JVM. An important JVM parameter is –Xrs which prevents JDK1.3
applications which run as a service on NT from shutting-down when the user who started
the service logs out. This problem does not occur on Win2K systems.
1. Set-up a ‘weblogic’ user account that is a member of the Users group
and has explicitly assigned 'log on as a service' right.
2. At a command prompt install srvany with the command
INSTSRV WGO_server c:\winnt\system32\srvany.exe
3. Use the services applet (in the Control Panel) to ensure that the service will
run using the weblogic account and that the service is set for automatic startup
4. Use the Registry Editor REGEDT32.exe to configure srvany as follows:
a. Highlight HKEY_LOCAL_MACHINE\SYSTEM\CurrentContrelSet\Services\WGO_server and
select Add Key from the edit menu.
b. The key to be added should have the name “Parameters” – the
class field may be left empty.
c. Highlight the newly created Parameters key and select the Add Value option from
the edit menu. The name of the value to be added is “Application” and
the type of value is REG_SZ. When you o.k. these options, you will be asked to provide
the string value representing the application to be triggered by servany –
type in the path to the startweblogic.cmd file:
c:\weblogic\WGO_server\startweblogic.cmd
d. With the Parameters key still highlighted, select the Add Value option from the
edit Menu. The name of the value is “AppDirectory” and the type is REG_SZ.
Set the directory in which the application runs by typing in the path
c:\weblogic\WGO_server
5. To start the weblogic server, return to the Service applet in the control panel
and start the service named WGO_server. To shutdown the service, first run the script
c:\weblogic\WGO_server\shutdown to shutdown weblogic cleanly, wait a few moments
and then stop the WGO_server service via the Service applet.
If anyone has experienced a similar problem please let me know
Thanks
JoI would look at all the other startup script you have on your machine already.
They are usually placed in /etc/init.d and these files are often linking into /etc/rc3.d
I suggest you google on how to setup a service for your flavour of linux as they are not all the same. -
Tryin to Profile weblogic with NetBeans Profiler, getting jrocke exception
Hi there,
I am using Weblogic 10, and want to profile a web application on it with Netbeans Profiler. But am getting the following exception upon starting weblogic (Please tell a solution......)
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Development
+.+
CLASSPATH=;C:\bea\patch_wls1001\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\JROCKI~1\lib\to
+;C:\bea\WLSERV~1.0\server\lib\weblogic_sp.jar;C:\bea\WLSERV~1.0\server\lib\weblogic.jar;C:\bea\modules\features\w+
+.server.modules_10.0.1.0.jar;C:\bea\modules\features\com.bea.cie.common-plugin.launch_2.1.2.0.jar;C:\bea\WLSERV~1+
er\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0/lib/ant-contrib.jar;;C
LSERV~1.0\common\eval\pointbase\lib\pbclient51.jar;C:\bea\WLSERV~1.0\server\lib\xqrl.jar;;
+.+
PATH=C:\bea\patch_wls1001\profiles\default\native;C:\bea\WLSERV~1.0\server\native\win\32;C:\bea\WLSERV~1.0\server
+\bea\modules\ORGAPA~1.5\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS+
+32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\CVSNT\;C:\bea\WLSERV~1.0\server\native\win\32\oci92+
+.+
+* 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:
Listening for transport dt_socket at address: 8453
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
BEA JRockit(R) (build R27.3.1-1_CR344434-89345-1.5.0_11-20070925-1628-windows-ia32, compiled mode)
Starting WLS with line:
C:\bea\JROCKI~1\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n
+.compiler=NONE -Xms256m -Xmx512m -agentpath:"C:\Program Files\NetBeans 6.1\profiler3\lib\deployed\jdk15\windows\+
+rinterface.dll=\"C:\Program Files\NetBeans 6.1\profiler3\lib\"",5140 -Xverify:none -ea -da:com.bea... -da:javel+
da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\bea\WLSERV~1.
+.home=C:\bea\WLSERV~1.0\server -Dweblogic.home=C:\bea\WLSERV~1.0\server -Dwli.home=C:\bea\WLSERV~1.0\integration+
ogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.di
ea\patch_wls1001\profiles\default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=C:
SERV~1.0\server\lib\weblogic.policy weblogic.Server
Profiler Agent: Initializing...
Profiler Agent: Options: >"C:\Program Files\NetBeans 6.1\profiler3\lib",5140<
Profiler Agent: Initialized succesfully
Listening for transport dt_socket at address: 8453
Profiler Agent: Waiting for connection on port 5140 (Protocol version: 8)
Profiler Agent: Established local connection with the tool
Profiler Agent: Unable to get address of JVM_DumpHeap function
+===== BEGIN DUMP =============================================================+
JRockit dump produced after 0 days, 00:00:20 on Thu Aug 28 18:46:28 2008
Additional information is available in:
C:\bea\user_projects\domains\nms_dev\jrockit.3728.dump
C:\bea\user_projects\domains\nms_dev\jrockit.3728.mdmp
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error Message: Unhandled native exception [85]
Exception Rec: EXCEPTION_STACK_OVERFLOW (c00000fd) at 0x004FE3DF
Minidump : Wrote mdmp. Size is 297MB
SafeDllMode : -1
.It looks like NetBeans does not support JRockit: http://profiler.netbeans.org/docs/help/5.5/vms.html
Regards,
/Staffan -
Hi OTNian,
Could you all please help me to understand below :
Does Weblogic with Apex 4.0 replaces OAS/SAO/Oracel web tier like HTTP sever functionality ?
background of quesion is:
we had hosted our oracle webplsql application using Oracle web tier using DAD configuration.
now some one sugegsted that we can use WLS(Weblogic server) with Apex 4.0,that too can work as HTTP sever for Oracel Webplsql application.Hi,
>
You asked:
Does Weblogic with Apex 4.0 replaces OAS/SAO/Oracel web tier like HTTP sever functionality ?
>
OAS = Oracle Application Server
SAO = Service Oriented Architecture ( this is not a server)
Oracle Web Tier is a bundle of matching servers for the web tier. Again is not a single server, its a collection.
APEX = A Rapid Application Development tool for webapplication development.
Oracle Apex runs with a number a J2EE Containers (Application Servers) and Oracle HTTP Server as well. It does not use OAS, only the OHS (mod_pls) and Cache, when configured on OHS.
APEX web access can be configured with ApexListener in a J2EE Container like WLS, Glassfish,etc.
PLSQL Web applications can be integrated into APEX applications and features, in the loose sense of the term, as they are.
Please search the forum to see what others have been doing for this.
I hope this clears up some aspects of your query.
Regards, -
What Solaris packages are needed to run WebLogic 5.1?
Solaris by default comes with 4 installation methods, namely core, end-user,
developer, full. In comparison, full consists of 300+ solaris packages and
core about 30+. I was wondering if there are any docs lying around on
specifcally what packages are required of Solaris 2.6 by Weblogic 5.1. Would
greatly appreciate any help here. Thx
Rgrds,
Wong.Acckk a full installation is bad... real bad for security in a production
env. You guys should investigate thoroughly exactly what packages are needed
to run JVM. There are a lot of useless binaries/libs in a full Solaris
installation. For the record, I installed a core installation + two packages
(required by JDK). The thing works anyhow... but I thought BEA would have
some guidelines on a Solaris installation for host security. I mean, even
M$ have guidelines on running IIS securely, and apache have theirs long ago.
Any of you guys ever tried stripping Solaris to run weblogic??
Rgrds,
Wong.
"Michael Girdley" <[email protected]> wrote in message
news:3988bbd3$[email protected]..
We certify with full installations, but others may work as well. The
ability to run the JVM is the biggest factor.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"C.M. Wong" <[email protected]> wrote in message
news:[email protected]..
Solaris by default comes with 4 installation methods, namely core,end-user,
developer, full. In comparison, full consists of 300+ solaris packages
and
core about 30+. I was wondering if there are any docs lying around on
specifcally what packages are required of Solaris 2.6 by Weblogic 5.1.Would
greatly appreciate any help here. Thx
Rgrds,
Wong.
Maybe you are looking for
-
Does VMIC driver support LV RT8.2?
Hello, Using VMIC-5565 instrument driver for LV, I am trying to setup reflective memory VMIC-5565 on LV RT 8.2. My problem is how to setup VMIC-5565 on RT and it is not detected on MAX. First, after installed the driver which is provided from GE FANU
-
Internal error code, ora-00600,inforrmatica
hi while running the session we are getting a error , internal error code help us out.
-
Data Migration to external hd. am i doing this right??
So i just got a new lacie 320gb hd and have some questions about using it. I clicked and dragged all my logic pro projects into the hd and it copied them all to it just fine. I did the same with the logic pro application itself. Now what this did was
-
Posting date changing manually-
Hi all, when we release a billing doc to accounting...can we change the posting date manually to the current date. If it is possible, how to do that in SAP . Is there any Transaction code for changing the date. thanx in advance sourav
-
Posting block for self billed invoices
Hi , My requirement is once a self billed invoice is generated , it should not be readily available for payment. It should be first treated as blocked for payment. There should be a manual check which when unticked would make the invoice ready to be