Exception handling branch not executing in BPM

Hi all,
We have a problem with exception handling in BPMs.
We have created an exception branch in a block and a transformation step in it. However, the branch doesn't get executed in case of exceptions.
Any ideas? Is this a known problem?
Many thanks,
Aldo

Hi VJ,
The exception name can only be selected from a list. There is no chance of mistaking/misspelling in there.
That is fine as it is. I am quite sure about it.
Any other ideas?
I found SAP note 1039330 but we are already on patch 12 and that correction was released on patch 12.
Thanks, regards,
Aldo

Similar Messages

Org.hibernate.exception.GenericJDBCException: could not execute query

while executing sql statements with hibernate oracle this type of errors
org.hibernate.exception.GenericJDBCException: could not execute query
ava.sql.SQLException: ORA-01001: cursore non valido can any one suggest
a solution for this.
Thanks

This is likely due to a commit/rollback being executed after the statement has been executed but befofre the result set has been processed by the application. In TimesTen, unlike Oracle, commit/rollback closes all open cursors on the connection. This could be a case of using the wrong Hibernate dialect. Are you using a TimesTen dialect in Hibernate?
Chris

Exception handler is not working

Hi fellas,
My function works fine when the entered username and password are correct. I'm trying to figure out why my exception handler is not displaying the contents of the DBMS_OUTPUT.PUT_LINE when the username or password are not correct. Any ideas?
Thanks,
Mat
VARIABLE g_output VARCHAR2(30)
VARIABLE g_username VARCHAR2(8)
VARIABLE g_password VARCHAR2(8)
VARIABLE g_ck CHAR
BEGIN
:g_username := 'gma1';
:g_password := 'gofy';
:g_ck := 'N';
END;
CREATE OR REPLACE PACKAGE login_pkg IS
FUNCTION log_in_pf
(p_username IN VARCHAR2,
p_password IN VARCHAR2,
p_ck IN OUT CHAR)
RETURN CHAR;
END;
CREATE OR REPLACE PACKAGE BODY login_pkg IS
FUNCTION log_in_pf
(p_username IN VARCHAR2,
p_password IN VARCHAR2,
p_ck IN OUT CHAR)
RETURN CHAR
IS
lv_username_txt bb_shopper.username %TYPE;
lv_password_txt bb_shopper.password%TYPE;
BEGIN
SELECT username, password
INTO lv_username_txt, lv_password_txt
FROM bb_shopper
WHERE username = p_username
AND password = p_password;
IF lv_username_txt||lv_password_txt = p_username||p_password THEN
p_ck := 'Y';
ELSE p_ck := 'N';
END IF;
RETURN p_ck;
EXCEPTION
WHEN NO_DATA_FOUND THEN
DBMS_OUTPUT.PUT_LINE('Invalid username or password');
END log_in_pf;
END;
BEGIN
:g_output := login_pkg.log_in_pf(:g_username, :g_password, :g_ck);
END;
BEGIN
ERROR at line 1:
ORA-06503: PL/SQL: Function returned without value
ORA-06512: at "SCOTT.LOGIN_PKG", line 23
ORA-06512: at line 2
Edited by: Mathew2 on Jul 20, 2009 3:20 AM

Change your package defination too::
CREATE OR REPLACE PACKAGE BODY login_pkg
IS
   FUNCTION log_in_pf (
      p_username   IN       VARCHAR2,
      p_password   IN       VARCHAR2,
      p_ck         IN OUT   CHAR
      RETURN CHAR
   IS
      lv_username_txt   bb_shopper.username%TYPE;
      lv_password_txt   bb_shopper.PASSWORD%TYPE;
   BEGIN
      SELECT username, PASSWORD
        INTO lv_username_txt, lv_password_txt
        FROM bb_shopper
       WHERE username = p_username AND PASSWORD = p_password;
      IF lv_username_txt || lv_password_txt = p_username || p_password
      THEN
         p_ck := 'Y';
      ELSE
         p_ck := 'N';
      END IF;
      RETURN p_ck;
   EXCEPTION
      WHEN NO_DATA_FOUND
      THEN
         DBMS_OUTPUT.put_line ('Invalid username or password');
        return 'N' ;   --Added return statement as also mentioned in other post.
   END log_in_pf;
END;

CcBPM Steps in exception branch not executed

Hi,
I have different blocks with transformations and sending steps in a integration process. Each block has a defined exception branch to handle its corresponding exception type.
However, when a mapping or receiver/interface determination error occurs, none of the steps (throw alert and send asynchr. message to logging) defined in the exception branch are executed... I can see from the pe monitoring that the process jumps into the exception branch but the steps are not being executed.
What could be the reason behind this situation?
Many thanks,
Roberto
PS: Alerts has been properly defined and we are receiving alerts from other events aoutside this integration process.

Hi,
just to check - modify your BPM process and in the exception branch have to control step to generate alert as the first step.........moreover send a fixed msg as an alert and see if your alert is getting generated.........moreover in your alert category for bpm, you should check the Dynamic text option to dynamically send alert msg from bpm..........
then re-run your scenario and from PE monitoring see if your exception branch was called and your alert generated..........if your alert got generated now, then either the container operation is having some issue or the alert step is having some issue.
Regards,
Rajeev Gupta

Exception handling is not working in GCC compile shared object

Hello,
I am facing very strange issue on Solaris x86_64 platform with C++ code compiled usging gcc.3.4.3.
I have compiled shared object that load into web server process space while initialization. Whenever any exception generate in code base, it is not being caught by exception handler. Even though exception handlers are there. Same code is working fine since long time but on Solaris x86, Sparc arch, Linux platform
With Dbx, I am getting following stack trace.
Stack trace is
dbx: internal error: reference through NULL pointer at line 973 in file symbol.cc
[1] 0x11335(0x1, 0x1, 0x474e5543432b2b00, 0x59cb60, 0xfffffd7fffdff2b0, 0x11335), at 0x11335
---- hidden frames, use 'where -h' to see them all ----
=>[4] __cxa_throw(obj = (nil), tinfo = (nil), dest = (nil), , line 75 in "eh_throw.cc"
[5] OBWebGate_Authent(r = 0xfffffd7fff3fb300), line 86 in "apache.cpp"
[6] ap_run_post_config(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x444624
[7] main(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0x42c39a
I am using following link options.
Compile option is
/usr/sfw/bin/g++ -c -I/scratch/ashishas/view_storage/build/coreid1014/palantir/apache22/solaris-x86_64/include -m64 -fPIC -D_REENTRANT -Wall -g -o apache.o apache.cpp
Link option is
/usr/sfw/bin/g++ -shared -m64 -o apache.so apache.o -lsocket -lnsl -ldl -lpthread -lthread
At line 86, we are just throwing simple exception which have catch handlers in place. Also we do have catch(...) handler as well.
Surpursing things are..same issue didn't observe if we make it as executable.
Issue only comes if this is shared object loaded on webserver. If this is plain shared object, opened by anyother exe, it works fine.
Can someone help me out. This is completly blocking issue for us. Using Solaris Sun Studio compiler is no option as of now.

shared object that load into web server process space
... same issue didn't observe if we make it as executable.When you "inject" your shared object into some other process a well-being of your exception handling depends on that other process.
Mechanics of x64 stack traversing (unwind) performed when you throw the exception is quite complicated,
particularly involving a "nearly-standartized" Unwind interface (say, Unwind_RaiseException).
When we are talking about g++ on Solaris there are two implementations of unwind interface, one in libc and one in libgcc_s.so.
When you g++-compile the executable you get it directly linked with libgcc_s.so and Unwind stuff resolves into libgccs.
When g++-compiled shared object is loaded into non-g++-compiled executable's process _Unwind calls are most likely already resolved into Solaris libc.
Thats why you might see the difference.
Now, what exactly causes this difference can vary, I can only speculate.
All that would not be a problem if _Unwind interface was completely standartized and properly implemented.
However there are two issues currently:
* gcc (libstdc++ in particular) happens to use additional non-standard _Unwind calls which are not present in Solaris libc
naturally, implementation details of Unwind implementation in libc differs to that of libgccs, so when all the standard _Unwind
routines are resolved into Solaris version and one non-standard _Unwind routine is resolved into gcc version you get a problem
(most likely that is what happens with you)
* libc Unwind sometimes is unable to decipher the code generated by gcc.
However that is likely to happen with modern gcc (say, 4.4+) and not that likely with 3.4.3
Btw, you can check your call frame to see where _Unwind calls come from:
where -h -lIf you indeed stomped on "mixed _Unwind" problem then the only chance for you is to play with linker
so it binds Unwind stuff from your library directly into libgccs.
Not tried it myself though.
regards,
__Fedor.

Automated activity not executing in BPM process

Hi All,
We have created a BPM process in NWCE72, and it was executing fine.
When we added an automated activitiy and assigned a Web Service created from a rule and run the process, it is possible to run the process till the automated activity only. The automated activity is throwing error a snapshot of the same pasted belw
If anyone has encountered simllar problem kindly let us know how to overcome.
Lookforward for help in overcoming this problem
Down below it is saying that "You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed. "
=====================================================================================================
An error occurred while executing transition AUTOMATED_ACTIVITY_Determine_Criticality(Token_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{64810061-7973-11df-872e-02004c4f4f50}(Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{4be7da15-7973-11df-b824-02004c4f4f50}(?),1,null,operator,ff12474b71b3fa29a516e53e125eaa18), Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{4be7da15-7973-11df-b824-02004c4f4f50}(null,null,null,false), Context_0_DO_IssueTrackingProcess_2baa0100a79b04782f33bbea2160cdf3{4be7da30-7973-11df-c7a0-02004c4f4f50}(Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{4be7da15-7973-11df-b824-02004c4f4f50}(?),Scope_14_Equipment_Issue_Reporting_2baa0100a79b04782f33bbea2160cdf3{4be7da2f-7973-11df-cc05-02004c4f4f50}(?),1,true,false,null)): com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_Equipment_Issue_Reporting:AUTOMATED_ACTIVITY_Determine_Criticality(
      com.sap.glx.adapter.BPMNAdapter:Token_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3 token,
      com.sap.glx.adapter.BPMNAdapter:Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3 parent,
      com.sap.glx.adapter.internal.ContainerAdapter:Context_0_DO_IssueTrackingProcess_2baa0100a79b04782f33bbea2160cdf3 context_1){
exit=new com.sap.glx.adapter.BPMNAdapter:Exit();
exit:onActivation("E01DFA6EF00BAFC0797011DFB05502004C4F4F50", parent, token);
delete exit;
controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController();
controller:setContext(token);
delete controller;
callscope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_7_Equipment_Issue_Reporting_2baa0100a79b04782f33bbea2160cdf3(parent);
call=new com.sap.glx.adapter.UnifiedConnectivityAdapter:Call_0_Determine_Criticality_2baa0100a79b04782f33bbea2160cdf3(callscope);
ppUsername=token:ppUsername;
ppHash=token:ppHash;
call:setPrincipal(ppHash, ppUsername, token);
request=callscope:instantiate("http://www.sap.com", "#RulesTypes-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet");
mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
data=context_1:getData();
yves_in:setData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", data, "C000F957BEB5AA9E0E98E96A67EE2D06");
yves_out:setData("http://www.sap.com", "$http://www.sap.com:Request-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", request, "8F3954721A11A18DF1A2321F9544700D");
mapper:map("E01DFA6EF00DF9B0797011DFC8A002004C4F4F50_2baa0100a79b04782f33bbea2160cdf3", yves_in, yves_out);
request=yves_out:getData("http://www.sap.com", "$http://www.sap.com:Request-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", "8F3954721A11A18DF1A2321F9544700D");
delete yves_in;
delete yves_out;
delete mapper;
call:setInputData("http://www.sap.com", "$http://www.sap.com:Request-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", request);
response=callscope:instantiate("http://www.sap.com", "#RulesTypes-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet");
call:setOutputData("http://www.sap.com", "$http://www.sap.com:Response-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", response);
call:invoke();
response=call:getOutputData("http://www.sap.com", "$http://www.sap.com:Response-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet");
mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
yves_in:setData("http://www.sap.com", "$http://www.sap.com:Response-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", response, "8F3954721A11A18DF1A2321F9544700D");
data=context_1:getData();
yves_in:setData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", data, "C000F957BEB5AA9E0E98E96A67EE2D06");
bind context_1;
data=context_1:getData();
scope=new com.sap.glx.adapter.internal.TypeRegistry:GenericScope(null, "C000F957BEB5AA9E0E98E96A67EE2D06");
copy=scope:copy(data);
delete scope;
yves_out:setData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", copy, "C000F957BEB5AA9E0E98E96A67EE2D06");
mapper:map("E01DFA6EF0106AB0797011DFBC6D02004C4F4F50_2baa0100a79b04782f33bbea2160cdf3", yves_in, yves_out);
data=yves_out:getData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", "C000F957BEB5AA9E0E98E96A67EE2D06");
context_1:setData(data);
delete yves_in;
delete yves_out;
delete mapper;
delete call;
delete callscope;
token:state=0;
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:68)
at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:138)
at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:126)
at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:121)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:337)
at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:118)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:277)
Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "call:invoke()"
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:796)
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:63)
... 11 more
Caused by: java.lang.RuntimeException: com.sap.glx.adapter.api.AdapterException: com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name b51513b6-379d-4c0b-be2a-a3b13d7fe23b, component name demo.sap.comreportissueprocessdcBPMcomponent, application name demo.sap.com/reportissueprocessdc.
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject$PropagatedCall.run(UnifiedWebServiceCallObject.java:127)
at com.sap.glx.core.login.LoginPersisterProxy$1.run(LoginPersisterProxy.java:76)
at com.sap.glx.core.resource.impl.j2ee.J2EELoginPersisterImpl$1.run(J2EELoginPersisterImpl.java:80)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.glx.core.resource.impl.j2ee.J2EELoginPersisterImpl.invokeAsPropagated(J2EELoginPersisterImpl.java:74)
at com.sap.glx.core.login.LoginPersisterProxy.invokeAsPropagated(LoginPersisterProxy.java:72)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject.invokeWebServiceOperation(UnifiedWebServiceCallObject.java:93)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.invoke(UnifiedWebServiceCallClass.java:174)
at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:528)
at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:245)
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:791)
... 12 more
Caused by: com.sap.glx.adapter.api.AdapterException: com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name b51513b6-379d-4c0b-be2a-a3b13d7fe23b, component name demo.sap.comreportissueprocessdcBPMcomponent, application name demo.sap.com/reportissueprocessdc.
at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:151)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject$PropagatedCall.run(UnifiedWebServiceCallObject.java:125)
... 23 more
Caused by: com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name b51513b6-379d-4c0b-be2a-a3b13d7fe23b, component name demo.sap.comreportissueprocessdcBPMcomponent, application name demo.sap.com/reportissueprocessdc.
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:362)
at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:116)
... 24 more
Caused by: com.sap.engine.interfaces.sca.config.exception.ESBConfigurationException: Configuration not found for application: demo.sap.com/reportissueprocessdc,composite:reportissueprocessdc,component:demo.sap.comreportissueprocessdcBPMcomponent,reference:b51513b6-379d-4c0b-be2a-a3b13d7fe23b,bindingType:WS
at com.sap.esi.esp.service.server.ESPServiceInterfaceImpl.getConfiguration(ESPServiceInterfaceImpl.java:450)
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.initWsdas(WebServiceImplementationInstance.java:193)
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:76)
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:335)
... 25 more
Caused by: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: Configuration not found for application: demo.sap.com/reportissueprocessdc,composite:reportissueprocessdc,component:demo.sap.comreportissueprocessdcBPMcomponent,reference:b51513b6-379d-4c0b-be2a-a3b13d7fe23b,bindingType:WS
at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:276)
at com.sap.esi.esp.service.server.ESPServiceInterfaceImpl.getConfiguration(ESPServiceInterfaceImpl.java:443)
... 28 more
Caused by: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: Configuration not found for application: demo.sap.com/reportissueprocessdc,serviceRefId:reportissueprocessdc_demo.sap.comreportissueprocessdcBPMcomponent_b51513b6-379d-4c0b-be2a-a3b13d7fe23b_WS. Please check the configuration details from the NWA. You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed.
at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:334)
at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:263)
... 29 more
Date: 2010-06-16
Time: 19:17:16:800
Category: com.sap.glx.core.kernel.execution.LeaderWorkerPool
Location: com.sap.glx.core.kernel.execution.LeaderWorkerPool
Application: sap.com/com.sap.glx.process.ear
Thread: Galaxy 340 / Follower Worker
Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
DSR Transaction: c6a0ff48796211dfca1602004c4f4f50
Message ID: com.sap.BPM.core_svc.000047
Session: 0
Transaction:
User: SAP_BPM_Service
Time Zone: +0100
Customer Message Component: BC-BMT-BPM-SRV
DC Name: com.sap.glx.core.svc
Correlation ID: 5164050000004002
DSR Root Context ID: C6A0FF48796211DFCA1602004C4F4F50
DSR Connection: c6a0ff48796211dfca1602004c4f4f50
DSR Counter: 0
Host: dcwwwx11871
System: CE2
Instance: J00
Node: server0
Log ID: 02004C4F4F50039E000000010000162C

Hi,
Your Error Says
You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed. at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration
Procedure to Create Provide System
https://cw.sdn.sap.com/cw/docs/DOC-101203 (From the service where you are consuming)
Procedure to Create and Assign ServiceGroup
While importing the Enterprise Service into Automated Activity it will ask the name of Service Group.Please check what is the Service Group Name and Assign the Service Group to the Provider System by following the Below Procedure.
https://cw.sdn.sap.com/cw/docs/DOC-109461
Thanks
Srikanth

BPM send step not executed in BPM (after Message split)

Hello everybody,
we use BPM:
We have a paralell Block which should send the rows of a multiline element. In SXMB_BPE_MONI the send step is not executed?
Any idea?
Thanks lot, regards Mario

HI,
Go to SXMB_MONI_BPE->and check the workflow log (technical details).and go to SXI_CACHE and check the return code of the Integration Process. It should be zero. If not try to activate the same
If there is no error then go with like this-
Also check the Syntax in Integration Repository with F7. Change the IP and activate it. If there is no syntax errors.
Then reimport the IP into Directory and then test your scenario
Regards,
Moorthy

Exception Handling for Multi Mapping in bpm

Hello,
does anybody know a way of catching an error occured in a multi-mapping used in an integration process.
It seems to me, that when i am using a multi-mapping in an integration process and an error occurs, the message cannot get back to the integration process. In smq2 I can see, that there is the following error:
CX_MERGE_SPLIT
Regards
Günther

The transformation-step is in an block with an exception branch and it is well configured.
When I use a 1 to 1 mapping and an error in the mapping occurs, all is correct. The integration process jumps in to the exception branch and finishes correct. But when use a multi mapping (1 to n; n to 1; n to m) and an error in the mapping occurs, then there is always an error in the bpe inbound queue.
There must be some problem with the split-and-merge program. I think that the split-and-merge program handles the merging of n messages into 1. You can see this when you test a mapping in the integration builder designer. In a multi-mapping there you can see a xml-structure that envelopes the application messages, f. ex.:
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
   <ns0:Message1>
      <myMessage1>data</myMessage1>
   </ns0:Message1>
   <ns0:Message2>
      <myMessage2>data2</myMessage2>
   </ns0:Message2>
</ns0:Messages>

Exception handler activity doesn't execute

I have an exception handler in my bounded task flow but it not always executes when an error is raised by some of the BTF activities.
In my application I'm having a problem with connections closed.
I don't know if the database, the firewall or who is closing connections but sometimes I get an error in the logs "oracle.jbo.JboException: JBO-29000: Se ha obtenido una excepción inesperada: java.sql.SQLRecoverableException, mensaje=Conexión cerrada" translation "oracle.jbo.JboException: JBO-29000: Un unexpected exception has been raised: java.sql.SQLRecoverableException, message=Closed connection".
That is bothering me specially because my task flow continues execution despite of the error. ADF opens the connection and then continues execution. This is fatal because previous updating in the entity objects is lost and the consequence is very bad.
Well, I have tried to insert an exception handler in my task flow in order to capture this errors and then stop execution of the task flow.
Currently, I'm more upset because of task flow continues execution after the connection closed error that for the error itself.
The problem is that sometimes the connection closed appears in the log window but the exception handler is not executed. Sometimes yes, some others no.
In order to test I'm forcing the error manually killing the sessions in the server.
Any help for any of both problems ? (1- BTF continuing execution after this error raising and 2-Why the exception handler doesn't always execute when a java error stack appears in the log window).
Thank you.

this might be caused by a bug I found too causing eventhandlers not to work, the work round in your case would be:
blar blar blar
</variables>
<scope>
<faultHandlers>
blar blar blar
blar blar blar
</sequence>
</scope>
</process>
i.e. what I'm saying is that top level handler don't work since they are ignored by the engine because they are not in a scope. Try it and see....

Exception Handling Problem In BPM

All
I am facing an exception handling problem I am using BPM and , I have caught exception in the transformation step but when there is any data problem in that mapping(mentioned in the transformation)
it is not throwing the exception . is there any option to collect these type of system exception in the bpm and give a alert thru mail
is there any way to collect these type of exception happened in the BPE and raise alert thru generic alert
Thanks
Jayaraman

Hi Jayaraman,
When you say there is any data problem, does that fail the message mapping that you have defined?
If the message mapping used in the tranformation fails, it should raise an exception in the BPM.
Did you test the message mapping using the payload and see if it really fails or not?
Regards,
Ravi Kanth Talagana

Exception Handling in Web Center for UI related Errors not working.

Hi Guys,
I have implemented Error Handling in ADF Application with Custom Model Exception Handler ( which is "CustomExceptionHandler extends DCErrorHandlerImpl") to catch all Model Layer Exception and to customize those error messages.
I have implemented Error Handling in ADF Application with Custom View Exception Handler ( which is "CustomViewErrorHandler extends oracle.adf.view.rich.context.ExceptionHandler";) to catch all View Layer Exception and to customize those error messages.
The design for this is , in Model Custom Exception Handler i find the exception message in "public String getDisplayMessage(BindingContext bindingContext,Exception exception) " method and throw RuntimeException to pass this exception to Custom View Layer Exception , so that i can handle all the exception @ View Layer it self .
In the View Layer Exception Handler i am navigating to specific error page using
String contextPath = ((HttpServletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest()).getContextPath();
ExternalContext ectx = facesContext.getExternalContext();
ectx.redirect.
All these things absolutly working in ADF Application for all the exception ( Model , View ) and i am successfully navigating to error page.
Problem :
When i implement the same thing in Webcenter Application ( Model Custom Exception Handler and View Custom Exception Handler), Model Part is working as expected , but View Custom Exception Handler is not all calling .
i am assuming that ,this View Custom Exception Handler (CustomViewErrorHandler extends oracle.adf.view.rich.context.ExceptionHandler) works only for JSF Life cycle
"Allows frameworks to intercept otherwise unhandled exceptions thrown during the JSF lifecycle. ExceptionHandlers can be registered by adding a service file with a class name at META-INF/services/oracle.adf.view.rich.context.ExceptionHandler." from http://jdevadf.oracle.com/adf-richclient-demo/docs/apidocs/oracle/adf/view/rich/context/ExceptionHandler.html";
As Webcenter Portal uses ADF Life Cycle this Exception Handler is not calling , i am not sure.
if any one has any idea please let me know .
Thanks
Annapareddy Srinivasrao
Edited by: Srinivasrao Annapareddy on May 22, 2013 12:06 PM

i used runtime exception along with the wdwsmodel exception

Handling SOAP Fault messages in BPM

Hi,
My scenario is Sync-Async Bridge involving File to SOAP transformation. I have used BPM as 1 file has many records and each record is required to call the web service synchronously.
In the BPM I have
Receive ---> Transform (1:n multimapping ) -
> Block (Par for Each)
In Block I have Send Sync step to call Web service . I have an exception branch for the send step for catching Fault message that is sent back from webservice for Application Fault.
Problem:
Though the Fault message is sent from web service ,in the BPM the block goes in error saying : "No exception defined for fault message ". The Exception brach is not executed.
Please suggest if anyone has come across such a scenario and solution to this.

hi satesh
using "exception handler" in BPM we can handle the error messages
regards
kummari

Exception Handling in bounded taskflows - expected behaviour

Hi,
I'm currently reviewing exception handling in bounded task flows and some things does not seems to be very clear for me.
(q1) Does it make sense that a bounded task flow calls a method (via a method activity) defined on the page definition of another page (outside of the BTF) by using a #{data.xxxmyPageDef.myMethodName.execute} EL expression?
(q2) Is is correct to expect the application to execute the method marked as ExceptionHandler in the taskflow, whenever an exception occurs?
(q3) I created 5 different scenarios where I call a service method which throws an exception, from within a page fragment of the BTF.
(q3 – sc1) Call a service method through the binding layer of the current page (by using #{bindings.xxx.execute})
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.(q3 – sc2) Call a service method through a task flow method activity using #{bindings.xxx.execute}
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.(q3 – sc3) Call a service method through a task flow method activity using #{data.myPageFragementPagedef.xxx.execute} (accessing the pageDef of the page fragment)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.(q3 – sc4) Call a service method through a task flow method activity using #{data.myPageContainingThePageFragmentPageDef.xxx.execute} (accessing the page containing the BTF region)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage. (q3 – sc5) Call a service method through a task flow method activity using #{data.aPageOutsideTheBTFPageDef.xxx.execute} (accessing a page outside the BTW)
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage. (q4) How can it be possible that – without an exception handler – exceptions occur when calling method activities, without the exceptions being translated to FacesMessages?
Thanks in advance,
Koen Verhulst
JDeveloper 11.1.1.4

Koen,
+(q1) Does it make sense that a bounded task flow calls a method (via a method activity) defined on the page definition of another page (outside of the BTF) by using a #{data.xxxmyPageDef.myMethodName.execute} EL expression?+
No. Exceptions should be handled locally.
+(q2) Is is correct to expect the application to execute the method marked as ExceptionHandler in the taskflow, whenever an exception occurs?+
Only for exceptions that are before Render Response. The Render Response Phase is not handled in ADFc. So exceptions that occur in managed beans may fall through
+(q3) I created 5 different scenarios where I call a service method which throws an exception, from within a page fragment of the BTF.+
+(q3 – sc1) Call a service method through the binding layer of the current page (by using #{bindings.xxx.execute}) Result: A dialog containing the exception message appears.+
This is what I expected. Althought, the exception handler method does not seems to be invoked.
The binding layer has an error handler you can override in the DataBinings.cpx file
+(q3 – sc2) Call a service method through a task flow method activity using #{bindings.xxx.execute}+
Result: A dialog containing the exception message appears.
This is what I expected. Althought, the exception handler method does not seems to be invoked.
Again, you use the binding layer to invoke the service
+(q3 – sc3) Call a service method through a task flow method activity using #{data.myPageFragementPagedef.xxx.execute} (accessing the pageDef of the page fragment)+
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
Never use such a call. Its bad practice as there is no guarantee the container you reference is active. Always have the method call activity have its own binding defined when accessing a method call activity. I know there are lots of example floating aroundthat you #{data ...} and many are from 10.1.3. This should be avoided alltogether though
+(q3 – sc4) Call a service method through a task flow method activity using #{data.myPageContainingThePageFragmentPageDef.xxx.execute} (accessing the page containing the BTF region)+
Result: Nothing happens.
This is not what I expected. Although, the exception handler method does not seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
Again, this is not a proper use of the ADF framework.
+(q3 – sc5) Call a service method through a task flow method activity using #{data.aPageOutsideTheBTFPageDef.xxx.execute} (accessing a page outside the BTW)+
Result: Nothing happens. This is not what I expected. Although, the exception handler method does nog seems to be invoked, I expect the ADF Error Handler to create a FacesMessage.
accessing a page outside the BTW (!!!) This should ring a worst practices alarm on your laptop (obviously doesn't do it either)
+(q4) How can it be possible that – without an exception handler – exceptions occur when calling method activities, without the exceptions being translated to FacesMessages?+
Exceptions are not handled in a single place but stacked. The business service raises an exception and passes it to the binding layer if not handled. The binding layer handles the exception and if it can't passes it to ADFc. ADFc can handle this exception if it is not during Render Response.
Bottom line: There is no single point of exception handling. So as a recommendation for best practices
- Catch and handle exceptions as close as possible to their origins
- If things can go wrong, thy will - use try/catch blocks in managed beans
- Use an exception handling activity in all bounded task flows. In the case of task flow call activities being used exceptions can bubble up to the caller. However, this would take users out of their current application context
- Exceptions not handled in ADFc can be intercepted by overriding the application task flow exception handler (used by the exception handler activities). This would give you a chance e.g. to handle issues during Render Response
- Never fight the framework, never bend the framework: Don't use out of scope access to page definitions and resources. Exception handling is not a replacement for bad code practices (sorry for saying this, its not meant to be rude) :-)
Though I don't have a qualified numbers of bugs open for exception handling in ADF between 11.1.1.4 and now (and some that are open), but there are issues reported in this area. If there is something that really feels wrong, please go ahead and file a bug and provide a test case for development to have a look. The Render Response issue, for example is something we are aware of and that is in discussion (afaik knows, there is a change in exception handling in JSF 2 that may have an impact to what we can do in ADFc).
thanks
Frank

TaskFlow Exception Handler Behavior

Hi all,
I have a question about taskflow exception handler.
My customer is using method-call exception handler to display error detail as FacesMessage dialog in their taskflow.
And they are now trying to find the way to call exception handler but not to show the dialog in case that some sort of exceptions happen.
To achieve this requirement they delete FacesContext.addMesage() from their exception handler, but when not call addMessage() they always get return code 500 (internal server error).
From the behavior we've got, do we always need to call addMessage() in it to come back to original page?
Regards,
Atsushi

Hi Frank,
Thank you for your reply. Please let me ask you another question.
When method-call error handler is executed it returns an outcome. And the outcome determines the next activity I get to.
My question is whether it is a designed behavior of method-call error handler that when the below two conditions are met I get back to the original error page to see facesMessage dialog.
1. The method-call outcome doesn't match any control flow case
2. addMessage() is called in the method defined at method-call
If any, I'd like to know how to get back the original page after error handler is executed without faces message.
Thanks,
Atsushi

Exception handling in VC?

Hello,
is there a way to handle exceptions that might occur when invoking a web service from a VC model? Actually, a technical error message is displayed when the invocation of a web service fails.
Rather, I would prefer to catch the exception and display a more user-friendly error message myself.
Any suggestions?
Best regards
Alexander

Hi Alexander,
[Here|Exception handling; (unfortunately not)
Regards,
Dharmi

Exception handling branch not executing in BPM

Similar Messages

Maybe you are looking for