Transaction Debugging

Hi,
    While trying to post some data in any sap transaction you are getting an error message issued by sap. How can you quickly debug and get to the point where the error message is being issued?

When you get the short dump just press the DEBUGGER button on the screen. It will take you to the code where error occurs. place a breakpoint there and re execute the Tcode. Now you can check the value.
Regards,
Amit
Reward all helpful replies.

Similar Messages

  • Getting "JTA transaction is not present" error while updating db table.

    Hi All,
    In one of my BPEL process, In a loop, I am updating value of database column Flag from 0 to 1. It was working fine in dev environment, but failed in Prod with below errors, Can Any one suggest on this.
    There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
    OPMN logs:
    <2010-05-05 01:56:49,395> <ERROR> <gemptp.collaxa.cube.engine> The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Thanks in advance.

    I can envisage this happening only in a case where the update is taking a longer time than the value of JTA transaction timeout.
    Is this happening for all BPEL instances or some of them get thru succesfully ?
    Are you EVER updating that particular row of your table ( before/after) ?
    -Shishir

  • Debug.log is created

    When ever we create a form a debug.log is created and there is nothing in the file.
    If we delete it then the logo in the dynamic form disappears.
    Can anyone say why its formed and what is the use of this.
    Thanks,
    Anusha

    Hi Sudarshan,
    Please refer to the following link:
    *[How to Get the R12 Trace and FND Debug File / FND Log|https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=458371.1]*
    *[How to Generate Receiving Transaction Debug Statements in 11.5.10 and R12|https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=299497.1]*
    Thanks,
    Anchorage :)

  • JTA transaction is not present or the transaction is not in active state

    Hi,
    I am trying to execute an asynchronous bpel process. the bpel process has 5 OSB calls and is taking approximately 100 seconds for completion. The OSB calls in the BPEL are taking 90 seconds for completion. In the end of the BPEL process, after completion I get the following error:
    [2010/07/22 01:56:44] BPEL process instance "1220007" completed
    [2010/07/22 01:56:44] There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1,220,007". The reason is The execution of this instance "1220007" for process "BPELProcess1" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
    We do not want to increase the transaction-timeout properties in the server in the Transaction-manager.xml or in the orion-ejb-jar.xml since we have other projects with synchronous processes running in the same server.
    Can anybody please suggest a workaround to overcome this issue apart from increasing the transaction-timeout?

    Hi 783703,
    As Sridhar suggested for your problem you have to set transaction-time out in j2ee/home/config/transaction-manager.xml.
    If you use Idempotent as false for your partnerlinks, BPEL PM will store the status till that invoke(Proof that this invoke gets executed).
    So better to go for increasing the time instead of going for idempotent as it has some side effects.
    And coming to dehydration ....Ideally performance will be more if there are no much dehydration poitns in our process. But for some scenarios it is better to have dehydration(ex: we can know the status of the process...etc)
    Dehydration store will not get cleared after completion of the process. Here dehydration means ....it will store these dtails in tables(like Cube_instance,cube_scope...etc).
    Regards
    PavanKumar.M

  • Error handling via CatchAll and JTA transaction error.

    Hi
    soa 10.1.3.5.0
    I have created a test BPEL process where i am updating already completed Human task. I know it's wrong and i am doing it purposely to test error handling mechanism.
    In the same BPEL I added a Catch all handler hoping that this will catch the error and will let me complete the process.
    However BPEL is failing in the Catch All scope with lovely error: JTA transaction is not present or the transaction is not in active state.
    Does anybody know how and why humantask update activity suddenly changes jta transaction state? Any thoughts of how i can catch the error in the situation i described and process it gracefully?
    Thanks for your help!
    piece from domain.log starting from the place where task service failing to update already completed human task.
    <2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> Invalid action on workflow task.
    <2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> Action OUTCOME_UPDATE on task 11d1def534ea1be0:65540537:141a4173a84:-7fa1 is not valid because of .
    <2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*> Contact oracle support if error is not fixable.
    <2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*>
    <2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3600)
    <2013-10-10 17:01:00,520> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3557)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcomeAndEvaluateRoutingSlip(TaskService.java:1139)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcome(TaskService.java:1006)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskService.updateTaskOutcome(TaskService.java:985)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.ejb.TaskServiceBean.updateTaskOutcome(TaskServiceBean.java:409)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at java.lang.reflect.Method.invoke(Method.java:597)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    <2013-10-10 17:01:00,521> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ThreadState.runAs(ThreadState.java:705)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    <2013-10-10 17:01:00,522> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at TaskServiceBean_LocalProxy_68d4144.updateTaskOutcome(Unknown Source)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.client.TaskServiceLocalClient.updateTaskOutcome(TaskServiceLocalClient.java:678)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskServiceWSIF.updateTaskOutcome(TaskServiceWSIF.java:580)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at java.lang.reflect.Method.invoke(Method.java:597)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.ws.wsif.providers.java.WSIFOperation_Java.executeRequestResponseOperation(WSIFOperation_Java.java:1019)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:480)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:538)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:286)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:832)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:413)
    <2013-10-10 17:01:00,523> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:200)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:4326)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1839)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:77)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:240)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:345)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:6460)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2267)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:185)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:156)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    <2013-10-10 17:01:00,524> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at java.lang.reflect.Method.invoke(Method.java:597)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ThreadState.runAs(ThreadState.java:705)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    <2013-10-10 17:01:00,525> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at ActivityManagerBean_LocalProxy_4bin6i8.expireActivity(Unknown Source)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:150)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>     at java.lang.Thread.run(Thread.java:662)
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Caused by: ORABPEL-30036
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Invalid action on workflow task.
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Action OUTCOME_UPDATE on task 11d1def534ea1be0:65540537:141a4173a84:-7fa1 is not valid because of The task has been completed..
    <2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*> Contact oracle support if error is not fixable.
    <2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*>
    <2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*>     at oracle.bpel.services.workflow.task.impl.TaskService.performPreActionValidation(TaskService.java:3592)
    <2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*>     ... 71 more
    <2013-10-10 17:01:00,562> <ERROR> <services.collaxa.cube.engine> The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    <2013-10-10 17:01:00,571> <WARN> <services.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Failed due to unhandled bpel fault.
    <2013-10-10 17:01:00,584> <ERROR> <services.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
    ORABPEL-02182
    JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "390,003". The reason is The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
        at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java:6176)
        at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:6482)
        at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2267)
        at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:185)
        at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:156)
        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)
        at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
        at com.evermind.server.ThreadState.runAs(ThreadState.java:705)
        at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
        at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
        at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
        at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
        at ActivityManagerBean_LocalProxy_4bin6i8.expireActivity(Unknown Source)
        at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
        at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:150)
        at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
    <2013-10-10 17:01:00,585> <ERROR> <services.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> Not fatal connection error ... not retrying: class com.collaxa.cube.engine.UnhandledFaultException: Failed due to unhandled bpel fault.
    <2013-10-10 17:01:00,593> <ERROR> <services.collaxa.cube.engine.dispatch> <BaseDispatchTask::run> Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "390,003". The reason is The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
    ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "390,003". The reason is The execution of this instance "390003" for process "MY_BPEL_PROCESS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
        at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:226)
        at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)

    If you look at the error, it suggests that the action you are performing is invalid.That is you cannot update human task which has been already completed. Thats why you are getting that "JTA transaction not active error". Since your human task has already been completed, it is not able to update it again.
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Caused by: ORABPEL-30036
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*>
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Invalid action on workflow task.
    <2013-10-10 17:01:00,526> <ERROR> <services.collaxa.cube.services> <*::*> Action OUTCOME_UPDATE on task 11d1def534ea1be0:65540537:141a4173a84:-7fa1 is not valid because of The task has been completed..
    <2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*> Contact oracle support if error is not fixable.
    <2013-10-10 17:01:00,527> <ERROR> <services.collaxa.cube.services> <*::*>
    May be you can try some other usecase ? Also could you let me know whether you are getting this error in logs only or in your composite instance as well. I mean whether the instance gets successfully terminated or completed ??
    Regards,
    Karan

  • MII 12.1.5 problem: XML-Doc not initialized in second transaction call

    (Sorry- I don't know why the lines are not seperated as in my input text...)
    Hello!
    We are migrating our projects from MII 12.5 to 12.1.5(Build 99).
    Most of the problems we found last year during our 12.1 rampup tests are fixed now.
    We are very happy about the improved expression parser- it now finds all syntax errors which are ignored in 12.0 (like missing parenthesis).
    The new tracing options make is easy to remove such errors.
    We found some small problems but this problem ist not easy to see and the result are some hundred wrong SAP postings:
    In a called transaction we have a XML-Doc action block  which manually configured fields.
    Then we adds rows to this document using the ROW-action block.
    Note: In the calling main transaction the option "reload transaction after each execution" is UNchecked (the default)
    This works fine for the first call of this transaction.
    The problems starts with the second call.
    Some initalization for the XML-Doc ist not executed (see trace below)
    VERY BAD: the ROW-actions to fill the document are executed WITHOUT errors!
    Result: an EMPTY XML-Doc!
    The solution is to check the option "reload transaction after each execution" in the Transaction call action.
    In MII 12.0 the XML-Doc was initalized and filled correctly for both calling options.
    Questions:
    - Is this a bug or a known behaviour?
      During the rampup test we found some problems with local variables and discussed this with SAP (Mr Schuette).
      what I remeber: with the unchecked option the local transaction variables should keep the old values of the last call -
      but XML-Docs should be initialzed always. The big problem is that the ROW action don't raise an error. 
    - Should the option "reload transaction after each execution" be checked as default?  
    - Are there performance differences for both options?
    Best regards,
    Roger Zuehlsdorf
    Trace output:
    ==========================================================
    FIRST CALL of Sub-Transaction
    [DEBUG] [TESTSUB1] Loading action: Document_0, type: IlluminatorDocument
    [DEBUG] [TESTSUB1] [Sequence]: Started sequence execution
    [DEBUG] [TESTSUB1] [Document_0]: Started action execution
    [DEBUG] [TESTSUB1] [Document_0]: Type: IlluminatorDocument, Description:
    [DEBUG] [TESTSUB1] [Document_0]: [Initializing Action][Initializing Parameters: [Document_0.EndDate = Document_0.EndDate=[timestamp:2010-08-23T12:58:51]][Document_0.StartDate = Document_0.StartDate=[timestamp:2010-08-23T12:58:51]][Document_0.Output = Document_0.Output=[xml:<?xml version="1.0" encoding="UTF-8"?>
    <Rowsets DateCreated="2010-08-23T16:09:59" EndDate="2010-08-23T12:58:51" StartDate="2010-08-23T12:58:51" Version="12.1.5 Build(99)">
    <Rowset>
    <Columns>
    <Column Description="" MaxRange="1" MinRange="0" Name="TESTTEXT" SQLDataType="1" SourceColumn="TESTTEXT"/>
    </Columns>
    <Row>
    <TESTTEXT>STRING</TESTTEXT>
    </Row>
    </Rowset>
    </Rowsets>]][Document_0.ColumnSpecifications = Document_0.ColumnSpecifications=[xml:<?xml version="1.0" encoding="UTF-8"?>
    <ColumnSpecifications>
    <ContextItem>
    <Name>TESTTEXT</Name>
    <Description/>
    <MinRange>0</MinRange>
    <MaxRange>1</MaxRange>
    <Value xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="string">STRING</Value>
    <ReadOnly>false</ReadOnly>
    </ContextItem>
    </ColumnSpecifications>]]]
    [DEBUG] [TESTSUB1] [Document_0]: Resolving Input Links
    [DEBUG] [TESTSUB1] Action parameter creating time [ <1 ms]
    [DEBUG] [TESTSUB1] Entering action 'Document_0' implementation.
    [DEBUG] [TESTSUB1] Exiting action 'Document_0' implementation
    [DEBUG] [TESTSUB1] [Document_0]: Resolving Output Links
    [DEBUG] [TESTSUB1] [Document_0]: Finished[ <1 ms] Succeeded: true
    Add Row***
    [DEBUG] [TESTSUB1] [Row_0]: Started action execution
    [DEBUG] [TESTSUB1] [Row_0]: Type: IlluminatorRow, Description:
    [DEBUG] [TESTSUB1] [Row_0]: [Initializing Action][Initializing Parameters: [Row_0.IlluminatorDocument = Row_0.IlluminatorDocument=[string:Document_0.Output]]]
    [DEBUG] [TESTSUB1] [Row_0]: Resolving Input Links
    [DEBUG] [TESTSUB1] [Row_0]: Link Stats: Row_0.TESTTEXT, Type [Assign], Time [ <1 ms], Expression: "xxxxxx xTHIS IS MY TEXT xxxxxxxxx "
    [DEBUG] [TESTSUB1] Action parameter creating time [ <1 ms]
    [DEBUG] [TESTSUB1] Entering action 'Row_0' implementation.
    [DEBUG] [TESTSUB1] Exiting action 'Row_0' implementation
    [DEBUG] [TESTSUB1] [Row_0]: Resolving Output Links
    [DEBUG] [TESTSUB1] [Row_0]: Finished[ <1 ms] Succeeded: true
    >>>> Result  OK, Teststring is added to Document_0
    [INFO] [TESTSUB1] [Tracer_0]Exit SUB: TESTTEXT in XML: <?xml version="1.0" encoding="UTF-8"?>
    <Rowsets DateCreated="2010-08-23T16:14:15" EndDate="2010-08-23T12:58:51" StartDate="2010-08-23T12:58:51" Version="12.1.5 Build(99)">
    <Rowset>
    <Columns>
    <Column Description="" MaxRange="1" MinRange="0" Name="TESTTEXT" SQLDataType="1" SourceColumn="TESTTEXT"/>
    </Columns>
    <Row>
    <TESTTEXT>xxxxxx xTHIS IS MY TEXT xxxxxxxxx </TESTTEXT>
    </Row>
    </Rowset>
    </Rowsets>
    ===============================================================================
    SECOND CALL of Sub-Transaction => XML-Doc NOT initalized!?
    [DEBUG] Entering action 'Transaction_Call_0' implementation.
    [DEBUG] [TESTSUB1] [Sequence]: Started sequence execution
    [DEBUG] [TESTSUB1] [Document_0]: Started action execution
    [DEBUG] [TESTSUB1] [Document_0]: Type: IlluminatorDocument, Description:
    [DEBUG] [TESTSUB1] [Document_0]: [Initializing Action][Initializing Parameters: ]
    [DEBUG] [TESTSUB1] [Document_0]: Resolving Input Links
    [DEBUG] [TESTSUB1] Action parameter creating time [ <1 ms]
    [DEBUG] [TESTSUB1] Entering action 'Document_0' implementation.
    [DEBUG] [TESTSUB1] Exiting action 'Document_0' implementation
    [DEBUG] [TESTSUB1] [Document_0]: Resolving Output Links
    [DEBUG] [TESTSUB1] [Document_0]: Finished[ <1 ms] Succeeded: true
    Add Row***  =>  NO error message!?
    [DEBUG] [TESTSUB1] [Row_0]: Started action execution
    [DEBUG] [TESTSUB1] [Row_0]: Type: IlluminatorRow, Description:
    [DEBUG] [TESTSUB1] [Row_0]: [Initializing Action][Initializing Parameters: ]
    [DEBUG] [TESTSUB1] [Row_0]: Resolving Input Links
    [DEBUG] [TESTSUB1] [Row_0]: Link Stats: Row_0.TESTTEXT, Type [Assign], Time [ <1 ms], Expression: "xxxxxx xTHIS IS MY TEXT xxxxxxxxx "
    [DEBUG] [TESTSUB1] Action parameter creating time [ <1 ms]
    [DEBUG] [TESTSUB1] Entering action 'Row_0' implementation.
    [DEBUG] [TESTSUB1] Exiting action 'Row_0' implementation
    [DEBUG] [TESTSUB1] [Row_0]: Resolving Output Links
    [DEBUG] [TESTSUB1] [Row_0]: Finished[ <1 ms] Succeeded: true
    >>>>  Result=> PROBLEM !??? Document_0 is empty:
    [INFO] [TESTSUB1] [Tracer_0]Exit SUB: TESTTEXT in XML: <?xml version="1.0" encoding="UTF-8"?>
    <Rowsets DateCreated="2010-08-23T16:14:15" EndDate="2010-08-23T12:58:51" StartDate="2010-08-23T12:58:51" Version="12.1.5 Build(99)">
    <Rowset>
    <Columns>
    <Column Description="" MaxRange="1" MinRange="0" Name="TESTTEXT" SQLDataType="1" SourceColumn="TESTTEXT"/>
    </Columns>
    </Rowset>
    </Rowsets>
    ===================================================================================
    Edited by: Roger Zuehlsdorf on Aug 24, 2010 4:51 PM

    Hi.
    It is very hard to read your description, but have a look at SP6 patch 2. This contains a fix for initialising of XML documents in transactions. I am not sure weather that is your problem but have a look.
    BR
    Poul.

  • Database adapter - table related by foreign key - not picking

    Hi All,
    we have a Invoke which picks data from database by using the query feature(not polling) of db adapter.
    we are picking data from multiple tables.
    there is foreign key relation between tables,which we have defined at the db adapter.
    Parent - > child 1
    > child 2 > child 3
    > child 4 > child 5
    So we have a case where parent has 3 rows but children tabls have 3000+.
    This error is happening in such cases.
    Please let me know.
    <2009-08-06 16:58:54,833> <ERROR> <default.collaxa.cube.engine> The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    <2009-08-06 16:58:54,842> <WARN> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Failed due to unhandled bpel fault.
    <2009-08-06 16:58:54,852> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
    ORABPEL-02182
    JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "90,045". The reason is The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
         at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java:5514)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5799)
         at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2086)
         at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:174)
         at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
         at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
         at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
         at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at ActivityManagerBean_LocalProxy_4bin6i8.expireActivity(Unknown Source)
         at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
         at java.lang.Thread.run(Thread.java:595)
    <2009-08-06 16:58:54,853> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> Not fatal connection error ... not retrying: class com.collaxa.cube.engine.UnhandledFaultException: Failed due to unhandled bpel fault.
    <2009-08-06 16:58:54,854> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseDispatchTask::run> Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "90,045". The reason is The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
    ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "90,045". The reason is The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:206)
         at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
         at java.lang.Thread.run(Thread.java:595)

    Also for above issue , we increased the timeout in transaction manager
    transaction-timeout and syncMaxWaitTime properties as follows:
    Property     File Location     This Value Must Be...     Example
    transaction-timeout     SOA_Oracle_Home\j2ee\home\config\transaction-manager.xml     Larger than the transaction-timeout value in orion-ejb-jar.xml and the syncMaxWaitTime value.     7200
    transaction-timeout     SOA_Oracle_Home\j2ee\home\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml     Less than the transaction-timeout value in transaction-manager.xml.
    Note: You must set all transaction-timeout properties that display in this file.     3600
    syncMaxWaitTime     SOA_Oracle_Home\bpel\domains\domain_name\config\domain.xml
    where domain_name is the name of the domain to which you are deploying.     Less than the transaction-timeout value in orion-ejb-jar.xml.     240
    2.     
    The above refernece was useful in resolcing our issue.
    Regards
    Arc

  • SOA Suite 10.1.3.4 loses instances in the BPEL console

    Hello,
    One of my BPEL processes loses instnaces in the BPEL console.
    OS: AIX 5.3 oslevel –s:5300-04-02
    SOA Suite 10.1.3.4
    I feel I hit the same problem as this thread, process is supposed to be in a jta transaction
    But I have set following 3 values (all in seconds), and I still have the problem. The SYNC call is to query the Oracle EBS PO by PO NO, and get its po lines, line shipments, and shipment distributions by Oracle Database Adapter. If my PO just had one line, the process instance can be seen in the console, otherwise it won't, but all these instances are finished, because in the end the process will enqueue a message into a queue. And I can see all these messages there. Anyone can help? Thanks!
    $ORACLE_HOME/j2ee/oc4j_soa/config/transaction-manager.xml
    transaction-timeout="240"
    $ORACLE_HOME/j2ee/oc4j_soa/application-deployments/orabpel/ejb_ob_engine/orion-ejb-jar.xml
    transaction-timeout="180"
    $ORACLE_HOME/bpel/domains/default/config/domain.xml
    <property id="syncMaxWaitTime">
    <name>Delivery result receiver maximum wait time</name>
    <value>600</value>
    -------------- Error messages ----------------
    <2009-04-02 11:40:03,319> <ERROR> <default.collaxa.cube.engine> The execution of this instance "40002" for process "PROEBSMsgToB2B" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    <2009-04-02 11:40:03,324> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Scope not found.
    The scope "BpPrc0.1" has not been defined in the current instance.
    ORABPEL-02094
    Scope not found.
    The scope "BpPrc0.1" has not been defined in the current instance.
    Regards,
    Kerr
    Edited by: Kerrs on 2/04/2009 12:15

    Hi Kerr,
    These are the possible cause to the problem and their solutions:
    Poor performance of the dehydration database If you are using Oracle Lite as dehydration store, please switch to use Oracle 9i or 10g. If Oracle 9i/10g is already in use, check the database parameter 'process' and 'session' to make sure it can handle the expected throughput.
    OC4J has too few available connections to the dehydration database. Increase the maxConnection number of the BPELServerDataSource at the BPEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml (for developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/data-sources.xml (mid-tier installation).
    Size of message is too big Two ways to deal with this problem:
    Increase the transaction timeout at PEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/server.xml (developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/server.xml (mid-tier installation) : http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/app_trblshoot.htm#sthref3957
    Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.
    Having said all that , its always good to be on latest 10.1.3.4 MLR # 5, so that if you have an SR logged with Oracle Support, they will not again ask you to upgrade to latest patch, rather they can focus on getting a fix for you on top of the latest patch itself.
    Hope this helps!
    Cheers
    Anirudh Pucha

  • What is the max file limit for FTP adapter that uses FileIoInteractionSpec

    Hi,
    I know that Oracle provided some new features in 10.1.3.4 using which we can use the file and ftp adapter to move files in a more efficient way
    http://download.oracle.com/docs/cd/E12524_01/relnotes.1013/e12523/adapters.htm#CHDGFAAB
    Essentially it involves modifying the WSDL to use the new InteractionSpec="oracle.tip.adapter.file.outbound.FileIoInteractionSpec"
    Now my question is, what is the file size limit which can be transferred using this.
    I have tried with 20 mb file, it works. But I want to know the upper limit.
    Thanks,
    Amit

    Tried with 31 mb file.
    It successfully delivers the file but....
    The instance never completes successfully in the BPEL Console. If I open the audit tab, it shows the following message
    There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "7,200,001". The reason is The execution of this instance "7200001" for process "TestFTPLimit" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.less
    ORABPEL-02182
    JTA transaction is not present or the transaction is not in active state.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "7,200,001". The reason is The execution of this instance "7200001" for process "TestFTPLimit" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Please consult your administrator regarding this error.
         at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java:5514)
    So does anybody know how to get over this.
    I understand that sync read is a sync operation, so obviously it was going to timeout, as this transfer took around 4 minutes for me. But then, isnt this a bug from Oracle's side

  • ESYU: FAQ - Drop Ship Purchase Orders 2

    Purpose
    RECEIVING: Drop Ship PO's - Release 10.7, 11.0, 11.5.X, r12
    Information in this document applies to any platform.
    Q/A를 통해 Drop Ship Purchase Orders에 대한 이해도를 높인다.
    Solution
    Q8. Configurable Items은 Drop Shipped 가능한가?
    A8: 현재는 Standard Items 만을 Drop Shipped 할 수 있다.
    Configurable Items를 위한 functionality는 향후 release에 포함될 것이다.
    Q9. Operating Units를 교차하여 Drop Ship을 할 수 있는가?
    A9: Release 11i는 현재 이 functionality는 지원하지 않는다.
    Q10. Drop Shipment에서 over/under shipment는 어떻게 처리하는가?
    A10: 만일 drop-ship line의 일부만 ship 되고 나머지 수량에 대해 fulfill을 원하지 않는다면 line을 cancel 한다.
    Over shipments 또한 manual 하게 처리해야 한다.
    만일 supplier가 ordered quantity 보다 많은 수량을 ship 하였다면, customer에게 추가된 수량만큼
    bill을 할 수 있거나 customer에게 추가 수량을 return 해 달라고 요청 할 수 있다.
    Drop-ship Sales Orders와 이에 연계된 purchase requisition/orders 간의 차이를 보고 싶으면
    Drop Ship Order Discrepancy report를 이용한다.
    Q11. Drop Shipment와 Blanket PO's를 사용할 수 있는가?
    A11: Blanket PO는 Drop Shipment와 같이 사용할 수 없다. 왜냐하면 PO는 OM이 PO에게 Drop Ship order가
    생성되었음을 공지시 생성되어야 하기 때문이다.
    Rececipt이 될때(partial or complete) 이 PO는 Drop Ship order와 link 된다.
    Drop Ship lines은 pick release, ship confirm 혹은 INV interface order cycles을 이용하지 않는다.
    Q12. Valid Blanket PO를 생성시 blanket agreement에 있는 item을 위해 drop shipment orders를 base로 하는
    release를 생성하는 것이 가능한가?
    A12: Yes, drop ship orders로부터 자동 혹은 autocreate window를 통하여 release를 생성하는 것은 가능하다.
    만일 drop ship requisition이 correct blanket information(source)을 가지고 있다면
    1. 요구되는 supplier site에 대한 ASL entry를 setup
    2. Hierachy에 따라 어떤 assigment가 좀 더 알맞은지 결정하고, 요구되는 supplier/site를 가지고 요구되는
    level에 따라 sourcing rule을 정의한다.
    또한 위 supplier/site에 대한 ASL entry가 존재하는지 확인한다.
    Profile option 'PO:Allow Automatic Sourcing' = Yes인 경우 automatic sourcing이 실행되며, creation date와
    document type에 따하 source document가 자동으로 결정될 것이다.
    Q13. Receive 후 Drop Shipment를 cancel 할 수 있는가?
    A13: Oracle Purchasing에 한 번 receipt 한 후에는 Drop Shipment는 cancel 할 수 없다.
    만일 Drop Ship Sales Order line을 cancel 하길 원한다면 cancel을 원하는 line에 대해 receipts은 없는지와
    연계된 requisiton이나 purchase order가 cancel 되어 있는지 확인을 해야 한다.
    Partial Deop Ship receipt에 대한 cancellation은 가능하나 아직 receive 되지 않은 부분에 대해서만 cancel
    할 수 있다.
    만일 모든 수량을 shipped 하지 않은 drop shipment line을 cancel 한다면 order processing은 line을 split 한다.
    첫번째 line은 shipped 한 수량을 포함하고 두 번째 line은 non-shipped 수량을 backorder로 가지며,
    이 두 번째 line(backorder)을 cancel 할 수 있다.
    PO line 수량은 새로운 수량을 반영하기 위해 변경되어져야 한다.
    Q14. Drop Shipment를 위한 debugging tools은 무엇인가?
    A14: 1. Note 133464.1 - Sales Order의 troubleshooting problems을 위해 사용할 있는 diagnostic script를 포함.
    2. Receipt transaction이나 Sales Order issue transaction debugging을 위해 아래 profile options을 set:
    RCV: Processing Mode to Immediate or Batch
    RCV: Debug Mode to Yes
    OM: Debug Level to 5
    INV: Debug Trace to Yes
    INV: Debug level to 10
    TP: INV Transaction processing mode to Background
    - Sys Admin: Concurrent> Program> Define> query up the Receiving Transaction Processor and check the Enable Trace box
    - Deliver Transaction을 위한 receipt을 저장 (Deliver Tranasction을 위한 destination type은 inventory 이어야 함)
    - Receiving Transaction Processor log file, Inventory Transaction Worker log file, trace등을 review
    Q15. Drop Shipment로 부터 생성된 PO의 status와 Import source는 무엇인가?
    A15: PO status는 언제나 approved.
    Import source: Order Entry
    Q16. 관련된 Sales Order Line이 cancelled/closed 된 PO shipment를 receive 할 수 있는가?
    A16: 관련된 Sales Order Line이 cancel 되었거나 closed 되었다면 PO shipment는 receive 할 수 없다.
    이 PO shipment는 cancel 해야 하며, 필요하다면 새로운 Sales Order Line이 생성되어야 한다.
    Reference
    Note 225434.1

    Hi Suda,
    Yes, the purchase orders are created directly from the sales order, so there should be some sort of link between the two I would think.  However, I may be wrong in this line of thinking.
    The UDF would be on the header as our customer puts an entire sales order on only one purchase order.
    Thank you for your quick response.
    Amanda

  • Having issue with OEG (11.1.1.6.1) and OES (11.1.1.5) integration

    Hi,
    I have installed latest OEG release (11.1.1.6) and OES 11.1.1.5, followed the instructions in the OEG and OES integration guide to create a policy that delegates authorization to OES through OES 11g Authorization filter.
    Before testing the OEG policy, I created a OES11g authorization policy on OES Admin Server, and used a simple Java application to invoke authorization decisions successfully. But when testing the OEG policy from Service Explorer, I got the an error, and below is the trace stack:
    DATA     3/19/12 17:49:15.186     trace transaction
    DEBUG     3/19/12 17:49:15.186     add header Host:localhost:8080
    DEBUG     3/19/12 17:49:15.186     add header Authorization:Basic d2VibG9naWM6d2VsY29tZTE=
    DEBUG     3/19/12 17:49:15.186     add header SOAPAction:"http://startvbdotnet.com/web/Add"
    DEBUG     3/19/12 17:49:15.186     add header User-Agent:Gateway
    DEBUG     3/19/12 17:49:15.186     incoming content-length: 344
    DEBUG     3/19/12 17:49:15.186     add header Connection:close
    DEBUG     3/19/12 17:49:15.186     add header X-CorrelationID:Id-854f5ea44f67a9db01190000 1
    DEBUG     3/19/12 17:49:15.186     add header Content-Type:text/xml; charset="utf-8"
    DEBUG     3/19/12 17:49:15.186     Incoming HTTP request: method=POST, host=(unset), port=(unset), path=/, query=(unset), version=1.1
    DATA     3/19/12 17:49:15.186     Firewall resolved uri '/' against '/'
    DATA     3/19/12 17:49:15.186     Firewall failed to resolve uri '/' against '/healthcheck'
    DEBUG     3/19/12 17:49:15.186     using handler at /
    DEBUG     3/19/12 17:49:15.186     Adding MessageListener: com.vordel.circuit.FilterPathTracker@f0f11b8
    DEBUG     3/19/12 17:49:15.186     Adding MessageListener: com.vordel.reporting.rtm.RealtimeMonitoring$1$1@70c7c57c
    DEBUG     3/19/12 17:49:15.187     handle type text/xml with factory class com.vordel.mime.XMLBody$Factory
    DEBUG     3/19/12 17:49:15.187     Adding MessageListener: com.vordel.dwe.http.HTTPMessageListener@5200089
    DEBUG     3/19/12 17:49:15.187     Circuit reference [Global Request Policy] is not enabled - ignoring
    DEBUG     3/19/12 17:49:15.187     Circuit reference [Custom Request Policy] is not enabled - ignoring
    DEBUG     3/19/12 17:49:15.187     Circuit reference [Path Specific Policy] valid and enabled - calling
    DEBUG     3/19/12 17:49:15.188     run circuit "OES11g Authorization "...
    DEBUG     3/19/12 17:49:15.188     run filter [HTTP Basic] {
    DEBUG     3/19/12 17:49:15.188     VordelRepository.checkCredentials: username=weblogic
    DEBUG     3/19/12 17:49:15.188     } = 1, filter [HTTP Basic]
    DEBUG     3/19/12 17:49:15.188     Filter [HTTP Basic] completes in 0 milliseconds.
    DEBUG     3/19/12 17:49:15.188     run filter [11g Authorization] {
    DEBUG     3/19/12 17:49:15.188     creating subject from 'weblogic'
    DEBUG     3/19/12 17:49:15.197     checking 'write' to resource: HelloOESworld/MyResourceType/MyResource
    DEBUG     3/19/12 17:49:15.262     parsing XML body from input stream of type sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream. ContentSource is of type java InputStream
    DATA     3/19/12 17:49:15.263     getting class javax.xml.xpath.XPath with classLoader.loadClass()
    DATA     3/19/12 17:49:15.263     loaded class javax.xml.xpath.XPath
    DATA     3/19/12 17:49:15.263     getting class javax.xml.xpath.XPathConstants with classLoader.loadClass()
    DATA     3/19/12 17:49:15.263     loaded class javax.xml.xpath.XPathConstants
    DATA     3/19/12 17:49:15.263     getting class javax.xml.namespace.QName with classLoader.loadClass()
    DATA     3/19/12 17:49:15.263     loaded class javax.xml.namespace.QName
    DEBUG     3/19/12 17:49:15.277     parsing XML body from input stream of type java.io.FileInputStream. ContentSource is of type java InputStream
    DATA     3/19/12 17:49:15.278     getting class javax.xml.namespace.NamespaceContext with classLoader.loadClass()
    DATA     3/19/12 17:49:15.279     loaded class javax.xml.namespace.NamespaceContext
    DEBUG     3/19/12 17:49:15.744     parsing XML body from input stream of type sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream. ContentSource is of type java InputStream
    DEBUG     3/19/12 17:49:15.774     parsing XML body from input stream of type sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream. ContentSource is of type java InputStream
    DEBUG     3/19/12 17:49:15.845     } = 2, filter [11g Authorization]
    DEBUG     3/19/12 17:49:15.845     Filter [11g Authorization] completes in 657 milliseconds.
    DEBUG     3/19/12 17:49:15.845     ..."OES11g Authorization " complete.
    DATA     3/19/12 17:49:15.846     getting class com.vordel.reporting.rtm.api.MetricTypeRangeCount with classLoader.loadClass()
    DATA     3/19/12 17:49:15.846     loaded class com.vordel.reporting.rtm.api.MetricTypeRangeCount
    DATA     3/19/12 17:49:15.847     getting class java.lang.Throwable with classLoader.loadClass()
    DATA     3/19/12 17:49:15.847     loaded class java.lang.Throwable
    DATA     3/19/12 17:49:15.848     getting class com.vordel.system.NativeOutputStream with classLoader.loadClass()
    DATA     3/19/12 17:49:15.849     loaded class com.vordel.system.NativeOutputStream
    DATA     3/19/12 17:49:15.849     getting class com.vordel.system.NativeOutputStream with classLoader.loadClass()
    DATA     3/19/12 17:49:15.849     loaded class com.vordel.system.NativeOutputStream
    DATA     3/19/12 17:49:15.849     getting class java.io.PrintStream with classLoader.loadClass()
    DATA     3/19/12 17:49:15.849     loaded class java.io.PrintStream
    ERROR     3/19/12 17:49:15.850     java exception running circuit: java.lang.RuntimeException: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:61) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.initCipherService(UpdatePolicySet.java:211) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.<init>(UpdatePolicySet.java:139) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initializeControlledPD(PDPServiceImpl.java:296) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initial(PDPServiceImpl.java:368) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.<init>(PDPServiceImpl.java:268) at oracle.security.jps.az.internal.runtime.provider.PDPServiceProvider.getInstance(PDPServiceProvider.java:89) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:159) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:165) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.<init>(PepRequestFactoryImpl.java:123) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.getPepRequestFactory(PepRequestFactoryImpl.java:113) at com.vordel.circuit.oracle.oeseleveng.OES11GAuthZProcessor.invoke(OES11GAuthZProcessor.java:76) at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154) at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43) at com.vordel.circuit.InvocationEngine.processMessage(InvocationEngine.java:229) at com.vordel.circuit.SyntheticCircuitChainProcessor.invoke(SyntheticCircuitChainProcessor.java:36) at com.vordel.dwe.http.HTTPPlugin.invokeDispose(HTTPPlugin.java:290) at com.vordel.dwe.http.HTTPPlugin.invoke(HTTPPlugin.java:131) Caused by: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.retrieveRawKey(AESCipherImpl.java:140) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.getKey(AESCipherImpl.java:184) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.<init>(AESCipherImpl.java:87) at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:59) ... 21 more
    DEBUG     3/19/12 17:49:15.850     add header Content-Type:text/plain
    DEBUG     3/19/12 17:49:15.850     add header Server:
    DEBUG     3/19/12 17:49:15.850     send prologue: content length -1
    DEBUG     3/19/12 17:49:15.850     peer can do chunking
    DEBUG     3/19/12 17:49:15.850     add header Transfer-Encoding:chunked
    DEBUG     3/19/12 17:49:15.850     reused connection 0x2b72480 1 times
    Am I missing something? Please help.

    Hello,
    I too am facing the same error. The environment details are as follows:
    OS: Win2k8 64 bit
    OEG: 11.1.1.6.1
    OES: 11.1.1.5
    OES Client: 11.1.1.5
    I have also applied the patch 12917515 to OES (both server and client). This patch contains 2 sub-folders [APM and OES]. I have installed the OES sub-folder patch only.
    Steps: I followed the steps as mentioned in OEG-OES 11g integration guide: http://www.oracle.com/technetwork/middleware/id-mgmt/oes11g-integration-guide-1520074.pdf
    Note: Instead of using a HTTP Basic filter, I set the "authentication.subject.id" attribute manually and then call "OES 11g Authorization" filter.
    Issue,
    The following exception is thrown when the authorization filter runs,
    java exception running circuit: java.lang.RuntimeException: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:61) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.initCipherService(UpdatePolicySet.java:211) at oracle.security.jps.az.internal.runtime.pd.receiver.UpdatePolicySet.<init>(UpdatePolicySet.java:139) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initializeControlledPD(PDPServiceImpl.java:296) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.initial(PDPServiceImpl.java:368) at oracle.security.jps.az.internal.runtime.service.PDPServiceImpl.<init>(PDPServiceImpl.java:268) at oracle.security.jps.az.internal.runtime.provider.PDPServiceProvider.getInstance(PDPServiceProvider.java:89) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170) at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:159) at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:165) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.<init>(PepRequestFactoryImpl.java:123) at oracle.security.jps.openaz.pep.PepRequestFactoryImpl.getPepRequestFactory(PepRequestFactoryImpl.java:113) at com.vordel.circuit.oracle.oeseleveng.OES11GAuthZProcessor.invoke(OES11GAuthZProcessor.java:76) at com.vordel.circuit.InvocationEngine.invokeFilter(InvocationEngine.java:154) at com.vordel.circuit.InvocationEngine.invokeCircuit(InvocationEngine.java:43) at com.vordel.circuit.InvocationEngine.processMessage(InvocationEngine.java:229) at com.vordel.circuit.SyntheticCircuitChainProcessor.invoke(SyntheticCircuitChainProcessor.java:36) at com.vordel.dwe.http.HTTPPlugin.invokeDispose(HTTPPlugin.java:290) at com.vordel.dwe.http.HTTPPlugin.invoke(HTTPPlugin.java:131) Caused by: oracle.security.jps.service.policystore.PolicyStoreException: JPS-10619: Failed to initialize cipher for local cache encryption/decryption. at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.retrieveRawKey(AESCipherImpl.java:140) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.getKey(AESCipherImpl.java:184) at oracle.security.jps.az.internal.runtime.encryption.AESCipherImpl.<init>(AESCipherImpl.java:87) at oracle.security.jps.az.internal.runtime.encryption.CipherServiceFactory.getService(CipherServiceFactory.java:59) ... 21 more
    Is there any other patch required to make OEG work with OES 11g ? How to resolve this error ?
    Any help will be greatly appreciated.
    Regards.

  • JMS Request - Response Correlation Not Working

    Hello Experts -
    I am new to OAG and hence seek your expert advice. Following is our use-case scenario:
    1. OAG needs to push a sample XML Message to Weblogic Request JMS Queue. In the Request tab of "Routing to Messaging System filter" I set the CorrelationId
    2. In the response tab wait for a timeout (I set to 600000 secs)
    3. Retrieve Response from the Weblogic Response Queue
    4. Send the Response back to the client
    When i invoke the OAG policy, I am able to post the message to the Request Queue. For my testing purpose, I manually get the correlation id from the request message in the request queue and then populate the same in the response message correlation id field and post the same to the response queue.
    Unfortunately I am not able to see the response back. Below is the log.
    Any help is greatly appreciated.
    Thanks!
    Dibya
    DEBUG   29/Jan/2015:23:38:55.677 [3220]     handle type text/plain with factory class com.vordel.mime.Body$1
    DEBUG   29/Jan/2015:23:38:55.677 [3220]     Added converted message is added to the whiteboard
    DEBUG   29/Jan/2015:23:38:55.677 [3220] } = 1, filter [Request Message on Queue(Set Message)]
    DEBUG   29/Jan/2015:23:38:55.678 [3220] Filter [Request Message on Queue(Set Message)] completes in 1 milliseconds.
    DATA    29/Jan/2015:23:38:55.678 [3220] LogManager logging {
    DATA    29/Jan/2015:23:38:55.678 [3220]     Logging at Success
    DATA    29/Jan/2015:23:38:55.678 [3220]     Calling write log on class com.vordel.log.trace.TraceLogger
    DATA    29/Jan/2015:23:38:55.679 [3220] }
    DEBUG   29/Jan/2015:23:38:55.679 [3220] run filter [Place Message on Weblogic Queue (Messaging system)] {
    DEBUG   29/Jan/2015:23:38:55.893 [2300] start thread 10706770 in set "netsvc threadpool": count=11, busy=10, idle target=4, max=512
    DEBUG   29/Jan/2015:23:38:56.388 [3220]     Set Reply to on a named queue: TokenJMSModule!SMAIPO.ActiveSubscriptionResponse
    DEBUG   29/Jan/2015:23:38:56.389 [3220]     creating consumer from QueueSession
    DEBUG   29/Jan/2015:23:38:56.758 [3220]     cache com.vordel.circuit.jms.JMSProcessor$PoolContextCache@19c45da grows to 3
    DEBUG   29/Jan/2015:23:38:56.759 [3220]     JMSProcessor message ID is: Id-ef18cb542c01000000000000bcac40f9
    DEBUG   29/Jan/2015:23:38:56.760 [3220]     Creating JMS byte message using automime
    DEBUG   29/Jan/2015:23:38:56.760 [3220]     new buffered content factory 10674640
    DEBUG   29/Jan/2015:23:38:56.760 [3220]     buffered content 10674640, size=0/8
    DEBUG   29/Jan/2015:23:38:56.761 [3220]     [10674640] new chunk 10541538 from 10606CC8 to 10606DFE (310)
    DATA    29/Jan/2015:23:38:56.761 [3220]     new content stack 105488F8
    DATA    29/Jan/2015:23:38:56.761 [3220]     push source buffered onto 105488F8
    DEBUG   29/Jan/2015:23:38:56.761 [3220]     Setting reply to named queue
    DEBUG   29/Jan/2015:23:38:56.761 [3220]     setJMSMessageID: Id-ef18cb542c01000000000000bcac40f9
    DEBUG   29/Jan/2015:23:38:56.761 [3220]     setJMSCorrelationID: Id-ef18cb542c01000000000000bcac40f9
    DEBUG   29/Jan/2015:23:38:56.762 [3220]     Calling post JMS creation hook
    DEBUG   29/Jan/2015:23:38:56.762 [3220]     Post JMS creation hook completed
    DEBUG   29/Jan/2015:23:38:56.762 [3220]     Sending JMS message to TokenJMSModule!SMAIPO.ActiveSubscriptionRequest
    DATA    29/Jan/2015:23:38:57.120 [3220]     trace transaction
    DEBUG   29/Jan/2015:23:38:57.121 [3220]     Wait for repsonse ? true
    DEBUG   29/Jan/2015:23:38:57.819 [2300] incoming call on interface localhost:8085 from ::1:63317
    DEBUG   29/Jan/2015:23:38:57.820 [2300] new connection 02F0FB08,  settings source incoming interface (allow 1.1=no, idleTimeout=60000, activeTimeout=60000, contentLength: req=no, res=no)
    DEBUG   29/Jan/2015:23:38:57.820 [2300] push SSL protocol on to connection
    DATA    29/Jan/2015:23:38:57.820 [2300] [SSL_accept, 00006000] before/accept initialization.
    DEBUG   29/Jan/2015:23:38:57.821 [2300] No SSL host name provided, defaulting to certificate: { subject: /CN=instance-1 }.
    DATA    29/Jan/2015:23:38:57.821 [2300] [SSL_accept, 00002110] SSLv3 read client hello A.
    DATA    29/Jan/2015:23:38:57.821 [2300] [SSL_accept, 00002130] SSLv3 write server hello A.
    DATA    29/Jan/2015:23:38:57.823 [2300] [SSL_accept, 000021D0] SSLv3 write change cipher spec A.
    DATA    29/Jan/2015:23:38:57.823 [2300] [SSL_accept, 000021E0] SSLv3 write finished A.
    DATA    29/Jan/2015:23:38:57.823 [2300] [SSL_accept, 00002100] SSLv3 flush data.
    DATA    29/Jan/2015:23:38:57.824 [2300] [SSL_accept, 000021C0] SSLv3 read finished A.
    DEBUG   29/Jan/2015:23:38:57.825 [2300] negotiated SSL cipher "DHE-RSA-AES256-SHA", session 00000000 (reused) peer cert /CN=nodemanager-1
    DATA    29/Jan/2015:23:38:57.825 [2300] client certificate: { subject: /CN=nodemanager-1 }
    DEBUG   29/Jan/2015:23:38:57.826 [30a4] incoming call on interface localhost:8085 from 127.0.0.1:63320
    DATA    29/Jan/2015:23:38:57.826 [2300] rcv 979 from max of 2048: <GET /api/monitoring/metrics/summary?timeline=10m&metricGroupType=Service HTTP/1.1
    Host: localhost:8085
    Accept: application/json
    Accept-Language: en-US,en;q=0.8
    authentication.subject.id: admin
    authentication.subject.role: API Server Operator:API Service Developer:Policy Developer:API Service Administrator:API Server Administrator:Deployer:KPS Administrator
    Authorization: Basic YWRtaW46Y2hhbmdlbWU=
    Cookie: avlastvisit=1411930906; avlastactivity=0; __utma=125953885.1884274842.1414410173.1414410173.1417627152.2; __utmz=125953885.1417627152.2.2.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided); utag_main=_st:1417668298258$ses_id:1417666771075%3Bexp-session; WT_FPC=id=cfc9b752-08a3-4756-8d26-c4ca2d77219f:lv=1417670100029:ss=1417670100029
    Host: localhost:8085
    Referer: https://xx1211000592.global.avaya.com:8090/
    User-Agent: Gateway
    X-Requested-With: XMLHttpRequest
    Connection: close
    X-CorrelationID: Id-f118cb54e204000000000000373fba90 1

    Hi Michael,
    I think the adapter type is for the receiver channel looking at the documentation SAP Library - SAP Exchange Infrastructure
    Have you checked your receiver channel doesn't belong to a party?
    I havent tried this bridge with the http_aae but looks to be problematic according with Michal comment here http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/01/28/generic-pi-async-sync-bridge-configuration-for-any-adapters#comment-454463
    Regards.

  • Query key Date Variable not working

    Hi Folks -
         I am coming across an issue with which some of you might be able to help me. I have a time dependent master data object which I've marked as a datatarget and have created a report on it. I wanted to give the user an option of specifying the key date and hence have created a variable in the query properties for the key date. This variable is of the type SINGLE VALUE, MANDATORY, USER ENTRY and CAN BE CHANGED DURING QUERY NAVIGATION.
         Now my issue is that even though I enter a specific key date, the query is not pulling the records according to the key date. But instead if I use the option of specifying a particular date (instead of a variable in query properties), the query is running fine!!! Can someone please let me know why this is happening? Why is the query working fine when I mention a single constant value but not when I use a variable? Thanks for your help in advance.

    hi
    This clearly shows your variable is not working fine
    So in RSRT transaction debug using your variable
    See in every step whether the variable is working properly
    Assign points if useful
    Thanks
    N Ganesh

  • HKONG: Inter-Organization Transfers의 receive시 "rvtptcontrol failed" Error처리

    PURPOSE
    Inter-Organization Transfers의 receive시 발생하는 "rvtptcontrol failed" Error처리 방법을 기술하고자 함.
    Problem Description
    Inter-Organization Transfers의 receive시 "rvtptcontrol failed" Error 발생.
    debug file :
    [12-JUN-06 09:31:24] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: LOT NOT ENTERED ON PARENT: WMSINB-22155
    [12-JUN-06 09:31:24] INV_RCV_INTEGRATION_PVT: VALIDATE_LOT_SERIAL_INFO: LOT CONTROL FROM ORG: 2 : WMSINB-22161
    [12-JUN-06 09:31:24] INV_RCV_INTEGRATION_PVT: Exitting VALIDATE_LOT_SERIAL_INFO - execution error:2006-06-12 09:12:24:WMSINB-22192
    [12-JUN-06 09:31:24] INV_RCV_INTEGRATION_PVT: STACKED ERROR MESSAGES :
    [12-JUN-06 09:31:24] inv_receiving_transaction: TXN_COMPLETE - Enter txn_complete : 10: 2006-06-12 09:12:24
    Workaround
    N/A
    Solution Description
    1. Patch 4473106 적용
    Update RcvTrxManager.java to version 115.51.115100.4 or higher.
    2. 만약, datafix가 필요하다면 다음 정보들을 수집하여 SR을 등록하여 주시기 바랍니다.
    1.Screenshot of the Shipping Networks between the two orgs:
    Inventory: Setup -> Organizations -> Shipping Networks
    2.Run the statements below and upload the results in excel format with column headings:
    a. select * from rcv_transactions
    where shipment_line_id = &shipment_line_id;
    b. select * from rcv_transactions_interface
    where shipment_line_id = &shipment_line_id;
    c. select * from rcv_serials_supply
    where shipment_line_id = &shipment_line_id;
    d. select * from rcv_shipment_headers
    where shipment_line_id = &shipment_line_id;
    e. select * from rcv_lots
    where shipment_line_id = &shipment_line_id;
    3. Run the "Diagnostics: Apps Check" Report using a Purchasing responsibility:
    - Reports > Run
    - Submit a Single Request
    - Name: Diagnostics: Apps Check
    - Parameters: Application 1: Oracle Purchasing
    Application 2: Oracle Inventory
    - Submit the request
    - View > Requests
    Select the Concurrent Request and upload the report output (not the log)
    Reference Documents
    Bug 4473106 - ''RCVTPT CONTROL FAILURE'' ERROR ON RECEIVING IN DIFFERENT UOM FOR LOT ITEM
    Bug 5352266 - DATAFIX: ''RVTPTCONTROL FAILED'' ERROR WHEN ATTEMPTING TO RECEIVE INTRANSIT
    Note 299497.1 - How to Generate Receiving Transaction Debug Statements in 11.5.10

  • How to find error

    hi friends,
    i have a scenario in which, a function module is being called from an idoc,
    and that function module throws an error message when a
    document is not found in a standard table.
    now my work is to go to the place where the error is bieng triggered,
    and split the error into two more specific errors, as to what went wrong.
    how do i reach this place,
    this is what i did,
    went to se37, entered the function modulename.
    got into the code, and went line by line, found that,
    an internal table is made and passed on to a bapi,
    i went into the bapi too, could not trace out at what point the error is bieng triggered.
    can some intelligent people, give me some tricks.
    thank you.

    If you have message id and message number then do create watch point,it will take you exactly that point.
    suppose your case is Inbound IDOC ,use WE19 Transaction,debug the idoc.
    now create watch point,use variable as message id ,value as message number
    use compare is =
    Then it will take you exact point.
    other way ,goto SE91 Transaction,use message id and message number,keep the cursor on message number and do where used list.
    if it shows program name ,then keep the break point all the area
    Thanks
    Seshu

Maybe you are looking for

  • Error in accessing the start Page

    Hi , I have genereated the URL for accessing the Erecruitment Pages of the Recruiter. After entering the user name and password in the login page an error message is being displayed saying that " An internal error had occured, Pl try again". Can some

  • MRIO Before Goods receipt

    Hi, I am facing a problem, some of goods we need to pay to vendor before goods delivered to us, I know that we can do the MIRO before goods receipt. But I would like to know any influence if I use this approach? Thanks!

  • TAXINN & TAXINJ with example ..?

    Hi all can anybody explain me clearly step by step about TAINN & TAXINJ..? Please assume we are going to implement SAP in one client, wht is the first step to choose TAX procedure..? And wht are the detailed procedure to be followed for this .. Pleas

  • Itunes xml file corruption

    I'd like to ask the community if anyone else is having trouble with corruption of their iTunes XML library file? Back on October 20th, my iTunes library completely imploded: roughly one third of all songs stopped playing, all my Digital Copy movies r

  • Unable to open *any* picture files in Photoshop CC

    I cannot seem to open any picture files in Photoshop CC. It doesn't seem to matter what file type it is. .jpg .gif .png  no file will open.  They open just fine in Illustrator but Photoshop can't seem to find them. I've tried modifying what program "