Exception Handling in C++ generate core

Hello ,
I have a shared lib which is having some code for exception handling ,till the point of exception thrown program is running fine but after the exception get thrown the program is crasing and creating the core .
I am using Solaris 5.9 on intel(x86) using compiler CC (CC: Sun C++ 5.5 2003/03/12 )
I am specifing the Makefile here . If any one have faced the same kind of problem then please help me out.
***********************Makefile *****************************
SHARED_LIBS = \
/opt/SUNWspro/prod/lib/libp/libgc.a \
/usr/lib/libCrun.so.1 \
/opt/SUNWspro/prod/lib/CC4/libC.a \
$(WLESSL)/lib/libgp.a \
$(WLESSL)/lib/sslplus.a
LIB=$(OBJ) $(SHARED_LIBS)
LIB128=$(OBJ128) $(SHARED_LIBS)
LIB_20=$(OBJ_20) $(SHARED_LIBS)
CC_20=/opt/SUNWspro/bin/CC
cc_20=/opt/SUNWspro/bin/cc
CC_OUT_20=-w -KPIC -mt -lpthread -c $< -o $@
# compile defintions
DEF=-DAPACHE -DSOLARIS -DEAPI -D_POSIX_PTHREAD_SEMANTICS -D_PTHREAD -D_REENTRANT
DOMFLAG=-DDOMESTIC_STRENGTH_ENABLED
# this is not needed if apache20/bin/apxs is working properly
APXS_CFLAGS_20=-mt -lpthread
COMPILE=$(cc_20) $(APXS_CFLAGS_20) $(STD_20_INC) $(VER2) -c $(SRC) -o $(OBJDIR_20)/abc_w.o
LOAD=$(cc_20) -G -z lazyload -o $(OBJDIR)/abc_wl_20.so $(LIB_20) $(OBJDIR_20)/abc.o
LOAD128=$(cc_20) -G -o $(OBJDIR)/abc_wl128_20.so $(LIB128_20) $(OBJDIR_20)/abc.o
# the DSO and objs should be placed in this directory
OBJDIR=sol_x86
OBJDIR_20=sol_x86/a20
# WLE include files include tmmach which are platform specific
WLESSLINC=$(WLESSL)/sysinclude

Hi Santinu,
I saw your question and thought of replying you, but I guess you might have got the solution by now as because the post date of your question is around a year back.
You need to change $LOAD so that id uses CC instead of cc. There's a compatibility issue.
LOAD=$(CC_20) -G -z lazyload -o $(OBJDIR)/mod_wl_20.so $(LIB_20) $(OBJDIR_20)/mod_weblogic.o
LOAD128=$(CC_20) -G -o $(OBJDIR)/mod_wl128_20.so $(LIB128_20) $(OBJDIR_20)/mod_weblogic.o
Hope this Helps.
Thanks
Somak

Similar Messages

Global exception handler not being called

Hi,
I have a wli process that has a global excepton handler. One of the controls throws a NullPointerException but it is not being handled by the group exception handler nor the global exception handler.
Does anyone have any idea what may be causing this behaviour?
Thanks,
Dale

I have discovered that using -memalign=Ns with N greater than 1 does not work for me. For example, if I remove a VME card from the system and try to use an unsigned short pointer to access a 16-bit register in the card's vacated VME address space, my signal handler gets called when I compile the code with N=1, but for any other N, my handler is ignored and my program cores.
Unfortunately, using N=1 causes other code that works with higher N to fail. I have one VME card where I need to access a register as a 16-bit read. The code the compiler generates to access the unsigned short pointer value results in two single-byte load instructions - this causes the device to cry foul and as a result, the driver raises SIGBUS, which my program handles. For higher N, the compiler generates one two-byte load instruction, and the device is happy to send back the data.
So it would appear there is some kind of problem with -xmemalign=Ns for N > 1. It seems like the SIGBUS handler typically imployed by the compiler to handle the misalignment problems when -xmemalign=Ni is used is being invoked.
Any other ideas?

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.

Error/Exception handling in MQSeries

Hi,
What is the robust (yet simple) way to handle any exception generated while doing any operation in MQ Series for e.g. putting messages on queue.
Currently i have just done exception handling using try/catch blocks in my java application.
Kindly explain.
Thanks,
Sahil

This forum is specific to the Sun Java System Message Queue
product and is not a forum on IBM's MQSeries product.
If you have a question on MQSeries, you may want to look for a forum on IBM's site.

Exception handling in report

Hello all,
i want oto implement exception handling in report.
scenario:
i have a parameter form par.fmb
i provide parameter on form then call the report.
if there is some error generate while query of report then how to handle it, so that user get the message.
below query is used in report:
SELECT SPC_ITEM_CODE,GENERATE_ITEM_NAME(SPC_ITEM_CODE),MOD_DATE,OBU,REQ_NO,REQ_QTY,OQC_QTY,SPC_ITEM_QTY,process
, INSP_LOT_SIZE,REMARKS,INSP_STATUS
FROM OQC_DATA
WHERE (REQ_NO=:REQ_NO OR :REQ_NO IS NULL) AND trunc(MOD_DATE) BETWEEN :FROM_DATE AND :TO_DATE
AND SPC_LOCN_CODE=:LOCN_CODE
ORDER BY REQ_NO,SPC_ITEM_CODE
here: GENERATE_ITEM_NAME(SPC_ITEM_CODE) is database function.
as spc_item_code is column in OQC_DATA table, it any how there is null value in spc_item_code then error will raise, i and want to handle this error sothat ,
i found the reason.
Thanks
yash
Edited by: yash_08031983 on Jan 27, 2012 9:11 PM

yash_08031983 wrote:
Hello all,
i want oto implement exception handling in report.
scenario:
i have a parameter form par.fmb
i provide parameter on form then call the report.
if there is some error generate while query of report then how to handle it, so that user get the message.
below query is used in report:
SELECT SPC_ITEM_CODE,GENERATE_ITEM_NAME(SPC_ITEM_CODE),MOD_DATE,OBU,REQ_NO,REQ_QTY,OQC_QTY,SPC_ITEM_QTY,process
, INSP_LOT_SIZE,REMARKS,INSP_STATUS
FROM OQC_DATA
WHERE (REQ_NO=:REQ_NO OR :REQ_NO IS NULL) AND trunc(MOD_DATE) BETWEEN :FROM_DATE AND :TO_DATE
AND SPC_LOCN_CODE=:LOCN_CODE
ORDER BY REQ_NO,SPC_ITEM_CODE
here: GENERATE_ITEM_NAME(SPC_ITEM_CODE) is database function.
as spc_item_code is column in OQC_DATA table, it any how there is null value in spc_item_code then error will raise, i and want to handle this error sothat ,
i found the reason.You can handle the error in two way.
First from the function, you can use exception in it and through 0(zero) if it didn't get any value.
2nd use nvl function in the sql like nvl(GENERATE_ITEM_NAME(SPC_ITEM_CODE),0) if number data type or NVL(GENERATE_ITEM_NAME(SPC_ITEM_CODE),'n/a') if char data type output.
You can also use decode.
Hope this will help you.

Exception Handling in webdynpro abap

Hi
I have a function call which raises an exception. How do i handle it?

hi,
In WD4A, Exception handling in FM is same as We do in R/3. You can check sy-subrc after calling the function module.
Also you can raise error message by using web dynpro code wizard(control + F7 ) button:
Select Generate message radio button. You will find number of methods in F4. You can use them as per your requirement
Example :
Suppose you call a FM like this in WD ABAP :
CALL FUNCTION 'F4UT_RESULTS_MAP'
    TABLES
      shlp_tab          = t_shlp_tab
      record_tab        = t_record
      source_tab        = t_HCP
    CHANGING
      shlp              = p_shlp_descr
      callcontrol       = icallcontrol
    EXCEPTIONS
      illegal_structure = 1
      OTHERS            = 2.
Now after this FM, check the sy-subrc value Like this:
if sy-subrc = 1.
<Report message for exception 1>.
elseif sy-subrc = 2.
<Report message for exception 2>
endif.
Edited by: Saurav Mago on Oct 16, 2009 10:22 AM

BPM - Exception handling in multiline mapping

Hi,
I have in a BPM a block with processing mode ParForEach containing a transformation and then a send step.
If the transformation (mapping) generates an exception for one of the lines of the multiline variable being processed, no subsequent lines are passed to the send step.
I want the process to execute the mapping for each line and then send messages corresponding to lines without error. How can I do?
Thank you
Simona

Hi Simona,
I also feel that Michal had suggested the correct solution. Not sure why you are saying that the error gets propagated, if you have defined a proper Exception handling for the inner block.
But regarding your design for "ParForEach", I am not sure whether you really need to carry out a transformation step for each Block instance, in which case you can keep the transformation step before the "ParForEach" block.
Rgds
R Chandrasekhar (RC)

Exception handling in GOOP

Does anyone know if it is possible to generate exceptions in GOOP,
just like in other OO languages?
Also: are there any other ways to incorporate exception handling in LabVIEW?
Thanks!

> Does anyone know if it is possible to generate exceptions in GOOP,
> just like in other OO languages?
> Also: are there any other ways to incorporate exception handling in LabVIEW?
If you are looking for a good way of handling errors, then I'd encourage you
to look at using Error I/O. It is basically a technique for throwing errors
forward, and catching them downstream. This avoids problems with parallelism
and determining vales for downstream signals. If you have ideas about what
you would like to see, please suggest them.
Greg McKaskle

Exception Handling related problem

Can anybody tell me why it is not giving ArithmeticException.
package pckg1;
* @author anil_saini
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
import java.io.FileNotFoundException;
public class Average7 {
     public static void main(String[] args) throws InterruptedException,FileNotFoundException {
     try {                                                      // (1)            System.out.println(printAverage(100, 0));                                  // (2)
     } catch (ArithmeticException ae) {                         // (3)
     Thread.sleep(1000);
          ae.printStackTrace(); // (4)
System.out.println("Exception handled in " + // (5)
     "main().");
     finally {
     System.out.println("Finally in main()."); // (6)
     System.out.println("Exit main()."); // (7)
public static int printAverage(int totalSum, int totalNumber) {
     int average=0;
     try {                                                      // (8)
average = computeAverage(totalSum, totalNumber); // (9)
     System.out.println("Average = " + // (10)
     totalSum + " / " + totalNumber + " = " + average);
     return average;
     } catch (IllegalArgumentException iae) {                   // (11)
          iae.printStackTrace(); // (12)
System.out.println("Exception handled in " + // (13)
     "printAverage().");
     } finally {
System.out.println("Finally in printAverage()."); // (14)
     return average;
     }     // (15)
public static int computeAverage(int sum, int number) {
     System.out.println("Computing average.");
     if (number == 0) // (16)
throw new ArithmeticException("Integer division by 0");// (17)
     return sum/number; // (18)
Output
=======================
Computing average.
Finally in printAverage().
0
Finally in main().
Exit main().

Because return statements in finally blocks are evil!
int average = 0;
try
{ // (8)
     average = computeAverage(totalSum, totalNumber); // (9)
     System.out.println("Average = " + // (10)
               totalSum + " / " + totalNumber + " = " + average);
     return average;
catch (IllegalArgumentException iae)
{ // (11)
     iae.printStackTrace(); // (12)
     System.out.println("Exception handled in " + // (13)
               "printAverage().");
     throw new IllegalArgumentException();
finally
     System.out.println("Finally in printAverage()."); // (14)
     return average; // (15)
}You get an exception at (9), but finally is guaranteed to be executed, so the JVM executes it. Now you return in your finally block (15), and the JVM is left with the choice of executing your return statement or propagating the exception. Since, as said, finally is guaranteed to be executed, it returns and swallows the exception.
That's why IMHO return statements in finally blocks should not be allowed.
(Some compilers issue warnings)
If you move your return statement out of the finally block, it will work as you'd expect it.

Bounded Taskflow Exception Handler not working with Page Fragements

I have one bounded - taskflow task-flow-definition
<?xml version="1.0" encoding="windows-1252" ?>
<adfc-config xmlns="http://xmlns.oracle.com/adf/controller" version="1.2">
<task-flow-definition id="task-flow-definition">
    <default-activity>view1</default-activity>
    <managed-bean>
      <managed-bean-name>backing_main</managed-bean-name>
      <managed-bean-class>view.backing.Main</managed-bean-class>
      <managed-bean-scope>pageFlow</managed-bean-scope>
    </managed-bean>
    <managed-bean>
      <managed-bean-name>backing_view1</managed-bean-name>
      <managed-bean-class>view.backing.View1</managed-bean-class>
      <managed-bean-scope>pageFlow</managed-bean-scope>
    </managed-bean>
    <managed-bean>
      <managed-bean-name>backing_view2</managed-bean-name>
      <managed-bean-class>view.backing.View2</managed-bean-class>
      <managed-bean-scope>pageFlow</managed-bean-scope>
    </managed-bean>
    <exception-handler>view2</exception-handler>
    <view id="view1">
      <page>/view1.jsff</page>
    </view>
    <view id="view2">
      <page>/view2.jsff</page>
    </view>
    <use-page-fragments/>
</task-flow-definition>
</adfc-config>view1.jsff contains one command button, which calls one ActionListener
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<af:commandButton text="commandButton 1" actionListener="#{pageFlowScope.backing_view1.callMyFunction}"
                    binding="#{pageFlowScope.backing_view1.commandButton1}"
                    id="commandButton1"/>

</jsp:root>view1.java callMyFunction throws an Exception
    public void callMyFunction(ActionEvent event) throws Exception{
        throw new Exception();
    }view2.jsff is an exception handler
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<af:activeOutputText value="Exception Occured"
                       binding="#{pageFlowScope.backing_view2.activeOutputText1}"
                       id="activeOutputText1"
                       inlineStyle="font-size:xx-large; color:red;"/>

</jsp:root>above taskflow is dragged-drop as a Region in one file main.jspx
<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
          xmlns:f="http://java.sun.com/jsf/core"
          xmlns:h="http://java.sun.com/jsf/html"
          xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=windows-1252"/>
<f:view>
    <af:document binding="#{pageFlowScope.backing_main.document1}"
                 id="document1">
      <af:form binding="#{pageFlowScope.backing_main.form1}" id="form1">
        <af:region value="#{bindings.taskflowdefinition1.regionModel}"
                   id="taskf1"
                   binding="#{pageFlowScope.backing_main.taskf1}"/>
      </af:form>
    </af:document>
</f:view>

</jsp:root>*pressing a commandButton on view1.jsff throws an Exception as expected but does not go to exceptionHandler [view2.jsff]*
However, this does work with Bounded Task-Flow without page fragments , view1.jspx contains one button, calling one method which throws an Exception,
view2.jspx is an Exception Handler, and in this case it redirects to the view2.jspx [error page]
any ideas?
thanks

Hi,
Pretty much. However, you got the event part wrong, which is mostly my fault here. First, let put down some general JSF facts about event handling.
1. http://java.sun.com/javaee/5/docs/api/javax/faces/component/UIComponent.html#queueEvent(javax.faces.event.FacesEvent)
2. So, basically, queuing an event on a component means queuing it on its parent until you reach the UIViewRoot that will really actually queue it. That strategy allows iterating components to intercept event queued on their children to record the row index as well so that the data model can be synchronized correctly during the broadcast phase (see http://java.sun.com/javaee/5/docs/api/javax/faces/component/UIData.html#queueEvent(javax.faces.event.FacesEvent) and http://java.sun.com/javaee/5/docs/api/javax/faces/component/UIData.html#broadcast(javax.faces.event.FacesEvent))
3. Exceptions that aren't handled by the exception handler are thrown during broadcast or various process* methods.
So, the catch component must leverage these facts to intercept events queued on its children (by overriding queueEvent method) wrapping the original event in a custom on that flag the catch component itself as the source of the event. The result will be that the broadcast method of the catch component will be called to handle the event. The broadcast method must then unwrap the event (to get the original event), gets the original source, then call originalSource.broadcast(originalEvent) within a try-catch block.
Does it make any more sense put that way? Note that it's an obscure part of JSF so I cannot make it incredibly simple either.
Regards,
~ Simon

Database Exception Handling Error

Hi
Platform: BPEL/SOA Suite 10.1.3.3
I created an async BPEL process that does a simple insert into a database, and added error handling to ensure that database errors are trapped and interested parties notified when errors occur. To test the exception handling, I created a dummy table with an id and value column, where the value is declared as varchar2(1). Then I invoked the BPEL process with a string value longer than 1 character.
I expected to have the process catch the error, execute a java embedded System.out.println, assign the fault details to a fault variable string, and then terminate, with the terminated process displayed in the BPEL Console. Much to my surprise, as this executed perfectly in BPEL 10.1.2, this did not happen. Instead, the java embedded System.out.println executed, but then the following error was generated and the BPEL process was sent to the Manual Recovery area.
2007-10-18 10:52:29,879> <ERROR> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.DBInteraction executeOutboundWrite> unable to execute the outbound insert operation on: DBAccessDummyTable.TestDummy
<2007-10-18 10:52:29,879> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/E:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_Test_DummyTable_Async_1.5_709050a551839440870cf17aba79c0f7.tmp/DBAccess_DummyTable.wsdl [ DBAccess_DummyTable_ptt::insert(TestDummyCollection,TestDummyCollection) ] - Could not invoke operation 'insert' against the 'Database Adapter' due to:
ORABPEL-11616
DBWriteInteractionSpec Execute Failed Exception.
insert failed. Descriptor name: [DBAccessDummyTable.TestDummy]. [Caused by: ORA-12899: value too large for column "ALE_ADAPTER"."TEST_DUMMY"."DUMMY_STRING_VALUE" (actual: 4, maximum: 1)
Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.3.0) (Build 070608)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-12899: value too large for column "ALE_ADAPTER"."TEST_DUMMY"."DUMMY_STRING_VALUE" (actual: 4, maximum: 1)
Error Code: 12899
Call:INSERT INTO TEST_DUMMY (DUMMY_ID, DUMMY_STRING_VALUE) VALUES (?, ?)
     bind => [280, long]
Query:InsertObjectQuery(<TestDummy 280 />).
     at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:469)
     at oracle.tip.adapter.db.exceptions.DBResourceException.outboundWriteException(DBResourceException.java:510)
     at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:963)
     at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:225)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:485)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:435)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:443)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:727)
I decided to test this on my local SOA Suite, instead of deploying to the development server, and again to my surprise, the exception was caught and handled as expected, with no errors thrown. I then realized that I hadn’t set up the datasource, connection pool, and DbAdapter connection factory in Enterprise Manager for the database being used. I configured these appropriately, and once again the above error happened, this time on my local SOA Suite. I removed the connection from the DbAdapter connection factory, and the exception was once again caught and handled appropriately.
Since our database passwords have to be changed periodically, we are required to configure the datasource etc on the server so password management can be done in one place. That being the case, I’m hoping someone can provide some ideas to help resolve this issue. I tried changing a few of the database settings in Enterprise Manager (using dataSourceName instead of xADataSourceName, setting usesBatchWriting to false instead of true) but none of these changes worked.
Thanks

You should look into Bridge [GOF:151] and Memento [GOF:273].
Bridge allows you to decouple your mechanism from the implementation memento on how to propergate the decoupled exception information.

Generalised Event Exception Handler

Hi all experts,
Can anybody plz tell how to create a generalised Exception Handler , so that wenever a exception is generated in the main method the Exception Event Handler shud be initialised to catch the exception for all the exceptions generated at runtime.
I want the Exception Event Handler to catch the exceptions for RFC BAPI,EJB Webservice,etc..as i am using this in my application to give general message at runtime if any exceptions is generated from the try-catch block.
Waiting for the reply.
Regards:
SK

Hi SK,
There is a general Exception that you can use for all exceptions thrown.
just add this code for any exception you want to catch.
try
// try anything
catch(Exception e)
// catch any exception
Regards,
Marshall.

What King of exception handling is done in OA framework code?

Hi All,
I am not a core java person but have to do some OA framework code changes.Wanted to know what kind of exception handling is done in OAF codes?
I was looking as the seeded oracle controllers and dont see any try catch blocks.
can anyone guide me?

OAF java based framework, hence exception handling is similar to how its done in core java. I would advuce to better go through exception handling concepts of core java.
--Mukul

Bean exception handling

Hello,
I have a question concerning the bean exception handling. If I'd like to use a DB-connection inside a bean, how to handle the SqlException to display a nice error message to the user (perhaps next to the submit-button or redirect to another site).
Thx
Stefan

Thank you for the reply. That works fine but I wanted
to avoid using Faces-code inside of the bean because
of portability. Is there a possibility to throw an
exception inside of a setter and catch it somewhere
else to generate the FacesMessage there ?There are at least two ways to look at this.
First, I've found that you often need one or more beans that ties the UI to the backend. For instance, my backend bean may have a method for saving itself to a database, but that method most likely doesn't return a String, as an "action method" must. I also often need a bean to hold UI values that are pure UI artifacts rather than backend values, say a filter criteria for a database search. In this type of bean (I call them "glue beans", others call them "backing bean" or "code behind file") I don't mind having JSF code, so my original suggestion applies to this type of bean rather than to the real backend beans.
Second, in an application where you can bind the JSF components directly to backend bean properties and methods, you can set up an error handler in the web.xml file that displays a nice error message and logs details about the problem for further analysis.
Hans Bergsten (EG member)

Default Exception Handling in B2B

Hi All,
Need your help and advise on the below requirement we have currently:
Source system sends an XML input to MW and therein, we transform it into PO_850 XSD and sends it to B2B. We are validating the XSD in B2B and then generating an EDI_PO_850 file and sending it to the Trading Partner. We are going to have 5 different Target Trading Partner. I have 2 questions w.r.t the default exception handling in place for Oracle B2B:
1. Which Queue will have the Error Information for the above case? B2B_IN_Queue/B2B_OUT_Queue/B2B_IP_IN_Queue
2. We would like to consume the error messages specific to a trading partner from the JMS Queue directly, how can we achieve it?
Appreciate your help in this regard.
Thanks in Advance
Priyanka

Hi Priyanka
B2B operates in two modes for default internal queue communication - AQ and JMS. This is controlled in the Admin/Configuration page "use JMS queues" checkbox.
In AQ, the queue to which the exception message is delivered would be IP_IN_QUEUE
In JMS the queue to which the exception message is delivered would be B2B_IN_QUEUE. Since you speak about reading error message from the JMS queue directly, am thinking this would be the one of interest to you.
In addition to the above we can create custom JMS internal delivery queue and this can be associated to the Exception Queue which can be assigned in the Admin/Configuration page.
With regards to reading the exception msg specific to the trading partner from the JMS Queue directly, this can be done by adding a check on the dequeue process. Each exception message is populated with From_Party and To_Party information. In the outbound delivery case, the exception message should have To_Party set as the partner's name. This can be checked.
Hope that helps.
Regards
Arun

Exception Handling in C++ generate core

Similar Messages

Maybe you are looking for