WebLogic and Transaction related exception

We deploy our application on Web logic 8.1 and used SQL Server 2000 as database.
we received the following error: (never received this any time in the past for 3 yrs)
JTS.Site.DB_Name, HeuristicHazard, (javax.transaction.xa.XAException: [TDS Driver]The connection is closed)) !
Here is more information from Web Logic Log.
<ExecuteThread: '8' for queue: 'ServletQueue'> <<anonymous>> <BEA1-075FCECB75B815E20364> <BEA-110412> <Xid=BEA1-075FCECB75B815E20364(187704364),Status=Committed,HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=120,activeThread=Thread[ExecuteThread: '8' for queue: 'ServletQueue',5,Thread Group for Queue: 'ServletQueue'],XAServerResourceInfo[JTS.SITE.JNDI_Name]=(ServerResourceInfo[JTS.SITE.JNDI_Name]=(state=committed,assigned=PAS Name),xar=JTS.SITE.JNDI_Name])........
Any help or advice in this regard will be appreciated....Thanks.

Dear readers,
Found the cause: somewhere OpenJPA threw an exception which caused the transaction to roll back.
The exception was caught locally hiding the rollback.
cheers
Marc

Similar Messages

  • Weblogic 7 SP5 SQL Exceptions follow a JTA transaction timeout

    I have a problem in Weblogic 7 SP5 that was not happening in SP2. I'm using the
    Weblogic jDriver (weblogic.jdbc.mssqlserver4.Driver)
    I have a transaction that times out due to JTA transaction timeout, and then gets
    marked for rollback. For several minutes after the timeout, I get many SQL Exceptions
    with bogus messages like "invalid column name" when the column name is, in fact,
    correct.
    Then the weblogic log file shows "Exception during rollback of transaction" (javax.transaction.SystemException:
    Heuristic hazard). Next, the connection is tested on reserve, this test fails,
    and the connection is refreshed. As soon as the connection is refreshed, I stop
    getting SQL exceptions and everything starts working correctly again.
    It seems like the transaction timeout is making the connection go bad, and somehow
    other requests are using this bad connection before the transaction finishes rolling
    back. What could the problem be? Some excerpts from my app log and weblogic log
    are below.
    com.workpoint.server.ejb.WorkPointEJBException: The transaction is no longer active
    - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 901 seconds
    Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17109:68c10765ba68aaaa(12114044),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=901,seconds left=60,activeThread=Thread[WorkQueueThread[q=1, qName=ProcReleaseTaskWorkers,
    id=6],5,WorkQueueGroup[id=1, name=ProcReleaseTaskWorkers]],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none,xar=weblogic.jdbc.jts.Connection@18cd616,re-Registered
    = false),SCInfo[DomainManager+edwards-s1]=(state=active),properties=({weblogic.transaction.name=[EJB
    com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
    weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
    Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+)]'.
    No further JDBC access is allowed within this transaction.SQL Command = INSERT
    INTO WP_PROCI_NODE_HIST (NODE_HIST_ID, NODE_HIST_DB, PROCI_ID, PROCI_DB, PROCI_NODE_ID,
    PROCI_NODE_DB, NODE_ITERATION, NODE_STATE_ID, ROW_VERSION, LU_ID, LU_DATE) VALUES
    weblogic.jdbc.mssqlserver4.TdsException: Invalid column name 'user_fname'.
    [from weblogic log]
    ####<Jun 17, 2004 8:14:16 AM MDT> <Error> <EJB> <EDWARDS> <edwards-s1> <WorkQueueThread[q=1,
    qName=ProcReleaseTaskWorkers, id=7]> <kernel identity> <> <010025> <Exception
    during rollback of transaction Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17439:68c10765ba68aaaa(31878774),Status=Rolled
    back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=3,seconds left=57,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=edwards-s1,xar=weblogic.jdbc.jts.Connection@15e1b7e,re-Registered
    = false),SCInfo[DomainManager+edwards-s1]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
    com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
    weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
    Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+): javax.transaction.SystemException:
    Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException:
    I/O exception while talking to the server, java.io.EOFException))
    ####<Jun 17, 2004 8:14:17 AM MDT> <Warning> <JDBC> <EDWARDS> <edwards-s1> <ExecuteThread:
    '8' for queue: 'default'> <kernel identity> <> <001094> <A connection from pool
    "sp_connection_pool" was tested during reserve with the SQL "select 1" and failed:
    weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server,
    java.io.EOFException
    ...[stack trace omitted]...
    This connection will now be refreshed.>

    Brad Swanson wrote:
    According to BEA's documentation, the jDriver is deprecated (no longer supported)
    in WLS 7 SP5. Not sure when they stopped supporting it, but sometime after SP2,
    apparently. Our solution, unfortunately, was to stay with SP2. Using the newer,
    supported JDBC driver would presumably fix the problem, but we didn't have time
    to do a full regression test with a different driver.Hi, no. The jDriver is deprecated, not unsupported. For WLS releases that contain
    the jDriver it will be supported for as long as we support the WLS release!
    Deprecation just means that we may choose to not supply that driver in any future
    release, and will not support it in that or any subsequent release.
    Practically, much depends on which jDriver you're using. In decreasing order
    of practical support we have: The weblogic.jdbc.oci.Driver to Oracle: We do actively
    continue to fix bugs in it. The weblogic.jdbc.mssqlserver4.Driver: Very unlikely that
    we will fix any new problem with it. The weblogic.jdbc.ifmx.Driver: Even less
    likely that we will do anything with it...
    I hope that makes it better for you.
    Joe

  • Mqseries and weblogic: XA transactions with MessagingBridge

    Hello.
              Due to usage of XA transaction with MQSeries on host rather that weblogic host, require Extended Transactional Client - i have tried to use MessagingBridge feature in weblogic8.1.
              So, when we send message to JMS queue (source destination for messaging bridge) in transactional context it will be forwarded to MQSeries destination only after commit transaction. And if transaction will be crashed, MessagingBridge will not forward message from JMS to MQSeries.
              It is good substitution for XA transactions with MQSeries, i hope.
              In config.xml it looks like
              <BridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              Name="mq_q_xa_bridgeQueue" Properties="DestinationJNDI=TEST2;DestinationType=Queue;ConnectionURL=file:/c:/jndidir;InitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory;ConnectionFactoryJNDI=QCF2"/>
              <JMSBridgeDestination
              ConnectionFactoryJNDIName="thqueueconnectionfactory"
              DestinationJNDIName="bridgequeue" Name="THbridgequeue"/>
              <MessagingBridge AsyncEnabled="false" Name="wls2mqXA"
              QOSDegradationAllowed="false" QualityOfService="Exactly-once"
              SourceDestination="THbridgequeue" Started="true"
              TargetDestination="mq_q_xa_bridgeQueue" Targets="cgServer"/>
              And this implementation of XA transaction in weblogic+mqseries work.
              Does it have any bugs or hole or another disadvantages?
              Thanks.
              btw, i have found some interesting product at https://jmsbridgesxa.projects.dev2dev.bea.com/.
              But it not works on my environment (weblogic and mqseries on different hosts)

    Hello.
              Due to usage of XA transaction with MQSeries on host rather that weblogic host, require Extended Transactional Client - i have tried to use MessagingBridge feature in weblogic8.1.
              So, when we send message to JMS queue (source destination for messaging bridge) in transactional context it will be forwarded to MQSeries destination only after commit transaction. And if transaction will be crashed, MessagingBridge will not forward message from JMS to MQSeries.
              It is good substitution for XA transactions with MQSeries, i hope.
              In config.xml it looks like
              <BridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              Name="mq_q_xa_bridgeQueue" Properties="DestinationJNDI=TEST2;DestinationType=Queue;ConnectionURL=file:/c:/jndidir;InitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory;ConnectionFactoryJNDI=QCF2"/>
              <JMSBridgeDestination
              ConnectionFactoryJNDIName="thqueueconnectionfactory"
              DestinationJNDIName="bridgequeue" Name="THbridgequeue"/>
              <MessagingBridge AsyncEnabled="false" Name="wls2mqXA"
              QOSDegradationAllowed="false" QualityOfService="Exactly-once"
              SourceDestination="THbridgequeue" Started="true"
              TargetDestination="mq_q_xa_bridgeQueue" Targets="cgServer"/>
              And this implementation of XA transaction in weblogic+mqseries work.
              Does it have any bugs or hole or another disadvantages?
              Thanks.
              btw, i have found some interesting product at https://jmsbridgesxa.projects.dev2dev.bea.com/.
              But it not works on my environment (weblogic and mqseries on different hosts)

  • How to transport a transaction variant and her related screen variant?

    Hello to every SDN member,
    I am looking to transport a transaction variant and the related screen variants.
    I read the help and I am concerned by the paragraph about the Client-specific transaction variants because when I created the transaction variant, no dialog box appeared.
    In the paragraph about the Client-specific transaction variants, it is told to transport the variants with the Transport function but the problem is that I cannot find it. How can I use this function? It is not in the toolbar and not in the differents menus.
    Can you please give me the solution to transport the transaction variant and the screen variant?
    Thank you very much in advance.
    Best regards,
    Matthieu Chérier

    Hi,
    You can transport a variant by :
    1. Running the program RSTRANSP. Mention your program and variant name there.
    2.Create a variant with prefix 'CUS&'. This type of variants will be automatically transported to target system through transport request.
    3.Go to Se38 --> Input report name --> Select Variants
       On the screen  --> Go to Utilities -> Select transport request
        --> Provide the program name and Variant --> Assign Transport request to variant. Then release the transport.
    Regards.

  • Field sales related tables and Transaction code

    Dear SAPGurus,
    I have been working with field sales activities in mySAP CRM..
    Can I have the list of the tables and transaction code related to Field sales sales activies..
    I am grateful for ur help....
    I would like to appreciate u by rewarding the points
    Thanks a lot

    Hi Pratik Patel,
    Thank u very much for sending the table names.They are all very useful unto me
    Can I have the more table in this area
    If u have the CRM Data model and its relationship...Pls share with me..
    I  appreciate ur help by rewarding the points
    Regards,
    CRM Consultant

  • Relation between master and transaction data

    Hi experts,
    I have a basic question how the relation between masterdata and transction data is maintained in R/3. As I know first we extract master data and later transaction data in a typical R/3 based scenario.
    1.How does BW knows that , the transaction data are  related masterdata in the same sense as in R/3 ?
    I am involved in an enhancement of R/3 extractor. I need to derive 3 more fields and map it to info objects in BW. Cld any one explain me ( with an example plz) how these alignments to be made. How can I establish relation b/w derived fields and transaction data during extractions ?
    regs
    D Bret

    Hi Dave.
    Let's see if I can get all of your questions answered.  First, when Transactional Data is loaded, BW checks to see if a SID exists for each characterisatic field & value in the load.  If one doesn't, it either creates a SID (Surregate ID) in the master data tables (default action) or the load fails (if the enforece referential intgegrity flag is set).  It's better to load master data first in either case as it will improve the performance of the transactional load.
    In terms of R/3, the data has similar relationships as in BW.  There are master data tables and transactional data tables.  The difference is that while R/3 uses ~1 master data table per field, BW uses more.  Same thing for transactional data.
    As for your enhancement, if everything you need for the derivation of the extra field is in R/3, then you can enhance the extractor in RSA6 and do the mapping in R/3.  Once you replicate the DataSource to BW and reconnect the transformation & update rules, the load should work.  If you can give a bit more information on what sort of enhancement you are attempting, I can give a better example.
    Cheers,
    Adam

  • Weblogic 5.1 - Unrelated exceptions in application

    I have been trying to figure this problem for about an hour now. Apparently
    it is only happening on heavy load, cannot reproduce it in our QA
    environment
    For last 2 weeks webloigc 5.1 sp9 on Sun Jdk 1.3, Solaris 5.8 (our live
    platform) starts acting strange after being run for a couple of hours.
    Interestingly no one has made changes to it, and the problem does not look
    related to a software patch in anycase, might even be a JVM bug.
    Basically weblogic starts throwing Exceptions all over the code, mostly they
    are null pointer exceptions except where we check for a null and throw an
    alternate exception. Its almost as if the reference table in the JVM decides
    that everything is null.
    Following is a bit of the log just before it crash, if anyone has hints as
    to what might be going on or has had similar problems please let me know.
    Thanks
    part of Log follows:
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:277)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:277)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.io.IOException: Broken pipe
    at java.net.SocketOutputStream.socketWrite(Native Method)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
    at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:114)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
    mpl.java:125)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.flushWithCheck(ServletOutp
    utStreamImpl.java:343)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.checkForFlush(ServletOutpu
    tStreamImpl.java:484)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamI
    mpl.java:197)
    at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:140)
    at jsp_servlet._prod50._loca.__loca._jspService(__loca.java:412)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:371)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:371)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    Login of user with roleid:3000, prod_USER
    java.io.IOException: Broken pipe
    at java.net.SocketOutputStream.socketWrite(Native Method)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
    at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:114)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
    mpl.java:125)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.checkForFlush(ServletOutpu
    tStreamImpl.java:488)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamI
    mpl.java:197)
    at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:140)
    at jsp_servlet._prod50._comn.__myprofile._jspService(__myprofile.java:422)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    Mon Feb 09 15:07:51 EST 2004:<I> <EJB JAR deployment
    /prod/jars/reuse/ejb_RUNavigationS.jar> Exception in non-transactional EJB
    invoke:
    weblogic.ejb.extensions.LockTimedOutException: Lock for primaryKey:121_9:1
    timed out after 300000 ms.
    at
    weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
    at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
    at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
    at weblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
    at
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:162)
    at weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
    at
    com.prod.ejb.domain.runavigation.impl.RUNavigationDBeanEOImpl.getNavigation(
    RUNavigationDBeanEOImpl.java:149)
    at
    com.prod.ejb.service.runavigation.impl.RUNavigationSBean.getNavigation(RUNav
    igationSBean.java:123)
    at
    com.prod.ejb.service.runavigation.impl.RUNavigationSBeanEOImpl.getNavigation
    (RUNavigationSBeanEOImpl.java:187)
    at
    com.prod.ejb.service.runavigation.impl.RUNavigationSBeanEOImpl_ServiceStub.g
    etNavigation(RUNavigationSBeanEOImpl_ServiceStub.java:157)
    at com.prod.applications.reuse.ui.Nav.populateCache(Nav.java:398)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:321)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:285)
    at com.prod.applications.site.ui.SiteUI.<init>(SiteUI.java:26)
    at jsp_servlet._prod50._mktp.__site._jspService(__site.java:191)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    com.prod.applications.reuse.ui.UIException: Exception on Client Id(121)
    at com.prod.applications.reuse.ui.Nav.populateCache(Nav.java:412)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:321)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:285)
    at com.prod.applications.site.ui.SiteUI.<init>(SiteUI.java:26)
    at jsp_servlet._prod50._mktp.__site._jspService(__site.java:191)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    com.prod.applications.reuse.ui.UIException: Exception on Client Id(121)
    at com.prod.applications.reuse.ui.Nav.populateCache(Nav.java:412)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:321)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:285)
    at com.prod.applications.site.ui.SiteUI.<init>(SiteUI.java:26)
    at jsp_servlet._prod50._mktp.__site._jspService(__site.java:191)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    calling _checkReloadConfig at iteration 2030
    Terminated

    It turns out that there was an OutOfMemoryException when this all starts. I
    had missed this as it was a single line Exception with no stack trace in a
    15MB log file :(
    We had our site load increase 5 folds in a week. All the problem starts with
    the OutOfMemoryException. Increasing the VM heap size to 1GB have fixed the
    issue.
    To me it looks as if the GC is removing valid references if there is a
    OutOfMemoryException, or maybe even something in WL51 that tries to recover
    from an out of memory state and decides to release referenced objects in its
    cache.
    Thanks Rob
    "Rob Woollen" <[email protected]> wrote in message
    news:[email protected]...
    Looks like a NullPointerException in your jsp page. It's very hard for
    us to tell you anything more without more information.
    -- Rob
    Haider Kazmi wrote:
    I have been trying to figure this problem for about an hour now.
    Apparently
    it is only happening on heavy load, cannot reproduce it in our QA
    environment
    For last 2 weeks webloigc 5.1 sp9 on Sun Jdk 1.3, Solaris 5.8 (our live
    platform) starts acting strange after being run for a couple of hours.
    Interestingly no one has made changes to it, and the problem does notlook
    related to a software patch in anycase, might even be a JVM bug.
    Basically weblogic starts throwing Exceptions all over the code, mostlythey
    are null pointer exceptions except where we check for a null and throwan
    alternate exception. Its almost as if the reference table in the JVMdecides
    that everything is null.
    Following is a bit of the log just before it crash, if anyone has hintsas
    to what might be going on or has had similar problems please let meknow.
    Thanks
    part of Log follows:
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:277)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:277)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.io.IOException: Broken pipe
    at java.net.SocketOutputStream.socketWrite(Native Method)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
    atweblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:114)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
    mpl.java:125)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.flushWithCheck(ServletOutp
    utStreamImpl.java:343)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.checkForFlush(ServletOutpu
    tStreamImpl.java:484)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamI
    mpl.java:197)
    at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:140)
    at jsp_servlet._prod50._loca.__loca._jspService(__loca.java:412)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:371)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    java.lang.NullPointerException
    at jsp_servlet._prod50._comn.__login._jspService(__login.java:371)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    Login of user with roleid:3000, prod_USER
    java.io.IOException: Broken pipe
    at java.net.SocketOutputStream.socketWrite(Native Method)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
    atweblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:114)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamI
    mpl.java:125)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.checkForFlush(ServletOutpu
    tStreamImpl.java:488)
    at
    weblogic.servlet.internal.ServletOutputStreamImpl.print(ServletOutputStreamI
    mpl.java:197)
    at weblogic.servlet.jsp.JspWriterImpl.print(JspWriterImpl.java:140)
    atjsp_servlet._prod50._comn.__myprofile._jspService(__myprofile.java:422)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    Mon Feb 09 15:07:51 EST 2004:<I> <EJB JAR deployment
    /prod/jars/reuse/ejb_RUNavigationS.jar> Exception in non-transactionalEJB
    invoke:
    weblogic.ejb.extensions.LockTimedOutException: Lock forprimaryKey:121_9:1
    timed out after 300000 ms.
    at
    weblogic.ejb.internal.LockManagerImpl.waitForLock(LockManagerImpl.java:53)
    at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:146)
    at weblogic.ejb.internal.LockManagerImpl.lock(LockManagerImpl.java:81)
    atweblogic.ejb.internal.StatefulEJBCache.bind(StatefulEJBCache.java:456)
    at
    weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
    t.java:162)
    atweblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
    at
    com.prod.ejb.domain.runavigation.impl.RUNavigationDBeanEOImpl.getNavigation(
    RUNavigationDBeanEOImpl.java:149)
    at
    com.prod.ejb.service.runavigation.impl.RUNavigationSBean.getNavigation(RUNav
    igationSBean.java:123)
    at
    com.prod.ejb.service.runavigation.impl.RUNavigationSBeanEOImpl.getNavigation
    (RUNavigationSBeanEOImpl.java:187)
    at
    com.prod.ejb.service.runavigation.impl.RUNavigationSBeanEOImpl_ServiceStub.g
    etNavigation(RUNavigationSBeanEOImpl_ServiceStub.java:157)
    at com.prod.applications.reuse.ui.Nav.populateCache(Nav.java:398)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:321)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:285)
    at com.prod.applications.site.ui.SiteUI.<init>(SiteUI.java:26)
    at jsp_servlet._prod50._mktp.__site._jspService(__site.java:191)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    com.prod.applications.reuse.ui.UIException: Exception on Client Id(121)
    at com.prod.applications.reuse.ui.Nav.populateCache(Nav.java:412)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:321)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:285)
    at com.prod.applications.site.ui.SiteUI.<init>(SiteUI.java:26)
    at jsp_servlet._prod50._mktp.__site._jspService(__site.java:191)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    com.prod.applications.reuse.ui.UIException: Exception on Client Id(121)
    at com.prod.applications.reuse.ui.Nav.populateCache(Nav.java:412)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:321)
    at com.prod.applications.reuse.ui.Nav.<init>(Nav.java:285)
    at com.prod.applications.site.ui.SiteUI.<init>(SiteUI.java:26)
    at jsp_servlet._prod50._mktp.__site._jspService(__site.java:191)
    at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :120)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:922)
    at
    weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
    l.java:886)
    at
    weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
    Manager.java:269)
    at
    weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:380)
    atweblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:268)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    calling _checkReloadConfig at iteration 2030
    Terminated

  • Current server is the coordinator and transaction is not found

    Hi,
    We're using Weblogic 8.1 SP3. We have a single weblogic domain and 2 clusters in it. EAR1 is deployed in cluster 1 and EAR2 is deployed in cluster 2. EAR2 is compiled and created using j2ee.jar and not weblogic.jar.
    We have a MessageDrivenBean which is CMT / Required in EAR1 calls a BMT Stateless Session Bean in EAR2.
    A new transaction is begun in the BMT SB method and commit or rollback is called based on exception. A RuntimeException is thrown back to the MDB in case the transaction is rolled back in Bean Managed SB.
    Sometimes from the Bean Managed SB the following exception is thrown:
    javax.transaction.TransactionRolledbackException: Current server is the coordinator and transaction is not found. It was probably rolled back and forgotten already.
         at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
         at com.oakgrovesystems.reactor.frontDesk.EJBFrontDeskBean_1gq9kv_EOImpl_813_WLStub.handleRequest(Unknown Source)
         at com.oakgrovesystems.reactor.requests.ReactorRequest.send(ReactorRequest.java:212)
         at com.oakgrovesystems.reactor.client.EJBReactorProxy.sendRequest(EJBReactorProxy.java:44)
         at com.oakgrovesystems.reactor.client.AbstractReactorProxy.handleRequest(AbstractReactorProxy.java:52)
         at sun.reflect.GeneratedMethodAccessor153.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at tavant.bpm.client.proxy.DynamicFailoverReactorProxy.invoke(DynamicFailoverReactorProxy.java:84)
         at $Proxy11.handleRequest(Unknown Source)
         at tavant.bpm.client.ProcessHome.handleRequest(ProcessHome.java:298)
         at tavant.bpm.client.ProcessHome.startProcess(ProcessHome.java:87)
         at tavant.bpm.client.processor.CreateWorkflowInstance.startProcess(CreateWorkflowInstance.java:70)
         at tavant.bpm.client.processor.CreateWorkflowInstance.invoke(CreateWorkflowInstance.java:51)
         at tavant.bpm.ejb.AsynchronousProcessorMessageBean.onMessage(AsynchronousProcessorMessageBean.java:58)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    This is not consistently reproducible though it happens when server is heavily loaded. When this exception occurs, the transaction in the BMT Session Bean is actually getting committed! The message gets redelivered from the MDB.
    What could be the problem?
    Regards
    Sandhya

    I'm seeing a similiar problem on our servers recently and thought I would add my problem as well. We are using Weblogic 8.1; don't know which SP is in production. We have an EAR file with an SB EJB that puts messages in a queue. The EAR is deployed in a cluster along with the queues. The errors below occurred in 3 of the 4 WLS instances in our cluster. This happened during a peak period and lasted for several seconds in Production.
    ###<Jul 1, 2005 11:18:12 AM EDT> <Warning> <RMI> <exsdxtxeax1x.prod.xxxx.xxx> <ems-04> <ExecuteThread: '12' for queue: 'web
    logic.kernel.Default'> <<WLS Kernel>> <> <BEA-080006> <Failed to associate the transaction context with the response while marshall
    ing an exception to the client:
    javax.transaction.TransactionRolledbackException: Current server is the coordinator and transaction is not found. It was probably
    rolled back and forgotten already..
    javax.transaction.TransactionRolledbackException: Current server is the coordinator and transaction is not found. It was probably
    rolled back and forgotten already.
    at weblogic.transaction.internal.TransactionManagerImpl.sendResponse(Ljava.lang.Object;)Ljava.lang.Object;(TransactionManag
    erImpl.java:1438)
    at weblogic.rmi.internal.BasicServerRef.associateTxContext(Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundRespo
    nse;)V(BasicServerRef.java:490)
    at weblogic.rmi.internal.BasicServerRef.postInvoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.sp
    i.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Throwable;)V(Optimized Method)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.InboundRequest;)V(Optimized Method)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteThread;)V(Optimized Method)
    at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Optimized Method)
    at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
    at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
    >

  • CMR and Transaction Attribute

    I got two ReadOnly CMP entity beans with a 1:N relationship, and one session facade,
    all with the TX attribute of NotSupported. When I tried to get the CMR collection
    in the session bean, WebLogic 6.1 SP3 threw an EJBException saying the CMR collection
    could not be accessed outside a TX context. Only by changing the TX attribute
    of the SLSB to Required (left the CMP bean TX attribute unchanged) could I get
    the collection. What is the reason behind this behavior? I want the caching
    feature of the ReadOnly beans but do not want ot pay any price for transactions.
    Is this possible?

    I do one more test and found
    UPDATE exception raised when I have foreign key in table. If I use only plain fild evething is ok. If add to entity foreign key field container raise exception when it try to update record.

  • Weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException

    Hi,
    We are working with Weblogic 6.1.
    The system was quite stable, but a couple of days ago some batch process suddenly
    started to fail, with no apparent reason, there was no change in the system neither
    in the code.
    The following exception is received:
    Stopped, RemoteException weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
    We have also noticed that other jobs had failed before due to some memory problems,
    but using the Weblogic Console; Monitoring; Performance, then when some jobs had
    some memory problems forcing the garbage collection the batches worked properly.
    Maybe these 2 problems have no relation between one an other, but they appeared
    at the same time.
    Any help will be appreciated.
    Thanks and best regards.

    Hi,
    We are working with Weblogic 6.1.
    The system was quite stable, but a couple of days ago some batch process suddenly
    started to fail, with no apparent reason, there was no change in the system neither
    in the code.
    The following exception is received:
    Stopped, RemoteException weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
    We have also noticed that other jobs had failed before due to some memory problems,
    but using the Weblogic Console; Monitoring; Performance, then when some jobs had
    some memory problems forcing the garbage collection the batches worked properly.
    Maybe these 2 problems have no relation between one an other, but they appeared
    at the same time.
    Any help will be appreciated.
    Thanks and best regards.

  • Transaction Timeout Exception

    Hello all
    Problem...
    I am retrieving approx 1200 records from an Oracle database via an CMP EJB findByXXXXX method. The problem is my Transaction times out after 30 seconds.
    What I have already done...
    I'm using Weblogic 6.0 and have configured the JTA to timeout after 2 minutes. However, I'm still getting a Transaction timeout exception after only 30 seconds. I would Appreciate any help. Thank-you....
    Mark.

    Sounds like you might be running into this bug:
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.transaction&item=379&utag=

  • Weblogic JMS bridge between Weblogic and oracle Advanced Queue

    Hi,
    We are facing some issues when we are trying to integrate with Oracle AQ JMS through Weblogic.
    We have configured a Foreign AQ server which points to the oracle Advanced Queue and we are trying to create a Weblogic JMS bridge between AQ and weblogic. The bridge works perfectly if create the connection factories and bridge destinations with NonTX mode. The issue is with XA mode. Also we have deployed the Resource adaper for XAResource to use XA transactions.
    No help is available for the exception on google too :)
    Following is the exception we are getting.
    <An error occurred in bridge "aqjmsbridge" during the transfer of messages (javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XA_OK
    javax.transaction.xa.XAException: method start should not be called on weblogic.transaction.internal.IgnoreXAResource
    at weblogic.jms.foreign.IgnoreXAResourceImpl.start(ForeignAQIntegration.java:260)
    at weblogic.connector.security.layer.AdapterLayer.start(AdapterLayer.java:513)
    at weblogic.connector.transaction.outbound.XAWrapper.start(XAWrapper.java:466)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1184)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1117)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:516)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:443)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy59.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    .).>
    Will appriciate any help for the above.
    Thanks and Regards,
    Navin

    Maybe this if of any help:
    - Re: Help with creating AQ JMS
    or
    - Re: AQ Weblogic integration - JMS-107: Operation not allowed on Connection

  • CMP and Transaction Attribute

    Hi All!
    I try to play with cmp entity beans. All I try to do is find instance and call one from the methods.
    When I use transaction attribute another than "Required", I get exception 25222. Application module creation exception.
    If I change attribute to "Required New" then I get error while bean try to UPDATE record.
    I can't understand why this update appear on findByPrimaryKey!
    Can any body give some information on JBO behavior?
    Mike
    null

    I do one more test and found
    UPDATE exception raised when I have foreign key in table. If I use only plain fild evething is ok. If add to entity foreign key field container raise exception when it try to update record.

  • What  type of plug in do I need to use between weblogic and tomcat please

    Hi,
    Can anybody please tell me what type of plugin do I need to install to communicate between Tomcat4.0 and weblogic6.1 sp2.actually I wanted to use a connection pool from my servlet on my local tomact where connection pool is created on remote weblogic server.........?
    I have no idea what to do. I tried including the weblogic.jar in my local classpath where my tomcat is sitting. This didnot work . I got the following error......
    I want to know is it possible.............?
    javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    Your response is very inportant......
    Thnaks

    Thanks a lot for your rely....
    then how could I use the remote connection pool in my
    local Tomcat server.....?If thats is not possible then
    what if organisation have two webservers...? you mean
    thay have to create connection pool in two servers
    rather on one server and use it every where.....?
    Still depends on what you are trying to achieve.
    Most clustered systesm use a connections on each server. They sync the data retrieved between servers, not the connections themselves.
    If you simply one a single connection point then you need to use a driver that proxies requests to and from the real connection point.
    RmiJdbc is free at http://www.objectweb.org/.
    There are commercial drivers available, search at http://industry.java.sun.com/products/jdbc/drivers, which provide an enterprise layer for database access. They are probably more robust and feature rich than the above one.

  • Listing WBS elements and object relations

    Hello Friends,
    I want to output all wbs-elements and attached objects in a list, but I'm not sure how to do this. Is there a standard report for this? In trans cj03 you can only se the relation between one wbs-element and its related objects... I want to view them all. I considered to make a report with quickviewer but I am not sure which tables to connect, as the data-fields in transaction cj03 only reffers to structure fields... I would appreciate any input...
    best regards
    Ballo

    Hi Robert,
    Check out the conversion routine attached to the WBS element, and you need to add code in your program to convert it before downloading.
    If no conversion exit is available, you need to write code to select its mapping from database table.
    cheers
    swastik

Maybe you are looking for

  • How to change workflow for expired qualification in HR Module

    Hi, My question how to change workflow for expired qualification in HR Module.We need to when date is expired tcode OOQA that system will check and that time workflow should be triggred. I have serached sap help but i am not understand please below m

  • I turned off my ipod and when i went to turn it back on again it showed the apple but thats all it shows.

    I turned off my ipod and when i went to turn it back on again it showed the apple but thats all it shows.  I can restart it by holding the power button and the home key but it never turns on.

  • Converting IDOC to XML

    Hi, I have an application where i have to convert an IDOC to XML format so that it can be handled by webmethods. I want to know how to convert IDOC to XML. I have seen that in SAP there are two port types, XML and XML HTTP. Are they used for posting

  • Mac Pro not detecting internal HD. Blinking Question Mark!!

    Hi there, Ive been looking for an answer about my problem but it seems most of the people has got the problem; the hard drive might be damaged. Thats not my case. Ive got two Mac Pros. One is working flawlessly. So I swaped HDs to see what happened a

  • Javadoc error ( import class )

    I'm getting this error when I try to generate documentation. I guess javadoc doesn't like the import statement, has anyone seen this before? Any solutions? GridWithListeners.java:47: '.' expected import Ml30Key; ^