Previous     Contents     Index     DocHome     Next     
iPlanet Application Server Enterprise Connector for R/3 Developer's Guide



Appendix A      Error Messages

The developer writes servlets that use connectors to connect with the back end. Error messages are generated to assist the developer in debugging these processes. This appendix contains a list of identified errors and the error handling code that is used to identify the error.

The following topics are described:



Description of Errors

Table A-1 lists the error handling codes, msgid, and the corresponding messages.

Table A-1 Error Messages

Error Message Code msgid

Error Message

1  

Communication Failure. Error: {error text} (rc : {return code}), Applind : {indication}.  

2  

Failed to connect R/3, RFC Error: Key:{R/3 return code}, Status:{R/3 return status}, ErrorMessage:{error text}.  

3  

Output data is too long, maximal length {length}, actual length {length}.  

4  

Illegal user type value {type code} for property name {name}.  

5  

Internal error. Failed to get object {object type} {object name}.  

6  

Internal error. Object {object name} is NULL.  

7  

Type not supported, in Data Object {object name}, field {field name}, type {field type}.  

8  

Not used.  

9  

Not used.  

10  

Not used.  

11  

Not used.  

12  

Not used.  

13  

Not used.  

14  

Not used.  

15  

Not used.  

16  

R/3 memory exception.  

17  

R/3 Failed to create function object {function name}, Key:{R/3 return code}, Status:{R/3 return status}, ErrorMessage:{error text}.  

18  

R/3 function call Error, function name : { function name }, Return code:{numeric code}. ErrorMessage: { error text }.  

19  

   R/3 function call Error, function name : { function name }, Key:{R/3 return code}, Status:{R/3 return status}, ErrorMessage:{error text}.  



Error Handling Code



The error handling code is an example of how to handle an exception raised by the connector.

When there is an error in the process, the iPlanet Application Server Enterprise Connector for R/3 throws a BspException object. The exception object contains a data object. The data object contains the numeric code, msgid, as listed in Table A-1.

An example of error handling code is shown in Code Example A-1.

Code Example A-1 Error Handling Code Sample

try
{

   ... some code in the servlet

}

catch (BspException e)

{

IBSPDataObjectStructure info = null;

errorMessage += " Error : " + e.getMessage() ;

info=e.getInfo();

if (info != null && info.attrExists("msgid") )

{

errorMessage += " Error code : " + info.getAttrInt("msgid") ;

}

}



Previous     Contents     Index     DocHome     Next     
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.

Last Updated November 01, 2000