Transactions of unknown materials

I have a problem with transactions that are not be encrypted. They have no errors. I followed the instructions of


Thank you.

Hello

It seems that your cost Manager is perhaps not active, or you use a method of costs for operations to assess the cost in the order and the first record might be in error.

To check if the cost Manager is active, go to: responsibility of stocks > Setup > Interface managers, Cost Manager must be active. If not, run it from the tools > Launch Manager

To check if there are records that are not encrypted by mistake, run the query: select count (*) in the mtl_material_transactions where costed_flag = 'E ';

If all these have been checked, and you have seen records, open an SR with the support of the inventory team, subcomponent 508, produced transactions to ask for help.

I hope this helps.

Kind regards
Released

Tags: Oracle Applications

Similar Questions

  • HP14 TS NOTEBOOK PC: software of unknown device

    I recently downloaded a recovery image started my sytem with it after no recovery manager missed
    Allot if things changed tho
    But I got a rear part by downloading their drivers
    I always get this unknown device needs software update message with an exclamation point on its icon with PCI simple communication controller
    in the section other devices
    AV tried searching online for the software but cannot find a
    pls help
    It is really disturbing me

    Hello:

    For Simple Comms PCI controller, you need this driver.

    This package provides the driver Intel Management Engine Interface (MEI) for the notebook models and operating systems. The Management Engine Interface allows communication between the Towmi operating system and the Intel Management Engine firmware.

    File name: sp65359.exe

    For the unknown device, I would need the ID of the material because there may be several different unknown materials.

    To find the hardware ID, go to the Device Manager and click on the remaining unknown device need drivers.

    Then click on the Details tab in the upper part of the device window unknown.

    Now you should see a drop-down list of property and it is set by default to the Description of the unit.

    On this list and select the third element (Hardware ID).

    After the first string of characters you see in the window.

  • Can't get rid of a TX - message keeps appearing and being processed by the OSB

    I have a sort of a poison message or TX, I can't empty. Every 10 seconds, I get a message from journal like the second one below and the number of pending messages to several places and OSB proxy service processed messages keeps climbing--all this without producing new messages on my part I tried to delete the Bank to default server on the server managed OSB and storing files of the JMS server. No luck.

    When this first started happening, the error messages resemble the first below. Something I did caused the change, I guess. However, it's the same TX ID overall.

    So, first of all, how can I get rid of this thing? It makes me nuts and prevents me from closing on a VINE.

    Secondly, why is it happening? I have a suspicion - would it because we have configured somehow mutiple domains with the same name for a distributed application? It is not my habit but it happened. These areas do not communicate directly, but there are areas that need to communicate with both. So I think that the ambiguity of the name can be wrong us. Just a guess, if.

    In this case, the field of the sgosb proxy service (this domain name is unique) is receiving messages from a queue lies in the pega_domain to Singapore and another proxy service is put a message to another queue in the pega_domain in the United Kingdom. Is not in a single TX; the first proxy service forwards the message to a queue in the sgosb_domain, the second proxy service receives this message and puts it in the other pega_domain. It's a TX XA for each proxy service.

    Just to make it more fun, the sgosb_domain has another service of proxy read from a different queue and sent to a queue in the third pega_domain to the United States.

    DRM for any help or idea.

    Oh yes, the field of the OSB's WLS 10.3.4 while the pega_domains are WLS 10.3.2

    Original error message
    ####<Apr 13, 2011 4:32:13 AM GMT> <Error> <EJB> <sg01app510> <sgosb_1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'>
    <<anonymous>> <> <92f54a30d60e6302:-4b6d523c:12f4cfeaabc:-8000-0000000000000123> <1302669133597> <BEA-010026> <Exception occurred during commit of 
    transaction Xid=BEA1-039B0B6D3D0E77C1B135(1898471720),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since 
    begin=0,seconds left=600,XAServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=(ServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=
    (state=new,assigned=none),xar=null,re-Registered = false),SCInfo[sgosb_domain+sgosb_1]=(state=rolledback),SCInfo[pega_domain+pega_1]=(state=rolledback),properties=
    ({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+, XAResources={eis/tibjms/Topic,
    WLStore_sgosb_domain_FileStore_auto_1, eis/aqjms/Queue, eis/wls/Queue, eis/tibjms/Queue, WLStore_sgosb_domain__WLS_sgosb_1, eis/AQ/aqSample, eis/aqjms/Topic,
    eis/pramati/Queue, eis/sunmq/Queue, WLStore_sgosb_domain_WseeFileStore_auto_1, WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1, 
    WSATGatewayRM_sgosb_1_sgosb_domain, eis/jbossmq/Queue, eis/activemq/Queue, eis/fioranomq/Topic, eis/tibjmsDirect/Topic, eis/wls/Topic, 
    eis/tibjmsDirect/Queue, eis/Apps/Apps, eis/webspheremq/Queue},NonXAResources={})],CoordinatorURL=pega_1+nj09mhm5078:22111+pega_domain+t3+):
    javax.transaction.RollbackException: This transaction does not exist on the coordinating server.  It was probably rolled back and forgotten.
            at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
            at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
            at weblogic.transaction.internal.CoordinatorImpl_1032_WLStub.commit(Unknown Source)
            at weblogic.transaction.internal.TransactionImpl$1.run(TransactionImpl.java:331)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.transaction.internal.SecureAction.runAction(SecureAction.java:72)
            at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:327)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:252)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:326)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.RollbackException: This transaction does not exist on the coordinating server.  It was probably rolled back and forgotten.
            at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:94)
            at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
            at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
            at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    The error message I receive now
    ####<Apr 13, 2011 4:51:38 AM GMT> <Error> <EJB> <sg01app510> <sgosb_1> <[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> 
    <92f54a30d60e6302:-42808c28:12f4d3173cb:-8000-0000000000000032> <1302670298730> <BEA-010026> <Exception occurred during commit of transaction 
    Xid=BEA1-0011D0679BA5074B8E12(1930603846),Status=Rolled back. [Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds 
    left=60,XAServerResourceInfo[WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1]=(ServerResourceInfo[WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1]=
    (state=rolledback,assigned=sgosb_1),xar=WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1239571724,re-Registered = 
    false),XAServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=(ServerResourceInfo[WLStore_pega_domain_ProcessEventJMS_Store_mgd1]=
    (state=rolledback,assigned=pega_1),xar=null,re-Registered = false),SCInfo[sgosb_domain+sgosb_1]=(state=rolledback),SCInfo[pega_domain+pega_1]=(state=rolledback),properties=
    ({}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+, XAResources={eis/tibjms/Topic, 
    WLStore_sgosb_domain_FileStore_auto_1, eis/aqjms/Queue, eis/wls/Queue, eis/tibjms/Queue, WLStore_sgosb_domain__WLS_sgosb_1, eis/AQ/aqSample, eis/aqjms/Topic, eis/pramati/Queue, eis/sunmq
    /Queue, WLStore_sgosb_domain_WseeFileStore_auto_1, WLStore_sgosb_domain_MesssageForwardingJMS_Store_mgd1, WSATGatewayRM_sgosb_1_sgosb_domain, eis/jbossmq/Queue, eis/activemq
    /Queue, eis/fioranomq/Topic, eis/tibjmsDirect/Topic, eis/wls/Topic, eis/tibjmsDirect/Queue, eis/Apps/Apps, eis/webspheremq/Queue},NonXAResources=
    {})],CoordinatorURL=sgosb_1+152.64.128.243:22110+sgosb_domain+t3+): weblogic.transaction.RollbackException: Unknown reason
            at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1881)
            at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:345)
            at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
            at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:553)
            at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:424)
            at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:326)
            at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
            at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
            at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
            at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
            at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: javax.transaction.xa.XAException
            at weblogic.store.gxa.internal.GXAResourceImpl.prepare(GXAResourceImpl.java:1227)
            at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1295)
            at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:500)
            at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:380)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2593)
            at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1321)
            at weblogic.transaction.internal.SubCoordinatorImpl.startPrepare(SubCoordinatorImpl.java:183)
            at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
            at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
            at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    .>
    Published by: SteveElkind on April 13, 2011 05:50

    I see these possibilities:

    -Cross over the security of the domain (like atheek1 mentioned).
    -Transaction timeouts are too short (I think that there is a default configurable large area, as well as the ability to define a basis of CMT or BMT. waiting periods)
    -Configuration has a duplicate name.

    It is not required to nominate every single store between areas, is not generally necessary to ensure that each JMS server is named unique (even if it can help in certain use cases).

    WebLogic requires the following when you work with several areas:

    -Each unique domain name.
    -Name of the each server wl unique, even if in different areas.
    -Name of the each server unique, even if jms in different areas (is usually not necessary - and not the problem in this case - but you should do it anyway).
    -Name each unique, even if saf agent in different areas (is usually not necessary - and not the problem in this case - but you should do it anyway).
    -Configure the security of the area.

    For a bit more details, see the "best practices" section of the JMS configuration edoc.

    Tom

    Published by: falls on April 13, 2011 09:33

    Published by: falls on April 13, 2011 09:35

  • Unknown to the Transactions with the error.

    Hello

    I am facing problem in waiting Unknown to Transactions with the following error.
    Error code
    An invalid account is associated with the element being processed
    Explanation of the error
    An invalid account is associated with the element being processed

    Help, please.

    Thank you

    GHG.

    Hi, GHG,.

    The records are stuck because of the good DISTRIBUTION_ACCOUNT_ID in not associated with these records stuck.

    Please see the note of oracle that provide the script to update the DISTRIBUTION_ACCOUNT_ID below.

    Misc. erroneous Transactions (Doc ID 1398623.1)

    Try this script on 1 if test environment does not work then go for SR.

    Kind regards

    Ganesh

  • Impossible to install KB2686827 and KB2656368, keeps telling me that Windows Update encountered an unknown error. Code 641

    Check and fix the completed transaction. All of the files and registry keys listed in this operation were repaired successfully.  But I'm not able to upgrade windows (KB2686827) and (KB2656368).  Its keep telling me that Windows Update encountered an unknown error. 641, the code Please HELP. I have Windows Vista Home Premium 32 bit. Thanks in advance.

    Original title: of my CBS.log

    Try the manual download for both method:

    Update of security for Microsoft .NET Framework 4

    Update of security for Microsoft .NET Framework 4

  • I tried to send an email and got the following message: an unknown error has occurred error number: 0x800CCC6F.

    Transaction failed.  Unable to send message. Possibility of abuse

    I tried to send an email and got the following message: an unknown error has occurred. Are subject: Hello from the UK', account: 'Martin', server: 'mail.btinternet.com', Protocol: SMTP, server response: 554 Transaction failed: cannot send the message due to the possibility of abuse. Please visit http://postmaster.yahoo.com/abuse_smtp.html for more information ', Port: 25, secure (SSL): no, Server error: 554, error number: 0x800CCC6F please can you advise what could be the problem?

    Hello

     
     
    1. what web browser do you use?   If you use Internet Explorer, what version you have?
    2. you use Yahoo mail?
    3. what anti-virus software is installed on your computer?

     
    "If you use Yahoo mail, I suggest you to report your request in the support forum for Yahoo mail.
    http://answers.Yahoo.com/dir/index?link=list&SID=396546091
     
  • Type [0] unknown calculation for the dynamic calculation. Only default agg/formula/time balance operations are managed.

    Hi all

    I came across this error last Monday. I tried all the recommendations and configurations and nothing seems to work to solve the problem.

    Here is the error message-

    [Game Sep 24 12:04:27 2015] Local, ARPLAN, ARPLAN, Ess.Tee@MSAD_2010/9240/Error (1012703)

    Type [0] unknown calculation for the dynamic calculation. Only default agg/formula/time balance operations are managed.

    [Game Sep 24 12:04:33 2015] Local, ARPLAN, ARPLAN, Ess.Tee@MSAD_2010/9240/Warning (1080014)

    Abandoned due to the State [1012703] [0x2e007c (0x56042d17.0xeadd0)] transaction.

    [Game Sep 24 12:04:33 2015] Local, ARPLAN, ARPLAN, Ess.Tee@MSAD_2010/8576/Warning (1080014)

    Abandoned due to the State [1012703] [0x40007d (0x56042d18.0x781e0)] transaction.

    [Game Sep 24 12:04:34 2015] Local, ARPLAN, ARPLAN, Ess.Tee@MSAD_2010/736/Info (1012579)

    Total time elapsed Calc [Forecast.csc]: [621,338] seconds

    The script I'm running-

    SET CACHE HIGH;

    SET MSG SUMMARY;

    LOW GAME REVIEWS;

    UPDATECALC OFF SET;

    SET AGGMISSG

    GAME CALCPARALLEL 2;

    SET CREATEBLOCKONEQ

    SET HIGH LOCKBLOCK;

    FIX ('FY16', 'Final', 'Forecasts', '11 + 1 forecasts', 'prediction of 10 + 2', '9 + 3 forecast', '8 + 4 forecasts', "forecast 7 + 5", "6 + 6 forecast", "forecast 5 + 7", 'forecast of 4 + 8', '3 + 9 forecast', 'forecast 2 + 10', '1 + 11 forecasts')

    DIFFICULTY (@IDESCENDANTS ('entity'))

    CALC DIM ("account");

    ENDFIX

    DIM CALC ("entity", "Currency");

    ENDFIX

    In the essbase.cfg I have already included-

    NETDELAY 24000

    NETRETRYCOUNT 4500

    /Calculator cache settings

    CALCCACHEHIGH 50000000

    CALCCACHEDEFAULT 10000000

    200000 CALCCACHELOW

    Lockblock/set limits

    CALCLOCKBLOCKHIGH 150000

    CALCLOCKBLOCKDEFAULT 20000

    CALCLOCKBLOCKLOW 10000

    Please suggest if there is a way to fix this error. I get a similar error for other calculations as well.

    Kind regards

    EssTee

    And you are positive that no one came in a new Member at level 0 as dynamic Calc?

    What are the versions do you use?

  • IOM, single-phase transaction Exception

    EIS,

    Lately, I noticed that there are a few errors in the newspapers about the JTA stuff. I'm not sure what caused these problems, but now they're here :-)

    Caused by: org.springframework.transaction.TransactionSystemException: failure JTA on commit; nested exception is javax.transaction.SystemException: a phase transaction BEA1-0A55CE70E54EFEEF22C1-6F696D4F7065726174696F6E7344425F69616D31 for oimOperationsDB_iam1 of the resource is in an unknown state.

    at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1044)

    at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:732)

    at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:701)

    at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)

    at oracle.iam.platform.tx.OIMTransactionManager.execute(OIMTransactionManager.java:22)

    at oracle.iam.catalog.repository.DBRepository.updateCatalogItems(DBRepository.java:4053)

    ... more than 193

    Caused by: javax.transaction.SystemException: a phase transaction BEA1-0A55CE70E54EFEEF22C1-6F696D4F7065726174696F6E7344425F69616D31 for oimOperationsDB_iam1 of the resource is in an unknown state.

    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:698)

    at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:555)

    at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:2064)

    at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2791)

    at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2701)

    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:319)

    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:267)

    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:307)

    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:301)

    at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1028)

    ... more than 198

    Caused by: oracle.jdbc.xa.OracleXAException

    at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1657)

    at oracle.jdbc.xa.client.OracleXAResource.commit(OracleXAResource.java:757)

    at weblogic.jdbc.jta.DataSource.commit(DataSource.java:1110)

    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:1434)

    at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:609)

    ... more than 207

    Caused by: java.sql.SQLException: ORA-00604: error occurred at the SQL level 1 recursive

    ORA-06550: line 1, column 7:

    PLS-00306: wrong number or types of arguments in the call to 'SYNCRN '.

    ORA-06550: line 1, column 7:

    PL/SQL: Statement ignored

    As they say, there must be some strange problems with the configuration of the transaction or something related to the oimOperationsDB_iam1 of source data/resources.

    Has anyone encountered this problem before? How did you solve this problem?

    Kind regards

    Vegard Aasen

    It seems that the problem of database. I found similar in 'Doc ID 1638989.1'.

    In your journal, I see that it comes in the catalogue (to the oracle.iam.catalog.repository.DBRepository.updateCatalogItems(DBRepository.java:4053)).

    The solution was the following: "apply the patch database #17501296 to the 11.2.0.4 database version.

  • WIP resource transaction


    Hello

    can I return a Resouce Transaction in a PENDING work order?

    Thank you

    Concerning

    Hello

    found the solution, I changed the Type of functioning power pull push for all the material for this WORK. I did the WIP move Transaction return and with materials with Push, the system referred only the resource. Before, changed again the Type of power to Push operation pull to all the material for this WORK.

    Concerning

    Samantha

  • WebLogic 8.14 - jdbc: Transaction has expired during application to XAResource 'PICPool '.

    Hello

    I invoke my mode of transaction and getConnection code:

    try {}

    String alias = "";

    javax.sql.DataSource ds = (javax.sql.DataSource) ic.lookup ("OraclePI");

    System.out.println ("test 1");

    If (inp.getCif ()! = null & &! inp.getCif (.equalsIgnoreCase("")) & &)

    inp.getAccountNumber ()! = null & &! inp.getAccountNumber (.equalsIgnoreCase("")) & &

    inp.getAccountAlias ()! = null & &! inp.getAccountAlias (.equalsIgnoreCase(""))) {}

    System.out.println ("test 2");

    Fitting out = null;

    connection = ds.getConnection ();      error here

    System.out.println ("test 3");

    I got the error:

    Test 1

    Test 2

    Alias of the exception:

    java.sql.SQLException: an unexpected exception while he used XAConnection java.sql.SQLException: XA error: XAER_

    RMERR: A resource manager error has occurred in the transaction branch start() failed on the 'PICPool' resource: XA

    ER_RMERR: A resource manager error has occurred in the transaction branch

    weblogic.transaction.internal.ResourceAccessException: Transaction has expired when application to XAResou

    CRE 'PICPool '.

    at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:724)

    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1191)

    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1124)

    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:269)

    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:449)

    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1592)

    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1512)

    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:455)

    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:410)

    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:344)

    at bphpbk.pi.piservice.PIServiceBean.executeService(PIServiceBean.java:4194)

    at bphpbk.pi.piservice.PIServiceBean.PIService_aroundBody4(PIServiceBean.java:737)

    to bphpbk.pi.piservice.PIServiceBean$ AjcClosure5.run (PIServiceBean.java:1)

    to com.ericpol.ejbim.aspect.InvocationInterceptor.ajc$ around$ com_ericpol_ejbim_aspect_InvocationInterce

    ptor$ $1 649afe7cproceed(InvocationInterceptor.AJ:1)

    to com.ericpol.ejbim.aspect.InvocationInterceptor.ajc$ around$ com_ericpol_ejbim_aspect_InvocationInterce

    ptor$ $1 649afe7c(InvocationInterceptor.AJ:49)

    at bphpbk.pi.piservice.PIServiceBean.PIService(PIServiceBean.java:604)

    at bphpbk.pi.piservice.PIService_px3dm8_EOImpl.PIService(PIService_px3dm8_EOImpl.java:46)

    at bphpbk.pi.piservice.PIService_px3dm8_EOImpl_WLSkel.invoke (ILweblogic.rmi.spi.InboundRequest; Lweblogi

    c.rmi.spi.OutboundResponse; Ljava.lang.Object); Lweblogic.rmi.spi.OutboundResponse; (Unknown source)

    at weblogic.rmi.internal.activation.ActivatableServerRef.invoke(ActivatableServerRef.java:90)

    to weblogic.rmi.internal.BasicServerRef$ 1.run(BasicServerRef.java:434)

    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)

    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)

    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:429)

    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:32)

    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)

    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

    at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1597)

    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1512)

    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:455)

    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:410)

    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:344)

    at bphpbk.pi.piservice.PIServiceBean.executeService(PIServiceBean.java:4194)

    What is the reason? Without transaction mode it works. What parameters to the connection pool are important set?

    Supports local transactions is disable


    Thank you

    concerning

    Solved. We have a few problems to test with transactions env and at the next accept env it works correctly, but only called from interface system (my Summoner doesn't) cordially

  • OSB 11 g - management transactions @ EJB typed Trasport

    Hello

    We are having a problem with the flow of the following messages:

    Http PS-> Local PS-> EJB BS-> EJB 2.1-> Oracle 8i DB

    We have activated + "Transaction Requiered" + in the Http and the Local PS.

    We active + "Same Transaction for answer" + local PS + (local PS is a Legacy adapter, ergo, it should be able to be re-used). +

    The Local PS on an error event, propagates the exception using a + 'answer failed. "+"

    The Http PS on an error event, intercepts the error and + "Successfully met" + for the customer.

    If the stream enconunters one exception the changes made by the EJB are not committed or rollbacked. The following response is the only evidence we have about what's going on:

    < con xmlns:con: fault = "http://www.bea.com/wli/sb/context" >
    < con: errorCode > BEA-382051 < / con: errorCode >
    < con: reason >
    No operation on the current thread
    < / con: reason >
    < con: location >
    pipeline response - < con: path > < / con: path >
    < / con: location >
    < / con: fault >

    We followed the steps to enable the features of the TX, you can lend me a helping hand?

    Thank you.

    --------

    UPDATE:

    Activate the Debug XA mode on the run, we get this exception:

    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425379 > < BEA-000000 > < registerMBean resources MBean isResourceRegisterMBean: false to resources : weblogic.jdbc.wrapper.JTSXAResourceImpl >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425380 > < BEA-000000 > < ResourceDescriptor [weblogic.jdbc.wrapper.JTSXAResourceImpl]: getOrCreate creates rd: name = weblogic.jdbc.wrapper.JTSXAResourceImpl
    resourceType = 2
    registered = true
    scUrls =
    xar = weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e
    good health = true
    lastAliveTimeMillis = - 1
    numActiveRequests = 0
    >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425390 > < BEA-000000 > < BEA1-000B1169AF02F558E4E0: null: XA.start (rm = weblogic.jdbc.wrapper.JTSXAResourceImpl, xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e) (, flags = TMNOFLAGS) >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425391 > < BEA-000000 > < resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl' setTransactionTimeout (30) not called. callSetTransactionTimeout = false supportsSetTransactionTimeout = true >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425393 > < BEA-000000 > < startResourceUse, number of active requests: 1, last time living : 0 ms it y a. >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425394 > < BEA-000000 > < BEA1-000B1169AF02F558E4E0: null: FACT of XA.start (rm = weblogic.jdbc.wrapper.JTSXAResourceImpl , xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > < BEA1-000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425395 > < BEA-000000 > < endResourceUse, number of requests: 0 active >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <>< 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425973 > < BEA-000000 > < BEA1-000B1169AF02F558E4E0: null: XA.end (rm = weblogic.jdbc.wrapper.JTSXAResourceImpl, xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e) (, flags = TMSUCCESS) >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <>< 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425973 > < BEA-000000 > < startResourceUse, number of active requests: 1, last time living : 0 ms it y a. >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > < BEA1 000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425974 > < BEA-000000 > < FACT of XA.end (rm = weblogic.jdbc.wrapper.JTSXAResourceImpl, xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e >)
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > < BEA1 000B1169AF02F558E4E0 > < 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520425974 > < BEA-000000 > < endResourceUse, number of requests: 0 active >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520426405 > < BEA-000000 > < startResourceUse, number of active requests: 1, last time living : 0 ms it y a. >
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520426425 > < BEA-000000 > < BEA1-000B1169AF02F558E4E0: null: FACT of XA.commit (rm = weblogic.jdbc.wrapper.JTSXAResourceImpl, xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e >)
    # < 29 October 2012 11 H 20' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-59a6deab:13a937f15aa: - 7ffd - 0000000000007f8d > < 1351520426425 > < BEA-000000 > < endResourceUse, number of requests: 0 active >
    # < 29 October 2012 11 H 20' ART > < Debug > < JNDIResolution > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520434298 > < BEA-000000 > <-failed to find NotificacionesPorting >
    # < 29 October 2012 11 H 20' ART > < Debug > < JNDIResolution > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520444302 > < BEA-000000 > <-failed to find NotificacionesPorting >
    # < 29 October 2012 11 H 20' ART > < health > < > < tepe008 > < TPBUSAPP1 > < weblogic. GCMonitor > < < < > anonymous > > <>< 1351520452165 > < BEA-310002 > < 75% of the total server memory is free >
    # < 29 October 2012 11 H 20' ART > < Debug > < JNDIResolution > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520454304 > < BEA-000000 > <-failed to find NotificacionesPorting >
    # < 29 October 2012 11 H 21' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520462782 > < BEA-000000 > < BEA1-000B1169AF02F558E4E0: null: XAResource [weblogic.jdbc.wrapper.JTSXAResourceImpl] .rollback () >
    # < 29 October 2012 11 H 21' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520462782 > < BEA-000000 > < startResourceUse, number of active requests: 1, last time living: 0 ms it y a. >
    # < 29 October 2012 11 H 21' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520462785 > < BEA-000000 > < BEA1-000B1169AF02F558E4E0: null: XAResource [weblogic.jdbc.wrapper.JTSXAResourceImpl] .rollback: failed, error code: XA_OK, message: no link associated with xid = BEA1-000B1169AF02F558E4E0-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C
    javax.transaction.xa.XAException: no connection associated with xid = BEA1-000B1169AF02F558E4E0-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C
    at weblogic.jdbc.wrapper.JTSXAResourceImpl.rollback(JTSXAResourceImpl.java:69)
    at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:1401)
    at weblogic.transaction.internal.XAServerResourceInfo.rollback(XAServerResourceInfo.java:746)
    at weblogic.transaction.internal.ServerSCInfo.startRollback(ServerSCInfo.java:872)
    at weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:2032)
    at weblogic.transaction.internal.ServerTransactionImpl.globalRetryRollback(ServerTransactionImpl.java:3086)
    at weblogic.transaction.internal.ServerTransactionImpl.globalRollback(ServerTransactionImpl.java:2838)
    at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:400)
    at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:379)
    at weblogic.transaction.internal.CoordinatorImpl.startRollback(CoordinatorImpl.java:343)
    at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke (unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:590)
    to weblogic.rmi.internal.BasicServerRef$ 1.run(BasicServerRef.java:478)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs (unknown Source)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    # < 29 October 2012 11 H 21' ART > < Debug > < JTAXA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520462788 > < BEA-000000 > < endResourceUse, number of requests: 0 active >
    # < 29 October 2012 11 H 21' ART > < error > < JTA > < tepe008 > < TPBUSAPP1 > < ExecuteThread [ASSET]: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < > anonymous > > <>< 1351520462814 > < BEA-110412 > < Xid = BEA1-000B1169AF02F558E4E0 (450424591), status = Rolled back. [Reason = weblogic.transaction.internal.TimedOutException: Transaction timed out after 29 seconds]
    BEA1-000B1169AF02F558E4E0],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=39,seconds left=30,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=TPBUSAPP1),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@1832e78e,re-Registered = false),SCInfo[TPBUS+TPBUSAPP1]=(state=rolledback),SCInfo[TPBUSESB+TPESB1]=(state=rolledback),properties=({weblogic.jdbc=t3://xxxxx}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=TPBUSAPP1+172.17.195.76:8505+TPBUS+t3+, XAResources={WLStore_TPBUS_FileStore-0, cgDataSource, p13nDataSource, WLStore_TPBUS_cgJMSPagingStore_1, WLStore_TPBUS_FileStoreTPBUSAPP1 weblogic.jdbc.wrapper.JTSXAResourceImpl (,_bpmArchDataSource,_WLStore_TPBUS__WLS_TPBUSAPP1,_WLStore_TPBUS_WSStoreForwardInternalFileStore,_WLStore_TPBUS_WseeFileStore_auto_1},_NonXAResources_=_{})], CoordinatorURL = TPBUSAPP1 + xxxxx + TPBUS + t3 +) full heuristic way: (weblogic.jdbc.wrapper.JTSXAResourceImpl, HeuristicHazard, (javax.transaction.xa.XAException: no connection associated with xid = BEA1-000B1169AF02F558E4E0-7765626C6F6769632E6A6462632E777261707065722E4A545358415265736F75726365496D706C)) >


    Thank you!

    Published by: 966992 on October 29, 2012 07:25

    -------


    UPDATE


    What I see in the OSB handled when I activated most febug functions:

    # < 29 October 2012 16:07:29 ART > < Debug > < JTA2PC > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-0002E247CCDEF558E4E0 > < 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649868 > < BEA-000000 > < BEA1-0002E247CCDEF558E4E0: null: active TX [BEA1-0002E247CCDEF558E4E0]-> pre_preparing
    java.lang.Exception: DEBUGGING
    at weblogic.transaction.internal.TransactionImpl.setState(TransactionImpl.java:1744)
    at weblogic.transaction.internal.ServerTransactionImpl.setPrePreparing(ServerTransactionImpl.java:3165)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:251)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:239)
    at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:299)
    at com.bea.wli.sb.pipeline.RouterContext.endTransactionalMsgFlow(RouterContext.java:321)
    at com.bea.wli.sb.pipeline.MessageProcessor.processResponse(MessageProcessor.java:216)
    at com.bea.wli.sb.pipeline.RouterCallback.onReceiveResponse(RouterCallback.java:100)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.onReceiveResponse(LoadBalanceFailoverListener.java:253)
    at com.bea.wli.sb.transports.local.LocalMessageContext.sendResponse(LocalMessageContext.java:246)
    at com.bea.wli.sb.transports.local.LocalMessageContext.close(LocalMessageContext.java:219)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    to com.bea.wli.sb.transports.Util$ 4.invoke(Util.java:351)
    to $Proxy150.close (Unknown Source)
    at com.bea.wli.sb.pipeline.MessageProcessor.finishProcessing(MessageProcessor.java:398)
    at com.bea.wli.sb.pipeline.RouterCallback.onReceiveResponse(RouterCallback.java:108)
    at com.bea.wli.sb.transports.LoadBalanceFailoverListener.onReceiveResponse(LoadBalanceFailoverListener.java:253)
    to com.bea.wli.sb.transports.ejb.EjbEndpoint$ 1.run(EjbEndpoint.java:402)
    at weblogic.work.ContextWrap.run(ContextWrap.java:41)
    to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTA2PC > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-0002E247CCDEF558E4E0 > < 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649868 > < BEA-000000 > < BEA1-0002E247CCDEF558E4E0: null: validation >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTA2PC > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-0002E247CCDEF558E4E0 > < 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649868 > < BEA-000000 > < BEA1-0002E247CCDEF558E4E0: null: co.commit >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTANaming > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < < anonymous > > BEA1-0002E247CCDEF558E4E0 > < 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649868 > < BEA-000000 > < SecureAction.runAction use the subject = < anonymous > for action: co.commit to t3: / / xxxxx >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTA2PC > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > < BEA1-0002E247CCDEF558E4E0 > < 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < BEA1-0002E247CCDEF558E4E0: null: remove weblogic.jdbc.wrapper.JTSXAResourceImpl, TMSUSPEND, beforeState = new, startThread = null >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTA2PC > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > < BEA1-0002E247CCDEF558E4E0 > < 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < BEA1-0002E247CCDEF558E4E0: null: remove weblogic.jdbc.wrapper.JTSXAResourceImpl, afterStatenew >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTAPropagate > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < PropagationContext: Peer = null, Version = 4 >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTAPropagate > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < +++ otherPeerInfo.getMajor (): 10 >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTAPropagate > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < +++ otherPeerInfo.getMinor (): 3 >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTAPropagate > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < +++ otherPeerInfo.getServicePack (): 0 >
    # < 29 October 2012 16:07:29 ART > < Debug > < JTAPropagate > < tepe008 > < TPESB1 > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < anonymous > > <>< 11d1def534ea1be0:-4ea62a70:13aaddff0d6: - 7ffd - 00000000000000af > < 1351537649869 > < BEA-000000 > < +++ otherPeerInfo.getRollingPatch (): 0 >

    Published by: 966992 on October 29, 2012 12:11

    You use an action to publish in the proxy mail flow? If Yes, then make sure that in the routing of the action Options to publish, you set Quality of Service (QoS) as "Exactly Once".

    Kind regards
    Anuj

  • I HA: can a master State Unknown to transition to instead of throwing IRE?

    Hello

    I 5.0.48

    I runs tests using the example of quotes with a cluster of four nodes. I have a question about the behavior of the cluster as replicas are killed.

    I start with four nodes, n1, n2, n3 and n4. N1 was elected master. N2 - n4 become replicas.

    If I kill n3 n1 rest master and written is still allowed as there are sufficient replicas to satisfy policy SIMPLE_MAJORITY. If I didn't then go on to kill n4, n1 is always master but InsufficientReplicasException is thrown in response to each entry. I see in the documentation, it's expected behaviour.

    In our case, we want to know immediately when the number of replicas becomes too few to meet the ReplicaAckPolicy, rather than waiting for the next transaction due to InsufficientReplicasException. We wonder if there is a way to organize for the master to the transition from unknown back when this condition arises. If this is not possible, is it possible for the application to learn it in the other direction? I read on Monitor.startListener () and MonitorChangeListener. These could help us?

    Any advice would be much appreciated.

    Best regards, Keith Wall.

    Keith,

    Yes, the various mechanisms of notification that informs the user of the status of the members are the right way to go. You have already noticed the Monitor and MonitorChangeListener classes and I hope that the javadoc (starting with com.sleepycat.je.rep.monitor.monitor) chapter in the guide of replication is pretty informative: http://docs.oracle.com/cd/E17277_02/html/ReplicationGuide/monitors.html. Also note the chapter on the use of com.sleepycat.je.rep.StateChangeListener: http://docs.oracle.com/cd/E17277_02/html/ReplicationGuide/replicawrites.html.

    The two mechanisms differ from the point of view of the question of if the management is at the point when the application has access to a ReplicatedEnvironment, or if it is done by an entity of the third party, such as a load balancer. They are two sides of the same coin. But neither to totally exempt the application code to handle the possibility of an InsufficientReplicasException.
    -It is always possible that the notifications will be sent and processed later than the exception
    -l' lack of response to a replica may be due to a temporary network problem, and as it was not a real change state, no notification is sent
    -If a node goes down, it cannot send its own notification, of course, and it may take a little while for other nodes to intervene, to detect status change and make a notification

    So the notification mechanisms can optimize and reduce the possibility of obtaining an InsufficientReplicasException, but it can not remove it completely. This could lead to having to manage various exceptions in the application code. For a long time, Jeff Alexander wrote this example of how he made a wrapper of the transaction to modularize all exception management: https://blogs.oracle.com/jhalex/entry/handling_transactions_in_bdb_je. We tend to do something in this sense when write us code that emits data against a BDB I HA cluster operations.

    Hope that helps,

    Linda

  • coherence.transaction.internal.storage.FixedPartitionKey exception

    Get the following exception when you try to insert POF objects in a transactional Cache


    2012-01-05 12:46:36.794/124.850 Oracle coherence GE 3.6.0.4 < WARNING > (thread = TransactionFrameworkThread, Member = 1): Manager Version of transactions caught exception: java.io.IOException (Wrapped): unknown user type: com.tangosol.coherence.transaction.internal.storage.FixedPartitionKey
    at com.tangosol.util.ExternalizableHelper.toBinary(ExternalizableHelper.java:215)
    to com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService$ ConverterKeyToBinary.convert (PartitionedService.CDB:60)
    at com.tangosol.util.ConverterEnumerator.next(ConverterEnumerator.java:99)
    at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService.splitKeysByOwner(PartitionedService.CDB:16)


    CODE
    ====

    Connection con = new DefaultConnectionFactory () .createConnection ("TransactionalCache");
    OptimisticNamedCache tokenCache = con.getNamedCache("AceTokenCache");
    Token tokenAdded is new token (UUID.randomUUID (), (), TOKEN_AVAILABLE, Networkid m:System.NET.SocketAddress.ToString);.
    tokenCache.put (tokenAdded.getTokenID (), tokenAdded);
    con. Close;


    CACHE CONFIGURATION
    =================

    Coherence-cache-config. XML

    <!--
    Transactional caching scheme.
    ->
    < transactional system >
    < scheme name > transactional example < / system-name >
    < service name > TransactionalCache < / service-name >
    < serializer >
    < instance >
    > class name < com.tangosol.io.pof.ConfigurablePofContext < / class name >
    < init-params >
    < init-param >
    type string < param > < / param-type >
    chips-pof - config.xml < param-value > < / param-value >
    < / init-param >
    < / init-params >
    < / body >
    < / serializer >
    < number of threads > 3000 < / thread count >
    < autostart > true < / autostart >
    < request-timeout > 30000 < / timeout request >
    < / transactional system >
    < / cache-plans >
    < / cache-config >

    I have POF working for other patterns of caching (Distributed, replicated) in the past.

    Help, please.


    Kind regards
    Ankit

    You need to include txn - pof - config.xml in your pof config file.

  • Update operation transaction expire

    Hello

    I have a large data structure that must be updated atomically (i.e. within a transaction). I call the logical service via a web service map, so I assume that the transaction starts when the logical service is called. It has a timeout of the transaction on the server, which I think is fixed at 30 seconds to the WebLogic level by our team of middleware. (See the following stack trace).

    The SDO XML update operation is less than 2 MB.

    1. is it possible to override this time-out in transaction space or data service level?
    2. is there a more effective way to make this update? Sending a big wad of xml is inefficient, and I'm not aware of any other format supported by the web services ODSI. I can't use mediator API straight from my client to ODSI.
    3. If I have to break my record, operation into pieces, is it possible to achieve effective transactional update through several web service calls?

    Any advice would be much appreciated.

    Thank you

    Jeff


    weblogic.xml.query.exceptions.XQuerySystemException: {bea - err} SYS003: unexpected exception
    at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:96)
    at weblogic.xml.query.transaction.TransactionManager.teardownOnSuccess(TransactionManager.java:178)
    at com.bea.ld.EJBRequestHandler.handleProcessingComplete(EJBRequestHandler.java:1020)
    at com.bea.ld.EJBRequestHandler.handlePusher(EJBRequestHandler.java:979)
    at com.bea.ld.EJBRequestHandler.invokeOperation(EJBRequestHandler.java:323)
    at com.bea.ld.ServerWrapperBean.invoke(ServerWrapperBean.java:153)
    at com.bea.ld.ServerWrapperBean.invokeOperation(ServerWrapperBean.java:80)
    at com.bea.ld.ServerWrapper_s9smk0_ELOImpl.invokeOperation(ServerWrapper_s9smk0_ELOImpl.java:141)
    to com.bea.dsp.ws.RoutingHandler$ PriviledgedRunner.run (RoutingHandler.java:96)
    at com.bea.dsp.ws.RoutingHandler.handleResponse(RoutingHandler.java:217)
    at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
    at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
    at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:176)
    at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
    at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
    at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
    to weblogic.wsee.server.servlet.BaseWSServlet$ AuthorizedInvoke.run (BaseWSServlet.java:285)
    at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.run (WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs (unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.transaction.RollbackException: Transaction timed out after 33 seconds
    BEA1-460E808DE23C779E385F
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1818)
    at weblogic.transaction.internal.TransactionImpl.checkIfCommitPossible(TransactionImpl.java:1708)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:255)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
    at weblogic.xml.query.transaction.TransactionHelper.commit(TransactionHelper.java:94)
    ... more than 30
    Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 33 seconds
    BEA1-460E808DE23C779E385F
    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1734)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1607)
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1879)
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1517)
    at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    to weblogic.work.SelfTuningWorkManagerImpl$ WorkAdapterImpl.run (SelfTuningWorkManagerImpl.java:516)
    ... 2 more

    If I remember correctly, ODSI only creates a transaction to create/modify/delete and libraryProcedure. If your physical data of java service is not one of those, and if what you call for is none of these, there will be no (global) transaction. That's why I wrote the book on xquery being declarative and compiler/optimizer etc in my previous post.

    Can you post the pragma and the signature of your physical data service function?

  • The transaction is no longer active - Transaction has expired after 30 seconds

    We have an intermittent error here, and I'm a rookie. The error will cause a 500 sent to the client every 10-20 POSTS and only occurs under heavy load. Heavy load exceeds for the day, but he'll be back.

    My first suspicion was the app work transaction code and database performance problems. But the app is not transactional and database is fine. The firm (4) server nodes all the problems at equal rates, and other applications on the farm are very well, so it seems to be specific app rather than rooted in the State of the server or database.

    I watched the battery a little closer and it seems to be some kind of internal persistence problem, but a completely alien to me. We have no persistent store configured, so I don't know where to start on this puppy.

    EJB Exception occurred during invocation of the House: weblogic.ejb.container.internal.StatelessEJBLocalHomeImpl@d1e1f4 threw the exception: < 1.0.0 not fatal General error > org.apache.openjpa.persistence.PersistenceException: operation is not active - status: ' marked rollback. [Reason = weblogic.transaction.internal.TimedOutException: Transaction has expired after 30 seconds]
    BEA1-32AE928C966AC66F424D]'. No other JDBC access is allowed in this transaction.
    < 1.0.0 not fatal General error > org.apache.openjpa.persistence.PersistenceException: operation is not active - status: ' marked rollback. [Reason = weblogic.transaction.internal.TimedOutException: Transaction has expired after 30 seconds]
    BEA1-32AE928C966AC66F424D]'. No other JDBC access is allowed in this transaction.
    at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:3784)
    at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:97)
    at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:83)
    at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:59)
    at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.handleCheckedException(SelectResultObjectProvider.java:155)
    to org.apache.openjpa.lib.rop.EagerResultList. < init > (EagerResultList.java:40)
    at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
    at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
    at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
    at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
    at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
    at sun.reflect.GeneratedMethodAccessor2150.invoke (unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    to $Proxy365.performAction (Unknown Source)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
    at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
    at sun.reflect.GeneratedMethodAccessor2149.invoke (unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
    at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
    at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
    at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
    to com.sun.xml.ws.server.WSEndpointImpl$ 1.process(WSEndpointImpl.java:139)
    to com.sun.xml.ws.transport.http.HttpAdapter$ HttpToolkit.handle (HttpAdapter.java:153)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:226)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.run (WebAppServletContext.java:3395)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs (unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    java.sql.SQLException: the operation is not active - status: ' marked rollback. [Reason = weblogic.transaction.internal.TimedOutException: Transaction has expired after 30 seconds]
    BEA1-32AE928C966AC66F424D]'. No other JDBC access is allowed in this transaction.
    at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:178)
    at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:188)
    at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:57)
    at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next (unknown Source)
    at org.apache.openjpa.lib.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:106)
    at org.apache.openjpa.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:210)
    to org.apache.openjpa.jdbc.sql.SelectImpl$ SelectResult.nextInternal (SelectImpl.java:2209)
    at org.apache.openjpa.jdbc.sql.AbstractResult.next(AbstractResult.java:168)
    at org.apache.openjpa.jdbc.kernel.SelectResultObjectProvider.next(SelectResultObjectProvider.java:99)
    to org.apache.openjpa.lib.rop.EagerResultList. < init > (EagerResultList.java:35)
    at org.apache.openjpa.kernel.QueryImpl.toResult(QueryImpl.java:1219)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:987)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:839)
    at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:770)
    at kodo.kernel.KodoQuery.execute(KodoQuery.java:47)
    at org.apache.openjpa.kernel.DelegatingQuery.execute(DelegatingQuery.java:525)
    at org.apache.openjpa.persistence.QueryImpl.execute(QueryImpl.java:229)
    at org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:269)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at kodo.persistence.KodoQueryImpl.getResultList(KodoQueryImpl.java:213)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactionsExcludingApplication(ApproveApplicationHelper.java:167)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.createNewTransactions(ApproveApplicationHelper.java:129)
    at com.company.buapp.buslogic.helpers.ApproveApplicationHelper.stageAction(ApproveApplicationHelper.java:74)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean.performAction(ApproveApplicationSessionBean.java:348)
    at sun.reflect.GeneratedMethodAccessor2150.invoke (unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at weblogic.ejb.container.injection.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:68)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    to $Proxy365.performAction (Unknown Source)
    at com.company.buapp.buslogic.session.ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.performAction(ApproveApplicationSessionBean_gc4fhc_ApproveApplicationSessionLocalImpl.java:148)
    at com.company.buapp.si.ApplicationWS.performAction(ApplicationWS.java:114)
    at sun.reflect.GeneratedMethodAccessor2149.invoke (unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:50)
    at weblogic.wsee.jaxws.WLSInvoker.invoke(WLSInvoker.java:42)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:247)
    at com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:97)
    at weblogic.wsee.jaxws.MonitoringPipe.process(MonitoringPipe.java:98)
    at com.sun.xml.ws.protocol.soap.ServerMUPipe.process(ServerMUPipe.java:62)
    to com.sun.xml.ws.server.WSEndpointImpl$ 1.process(WSEndpointImpl.java:139)
    to com.sun.xml.ws.transport.http.HttpAdapter$ HttpToolkit.handle (HttpAdapter.java:153)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:235)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:97)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:36)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:218)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:226)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.run (WebAppServletContext.java:3395)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs (unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

    It was actually my first conclusion as well. But when I went to the Source of data for this connection, I found that it is a driver not transactional. It's what made me go back and give the track a second look. I don't see any reference to the Source of the data in question. It is OpenJPA tips and tricks Session persistence.

    Non - XA drivers can still participate in an XA transaction through a variety of options for a JDBC data source - for example, "1PC" and "WURA" marked on the console. (If you want to understand the search terms "JTS" or "WURA" in the edocs JDBC).

    You seem to suggest that perhaps the adjustment can be made in a doc config, possibly of the application itself, right?

    Right. EJB have a transaction-timeout attribute.

    Rather than put in the console.

    WebLogic is a domain wide transaction-timeout by default that can be set on the console, but I tend to not recommend to use it. In addition, there is what is called a 'plan of deployment', which can be used to replace some of the common attributes EJB through the configuration, but I know personally use.

    But is not steam setting, if we use a nonXA driver?

    Laughing out loud

    I wonder if this thing could not tell me that he has to wait on the next available persistence subsystem to store simple session data?

    Sometimes, the problem is that there are applications app more complex/superiors of other periodicals. Sometimes the system is simply overloaded and takes 30 seconds to honour a request that can take normally 10 seconds.

    This other application is all about persistence. What happens if app2 suck a dry persistence subsystem and app 1 expected just to store session data?

    Could be.

    If the nonXA thing really doesn't kill not the quick workaround solution timeout, how could I-health check of the persistence subsystem?

    Don't know. At a wild guess I check for CPU 100% on all the parties concerned is used and review database statistics.

Maybe you are looking for

  • What program to launch my exe files with

    OK so I download something on my computer and the exe file was not open so I accidentally made sure all exe files open with winrar I fixed but know that I have to open it with a program and I don't know what program I need to run exe files, I'm on a

  • Networking freezes completely, only restart allows

    before I changed the power supply and now after that I sometimes find my network frozen (after I have unlock my computer and sign in again - maybe it is related to saving energy?) and frozen to - I mean completely unreversable frozen - network adapte

  • watermark Adobe?

    I had Adobe Creative Cloud for about 3 weeks now (it's student-teacher edition 1 year/prepaid) and just a short time ago, I went to import some sequences in the first and all of a sudden there seems to be a weird watermark on the right side of the mi

  • Do you provide Linux for Sony DSC-QX100 driver?

    I wanted to have Linux drivers to integrate the Sony DSC-QX100? What do you bring?

  • What is my cloud maximum storage capacity?

    What is my cloud maximum storage capacity?