How to write user defined exception for timeout event happen - weblogic.developer.interest.webservices.general(Archived)

Hi all,
The client sending request to the server for transaction of detail with using webservices,but server is not available due to connectivity loss or taking long time to connect,this lead to the timeout exception.
I am in need of how to write user defined exception for timeout event.Please help on how to write the user-defined exception or some pre-defined exception is available or not
Regards
Karthik
--
Karthik

Related

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 
In Database to File Transaction, How to capture the Runtime Exceptions like FileNotFoundException as Server log placed in the OracleHome\J2ee\Log\ location?
I had done the Logging and able to create the Log files based on the Login.

ProcessControlExceptions in Asynchronous Services

I have built an asynchronous web service (jws) that invokes a synchronous process (jpd) via a process control (jcx). I'm having trouble with my exception handling.
My JPD has a global exception handler, which throws a SoapFaultException wrapping the exception that was caught. My JWS file has a try-catch block around the call to the process control, which catches a ProcessControlException, and extracts the relevent information from the contained SoapFaultException. I do not rethrow any exceptions.
Despite the fact that I handle the exception in the JWS, it seems that once the method completes (in its entirety) if an exception was caught, the transaction is rolled back, and - since this method starts the conversation - the conversation is not created. This is a major problem, since polling the service will throw a ConversationNotFoundException.
I have done some testing, and the issue only occurs when an exception is thrown from a process control within my jws method. My best guess is that since the transaction is passed to the control, and the control throws an exception, the transaction is set to be rolled-back, even though the exception is being handled at the JWS level. Am I doing something wrong? Is there a way for me to prevent the transaction from rolling back? Any help would be greatly appreciated.
Thanks.
-Brian 
Information at the following link may be helpful:
http://forums.bea.com/bea/thread.jspa?messageID=600034865&#600034865
Regards,
Rommel Sharma

JTA transaction is aborting due to an user rollback fault

Hi,
While testing the ReceiptEBS on EM, we are getting given error, few minutes before EBS was working fine.
Error -
The selected operation CreateReceiptList could not be invoked.
An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Global retry rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new
JTA transaction upon catching this fault.
This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll
back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.
There is no action recommended.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Global retry rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a
new JTA transaction upon catching this fault.
This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine
to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.
There is no action recommended. 
Hi,
I am also getting the same error .Would like to know why this issue is coming and how this can be fixed. Any help is greatly appreciated.
Thanks 
Hi,
This seems to be a timeout error during JTA transaction. Some of my suggestions are
1. Put a timeout value in the partner link properties.
2. Set the timeout parameter for JTA under Domain configuration in console.
Regards,
Rahul 
Hi,
Even we have faced the similar issue, it was all related to DB.
There might be some problem on table space issue on DB side because of which the DB adapter is not working.

[Urgent] TimeOutException encountered when using Mediator+DBAdapter

Dear experts,
We are using FileAdapter+Mediator+DBAdapter in our project to read->transformation>insert/updateDB. The platform is SOA Suite 11.1.1.3 running on 2GB memory server.
When the record count in inbound file is more than 200, then the instance will be terminated and following error will be thrown in log.
**************************************************************************
weblogic.transaction.internal.TimedOutException: Transaction timed out after 301 seconds
....................
<Free memory in the server is 4,318,096 bytes. There is danger of OutOfMemoryError>
....................
java.net.SocketTimeoutException: Read timed out
**************************************************************************
We can accept the poor performance on this 2GB memory server, but we cannot allow the transction timeout error. What we need is to let process to execute successfully, even though it will take long time.
So could you please give me some idea on it to avoid such timeout error thrown?
Thank you in advance.
Regards,
Tony 
You can configure QueryTimeout from the Adapter Configuration Wizard- Advanced Options page. This feature exposes the java.sql.Statement level property of the same name. Essentially, QueryTimeout allows you to configure a time-out on the call.
Also increase the JTA timeout value (Domain_Name --> JTA subtab on Weblogic Admin Console) and see if it works.
Regards,
Anuj 
Thanks Anuj. I will try to modify these parameters later.
BTW, there are also some project which use pure JDBC operation in JAVA class instead of DBAdapter. So for these kind of, which parameter could be set for timeout?
Thank you.
Regards,
Tony 
You may use setQueryTimeout() method of java.sql.Statement class to produce similar effect-
http://download.oracle.com/javase/1.4.2/docs/api/java/sql/Statement.html#setQueryTimeout%28int%29
Regards,
Anuj

Set a timeout value on the Mdeiator

HI, I found my mediator is timing out after nearly 9 minute and rolling back themessage it received to the JMS queue it consumed from and the JMS. How can this be avoided.How can I increase the timeout on the mediator.The invoked target is asynchronous BPEL. ORAMED-03303:[Unexpected exception in case execution]Unexpected exception in request response operation "process" on reference   Waiting for response has timed out. The conversation id is ID%3A%3C653242.1499650483401.0%3E. Please check the process instance for detail.  This error is also seen in the flow, <Failed to handle dispatch message ... exception ORABPEL-05002  Message handle error.error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the reported exception is: Block cannot handle exception.failure of the block "BpPrc0" to handle a business exception for the instancethe reported exception is: Block cannot handle exception.failure of the block "BpPrc0" to handle a business exception for the instance "44614629"; exception reported is: faultName: 
Hi, You need to increase the JTA time-out for you environment. Read the below blog to get an idea "Increase Global Timeouts" http://chintanblog.blogspot.in/2013/11/connection-timeout-and-recovery-usecase.html Thanks,Tapan
Although increasing the JTA timeout is a good suggestion and might help and sometimes is necessary, I'm not fond of it. Time-outs are there for a reason.I think it's better to investigate which service is causing the time out and define the scope of the global transaction.Since you're calling an Async BPEL, it can be running much longer than 9 minutes. You can also set the one way delivery method of BPEL to async.persist. See also: Darwin-IT: XA Transactions with SOASuite JMS Adapter .I think in your case BPEL might be needed to create a new transaction around the service that is taking a long time. Subscribing to the JMS queue within a transaction should only be done if the transaction can be completed in a reasonable amount of time. Changing the transaction time-out might be a slippery slope because what is the you need to define the reasonable time the transaction might take. Regards,Martien

Categories

Resources