Weblogic 12.1.1 Java-level deadlock

Hi!
Recently i accidentally saw that my wl server stop responding. Here is the short thread dump. If somebody need the full one - mail me please.
[email protected]
java version "1.6.0_34"
Java HotSpot(TM) 64-Bit Server VM (build 20.9-b04, mixed mode)
WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491
Found one Java-level deadlock:
=============================
"[ACTIVE] ExecuteThread: '34' for queue: 'weblogic.kernel.Default (self-tuning)'":
  waiting to lock monitor 0x00007f8224170830 (object 0x0000000505a28f48, a weblogic.work.CalendarQueue),
  which is held by "[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'"
"[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'":
  waiting to lock monitor 0x00007f816c0052b8 (object 0x0000000507bad3b0, a weblogic.diagnostics.watch.WatchLogAppender),
  which is held by "[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'"
"[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'":
  waiting to lock monitor 0x00007f8224170830 (object 0x0000000505a28f48, a weblogic.work.CalendarQueue),
  which is held by "[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'"
Java stack information for the threads listed above:
===================================================
"[ACTIVE] ExecuteThread: '34' for queue: 'weblogic.kernel.Default (self-tuning)'":
at weblogic.work.RequestManager.executeWorkFromPriorityQueue(RequestManager.java:628)
- waiting to lock <0x0000000505a28f48> (a weblogic.work.CalendarQueue)
at weblogic.work.RequestManager.registerIdle(RequestManager.java:458)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:224)
"[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'":
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:201)
- waiting to lock <0x0000000507bad3b0> (a weblogic.diagnostics.watch.WatchLogAppender)
at weblogic.logging.log4j.WLLog4jLogger.callAppenders(WLLog4jLogger.java:46)
at weblogic.logging.log4j.JDKLog4jAdapter.log(JDKLog4jAdapter.java:218)
at weblogic.work.WorkManagerLogger.logMaxThreadsConstraintReached(WorkManagerLogger.java:1011)
at weblogic.work.MaxThreadsConstraint.logConstraintReached(MaxThreadsConstraint.java:146)
at weblogic.work.MaxThreadsConstraint.access$000(MaxThreadsConstraint.java:20)
at weblogic.work.MaxThreadsConstraint$1.unbox(MaxThreadsConstraint.java:44)
at weblogic.work.MaxThreadsConstraint$1.unbox(MaxThreadsConstraint.java:22)
at weblogic.work.CalendarQueue.pop(CalendarQueue.java:200)
- locked <0x0000000505a28f48> (a weblogic.work.CalendarQueue)
at weblogic.work.RequestManager.executeWorkFromPriorityQueue(RequestManager.java:629)
- locked <0x0000000505a28f48> (a weblogic.work.CalendarQueue)
at weblogic.work.RequestManager.registerIdle(RequestManager.java:458)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:224)
"[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'":
at weblogic.work.RequestManager.executeWorkFromPriorityQueue(RequestManager.java:629)
- waiting to lock <0x0000000505a28f48> (a weblogic.work.CalendarQueue)
at weblogic.work.RequestManager.addToCalendarQueue(RequestManager.java:318)
at weblogic.work.RequestManager.addToPriorityQueue(RequestManager.java:301)
at weblogic.work.RequestManager.addToMinAndPriorityQueue(RequestManager.java:340)
at weblogic.work.RequestManager.executeIt(RequestManager.java:235)
at weblogic.work.SelfTuningWorkManagerImpl.scheduleInternal(SelfTuningWorkManagerImpl.java:164)
at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:144)
at weblogic.diagnostics.watch.WatchManager.evaluateLogEventRules(WatchManager.java:489)
at weblogic.diagnostics.watch.WatchLogAppender.append(WatchLogAppender.java:51)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
- locked <0x0000000507bad3b0> (a weblogic.diagnostics.watch.WatchLogAppender)
at weblogic.logging.log4j.WLLog4jLogger.callAppenders(WLLog4jLogger.java:46)
at weblogic.logging.log4j.JDKLog4jAdapter.log(JDKLog4jAdapter.java:218)
at weblogic.transaction.internal.TXLogger.logResourceNotAssignedForCommitRetry(TXLogger.java:2550)
at weblogic.transaction.internal.ServerTransactionImpl.allResourcesAssigned(ServerTransactionImpl.java:2559)
at weblogic.transaction.internal.ServerTransactionImpl.assignNonLocalResourcesToOtherSCs(ServerTransactionImpl.java:2542)
at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2740)
at weblogic.transaction.internal.ServerTransactionImpl.access$200(ServerTransactionImpl.java:65)
at weblogic.transaction.internal.ServerTransactionImpl$2.run(ServerTransactionImpl.java:3433)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Found 1 deadlock.
Obviously there is some problem in wllog4j.jar and for our application it is not critical (but nice) at all. Maybe this information will be useful for upgoung support.
File system have free disk space, i checked.
Thanks.

It is EAR with separate WAR. But in stack trace there are no our classes at all.
Yes - we have an limitation for 100 threads per server within domain. But basically this server is used for testing, and only one user is working on it.
It is absolutely impossible for one user to reach 100 threads for sure.

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 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

  • 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 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

  • Putting attribute value from java level into sessionScope variable?

    Hallo,
    is it possible to put an attribute value from java level into a sessionScope variable?
    For example when i'am in prepareSession is it possible to fill a sessionScope variable which i can use in a jspx-Site? And when how i must do it?
    Any help is appreciated.

    At the java level i make this
    private void setUserIdIntoUserDataHashtable() {
    Integer userid = getUserIdForLoggedInUser();
    Integer groupid = getGroupIdForLoggedInUser();
    Hashtable userdata = getDBTransaction().getSession().getUserData();
    if (userdata == null){
    userdata = new Hashtable();
    userdata.put(PBConstants.CURRENT_USER_ID, userid);
    userdata.put(PBConstants.CURRENT_GROUP_ID, groupid);
    And when i at the java level i can use the constants. But i don't have an interaction at this point. Thats why i don't now how to bring the values to a sessionScope variable i need later in a / some sites?

  • 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 4.5.1 easy to deadlock

    I have downloaded and begun to evaluate WL.
    I must not understand some configuration settings because I have found
    it easy to deadlock the server.
    I have set weblogic.system.executeThreadCount=30
    I have a benchmark.jsp file where the java code in the jsp page creates
    on t3 connection to the local host and makes use of that t3 connection
    to open a jdbc connection from a weblogic jdbc connection pool that I
    set up.
    I have a test http client that can simulataneously open N connections to
    an http server and fetch pages. The number of N connections is
    configurable.
    I have found that as the number of connections opened in parallel
    approaches 30 (executeThreadCount value), WL seems to deadlock. My
    guess is that 30 execute threads are allocated to http/jsp requests,
    each of these 30 threads is now locked waiting for a t3 connection,
    which will never happen because the execute thread pool is empty. All
    of the executeThreads are blocked waiting for a t3 connection that
    requires an executeThread of its own.
    Does my analysis make sense? Is it possible to change some
    weblogic.properties to avoid this scenario? I don't think that simply
    increasing executeThread count is the answer since it only changes the
    threshold. I don't want a threshold at which my system just stops
    responding.
    I thought that perhaps using a different webserver would alleviate the
    problem of wasting the executeThread pool on http connections. But then
    I thought that there would be a connection for each servlet engine
    connection so the problem is no different.
    Thanks,
    Kevin

    Joseph,
    You were exactly right. Problem solved.
    Thanks,
    Kevin
    Joseph Weinstein wrote:
    >
    Hi Kevin. The docs are being fixed up to remove T3 connecting from the
    forefront. This was from when most clients were external JVMs. You should
    never make a JDBC-T3 connection from a serverside class. That makes
    a socket connection out of, and back into the server, just to get to the pool,
    and if the latter has to call a DriverManager call, you will deadlock because
    DriverManager calls like getCOnnection or even println() are class synchronized.
    Look to the documentation for the pool driver for accessing pool connections
    from serverside classes such as servlets.
    Joe
    Kevin McEntee wrote:
    I have downloaded and begun to evaluate WL.
    I must not understand some configuration settings because I have found
    it easy to deadlock the server.
    I have set weblogic.system.executeThreadCount=30
    I have a benchmark.jsp file where the java code in the jsp page creates
    on t3 connection to the local host and makes use of that t3 connection
    to open a jdbc connection from a weblogic jdbc connection pool that I
    set up.
    I have a test http client that can simulataneously open N connections to
    an http server and fetch pages. The number of N connections is
    configurable.
    I have found that as the number of connections opened in parallel
    approaches 30 (executeThreadCount value), WL seems to deadlock. My
    guess is that 30 execute threads are allocated to http/jsp requests,
    each of these 30 threads is now locked waiting for a t3 connection,
    which will never happen because the execute thread pool is empty. All
    of the executeThreads are blocked waiting for a t3 connection that
    requires an executeThread of its own.
    Does my analysis make sense? Is it possible to change some
    weblogic.properties to avoid this scenario? I don't think that simply
    increasing executeThread count is the answer since it only changes the
    threshold. I don't want a threshold at which my system just stops
    responding.
    I thought that perhaps using a different webserver would alleviate the
    problem of wasting the executeThread pool on http connections. But then
    I thought that there would be a connection for each servlet engine
    connection so the problem is no different.
    Thanks,
    Kevin--
    PS: Folks: BEA WebLogic is in S.F., and now has some entry-level positions for
    people who want to work with Java and E-Commerce infrastructure products. Send
    resumes to [email protected]
    The Weblogic Application Server from BEA
    JavaWorld Editor's Choice Award: Best Web Application Server
    Java Developer's Journal Editor's Choice Award: Best Web Application Server
    Crossroads A-List Award: Rapid Application Development Tools for Java
    Intelligent Enterprise RealWare: Best Application Using a Component Architecture
    http://weblogic.beasys.com/press/awards/index.htm

  • Weblogic server start error: java.lang.OutOfMemoryError

    Hi:
              when i start weblogic server, i met following error !
              java.lang.OutOfMemoryError
              <<no stack trace available>>
              why?
              thanks!
              starting output as follow :
              C:\bea7\user_projects\zhudomain>startweblogic
              C:\bea7\user_projects\zhudomain>echo off
              CLASSPATH=C:\bea7\jdk131_03\lib\tools.jar;C:\bea7\weblogic700\integration\li
              b\wl
              pi-worklist.jar;C:\bea7\weblogic700\samples\server\eval\pointbase\lib\pbserv
              er42
              ECF172.jar;C:\bea7\weblogic700\server\lib\weblogic_sp.jar;C:\bea7\weblogic70
              0\se
              rver\lib\weblogic.jar;
              PATH=.;C:\bea7\weblogic700\server\bin;C:\bea7\jdk131_03\bin;C:\PROGRA~1\RATI
              ONAL
              \RATION~1\NUTCROOT\bin;C:\PROGRA~1\RATIONAL\RATION~1\NUTCROOT\bin\x11;C:\PRO
              GRA~
              1\RATIONAL\RATION~1\NUTCROOT\mksnt;c:\Oracle\Ora81\bin;C:\WINNT\system32;C:\
              WINN
              T;C:\WINNT\System32\Wbem;C:\PROGRA~1\ULTRAE~1;C:\CTEX\MiKTeX\TeXMF\miktex\bi
              n;C:
              \CTEX\MiKTeX\LocalT~1\cct\bin;C:\Program Files\Rational\common;C:\Program
              Files\
              Rational\ClearQuest;C:\Program Files\Rational\Rose\TopLink\;C:\Program
              Files\Rat
              ional\Rational Test;C:\bea7\jdk131_03\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 *
              C:\bea7\user_projects\zhudomain>"C:\bea7\jdk131_03\bin\java" -hotspot -Xms32
              m -X
              mx200m -Dweblogic.security.SSL.trustedCAKeyStore=C:\bea7\weblogic700\server\
              lib\
              cacerts -Dweblogic.Name=myserver -Dbea.home="C:\bea7" -Dweblogic.management.
              user
              name= -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled= -Dja
              va.s
              ecurity.policy="C:\bea7\weblogic700\server\lib\weblogic.policy"
              weblogic.Server
              <2002-11-13 ÏÂÎç04ʱ21·Ö01Ãë> <Info> <Security> <090065> <Getting boot
              identity
              from user.>
              Enter username to boot WebLogic server:system
              Enter password to boot WebLogic server:
              Starting WebLogic Server...
              <2002-11-13 ÏÂÎç04ʱ21·Ö08Ãë> <Notice> <Management> <140005> <Loading
              configurat
              ion C:\bea7\user_projects\zhudomain\.\config.xml>
              java.lang.OutOfMemoryError
              <<no stack trace available>>
              

    Hi JLK,
    Now as you can see that you are getting "java.lang.OutOfMemoryError: PermGen space" during the activation on an application it means that you are application needs more space in the non-heap part of the JVM which is PermGen to create the Classes, Class Structures, Methods and Reflection Objects of this applications hence you are getting this issue.
    Now how to solve this issue you try the following check list which would help you resolve this issue and overcome same type of issue in future
    1). Make Sure that the PermGen Area is not set to a very less value.
    2). Usually if an Application has Many JSP Pages in that case every JSP will be converted to a *.class file before JSP Request Process. So a large number of JSPs causes generation of a Large number of *.class files all these classes gets loaded in the PermGen area.
    3). While allocating the -XX:MaxPermSize make sure that you follow a rough Formula… which works in most of the Application Servers.
    MaxPermSize = (Xmx/3) —- Very Special Cases (One Third of maximum Heap Size)
    MaxPermSize = (Xmx/4) —- Recommended (One Fourth Of maximum Heap Size
    To get more information on this I would suggest you to have look at the below link which would surely help you in this case
    Topic: OutOfMemory Causes and First Aid Steps?
    http://middlewaremagic.com/weblogic/?p=4464
    Regards,
    Ravish Mody

  • Use DataSource of weblogic in a standalone Java file

    Hi,
    We have a requirement to run a java file at a scheduled time in a day using cron scheduler on our linux server.
    We need to fetch data from the database & perform some business logic in this standalone JAVA file.
    Our application has an EAR which is deployed on Weblogic 10.3 server & in our application, we are utilizing the datasource created in that domain using Hibernate.
    Now, can we create a standealone Java file & use exisitng datasource (without Hibernate) instead of legacy JDBC code to connect to DB.
    Also, do we need to keep this JAVA file a part of this EAR, WAR or can we put the class file in anylocation outside this EAR & then utilize datasource feature.
    Please help on the same in implementation.
    Thanks,
    Uttam

    Hi Ravi,
    I did create Datasource domain & put wlclient.jar in my application classpath (Add jar in Java Build path of application), but, when I ran application, its giving below error
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/kernel/KernelStatus
         at weblogic.jndi.Environment.<clinit>(Environment.java:78)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:198)
         at TestDataSource.main(TestDataSource.java:37)
    Also, I'm putting code here as I there is no provision to attach the file here. Please let me know whats wrong here.
    Also, I've given the name of datasource as testDataSource through Admin console of the domain. Do we need to prefix the name with jdbc/ in the code or without that also it works?
    import java.sql.Connection;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import java.sql.Statement;
    import java.util.Hashtable;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import javax.sql.DataSource;
    public class TestDataSource {
         public static void main(String[] args)
              DataSource ds=null;
              Connection conn=null;
              Statement stmt=null;
              ResultSet rs=null;
              Context ctx=null;
              try
                   Hashtable ht = new Hashtable();
                   ht.put(Context.INITIAL_CONTEXT_FACTORY,
                   "weblogic.jndi.WLInitialContextFactory");
                   ht.put(Context.PROVIDER_URL,
                   "t3://172.19.244.180:7001");
                   System.out.println("HERE");
                   ctx=new InitialContext(ht);
                   ds=(DataSource)ctx.lookup("jdbc/testDataSource");
                   System.out.println("HERE AFER CONTEXT CREATION");
                   conn=ds.getConnection();
                   stmt=conn.createStatement();
                   rs=stmt.executeQuery("select distinct(circle) from AIRCEL_STORE_FINDER order by 1 ");
                   while (rs.next())
                        System.out.println("circle name "+rs.getString(1));
              }catch (Exception e) {
                   System.out.println("Error in Main "+e.toString());
                   e.printStackTrace();
              finally{
                   try{
                   if(rs!=null)
                        rs.close();
                   if(stmt!=null)
                        stmt.close();
                   if(conn!=null)
                        conn.close();
                   if(ds!=null)
                        ds=null;
                   if(ctx!=null)
                        ctx.close();
                   }catch (SQLException e) {
                        System.out.println("Error in SQLException Finally "+e.toString());
                   catch (NamingException e) {
                        System.out.println("Error in NamingException Finally "+e.toString());
    }

  • Weblogic 10 - SEVERE: null java.lang.NullPointerException

    I'm facing this Error while invoking a webservice
    SEVERE: null
    java.lang.NullPointerException
    at com.bea.staxb.buildtime.internal.bts.XmlTypeName.findTypeIn(XmlTypeName.java:555)
    at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.getTypeNamed(AnonymousTypeFinder.java:73)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createBindingTypeFrom(Deploytime109MappingHelper.java:1088)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:519)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:266)
    at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:166)
    at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
    at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:709)
    at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:409)
    at weblogic.wsee.ws.WsFactory.createClientService(WsFactory.java:45)
    at weblogic.wsee.jaxrpc.ServiceImpl.init(ServiceImpl.java:154)
    at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:122)
    at com.samba.service.client.GosiPaymentSambaServices_Impl.<init>(Unknown Source)
    at com.samba.service.client.GosiPaymentSambaServices_Impl.<init>(Unknown Source)
    can Any body Help me through this?

    Hi,
    Resource adapter is not available remotely - with your JNDI context
    ctx.lookup("tangosol.coherenceTx");will return null. Instead of using resource adapter remotely you can implement a session bean, deploy it on a WLS instance and invoke it remotely.
    Regards,
    Dimitri

  • Scheduling in weblogic 7.0 using java API

    Hi,
    There is a java class that needs to be executed each day at a specified time through
    weblogic 7.0 app server. In weblogic 6.1, the weblogic timer classes were deprecated.
    Weblogic 7.0 suggests using 3rd party J2EE scheduling tools like FLUX and Kronos
    Enterprise Scheduler. However, are there some other weblogic java APIs available
    in weblogic 7.0 through which scheduling can be achieved?
    TIA,
    abhishek.

    you might also consider using java.util.Timer. See
    http://java.sun.com/j2se/1.3/docs/api/java/util/Timer.html
    Regards,
    Michael
    "abhishek" <[email protected]> wrote in message
    news:[email protected]..
    >
    Hi,
    There is a java class that needs to be executed each day at a specifiedtime through
    weblogic 7.0 app server. In weblogic 6.1, the weblogic timer classes weredeprecated.
    Weblogic 7.0 suggests using 3rd party J2EE scheduling tools like FLUX andKronos
    Enterprise Scheduler. However, are there some other weblogic java APIsavailable
    in weblogic 7.0 through which scheduling can be achieved?
    TIA,
    abhishek.

  • Weblogic 10 support for java 1.4

    Hi,
    My application is currently running on weblogic 8.1 sp3. We are upgrading to weblogic 10 on Solaris 10.
    Can I run weblogic 10 on java 1.4 in Solaris 10.
    This may not sound logical, but I need answers.
    Thanks in advance,
    Rama

    Rama,
    You also need to consider the End of Life policy for JDK 1.4, unless you have a "Business Release" you will run out of support in October 2008. My understanding is BEA/Oracle will continue to support WL8 but only as far as they can. Have a look at http://java.sun.com/products/archive/eol.policy.html for more details.
    Regards, Geoff

  • Weblogic 8.1 & Sun Java Studio Creator

    I'm in a new position where I need to deploy web apps created in Sun's Java Studio Creator to Weblogic 8.1, that hits an Oracle 8i back end.
    I'm curious to see if anyone on this board is using a similar mix of technologies. If so, what drivers are you using in your Studio Creator data sources?
    Thanks!

    Check it out. You will see, there is a problem.
    Error message from Sun Java Studio Creator:
    Start file:///C:\Documents and Settings\computer user\.Creator\EA\websvc\TFormat.wsdl 06/25/2004 12:23:22:�Parsing WSDL. Please wait ..WSDL - file:/C:/Documents and Settings/computer user/.Creator/EA/websvc/TFormat.wsdl 06/25/2004 12:23:49:�Error Parsing WSDL. Please see the log file for details. Exception = modeler error: failed to parse document at "file:/C:/Documents and Settings/computer user/.Creator/EA/websvc/TFormat.wsdl": org.xml.sax.SAXParseException: Content is not allowed in prolog.
    }}

Maybe you are looking for

  • I am done editing in Develop; how do I save edited images for web?

    I get the import and development options in Lightroom but I was told by a LR representative when I called for assistance that LR does not retain any data.  So, if I import photos from my camera (NEF files) and edit in Develop; where do I save the edi

  • Sending Map String,String data to an MXBean?

    Hi, I have been trying to figure out how to send a HashMap<String, String> from a JMX client to a remote MBean Server. I have looked into constructing the data using TabularDataSupport but can not figure out the exact syntax. I have attached the stac

  • SI4_TestDrive - SAP didnt start after linux reboot.

    Hello Forum, I installed the preview version (SI4_TestDrive) on Suse 9.1./DB2 The installation went through successful and I could connect to SAP from another system. But when I reboot the linux I couldn't start SAP.When I issue the command "startsap

  • Mail fails to connect to smtp servers after 10.9.3 update

    Wiped hard drive and installed 10.9 plus 10.9.3 combo updater. 90% of my email accounts cannot connect to their smtp servers. Created a new user account and setup Mail with an account with the same result.

  • Sales Activity

    Dear all, I am creating Sales activity by VC01N I am also change the incompletion procedure for Sales Employee mandatory entry as we cannot implement HR module. Is there any affect in the status of sales activity? can i got the all report with refere