Weblogic Thread hogging at java.io.WinNTFileSystem.getBooleanAttributes at high loads

Hi,
At high loads, we are seeing that one WebLogic thread is active on a windows native call for quite some time.. I can see the following stack statements in thread dumps taken at 10 minutes interval. This has led to slow server performance.
This happens on WebLogic 10.3.2 that is hosted in Windows Server 64 bit 2008 Enterprise Edition SP1.
The JDK used is JRockit jdk1.6.0_20-R28.3.2 (64 Bit)
Also this happens at high user loads only and also irregularly.
Our eclipse link versions are (Implementation-Version: 1.0.1-20080905, Specification-Version: 1.0.1)
Any recommendation or pointer is appreciated.
Now the thread dump details
"[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE
            java.io.WinNTFileSystem.getBooleanAttributes(Native Method)
            java.io.File.isDirectory(File.java:754)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive$1.accept(DirectoryArchive.java:91)
            java.io.File.listFiles(File.java:1134)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:89)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.init(DirectoryArchive.java:95)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.<init>(DirectoryArchive.java:73)
            org.eclipse.persistence.internal.jpa.deployment.DirectoryArchive.<init>(DirectoryArchive.java:55)
            org.eclipse.persistence.internal.jpa.deployment.ArchiveFactoryImpl.createArchive(ArchiveFactoryImpl.java:76)
            org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.findPersistenceArchives(PersistenceUnitProcessor.java:184)
            org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.initialize(JPAInitializer.java:132)
            org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactory(PersistenceProvider.java:104)
            org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactory(PersistenceProvider.java:64)
            javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:78)
            javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:54)
            -- Our internal class calls
            org.jbpm.graph.def.Action.execute(Action.java:123)
            org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:235)
            org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:212)
            org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphElement.java:182)
            org.jbpm.graph.def.GraphElement.fireEvent(GraphElement.java:166)
            org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:120)
            org.jbpm.JbpmContext.newProcessInstance(JbpmContext.java:372)
            -- Our internal class calls
            sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            java.lang.reflect.Method.invoke(Method.java:597)
            org.apache.myfaces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:129)
            org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
            javax.faces.component.UICommand.broadcast(UICommand.java:106)
            org.ajax4jsf.framework.ajax.AjaxViewRoot.processEvents(AjaxViewRoot.java:180)
            org.ajax4jsf.framework.ajax.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:158)
            org.ajax4jsf.framework.ajax.AjaxViewRoot.processApplication(AjaxViewRoot.java:346)
            org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
            org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
            -- Our internal class calls
            javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
            weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
            weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
            weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
            weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127)
            org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277)
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            com.anychart.servlet.ResourceFilter.doFilter(ResourceFilter.java:53)
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            -- Our internal class calls
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            -- Our internal class calls
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
            weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
            weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
            weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
            weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
            weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
            weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
Maybe this thread could help, if it addresses your problem correctly:
Performance issues with class loader on Windows server
Regards,
Mohab

Similar Messages

Migration to Weblogic 10.3.5 + Java 1.6: xml errors

Hi all,
I describe my scenario:
I have a web application that works correctly on weblogic 8.1 + jdk 1.4.
Now i'm trying to migrate this web app on RHEL5 + weblogic 10.3.5 + Java SE Runtime Environment (build 1.6.0_25-b06).
Deploying stage gives me no errors (exploded folder), and application starting too.
But when i go into a section of the application that handles xml files, there are several errors like these, and i can't go on:
(package exception): Error calling (method)
at mypackage...
at mypackage...
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3717)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
This is the list of xml jars involved in the application:
     - esheetxml.jar
     - jaxb-api_1_0.jar
     - jaxb-libs.jar
     - jaxb-ri.jar
     - serializer.jar
     - sunxmlextension.jar
     - xalan.jar (1.3)
     - xercesImpl.jar
     - xerces.jar
     - xml-apis.jar
     - xmlparser2015mod.jar
     - xmlParserAPIs.jar
Main server log properties:
     -java.class.path = /home/weblogic10/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java/jdk1.6.0_25/lib/tools.jar:/home/weblogic10/wlserver_10.3/server/lib/weblogic_sp.jar:/home/weblogic10/wlserver_10.3/server/lib/weblogic.jar:/home/weblogic10/modules/features/weblogic.server.modules_10.3.5.0.jar:/home/weblogic10/wlserver_10.3/server/lib/webservices.jar:/home/weblogic10/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/weblogic10/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/weblogic10/wlserver_10.3/common/derby/lib/derbyclient.jar:/home/weblogic10/wlserver_10.3/server/lib/xqrl.jar
     -java.class.version = 50.0
     -java.endorsed.dirs = /usr/java/jdk1.6.0_25/jre/lib/endorsed
     -java.ext.dirs = /usr/java/jdk1.6.0_25/jre/lib/ext:/usr/java/packages/lib/ext
     -java.home = /usr/java/jdk1.6.0_25/jre
     -java.io.tmpdir = /tmp
     -java.library.path = /usr/java/jdk1.6.0_25/jre/lib/i386/client:/usr/java/jdk1.6.0_25/jre/lib/i386:/usr/java/jdk1.6.0_25/jre/../lib/i386:/home/weblogic10/patch_wls1035/profiles/default/native:/home/weblogic10/wlserver_10.3/server/native/linux/i686:/home/weblogic10/wlserver_10.3/server/native/linux/i686/oci920_8:/usr/java/packages/lib/i386:/lib:/usr/lib
     -java.runtime.version = 1.6.0_25-b06
     -java.version = 1.6.0_25
     -javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
     -javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
     -org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
     -org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
     -org.xml.sax.driver = weblogic.xml.jaxp.RegistryXMLReader
     -org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
     -os.name = Linux
     -os.version = 2.6.18-128.el5
     -sun.boot.class.path = /usr/java/jdk1.6.0_25/jre/lib/resources.jar:/usr/java/jdk1.6.0_25/jre/lib/rt.jar:/usr/java/jdk1.6.0_25/jre/lib/sunrsasign.jar:/usr/java/jdk1.6.0_25/jre/lib/jsse.jar:/usr/java/jdk1.6.0_25/jre/lib/jce.jar:/usr/java/jdk1.6.0_25/jre/lib/charsets.jar:/usr/java/jdk1.6.0_25/jre/lib/modules/jdk.boot.jar:/usr/java/jdk1.6.0_25/jre/classes
     -sun.boot.library.path = /usr/java/jdk1.6.0_25/jre/lib/i386
     -weblogic.ext.dirs = /home/weblogic10/patch_wls1035/profiles/default/sysext_manifest_classpath
     -weblogic.management.discover = true
I tried these actions, but without success:
- run Classloader Analysis Tool and insert <prefer-application-packages> list in weblogic.xml;
- copy these jars into java endorsed folder;
- force different xml parser into jvm parameters;
- tried proposed solutions about this topic in forum
I'm afraid there's a conflict between jar WL and jar application (or a parsing problem), but i'm not sure.
I hope in your help,
thank you.
George

Solved.
I removed glassfish.jaxb_1.0.0.0_2-1-12.jar from lib modules

Weblogic 10.0 Parsing Failure in config.xml: failed to load java type

Hello,
I've just installed a Weblogic 10.0 on a Linux server and when i try to start it, by :
bash$ : sudo -u weblogic ./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=128m
WLS Start Mode=Production
CLASSPATH=:/opt/weblogic/10.0/patch_wls1002/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/weblogic/10.0/patch_cie640/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/weblogic/10.0/jdk150_15/lib/tools.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic_sp.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic.jar:/opt/weblogic/10.0/modules/features/weblogic.server.modules_10.0.2.0.jar:/opt/weblogic/10.0/modules/features/com.bea.cie.common-plugin.launch_2.1.2.0.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/webservices.jar:/opt/weblogic/10.0/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/opt/weblogic/10.0/modules/net.sf.antcontrib_1.0b2.0/lib/ant-contrib.jar::/opt/weblogic/10.0/weblogic10.0/common/eval/pointbase/lib/pbclient51.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/xqrl.jar::
PATH=/opt/weblogic/10.0/weblogic10.0/server/bin:/opt/weblogic/10.0/modules/org.apache.ant_1.6.5/bin:/opt/weblogic/10.0/jdk150_15/jre/bin:/opt/weblogic/10.0/jdk150_15/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)
Starting WLS with line:
/opt/weblogic/10.0/jdk150_15/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -da -Dplatform.home=/opt/weblogic/10.0/weblogic10.0 -Dwls.home=/opt/weblogic/10.0/weblogic10.0/server -Dweblogic.home=/opt/weblogic/10.0/weblogic10.0/server -Dwli.home= -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/opt/weblogic/10.0/patch_wls1002/profiles/default/sysext_manifest_classpath:/opt/weblogic/10.0/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.security.providers.authentication.LDAPDelegatePoolSize=50 -Dweblogic.management.username=system -Dweblogic.management.password=admin9424 -Dweblogic.Name=AdminServer -Djava.security.policy=/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic.policy weblogic.Server
<Jun 7, 2010 9:49:12 AM CEST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n-schemas.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n_common.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n_system.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/wlp_services.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_common.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_schemas.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_system.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/wsrp-client.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/wsrp-common.jar>
<Jun 7, 2010 9:49:13 AM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_15-b04 from Sun Microsystems Inc.>
<Jun 7, 2010 9:49:13 AM CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP2 Sat Apr 25 01:45:38 EDT 2009 1213942 >
i got the following error messages :
*<Jun 7, 2010 9:49:14 AM CEST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: failed to load java type corresponding to e=domain@http://www.bea.com/ns/weblogic/920/domain>*
<Jun 7, 2010 9:49:14 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 7, 2010 9:49:14 AM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 7, 2010 9:49:14 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
If i start the server as root, it boots but i cant deploy anything.
Any idea about this behavior ?

Hi,
It is the problem in prasing the DTD of config.xml file
It look like this
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml http://www.bea.com/
ns/weblogic/90/security/xacml.xsd http://www.bea.com/ns/weblogic/90/security http://www.bea.com/ns/weblogic/90/security.xsd http://www.bea.com/ns/weblogic/92
0/domain http://www.bea.com/ns/weblogic/920/domain.xsd http://www.bea.com/ns/weblogic/90/security/wls http://www.bea.com/ns/weblogic/90/security/wls.xsd">
Please change your DTD to this lines and start the server.
Regards
Ravi D

Weblogic 10.0 error java.lang.NoClassDefFoundError:

Hi,
I am using weblogic 10.0 and trying to upload the EAR which is build using Weblogic Workshop 8.1 SP4. i am gettign the following error:
####<Feb 13, 2010 2:36:48 AM IST> <Error> <Deployer> <STPLT1005> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266008808529> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266008804528' for task '0'. Error is: 'java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/AsyncDispatcherBean : weblogic/ejb20/interfaces/JmsMessageDrivenBean'
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/AsyncDispatcherBean : weblogic/ejb20/interfaces/JmsMessageDrivenBean
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
     at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
     at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)

Hello,
I have not seen this particular error before, but if you can re-build the EJB using Workshop 10.0 I bet it will fix your problem. The old Workshop is running an old version of appc which the 10.0 version of WLS is probably not expecting.
Kevin

How to use a Java Thread in a Java Stored Procedure?

I am working with java stored Procedures but i have a problem when i use threads.While the thread is running all the processes are blocked because the thread is not detatched.I don't know if it is impossible to use Thread in a java stored procedure.i made many researches but didn't find information about this case of Thread.If someone knows what to do in this case it will be helpfull for me.Thanks

The JAR is already load by using CREATE JAVA RESOURCE ... or "loadjava -resolve –force -user p/p@SID –genmissing -jarasresource MyJar.jar"
If we can create a resource by SQL or loadjava, how can I use it in my java code?
Edited by: 847873 on 28 mars 2011 06:05
Edited by: 847873 on 28 mars 2011 06:07

Custom thread pool for Java 8 parallel stream

It seems that it is not possible to specify thread pool for Java 8 parallel stream. If that's so, the whole functionality is useless in most of the situations. The only situation I can safely use it is a small single threaded application written by one person.
In all other cases, if I can not specify the thread pool, I have to share the default pool with other parts of the application. If someone submits a task that takes a lot of time, my tasks will get stuck. Is that correct or am I overlooking something?
Imagine that someone submits slow networking operation to the fork-join pool. It's not a good idea, but it's so tempting that it will be happening. In such case, all CPU intensive tasks executed on parallel streams will wait for the networking task to finish. There is nothing you can do to defend your part of the application against such situations. Is that so?

You are absolutely correct. That isn't the only problem with using the F/J framework as the parallel engine for bulk operations. Have a look http://coopsoft.com/ar/Calamity2Article.html

Need help with the threads concept in java

i need a good explanation for the threads concept in java.Explanation with an example would be better.

JosAH wrote:
BIJ001 wrote:
Java still can't process them in real time because of its garbage collector.So real-time java is not conceivable \qu.e.d
http://java.sun.com/javase/technologies/realtime/index.jsp
http://jcp.org/en/jsr/detail?id=282
Is that implementation ready yet? The first link talks about 'more real time'; that garbage collector really is a burden when it comes to the real ticks ...
kind regards,
JosSpoon!

Starting weblogic server from a java application

Hello,
I am trying to start the weblogic server from a java application i wrote.
the code:
Process p=null;
try{
p= Runtime.getRuntime().exec("cmd /c c:/startWeblogic.cmd");
catch (Exception e)\[
this doesn't start the weblogic... Using the same line to start other types of files does work... only file with the extention of cmd i can't run.
I even tried to write a bat file that calls the cmd file but it still does't work.
Can someone help?
THANKS!!!
P.S.
The Java application I used implement the SysTrayMenuListner - can this be the problem?

no - nothing happened. it perform the next java code - and there is nothing else happen on the windows.
maybe i don't check in the right place for the error you are talking about?
i also tried i simple cmd file that does nothing - but still nothing...
for any other file types it works properly.

Weblogic thread issue

I am using Weblogic portal server 7.0 SP2
Lately, whenever there is a backend system failure (database or any other system), eventually, all weblogic threads wait for the backend connection and get stuck. I get following message for all threads
ExecuteThread: '28' for queue: 'default' has been busy for "785" seconds working on the request "Http Request: XXXXXX, which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Any idea why such a thing can happen?

You have a contention problem at back end ...

WebLogic 5.1 sp9 + java 1.3 startup problem.

Hi all,
I'm getting this error just with Java 1.3 - No probs with 1.2
at all. Same weblogic.properties, same startWebLogic.sh, etc. etc.
Tue Aug 28 12:57:58 GMT+01:00 2001:<I> <WebLogicServer> Invoking main-style
startup weblogic.jdbc.common.internal.JdbcStartup
weblogic.jdbc.common.internal.JdbcStartup
Tue Aug 28 12:57:58 GMT+01:00 2001:<E> <WebLogicServer> Failed to invoke
startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.
JdbcStartup
java.security.AccessControlException: access denied (java.sql.SQLPermission
setLog)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.
java:272)
at java.security.AccessController.checkPermission(AccessController.java:399)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.sql.DriverManager.setLogStream(DriverManager.java:397)
at weblogic.jdbc.common.internal.JdbcInfo.initLog(JdbcInfo.java:66)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:242)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
Thanks,
Brian.
Brian Scanlan, Systems Administrator.
Irish Times New Media - http://www.ireland.com

I think t WLS 5.1 SP 9 is support on JDK 1.3.0
http://e-docs.bea.com/wls/platforms/index.html#mix
Using Solaris 2.6, 2.7 and 8 on WebLogic 5.1.0 with Service Pack 9 or higher,
BEA has successfully tested client applications running under JDK 1.2.2_05a when
connecting to a server running SDK 1.3.0.
Thanks
"Sergio Ríos Mendoza" <[email protected]> wrote:
>
I had exactly the same problem and you know what was the response from
BEA? "Java
1.3 is not supported"
So, now i'm trying WLS 6.0 just because my boss want Java 1.3
Anyway, hope this helps
Regards from Mexico
Sergio Ríos
[email protected] () wrote:
Hi all,
I'm getting this error just with Java 1.3 - No probs with 1.2
at all. Same weblogic.properties, same startWebLogic.sh, etc. etc.
Tue Aug 28 12:57:58 GMT+01:00 2001:<I> <WebLogicServer> Invoking main-style
startup weblogic.jdbc.common.internal.JdbcStartup
weblogic.jdbc.common.internal.JdbcStartup
Tue Aug 28 12:57:58 GMT+01:00 2001:<E> <WebLogicServer> Failed to invoke
startup class
weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.
JdbcStartup
java.security.AccessControlException: access denied (java.sql.SQLPermission
setLog)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.
java:272)
at java.security.AccessController.checkPermission(AccessController.java:399)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.sql.DriverManager.setLogStream(DriverManager.java:397)
at weblogic.jdbc.common.internal.JdbcInfo.initLog(JdbcInfo.java:66)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:242)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
Thanks,
Brian.
Brian Scanlan, Systems Administrator.
Irish Times New Media - http://www.ireland.com

Weblogic 6.1 SP4 java.lang.UnsatisfiedLinkError: getEGroup0

Hi.
Why do I receive the following error message when execute startWeblogic.sh
The WebLogic Server did not start up properly.
Exception raised:
java.lang.UnsatisfiedLinkError: getEGroup0
at weblogic.platform.Unix.getEGroup0(Native Method)
at weblogic.platform.Unix.getEffectiveGroup(Unix.java:96)
at weblogic.t3.srvr.T3Srvr.switchEffectiveGroup(T3Srvr.java:1364)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:212)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
I use Solaris 7 with Weblogic 6.1 SP4 and environments :
LD_LIBRARY_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib:/opt/oracle7/product/8
..1.7/lib:/opt/bea/wlserver6.1/lib/solaris:/opt/bea/wlserver6.1/lib/solaris/o
ci817_8:/opt/oracle7/product/8.1.7/lib

Hi.
Why do I receive the following error message when execute startWeblogic.sh
The WebLogic Server did not start up properly.
Exception raised:
java.lang.UnsatisfiedLinkError: getEGroup0
at weblogic.platform.Unix.getEGroup0(Native Method)
at weblogic.platform.Unix.getEffectiveGroup(Unix.java:96)
at weblogic.t3.srvr.T3Srvr.switchEffectiveGroup(T3Srvr.java:1364)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:375)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:212)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
I use Solaris 7 with Weblogic 6.1 SP4 and environments :
LD_LIBRARY_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib:/opt/oracle7/product/8
..1.7/lib:/opt/bea/wlserver6.1/lib/solaris:/opt/bea/wlserver6.1/lib/solaris/o
ci817_8:/opt/oracle7/product/8.1.7/lib

Exception thread in "main" java.lang :NoClassDefError Found:

HI all
i am using jdk1.2 version java . when ever i am programming the programs compiled successfully without any errors, but when execute to run or view the output the errors show likr this "Exception thread in main java.lang:No Class Def errror found ...
i hope i will get solution soon ...
thaks
vasi

I am getting this error right after Java auto updated my machine on 7/30/08. I didn't have any problems before. Now I can't run any java applications. No change made to the config of my machine nor the java codes. I uninstall and reinstall jdk. Same error since yeterday. Any ideas? It is not about the classpath for sure. I am running the app at the directory where the class files are. I was able to run java programs before.
Thanks. Sue

WebLogic Test Client, throws java.lang.NoSuchMethodException

In weblogic server 10.3, the WebLogic Test Client, throws java.lang.NoSuchMethodException for “any” soap fault message from the web service.
In Detail:
Our web services uses JAX-WS spec and are deployed in WebLogic server 10.3.The web service ear file is generated using standard ant utility. We are using “WebLogic Test Client” available through WebLogic server administration console .The issue is, for “any” soap fault message from the web service, the test client generates “java.lang.NoSuchMethodException:” . The key point is we are creating this class. We are not using our own client. WebLogic Test Client 's service response section has the following stack trace.
S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Server</faultcode>
<faultstring>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</faultstring>
<detail>
<ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="com.sun.xml.ws.encoding.soap.SerializationException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
<ns2:stackTrace>
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="328" method="createDetailFromUserDefinedException" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
<ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
<ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
<ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
<ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
<ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
</ns2:stackTrace>
<ns2:cause class="java.lang.NoSuchMethodException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
<message>our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
<ns2:stackTrace>
<ns2:frame class="java.lang.Class" file="Class.java" line="1605" method="getMethod" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="323" method="createDetailFromUserDefinedException" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
<ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
<ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
<ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
<ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
<ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
<ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
<ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
<ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
<ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
<ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
<ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
<ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
<ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
<ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
<ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
</ns2:stackTrace>
</ns2:cause>
</ns2:exception>
</detail>
</S:Fault>
</S:Body>
</S:Envelope>

Thanks for your assistance. Here is the log from weblogic. You may find "xxx" and "yyy" terms. these are given to our specific project oriented names. If you need any further info please let me know. Again a brief about the issue. when the service returns a fault soap message, the server trying to set the error code in a class generated by it's own where the method is not avilable. this happens for all fault soap message. In case of right response from the service no issues. all are working fine.
Note: Max 3000 characters are allowed to post. so truncating initial stack trace.
Thanks, ganesh.
<xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2e0bd8e
Bound datums[Lxxx.sql.STRUCT;@1b2d059
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1aa0f36
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@191d9ba
Bound datums[Lxxx.sql.STRUCT;@1dc70ec
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1def11c
xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2683f76
Bound datums[Lxxx.sql.STRUCT;@197400e
Caused by: our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy188.findxxxxxx(Unknown Source)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
... 30 more
Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
... 56 more
Nov 21, 2008 9:38:27 AM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
INFO: Service Provider API did not return any object back.
our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
at $Proxy188.findxxxxxx(Unknown Source)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.xxxlect.Method.invoke(Method.java:597)
at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:71)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
... 56 more
com.sun.xml.ws.encoding.soap.SerializationException: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:328)
at com.sun.xml.ws.fault.SOAPFaultBuilder.getFaultDetail(SOAPFaultBuilder.java:306)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:170)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:265)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
at java.lang.Class.getMethod(Class.java:1605)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:323)
... 30 more

JDBCDataSourceRuntime Information for Weblogic 10.3 using Java program

Hello All,
I am trying to get the JDBC datasource connection pool status in Weblogic 10.3 using java program - if it is in RUNNING state or Shutdown state.
Can someone provide me with the same java program for achieving this.
- - Tarun

Refer to this Doc ......... It may help you.
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13728.pdf

Weblogic Server hanging at high load!!!!!!!!!!!

Folks,
We have a weblogic server 9.2 which is running fine but after quiet a while at high load we observe that the server goes down and following exception is displayed in the server logs:
####<Nov 13, 2009 2:42:48 AM EST> <Error> <WebLogicServer> <ibmrxcptpnp-wb1> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1258098168215> <BEA-000337> <[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "617" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@1cec1cec", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
     java.net.SocketOutputStream.socketWrite0(Native Method)
     java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:105)
     java.net.SocketOutputStream.write(SocketOutputStream.java:149)
     oracle.net.ns.DataPacket.send(Unknown Source)
     oracle.net.ns.NetOutputStream.flush(Unknown Source)
     oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
     oracle.net.ns.NetInputStream.read(Unknown Source)
     oracle.net.ns.NetInputStream.read(Unknown Source)
     oracle.net.ns.NetInputStream.read(Unknown Source)
     oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1099)
     oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
     oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
     oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
     oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
     oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1060)
     oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839)
     oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1132)
     oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316)
     oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3422)
     weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:718)
     weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:460)
     weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1455)
     weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1372)
     weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1362)
     weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1767)
     weblogic.common.resourcepool.ResourcePoolImpl.access$700(ResourcePoolImpl.java:37)
     weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:1935)
     weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
     weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
Any answers?????

Hi,
I have a similar issue on ODSI 10gR3 (WLS 10.3). I am having stuck threads - but, in my case it is clear that the database is down (not at the startup)
Here is some more info:
1. Test Connections On Reserve - Enabled
2. Default values for other parameters
Using Oracle thin driver for the connection pool "MyPool" -
./wlserver_10.3/server/lib/ojdbc6.jar
My question is:
1. How do I avoid the stuck thread caused when the database is down? During peak load, the stuck threads are causing some service requests to fail.
I did my homework and the closest option I could find is set the statementTimeout (which is set currently to the default value of -1 i.e. never timeout). Oracle documentation (http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/111070_readme.html) says that the ojdbc6.jar supports setQueryTimeout() method.
Is there any better way to attack this problem?
<Dec 21, 2009 12:11:18 AM EST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "MyPool" failed with exception: "java.sql.SQLRecoverableException: Io exception: Read failed: Connection timed out".>
<Dec 21, 2009 12:14:27 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:18:38 AM EST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "600" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@297ac2b", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-52 "[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, waiting, priority=1, DAEMON> {
-- Waiting for notification on: javax.management.remote.rmi.RMIConnector$RMINotifClient@271498f[fat lock]
java.lang.Object.wait(Object.java:485)
com.sun.jmx.remote.internal.ClientNotifForwarder.postReconnection(ClientNotifForwarder.java:304)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.reconnectNotificationListeners(RMIConnector.java:1488)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.doStart(RMIConnector.java:1568)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin.restart(ClientCommunicatorAdmin.java:72)
com.sun.jmx.remote.internal.ClientCommunicatorAdmin.gotIOException(ClientCommunicatorAdmin.java:34)
javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.gotIOException(RMIConnector.java:1420)
javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:857)
weblogic.management.mbeanservers.domainruntime.internal.ManagedMBeanServerConnection.getAttribute(ManagedMBeanServerConnection.java:288)
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:235)
weblogic.management.jmx.MBeanServerInvocationHandler.doInvoke(MBeanServerInvocationHandler.java:477)
weblogic.management.jmx.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:294)
$Proxy69.getServerRuntime(Unknown Source)
weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.lookupServerRuntime(DomainRuntimeServiceMBeanImpl.java:242)
sun.reflect.GeneratedMethodAccessor1880.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:575)
weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:355)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:831)
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:255)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:441)
weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:55)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:441)
weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:437)
weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:576)
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:350)
weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:570)
weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:305)
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1378)
javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1338)
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:761)
javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:136)
weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:211)
javax.management.remote.rmi.RMIConnectionImpl_1030_WLStub.invoke(Unknown Source)
javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:969)
com.bea.diagnostics.server.MBeanServerUtil.processRecordsFromArchive(MBeanServerUtil.java:177)
com.bea.diagnostics.server.MetricEarliestTimestampLocator$RecordProcessorDesc.identifyEarliestTimestamps(MetricEarliestTimestampLocator.java:261)
com.bea.diagnostics.server.MetricEarliestTimestampLocator.identifyEarliestTimestamps(MetricEarliestTimestampLocator.java:84)
com.bea.diagnostics.server.MetricEarliestTimestampLocator.timerExpired(MetricEarliestTimestampLocator.java:79)
weblogic.timers.internal.TimerImpl.run(TimerImpl.java:253)
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:198)
weblogic.work.ExecuteThread.run(ExecuteThread.java:165)
<Dec 21, 2009 12:24:04 AM EST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "MyPool" failed with exception: "java.sql.SQLRecoverableException: Io exception: Connection reset".>
<Dec 21, 2009 12:24:04 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:24:04 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:24:05 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:24:07 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:24:12 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:24:17 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>
<Dec 21, 2009 12:24:22 AM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "MyPool": Io exception: The Network Adapter could not establish the connection>

Weblogic Thread hogging at java.io.WinNTFileSystem.getBooleanAttributes at high loads

Similar Messages

Maybe you are looking for