Exception handling of portal errors

Some par's or abstractportalcomponents throw Java exceptions. In the web.xml (irj/WEB-INF) you can handle those exceptions. Only it seems that it doesn't work. We use portal 7.
We used for example the following wiki documentation: http://wiki.sdn.sap.com/wiki/display/EP/CustomizingErrorMessagesinPortal
I've found the common documentation but that also doesn't solve our problem.
Any help is welcome.

Another relating question is that we want to replace the custom ErrorComponent portalcomponent. This component is shown when for example a null pointer exception occurs.
A short description ot this in CE 7.1 is found at https://cw.sdn.sap.com/cw//docs/DOC-112387/edit?containerType=14&container=5444
Only I can't find any document which describes how this should be done in 7.0.
Edited by: Sander Star on Dec 21, 2009 1:44 PM

Similar Messages

Removing Exception Handling Causes Compiler Error

I am very new to Java. I have a background in other programming languages including Ruby. I am in need of a convenient means to parse XML code. I picked up the code shown at the end of this message on the Internet. In its original form, it works perfectly. I experimented by trying to comment out the try block as you can see. I was surprised to find that in that form it wouldn't compile. In essence, I thought what I was doing was simply removing exception handling. I figured that since the code worked and there were no exceptions being thrown, it would work just fine for experimentation purposes. (I understand that I would not want to do this in production mode.) Can someone please explain to me why removing the exception handling causes the program to fail to compile?
Thanks for any input.
... doug
/* Experimental Code */
/* http://www.mkyong.com/java/how-to-read-xml-file-in-java-dom-parser/ */
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
import org.w3c.dom.Node;
import org.w3c.dom.Element;
import java.io.File;
public class ReadXMLFile {
public static void main(String argv[]) {
try {
File fXmlFile = new File("ReadXMLFile.xml");
DocumentBuilderFactory dbFactory = DocumentBuilderFactory.newInstance();
DocumentBuilder dBuilder = dbFactory.newDocumentBuilder();
Document doc = dBuilder.parse(fXmlFile);
doc.getDocumentElement().normalize();
System.out.println("Root element :" + doc.getDocumentElement().getNodeName());
NodeList nList = doc.getElementsByTagName("staff");
System.out.println("-----------------------");
for (int temp = 0; temp < nList.getLength(); temp++) {
Node nNode = nList.item(temp);
if (nNode.getNodeType() == Node.ELEMENT_NODE) {
Element eElement = (Element) nNode;
System.out.println("First Name : " + getTagValue("firstname",eElement));
System.out.println("Last Name : " + getTagValue("lastname",eElement));
System.out.println("Nick Name : " + getTagValue("nickname",eElement));
System.out.println("Salary : " + getTagValue("salary",eElement));
} catch (Exception e) {
e.printStackTrace();
private static String getTagValue(String sTag, Element eElement){
NodeList nlList= eElement.getElementsByTagName(sTag).item(0).getChildNodes();
Node nValue = (Node) nlList.item(0);
return nValue.getNodeValue();
}

877757 wrote:
I figured that since the code worked and there were no exceptions being thrown, it would work just fine for experimentation purposes. The compiler doesn't know that your code works. It only knows that some method you call can throw some checked exception, and it requires you to catch it or declare that you don't.

BPM Exception handling for RFC errors

Hi all
I have to handle the exception which would be like below:
com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
I am trying to put Block step and things are not working fine. Can anyone please explain me the steps to trap the exception?
My scenario has synchronous call to RFC FM.
Rightnow i have inserted Exception branch in my Block step and put the send step to write the error file. I have put the Synchronous SEND step as part of block. This is not working.
Help please??

Hello Samuel,
Just to close this thread and finish up my own search, where I met your discussion, here I'm quoting two experts of this forum:
"you cannot catch the exception's value in the XI "
(see posting from Michal Krawczyk, Jun 12, 2006, in thread catch the exception)
"The content of a fault message are not accessible inside a BPM."
(see posting from Bhavesh Kantilal, Oct 3, 2007, in thread Notify user about Exception in BPM)
Regards,
Dennis

Exception Handler Error: Source File Error please help me out

Hai i have simply added a text field and a button and i am trying to submit the data entered in text field to the database by pressing button.
It is compiling and running successfully. but when i press the button it is showing that exception handler : Source File error.

Could you post initial part of the exception displayed in the Error Page. With out it, it is difficult to say what is happening!
- Winston
http://blogs.sun.com/winston

Step repeated in Exception branch requires exception handler, why?

I have a BPM Integration process with a sync send step calling a RFC. Any system errors and application errors are handled by an exception branch where I send an alert as then re-do the send step (so that it will fail but allow me to restart from that point after fixing the issue). The problem I am having is that in this send step, since it is mandatory to have an exception handler for application errors (defined fault message RFC.Exception), what do I enter for exception handler in this send step which is itself in an exception branch? I do not want to handle the exception this second time since I want this step to fail and process stops here to be able to restart manually later.

Hi,
I am not sure, how you will restart the step manually? Because once there is an error in the sync send, the message will turn to "Cancelled" status. You cannot restart this message.
Now, for the second send step in the exception block you will not be able to choose the same exception block in the exception handler field. But for some reason if this send also fails then you cannot restart the process manually - same reason i mentioned above. It will fail as you intended it to do so.
Regards,
Balaji.M

Global Exception Handler

Hello,
I've implemented the Global Exception Handler how is saying at http://www.adobe.com/devnet/flex/articles/global-exception-handling.html
Some errors are being catched by it, and others not.
I looked at another thread here, but for him, the Debug Dialog was not appearing because another place was catching the exception for him.
There are some way to catch all errors in just on place?
I need this, because sometimes in production happen errors that we didn't find in development, but stills there.
The SDK is 4.1 and minimum Flash Player for the applications is 10.1.
Regards,
Fredy.

How to reproduce the error not being catched.
Main Application:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                                 xmlns:s="library://ns.adobe.com/flex/spark"
                                 xmlns:mx="library://ns.adobe.com/flex/mx"
                                 minWidth="955"
                                 minHeight="600"
                                 xmlns:views="views.*"
                  applicationComplete="onApplicationComplete()">
          <s:layout>
                    <s:VerticalLayout />
          </s:layout>
          <fx:Script>
                    <![CDATA[
                              import com.adobe.ac.logging.GlobalExceptionHandler;
                              import com.adobe.ac.logging.LogHandlerAction;
                              private var globalExceptionHandler:GlobalExceptionHandler;
                              private function onApplicationComplete():void {
                                        globalExceptionHandler = new GlobalExceptionHandler();
                                        globalExceptionHandler.preventDefault = true;
                                        var lha:LogHandlerAction = new LogHandlerAction();
                                        globalExceptionHandler.handlerActions = [];
                                        globalExceptionHandler.handlerActions.push(lha);
                    ]]>
          </fx:Script>
          <mx:ViewStack id="vs" creationPolicy="none">
                    <views:FirstView />
                    <views:SecondView />
          </mx:ViewStack>
          <s:Button label="Call Second View" click="vs.createDeferredContent()"/>
</s:Application>
First View:
<?xml version="1.0" encoding="utf-8"?>
<s:NavigatorContent xmlns:fx="http://ns.adobe.com/mxml/2009"
                     xmlns:s="library://ns.adobe.com/flex/spark"
                     xmlns:mx="library://ns.adobe.com/flex/mx" width="400" height="300"
                     creationComplete="onCreationComplete()">
          <fx:Script>
                    <![CDATA[
                              import mx.rpc.remoting.RemoteObject;
                              private function onCreationComplete():void {
                                        trace("First Created!");
                    ]]>
          </fx:Script>
</s:NavigatorContent>
Second View:
<?xml version="1.0" encoding="utf-8"?>
<s:NavigatorContent xmlns:fx="http://ns.adobe.com/mxml/2009"
                                                  xmlns:s="library://ns.adobe.com/flex/spark"
                                                  xmlns:mx="library://ns.adobe.com/flex/mx" width="400" height="300"
                                                  creationComplete="onCreationComplete()">
          <fx:Script>
                    <![CDATA[
                              import mx.rpc.remoting.RemoteObject;
                              private function onCreationComplete():void {
                                        trace("Second View created!");
                                        var ro:RemoteObject;
                                        ro.destination = "";
                    ]]>
          </fx:Script>
</s:NavigatorContent>
Regards,
Fredy.

Exception handling prob

I want to write an exception handler for forms error message ora-01403. The problem code is
PRAGMA Exception_Init (login_name_doesnt_exist, -01403);
It gives me an 'illegal oracle error number' when I compile. I've checked the specs and -01403 IS valid. It is an error for 'no data found' which is right for the way I'm trying to use it.
BTW It compiles OK when I use error code -01404
Anyone else had this problem?

Cheers, that works fine.
Thanks a lot
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Other Side ([email protected]):
You see IMHO, for proc
"PRAGMA Exception_Init (login_name_doesnt_exist, -01403);"
you must give sqlcode value, not the one what's in the sqlerrm.
So, instead -01403 try to use 100
P.S. have a nice day.<HR></BLOCKQUOTE>
null

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 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

How to display the 500-internal server error on the Exception Handler page

Hello
My situation is as follows : JDev 11.1.1.0.2, ADF fusion application, one unbounded task flow containing 2 view pages view1.jspx and error.jspx
The error jspx is marked as the exception handler.
When an error occurs (typically a 500-Internal Server Error) the error.jspx is correctly displayed and shows our message such as 'Don't panic, please call our tech support'
What I would like to do is to display the actual error stack on this page along with our message.
I've searched around and I can't find how to either get the error stack in a bean or what EL expression should be used to get the error stack.
Can anybody help ?
Best Regards
Paul
Switzerland

The error will be the same, but the stack trace will be different, such as
Error 500--Internal Server Error
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Echec de la vérification des autorisations : '/view1.jspx' 'VIEW'.
     at oracle.adf.controller.internal.security.AuthorizationEnforcer.handleFailure(AuthorizationEnforcer.java:145)
     at oracle.adf.controller.internal.security.AuthorizationEnforcer.checkPermission(AuthorizationEnforcer.java:124)
     at oracle.adfinternal.controller.state.ControllerState.initializeUrl(ControllerState.java:639)
     at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart2(ControllerState.java:449)
     at oracle.adfinternal.controller.application.SyncNavigationStateListener.afterPhase(SyncNavigationStateListener.java:44)
     at oracle.adfinternal.controller.lifecycle.ADFLifecycleImpl$PagePhaseListenerWrapper.afterPhase(ADFLifecycleImpl.java:529)
     at oracle.adfinternal.controller.lifecycle.LifecycleImpl.internalDispatchAfterEvent(LifecycleImpl.java:118)
     at oracle.adfinternal.controller.lifecycle.LifecycleImpl.dispatchAfterPagePhaseEvent(LifecycleImpl.java:166)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.dispatchAfterPagePhaseEvent
What I would like is to display the above stack trace on the page marked as the exception handler....
Regards
Paul

Error handling in Portal standard forms

I have a customer who needs to validate input on a Form Based on a Table (standard component). They have tried code, as shown below, as a PLSQL handler on a Save button. This example can obviously be solved with JavaScript validation on the client, but they have similar requirements for validation on DB level.
If procedure call 1) in the if statement is used, nothing happens. If procedure call 2) is used, it is executed in a new page as a standard error Oracle Portal error message.
declare
v_sender VARCHAR2(1000);
v_sender_id NUMBER;
begin
v_sender := p_session.get_value_as_VARCHAR2(
p_block_name => 'DEFAULT',
p_attribute_name => 'A_SENDER');
v_sender_id := p_session.get_value_as_NUMBER(
p_block_name => 'DEFAULT',
p_attribute_name => 'A_SENDER_ID');
insert into hd (number, text) values (hd_seq.nextval,
'step 3 v_sender = ' || v_sender ||
' v_sender_id = ' || v_sender_id);
if v_sender_id >= 100 then
1) Custom error handling, does not display:
show_error('Error message');
2) Error handling is displayed, but as a standard error:
raise_application_error(-20000, 'SenderID must be smaller than 100.');
else
doInsert;
end if;
end;
The customer has two questions:
Why does the custom procedure in 1) "show_error" not execute, and if it does, why does it not display? show_error works and the if statement is entered.
Is it possible to take control of Portals error handling on standard components (forms etc.), to show custom error messages with the style used on the component/page instead of the standard Error: ORA- ....etc. as Portal displays it?
Customer needs reply asap. Please reply directly. Any help will be much appreciated!
Kind regards
Jakob Lund

Jacob,
Try following:
declare
v_sender VARCHAR2(1000);
v_sender_id NUMBER;
begin
v_sender := p_session.get_value_as_VARCHAR2(
p_block_name => 'DEFAULT',
p_attribute_name => 'A_SENDER');
v_sender_id := p_session.get_value_as_NUMBER(
p_block_name => 'DEFAULT',
p_attribute_name => 'A_SENDER_ID');
insert into hd (number, text) values (hd_seq.nextval,
'step 3 v_sender = ' || v_sender ||
' v_sender_id = ' || v_sender_id);
if v_sender_id >= 100 then
p_session.set_value(
p_block_name => "_block",
p_attribute_name => '_STATUS',
p_value => 'Sender ID must be less than 100!');
-- return to your form with status message set
-- and all fields filled with recent values
return;
end if;
end;
-- This point is reached only if validation is OK
doInsert;
Regards,
Henn

Reboot due to system error / Register dump from exception handler

hi,
I have a problem with Labview RT when using Reboot function.
The RT target (desktop) reboot but there is a message : Reboot due to system error. And if I reboot once again, the target become in safe mode.
Now, If I look at the log I obtain the following message see more in the log attached!
*** REGISTER DUMP FROM EXCEPTION HANDLER (code 0x80000003) ***
I don't understand why there is this message.
Anybody has an explaination?
Attachments:
Nouveau Document texte2.txt ‏6 KB

julesjay a écrit:
ok I didn't know that. I will wait for tomorrow.
NI france is not very efficient about labview Real time problems.
There is one or two experts and there aren't easily reachable.
So a lot of question I send stay with no answer.....
That why I hope someone will be able to help me.
Hi Julesjay,
After i have see your log file and the problem, i think NI FRANCE are working on your request for all problems you have in your application.
And i don't understand what you say that, because we have make test, we have send us informations for make different tests, and we are still working on your problem.
I know the problem are not resolved, but we are working for resolve it quickly.
I suggested you to contact the AE that are your service request for have more information.
Best regards,
Christophe S.
FSE East of France І Certified LabVIEW Associate Developer І National Instruments France

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.

How to implement Exception Handling error in IDoc to File and RFC to File

Hi,
We are implementing the two below scenarios :
1. IDOC to File
2. RFC to File
We have to implement the Exception Handling for the above two cases. Kindly could you provide the inputs to implement the Exception Handling for the above two cases.
Please provide the precious inputs to implement this.
Thanks,
Ramesh

Hi Ramesh,
The exception handling for idocs
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
Exception handling in File to IDoc Scenario
For RFCs
Re: Passing SAP Exceptions to a sync SOAP Call
Error Handling when using RFC
Exception Handling while Calling RFC - BPM
handle exceptions in remote function modules
Regards,
Prateek

Exception while handling request: deserialization error: java.text.ParseExp

Hi guys,
While getting the sales order from the JDE database. It is giving
Caught exception while handling request: deserialization error: java.text.ParseException: Unparseable date: "-11-JA-01T12:00:00-05".
can any one of you can guide me about this exception
Expecting a reply from any one ASAP.
Regards,
Chakri

the schema element for this field is having different datatype than what you are receiving the data. Can you check logs and see on which column it is failing? If we know the exact xsd datatype used for the element and and value that is stored in table then we can correct the xsd accordingly. Are you using dynamic sql query or select options to get values from DB.

Exception handling of portal errors

Similar Messages

Maybe you are looking for