Exception only occuring during stress test

We are trying to get ready to release a beta version of the software I'm working on.. so part of getting ready for that was to try set up some stress tests and hit the server with multiple requests for the same page....
Not sure exactly how many it is taking but we are getting the following exception.
2005-06-10 13:20:23 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception
java.lang.NumberFormatException: For input string: "200044.E2000444E"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
        at java.lang.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1207)
        at java.lang.Double.parseDouble(Double.java:220)
        at java.text.DigitList.getDouble(DigitList.java:127)
        at java.text.DecimalFormat.parse(DecimalFormat.java:1070)
        at java.text.SimpleDateFormat.subParse(SimpleDateFormat.java:1386)
        at java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1156)
        at java.text.DateFormat.parse(DateFormat.java:333)
        at com.xxxxx.xxxxx.struts.adapter.BrowseBaseAdapter.formatYyyyMMddToLocaleStr(BrowseBaseAdapter.java:194)I can only assume that something was not thread safe and somehow something is getting confused....
this is the method that produced the error and the code that it runs.
I know absolutely nothing about making something thread safe.... can anyone give me good link to refer to or point something out in the below code that might be a no no.
private static final SimpleDateFormat xxxxxxxxDateFormat =
          new SimpleDateFormat("yyyyMMdd");
     protected String formatYyyyMMddToLocaleStr(
          String  xxxxxxxxDt,
          Locale locale) {
          String result = "";
          if ( xxxxxxxxDt != null &&  xxxxxxxxDt.length() == 8) {
               try {
                    Date tempDate =  xxxxxxxxDateFormat.parse( xxxxxxxxDt);
                    result = javaDataTypeToString(tempDate, locale);
               } catch (ParseException ex) {
          return result;
public String javaDataTypeToString(Object data, Locale locale) {
          String returnType = data.getClass().getName();
          String result = null;
          if (returnType.equals("java.lang.String")) {
               result = (String) data;
          } else if (returnType.equals("java.lang.Float")) {
               NumberFormat formatter = NumberFormat.getNumberInstance(locale);
               formatter.setMaximumFractionDigits(6);
               formatter.setGroupingUsed(false);
               result = formatter.format((Float) data);
          } else if (returnType.equals("java.lang.Double")
                    || returnType.equals("java.math.BigDecimal")) {
               NumberFormat formatter = NumberFormat.getNumberInstance(locale);
               formatter.setMaximumFractionDigits(13);
               formatter.setGroupingUsed(false);
               StringBuffer buffer = new StringBuffer();
               result = formatter.format(data, buffer, new FieldPosition(0))
                         .toString();
          } else if (returnType.equals("java.lang.Integer")) {
               Integer inte = (Integer) data;
               int intVal = inte.intValue();
               if (intVal != 0)
                    result = String.valueOf(intVal);
               else
                    result = "";
          } else if (returnType.equals("java.util.Date")) {
               java.util.Date date = (java.util.Date) data;
               SimpleDateFormat dateFormatter = getDatePattern(locale);
               result = dateFormatter.format(date);
          } else if (returnType.equals("com.sungard.stnweb.utility.Time")) {
               Time time = (Time) data;
               result = time.asString();
          } else if (returnType.equals("java.lang.Boolean")) {
               Boolean dataBool = (Boolean) data;
               if (dataBool.booleanValue())
                    result = "1";
               else
                    result = "";
          return result;

From the API on java.text.SimpleDateFormat
Synchronization
Date formats are not synchronized. It is recommended to create separate
format instances for each thread. If multiple threads access a format
concurrently, it must be synchronized externally. Being static, your date format object will be accessed by multiple threads.
Solution: Don't make the date format object static.
I would suggest like this:
private static final String dfString  ="yyyyMMdd";
protected String formatYyyyMMddToLocaleStr(String  xxxxxxxxDt, Locale locale) {
  String result = "";
  SimpleDateFormat xxxxxxxxDateFormat = new SimpleDateFormat(dfString );
  if ( xxxxxxxxDt != null &&  xxxxxxxxDt.length() == 8) {
  try {
    Date tempDate =  xxxxxxxxDateFormat.parse( xxxxxxxxDt);
    result = javaDataTypeToString(tempDate, locale);
  catch (ParseException ex) {}
          return result;
Ok, so it is constructing a DateFormatting object for each method call, but I don't see it as that big a deal. Its not a huge hit. You might get away with making it an instance variable - I don't know how you use the enclosing class. Start with this, and see if it works.
Cheers,
evnafets

Similar Messages

  • Toplink problem during stress tests

    Hello
    I have created simple Three tier application, where SLSBs connects using Toplink to Oracle database. During stress tests I'm having very offen following exception:
    Wyj¦tek [TOPLINK-4002] (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)): oracle.toplink.exceptions.DatabaseException
    Opis wyj¦tku: java.sql.SQLException: Wyj?tek we-wy: The Network Adapter could not establish the connection
    Wyj¦tek wewnŕtrzny: java.sql.SQLException: Wyj?tek we-wy: The Network Adapter could not establish the connection
    Error code: 17002
         at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:221)
         at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:105)
         at oracle.toplink.sessions.DatabaseLogin.connect(DatabaseLogin.java:218)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1323)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.incrementCallCount(DatabaseAccessor.java:1198)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:633)
         at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:506)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:131)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelectCall(CallQueryMechanism.java:194)
         at oracle.toplink.internal.queryframework.CallQueryMechanism.selectAllRows(CallQueryMechanism.java:565)
         at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:733)
         at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:708)
         at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:447)
         at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
         at oracle.toplink.queryframework.ReadQuery.execute(ReadQuery.java:125)
         at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
         at oracle.toplink.threetier.ServerSession.internalExecuteQuery(ServerSession.java:629)
         at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:392)
         at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
         at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1038)
         at petstore.ejb.OrderFacadeBean.getUserOrders(OrderFacadeBean.java:190)
         at OrderFacadeLocal_StatelessSessionBeanWrapper8.getUserOrders(OrderFacadeLocal_StatelessSessionBeanWrapper8.java:615)
         at petstore.wmodule.OrderFacadeBusinessDelegate.getUserOrders(OrderFacadeBusinessDelegate.java:50)
         at petstore.wmodule.struts.OrderListAction.execute(OrderListAction.java:57)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
         at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
         at petstore.wmodule.servlet.EncodingFilter.doFilter(EncodingFilter.java:32)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:16)
         at petstore.wmodule.servlet.SecurityFilter.doFilter(SecurityFilter.java:43)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:600)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.sql.SQLException: Wyj?tek we-wy: The Network Adapter could not establish the connection
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:345)
         at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:431)
         at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:515)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:345)
         at com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:116)
         at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:102)
         ... 40 more
    Toplink session is configured to use external transaction controller and data source. Application run on OC4J 9.0.4.1. Using jdbc debug options I wasn't able to find any causes. Has anyone faced this problem before?
    Regards
    Jarek

    Hi Jarek,
    TopLink uses the datasource similar to any other java application would, so there are no additional restrictions. From the error, you can see that the datasource is attempting to create a new connection and that is what is causing the exception. All TopLink did was call getConnection on the datasource ( DriverManagerDataSource.getConnection ).
    This could be a problem/glitch with the network or that the listener when down temporarily. Things to check would be:
    -how frequently this occurs
    -if it occurs for all connections after this point
    -the state of the database listener (can other applications connect to it, is it up, etc)
    -how many connections to the DB are active at this point
    -how many connections/sessions are active from this application
    -the OC4J and JDBC versions. Latest patches are better with regards to connection pools.
    What is strange though is that you have the min=max, so it should never create new connections after the first time the pool is accessed. Each connection should already have been created, which is why I suggest that you contact OC4J/JDBC support.
    Best Regards,
    Chris

  • Exception has occurred during data insertion ... Wrong number of parameters

    I am using an ADO dataflow source and an ADO dataflow destination to move data from a table on an IBM iSeries DB2 database to another IBM iSeries DB2 database on another machine.  The connection managers for source and destination both use .Net Providers\Odbc
    Data Provider with the Data Source Specification being ODBC connections specified on the Windows Server 2008 r2 machine hosting bids.  All the test connections work...so far so good.
    Issue is when I execute the control flow task the rows get picked up from the source DB2 database no problem but it fails on the insert to the destination DB2 table...The progress tab specifies the exceptions...
    [ADO NET Destination [601]] Error: An exception has occurred during data insertion, the message returned from the provider is: ERROR [07002] [IBM][System i Access ODBC Driver]Wrong number of parameters.
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "ADO NET Destination" (601) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (604). The identified
    component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.  There may be error messages posted before this with more information about the
    failure.
    I put a data viewer on the data flow connection and the records I expect are  getting picked up and look ok. I checked to make sure the source and destination tables have the same number of columns in their record layout and identical data
    types and they look fine.
    Could someone kindly tell me whats going wrong?  Does the error message indicate that some of the columns are getting dropped from the dataset before the insert?
    Thanks much in advance for any help, Roscoe

    Hi Roscoe,
    Glad to hear that you have found the root cause. So, the issue occurs because numeric values with no decimal cannot be inserted into the Decimal data type column in the DB2 table. In SSIS, data type Decimal of DB2 database is mapped to data type DT_NUMERIC.
    To address the issue, you can do a data conversion for the column in question to define its precision and scale such as DT_NUMERIC(9,2) by using the Data Conversion Transformation before the ADO NET Destination.
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • Error "A web exception has occurred during file upload" when trying to import ESXi image file into Update Manager

    I'm encountering this error and not sure how to fix, I'm quite new to vCenter so please bear with me.
    I'm trying out vCenter 5.1 with Update Manager 5.1 right now.  No license key has been entered and I still have 50 odd days to try it out.
    2 ESXi hosts are being managed by this vCenter, and they're both running ESXi 4.0
    I'm looking to use Update Manager to try to upgrade the ESXi 4.0 hosts to ESXi 5.1
    I downloaded the image file VMware-VIMSetup-all-5.1.0-799735.iso from VMWare website, and is looking to import it using the Update Manager so I can update the ESXi hosts, but I keep on getting the error:
    File name:     VMware-VIMSetup-all-5.1.0-799735.iso
    Failed to transfer data
    Error was: A web exception has occurred during file upload
    I tried importing it by using vSphere client to connect to vCenter server both remotely and locally, with firewall disabled.
    I've read http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026602
    I've disabled firewall, and there is no anti-virus program on the server.  I've also restarted the machine several times, to no avail, I didn't reinstall update manager because the whole Windows and VCenter installations are clean from scratch.
    I logged into the vSphere Client using Active Directory credentials, and I've made all Domain Admins (which my account is a member of) part of the administrator group on the vCenter server. I can't log in using admin@System-Domain because it tells me I don't have permissions for it, I still haven't really had the chance to figure out why that is and not sure if that makes a difference.
    Also, I'm fairly certain I'm using the right image file, as I've burned some DVD's used that image file to upgrade some other ESXi hosts.  Unless there's a special image file I need to download?
    I'm at lost on what I can do to make it work.  Please advise.
    Thanks.

    The ISO file you mentioned is the one for vCenter Server. What you need is the "VMware-VMvisor-Installer-5.1.0-799733.x86_64.iso" (or VMware-VMvisor-Installer-201210001-838463.x86_64.iso) for the ESXi host.
    André

  • Weblogic server hangs during stress-testing -- possibly EJB deadlocks

    Hi
    While running stress tests on our application, our WLS 4.5.1 hangs even at a
    mere load of 20 users. We are running on a Solaris machine. Database: Oracle
    8.1.5, running on the same machine. Using oracle.jdbc.driver.OracleDriver as
    the JDBC driver, and using JTS as the transaction manager.
    When we did a thread dump (complete lis at the end of this post) and
    basically we are seeing a bunch of our entity beans in a "locked" state. A
    common pattern we see in the thread dumps is that
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5] com.nps.ers.ejb.organization.<Our Entiy Bean>EOImpl.<a get
    method>(ERSSystemConfigurationBeanEOImpl.java:1539)
    [6] com.nps.ers.ejb.awardnomination.<Our entity bean>.<some method>
    After more thorough studying of EJB transactions, we changed the isolation
    level of all our beans from TRANSACTION_SERIALIZED to
    TRANSACTION_READ_COMMITTED and made sure all our beans say TX_REQUIRED for
    their transactionAttribue. Still, this problem persists.
    The basic scenario we are load testing is that of multiple users logging
    into the system and trying to access a particular user's record, and right
    now, this is causing deadlocks at 20 users.
    What we fail to understand is that --
    (a) even if a method is attempting a read-only access to the data, why would
    it try to obtain a lock? or why would it matter that the data is locked?
    Some of the locks we are seeing are actually on a bean that is used for
    read-only purposes.
    (b) if 2 or more processes are trying to access the same record, based on
    whichever process got their first, shouldn't one succeed, and the other go
    into a 'waiting' state?
    We have also opened this issue with weblogic support, and the response so
    far has been that there "may" be a bug in weblogic 4.5.1 itself that's
    causing it, and they need to look into it further. Other similar posts in
    the newsgroup haven't been resolved either -- hence this general plea for
    help. Please advise if you've any suggestions. Thanks
    Sandeep
    ---------------------------Complete Thread Dump Listing -------------------
    "HighPriority TimeEventGenerator" (TID:0x1488278, sys_thread_t:0x14881b8,
    state:CW, thread_t: t@46, threadID:0xd9271dc8, stack_bottom:0xd9272000,
    stack_size:0x20000) prio=9
    [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:249)
    [2]
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :143)
    [3] java.lang.Thread.run(Thread.java:479)
    "SSLListenThread" (TID:0x1588220, sys_thread_t:0x1588160, state:R, thread_t:
    t@45, threadID:0xd9321dc8, stack_bottom:0xd9322000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
    [4] java.net.ServerSocket.accept(ServerSocket.java:224)
    [5]
    weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
    :121)
    [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
    [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:230)
    "ListenThread" (TID:0x15f7d48, sys_thread_t:0x15f7c88, state:R, thread_t:
    t@44, threadID:0xd92a1dc8, stack_bottom:0xd92a2000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:230)
    "ExecuteThread-29" (TID:0xad1c90, sys_thread_t:0xad1bd0, state:CW, thread_t:
    t@40, threadID:0xd94e1dc8, stack_bottom:0xd94e2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5] com.nps.ers.ejb.user.UserBeanEOImpl.display(UserBeanEOImpl.java:1384)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.updatePointsUsed(AwardNo
    minationBean.java:1530)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.nominate(AwardNomination
    Bean.java:1279)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.nominate(AwardNomi
    nationBeanEOImpl.java:282)
    [9]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.nomina
    te(AwardNominationBeanEOImpl_ServiceStub.java:811)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [13] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [14] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [16] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [17]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [19]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [20]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [21] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [22] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-28" (TID:0xad1a78, sys_thread_t:0xad19b8, state:CW, thread_t:
    t@39, threadID:0xd9511dc8, stack_bottom:0xd9512000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-27" (TID:0xad1678, sys_thread_t:0xad15b8, state:CW, thread_t:
    t@38, threadID:0xd9541dc8, stack_bottom:0xd9542000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-26" (TID:0xac84e8, sys_thread_t:0xac8428, state:CW, thread_t:
    t@37, threadID:0xd9571dc8, stack_bottom:0xd9572000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-25" (TID:0xab7d50, sys_thread_t:0xab7c90, state:CW, thread_t:
    t@36, threadID:0xd95a1dc8, stack_bottom:0xd95a2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-24" (TID:0xab9b60, sys_thread_t:0xab9aa0, state:CW, thread_t:
    t@35, threadID:0xd95d1dc8, stack_bottom:0xd95d2000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-23" (TID:0xab9948, sys_thread_t:0xab9888, state:CW, thread_t:
    t@34, threadID:0xd9601dc8, stack_bottom:0xd9602000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5] com.nps.ers.ejb.user.UserBeanEOImpl.getUserId(UserBeanEOImpl.java:182)
    [6]
    com.nps.ers.ejb.login.LoginSessionBean.getUserStatus(LoginSessionBean.java:1
    61)
    [7]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl.getUserStatus(LoginSessionBeanE
    OImpl.java:212)
    [8]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl_ServiceStub.getUserStatus(Login
    SessionBeanEOImpl_ServiceStub.java:554)
    [9]
    com.nps.ers.servlet.LoginRequest.processLoginRequest(LoginRequest.java:248)
    [10] com.nps.ers.servlet.LoginRequest.getNextPage(LoginRequest.java:90)
    [11] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [12] com.nps.common.servlet.BaseServlet.doGet(BaseServlet.java:124)
    [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [15]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [16]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [18]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [19] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [20] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-22" (TID:0xabcc20, sys_thread_t:0xabcb60, state:CW, thread_t:
    t@33, threadID:0xd9631dc8, stack_bottom:0xd9632000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-21" (TID:0xa9ccf0, sys_thread_t:0xa9cc30, state:CW, thread_t:
    t@32, threadID:0xd9661dc8, stack_bottom:0xd9662000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-20" (TID:0xab2550, sys_thread_t:0xab2490, state:R, thread_t:
    t@31, threadID:0xd9691dc8, stack_bottom:0xd9692000, stack_size:0x20000)
    prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [4] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [5] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-19" (TID:0xa640c0, sys_thread_t:0xa64000, state:CW, thread_t:
    t@30, threadID:0xd96c1dc8, stack_bottom:0xd96c2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5] com.nps.ers.ejb.user.UserBeanEOImpl.display(UserBeanEOImpl.java:1384)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.updatePointsUsed(AwardNo
    minationBean.java:1530)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.nominate(AwardNomination
    Bean.java:1279)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.nominate(AwardNomi
    nationBeanEOImpl.java:282)
    [9]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.nomina
    te(AwardNominationBeanEOImpl_ServiceStub.java:811)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [13] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [14] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [16] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [17]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [19]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [20]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [21] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [22] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-18" (TID:0xa502d8, sys_thread_t:0xa50218, state:CW, thread_t:
    t@29, threadID:0xd96f1dc8, stack_bottom:0xd96f2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getCashWithinD
    ays(ERSSystemConfigurationBeanEOImpl.java:1231)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.getAwardNominationNotifi
    cationStates(AwardNominationBean.java:772)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.getAwardNomination
    NotificationStates(AwardNominationBeanEOImpl.java:247)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.getAwa
    rdNominationNotificationStates(AwardNominationBeanEOImpl_ServiceStub.java:41
    5)
    [9]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [12] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [13] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [16]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [19]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [21] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-17" (TID:0xa242d8, sys_thread_t:0xa24218, state:CW, thread_t:
    t@28, threadID:0xd9721dc8, stack_bottom:0xd9722000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.user.UserBeanEOImpl.getUserStatusCode(UserBeanEOImpl.java:22
    77)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.getApprovers(ApproverS
    electionBean.java:352)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.getApprovers(App
    roverSelectionBeanEOImpl.java:140)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.getA
    pprovers(ApproverSelectionBeanEOImpl_ServiceStub.java:554)
    [9]
    com.nps.ers.servlet.ApproverSelection.getApproverList(ApproverSelection.java
    :81)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-16" (TID:0xaa0ed8, sys_thread_t:0xaa0e18, state:CW, thread_t:
    t@27, threadID:0xd9751dc8, stack_bottom:0xd9752000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-15" (TID:0xad0220, sys_thread_t:0xad0160, state:CW, thread_t:
    t@26, threadID:0xd9781dc8, stack_bottom:0xd9782000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5] com.nps.ers.ejb.user.UserBeanEOImpl.getUserId(UserBeanEOImpl.java:182)
    [6]
    com.nps.ers.ejb.login.LoginSessionBean.getUserStatus(LoginSessionBean.java:1
    61)
    [7]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl.getUserStatus(LoginSessionBeanE
    OImpl.java:212)
    [8]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl_ServiceStub.getUserStatus(Login
    SessionBeanEOImpl_ServiceStub.java:554)
    [9]
    com.nps.ers.servlet.LoginRequest.processLoginRequest(LoginRequest.java:248)
    [10] com.nps.ers.servlet.LoginRequest.getNextPage(LoginRequest.java:90)
    [11] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [12] com.nps.common.servlet.BaseServlet.doGet(BaseServlet.java:124)
    [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [15]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [16]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [18]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [19] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [20] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-14" (TID:0xa8f4c0, sys_thread_t:0xa8f400, state:CW, thread_t:
    t@25, threadID:0xd97b1dc8, stack_bottom:0xd97b2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2] weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4] weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getCashWithinD
    ays(ERSSystemConfigurationBeanEOImpl.java:1231)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.getAwardNominationNotifi
    cationStates(AwardNominationBean.java:772)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.getAwardNomination
    NotificationStates(AwardNominationBeanEOImpl.java:247)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.getAwa
    rdNominationNotificationStates(AwardNominationBeanEOImpl_ServiceStub.java:41
    5)
    [9]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [12] com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [13] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [16]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [19]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [20] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [21] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-13" (TID:0xa194f0, sys_thread_t:0xa19430, state:CW, thread_t:
    t@24, threadID:0xd97e1dc8, stack_bottom:0xd97e2000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2] weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.E

    Can you post details on this instrumentation?
    I know in the past when we ran into this type of problem, it took us a while
    to think through and identify the problems.
    Thanks,
    Gary
    Rob Woollen <[email protected]> wrote in message
    news:[email protected]...
    Generally this indicates a deadlock in the order that you access your
    entity beans. Please follow-up with [email protected]. There is
    some instrumentation that you can turn on to help spot why this is
    occurring.
    -- Rob
    Sandeep Giri wrote:
    Hi
    While running stress tests on our application, our WLS 4.5.1 hangs even
    at a
    mere load of 20 users. We are running on a Solaris machine. Database:Oracle
    8.1.5, running on the same machine. Usingoracle.jdbc.driver.OracleDriver as
    the JDBC driver, and using JTS as the transaction manager.
    When we did a thread dump (complete lis at the end of this post) and
    basically we are seeing a bunch of our entity beans in a "locked" state.A
    common pattern we see in the thread dumps is that
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5] com.nps.ers.ejb.organization.<Our Entiy Bean>EOImpl.<a get
    method>(ERSSystemConfigurationBeanEOImpl.java:1539)
    [6] com.nps.ers.ejb.awardnomination.<Our entity bean>.<some method>
    After more thorough studying of EJB transactions, we changed theisolation
    level of all our beans from TRANSACTION_SERIALIZED to
    TRANSACTION_READ_COMMITTED and made sure all our beans say TX_REQUIREDfor
    their transactionAttribue. Still, this problem persists.
    The basic scenario we are load testing is that of multiple users logging
    into the system and trying to access a particular user's record, andright
    now, this is causing deadlocks at 20 users.
    What we fail to understand is that --
    (a) even if a method is attempting a read-only access to the data, whywould
    it try to obtain a lock? or why would it matter that the data is locked?
    Some of the locks we are seeing are actually on a bean that is used for
    read-only purposes.
    (b) if 2 or more processes are trying to access the same record, basedon
    whichever process got their first, shouldn't one succeed, and the othergo
    into a 'waiting' state?
    We have also opened this issue with weblogic support, and the responseso
    far has been that there "may" be a bug in weblogic 4.5.1 itself that's
    causing it, and they need to look into it further. Other similar postsin
    the newsgroup haven't been resolved either -- hence this general pleafor
    help. Please advise if you've any suggestions. Thanks
    Sandeep
    ---------------------------Complete Thread DumpListing -------------------
    >>
    "HighPriority TimeEventGenerator" (TID:0x1488278,sys_thread_t:0x14881b8,
    state:CW, thread_t: t@46, threadID:0xd9271dc8, stack_bottom:0xd9272000,
    stack_size:0x20000) prio=9
    [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:249)
    [2]
    weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java
    :143)
    [3] java.lang.Thread.run(Thread.java:479)
    "SSLListenThread" (TID:0x1588220, sys_thread_t:0x1588160, state:R,thread_t:
    t@45, threadID:0xd9321dc8, stack_bottom:0xd9322000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
    [4] java.net.ServerSocket.accept(ServerSocket.java:224)
    [5]
    weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java
    :121)
    [6]weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
    [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:230)
    "ListenThread" (TID:0x15f7d48, sys_thread_t:0x15f7c88, state:R,thread_t:
    t@44, threadID:0xd92a1dc8, stack_bottom:0xd92a2000, stack_size:0x20000)
    prio=5
    [1] java.net.PlainSocketImpl.socketAccept(Native Method)
    [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
    [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
    [4] java.net.ServerSocket.accept(ServerSocket.java:223)
    [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:230)
    "ExecuteThread-29" (TID:0xad1c90, sys_thread_t:0xad1bd0, state:CW,thread_t:
    t@40, threadID:0xd94e1dc8, stack_bottom:0xd94e2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]com.nps.ers.ejb.user.UserBeanEOImpl.display(UserBeanEOImpl.java:1384)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.updatePointsUsed(AwardNo
    minationBean.java:1530)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.nominate(AwardNomination
    Bean.java:1279)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.nominate(AwardNomi
    nationBeanEOImpl.java:282)
    [9]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.nomina
    te(AwardNominationBeanEOImpl_ServiceStub.java:811)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [13]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [14] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [16] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [17]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [19]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [20]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [21]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [22] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-28" (TID:0xad1a78, sys_thread_t:0xad19b8, state:CW,thread_t:
    t@39, threadID:0xd9511dc8, stack_bottom:0xd9512000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-27" (TID:0xad1678, sys_thread_t:0xad15b8, state:CW,thread_t:
    t@38, threadID:0xd9541dc8, stack_bottom:0xd9542000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-26" (TID:0xac84e8, sys_thread_t:0xac8428, state:CW,thread_t:
    t@37, threadID:0xd9571dc8, stack_bottom:0xd9572000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2]weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3]weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-25" (TID:0xab7d50, sys_thread_t:0xab7c90, state:CW,thread_t:
    t@36, threadID:0xd95a1dc8, stack_bottom:0xd95a2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-24" (TID:0xab9b60, sys_thread_t:0xab9aa0, state:CW,thread_t:
    t@35, threadID:0xd95d1dc8, stack_bottom:0xd95d2000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2]weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3]weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-23" (TID:0xab9948, sys_thread_t:0xab9888, state:CW,thread_t:
    t@34, threadID:0xd9601dc8, stack_bottom:0xd9602000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]com.nps.ers.ejb.user.UserBeanEOImpl.getUserId(UserBeanEOImpl.java:182)
    [6]
    com.nps.ers.ejb.login.LoginSessionBean.getUserStatus(LoginSessionBean.java:1
    61)
    [7]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl.getUserStatus(LoginSessionBeanE
    OImpl.java:212)
    [8]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl_ServiceStub.getUserStatus(Login
    SessionBeanEOImpl_ServiceStub.java:554)
    [9]
    com.nps.ers.servlet.LoginRequest.processLoginRequest(LoginRequest.java:248)
    [10] com.nps.ers.servlet.LoginRequest.getNextPage(LoginRequest.java:90)
    [11]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [12] com.nps.common.servlet.BaseServlet.doGet(BaseServlet.java:124)
    [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [15]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [16]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [18]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [19]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [20] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-22" (TID:0xabcc20, sys_thread_t:0xabcb60, state:CW,thread_t:
    t@33, threadID:0xd9631dc8, stack_bottom:0xd9632000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getEMTRoleId(E
    RSSystemConfigurationBeanEOImpl.java:1539)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.checkEMT(ApproverSelec
    tionBean.java:473)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.checkEMT(Approve
    rSelectionBeanEOImpl.java:71)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.chec
    kEMT(ApproverSelectionBeanEOImpl_ServiceStub.java:501)
    [9]
    com.nps.ers.servlet.NortelApproverSelection.updateApproverList(NortelApprove
    rSelection.java:87)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-21" (TID:0xa9ccf0, sys_thread_t:0xa9cc30, state:CW,thread_t:
    t@32, threadID:0xd9661dc8, stack_bottom:0xd9662000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2]weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3]weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-20" (TID:0xab2550, sys_thread_t:0xab2490, state:R,thread_t:
    t@31, threadID:0xd9691dc8, stack_bottom:0xd9692000, stack_size:0x20000)
    prio=5
    [1] java.net.SocketInputStream.socketRead(Native Method)
    [2] java.net.SocketInputStream.read(SocketInputStream.java:85)
    [3]weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [4]weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [5] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-19" (TID:0xa640c0, sys_thread_t:0xa64000, state:CW,thread_t:
    t@30, threadID:0xd96c1dc8, stack_bottom:0xd96c2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]com.nps.ers.ejb.user.UserBeanEOImpl.display(UserBeanEOImpl.java:1384)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.updatePointsUsed(AwardNo
    minationBean.java:1530)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.nominate(AwardNomination
    Bean.java:1279)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.nominate(AwardNomi
    nationBeanEOImpl.java:282)
    [9]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.nomina
    te(AwardNominationBeanEOImpl_ServiceStub.java:811)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [13]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [14] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [16] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [17]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [19]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [20]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [21]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [22] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-18" (TID:0xa502d8, sys_thread_t:0xa50218, state:CW,thread_t:
    t@29, threadID:0xd96f1dc8, stack_bottom:0xd96f2000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.organization.ERSSystemConfigurationBeanEOImpl.getCashWithinD
    ays(ERSSystemConfigurationBeanEOImpl.java:1231)
    [6]
    com.nps.ers.ejb.awardnomination.AwardNominationBean.getAwardNominationNotifi
    cationStates(AwardNominationBean.java:772)
    [7]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl.getAwardNomination
    NotificationStates(AwardNominationBeanEOImpl.java:247)
    [8]
    com.nps.ers.ejb.awardnomination.AwardNominationBeanEOImpl_ServiceStub.getAwa
    >>
    rdNominationNotificationStates(AwardNominationBeanEOImpl_ServiceStub.java:41
    5)
    [9]
    com.nps.ers.servlet.AwardNominationRequest.nominate(AwardNominationRequest.j
    ava:1339)
    [10]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [12]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [13] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [14] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [15] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [16]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [17]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [18]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [19]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [20]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [21] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-17" (TID:0xa242d8, sys_thread_t:0xa24218, state:CW,thread_t:
    t@28, threadID:0xd9721dc8, stack_bottom:0xd9722000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]
    com.nps.ers.ejb.user.UserBeanEOImpl.getUserStatusCode(UserBeanEOImpl.java:22
    77)
    [6]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBean.getApprovers(ApproverS
    electionBean.java:352)
    [7]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl.getApprovers(App
    roverSelectionBeanEOImpl.java:140)
    [8]
    com.nps.ers.ejb.awardnomination.ApproverSelectionBeanEOImpl_ServiceStub.getA
    pprovers(ApproverSelectionBeanEOImpl_ServiceStub.java:554)
    [9]
    com.nps.ers.servlet.ApproverSelection.getApproverList(ApproverSelection.java
    :81)
    [10]
    com.nps.ers.servlet.NortelApproverSelection.getApproverList(NortelApproverSe
    lection.java:62)
    [11]
    com.nps.ers.servlet.AwardNominationRequest.getApprovers(AwardNominationReque
    st.java:1412)
    [12]
    com.nps.ers.servlet.AwardNominationRequest.previewNominate(AwardNominationRe
    quest.java:1096)
    [13]
    com.nps.ers.servlet.AwardNominationRequest.processNextPage(AwardNominationRe
    quest.java:276)
    [14]
    com.nps.ers.servlet.AwardNominationRequest.getNextPage(AwardNominationReques
    t.java:109)
    [15]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [16] com.nps.common.servlet.BaseServlet.doPost(BaseServlet.java:184)
    [17] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [18] javax.servlet.http.HttpServlet.service(HttpServlet.java:835)
    [19]
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :75)
    [20]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:259)
    [21]
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:244)
    [22]
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:353)
    [23]weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:247)
    [24] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-16" (TID:0xaa0ed8, sys_thread_t:0xaa0e18, state:CW,thread_t:
    t@27, threadID:0xd9751dc8, stack_bottom:0xd9752000, stack_size:0x20000)
    prio=5
    [1] weblogic.common.internal.DynaQueue.getW(DynaQueue.java:219)
    [2]weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:212)
    [3]weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    [4] weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java:94)
    "ExecuteThread-15" (TID:0xad0220, sys_thread_t:0xad0160, state:CW,thread_t:
    t@26, threadID:0xd9781dc8, stack_bottom:0xd9782000, stack_size:0x20000)
    prio=5
    [1] weblogic.ejb.internal.BaseEJBContext.lock(BaseEJBContext.java:180)
    [2]weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:250)
    [3]
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:88)
    [4]weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:164)
    [5]com.nps.ers.ejb.user.UserBeanEOImpl.getUserId(UserBeanEOImpl.java:182)
    [6]
    com.nps.ers.ejb.login.LoginSessionBean.getUserStatus(LoginSessionBean.java:1
    61)
    [7]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl.getUserStatus(LoginSessionBeanE
    OImpl.java:212)
    [8]
    com.nps.ers.ejb.login.LoginSessionBeanEOImpl_ServiceStub.getUserStatus(Login
    SessionBeanEOImpl_ServiceStub.java:554)
    [9]
    com.nps.ers.servlet.LoginRequest.processLoginRequest(LoginRequest.java:248)
    [10] com.nps.ers.servlet.LoginRequest.getNextPage(LoginRequest.java:90)
    [11]com.nps.common.servlet.BaseServlet.handleRequest(BaseServlet.java:245)
    [12] com.nps.common.servlet.BaseServlet.doGet(BaseServlet.java:124)
    [13] javax.servlet.http.HttpServlet.service(HttpServlet.java:708)
    [14

  • WLS dies during stress testing

    We're using JMeter to send continuous requests to the server. It creates
    1500 threads and each requests Hello.jsp (see below) 500 times.
    The server runs fine for about 6.5 minutes (serviced ~120000 requests)
    before locking up. We let it sit for a while and about 4 minutes later, it
    starts spewing out the following (bottom part of weblogic.log)
    Fri May 19 10:48:37 GMT-04:00 2000:<I> <WebLogicServer> WebLogic Server
    started
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: init
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    verbose initialized to: true
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    packagePrefix initialized to: jsp_servlet
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    compileCommand initialized to: /opt/Solaris_JDK_1.2.2_05a/bin/javac
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    srcCompiler initialized to weblogic.jspc
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    superclass initialized to null
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    workingDir initialized to: /opt/ejbserver/weblogic/myserver/classfiles
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp: param
    pageCheckSeconds initialized to: 1
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:
    initialization complete
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> Generated
    java file:
    /opt/ejbserver/weblogic/myserver/classfiles/jsp_servlet/testpages/hello.java
    Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15123,localport=7111]''
    Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15172,localport=7111]''
    Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=11312,localport=7111]''
    Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=14368,localport=7111]''
    Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=14385,localport=7111]''
    Fri May 19 10:51:24 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15294,localport=7111]''
    Fri May 19 10:51:27 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15291,localport=7111]''
    Fri May 19 10:51:55 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=28068,localport=7111]''
    Fri May 19 10:51:56 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=28385,localport=7111]''
    Fri May 19 10:52:00 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=28421,localport=7111]''
    Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=63711,localport=7111]''
    Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connection rejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=63709,localport=7111]''
    Fri May 19 10:58:26 GMT-04:00 2000:<E> <WebLogicServer> Exception invoking
    weblogic.time.server.ScheduledTrigger@d2573f
    java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.lang.RuntimeException.<init>(Compiled Code)
    at weblogic.utils.UnsyncCircularQueue.expandQueue(Compiled Code)
    at weblogic.utils.UnsyncCircularQueue.put(Compiled Code)
    at weblogic.kernel.ExecuteThreadManager.execute(Compiled Code)
    at weblogic.kernel.Kernel.execute(Compiled Code)
    at weblogic.time.common.internal.ScheduledTrigger.private_execute(Compiled
    Code)
    at weblogic.time.server.ScheduledTrigger.private_execute(Compiled Code)
    at weblogic.time.common.internal.TimeTable.execute(Compiled Code)
    at weblogic.time.common.internal.TimeEventGenerator.run(Compiled Code)
    at java.lang.Thread.run(Thread.java:479)
    We get a steady stream of this exact same RuntimeException for about 20
    minutes before the whole thing dies.
    Any ideas would be great!
    Jason
    The setup is the following:
    Sun E250 with 1 CPU at 400MHz, 512 MB
    Solaris 2.6
    WLS 5.1 with SP3
    Solaris Performance Pack is used
    Sun JDK 1.2.2
    min heap size is 128MB and max as 128MB with options
    "-native -verbosegc"
    other changed to the OS:
    rlim_fd_max=4096
    rlim_fd_cur=4096
    tcp_close_wait_interval=10000
    tcp_flush_fin_wait_2=10000
    No paging/swapping takes place during the test.
    Hello.jsp is as follows:
    <html>
    <head>
    <title>A simple JSP file</title>
    </head>
    <body>
    <%
    out.print("<p><b>Hello World!</b>");
    %>
    </body>
    </html>

    Comments inline.
    Cheers - Wei
    Jason <[email protected]> wrote in message
    news:[email protected]...
    Thanks, that definitely sheds some light on the problem.
    We monitored the server and came up with the following. The queue isindeed
    growing and probably accounts for the eventual failure (does anyone know
    what the limit is?). The throughput is constant but just can't keep upwith
    the requests. Another thing is that the heap slowly increases along with
    the queue and it took a while for it to hit 100% and have GC occur.I am not sure about the limit. Either 32K or 64K, I guess. If you monitor
    your queue lenght frequently, you might have a chance to spot that limit.
    Every request need memory to hold. So the heap slowly increases along with
    the queue.
    >
    Now, we duplicated the test but accessed a Servlet directly instead of a
    JSP. This servlet simply did some out.print(...) statements to displaythe
    same page as Hello.jsp. This ran without a hitch. We had about 5 times
    more throughput and the queue wasn't growing out of control. Also, theheap
    would reach 100% much quicker and GC occured more frequently. I can't see
    how handling a JSP request is that much more resource intensive than a
    Servlet request...
    We then tried the original test again (accessing JSP) but this timeremoved
    Service pack 3. We were running straight WLS 5.1 (no service packs).
    Everything behaved nicely (just like the Servlet test did). Could it then
    be that SP3 introduced a bug relating to how JSP requests are handled?Well, if this was the case, you might need to address this with support.
    >
    Finally, all the tests ran without changing the default number of execute
    threads (15). I don't think increasing the number will help seeing how
    short-lived these requests are. I think more execute threads would just
    increase the context-switching.I agree. I've seen 15 to 60 threads in production. Might be worth a try to
    use larger number of threads in your test to see if it alleviated the
    problem.
    >
    Thanks again,My pleasure.
    Jason
    Wei Guan <[email protected]> wrote in message
    news:[email protected]...
    WebLogic has its interal request queue to enqueue all requests. Therequest
    refers to an unit of work for weblogic to process, such as a triggeredtime
    service, http request, etc. The finite number of worker threads defined
    in
    your weblogic.properties file will dequeue the requests inside therequest
    queue and process the work.
    There is an upper limit on the size of this queue. The message you gotmeans
    that your test hit that limit. In practice, if there were lots of
    requests
    inside that queue, every request need to wait for lots of time beforebeing
    processed (the queue is FIFO I believed). Open your WebLogic Console and
    monitor the size of the queue, in your test or in your production, if
    you
    see the size of the queue increases constantly, there is somethingwrong.
    You might need to increase the number of threads to handle the load. If
    tuning up the number of threads doesn't help, you might need useweblogic
    clustering (or add more servers in your clustering) to share the load.
    WebLogic engineers might be able to lift up the upper limit of the sizeof
    the queue. However, the larger upper limit on the queue might not helpyou
    in practice. Tuning your configuration and making sure the number of
    requests inside the queue do not increase constantly might be a good
    practice to follow.
    My 2 cents.
    Cheers - Wei
    Jason <[email protected]> wrote in message
    news:[email protected]...
    We're using JMeter to send continuous requests to the server. It
    creates
    1500 threads and each requests Hello.jsp (see below) 500 times.
    The server runs fine for about 6.5 minutes (serviced ~120000 requests)
    before locking up. We let it sit for a while and about 4 minutes
    later,
    it
    starts spewing out the following (bottom part of weblogic.log)
    Fri May 19 10:48:37 GMT-04:00 2000:<I> <WebLogicServer> WebLogic
    Server
    started
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:init
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    verbose initialized to: true
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    packagePrefix initialized to: jsp_servlet
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    compileCommand initialized to: /opt/Solaris_JDK_1.2.2_05a/bin/javac
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    srcCompiler initialized to weblogic.jspc
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    superclass initialized to null
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    workingDir initialized to: /opt/ejbserver/weblogic/myserver/classfiles
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:param
    pageCheckSeconds initialized to: 1
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General> *.jsp:
    initialization complete
    Fri May 19 10:48:47 GMT-04:00 2000:<I> <ServletContext-General>
    Generated
    java file:
    /opt/ejbserver/weblogic/myserver/classfiles/jsp_servlet/testpages/hello.java
    Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15123,localport=7111]''
    Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15172,localport=7111]''
    Fri May 19 10:51:10 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=11312,localport=7111]''
    Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=14368,localport=7111]''
    Fri May 19 10:51:20 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=14385,localport=7111]''
    Fri May 19 10:51:24 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15294,localport=7111]''
    Fri May 19 10:51:27 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=15291,localport=7111]''
    Fri May 19 10:51:55 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=28068,localport=7111]''
    Fri May 19 10:51:56 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=28385,localport=7111]''
    Fri May 19 10:52:00 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=28421,localport=7111]''
    Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=63711,localport=7111]''
    Fri May 19 10:53:45 GMT-04:00 2000:<W> <ListenThread> Connectionrejected:
    'Login timed out after: '5000' ms on socket:
    'Socket[addr=47.187.230.161/47.187.230.161,port=63709,localport=7111]''
    Fri May 19 10:58:26 GMT-04:00 2000:<E> <WebLogicServer> Exceptioninvoking
    weblogic.time.server.ScheduledTrigger@d2573f
    java.lang.RuntimeException: <UTIL> UnsyncCircularQueue was full!
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.lang.RuntimeException.<init>(Compiled Code)
    at weblogic.utils.UnsyncCircularQueue.expandQueue(Compiled Code)
    at weblogic.utils.UnsyncCircularQueue.put(Compiled Code)
    at weblogic.kernel.ExecuteThreadManager.execute(Compiled Code)
    at weblogic.kernel.Kernel.execute(Compiled Code)
    atweblogic.time.common.internal.ScheduledTrigger.private_execute(Compiled
    Code)
    at weblogic.time.server.ScheduledTrigger.private_execute(Compiled
    Code)
    at weblogic.time.common.internal.TimeTable.execute(Compiled Code)
    at weblogic.time.common.internal.TimeEventGenerator.run(CompiledCode)
    at java.lang.Thread.run(Thread.java:479)
    We get a steady stream of this exact same RuntimeException for about20
    minutes before the whole thing dies.
    Any ideas would be great!
    Jason
    The setup is the following:
    Sun E250 with 1 CPU at 400MHz, 512 MB
    Solaris 2.6
    WLS 5.1 with SP3
    Solaris Performance Pack is used
    Sun JDK 1.2.2
    min heap size is 128MB and max as 128MB with options
    "-native -verbosegc"
    other changed to the OS:
    rlim_fd_max=4096
    rlim_fd_cur=4096
    tcp_close_wait_interval=10000
    tcp_flush_fin_wait_2=10000
    No paging/swapping takes place during the test.
    Hello.jsp is as follows:
    <html>
    <head>
    <title>A simple JSP file</title>
    </head>
    <body>
    <%
    out.print("<p><b>Hello World!</b>");
    %>
    </body>
    </html>

  • Alert "An internal exception has occurred during discovery." related with Lync

    Greetings All,
    I'm facing this alert in one Lync 2013 agent. The problem is the SCOM agent is trying to execute a Lync 2010 PowerShell script in folder “'C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync'” but this server is Lync 2013 so this folder
    does not exist, due to this error is generated the alert.
     I have recreated the SCOM health state folder in order to force all discoveries process, but the problem continues after. 
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Log Name:      Operations Manager
    Source:        Health Service Script
    Date:          3/13/2014 1:47:48 PM
    Event ID:      223
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MYSERVER.MYDOMAIN.LOCAL
    Description:
    DiscoverCluster.ps1 : 
    -Script Name:      Lync Server MP Central Topology Discovery
    -Run as account:   nt authority\network service
    -Execution Policy: Bypass
    Value of Source Id is {333B2339-35AA-8115-0B0D-639F319A6333}.
    Value of ManagedEntity Id is {4B127CAD-36D6-FCAB-507F-03FF1CF5555}.
    Value of Target Computer is MYSERVER.MYDOMAIN.LOCAL.
    Failed to load Lync Server Module. Error: The specified module 'C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync' was not loaded because no valid module file was found in any module directory..
    An exception occured during discovery script, Exception : System.Management.Automation.CommandNotFoundException: The term 'Get-CsManagementStoreReplicationStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
    spelling of the name, or if a path was included, verify that the path is correct and try again.
       at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
       at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Health Service Script" />
        <EventID Qualifiers="0">223</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-13T12:47:48.000000000Z" />
        <EventRecordID>130617</EventRecordID>
        <Channel>Operations Manager</Channel>
        <Computer>MYSERVER.MYDOMAIN.LOCAL</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DiscoverCluster.ps1</Data>
        <Data>
    -Script Name:      Lync Server MP Central Topology Discovery
    -Run as account:   nt authority\network service
    -Execution Policy: Bypass
    Value of Source Id is {88BB2339-35AA-8115-0B0D-639F31999999}.
    Value of ManagedEntity Id is {4B127CAD-36D6-FCAB-507F-77777777}.
    Value of Target Computer is MYSERVER.MYDOMAIN.LOCAL.
    Failed to load Lync Server Module. Error: The specified module 'C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync' was not loaded because no valid module file was found in any module directory..
    An exception occured during discovery script, Exception : System.Management.Automation.CommandNotFoundException: The term 'Get-CsManagementStoreReplicationStatus' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
    spelling of the name, or if a path was included, verify that the path is correct and try again.
       at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
       at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame).
    </Data>
      </EventData>
    </Event>
    Thanks!

    Try adding the NETWORK SERVICE account to the following local groups on the Edge server:
    RTC Component Local
    RTC Local Administrators
    Then restart the System Center Management service.
    This fixed it for me. If you look at the membership of the equivalent local groups on a Lync Server 2013 Front End you'll see that these groups contain the NETWORK SERVICE account. Looks to be an oversight by MSFT.
    Also you can refer below link, Same issue here
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/f164f5a4-8dab-4f28-8cef-5d83d98d78a7/lync-2013-mp-lync-application-discovery-issue-for-the-dmz-servers?forum=operationsmanagermgmtpacks
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • ApplicationException during Stress Testing

    Hi All,
    I have a PAR file(dynpage application) which is deployed in QA portal.  The client did stress testing i.e multiple users are trying to access the application at the same time, clicking on various buttons.  Sometimes they are getting
    'com.sap.xxx.xxx.ApplicationException.'
    I did complete testing at my end.  The same application is working fine in DEV portal.  I do not have access to QA portal.  Also, I could not perform stress testing in DEV portal.
    But I understand that the problem is not with the coding. 
    What could be the issue?  Please suggest.  Hope I am clear. If not, please let me know.
    Thanks.

    Hi,
    Please find the latest log file.   Please suggest.
    #1.5 #00145E0B8976007500000007000015B4000463672289F723#1235194519179#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleThrowable(Throwable t)####n/a##6ced9ac3ffd911ddc9db00145e0b8976#Thread[JCO.ServerThread-5,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Java###Error in Server "SAP.CCMS.J2EE.QP1" :
    #1#SAP.CCMS.J2EE.QP1#
    #1.5 #00145E0B8976007500000008000015B4000463672289F8AE#1235194519179#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleThrowable(Throwable t)####n/a##6ced9ac3ffd911ddc9db00145e0b8976#Thread[JCO.ServerThread-5,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###
    RfcException:
        message: CPIC-CALL: SAP_CMACCPTP on convId: 00000000
    ERROR       gateway shutdown
    TIME        Fri Feb 20 21:35:18 2009
    RELEASE     640
    COMPONENT   CPIC (TCP/IP)
    VERSION     3
    RC          731
    MODULE      r3cpic.c
    LINE        9279
    COUNTER     1
        Return code: RFC_FAILURE(1)
        error group: 102
        key: RFC_ERROR_COMMUNICATION#
    #1.5 #00145E0B8976007500000009000015B4000463672289F91E#1235194519179#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleThrowable(Throwable t)####n/a##6ced9ac3ffd911ddc9db00145e0b8976#Thread[JCO.ServerThread-5,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###
    RfcException:
        message: CPIC-CALL: SAP_CMACCPTP on convId: 00000000
    ERROR       gateway shutdown
    TIME        Fri Feb 20 21:35:18 2009
    RELEASE     640
    COMPONENT   CPIC (TCP/IP)
    VERSION     3
    RC          731
    MODULE      r3cpic.c
    LINE        9279
    COUNTER     1
        Return code: RFC_FAILURE(1)
        error group: 102
        key: RFC_ERROR_COMMUNICATION
         at com.sap.mw.rfc.api.RfcApi.rfcAbort(RfcApi.java:873)
         at com.sap.mw.rfc.api.RfcApi.RfcAbort(RfcApi.java:911)
         at com.sap.mw.jco.MiddlewareJRfc.abort(MiddlewareJRfc.java:449)
         at com.sap.mw.jco.MiddlewareJRfc$Server.abort(MiddlewareJRfc.java:1715)
         at com.sap.mw.jco.JCO$Server.abort(JCO.java:7004)
         at com.sap.mw.jco.JCO$Server.listen(JCO.java:7344)
         at com.sap.mw.jco.JCO$Server.run(JCO.java:7162)
         at java.lang.Thread.run(Thread.java:534)
    #1.5 #00145E0B8976007400000006000015B400046367228A2DF0#1235194519195#System.err##System.err####n/a##6ced9ac2ffd911dda72600145e0b8976#Thread[JCO.ServerThread-1,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Plain###Feb 20, 2009 9:35:19 PM  ...fcengine.handleThrowable(Throwable t) [Thread[JCO.ServerThread-1,5,SAPEngine_System_Thread[impl:5]_Group]] Error: Error in Server "SAP.CCMS.J2EE.QP1" :
    Edited by: Subashini on Feb 25, 2009 8:29 AM

  • Error occured during the "test of the interface"

    Hi,everybody
    where I do the "Test Configuration" in the ID(Tools->Test Configuration),an error occured.
    Internal Error         
                HTTP connection to ABAP Runtime failed.
                Error:403ForbiddenURL:http://NEUESDNWXI01:8001/sap/xi/simulation?sap-client=500
                User: PIDIRUSER
    what can i do with the error?
    Thanks

    Hi
    Check if the  service for testing in XI (in transaction SCIF)is  turned on,
    <i>Note :Forebidden is generally an auth or password error. </i>
    Also Check This
    4) Error: HTTP 403 Forbidden
    Description: The server understood the request, but is refusing to fulfill it
    Possible Tips:
    Path sap/xi/engine not active
    • HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
    • Because of Inactive Services in ICF –Go to SICF transaction and activate the services. Refer SAP Note -517484
    • Error in RWB/Message Monitoring- because of J2EE roles – Refer SAP Note -796726
    • Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. –Because of the URL is incorrect or the adapter is not correctly deployed.
    Regards
    krishna

  • Reloading Plug-In Page causes browser to hang during stress test on IE & NS

    When an applet page is in the process of being loaded using the Java Plug-In and a second request is made to reload that applet or a new applet several times in succession, the browser hangs. Is there a work around for the Java Plug-In version 1.3.1.

    Hi,
    You can see fixed bugs in 1.3.1_01 version at
    http://java.sun.com/j2se/1.3.1/ReleaseNotes.html
    This is one of them:
    http://developer.java.sun.com/developer/bugParade/bugs/4477187.html
    Description: Loading applets, using IExplorer 5.0/5.5, sometimes caused a system hang.
    Hopefully this bug fix relates to your problem.

  • MOVED: CPU temp sensor hitting 255C during stress test

    This topic has been moved to Overclockers & Undervolting & Modding Corner.
    https://forum-en.msi.com/index.php?topic=155824.0

    Quote from: Bas on 12-January-12, 16:02:07
    I doubt TMPIN0 is connected to anything, ergo your program is reading nothing.
    If something was 255C then you would see flames comming out of the system.
    Exactly, and the heatsink is cool to the touch and the fans slow down.
    255 is simply the maximum value of 1 byte - a value that goes from 1 to 256 or in this case, 0 to 255. For some reason the sensor seems to bug out and report a value as high as it can report.

  • Errors encountered during perfromance testing

    While doing some stress testing on our WLS server we kept seeing the
    following errors:
    1) NullPointerException on NTSocketMuxer, error log follows:
    Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux> failure in processSockets()
    loop: GetData: fd=16764 numBytes=23
    Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux>
    java.lang.NullPointerException: null native pointer - socket was closed
    at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
    Code)
    This error doesn't seem to have any immediate impact, although it can't
    be a good thing and it seems to happen even at times when we are not
    doing stress testing. Also, it is very frequent that we see the above
    messages. We are running WLS 4.51 w/ Service Pack 5. I am wondering if
    this is a problem w/ Service Pack 5 since I don't see this on another
    machine running WLS 4.51 with Service Pack 4. Both are using JDK 1.2.2.
    2) Connection Rejected, error log follows:
    Tue Feb 22 07:08:16 EST 2000:<W> <ListenThread> Connection rejected:
    Login timed out after 15000 msec. The socket came from
    [host=207.17.47.141,port=11929,localport=443] See property
    weblogic.login.readTimeoutMillis.
    I know how to adjust this for this one. My questions on this are:
    If I set my readTimeoutMillisSSL (SSL in this case) from 15000 to 30000
    what does this exactly mean. Does this mean that instead of allowing a
    max 15 seconds for a connection to be established, now I am allowing 30
    seconds? Also, is this only for the initial connection establishment (ie
    user login), or does this parameter effect other aspects of the
    connection later on? What negative side effects would I encounter if I
    set this to 60000 (1 minute)?
    Finally, what can I do so that a connection does not take over 15
    seconds to establish? Note this is not the norm, just happens more often
    during stress testing.
    3) Creating & Closing connection & DGCserver, log follows:
    Tue Feb 22 07:08:44 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
    144.14.157.204/144.14.157.204 2864292845294268830
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:51 EST 2000:<I> <DGCserver> tried to renew lease for
    lost ref: 902
    Tue Feb 22 07:08:52 EST 2000:<I> <RJVM> Heartbeat/PublicKey resend
    detected
    Tue Feb 22 07:08:54 EST 2000:<I> <DGCserver> tried to renew lease for
    lost ref: 904
    Tue Feb 22 07:08:58 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Why the constant trying to create connection, close connection?
    What is DGCserver?
    4) Ignoring message from a previous JVM, log follows:
    Tue Feb 22 08:29:50 EST 2000:<E> <RJVM> Ignoring message from a previous
    generation: JVMMessage from 8729925219143181234C138.8.222.21 to
    -3465797227003769874C192.168.100.61 with CMD_ONE_WAY, prtNum=6, ack=103,
    seqNum=1384
    Tue Feb 22 08:30:15 EST 2000:<I> <HTTPTunneling> Sending DEAD response
    What does this mean?
    5) PeerGoneExceptions
    What causes these?
    Our environment is set up as follows:
    WLS Server
    WLS 4.51 w/ Service Pack 5
    NativeIO = true
    ExecuteThreadCount = 40
    readTimeoutMillis=5000
    readTimeoutMillisSSL=10000
    Dell Pentium III 600 w/ 512 MB memory
    NT 4.0
    JavaSoft 1.2.2
    -ms128 -mx350
    WLS Client
    Java Application
    t3s and https (using WLS RMI)
    JavaSoft 1.1.7b
    typically Pentium 200 MHz or better w/ 64MB or more
    Basically our clients connect to our WLS server using RMI. Each client
    also has a callback object where the server sends event notification
    back to the clients. Most of the communication is back through these
    client callback objects. Its similar to a stock trading application in
    that 1 client incoming requests will generate 200 outgoing events (if
    for example there are 200 users on the system). The above observations
    where made while 25 very active users where on the system.
    Thanks very much for any and all help,
    Edwin Marcial
    Continental Power Exchange

    Hi Kim,
    Thanks for the response, but which problem in particular did you solve, I've
    listed a couple here.
    Edwin
    kim hyun chan wrote:
    hi,
    I met the problem like you before.
    so I reduce executeThreadCount from 50 to 20 , and then I solved my proplem.
    "Edwin Marcial" <[email protected]> wrote in message
    news:[email protected]...
    While doing some stress testing on our WLS server we kept seeing the
    following errors:
    1) NullPointerException on NTSocketMuxer, error log follows:
    Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux> failure in processSockets()
    loop: GetData: fd=16764 numBytes=23
    Tue Feb 22 05:08:28 EST 2000:<E> <NTSockMux>
    java.lang.NullPointerException: null native pointer - socket was closed
    at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
    Compiled Code)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:19)
    at weblogic.t3.srvr.ExecuteThread.run(ExecuteThread.java, Compiled
    Code)
    This error doesn't seem to have any immediate impact, although it can't
    be a good thing and it seems to happen even at times when we are not
    doing stress testing. Also, it is very frequent that we see the above
    messages. We are running WLS 4.51 w/ Service Pack 5. I am wondering if
    this is a problem w/ Service Pack 5 since I don't see this on another
    machine running WLS 4.51 with Service Pack 4. Both are using JDK 1.2.2.
    2) Connection Rejected, error log follows:
    Tue Feb 22 07:08:16 EST 2000:<W> <ListenThread> Connection rejected:
    Login timed out after 15000 msec. The socket came from
    [host=207.17.47.141,port=11929,localport=443] See property
    weblogic.login.readTimeoutMillis.
    I know how to adjust this for this one. My questions on this are:
    If I set my readTimeoutMillisSSL (SSL in this case) from 15000 to 30000
    what does this exactly mean. Does this mean that instead of allowing a
    max 15 seconds for a connection to be established, now I am allowing 30
    seconds? Also, is this only for the initial connection establishment (ie
    user login), or does this parameter effect other aspects of the
    connection later on? What negative side effects would I encounter if I
    set this to 60000 (1 minute)?
    Finally, what can I do so that a connection does not take over 15
    seconds to establish? Note this is not the norm, just happens more often
    during stress testing.
    3) Creating & Closing connection & DGCserver, log follows:
    Tue Feb 22 07:08:44 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:45 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
    144.14.157.204/144.14.157.204 2864292845294268830
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:50 EST 2000:<I> <RJVM> Closing connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Tue Feb 22 07:08:51 EST 2000:<I> <DGCserver> tried to renew lease for
    lost ref: 902
    Tue Feb 22 07:08:52 EST 2000:<I> <RJVM> Heartbeat/PublicKey resend
    detected
    Tue Feb 22 07:08:54 EST 2000:<I> <DGCserver> tried to renew lease for
    lost ref: 904
    Tue Feb 22 07:08:58 EST 2000:<I> <RJVM> Creating connection to
    138.8.81.19/138.8.81.19 5634583086356155101
    Why the constant trying to create connection, close connection?
    What is DGCserver?
    4) Ignoring message from a previous JVM, log follows:
    Tue Feb 22 08:29:50 EST 2000:<E> <RJVM> Ignoring message from a previous
    generation: JVMMessage from 8729925219143181234C138.8.222.21 to
    -3465797227003769874C192.168.100.61 with CMD_ONE_WAY, prtNum=6, ack=103,
    seqNum=1384
    Tue Feb 22 08:30:15 EST 2000:<I> <HTTPTunneling> Sending DEAD response
    What does this mean?
    5) PeerGoneExceptions
    What causes these?
    Our environment is set up as follows:
    WLS Server
    WLS 4.51 w/ Service Pack 5
    NativeIO = true
    ExecuteThreadCount = 40
    readTimeoutMillis=5000
    readTimeoutMillisSSL=10000
    Dell Pentium III 600 w/ 512 MB memory
    NT 4.0
    JavaSoft 1.2.2
    -ms128 -mx350
    WLS Client
    Java Application
    t3s and https (using WLS RMI)
    JavaSoft 1.1.7b
    typically Pentium 200 MHz or better w/ 64MB or more
    Basically our clients connect to our WLS server using RMI. Each client
    also has a callback object where the server sends event notification
    back to the clients. Most of the communication is back through these
    client callback objects. Its similar to a stock trading application in
    that 1 client incoming requests will generate 200 outgoing events (if
    for example there are 200 users on the system). The above observations
    where made while 25 very active users where on the system.
    Thanks very much for any and all help,
    Edwin Marcial
    Continental Power Exchange

  • An error occured during the executin of the DETERMINE_ENGINE_RELEASE  i

    Hi,
             while installing EHP1 on java(Netweaver 2004s) using EHPInstalled we are stopped with this error in configuration stage
    An error occured during the executin of the DETERMINE_ENGINE_RELEASE phase could not detect as java release return code condition sucess evaluate to false for process java for ACTION_VERSION
    Please help us how to resolve this issue.
    Thanks in Advance

    Hi,
    I am getting the same error while upgrading to EHP4 and so not starting a seperate thread...
    I am pasting the log...
    Kindly suggest...
    This file is DETERMINE_ENGINE_RELEASE_DER_01.LOG
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[2.0.7.1006]/>
    <!NAME[/softcd_dump/EHPI/java/log/DETERMINE_ENGINE_RELEASE_DER_01.LOG]/>
    <!PATTERN[DETERMINE_ENGINE_RELEASE_DER_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
    <!ENCODING[UTF8]/>
    <!LOGHEADER[END]/>
    Feb 9, 2010 9:41:22 PM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/DETERMINE_ENGINE_RELEASE has been started.
    Feb 9, 2010 9:41:22 PM [Info]:                      com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypeDetectEngineRelease.
    Feb 9, 2010 9:41:22 PM [Info]: com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetector.detectEngineRelease(EngineReleaseDetector.java:73) [Thread[main,5,main]]: Checking AS Java release using version command.
    Feb 9, 2010 9:41:22 PM [Info]: com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetector.detectEngineRelease(EngineReleaseDetector.java:146) [Thread[main,5,main]]: The tool has not been found in location: /usr/sap/D50/DVEBMGS00/j2ee/cluster/bootstrap/scripts/version.sh.
    Feb 9, 2010 9:41:22 PM [Info]: com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetector.detectEngineRelease(EngineReleaseDetector.java:80) [Thread[main,5,main]]: Checking AS Java release using jspm tool.
    Feb 9, 2010 9:41:22 PM [Info]: com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetector.detectEngineRelease(EngineReleaseDetector.java:114) [Thread[main,5,main]]: The tool have been found in location /usr/sap/D50/DVEBMGS00/j2ee/JSPM.
    Feb 9, 2010 9:41:22 PM [Info]:       com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41) [Thread[main,5,main]]: AS Java process ID 4, name com.sap.sdt.jspm.main.Jspm has been started.
    Feb 9, 2010 9:41:22 PM [Info]:       com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54) [Thread[main,5,main]]:   Command line: /softcd_dump/EHPI/jvm/jre/bin/java -cp .:/usr/sap/D50/DVEBMGS00/j2ee/JSPM/lib/sdt_jspm.jar com.sap.sdt.jspm.main.Jspm -rootdir=/usr/sap/D50/DVEBMGS00/j2ee/JSPM -v
    Feb 9, 2010 9:41:22 PM [Info]:       com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55) [Thread[main,5,main]]:   Standard out: /softcd_dump/EHPI/java/log/JSPM_ACTION_VERSION__DER_01.OUT
    Feb 9, 2010 9:41:22 PM [Info]:                      com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:142) [Thread[main,5,main]]: Process ID 4 has been started.
    Feb 9, 2010 9:41:22 PM [Info]:                     com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:198) [Thread[main,5,main]]: Waiting for process ID 4, name java to finish.
    Feb 9, 2010 9:41:28 PM [Info]:                     com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:231) [Thread[main,5,main]]: Process ID 4, name java has been finished, exit code 1.
    Feb 9, 2010 9:41:28 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
    Feb 9, 2010 9:41:28 PM [Error]:        com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:524) [Thread[main,5,main]]: Return code condition success evaluated to false for process java for action ACTION_VERSION.
    Feb 9, 2010 9:41:28 PM [Error]:           com.sap.sdt.j2ee.tools.releasedetection.JSPMProcess.runVersionCommand(JSPMProcess.java:74) [Thread[main,5,main]]: Could not detect AS Java release.
    Feb 9, 2010 9:41:28 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/DETERMINE_ENGINE_RELEASE has been completed.
    Feb 9, 2010 9:41:28 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/02/09 21:41:22.
    Feb 9, 2010 9:41:28 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/02/09 21:41:28.
    Feb 9, 2010 9:41:28 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:05.925.
    Feb 9, 2010 9:41:28 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]
    This is Trouble ticket.txt
    Trouble Ticket Report
    Installation of enhancement package 1 for SAP NetWeaver 7.0
    SID................: SID
    Hostname...........: saptr10
    Install directory..: /usr/sap/SID
    Upgrade directory..: /softcd_dump/EHPI/java
    Database...........: $(/J2EE/DBSystem/DBInfoName)
    Operating System...: UNIX
    JDK version........: 1.6.0_07 SAP AG
    SAPJup version.....: 3.4.24
    Source release.....: $(/ER_CODE)
    Target release.....: 710
    Start release SP...: $(/J2EE/StandardSystem/SPLevel)
    Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
    Current usages.....:
    ABAP stack present.: true
    The execution of PREPARE/INIT/DETERMINE_ENGINE_RELEASE ended in error.
    Could not detect AS Java release.
    Return code condition success evaluated to false for process java for action ACTION_VERSION.
    More information can be found in the log file /softcd_dump/EHPI/java/log/DETERMINE_ENGINE_RELEASE_DER_01.LOG.
    Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
    com.sap.sdt.j2ee.phases.PhaseTypeDetectEngineRelease
    com.sap.sdt.j2ee.tools.releasedetection.EngineReleaseDetectionException
    Could not detect AS Java release.
    DETERMINE_ENGINE_RELEASE
    INIT
    PREPARE
    NetWeaver Enhancement Package Installation
    SAPJup
    Java Enhancement Package Installation
    Thanks,
    RaHuL...

  • ConnectionBean fail with stress test. please assist.

    I am using the following to get connected to database.
    package com.db;
    import java.util.*;
    import java.io.*;
    import java.sql.*;
    import javax.servlet.http.*;
    public class ConnectionManager implements HttpSessionBindingListener
      private Connection connection;
      private Statement statement;
      private String driver = "";
      private String dbURL = "";
      private String login = "";
      private String password = "";
    static public void main(String[] args)
          ConnectionManager cm = new ConnectionManager();
      } // main
    public ConnectionManager()
           Properties Prop = new Properties();
           try {
              InputStream configStream = getClass().getResourceAsStream("/config/database.properties");
                   Prop.load(configStream);
              configStream.close();
               } catch(IOException e) {
                      System.out.println("Error: Cannot laod configuration file ");
           driver =Prop.getProperty("driver");
           dbURL = Prop.getProperty("dbURL");
            login = Prop.getProperty("login");
            password = Prop.getProperty("password");
    public void setDriver (String sDriver)
       if (sDriver != null)
           driver = sDriver;
    public String getDriver ()
       return driver;
    public void setDbURL (String sDbURL)
        if (sDbURL != null)
         dbURL = sDbURL;
    public String getDbURL()
       return dbURL;
    public void setLogin (String sLogin)
       if (sLogin != null)
          login = sLogin;
    public String getLogin()
       return login;
    public void setPassword (String sPassword)
       if (sPassword != null)
          password = sPassword;
    private String getPassword()
       return password;
    private void getConn ()
       try
          Class.forName(driver);
          connection = DriverManager.getConnection(dbURL,login,password);
          statement=connection.createStatement();
       catch (ClassNotFoundException e)
          System.out.println("ConnectionManager: driver unavailable");
          connection = null;
       catch (SQLException e)
          System.out.println("ConnectionManager: driver not loaded");
          connection = null;
    public Connection getConnection()
       if (connection == null)
          getConn();
       return connection;
    public void commit() throws SQLException
        connection.commit();
    public void rollback() throws SQLException
        connection.rollback();
    public void setAutoCommit(boolean autoCommit)
        throws SQLException
        connection.setAutoCommit(autoCommit );
    public ResultSet executeQuery(String sql) throws SQLException
        if (connection == null || connection.isClosed())
            getConn();
        return statement.executeQuery(sql);
    public int executeUpdate(String sql) throws SQLException
        if (connection == null || connection.isClosed())
            getConn();
        return statement.executeUpdate(sql);
    public void valueBound(HttpSessionBindingEvent event)
        System.err.println("ConnectionBean: in the valueBound method");
        try
          if (connection == null || connection.isClosed())
            connection = DriverManager.getConnection(dbURL,login,password);
            statement = connection.createStatement();
        catch (SQLException e)
          e.printStackTrace();
          connection = null;
    public void valueUnbound(HttpSessionBindingEvent event)
        close();
    public void close()
       try
           if ( connection != null
                || !connection.isClosed())
            connection.close();
       catch (SQLException e)
          e.printStackTrace();
    }This is what I use to test this code:
    <%@ page import="java.sql.*" %>
    <%@ page import="java.text.*" %>
    <%@ page import="java.util.*"%>
    <%@ page import="java.io.*" %>
    <p>
    Testing DBConnection Bean. <p>
    <%
    String sql="SELECT * FROM BS_PERSON" ;
    com.db.ConnectionManager CM = new com.db.ConnectionManager();
    ResultSet rset = CM.executeQuery(sql);
    while (rset.next()) {
       out.println(rset.getString("PERSON_USERCODE") + "<br>");
    %>When I stress test it, the code perform well for a while and then throw the following on Tomcat:
    ConnectionManager: driver not loaded
    ConnectionManager: driver not loaded
    ConnectionManager: driver not loaded
    Is there anything I could improve?
    For application that has many database read/write, is there any open source connection program that uses connection pooling?
    Thank you.

    Thank you for the prompt response.
    Yes. the code works and the data set gets return when I execute the code. It only fail with stress test after say 150-160 hits.
    I have put in the printStack Trace and got the following:
    ConnectionManager: driver not loaded
    java.sql.SQLException: ORA-00020: maximum number of processes (150) exceeded
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
         at oracle.jdbc.ttc7.O3log.receive1st(O3log.java:407)
         at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:259)
         at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
         at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
         at java.sql.DriverManager.getConnection(DriverManager.java:512)
         at java.sql.DriverManager.getConnection(DriverManager.java:171)
         at com.db.ConnectionManager.getConn(ConnectionManager.java:106)
         at com.db.ConnectionManager.executeQuery(ConnectionManager.java:154)
         at org.apache.jsp.dbconnection_jsp._jspService(dbconnection_jsp.java:76)
    Could it be that I didn't specifically close the connection? How could I go about doing it?
    Thank you.

  • Error occured during the execution of the JSPM_main phase

    Hi,
    When ever I try to Start JSPM i get the following error saying that Cannot detect system kernel under the directory c:\usr\sap\EPD\sys directory and also error occured during the execution of the JSPM_main phase.
    Can any one help me in this regard.
    Thanks in advance.
    Thanks
    Venu

    Hi Anand,
    Please find the log file below.
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[C:\usr\sap\EPD\JC20\j2ee\JSPM\log\log_2007_04_03_16_57_45\JSPM_MAIN_1_01.LOG]/>
    <!PATTERN[JSPM_MAIN_1_01.LOG]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    #1.5#C000AC190C09000000000016019B539300042D33A14D91C0#1175599679640#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#JSPM/JSPMPhases/JSPM_MAIN#
    #1.5#C000AC190C09000000000017019B539300042D33A14DD040#1175599679656#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.jspm.phases.PhaseTypeJSPM#
    #1.5#C000AC190C09000000000018019B539300042D33A1531000#1175599680000#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:560)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:560)#Java###Starting Initialize dialog...##
    #1.5#C000AC190C0900000000001E019B539300042D33A15C5AE8#1175599680609#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:462)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:462)#Java###Detecting system parameters...##
    #1.5#C000AC190C0900000000001F019B539300042D33A15C5AE8#1175599680609#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#C:
    usr
    sap
    EPD
    JC20
    j2ee
    JSPM
    log
    log_2007_04_03_16_57_45
    DETECT_SYSTEM_PARAMETERS_01.LOG#
    #1.5#C000AC190C0900000000002D019B539300042D33A1AA1558#1175599685703#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:483)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:483)#Java###Detection of system parameters has finished.##
    #1.5#C000AC190C0900000000002E019B539300042D33A1AA4FF0#1175599685718#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:470)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:470)#Java###Initialize dialog has been processed.##
    #1.5#C000AC190C0900000000002F019B539300042D33A1AA4FF0#1175599685718#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1043)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1043)#Java###Starting dialog...#1#LogIn#
    #1.5#C000AC190C09000000000039019B539300042D33AA43E180#1175599830000#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1048)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1048)#Java###Dialog has been confirmed by the user.#1#LogIn#
    #1.5#C000AC190C0900000000003A019B539300042D33AA467D78#1175599830171#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Checking connectivity for SDM server on host , port ...#2#aprins02#52018#
    #1.5#C000AC190C0900000000003B019B539300042D33AA539CD8#1175599831031#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Connection to SDM server on host , port is valid.#2#aprins02#52018#
    #1.5#C000AC190C0900000000003C019B539300042D33AA65F810#1175599832234#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:192)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:192)#Java###Detecting components of the J2EE engine...##
    #1.5#C000AC190C0900000000003D019B539300042D33AA65F810#1175599832234#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#C:
    usr
    sap
    EPD
    JC20
    j2ee
    JSPM
    log
    log_2007_04_03_16_57_45
    DETECT_SYSTEM_COMPONENTS_01.LOG#
    #1.5#C000AC190C09000000000052019B539300042D33B5C8DEE8#1175600023265#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logError(JspmExtLoggingManager.java:275)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logError(JspmExtLoggingManager.java:275)#Java###Error during operation. For more information about the operation, see the previous message. For more information about the error, see the next messages.##
    #1.5#C000AC190C09000000000053019B539300042D33B5C91D68#1175600023281#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:258)#######Thread[main,5,main]##0#0#Warning#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:258)#Java###There are some WARNING messages in the child log .#1#C:
    usr
    sap
    EPD
    JC20
    j2ee
    JSPM
    log
    log_2007_04_03_16_57_45
    DETECT_SYSTEM_COMPONENTS_01.LOG#
    #1.5#C000AC190C09000000000054019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
    #1.5#C000AC190C09000000000055019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:285)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:285)#Java###java.io.IOException: CreateProcess: C:/usr/sap/EPD/JC20/exe/disp+work -V error=2##
    #1.5#C000AC190C09000000000056019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:284)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:284)#Java###Error while executing process C:/usr/sap/EPD/JC20/exe/disp+work.##
    #1.5#C000AC190C09000000000057019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:130)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:130)#Java###Could not start process C:/usr/sap/EPD/JC20/exe/disp+work.##
    #1.5#C000AC190C09000000000058019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.KernelRetriever.getCommandOutput(KernelRetriever.java:240)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.KernelRetriever.getCommandOutput(KernelRetriever.java:240)#Java###disp+work executable file cannot be run.##
    #1.5#C000AC190C09000000000059019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:767)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:767)#Java###Could not detect current system kernel in the C:
    usr
    sap
    EPD
    JC20
    exe directory.##
    #1.5#C000AC190C0900000000005A019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:435)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:435)#Java###Could not detect central instance kernel in directory C:
    usr
    sap
    EPD
    JC20
    exe.##
    #1.5#C000AC190C0900000000005B019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentsFromSystem(DetectKernelComponent.java:464)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentsFromSystem(DetectKernelComponent.java:464)#Java###Could not detect system kernel under the C:
    usr
    sap
    EPD
    SYS directory.##
    #1.5#C000AC190C0900000000005C019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectComponentsFromSystem(DetectKernelComponent.java:554)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectComponentsFromSystem(DetectKernelComponent.java:554)#Java###Could not detect version information of the current system kernel.##
    #1.5#C000AC190C0900000000005D019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:220)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:220)#Java###Could not detect deployed components.##
    #1.5#C000AC190C0900000000005E019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:676)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:676)#Java###Cannot initialize application data.##
    #1.5#C000AC190C0900000000005F019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#JSPM/JSPMPhases/JSPM_MAIN#
    #1.5#C000AC190C09000000000060019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/04/03 16:57:59#
    #1.5#C000AC190C09000000000061019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/04/03 17:03:43#
    #1.5#C000AC190C09000000000062019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:05:43.640#
    #1.5#C000AC190C09000000000063019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
    Thanks
    Venu

Maybe you are looking for

  • Deleting photos from HP Photosmart Studio

    I guess it doesn't get any more basic than this!  I'm using a friend's Mac for the first time, and iPhoto is easy to use, but I can't find how to delete images from HP Photosmart Studio!

  • OHS forwarding page request to WebLogic

    I have WebLogic v10.3.3.0 installed and up and running with Clustering. It has two managed servers, and each managed server is set up with SSL. I have an application deployed to the two managed servers and can bring up the application if typing in th

  • Limited Connectivity for users

    Hi all, We have 2 WLC connected with 7 RAPs and 16 MAPs , but some users connected to some APs don't get the DHCP IP and showing limited connectivity. But when I restart the APs ,they are able to connect sucessfully. The configurations of CoreSwitch,

  • Port configuration on WLC2006 and WLC2106

    In the WLC config guide V4.0 there is a clear explanation on how to use multiple distribution ports on the WLC440X. Is there also a similar sound description of how you can use multiple distribution ports on the WLC2006 and WLC2106 ? Somewhere in the

  • Compatibility after update to iOS 6.1.3

    I have a Philips Fidelio DS7550/37, and after running the latest iOS update, it no longer works... any suggestions?