Tuxedo Queue Problem

whenever I call tuxedo queue program ,
I meet some error message in ulog file .like this.
090148.kliux7!TMS_QM.280463.1.0: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message
operation failed because of the invalid message queue identifier): errno=22,qid=317696,buf=5369139416,bytes=4568,type=0,flag=2048

I also meet this problem;
the ULOG is:
193038.cipsms!BBL.680: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message operatio
n failed because the queue was removed): errno=36,qid=1,buf=135341876,bytes=4452
,type=-1073741824,flag=0
193038.cipsms!F000000.681: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message oper
ation failed because the queue was removed): errno=36,qid=2,buf=134691052,bytes=
4452,type=-1073741824,flag=0
193038.cipsms!F000000.682: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message oper
ation failed because the queue was removed): errno=36,qid=4,buf=134691052,bytes=
4452,type=-1073741824,flag=0
193038.cipsms!F000000.682: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message oper
ation failed because of the invalid message queue identifier): errno=22,qid=4,bu
f=134691052,bytes=4452,type=-1073741824,flag=0
193038.cipsms!F000000.682: LIBTUX_CAT:522: INFO: Default tpsvrdone() function us
ed
193038.cipsms!F000000.681: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message oper
ation failed because of the invalid message queue identifier): errno=22,qid=2,bu
f=134691052,bytes=4452,type=-1073741824,flag=0
193038.cipsms!F000000.683: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message oper
ation failed because the queue was removed): errno=36,qid=6,buf=134691052,bytes=
4452,type=-1073741824,flag=0
193038.cipsms!F000000.682: LIBTUX_CAT:522: INFO: Default tpsvrdone() function us
ed
193038.cipsms!F000000.681: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message oper
ation failed because of the invalid message queue identifier): errno=22,qid=2,bu
f=134691052,bytes=4452,type=-1073741824,flag=0
193038.cipsms!F000000.683: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message oper
ation failed because the queue was removed): errno=36,qid=6,buf=134691052,bytes=
4452,type=-1073741824,flag=0
193038.cipsms!F000000.684: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message oper
ation failed because the queue was removed): errno=36,qid=8,buf=134691052,bytes=
4452,type=-1073741824,flag=0
193038.cipsms!F000000.681: LIBTUX_CAT:522: INFO: Default tpsvrdone() function us
ed
193038.cipsms!F000000.685: ERROR: msgrcv err(LIBTUX_CAT:666: ERROR: Message oper
ation failed because the queue was removed): errno=36,qid=10,buf=134691052,bytes
=4452,type=-1073741824,flag=0
193038.cipsms!F000000.685: ERROR: msgrcv err(LIBTUX_CAT:669: ERROR: Message oper
ation failed because of the invalid message queue identifier): errno=22,qid=10,b
uf=134691052,bytes=4452,type=-1073741824,flag=0
193038.cipsms!F000000.685: LIBTUX_CAT:522: INFO: Default tpsvrdone() function us
ed
193038.cipsms!BBL.680: CMDTUX_CAT:26: INFO: The BBL is exiting system
I google the internet and find the reason maybe as follow:
1.somebody did an ipcrm and resources were cleaned.
2.Because, if the client's tpcall times out, the client probably
stops and its message queue disappears, resulting in the error essage. This is exactly what is meant by "client who exits efore the request is satisfied".
I don't know if there are other reason for this problem

Similar Messages

  • What is Event queue problem?

    HI,
    I have come across JSF document, they mentioned that Event queue
    Problem ins SUN's JSF implementation. what is that?

    You're going to have to be a little more specific.

  • OSB 10.3 JMS queue problem: JMSCorrelationID is null

    Hi everybody,
    I am new to OSB/ALSB, and need some help regarding JMS message handling. I am trying to put some input data into a JMS queue( say, reqQueue) and to get the response from another JMS queue(say resQueue). My architecture is:
    OSB proxy service->OSB business service->JMS queue(reqQueue)->BPEL process(through JMS adapter) ->JMS queue(resQueue)->OSB business service->OSB proxy service.
    I have used JMSCorrelationID for response correlation. but my problem is that when I am trying to test the service from proxy service, I am getting the JMSCorrelationId as null in BPEL process as well as in the weblogic server JMS log, and as I am getting the CorrelationId as null, I am unable to correlate the response, so I am not getting any response.
    This is urgent, please help me as soon as possible as possible.
    Thanks in advance.
    Joy

    Sovled it..
    OSB 10.3 JMS queue problem: JMSCorrelationID is null

  • Tuxedo queue size parameter is set in peoplesoft

    Hi
    Can you please help me on this
    tuxedo queue size parameter is set in peoplesoft
    Advance wishes

    Tuxedo queue size parameter is set in
       Select one
    a)tuxedo config file
    b)Service Parameter for tuxedo
    3)psappsrv.cfg
    d)installation of BEA tuxedo
    tuxedo queue size parameter is set in peoplesoft 

  • Monitoring Tuxedo queue-execution times.

    Hello,
    We are having some problems in our Tuxedo environment and would like to
    start monitoring a little the queueing-execution times for our services. As
    far as we can tell, we can see a couple of directions to follow:
    - Tmadmin scripts: Using psr, pq and pclt to gather information about
    the time requests sits queued.
    - Using SNMP: we have a SNMP capable tool that we can use to query the
    MIB and get the adequate values.
    As far as I can tell, I know a couple of things about monitoring, but
    far less about Tuxedo. Both ways seems possible to gather the data we need,
    but.... I would definetely appreciate any help-advice on the matter experts,
    for the best option to identify:
    - Peaks in service times for Tuxedo services.
    - Peaks in requests waiting for servers.
    I have seen tools out there that seem to do this kind of stuff, but
    I´m afraid in our environment the problem is in the Tuxedo applications, so
    I would like to gather data to have a first approach to the problem and then
    getting dirty into the Tuxedo applications. And, even more, I do not feel
    this products are doing anything but querying Tuxedo the same way I would
    do.
    Thanks for your help. I appreciate it a lot.
    Leopold.

    Hello,
    You can try the following:
      Queue q = jcsSession.getQueueByName("<queue name>");
      q.setExecutionSize(new Long(xx));
    Regards Gerben

  • IPC queue problems

    I�m working now with inter-process communication with queues in Solaris and facing the following problem: whenever we fill up a queue with messages, everything that relies on IPC hangs. Someone knows what�s happenning?

    Hi,
    What application are using ? the behaviour is quite dependent on the kernel parameter setting for Message Queues. More so to do with the buffer size of each message place in the queue.
    Do you get any error messages ?
    if you could highlight what application (Tuxedo or custom 'C' code, etc.) it would be easier to diagonise.
    regards
    anand

  • JMS queue problem integrating with TIBCO

    Hi all!
    We have several communication channels between XI 3.0 (SP21) and TIBCO via JMS queues. All of them are working fine except  one. This problem only happens in development and quality systems with SP21, production has SP17 and doesn't have this error on the same communication channel.
    We are getting the following error in communication channel details...
    27-03-2008 16:32:21   XI message ID corresponding to the JMS message ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' has the value 'null', with the ID: prefix removed+
    27-03-2008 16:32:21   XI message ID corresponding to JMS message with ID 'ID:EMS-QUALITY.14C46ECF3303EC:61' will be created with same value as JMSCorrelationID with value 'null'+
    27-03-2008 16:32:20   Error while processing message 'null';  detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in converting Binary message <?xml version="1.0" encoding="UTF-8"?> <ns0:MT_PedCarga_GE xmlns:ns0="http://pt.galp.is-oil.ec">    <Partner>        <ZIDIF>62</ZIDIF>    </Partner>    <Controle>        <Nr_Envio>29183049</Nr_Envio>        <Dt_envio>20080229</Dt_envio>        <Tipo_Carga>CPAT</Tipo_Carga>        <Operador>230</Operador>    </Controle>    <PedCarga>        <FRETE>            <Tipo_Registo>N</Tipo_Registo>            <Inst_Carreg>ES41</Inst_Carreg>            <Data_Execucao>20080228</Data_Execucao>            <Resp_Transporte>13</Resp_Transporte>            <Transporte>          </Transporte>            <Transportador>1700</Transportador>            <Ref_Externa_head>2008022931859</Ref_Externa_head>            <Gera_Docs>X</Gera_Docs>            <Imprim_Docs>X</Imprim_Docs>            <Imprim_Ordem_Carreg>X</Imprim_Ordem_Carreg>            <Confirm_Autom>X</Confirm_Autom>            <Operador>230</Operador>        </FRETE>        <ENTREGA>            <Tipo_Destinatario>1</Tipo_Destinatario>            <Local_Entrega>14018</Local_Entrega>            <Cod_Produto>GOA []</Cod_Produto>            <Quantidade>05100</Quantidade>            <Ref_Externa_Item>01737307470601</Ref_Externa_Item>            <Regime_Fiscal>N</Regime_Fiscal>        </ENTREGA>        <ENTREGA>            <Tipo_Destinatario>1</Tipo_Destinatario>            <Local_Entrega>14018</Local_Entrega>            <Cod_Produto>GOC []</Cod_Produto>            <Quantidade>13300</Quantidade>            <Ref_Externa_Item>02737307470602</Ref_Externa_Item>            <Regime_Fiscal>R</Regime_Fiscal>        </ENTREGA>    </PedCarga> </ns0:MT_PedCarga_GE> to XI message for message: null: InvalidParamException: Invalid message id: com.sap.guid.GUIDFormatException+
    Any clues?
    Regards,
    Fernando Figueiredo

    We changed the conversation ID from Message ID to Correlation ID.

  • Integration Sap PI - JCAPS through JMS queue problem

    Hi to all,
    we have to send data through Sap PI 7.1 to an application server Sun Seebeyond JCAPS via JNDI JMS.
    We created a Simple Java Test Class that sends data to Jcaps Queues using stcms libraries suggested from Sun.
    I already tested this code on Eclipse, and it works fine. (Jcaps receive correctly messages sent from Java Class)
    Using JMS Communication Channel on Sap PI with same settings used on Java Class (Queue Connection Factory, Initial Context Factory, URL, Queue Name) and deployed the same stcms libraries on PI,
    Jcaps doesn't receive any message. In ABAP Monitor and Communication Channel Monitor we don't check any error: infact in CC Monitor a "Succesfully Connected to Queue" is displayed.
    During our tests on Java Class, we tried to change CreateQueueSession istruction ( qsession = qcon.createQueueSession( false, javax.jms.Session.CLIENT_ACKNOWLEDGE ));
    we checked that any other setting (changing parameters required from Java Method), different from setting just exposed,
    messages are not received from Jcaps and we don't have any error during sending operation (like happens in Sap PI).
    So correct setting to send message to JCAPS are:
    Transacted = False;
    acknowledgeMode = CLIENT_ACKNOWLEDGE;
    How we can set this parameter in JMS Communication Channel on Sap PI?
    If the CC configuration is correct, where we can find the problem and what kind of issue could be? On client side (Sap PI) or on Server side (JCAPS)?
    Thanks

    In order to set Transacted = false, uncheck "Transactional JMS Session" in the Processing Tab of JMS adapter. Keep in mind that the message delivery is NOT guaranteed in such a scenario. It is recommended to use transactional sessions in JMS scenarios.
    The JMS sessions created by JMS adapter are of type "AUTO_ACKNOWLEDGE".
    Regards,
    TK
    Edited by: Sameej T.K. on Oct 20, 2010 10:47 PM

  • Jms queue problem in 11g

    exception trace is comming, while running the project in weblogic, in the project iam using jms queue, i configured the jms server and jms module and connection factory but it is showing these exception
    [The selected operation process could not be invoked.
    An exception occured while invoking the webservice operation. Please see logs for more details.
    oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: InvalidSecurity : error in processing the WS-Security security header]
    can any one please, provide the suggestions

    i got the solution for my problem, i just need to add owsm policies to my processs

  • JMS Queue problems causing EJB to rollback....

              We recently purchased WLS 6.1 and we have been using the product for the last few
              months. I am having a problem which I have detailed below. I have provided as much
              information as possible. If you need additional information, please let me know.
              Server A Config:
              Pentium III, 1000Mhz
              Windows 2000, SP2
              WLS WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
              Server B Config:
              SunBlade 100
              Solaris 5.8
              WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
              Server A contains a session EJB called GoalManager. This EJB has a method named cancel().
              The transactional attribute for all methods supported by this bean is REQUIRED. GoalManager
              uses a transactional data source deployed on Server A named "goal". There is nothing
              special about this data source aside from the fact that I have enabled two phase
              commit for it because a previous error was indicating that this was a required setting
              for the pool. A JMS server exists on Server B. A queue named "emailQueue" is set
              up as a destination on this JMS server. I also have a MDB on Server B that listens
              for messages on this queue. When a message is received, the MDB's onMessage() method
              extracts some properties from the message and sends an email to the specified recipient
              in the message. I have confirmed that this queue and MDB are working properly because
              I ran a small test program from the command prompt which creates a message and sends
              it to the queue on Server B. The MDB gets the message and sends the email to the
              correct recipient, so I am sure there are no misconfigurations on the server.
              The problem is as follows: The cancel() method in the GoalManager EJB on Server A
              performs some database work. If no exceptions are raised, the last task in the method
              attempts to access the queue on Server B and send a message to the queue. Here is
              the code that I am using to access the queue:
              QueueConnectionFactory queueFactory = (QueueConnectionFactory)context.lookup( "javax.jms.QueueConnectionFactory");
              QueueConnection queueConnection = queueFactory.createQueueConnection();
              Queue queue = (Queue)context.lookup( "emailQueue");
              QueueSession queueSession = queueConnection.createQueueSession( false, Session.AUTO_ACKNOWLEDGE);
              QueueSender queueSender = queueSession.createSender( queue);
              The cancel() method executes without error, but when the EJB container on Server
              A attempts to commit the transaction at the end of the cancel() method, I am receiving
              the following error on Server A's log:
              <Error> <EJB> <Exception during commit of transaction Name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
              Xid=0:7c2dda32cf39a36e(6911242),
              Status=Rolled back. [Reason=javax.transaction.xa.XAException],
              numRepliesOwedMe=0,
              numRepliesOwedOthers=0,
              seconds since begin=2,
              seconds left=10,
              ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=server1),
              ServerResourceInfo[JMS_EMailServer_NotDurable]=(state=rolledback,assigned=server1),
              SCInfo[FRX+server1]=(state=rolledback),
              SCInfo[frxnet+wlsvr1]=(state=rolledback),
              properties=({weblogic.transaction.name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
              weblogic.jdbc=t3://172.16.200.9:9005}),
              OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server1+172.16.200.9:9005+FRX+,
              Resources={})],
              CoordinatorURL=server1+172.16.200.9:9005+FRX+): javax.transaction.xa.XAException
              at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:853)
              at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:1124)
              at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:370)
              at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:186)
              at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1822)
              at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1607)
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
              at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
              at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
              at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
              at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.transaction.RollbackException: Could not prepare resource 'JMS_EMailServer_NotDurable
              - with nested exception:
              [javax.transaction.xa.XAException]
              at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1475)
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
              at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
              at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
              at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
              at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Just a quick note, I tried to change the following line to specify a "transacted"
              JMS session by passing "true" to the statement below. When I tested this, the cancel()
              method raised no exceptions, but the MDB on Server B is never invoked and the email
              is never sent. Strange.
              QueueSession queueSession = queueConnection.createQueueSession( true, Session.AUTO_ACKNOWLEDGE);
              If you need more info, let me know. I thank you for your help.
              

    Correct. According to the trace you have it set at 10 seconds, while the default is 30 seconds.
              Tom
              SAF wrote:
              > Thanks for the reply.
              >
              > Increase the trx time? You mean JTA, right?
              >
              > I already opened a case with BEA, so I'm waiting to get a response from them.
              >
              > Thanks again,
              >
              > Raffi
              >
              > Tom Barnes <[email protected]> wrote:
              > >Hi,
              > >
              > >I looked at the BEXAResource.java source code which the stack trace points
              > >at. It seems that from the
              > >JMS server's resource manager's point of view, it never heard of the transaction
              > >before, indicating
              > >that the transaction may have already rolled back. I think this could
              > >happen if the transaction
              > >times out before commit() is called, but I'm not sure what is wrong in your
              > >case -- as according
              > >to the trace you provided, your tx is 2 seconds old and your tx-timout is
              > >10 seconds.
              > >
              > >In any case, it looks like the culprit may be in the transaction code and
              > >not the JMS code...
              > >
              > >I suggest:
              > > A) increasing your tx timeout (what the heck give it a try)
              > > B) could it somehow be a clock synchronization problem? are multiple
              > >servers involved?
              > > C) posting to the transaction newsgroup
              > > D) contacting customer support
              > >
              > >Tom
              > >
              > >SAF wrote:
              > >
              > >> We recently purchased WLS 6.1 and we have been using the product for the
              > >last few
              > >> months. I am having a problem which I have detailed below. I have provided
              > >as much
              > >> information as possible. If you need additional information, please let
              > >me know.
              > >>
              > >> Server A Config:
              > >> Pentium III, 1000Mhz
              > >> Windows 2000, SP2
              > >> WLS WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
              > >>
              > >> Server B Config:
              > >> SunBlade 100
              > >> Solaris 5.8
              > >> WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
              > >>
              > >> Server A contains a session EJB called GoalManager. This EJB has a method
              > >named cancel().
              > >> The transactional attribute for all methods supported by this bean is
              > >REQUIRED. GoalManager
              > >> uses a transactional data source deployed on Server A named "goal". There
              > >is nothing
              > >> special about this data source aside from the fact that I have enabled
              > >two phase
              > >> commit for it because a previous error was indicating that this was a
              > >required setting
              > >> for the pool. A JMS server exists on Server B. A queue named "emailQueue"
              > >is set
              > >> up as a destination on this JMS server. I also have a MDB on Server B
              > >that listens
              > >> for messages on this queue. When a message is received, the MDB's onMessage()
              > >method
              > >> extracts some properties from the message and sends an email to the specified
              > >recipient
              > >> in the message. I have confirmed that this queue and MDB are working properly
              > >because
              > >> I ran a small test program from the command prompt which creates a message
              > >and sends
              > >> it to the queue on Server B. The MDB gets the message and sends the email
              > >to the
              > >> correct recipient, so I am sure there are no misconfigurations on the
              > >server.
              > >>
              > >> The problem is as follows: The cancel() method in the GoalManager EJB
              > >on Server A
              > >> performs some database work. If no exceptions are raised, the last task
              > >in the method
              > >> attempts to access the queue on Server B and send a message to the queue.
              > >Here is
              > >> the code that I am using to access the queue:
              > >>
              > >> QueueConnectionFactory queueFactory = (QueueConnectionFactory)context.lookup(
              > >"javax.jms.QueueConnectionFactory");
              > >> QueueConnection queueConnection = queueFactory.createQueueConnection();
              > >> Queue queue = (Queue)context.lookup( "emailQueue");
              > >> QueueSession queueSession = queueConnection.createQueueSession( false,
              > >Session.AUTO_ACKNOWLEDGE);
              > >> QueueSender queueSender = queueSession.createSender( queue);
              > >>
              > >> The cancel() method executes without error, but when the EJB container
              > >on Server
              > >> A attempts to commit the transaction at the end of the cancel() method,
              > >I am receiving
              > >> the following error on Server A's log:
              > >>
              > >> <Error> <EJB> <Exception during commit of transaction Name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
              > >> Xid=0:7c2dda32cf39a36e(6911242),
              > >> Status=Rolled back. [Reason=javax.transaction.xa.XAException],
              > >> numRepliesOwedMe=0,
              > >> numRepliesOwedOthers=0,
              > >> seconds since begin=2,
              > >> seconds left=10,
              > >> ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=server1),
              > >> ServerResourceInfo[JMS_EMailServer_NotDurable]=(state=rolledback,assigned=server1),
              > >> SCInfo[FRX+server1]=(state=rolledback),
              > >> SCInfo[frxnet+wlsvr1]=(state=rolledback),
              > >> properties=({weblogic.transaction.name=[EJB com.frx.emp.go.ejb.session.goal.GoalManagerBean.cancelGoal(com.frx.emp.entity.Employee,com.frx.emp.go.entity.Goal)],
              > >>
              > >> weblogic.jdbc=t3://172.16.200.9:9005}),
              > >> OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=server1+172.16.200.9:9005+FRX+,
              > >> Resources={})],
              > >> CoordinatorURL=server1+172.16.200.9:9005+FRX+): javax.transaction.xa.XAException
              > >> at weblogic.jms.backend.BEXAResource.prepare(BEXAResource.java:853)
              > >> at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:1124)
              > >> at weblogic.transaction.internal.ServerResourceInfo.prepare(ServerResourceInfo.java:370)
              > >> at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:186)
              > >> at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:1822)
              > >> at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1607)
              > >> at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
              > >> at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
              > >> at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
              > >> at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
              > >> at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
              > >> at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
              > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              > >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
              > >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
              > >> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
              > >> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
              > >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >> --------------- nested within: ------------------
              > >> weblogic.transaction.RollbackException: Could not prepare resource 'JMS_EMailServer_NotDurable
              > >> - with nested exception:
              > >> [javax.transaction.xa.XAException]
              > >> at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1475)
              > >> at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
              > >> at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
              > >> at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
              > >> at com.frx.emp.go.ejb.session.goal.GoalManagerBean_e3dvd2_EOImpl.cancelGoal(GoalManagerBean_e3dvd2_EOImpl.java:459)
              > >> at com.frx.emp.go.web.handler.UpdateGoalHandler.handleRequest(UpdateGoalHandler.java:55)
              > >> at com.frx.emp.web.mvc.HandlerMappedController.service(HandlerMappedController.java:115)
              > >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              > >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
              > >> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
              > >> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
              > >> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
              > >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >>
              > >> Just a quick note, I tried to change the following line to specify a "transacted"
              > >> JMS session by passing "true" to the statement below. When I tested this,
              > >the cancel()
              > >> method raised no exceptions, but the MDB on Server B is never invoked
              > >and the email
              > >> is never sent. Strange.
              > >>
              > >> QueueSession queueSession = queueConnection.createQueueSession( true,
              > >Session.AUTO_ACKNOWLEDGE);
              > >>
              > >> If you need more info, let me know. I thank you for your help.
              > >
              

  • Queue problem ?

    I am working on IDOC-XI-FIle scenario.
    I see IDOC in IDX5 but file is not created.
    SXMB_MONI has a status of 'Scheduled for outbound status'. When I dbl-click the message to view the message, I get empty screens (no message details are seen). But If I go to RWB and click on message details,
    (status is waiting), I do see the message XML details (for the same message ID).
    Queue status on sxmb_moni line has status of 'Stopped'.
    SMQ2 shows status of 'SYSFAIL' for XBT0___000.
    SMQR has scheduler status of 'INACTIV' and all queue have type field eq 'R'.(so all of them are registered).
    Though I do not see XBTO* in the list !!!!
    ANy ideas what is happening ?
    -Thanks
    Bhaven

    They were active and registered.
    But I am still having problem to create the file.
    It is a very simple mapping and sxmb_moni is giving error in the mapping step. I copied the XML data and map works perfect in IR.
    If I remove the map from interface determination, file is created.
    I also did a IDOC-IDOC map and it still gives the error. Any ideas ?
    Error in sxmb_moni is :
    Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

  • BPM Queue problem

    Hi there, i have a BPM with a Block step that has an infinite loop and collects delivery idocs, i have an exception set to 2 minutes or 500 idocs, basically when i send more than 500 idocs or it takes more than 2 minutes the first group is processed perfectly, but the remaining idocs are stuck on a queue visible under the smq2 with the status READY, does anybody has an idea of what could be the problem?,
    Best Regards,
    Roberto.

    Hi there,
    i cannot see any errors, i do have a correlation active by some region ID, but my test involves only delveries of 1 region, i don't know what could be wrong about the correlation, in addition the bpm steps goes as follow:
    - infinite loop with a receiver step inside a block step with a timeout exception
    - after that i transform those collected messages into 1
    - synchronous call to a 3rd party via webservice
    - send back the response to ECC
    Roberto.

  • Multiple Queue problem

    Hi,
    I had created 3 Queue between two database.
    Source : Oracle 8.1.7 and
    Target is 9.2
    All the three queues are independent except for the dblink btw source and target.
    While testing the fail over,we are bouncing the database at the target side and restarting it.
    Now if there are messages pending for propagation in all the three queue tables only one is getting propagated remaining message are not getting propagated at all.
    I had tested the same with a single queue it works fine. Problem starts only when there are more then one queue.
    Any help on this will be appreciated.

    I found the solution, I had defined a private database like, i just replaced it with a public link. Everything seems to be working fine.

  • PI Queues - problem

    Hi Experts,
       I am working on PI - ABAP Proxy to JDBC Scenario. The database is SQL Server on the legacy system. The interface was running fine till last week. Now I am getting a problem in the Queues.
    When I checked SMQ2 I got an error like " SQL Error while accessing the database table".
    I checked all permissions on the database table and everything is fine.
    I tried registering and activating the queues. But still the error persists.
    What could be the problem for this.
    Thanks
    Ashok

    Hi,
    Have you checked these two threads....give the same solution though:)
    "SQL error in the database when accessing a table "error
    Inbound-Queue SYSFAIL: SQL error in the database when accessing a table
    Regards,
    Abhishek

  • Queues Problem

    Hi Friends,
    I am facing a problem in Production server Related to Queus.I am sending employee information from oracle systems to sap system.I have used sender as JDBC adapter and Reciver as Inbound Proxy.I am sending 10000 above records.When i run the interface it surct in R/3 sever in SMQ2.The queue status in RUNNING and text is Trasaction is executing.After i activate the queue,it went after 30M.I did all the configuaration related to Queues.But problem is not resolved.So,pls help on this.
    Thanks
    Ravi

    Hi Ravi,
    Instead of sending thousands of messages at a time, send bit by bit like 500 msgs at a time like that, then performanc is High as well as we don't face this type of problems.
    Check this links
    /people/udo.paltzer/blog/2008/11/03/real-life-customer-examples-for-high-volume-scenarios-with-sap-netweaver-process-integration
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00982670-748c-2a10-3985-cdd42fb43e50?quicklink=index&overridelayout=true
    or you can use message packaging
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a9447c?quicklink=index&overridelayout=true
    Regards
    Ramesh

Maybe you are looking for