Skip Headers

Oracle TopLink Developer's Guide 10g Release 3 (10.1.3) B13593-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# Session Errors (800 – 812)

This section lists the TopLink sessions XML errors.

801: [session name] Login - The connection URL has to be specified.
  Cause: You have not specified a connection URL for the session (when using a database driver manager). Each session must have at least one login connection.
  Action: On the session's Login – Connection tab, complete the Driver URL field. See "Configuring a Session Login".

802: [session name] Login - The driver class has to be specified.
  Cause: You have not specified a driver class for the session (when using a data source database driver).
  Action: On the session's Login – Connection tab, complete the Driver Class field. See "Configuring a Session Login".

803: [session or connection pool name]Login - Login - The data source name has to be specified.
  Cause: You have not specified a driver class for the session login (when using a J2EE data source database driver).
  Action: On the session's or connection pool's Login – Connection tab, complete the Data Source field. See "Configuring a Session Login".

804: Login - Session Broker - It has to have at least one session, either a server or a database session.
  Cause: You created a session broker but did not add any sessions. Each session broker must contain a session.
  Action: On the session broker's General – Sessions tab, select a session to add to this broker. See "Configuring Session Broker and Client Sessions".

805: [session name] Database Session - It has to have at least one XML file or a class specified.
  Cause: Your database session does not have a primary project (an associated deployment XML file or Java class file).
  Action: On the session's Project – General tab, complete the Primary Project field. See "Configuring a Primary Mapping Project".

806: Login - The transport class has to be specified.
  Cause: You selected a custom (user-defined) cache coordination type, but did not specify the transport class for cache coordination.
  Action: On the session's Cache Coordination tab, complete the Transport Class field, or select a different cache coordination type. See "Configuring a Coordinated Cache".

807: [session name] Login - The location of the log file has to be specified.
  Cause: You are using standard logging and selected to have the log saved to a file, but did not select a file name and location.
  Action: On the session's Logging tab, complete the Log Location field. See "Configuring Logging".

811: [session or broker name] - An external transaction controller (JTA) has to be specified.
  Cause: You selected a custom server platform, but did not specify the JTA for the platform.
  Action: On the session or session broker's General – Server Platform tab, complete the External Transaction Controller (JTA) field. See "Configuring the Server Platform".

812: [session or broker name] - A server class has to be specified.
  Cause: You selected a custom server platform, but did not specify the server class for the platform.
  Action: On the session or session broker's General – Server Platform tab, complete the Server Class field. See "Configuring the Server Platform".