Skip Headers

# Session Loader Exceptions (9000 - 9010)

Previous

Next

`SessionLoaderException` is a run-time exception that is raised if the session manager encounters a problem loading session information from a `sessions.xml` (for non-EJB applications) or `toplink-ejb-jar.xml` (for EJB applications) properties file.

Format

    EXCEPTION [TOPLINK – error code]: Exception name
    EXCEPTION DESCRIPTION: Message

Session Loader Exception

    EXCEPTION [TOPLINK – 9004]: oracle.toplink.exceptions.SessionLoaderException
    EXCEPTION DESCRIPTION: The <project-xml> file MyProject was not found on the classpath, nor on the filesystem.

9000: FINAL_EXCEPTION
  Cause: The session loader caught one or more XML parsing exceptions while loading session information. The specific XML exceptions follow.
  Action: Verify your session configuration XML file.

9001: UNKNOWN_TAG
  Cause: An unknown tag was encountered in the specified XML node.
  Action: Examine the specified XML node in your session configuration XML file. Ensure that you use only the tags defined for that node in the appropriate TopLink XSD. See the directory where you installed TopLink (for example, <`ORACLE_HOME`>`/toplink/config/xsds`)

9002: UNABLE_TO_LOAD_PROJECT_CLASS
  Cause: The specified class loader could not load a class with the name given by the `project-name` property.
  Action: Verify the value of the `project-name` property and if correct, ensure that a class with that name is in your classpath.

9003: UNABLE_TO_PROCESS_TAG
  Cause: The session loader caught an exception while either parsing the value of the specified tag or calling the setter method associated with the specified tag.
  Action: Verify the value shown for the specified tag.

9004: COULD_NOT_FIND_PROJECT_XML
  Cause: The session loader could not find the file identified by the `project-xml` tag on either the classpath or the file system.
  Action: Verify the value of the `project-xml` tag and if correct, ensure that a `project.xml` file with that name exists in your classpath or file system.

9005: FAILED_TO_LOAD_PROJECT_XML
  Cause: The session loader caught an exception while trying to load the file identified by the `project-xml` tag either because the file could not be found, or because the file could not be parsed.
  Action: Verify the configuration of the project XML file and ensure that a `project.xml` file with that name specified by the `project-xml` tag exists in your classpath or file system.

9006: UNABLE_TO_PARSE_XML
  Cause: The session loader caught a SAX exception while trying to parse the XML at the given line and column of the specified XML file. Oracle TopLink 10g supports only UTF-8 encoding. The TopLink `SAXParseException` occurs if you attempt to read a non-UTF-8 formatted XML file.
  Action: Verify that the XML is correctly formatted at the given line and column. Alternatively, ensure the Oracle parser is in your classpath and that it appears before any other XML parser.

9007: NON_PARSE_EXCEPTION
  Cause: The session loader caught an exception unrelated to XML parsing (for example, a premature end-of-file exception) while trying to parse the specified XML file.
  Action: Verify the integrity of the XML file.

9008: UN_EXPECTED_VALUE_OF_TAG
  Cause: The value of an XML tag does not correspond to any known TopLink required values.
  Action: Please verify the list of values for this tag.

9009: UNKNOWN_ATTRIBUTE_OF_TAG
  Cause: There is an incorrect name value pair when processing transport properties for the XSD tag.
  Action: Please verify that all properties have both the name and the value filled in, in the session configuration XML file.

9010: XML_SCHEMA_PARSING_ERROR
  Cause: An exception was raised while parsing the XML file against the XML schema.
  Action: Examine the exception and take the appropriate action.