ADF Mobile Error handling and redirect

I'm stuck on how to handle errors within my ADF Mobile application. My application consumes a number of web services and we have found we often get error messages when phone connections switch from wifi to 3g or lose connection altogether. These are errors such as SSL handshake failure, HTTP500 errors, and also errors where it can't display the binding eh "Unable to get value for the property due to invalid binding iterator" because a WS call has failed. From the little information I can find - and none of it specific to ADF Mobile, I think I need to write an error handler class which I set against ErrorHandlerClass in databinding.cpx - if that correct? Am I able to catch these errors using that method and if so has anyone got any examples at all. Ideally what I'd like to do when I've caught those errors is redirect to another page (showing something like facebooks app does when it loses a connection and says tap to try again), does anyone have any suggestions or examples?
thanks
lynsey

A sample for ADF Mobile Error Handling.
SDA013
Error Handling in ADF Mobile
https://java.net/projects/smuenchadf/pages/ADFMobile#SDA013

Similar Messages

ADF Mobile error: more than one emulator

I'm using the latest ADF Mobile development tools and trying to get a simple application deployed but I can't get past this error. I followed the tutorial on the Oracle site to get to this point so I believe I've got everything set up as recommended by Oracle. Does anyone know how to get past this?
[10:58:00 AM] Updating Android profile dependencies with FAR profiles created from application projects...
[10:58:00 AM] ---- Deployment started. ----
[10:58:00 AM] Target platform is (Android).
[10:58:00 AM] Beginning deployment of ADF Mobile application "MobileApp1" to Android using profile "ANDROID_MOBILE_NATIVE_archive1".
[10:58:01 AM] Checking state of Android Debug Bridge server...
[10:58:07 AM] Started Android Debug Bridge server.
[10:58:07 AM] Verifying a single Android emulator is online and connected to the ADB server...
[10:58:07 AM] Command-line executed: ["C:\adt-bundle-windows-x86_64\sdk\platform-tools\adb", -e, shell, cat, /proc/cpuinfo]
[10:58:07 AM] error: more than one emulator
[10:58:07 AM] Command-line execution failed (Return code: -1)
[10:58:07 AM] Command-line executed: "C:\adt-bundle-windows-x86_64\sdk\platform-tools\adb" -e shell cat /proc/cpuinfo
[10:58:07 AM] Shutting down Android Debug Bridge server...
[10:58:07 AM] Deployment cancelled.
[10:58:07 AM] ---- Deployment incomplete ----.
[10:58:07 AM] Deployment failed due to one or more errors returned by 'C:\adt-bundle-windows-x86_64\sdk\platform-tools\adb'. The following is a summary of the returned error(s):
Command-line execution failed (Return code: -1)
error: more than one emulator

More information: if I start the Android emulator I have two android device emulators:
emulator-5554 offline
emulator-5556 device
So I assume somehow in trying to get this all configured I got an extra device emulator out there and when the Android SDK manager runs it creates that second device. I had problems installing the SDK due to windows updates... so I assume my problem is that somewhere in some file a second emulator is registered. Does anyone know where this file is or how to clean it up?

BPM for error handling and acknowledgements

Hi,
Can any one tell me how to handle BPM for error handling and acknowledgements in one scenario.
Please send me the link if you have other wise give me the solution on the same.
Thanks,
Nagesh

Hi !
Just check out these links This might help you.
Usually Application Level Acknowledgement is considered during Sync communication. If you are using RFC, you can make use of Sync communication. So you can handle it without bpm, provided your both sender and receiver are sync interfaces.
To know about Ack-
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
you can not dirrectly access the content of the ACK, however the BPM shows different behaviours based on the ACK status. E.g. if the ACK contains a success message the BPM will continue in its normal process, if the ACK contains a permanent error, it will either stop or go through an exception branch (provided such a branch has been defined). Have a look at the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm It doesnt"t state the above mentioned behaviour in detail but says that you need to define an exception branch.
The trickiest part is always to find out, when you will get a transient vs. as permanent error ack. If you are using ACKs with Proxies refer also to this link http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm and this http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
The following link has entire configuration of Receiver XI Adapter (including acknowledgements)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
 eror handling in BPM.

1. CCMS monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/42fb24ff-0a01-0010-d48d-ed27a70205a8
2. BPM Monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
3. Monitoring XML Messages http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Also see the below BPM related links
check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Many other examples can be found under the following link at help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
And some weblogs
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
/people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
Also have a look at these seminars,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
Thanks !!!
Regards
Abhishek Agrahari
Questions are welcome here!!
Also mark helpful answers by rewarding points

ESB error handling and notification features

Hello everyone,
I am newbie to oracle SOA ESB. I am an oracle apps guy.
This being my first post to this forum, I have a lot of questions. :-)
For a small intergration requirement, we are looking for a good integration tool
Some requirements are:
1) Flat files will be generated by concurrent programs on oracle apps which need to be transferred to legacy systems.
2) Pick the data from apps tables and insert them into another database. Not much translation required.
After some research, found ESB to be a good fit.
Before actually start using it, we wanted to do a couple of POCs.
So far we are using shell scripts for ftp process. We opted for an integration tool to have DB to DB transmission. Apart from this we need better error handling and error notification mechanism.
Some error conditions:
1) Unavailability of ftp server or Database server.
2) Permission issues. Say some files may not have read, write, deletion permissions. They need to be caught and notified.
3) Mandatory field missing while inserting data which is read from a flat file into a DB table etc..
My initial thoughts on error handling are:
Connection error: To retry for connection errors. If the retry fails send notification via email and also write the failed connection details into an error log file(apart from the server log file).
Data mismatch: NOtification to be sent with the error details.
I would like to know What happens to the file if the destination ftp server is unavailable while ESB is trying to FTP the file. Will ESB retain the file with itself and FTP the file once the ftp server is up?
In BPEL I could see try catch blocks which can be used to handle the errors and thus send notifications.
ESB documents introduced terms like error hospital related to error handling but I was not able to figure out a way of implementing them. As I am not well versed with XML and WSDL I am probably unable to use the fault tab which is in the routing service. I feel Oracle could have given some samples that explain about ESB error handling.
Also to my dismay, adapter docs say that there is a limitation of 7MB size for ftping. Although our file sizes often fall below this size, I would want to know if there is any workaround to over come this size constraint.
I think I put a lot of stuff in a single post and may be in the most haphazard way. Please bear with me.
Please suggest me of some documents if any related to my questions.
Would be really great if you can give me a straight forward solution to all the above problems
Hope this forum would be a great help to me.
Cheers,
Robert.

I have worked on a few SOA Apps implementations. Some successful and some not so. It really comes down to the type of integrations.
But I would say the majority of your integration will be batch as this is what eBus is all about. If this is the case then I would recommend Oracle Data Integrator. If you go Oracle Data Integrator Suite it includes Service Bus and BPEL. ODI has an eBusiness Suite adapter as well.
The good thing about ODI is that you can use it for data conversion, that conversion can then be reused once live, so the conversion is not throw away.
In SOA 10.1.3.4 the limit of 7MB has been resolved but you must be using the file / FTP adapter for input and out, from the sounds of it you want to call concurrent programs so this probably wouldn't work.
cheers
James

Request for info on fatal error handling and High-Precision Timing in J2SE

Hi
Could anyone please provide me some information or some useful links on fatal error handling and High-Precision Timing Support in J2SE 5.0.
Thanks

Look at System.nanoTime

Messages from PI are successful , but not shown in AIF error handling and monditoring

Dear All,
We have messages being triggered from PI to proxy and to AIF.
Messages status is shown as successful in sxmb_moni transaction but I don't get to see these in /AIF/err - error handling and monitoring transaction.
WHat could be the possible reason? would there be any missing authorization.
Note: this is working in Development but having this issue in test environment.
Thanks and Regards,
Archana

Hi Archana,
About ERR_WEB, probably run an old version, but this won't help you either, I think.
Another tip is to look in PI:
Is your service synchronous? For synchronous messages PI only persists the message in PI's message store if the abap proxy returns an error, such as a SOAP Fault. If your abap proxy is not returning an error, then make sure it does. You can raise an application error in AIF.
If PI already receives a SOAP fault, then I suggest you to check if the message was stored in PI: see SAP note 872388 to guide you on this task.

ADF mobile Data sync and sql lite usage

Hi,
We are working on ADF mobile POC.(Jdev version 11.1.2.3.0)
Following Oracle mobile developer guide we generated "Webservice data control" which creates process(object) method to work with Webservice. We created the data-controls and used them in our Java code and are able to get the Webservice response also.
However we want to implement the offline mode feature and for this we are not able to get any document reference for implementation.
With offline mode support is it the application's responsibility to store the data locally using SQL Lite and do the data sync (using Web Service) OR will the framework would do the data sync automatically. Can someone please provide the implementation hint on how to do the Offline mode support in the mobile application using ADF.
Thanks
Pavan

Hi,
With offline mode support is it the application's responsibility to store the data locally using SQL Lite and do the data sync (using Web Service) OR will the framework would do the data sync automatically.
This is all you. In this version of ADF Mobile there is no automatic data synchronization between local data and the server side. The sample that come with the ADF Mobile extension have a SQLLIte example as well, which is in the HR application. Look for the "DBConnectionFactory" file
package application;
import java.sql.Connection;
import java.sql.SQLException;
import oracle.adfmf.framework.api.AdfmfJavaUtilities;
public class DBConnectionFactory {
 public DBConnectionFactory() {
 super();
 protected static Connection conn = null;
 public static Connection getConnection() throws Exception {
 if (conn == null) {
 try {
 // create a database connection
 String Dir = AdfmfJavaUtilities.getDirectoryPathRoot(AdfmfJavaUtilities.ApplicationDirectory);
 String connStr = "jdbc:sqlite:" + Dir + "/HR.db";
 conn = new SQLite.JDBCDataSource(connStr).getConnection();
 } catch (SQLException e) {
 // if the error message is "out of memory",
 // it probably means no database file is found
 System.err.println(e.getMessage());
 return conn;
}The LifeCycleListenerImpl class in the same demo shows how to use this SQL Lite connection
package application;
import java.io.BufferedReader;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
import java.util.ArrayList;
import java.util.List;
import javax.el.ValueExpression;
import oracle.adfmf.application.LifeCycleListener;
import oracle.adfmf.framework.api.AdfmfJavaUtilities;
public class LifeCycleListenerImpl implements LifeCycleListener {
 public LifeCycleListenerImpl() {
 * The start method will be called at the start of the application. Only the
 * Application Lifecycle Event listener will be called on start up.
 public void start() {
 System.out.println("!!!!!!!!!!!!!! App Start !!!!!!!!!!!!!!");
 //InitDB();
 try {
 Statement stat = DBConnectionFactory.getConnection().createStatement();
 ResultSet rs = stat.executeQuery("SELECT * FROM EMPLOYEES;");
 } catch (SQLException e) {
 // if the error message is "out of memory",
 // it probably means no database file is found
 System.err.println(e.getMessage());
 System.out.println("Database does not exist, creating it");
 InitDB();
 } catch (Exception e) {
 System.err.println(e.getMessage());
 System.out.println("!!!!!!!!!!!!!! Done App Start !!!!!!!!!!!!!!");
 * The stop method will be called at the termination of the application. Only
 * the Application Lifecycle Event listener will be called on start up.
 * NOTE: Depending on how the application is being shutdown, this method may
 * or may not be called. Features should save off their state in the deactivate
 * handler.
 public void stop() {
 // Add code here...
 * The activate method will be called when the feature is activated. The
 * Application Lifecycle Event listener will be called on application
 * being started and resumed.
 public void activate() {
 // Add code here...
 * The deactivate method will be called when the feature is deactivated. The
 * Application Lifecycle Event listener will be called on application
 * being hibernated.
 public void deactivate() {
 // Add code here...
 private void InitDB() {
 try {
 System.out.println("!!!!!!!!!!!!!!InitDB Start!!!!!!!!!!!!!!");
 ClassLoader cl = Thread.currentThread().getContextClassLoader();
 InputStream is = cl.getResourceAsStream(".adf/META-INF/hr.sql");
 if (is == null) {
 System.err.println("###### Could not look up : /META-INF/hr.sql");
 return;
 BufferedReader bReader = new BufferedReader(new InputStreamReader(is));
 List stmts = new ArrayList();
 String strstmt = "";
 String ln = bReader.readLine();
 while (ln != null) {
 if (ln.startsWith("REM") || ln.startsWith("COMMIT")) {
 ln = bReader.readLine();
 continue;
 strstmt = strstmt + ln;
 if (strstmt.endsWith(";")) {
 System.out.println(strstmt);
 stmts.add(strstmt);
 strstmt = "";
 ln = bReader.readLine();
 continue;
 ln = bReader.readLine();
 DBConnectionFactory.getConnection().setAutoCommit(false);
 for (int i = 0; i < stmts.size(); i++) {
 Statement pStmt = DBConnectionFactory.getConnection().createStatement();
 pStmt.executeUpdate((String)stmts.get(i));
 DBConnectionFactory.getConnection().commit();
 System.out.println("!!!!!!!!!!!!!!InitDB Done!!!!!!!!!!!!!!");
 } catch (Exception e) {
 e.printStackTrace();
}Hope this is what you were looking for
Frank

ADF Mobile - Error deploying to Default Server

Hi
I am currently doing an ADF mobile application, I can successfully build and compile the project but then when i run my br-o.jspx i encounter this error:
C:\bea\jdeveloper\system\system11.1.1.0.31.52.05\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
JAVA Memory arguments: -Xms256m -Xmx512m
WLS Start Mode=Development
CLASSPATH=;C:\bea\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\JROCKI~1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\bea\WLSERV~1.3\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea\WLSERV~1.3\server\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\bea\jdeveloper\modules\features\adf.share_11.1.1.jar;;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;C:\bea\WLSERV~1.3\server\lib\xqrl.jar;;
PATH=C:\bea\patch_wlw1030\profiles\default\native;C:\bea\patch_wls1030\profiles\default\native;C:\bea\patch_jdev1111\profiles\default\native;C:\bea\patch_cie660\profiles\default\native;C:\bea\WLSERV~1.3\server\native\win\32;C:\bea\WLSERV~1.3\server\bin;C:\bea\modules\ORGAPA~1.5\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\Hyperion\common\CSS\9.5.0.0\bin;C:\Hyperion\common\EssbaseRTC\9.5.0.0\bin;C:\app\L308C11\product\11.1.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\WBEM;C:\Program Files\ZipGenius 6;C:\Program Files\Microsoft SQL Server\80\Tools\Binn;C:\Program Files\Microsoft SQL Server\90\DTS\Binn;C:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies;C:\Hyperion\common\ODBC\Merant\5.2\Drivers;C:\Hyperion\common\ODBC\Merant\5.2\Drivers;C:\bea\WLSERV~1.3\server\native\win\32\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
BEA JRockit(R) (build R27.6.0-50_o-100423-1.6.0_05-20080626-2105-windows-ia32, compiled mode)
Starting WLS with line:
C:\bea\JROCKI~1\bin\java -jrockit -Xms256m -Xmx512m -Xverify:none -da -Dplatform.home=C:\bea\WLSERV~1.3 -Dwls.home=C:\bea\WLSERV~1.3\server -Dweblogic.home=C:\bea\WLSERV~1.3\server -Ddomain.home=C:\bea\JDEVEL~1\system\SYSTEM~1.05\DEFAUL~1 -Doracle.home=C:\bea\jdeveloper -Doracle.security.jps.config=C:\bea\JDEVEL~1\system\SYSTEM~1.05\DEFAUL~1\config\oracle\jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea\patch_wlw1030\profiles\default\sysext_manifest_classpath;C:\bea\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\bea\patch_jdev1111\profiles\default\sysext_manifest_classpath;C:\bea\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\bea\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
<Jul 2, 2009 10:37:17 AM SGT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\bea\patch_wls1030\profiles\default\sysext_manifest_classpath\weblogic_ext_patch.jar>
<Jul 2, 2009 10:37:18 AM SGT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2105-windows-ia32 from BEA Systems, Inc.>
<Jul 2, 2009 10:37:18 AM SGT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR380042 Thu Sep 11 13:33:40 PDT 2008
WebLogic Server Temporary Patch for 7372756 Fri Sep 12 17:05:44 EDT 2008
WebLogic Server Temporary Patch for CR381265 Wed Oct 08 10:15:58 PDT 2008
WebLogic Server Temporary Patch for CR380913 Wed Oct 15 13:24:22 PDT 2008
WebLogic Server Temporary Patch for CR382965 Fri Nov 21 15:51:48 PST 2008
WebLogic Server Temporary Patch for CR383260 Thu Nov 20 12:58:15 PST 2008
WebLogic Server Temporary Patch for CR383202 Fri Nov 21 09:58:15 PST 2008
WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Jul 2, 2009 10:37:20 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 2, 2009 10:37:20 AM SGT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jul 2, 2009 10:37:20 AM SGT> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\jdeveloper\system\system11.1.1.0.31.52.05\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
<Jul 2, 2009 10:37:26 AM SGT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jul 2, 2009 10:37:35 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jul 2, 2009 10:37:35 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jul 2, 2009 10:37:38 AM SGT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.248.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<Jul 2, 2009 10:37:39 AM SGT> <Warning> <Server> <BEA-002611> <Hostname "L30911.sitfypj.nyp.edu.sg.sitfypj.nyp.edu.sg", maps to multiple IP addresses: 192.168.154.1, 192.168.248.1, 172.20.132.71, 192.168.2.2, 127.0.0.1>
<Jul 2, 2009 10:37:39 AM SGT> <Warning> <Server> <BEA-002611> <Hostname "L30911.sitfypj.nyp.edu.sg", maps to multiple IP addresses: 192.168.154.1, 192.168.248.1, 172.20.132.71, 192.168.2.2, 127.0.0.1>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 192.168.2.2:7101 for protocols iiop, t3, ldap, snmp, http.>
<Jul 2, 2009 10:37:39 AM SGT> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 192.168.154.1, 192.168.248.1, 172.20.132.71, 192.168.2.2, 127.0.0.1>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.154.1:7101 for protocols iiop, t3, ldap, snmp, http.>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 172.20.132.71:7101 for protocols iiop, t3, ldap, snmp, http.>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
<Jul 2, 2009 10:37:39 AM SGT> <Warning> <Server> <BEA-002611> <Hostname "L30911", maps to multiple IP addresses: 192.168.154.1, 192.168.248.1, 172.20.132.71, 192.168.2.2, 127.0.0.1>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Jul 2, 2009 10:37:39 AM SGT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
DefaultServer startup time: 32533 ms.
DefaultServer started.
[Running application adfm-new on Server Instance DefaultServer...]
Uploading credentials.
---- Deployment started. ---- Jul 2, 2009 10:37:47 AM
Target platform is (Weblogic 10.3).
Running dependency analysis...
#### Deployment incomplete. #### Jul 2, 2009 10:37:47 AM
java.lang.RuntimeException: java.lang.NullPointerException
 at oracle.jdevimpl.deploy.common.ModulePackagerImpl.deployProfiles(ModulePackagerImpl.java:88)
 at oracle.jdeveloper.deploy.common.ModulePackager.deployProfiles(ModulePackager.java:63)
 at oracle.jdeveloper.deploy.common.ModulePackager.deployImpl(ModulePackager.java:52)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
 at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
 at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
 at oracle.jdevimpl.runner.adrs.AdrsStarter$5$1.run(AdrsStarter.java:1365)
Caused by: java.lang.NullPointerException
 at oracle.ide.net.URLFileSystem$TrackedOutputStream.flush(URLFileSystem.java:2332)
 at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
 at oracle.jdevimpl.deploy.stripe.MonitoredOutputStream.flush(MonitoredOutputStream.java:84)
 at java.io.FilterOutputStream.close(FilterOutputStream.java:140)
 at oracle.jdevimpl.deploy.stripe.MonitoredOutputStream.close(MonitoredOutputStream.java:89)
 at oracle.jdevimpl.webapp.jsp.libraries.wl.WebLogicDeployerListener.prepared(WebLogicDeployerListener.java:146)
 at oracle.jdevimpl.deploy.fwk.ListenerSupport.firePrepared(ListenerSupport.java:178)
 at oracle.jdeveloper.deploy.common.AbstractDeployer.prepare(AbstractDeployer.java:78)
 at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:430)
 at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
 at oracle.jdevimpl.deploy.common.ModulePackagerImpl.deployProfiles(ModulePackagerImpl.java:82)
 ... 26 more
#### Cannot run application adfm-new due to error deploying to DefaultServer.
[Application adfm-new stopped and undeployed from Server Instance DefaultServer]
Please advice how do i solve it, and its quite urgent. Thanks
Shirleen
Edited by: Shirleen on Jul 1, 2009 2:19 PM
Edited by: Shirleen on Jul 2, 2009 11:12 AM

Hi, Shirleen, I have recently uploaded a new version of the sample mobile application to Oracle Technology Network that would work with the latest/current version of JDeveloper (11.1.1.1.0). Please try to download it at http://www.oracle.com/technology/tech/wireless/adf_mobile.html.
Also, from the error message I am unable to see anything specific that could help, but I would just make sure that you have FOD schema already downloaded and installed, and have configured the database connection in the sample application to point to the database running the FOD schema.
Thanks,
Joe Huang

ADF Custom error handler not working.

Hi All,
i am using jdev version 11.1.1.5.0. i have created one custom error handler class in model layer which extend DcErrorHandlerImpl class.
and do the entry in Databinding.cpx file
*<Application ErrorHandlerClass="mypackage.classname"/>*
i have override getDisplayMessage(BindingContext ctx, Exception ex) method to show SQL Exception which comes from database table trigger.
code is following-
package com.in.jagran.view.services;
 import java.sql.SQLException;
 import oracle.adf.model.BindingContext;
 import oracle.adf.model.binding.DCErrorHandlerImpl;
 import oracle.jbo.JboException;
 public class AclasErrorHandler extends DCErrorHandlerImpl {
 public AclasErrorHandler(boolean setToThrow) {
 super(setToThrow);
 System.out.println("Inside Error Handler class");
 public AclasErrorHandler() {
 super(true);
 // this(true);
 * Returns the message that will be reported to JSF for each error that occurs.
 * Returning "null" is the way the custom error handler signals that a given exception
 * should not be reported to the client.
 @Override
 public String getDisplayMessage(BindingContext ctx, Exception ex)
 if (ex instanceof oracle.jbo.ValidationException) {
 return super.getDisplayMessage(ctx, ex);
 else {
 // Extract and return the error message that has to be displayed
 Exception exception = ex;
 String message = "";
 // If this exception is an instance of JboException,
 // try to find the cause by recursing over the eventual causing exceptions
 if (exception instanceof JboException)
 Throwable[] exceptionList = ((JboException)exception).getExceptions();
 while (exception instanceof JboException
 && exceptionList != null && exceptionList.length > 0)
 exception = (Exception)exceptionList[0];
 if (exception instanceof JboException) {
 exceptionList = ((JboException)exception).getExceptions();
 // *** Special processing of SQLExceptions
 if (exception instanceof SQLException) {
 message = exception.getMessage();
 // Ignore the lines in the error message that indicate the line number in the PLSQL code that the error resulted on.
 int ind = message.indexOf("ORA-06512");
 if (ind > 0)
 message = message.substring(0, ind);
 // *** If the the reason for the JboException was data creation exception then display the message
 // of the top JboException (i.e. JBO-*****: Invalid numeric value, date format or time format)
 else if (exception instanceof NumberFormatException || exception instanceof IllegalArgumentException) {
 // Report the top exception
 message = ex.getMessage();
 // Otherwise report the message of the lowest exception in the hierarchy
 else {
 message = exception.getMessage();
 return message;
 }but it is not working for me.
thanks in Advance.

yes i have used dubugger.
i have set break point to following line-
return super.getDisplayMessage(ctx, ex);
if (ex instanceof oracle.jbo.ValidationException) {
 return super.getDisplayMessage(ctx, ex);
}when atttribute validation done like i have attribute of type number and i have done the validation "must be greater than 0" now when i have given negative value control go to above line.
and i have added following code also in handler class
 @Override
 public void reportException(DCBindingContainer dCBindingContainer,
 Exception exception) {
System.out.println(exception.getMessage());
 super.reportException(dCBindingContainer, exception);
 }now when i have done commit operation control go to here and println statement print follwoing error on log window.
JBO-26041: Failed to post data to database during "Rollback to Savepoint": SQL Statement "null".

Error Handler and Page Bindings

Hi,
I have a task flow with an error-handler defined. Any action-binding method calls which throw exceptions from the business layer are handled nicely by the error handler. The same doesn't happen though when the binding is in the page, tied to a button (as created when you drag a method from the data control palette onto the page). The exception is instead displayed in the calling page. What am I missing here?
Thanks,
Barry.

Hi,
the ADF Controller catches excptions occuring while it processes an activity. If JSF catches the exception then this does not involve navigation and therefore the message displays on the page
Frank

OSB 10gR3 Error handling and reporting action approach

My use case:
Simple Proxy service routes to an external web service created as Business service in OSB
Whenever there is transport error/soap fault from the external web service, that error needs to be reported along with the original request received by the proxy service.
What I have tried so far?
Created a error handler/stage in the route node of my proxy service. Within that stage, added a report action to report $body which contains the error received from the external service. I created a report index key/value to report for this request, I used a specific element in the body of the original request sent to the proxy service.
Within the route error handling stage, I realized that $body which had my original request to the proxy service lost its content and replaced by the fault from external WS. So I made a copy of $body in my request pipeline and tried to use an element from that copy to index my failed request. But the copied variable always seem to be empty within the error handling stage.
So, my questions to the experts,
1)What variables are visible within the error handling stage/scope?
2)What is the best way(less overhead) to preserve my original request as $body context variable is already changed with fault by the time error handler is invoked? Remember I wanted to report the original request only incase of error, for success cases I don't care/I don't want to un-necessarily add an overhead of copying to a vairbale.
3)Is there another proper way to simply report the original request received by proxy and fault received from external service for a given key in the request, say orderId
Sample proxy request:
<MyData>
<OrderId>123</OrderId>
</MyData>

1)What variables are visible within the error handling stage/scope? $fault - http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1051816
$body - http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/context.html#wp1103311
2)What is the best way(less overhead) to preserve my original request as $body context variable is already changed with fault by the time error handler is invoked? Remember I wanted to report the original request only incase of error, for success cases I don't care/I don't want to un-necessarily add an overhead of copying to a variable.Can you print $body and $fault variables in your error handler?. Are they different ? What I'm suspecting is the back-end webservice is faulting (returning soap-fault and http response =5xx). There is no other way I can think of than copying the contents of $body to a separate variable.
Thanks
Manoj

'Structured' error handling and reentrancy

The parentheses in the subject are due to the fact that I'm not using the Structured Error Handler reference library, but have rolled my own to do something similar but in the manner I want it to. I don't actually use the SEH (haven't even got it installed at the moment on this PC) so am not sure exactly how it works under the hood.
I have a reasonably large application with a number of distinct parallel modules (GUI, state module, communication, motion control). The final parallel module is an error handling module. This consists of two queues - one for incoming errors, and one for outgoing actions. Errors are dequeued and their codes checked for their category (critical, warning, ignore or unclassified, for instance) and the appropriate category is returned to a local error handler via the action queue. When an error is passed to a local error handler VI, it enqueues the error to the main handler and waits for a response to that particular error.
This all works nicely, in much the same way the SEH would do. However, with either the SEH or my local error handler method, I find myself wondering how often to place these down and the consequences of doing so. If they're non-reentrant, I imagine I may end up with lots of parallel processes sitting patiently to access the VI as it's blocked by another, causing jitter. If I go pre-allocated clone, I could potentially have many many callers using this function, which strikes me as a bit of a waste of resources. My gut feel is to go with shared-allocation clones, as the vast majority of the time it'll be no error passed through an empty case, and not to place them in absolutely every subVI - just perhaps after a state executes in the state handler, in all the parallel loops of the submodules etc.
Just wondering what anyone else does with their error handling solution, and whether my thoughts make sense.
CLD

Having chatted to my friendly neighbourhood Spiderman Architect, he suggested I should probably just stop being a wimp and just use pre-allocated clones to avoid the jitter and to stop worrying about the resource hit, as you suggest
I'll use the same code on both PC host and RT host, hence the jitter concerns on the RT.
Thanks for the thoughts!
CLD

Error Handling and Freeing-up Memory

I'm trying to write my java programs as responsibly as possible. When an exception is caught and sent to my catch block, in order to properly free up memory do I need to set all objects (created prior to the error occurance in the try block) to null or does Java do this for me at the termination of the routine or thread? I used to do this in VB within my error handlers. For example, in VB, if I had created an XYZ object and an error occured later on, before I was done using object XYZ, as part of my error handler I would "Set XYZ = Nothing". Is something similar needed in Java?

Well it is always good to do a clean up routine you can do this by makeing a method that will set things to null and such and you also can use finally after the exception handler has exit and close streams and such in the finally {} catch also you can forcing finalization and carbage collection
here is a link for that
http://java.sun.com/docs/books/tutorial/essential/system/garbage.html
but I thank it is alway good programming practice to clean up after your self
ps I hope this helps

Error Handling and Error Messages

I already posted this in the java programming forum, but I dont think the people responded understand patterns, or what I was asking. Here is my original post, for reference I am not asking how to catch and exception, or how to display an error, I am asking about the pattern implementation.
I am currently in the process of creating my Exception model for my program, and I have a question about error messages. I was reading the book "Effective Java Programming" which deals with patterns and it states that an exception should state the error and report information on all relavent states. For instance If you have a class the modeled some sort of memory array, and an access was requested to a block of memory outside the array you should throw an ArrayIndexOutOfBoundsException("Index:" + index + ", start:" + 0 + ",end:" + Array.length) or if you made your own MemoryAddressOutOfBoundsException(same as above) which when printed should read
ArrayIndexOutOfBoundsException: Index:-1, start:0, end:0
stack trace
The pertinate information is the index, start index, and end index.
The book CLEARLY states as an industry design pattern that exceptions weather checked or unchecked should not contain user error messages. For instance with the above example one might be tempted to use this as the exception message: "The memory addres index is not a valid memory address." This is clearly a user error message.
So heres my situation. In a gui environment (command line console not visible) how do you generated a user error message, letting the user know that an internal exception has occured.
In my previous implementation of my project, I used the exception message the user error message and just reported the message on a dialog. I have heard of people using error catalogs, which centrallizes all the error messages into a single class or file.
I was wondering if and Error catalog was a good approach, how I might go about implementing one, and if not how do you the community handle user error messages.

class MyAppErrors {
   public static final int FILE_NOT_FOUND = 0;
   public static final int DIR_NOT_FOUND = 1;
   public stat final String[] errMsgs = {
      "The file was not found.",
      "The directory was not found.",
   public String getErrMsg( int n ) { return errMsgs[n]; }
[\code]
And a nicer version would allow the calling code to pass in a substring so you could say "The file 'somename.ext' was not found."

Regarding Error handling and customisation in RFC, Idocs and Proxy

Hi,
I wanted to compare RFC, Proxy and Idocs on the basis of the amount of customisation required in ECC when sending data from ECC to XI using the above stated means and also the error handling provided in these methods.
Please let me know in detail if possible.
Regards,
Sampada

Hi ,
Check this blog to know when to use which adapter:
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
we use proxy in sap 6.0 version or higher.
Basically used for adapter less communication
& very high volume of data has to be transfered.
Step for Configuration fo IDOC in R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Vinod.

ADF Mobile Error handling and redirect

Similar Messages

Maybe you are looking for