Advantage of Java Exceptions over C error handling.

I understand the advantages of Java Exception handling(as against C) when it comes to the ability to define exclusive Exception types or reuse exceptions, documentation benefits of the throws clause, advantages due to OO etc. But some people say that using exceptions in Java it is possible to recover from an exceptional condition and that's an advantage over how errors are dealt in C.
Is that really an advantage? (I mean is that true?)AFAIK in C errors can be handled using perror or errno.h. For every error code generated there seems to be a description. And by checking the return values from functions we could see if there had been an exceptional condition and if there really had been one take appropriate action and recover from the error. So how is it that Java can recover from exceptions while in C it is not possible to recover from errors?
Thank you very much.

I'm waiting in my cold cell when the bell begins to chime
Reflecting on my past life and it doesn't have much time
Cos at 5 o'clock they take me to the Gallows Pole
The sands of time for me are running low
When the priest comes to read me the last rites
I take a look through the bars at the last sights
Of a world that has gone very wrong for me
Can it be there's some sort of error
Hard to stop the surmounting terror
Is it really the end not some crazy dream
Somebody please tell me that I'm dreaming
It's not so easy to stop from screaming
But words escape me when I try to speak
Tears they flow but why am I crying
After all I am not afraid of dying
Don't believe that there is never an end
As the guards march me out to the courtyard
Someone calls from a cell "God be with you"
If there's a God then why has he let me die?
As I walk all my life drifts before me
And though the end is near I'm not sorry
Catch my soul cos it's willing to fly away
Mark my words please believe my soul lives on
Please don't worry now that I have gone
I've gone beyond to see the truth
When you know that your time is close at hand
maybe then you'll begin to understand
Life down there is just a strange illusion.
Yeah, yeah, yeah, Hallowed be thy name
Yeah, yeah, yeah, Hallowed be thy name

Similar Messages

Phonebook-S java exception-RuntimeExcepyion(severe error)

Hi,
I am experiencing an error when I try to add or edit a contact on the phonebook. Anyone with the solution? Below is the event log info on the error;
Name: RuntimeException
GUID: 9c3cd62e3320b498
Time: Apr 14, 2012 17:41:29
ApplicationRegistry.getOrWaitFor(0x103243b6b5a66317) owner died Thread[Thread-578333696,5]
net_rim_cldc-8(4BE1E8C0)
ApplicationRegistry
getOrWaitFor
0x81E3
net_rim_bb_qm_msn-11(4F6C9271)
Smileys
getEmoticonStringPattern
0x9C8
net_rim_bb_qm_msn-11(4F6C9271)
Smileys
getEmoticonPatternContainer
0x9F8
net_rim_bb_qm_msn(4F6C9271)
WLMIMIDModelImpl
getField
0x436D
net_rim_bb_framework_api-3(4BE1E919)
EditorUsingRIMModelFactory
<private>
0xF49
net_rim_bb_framework_api-3(4BE1E919)
EditorUsingRIMModelFactory
insertModel
0x91A
net_rim_bb_framework_api-3(4BE1E919)
EditorUsingRIMModelFactory
populateModels
0xA6A
net_rim_bb_framework_api-3(4BE1E919)
EditorUsingRIMModelFactory
setModel
0x7EF
net_rim_bb_addressbook_app-1(4BE21577)
EditAddressCardScreen
setAddressCardModel
0x4C47
net_rim_bb_addressbook_app-1(4BE21577)
AddressCardVerb
invoke
0x2AD7
net_rim_bb_addressbook_app-2(4BE21577)
AddressBookListUI$NewAddressBookEntryVerb
invoke
0x26F1
net_rim_bb_addressbook_app-2(4BE21577)
AddressBookListUI
doVerbAction
0xEFB
net_rim_bb_addressbook_app-2(4BE21577)
AddressBookListUI
invokeAction
0x1505
net_rim_cldc-12(4BE1E8C0)
Screen
navigationUnclickUnhandled
0x8B79
net_rim_cldc-12(4BE1E8C0)
Screen
dispatchNavigationEvent
0x736F
net_rim_cldc-13(4BE1E8C0)
UiEngineImpl
processMessage
0x758A
net_rim_cldc-8(4BE1E8C0)
Application
<private>
0x29E2
net_rim_cldc-8(4BE1E8C0)
Application
processNextMessage
0x1AEF
net_rim_cldc-8(4BE1E8C0)
Application
enterEventDispatcher
0x1A2C
net_rim_bb_addressbook_app(4BE21577)
AddressBookApp
main
0x1C6
Solved!
Go to Solution.

Hello !
Try the following:
Simply delete all the Messenger apps (Yahoo, MSN or Live) which you might have upgraded recently / delete apps which were recently installed before the error which actually started occuring .
After that unplug the battery while the phone is still "on" and restart the phone.
In fact I had deleted a whole bunch of apps to facilitate my OS upgrade as I did not have enough memory on my Device.
This not only helped solve my above mentioned problem but also made my phone restart in less than 3 minutes (the earlier reboot was done in not less than 15 minutes !!).
Therefore my conclusion as from the above incidents is to keep your apps in the bare minimum so that your phone performs to the best.
Hope this resolves your Problem!
If your problem has been resolved then would request you to Click on "Like" and accept as "Solution" so that other Advisors doesnt invest their time on this Message anymore.
Thanks.

Can error handling framework use fault policies and BPEL catch blocks

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

As part of an integrated customer solution that makes substantial use of SOA Suite (including OSB, BPEL, Mediator, etc) we are in the process of designing an “Error Hospital” subsystem to expose a web service API specifically for BPEL services and/or the OSB layer to call whenever they encounter an exception which they cannot handle so that the appropriate user is notified of the error (via email) and the error is recorded (in an appropriate common fault format, with error codes elaborated into more meaningful descriptions, etc) within OEM, immediately prior to returning the exception to the caller.
The problem we have experienced in our design is as follows:
•     We have an error handling service to be called, inside the BPEL catch blocks, when an error occurs to notify the appropriate user, via email, that an error has occurred;
•     We also use the error handling XML fault-policies so that we can recover from an error using OEM (via human intervention);
•     The error service needs to be called before the process is suspended (waiting for human intervention) so the email notification and error message formatting occurs BEFORE the recovery action. Unfortunately the fault policies trigger BEFORE the error handler is able to transform the error into the appropriate format and notify the user so the error recorded is not the reformatted one and the user is never notified.
The key question is how can a BPEL, upon catching an exception, invoke the error handling service and AFTER that send the error to OEM (and have the process suspended).
It seems the two mechanisms "cannot play nicely together"

Error handle request; Root exception is: java.lang.NoSuchMethodError

Hello Guys,
I am running EBS 11i, rdbms 10g on OEL4. After applying a bunch of patches to resolve some IE issues I ran into an error:
"FRM-41072: Cannot create group ACTION_REC_GROUP" when trying to cancel a PO.
An SR directed me to apply patch 8286920 which indeed fixed the FRM-41072 error. After this patch "Logon to Oracle Applications Manager" is not possible as the page gives me :
Error handle request; Root exception is: java.lang.NoSuchMethodError: oracle.apps.fnd.security.AolSecurity.userPwdHash(Ljava/lang/String;)Ljava/lang/String;
MOS thinks that patch 8286920 didn't break OAM but I don't think so since this is only happening on my DEV and TEST systems on which I have applied the patch. PROD, wihtout the patch, is accessible through OAM just as usual?
Any thouths?
Thank you
Mathias

Did you apply all patches mentioned in the following docs?
FRM-41072 - Unable to Cancel Purchase Order or Purchase Order Line or Release [ID 947402.1]
Change Tax Code in the Purchase Order Gets Error - Could not reserve record (2 tries) Keep trying [ID 956047.1]
Autocreate Process Does Not Default Purchase Order Form As The Active Window After PO Is Created - Does Not Come To The Front [ID 1055623.1]
Did you bounce all the services and see if you ca reproduce the issue?
What about clearing the server cache files? -- How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite? [ID 742107.1]
Can you find any errors in the database/apache log files? Any invalid objects?
If you have verified all the above please update the SR with the error you have after applying that patch.
Thanks,
Hussein

Bursting with JAVA APIs / MultiThreading / Errors Handling

We are trying to use the bursting JAVA APIs 10.1.3.3.1 Standalone) to burst huge XML files and generate PDF Files from RTF templates. Here are a list of our issues with this feature:
1. We have some problems catching the errors when bursting. We have tried to use the "oracle.apps.xdo.common.log.Logger" class, but it is not always reacting like we think it should. Could you please give us an exemple of a clean bursting error catching or a brief description of how we could do it. We have a lot of difficulties to find information about using the JAVA APIs of BIP.
2. Is it a clean way of catching the bursting errors to use the "oracle.apps.xdo.common.log.Logger" class?
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?

1. Check tim d. blog, you can use the bursting listners to get the errors. It's also in the documentation.
First, on every exception, the Bursting APIs are dumping the error in the Logger. So I can't see how we can use the listeners to catch these. We can check the hasExceptions on the Logger but still, we have some problems with this. When we deploy our application as a MDB (Message driven bean), it seems that once the hasException flag has been raised, if we call the MDB again, it is still up. Is there documentation about that Logger class? Also, I'm worried that we won't be able to call our MDB twice to run simultaneously 2 different bursting process since it seems the Logger is something static, keeping every exception in memory... That's bad.. And show me where you have found documentation about this. All I see in documentation is how to call the DocumentProcessor in a couple of lines. I don't see anything about a clean way to catch errors.
2. Yes/No/Depends. I think it's fine. If your changing the logger options in your program that could come back to haunt you.
I guess so, I'm not changing anything and its already haunting me...
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
Even worst, when we deploy the component has an MDB, when the error happens, it kills the whole oc4j container... please correct this quick.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?
We got an answer from the dev team which is to add two properties to the document processor, something like:
enable-multithreading: true
thread-count: >2
We did that and what we got is that the process started and it got stuck in a dead lock at the first document processing. How nice! :)
We got a milestone in March and I'm really worried about all those problems... Not enough documentation, a pretty bad error handling, errors making crash the whole oc4j container, Logger seems not to be handling simultaneous calls/ threads, not even handling two subsequent calls... etc.
If anyone has the magic answer, it would be pretty welcomed!
Thanks

Java exception appear during file adapter to handle large xml

Hi,Guys,
I am using file adapter to poll one folder of my local.one get input.xml,then do something,then write out output.xml.
input.xml format is :
<mes:DataRequestIns xmlns:mes="http://xml.netbeans.org/schema/MessageDefined">

     <mes:DataIns>
          <mes:address>Ang Mo Kio 5,63 street</mes:address>
          <mes:birthday>14/12/1970</mes:birthday>
          <mes:firstName>Sing1</mes:firstName>
          <mes:gender>0</mes:gender>
          <mes:ID>1001</mes:ID>
          <mes:lastName>NorthMan</mes:lastName>
          <mes:postcode>2002</mes:postcode>
          <mes:telephone>6665222</mes:telephone>
          <mes:surname>Sur</mes:surname>
          <mes:status>single</mes:status>
          <mes:location>sgp</mes:location>
          <mes:HP1>11111</mes:HP1>
          <mes:HP2>22222</mes:HP2>
          <mes:passport>123456878</mes:passport>
          <mes:company>ST</mes:company>
          <mes:department>TO</mes:department>
          <mes:occupation>engineer</mes:occupation>
          <mes:experience>10</mes:experience>
          <mes:level>2</mes:level>
          <mes:certificate>high</mes:certificate>
          <mes:specialisation>computer</mes:specialisation>
          <mes:staffNumber>1020</mes:staffNumber>
          <mes:fax>00200</mes:fax>
          <mes:email>[email protected]</mes:email>
          <mes:national1>sgp</mes:national1>
          <mes:national2>sgp</mes:national2>
          <mes:interestingField>bpel</mes:interestingField>
          <mes:national>earth</mes:national>
          <mes:oversea>yes</mes:oversea>
     </mes:DataIns>
<mes:DataIns>
</mes:DataIns>
</mes:DataRequestIns>
if my input.xml contain less than 1000 records,then it's working,once greater than 1000,then appear exception.for normal case ,must have more than 10000 records need to handle,and file size is 11.2MB.
so,Does any other way or how to use file adapter to handle it ?
thank you
exception :
SEVERE: An error occured while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Failed to obtain DB connection from data sou
rce 'soaNonManagedDS': java.sql.SQLException: Could not retrieve datasource via
JNDI url 'jdbc/SOALocalTxDataSource' weblogic.jdbc.extensions.ConnectionDeadSQLE
xception: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.
ResourceException: Could not create pool connection. The DBMS driver exception w
*as: Socket read timed out [See nested exception: java.sql.SQLException: Could no*
*t retrieve datasource via JNDI url 'jdbc/SOALocalTxDataSource' weblogic.jdbc.ext*
*ensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadExc*
*eption: 0:weblogic.common.ResourceException: Could not create pool connection. T*
*he DBMS driver exception was: Socket read timed out]*
at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(Jo
bStoreCMT.java:167)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLoc
k(JobStoreSupport.java:3652)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobSt
oreSupport.java:2654)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:
*235)*
Caused by: java.sql.SQLException: Could not retrieve datasource via JNDI url 'jd
bc/SOALocalTxDataSource' weblogic.jdbc.extensions.ConnectionDeadSQLException: we
blogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceExce
ption: Could not create pool connection. The DBMS driver exception was: Socket r
ead timed out
another exception:
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.
message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Ro
lledback.: weblogic.transaction.internal.TimedOutException: Transaction timed ou
t after 302 seconds
BEA1-3468FC5E3C698D2A82F7
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTran
sactionImpl.java:1742)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTim
edOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(Transacti
onManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(Ser
verTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
*; nested exception is: weblogic.transaction.internal.TimedOutException: Transact*
ion timed out after 302 seconds
BEA1-3468FC5E3C698D2A82F7
This error contained an exception thrown by the message handler.
Edited by: aris yu on Dec 27, 2009 11:55 PM

Hi,
we have to explicitly mention batch while configuaring file adapter.
i.e. in step 5 : Check file contains multiple messages and mention how many messages u want to process in a batch.
i.e. if you have 10000 msgs in ur file mention the size as 500. Then it will read 10000 records in 20 batches.
Now while writing to a file use Append=true property.
U have to add this property to fileadapter.wsdl (in jca:operation tag) which will be created when u complete the configuaration of file adapter with write operation.
Regards
PavanKumar.M

Is there a way to handle custom java exception in OSB?

For example, i created a exception that extends RuntimeException.
My exception has a new field called "code".
I want to handle this exception in Oracle Service Bus process and retrieve this code to throws another exception with a XML structure that includes the code.
Is there a way to do that ?
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382515</con:errorCode>
     <con:reason>Callout to java method "public static org.apache.xmlbeans.XmlObject ...</con:reason>
     <con:java-exception xmlns:con="http://www.bea.com/wli/sb/context">
         <con:java-content ref="jcid:33a6c126:14006f3df18:-7fd9"/>
     </con:java-exception>
     <con:location xmlns:con="http://www.bea.com/wli/sb/context">
         <con:node>optmusPipeline</con:node>
         <con:pipeline>optmusPipeline_request</con:pipeline>
         <con:stage>processStage</con:stage>
         <con:path>request-pipeline</con:path>
     </con:location>
</con:fault>
it is not enough to recover the information i needed.

Hi Sandro,
I've got the same situation. I agree that returning xml from function is not a best choice as you have to manually check if return status is an error or not. Processing exception in error handler is better and this is how I do it:
I am doing a java callout to a function that can throw exception. Then I add ErrorHandler to stage containing this callout (all the exception are caught here).
In the error handler I check if $fault/ctx:java-exception is not null. If not then I pass thrown exception to my utility function that converts it to xml similar to yours:
import org.apache.xmlbeans.XmlException;
import org.apache.xmlbeans.XmlObject;
public static XmlObject exceptionToXML(Throwable exception)
throws XmlException {
String xmlString = exceptionToString(exception);
return XmlObject.Factory.parse(xmlString);
public static String exceptionToString(Throwable exception) {
String cause = "";
if (exception.getCause() != null) {
cause = exceptionToString(exception.getCause());
return String
.format("<exception><name>%s</name><description>%s</description>%s</exception>",
exception.getClass().getName(), exception.getMessage(),
cause);
Calling exceptionToXML with $fault/ctx:java-exception/ctx:java-content returns:
<exception>
     <name>pl.app.MyException</name>
     <description>Exception message</description>
</exception>
Then you can check the exception class (IF action: $exception/name/text() = "pl.app.MyException") and handle it accordingly.
Good luck,
Krzysiek

Error: ORA-29532: Java call terminated by uncaught Java exception:

Anyone have this similar problem of
ORA-29532: Java call terminated by uncaught Java exception:
javax.xml.rpc.soap.SOAPFaultException: Caught exception while handling request:
deserialization error: XML reader error: unexpected character content:
"A"
The service is running fine in a browser and returns the date. When I run it using the PL/SQL it has the error mentioned above.
I am running the following:
CREATE OR REPLACE FUNCTION GetDate_wb( p_dummy IN VARCHAR2 )
RETURN DATE
AS
l_service sys.UTL_DBWS.service;
l_call sys.UTL_DBWS.call;
l_result ANYDATA;
l_wsdl_url VARCHAR2(1024);
l_service_name VARCHAR2(200);
l_operation_name VARCHAR2(200);
l_input_params sys.UTL_DBWS.anydata_list;
l_port sys.UTL_DBWS.qname := 8988;
BEGIN
l_wsdl_url := 'http://org-lblakisa1:8988/BPEL_OD-LoginWS-context-root/getDate1SoapHttpPort?WSDL';
l_service_name := 'getDate1';
l_operation_name := 'getDate';
l_service := sys.UTL_DBWS.create_service (
wsdl_document_location => URIFACTORY.getURI(l_wsdl_url),
service_name => l_service_name);
l_call := sys.UTL_DBWS.create_call (
service_handle => l_service,
port_name => NULL,
operation_name => l_operation_name);
l_input_params(1) := ANYDATA.ConvertVarchar2(p_dummy);
l_result := sys.UTL_DBWS.invoke (
call_handle => l_call,
input_params => l_input_params);
sys.UTL_DBWS.release_call (call_handle => l_call);
sys.UTL_DBWS.release_service (service_handle => l_service);
RETURN ANYDATA.AccessDate(l_result);
END;
/

Problem is resolved... We had a version issue in that 10.1.3 web service is not compatible. 10.1.2 worked.

CORE4007: Internal error: Unexpected Java exception thrown (java.lang.NullP

Hi,
Currently we have a custom devoloped Java application deployed in oracle iplanet webserver 7 with JDK 1.6. I am receiving the below errors. The application is not stable. It gives a 500 internal error sometimes when browsing. When i checked the error log. Below is the message.
CORE4007: Internal error: Unexpected Java exception thrown (java.lang.NullPointerException, no description), stack: java.lang.NullPointerException
Could you please throw some light on this.

You need to fix your custom developed app since it is causing the errors and instability. Tell the developers to properly verify the input data and improve their exception handling so you get better error messages that tells you what went wrong.

Conflict Error Handler Exception in Cluster

          Hi
          We bind some objects using rebind method to the JNDI in our weblogic servers.
          If we run one instance of weblogic server no problem but if we start another one
          server in the cluster it throughs conflict error handler exception. More over
          if we refresh one object instance in one server (by rebind) the new changes in
          the object doesn't reflect in other servers.


If you bind non clusterable objects in the jndi from two servers then you
          will run into conflicts.
          Basically in a cluster, two servers cannot provide the same service unless
          it is clusterable.
          WLS assumes that everything you bind into jndi is a service.
          -- Prasad
          "BSIL" <[email protected]> wrote in message
          news:3b94f93a$[email protected]..
          >
          > Hi
          > We bind some objects using rebind method to the JNDI in our weblogic
          servers.
          > If we run one instance of weblogic server no problem but if we start
          another one
          > server in the cluster it throughs conflict error handler exception. More
          over
          > if we refresh one object instance in one server (by rebind) the new
          changes in
          > the object doesn't reflect in other servers.

Error handling notification type=Platform,Domain=java.lang,subType=GC

I'm seeing this error over and over. Odd that 17 and 18 are not listed as members.
-Andrew
MemberId|ServiceVersion|ServiceJoined|MemberState
    2|3.7.1|2012-03-28 08:59:53.744|JOINED,
    4|3.7.1|2012-03-28 04:42:03.799|JOINED,
    6|3.7.1|2012-03-28 05:22:21.955|JOINED,
    7|3.7.1|2012-03-28 05:55:56.571|JOINED,
    8|3.7.1|2012-03-28 05:55:56.584|JOINED,
    9|3.7.1|2012-03-28 06:42:46.461|JOINED,
    10|3.7.1|2012-03-28 06:00:00.698|JOINED,
    11|3.7.1|2012-03-28 08:20:01.535|JOINED,
    12|3.7.1|2012-03-28 08:20:02.32|JOINED,
    13|3.7.1|2012-03-28 08:21:12.046|JOINED,
    14|3.7.1|2012-03-21 09:10:59.991|JOINED,
    16|3.7.1|2012-03-21 09:11:03.034|JOINED,
    20|3.7.1|2012-03-21 09:10:59.236|JOINED,
    22|3.7.1|2012-03-21 09:11:00.273|JOINED,
    23|3.7.1|2012-03-21 09:11:02.329|JOINED
RecycleMillis=1200000
RecycleSet=MemberSet(Size=0
TcpRing{Connections=[23]}
IpMonitor{AddressListSize=1}
2012-03-28 09:00:04.395/11.378 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Service Managemen
t joined the cluster with senior service member 14
2012-03-28 09:00:04.659/11.642 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18
2012-03-28 09:00:04.677/11.660 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=17
2012-03-28 09:00:04.693/11.676 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18
2012-03-28 09:00:04.706/11.689 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=17
Map (?):
2012-03-28 09:00:04.875/11.858 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18

No ideas on a cause or solution for this? I only saw it once and I don't know how to reproduce it.
-Andrew

"Authentication Exception due to incorrect handler" error

I install Java Enterprise Platform 2003Q4
In current time i have problem in PS 6.2 with creating multiple organisation on single portal server.
I make procedures two times, from http://docs.sun.com/source/816-6748-10/dsameadm.html#wp27088
- chapter "Creating a New Portal Organization Quick Start " and i have strange message:
"Authentication Exception due to incorrect handler." on URL http://server:port/amserver/UI/login?org=neworg.
But, PS normally log in to user's area on newly created organisation from Identity server console;

Hi all,
I also had a same problem when i was testing Following SSO scenario.
I had deployed my two web application on physically separate machines named A, B.
My Sun Access Manager (IDP) was on Machine say C.
while accessing any page of web Application A from machine B. According to SSO mechanism he asks for SAM login.
Hence Login page of SAM was not rendered properly.After Giving Credentials SAM thrown above error.
I Just inserted the SAM URL. i.e http:///SAMidp in the Trusted sites of Browser.
And It worked fine..
Thanks
Manohar

Handling/passing Java exceptions to JavaFX

My Java class has a try/catch statement indicating a communication error to MySQL server. I want to add a user-friendly dialog box in my JavaFX application in the event my java class cannot access the database.
What's the best way of handling Java exceptions within JavaFX?
Cheers!

Rethrow an exception and catch it in the call in JavaFX code?

CCI exception error handling

hi,
I am a running a java program using CCI Non-Managed environment to connect to CICS commarea program.....
in that when i run the Java code without my gateway daemon CTG interface to CICS. I get an error when CTG(CICS Transaction gateway) service has not been started.
The error is in my ConnectionFactory class:
12:15:02:806 : [main:17ace8d] : Exception Logged by: com.ibm.connector2.cics.EC
IManagedConnection
12:15:02:822 : [main:17ace8d] : javax.resource.spi.CommException: CTG9631E Error
occurred during interaction with CICS. Error Code=: ECI_ERR_NO_CICS
12:15:02:822 : [main:17ace8d] : at com.ibm.connector2.cics.ECIManagedCon
nection.checkReturnCode(Unknown Source)
12:15:02:822 : [main:17ace8d] : at com.ibm.connector2.cics.ECIManagedCon
nection.call(Unknown Source)
12:15:02:822 : [main:17ace8d] : at com.ibm.connector2.cics.ECIConnection
.call(Unknown Source)
12:15:02:822 : [main:17ace8d] : at com.ibm.connector2.cics.ECIInteractio
n.execute(Unknown Source)
12:15:02:822 : [main:17ace8d] : at Ccitest.flowrequest(Ccitest.java:113)
12:15:02:822 : [main:17ace8d] : at Ccitest.main(Ccitest.java:219)
How do i handle this exception????kindly suggest........

This is my code:
import com.ibm.connector2.cics.ECIManagedConnectionFactory;
import com.ibm.connector2.cics.ECIManagedConnectionFactory;
import com.ibm.connector2.cics.ECIInteractionSpec;
import javax.resource.cci.ConnectionFactory;
import javax.resource.cci.Connection;
import javax.resource.cci.Interaction;
import javax.resource.ResourceException;
import java.io.UnsupportedEncodingException;
import javax.resource.cci.LocalTransaction;
import java.io.IOException;
import java.io.*;
import java.lang.*;
import java.util.*;
import java.lang.String.*;
import java.text.*;
public class Ccitest
     static String message=null;
     static String err=null;
     static StringBuffer sb1 = null;
     public String s1;
     public static int iValidationFailed = 0;
     static StringBuffer sb = null;
     public static class GenericRecord implements javax.resource.cci.Record,javax.resource.cci.Streamable
          private byte commarea[]=null;
          public GenericRecord()
               super();
          public GenericRecord(byte[] comm)
               setCommarea(comm);
          public Object clone() throws CloneNotSupportedException
               return super.clone();
          public void setCommarea(byte[] comm)
               try
                    read(new java.io.ByteArrayInputStream(comm));
               catch (java.io.IOException ioe)
          public byte[] getCommarea()
               return commarea;
          public void read(java.io.InputStream in) throws java.io.IOException
               commarea=new byte[in.available()];
               in.read(commarea);
          public void setRecordName(String arg1)
          public String getRecordName()
               return null;
          public void setRecordShortDescription(String arg1)
          public String getRecordShortDescription()
               return null;
          public void write(java.io.OutputStream out) throws java.io.IOException
               out.write(commarea);
               out.flush();
public void flowrequest(String str,StringBuffer sb)
     //Create and set values for ECI managed connection factory
          try
          ECIManagedConnectionFactory mcf= new ECIManagedConnectionFactory();
          mcf.setConnectionURL("localhost");
          mcf.setPortNumber("2006");
          mcf.setServerName("CICS1");
          mcf.setUserName("dsrm022");
          mcf.setPassword("dsrm022");
          //mcf.setTranName("M22I");
          //System.out.println("MCF"+mcf);
     //Create a connection factory connection object
          ConnectionFactory cxnf=(ConnectionFactory)mcf.createConnectionFactory();
          //System.out.println("cxnf"+cxnf);
          Connection cxn= cxnf.getConnection();
          //System.out.println(cxn);
     //create an interaction with CICS to start program ECIPROG
          Interaction ixn= cxn.createInteraction();
          ECIInteractionSpec ixnSpec= new ECIInteractionSpec();
          ixnSpec.setInteractionVerb(ixnSpec.SYNC_SEND_RECEIVE);
          LocalTransaction tran = cxn.getLocalTransaction();
          ixnSpec.setFunctionName("M22AP05");
          ixnSpec.setTPNName("M22I");
          //System.out.println(ixnSpec);
     //Create a new record for handling the COMMAREA byte array
          GenericRecord record = new
          GenericRecord((str).getBytes("IBM037"));
          System.out.println("Comm in: "+new String(record.getCommarea(),"IBM037"));
     //Finally execute and flow the request to CICS
     boolean res;
          res = ixn.execute(ixnSpec, record, record);
//code added by shiyamala for checking the connection messages-22/oct/07
          //message = new String(record.getCommarea(), "IBM037");
          //sb = new StringBuffer(message);
          //System.out.println("res"+res);
          if(res)
               message = new String(record.getCommarea(), "IBM037");
          sb = new StringBuffer(message);
          System.out.println(sb);
          else
                    message = "null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"ECI flow Error";
                    sb = new StringBuffer(message);
                    // System.out.println(sb);
     //Close the interaction and the connection
          ixn.close();
          cxn.close();
          System.out.println("Comm out: "+new String(record.getCommarea(),"IBM037"));
          //System.out.println("res after comm out"+res);
catch (ResourceException re)
     //System.out.println("Error: "+re.getErrorCode());
     int errorcode =      Integer.parseInt(re.getErrorCode());
     //System.out.println("Errorcode: "+re.getErrorCode());
          switch(errorcode)
                         case     (-3):
                                   message = "null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"CICS not available";
                                   sb = new StringBuffer(message);
                                   // System.out.println(sb);
                                   break;
                         case     (-7):
                                   message = "null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"You are not authorized to run the transaction";
                                   sb = new StringBuffer(message);
                                   // System.out.println(sb);
                                   break;
                         case     (-4):
                                   message = "null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"CICS died";
                                   sb = new StringBuffer(message);
                                   // System.out.println(sb);
                                   break;
                         case     (-6):
                                   message = "null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"Response Timeout";
                                   sb = new StringBuffer(message);
                                   // System.out.println(sb);
                                   break;
                         default:
                                   message = "null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"null"+"~"+"ECI flow Error";
                                   sb = new StringBuffer(message);
                                   // System.out.println(sb);
     catch (Exception ioe)
               System.out.println("test");
public class CommException extends ResourceException
               public CommException(String message, String errorCode)
                    super(message, errorCode);
     public static void main(String args[])
               int i;
               String sNextToken;
               String s=" ";
               String customerno     =     args[0].toUpperCase();
               //This is to append the commarea space length
               int     temp1 = 500;
               System.out.println("Length of temp1: "+temp1);
               for(int j=0;j<temp1;j++)
                    s=s+" ";
               //System.out.println("spaces:"+s);
               String str = customerno+s;
               Ccitest c = new Ccitest();
               c.flowrequest(str,sb);
               sb = new StringBuffer(message);
System.out.println("comm out flow : "+sb);
               String s1 = new String();
               s1 = String.valueOf(sb);
               String s2 = s1.trim();
               StringTokenizer st = null;
               String result=null;
               Vector oActVector = new Vector();
               st = new StringTokenizer(s2,"~#~");
                    while(st.hasMoreTokens())
                              sNextToken = st.nextToken();
                              System.out.println("sNextToken==>"+sNextToken);
                              oActVector.addElement(sNextToken);
                              //System.out.println("length:"+sNextToken.length());
          String CustomerId                    =     (String) oActVector.elementAt(0);
          String CompanyName                    =     (String) oActVector.elementAt(1);
          String Website                         =     (String) oActVector.elementAt(2);
          String Industry                         =     (String) oActVector.elementAt(3);
          String phone                         =     (String) oActVector.elementAt(4);
          String Zip                              =     (String) oActVector.elementAt(5);
          String mesg                         =     (String) oActVector.elementAt(6);
          System.out.println("String CustomerId:"+CustomerId);
          System.out.println("String Company Name:"+CompanyName);
          System.out.println("String Website:"+Website);
          System.out.println("String Industry:"+Industry);
          System.out.println("String phone:"+phone);
          System.out.println("String Zip:"+Zip);
          System.out.println("String mesg:"+mesg);
}

File Adapter - Exception / Error handling

We are using File Adapter in BPEL process to read multiple records from the file. Additionally, we have also handled rejectedMessageHandlers & fatalErrorFailoverProcess exception to lunch custom BPEL process. The process is running fine and also successfully launches custom handler processes too.
Need help / direction in addressing following issues.
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process.
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also.
Are we missing any set up ? We are on 10.1.3.1
thanks
-Yj
Sample Log file:
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::init - Initializing the JCA activation agent, processId='bpel://localhost/default/TestFileRead~1.0/
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:
process='bpel://localhost/default/TestFileRead~1.0/'
domain='default'
WSDL location='Read.wsdl'
portType='Read_ptt'
operation='Read'
activation properties={portType=Read_ptt, rejectedMessageHandlers=bpel://default|AdapterError2|initiate|payload}
<2009-04-20 11:46:14,096> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Endpoint Activation called in File Adapter for endpoint: c:\temp\yj
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:30,580> <WARN> <default.collaxa.cube.activation> <File Adapter::Inbound> PollWork::run exiting, Worker thread will die
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Translated inbound batch index 1 of file {testdata6.txt} with corrupted message count = 1
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Sending message to Adapter Framework for rejection to user-configured rejection handlers : {
fileName=C:\temp\yj\testdata6.txt, startLine=3, startColumn=1, endLine=-1, endCol=-1, Exception=ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.
<2009-04-20 11:47:14,158> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Root-Element)]onReject: Sending invalid inbound message to Exception Handler: bpel://default|AdapterError2|initiate|payload
<2009-04-20 11:47:14,315> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Setting last error record to : -1
<2009-04-20 11:47:14,658> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchFailure: Batch 'bpel://localhost/default/TestFileRead~1.0//testdata6.txt_1240205493408' (C:\temp\yj\testdata6.txt) has failed due to: ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

Advantage of Java Exceptions over C error handling.

Similar Messages

Maybe you are looking for