Capture Origin of Exception: PageLifecycle

I've altered my project to include classes that modify exceptions that are thrown. Like the SRDemo example, I have ErrorHandler, PageLifecycle, PhaseListener, and KnowErrorStopException classes. In the PageLifecycle class, I can catch and modify the exception being thrown, but I would like to include the origin of the error. Is there any way to capture the name of the page that the error is being thrown on? Or is there a way to capture the name of the table or bc view that the error is comming from?
Thanks,
Tim

1) Does the OoM happens while instantiating the buffered image, (which probably tries to allocate a big continuous native array of pixels)?
Or the Graphics object (same reason, though the Graphics is probably just an empty shell over the big pixel array)?
2) In which format do you need to save the image? Do you only need to be able to read it again in your own program?
If yes to both questions, then a pulled-by-the-hair solution coud be to instantiate your own Graphics subclass (no Buffered Image), whose operations would save their arguments directly to the image file, instead of into a big in-memory model of the panel image.
If the output format is a standard one though (GIF, JPG,...), then maybe your custom Graphics's operations could contain the logic to encode/compress as much as possible of the arguments into an in-memory bytearray of the target format?
I'm not very confident though; I d'ont know the GIF or JPEG encoding, but I suspect (especially for JPEG) that you need to know the "whole" image to encode it properly.
But if the target format supports encoders that work on the fly out of streams of bytes (e.g. BMP ) then you can use whatever compress/uncompress technique you see fit (e.g. RLE ): you know the nature of the panels, you may be aware of some optimizations you may perform wrt pixels storage. prior to encoding (e.g., bug empty areas, predictable chessboard pattern, black-and-white palette,...).
Edited by: jduprez on Sep 19, 2009 7:33 PM

Similar Messages

Obtaining the original JDBC exception from an EJBException?

Hello All,
I am using EJB3 on Glassfish using the default TopLink persistence manager. Within a Session Bean, when the persistence manager catches a DB exception, it marks the transaction to be rolled back, and throws an EJBException, in turn wrapping a RollbackException. Now I was expecting to be able to get the original jdbc exception out of the caused by exception of one of these exceptions, but it is not.
It is important that I do retrieve the original exception, as I need to report back to the users what the problem is, and to do this I need to analyse the SQL error codes.
Note that these are the DB exceptions caught by toplink during managed transactions (e.g. an EJB persist or merge), not exceptions thrown by our code.
Does anyone know if it is possible to get this information from Toplink?
Edited by: user11973327 on Oct 4, 2009 7:19 AM

It is odd that Glassfish would throw an exception on marking the transaction for rollback, and ignore the thrown error. You might wish to check with Glassfish on this. What version of TopLink are you using? A similar issue on WLS was fixed in EclipseLink, you may wish to try the latest EclipseLink release.
You could also call flush() in your SessionBean to obtain the real database exception.
James : http://www.eclipselink.org : http://en.wikibooks.org/wiki/Java_Persistence

UCCX Script: Capture Original Called Number

Hi Folks,
I am not a expert in UCCX Environment, but I have to perform a basic script to capture original Called Number.
1) I have two Cisco 3825 Gateways connected over the PSTN with ISDN Signalling;
2) I am receiving the last four digits from my local provider (XXXX) and send that via voip dial peer to UCCX 10.1 to trigger 71011000. I am using the num-exp .... 71011000 to matching this dial peer.
My problem:
I need to play an annoucement that this prefix will change to another, but I have to delivery the call to CUCM extension number after that. I have the prompts yet, but how can I capture the original Called Number, since I have translated it using the num-exp commando on Cisco 3825 Gateway ?
Regards,
Luiz

I would create a separate dial-peer with the correct called number on the gateway, and add a trigger for that extension number in UCCX. Even if you have to translate it from 4 digits to an 8 digit number, you still have a unique called number coming into UCCX that you can use in your script.

Capturing error in Exceptions Block in a PLSQL Procedure

Hi,
I am creating a procedure where i need to update a table with some constraints.
i need to update atleast a million records with data from another table.
but here is the catch while updating million records, there may be some records which wont be vaild because of the constraints and cannot be updated and hence will give an error.
but in my procedure i want to write an exception block where it captures the error, ignores the error and keep coninuing the procedure and update all the remaining records instaed of getting hanged at the point of erorr.
How can i do this.
I know i can disable the constraints in the table.
but i want the constraints enabled, so that the errors are trapped and skipped and only the records that are valid are updated.
Can seomone help me write this exception block which does this function.
Thanks,
Philip.

Hi,
I used the exception bloack as u said.
i have a sample of 20 records and i know the 11th record is not valid and should be inserted in a different way from the rest 19 records.
so i ran the same query with the exceptions block.
but what happened, until 10th record everything was fine.
on the 11th record the execution went into the exceptions block and executed whatever was there in the exception block, but then the script just exited after exception block, it did not go back to fetch the remaining records from 12th unitl 20th.
How can i fix this.
Philip.

Capturing actual JDBC exception in BPM

I have a scenario wherein i am inserting data in sql server syncronously using the xml insert structure.
I have a BPM in place to do error handling, so that whenver any exception occurs, exception branch is executed,
however, in the exception branch am not able to detect wht the error was. Like was the error related to connectivity or related to DB that something failed because of BD constraint.
How can I trap the actual JDBC error in my exception handling..

Hi,
As you are using BPM and the call is Sync,you can get the response back if everything is fine. If not it will throw exception.
If you want to detect the Application errors, one option is using Stored Procedures in the DB side, so that it will respond you back with insertion failed bacause of duplicate entry etc...
If you want to handle , exceptions for connectivity issuses, you can make use of ALerts configured for JDBC adapters.. So you can create the Alerts like that.
To know more-
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm
Hope this helps
Regards,
Moorthy

Capturing trace of exception

Suppose following stored procedure:
PROCEDURE TEST_PRC
IS
BEGIN
RAISE VALUE_ERROR;
END;
If I call this procedure in Sql*Plus, I get:
BEGIN test_prc; END;
ERROR in line 1:
.ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SCH_PERSONEN.TEST_PRC", line 4
ORA-06512: at line 1
I can see exactly on which line the exception was raised: line 4.
I can see this linenumber also in Sql*Navigator or in de stacktrace of the SqlException in a Java-program.
But how can I catch this information to store in a logtable ?
When I change the stored procedure as follows, I get only the number of the line where format_call_stack is called.
But I want the number of the line where the exception is raised !!!
PROCEDURE TEST_PRC
IS
BEGIN
RAISE VALUE_ERROR;
EXCEPTION
WHEN VALUE_ERROR THEN
DBMS_OUTPUT.put_line(SUBSTR(DBMS_UTILITY.format_error_stack || DBMS_UTILITY.format_call_stack, 1, 255));
END;
The output in Sql*Plus is:
ORA-06502: PL/SQL: numeric or value error
----- PL/SQL Call Stack -----
object line object
handle number name
2ae87f14 7 procedure SCH_PERSONEN.TEST_PRC
291f19b4 1 anonymous block

Start at the top and work your way back. If the error was in a class you did not write, read thru the trace until you get to the class you wrote and figure out what might be wrong there that could have caused the problem. Other than that, Norweed is right in saying it is a case by case basis.

On Time Delivery Reporting - Capturing original promise date to customers?

We have a business metric that we use to track how well we do based on what we told our customers the delivery date was versus when we actually delivered the product(s). However, because of rescheduling, usually this original date that was "promised" is "lost" because of the new delivery date that is proposed. Therefore, we are unable to report on what we originally told the customer.
Does anybody have any suggestions or experience in this area? How do you report on how well you do in terms of delivering to your customers? How do you measure your "on time" delivery?
Thank you, Paul

you will not be in a position to track this data unless & otherwise you had recorded the schedule line details on a timely basis.
Say for an example, if you are scheduling the V_V2 or rescheduling option.
You go for a ztable where u have the VBBE/VBEP table details recorded seperately or you can save the details of this output on a local system (ideally we can have this data collected just before the run of V_V2 or rescheduling) and this can be used for evaluation / comparison on the original proposed date at the order level and the actual GI date recorded at the delivery level.
Regards
Ilango

How to capture the exact SQL exception for failure to connect to database

Hi, i would like to capture the exact exception for failure to connect to a Oracle 9i database (via JDBC). I learnt that there is specific code or exception that can be captured, so that a more proper error message can be thrown out like "Failure to connect to database" can be displayed. Anyone know how to go about doing it? thanks

That depends on your database vendor, I believe. (Unless there's a SQL standard for states and codes that I'm unaware of.)
Personally, I wouldn't worry about "catching" a particular code. (You've already caught the exception - that's the best you can do.) I'd report the error code and state and just look up what it means when I got one.
Hopefully you won't be catching exceptions. They're supposed to be rare. - MOD

How to capture exception in cursors

Hi,
I wnated to bulk collect say 100 record into global temporaary table,suppose if there is a exception in any of the record how could i handle it?
for example 2 records are throwing exception in this case i want remaining 98 to get processed and remaining 2 should be captured in the exception block.
Please share your suggestion

user13710379 wrote:
for example i used a global temporary table..lets be any table am populating using a bulk collect.My point was that BULK COLLECT is used to populated PL/SQL collections, not tables.
exceptions which i'm refering are like..in 100 records for 65 and 68th record some columns has junk values,so it wont get insert into the resultant table..as a result the bulk collect will fail.i want to handle this type of exception so that other 98 records gets inserted without rollingback.You could incorporate something into your SQL to 'correct' the data if it can be corrected, or you could incorporate something in the SQL to 'detect' where values are junk and not insert those rows, then have another SQL that picks out rows with 'junk' values so you can report on them.
There should be very little need to be loading data into expensive PGA memory or looping through row by row (slow by slow) for each record, to try and capture exceptions.
Better still do some SQL analysis on the data, determine what data has 'junk' in it and then get it fixed at source, and then implement something (or get whoever to do that) so that no more junk data can be entered.

Capturing Runtime Exception in ESB

How to capture the Runtime Exception in ESB?
Is there any special API to handle the Exceptions and Logging?

If it's a Sync call the caller should get SOAP fault and if it's Asynch then it goes into ESB error hospital logic. Depending on type of fault (Retriable vs Business) you can retry or view the error from ESB Console. What special exception handling you need?
Only logging available for now is Instance Tracking. Any sophisticated requirements need to come up with their own Auditing service.
Regards,
Rajesh

Cannot capture the exception generated by EJB components.

Hi, All:
I got a strange problem when developing EJB application under SAP WAS server. I developed an EJB as below:
public class UserAccountBean implements SessionBean{
     String getUserEmail(String accountID) throws SAPSystemException{
          if(error){
               throw new SAPSystemException("Specified user not found.");
Exception I defined as below.
public class SAPSystemException extends Exception {
@param message
     public SAPSystemException(String message) {
          super(message);
In client side I code as below:
public String getUserMail(String accountID){
     UserAccount bean = home.create();
     try{
          String email = bean.getUserEmail(accountID);
     }catch(SAPSystemException e){
          // do something here;
     }catch(Exception e){
          // do some other thing here;
It is strange that the SAPSystemException I throw out in the bean cannot be caught by the block catch(SAPSystemException e), it is only captured as general exception and it is said as UndeclaredThrowableException.
When I deployed EJB components and Web components together, the exception can be captured successfully. But when I deployed them separately, it has problem for exception capture. I think it must be the protocol problem. Before I only use RMI-IIOP but SAP WAS server using RMI-P4. Is anything I can do to solve this problem?
I packed the remote and home interface for the EJB and common classes like value objects and exceptions in both components. Is there anything I forgot to set for the deployment?
Thanks in advance.
Message was edited by: Weimin Guo
Message was edited by: Weimin Guo

Thank you very much Gregor. In fact, I already defined this throws exception in the remote object interface.
public interface UserAccount extends EJBObject {
     public String getUserEmail(String accountID) throws RemoteException, SAPSystemException;
This is application-specific interface and this mechanism works well in my previous in other application server.
I checked the SAP document and found if you using RMI-IIOP, you need to get the client package for your deployed EJBs and put in the path accessible by the WEB components. Based on this suggestion, I put the EJB jar file together with WEB application (Sure the EJB application still deployed in other host and JNDI point to that host. I remembered one book mentioned that if you don't want generate the client package from EJB containter, you can do it this way. For me, I just haven't found the way to get the client package with Administrator Tool it said.), It works!!!. I checked the remote object generated by home object, it is different with EJB jar file there or not. But in the document SAP said that only if you use RMI-IIOP you need do this way, for RMI-P4, you don't need that. Anyway, it seems that RMI-P4 use same way as RMI-IIOP(You only don't need narrow the home object after lookup).
I'll try to find how to get EJB client package from WAS server. For this is my first time to use SAP WAS Server, things a little strange.
Thank you very much for your great help.
Cheers.

Handling ABAP Exceptions in a Block

Hi,
If a background task calls an ABAP Class Method and that method throws a defined exception of type CX_BO_ERROR, I would expect to see a possible outcome for that exception that would allow me to handle the exception for the specific task. If I activate that outcome then an exception handling path will be displayed on the graphical representation which is taken if the exception is then raised by the method. If the outcome is disabled then the workitem goes to error.
If I want to catch these exceptions (for multiple tasks) in an enclosing block in order to handle them in a single, standard way, how do I achieve that? It does not seem possible to simply define the exception type in the enclosing block and then activate it in order to then be able to automatically catch any exceptions of a particular type that have their outcomes disabled in their individual tasks. It would appear that I have to activate the outcomes for each task and then raise it during with a Process Control item on the exception handling path of the task. This seems to defeat the object of having exception handling at the Block level. Is my understanding correct or am I doing something wrong?
Also, is it possible to capture the class exception object from the method call and store it in the Task Container (in order to get text & longtext details)?

Thankyou for both of your responses.
I understand that an individual ABAP Object or BOR method (call during an Activity) can raise an exception which can be handled as a separate outcome of that activity. However, if there are multiple Activity steps in the workfow that can all throw similar exceptions and I want to react to all of those exceptions in a uniform way, it seems excessive to have to handle each exception individually for each Activity in order to do the same thing (e.g. I may just want to send a standard email to someone or trigger another workflow event).
I may have misunderstood things but I thought that the purpose of the Block step was to be used as a kind of TRY..CATCH mechanism that will allow exceptions to thrown to the Block by enclosed Activities without the need for enabling outcomes at the Activity level. I thought it would be possible for the exception type to be defined in the Block properties so that all exceptions of that type could be handled at a higher level by a single Block outcome (regardless of which enclosed Activity threw it). If this is the case then I do not see the point in having to define individual outcomes for each activity within the Block.
That said, I cannot seem to get it to work without enabling the outcome for each activity and using a Process Control step to raise the exception to the Block (which seems to defeat the object because I have, in fact, just handled the exception!). The reason for my original posting is to verify whether or not what I am trying to do is possible and to find out what I doing wrong with regards to Block configuration.
Kind Regards
Simon.

Logging all exceptions

Hi,
I am working on a project where we extend an application built by a third party vendor. I've spent hours trying to determine the cause of some exceptions. The vendor transforms exceptions thrown by the application server or Oracle into their own exceptions. In this process they tend to drop the original cause or message and replace it by a somewhat vague "Database problem probably due to RI violation." not mentioning what constraint caused it. After a long debugging session I managed to figure it out.
I was wondering if I could somehow log all exceptions thrown in the application. I was thinking of some AOP kind of way. Since I don't have the code of the core product classes, I would have to add something at runtime? I believe AspectJ is out of the question since I cannot recompile the vendors code. Spring AOP is out of the question, because I believe it can only add extra behaviour to beans in the application context. We don't use spring at all, so no beans available.
Is there any other way to get to the hidden exceptions or should I just forget about this? I'm going to try to solve some part with jdbc logging first.
Thanks for any input.

garava wrote:
I guess if you don't have the code with you, there is no point in exploring the exceptions. Basically they have already catched them.There actually is a point in exploring them: If Oracle throws an exception "Unique constraint YOUR_UNIQUE_CONSTRAINT violated." and all you see is "There was an exception", then there is a good point in getting that exception information. It could be some parameter that you pass to the system that might cause this problem. The way I did it now was telling the eclipse debugger to break at every exception. I honestly hadn't expected to see that application throw so many internal exceptions!
georgemc wrote:
You could slip your own JDBC driver in between the app and the real JDBC driver, give you a bit more insight into what's going on. Write some classes that implement the basic JDBC interfaces, do some logging or whatever, then pass the calls on to your "real" JDBC driver classes. There's at least one open-source project around that already does this, but I can't remember the name of it off the top of me headThanks George, I might do that if I get enough time for it. I found [this article|http://www.rgagnon.com/javadetails/java-0411.html] where they set a logWriter on a DriverManager. This might be enough to capture the jdbc exceptions.

Capturing JVC GR-PD1 Hi-Res format to FCP

The problem:
I unintentionally recorded a lot of footage in Hi-Res format on my JVC GR-PD1. When I capture the footage in FCP it plays the video track at double speed and audio at normal speed and the sync is, not surprisingly, scuppered. When I reduce the video play speed to 50% (effectively doubling the length of the video track) the video track plays just fine and I can sync the audio but, of course, I only have audio for the first half of the footage!
This is driving me bonkers!
The background:
If understand the camera user manual correctly, the format captures video at 25fps but audio at 50fps. When the footage is played back on the camera everything appears fine because the "magic in the box" plays both video and audio at 50fps. I have captured the footage to a PC successfully using the JVC-supplied MPEG capture and audio converter utility. This works well except that it leaves me with a "m2t" file that (when transferred to the Mac obviously) is not recognised by FCP. I have tried converting the ".m2t" file to DV using DVdrop but the synced ".m2t" file that goes in comes out unsynced (exactly the same result as I get by capturing in FCP except it's in NTSC which doesn't help matters because I'm working in PAL!)
So, how do I go about capturing the JVC Hi-Res format in FCP so that the video and audio tracks match?
All creative thoughts and practical solutions gratefull received.
Regards,
Bowjey

I would read the manual to better understand the recording options if I were you.
I searched for a manual online for your camera and couldn't find it. If you could post a link I will read it and to try and help you.
Here is a link..... M2t to Quicktime
http://www.squared5.com/
Good Luck
Z1

How to access custom exception in client side in web services?

I have an interface and implementation of a java web services. One method in it throws a custom exception indicating the error type (authrization fails, db connection lost, etc...). But in the generated proxy file, the catched exception for the correspondent method becames java.lang.Exception. I check the code and found the actual thrown exception is com.apache.soap.SOAPExcetion. In the client code, I printed out all the SOAPExcetion and related Fault messages but could not find my original custom exception info. I need this custom exception to be accessed to the client so the client knows what's wrong.

for current user, SPGroup.ContainsCurrentUser
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spgroup.containscurrentuser.aspx
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Capture Origin of Exception: PageLifecycle

Similar Messages

Maybe you are looking for