geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacek Laskowski" <>
Subject Messages about Derby while undeploying JPA app with PostgreSQL datasource
Date Sat, 27 Oct 2007 22:42:09 GMT

While undeploying an app with JPA that's configured with
PostgreSQL-based datasource (JTA mode) Geronimo spits the following:

23:53:12,515 INFO  [JDBC] OpenJPA will now connect to the database to
attempt to determine what type of database dictionary to use.  To
prevent this connection in the future, set your o
penjpa.jdbc.DBDictionary configuration property to the appropriate
value for your database (see the documentation for available values).
23:53:12,515 INFO  [JDBC] Using dictionary class
"org.apache.openjpa.jdbc.sql.DerbyDictionary" (Apache Derby -
(561794) ,Apache Derby Embedded JDBC Driver - (561794)).

Why is that? The app doesn't touch Derby at all. Its startup is clean
as it should be:

Geronimo startup complete
22:34:48,796 INFO  [config] Configuring Service(id=Default Stateless
Container, type=Container, provider-id=Default Stateless Container)
22:34:48,796 INFO  [config] Configuring Service(id=Default Stateful
Container, type=Container, provider-id=Default Stateful Container)
22:34:48,796 INFO  [config] Configuring Service(id=Default BMP
Container, type=Container, provider-id=Default BMP Container)
22:34:48,796 INFO  [config] Configuring Service(id=Default CMP
Container, type=Container, provider-id=Default CMP Container)
22:34:48,796 INFO  [config] Configuring app:
22:34:49,000 INFO  [OpenEJB] Auto-deploying ejb TicketServiceBean:
22:34:49,406 INFO  [config] Loaded Module:
22:34:52,390 INFO  [Enhance] You have enabled runtime enhancement, but
have not specified the set of persistent classes.  OpenJPA must look
for metadata for every loaded class, which mi
ght increase class load times significantly.
22:34:54,171 INFO  [config] Configuring Service(id=Default MDB
Container, type=Container, provider-id=Default MDB Container)
22:34:56,187 INFO  [startup] Assembling app:
22:34:56,250 INFO  [startup]
Jndi(name=TicketServiceMDB.jar/TicketServiceBean) -->
22:34:56,437 INFO  [startup] Created
22:34:56,437 INFO  [startup] Deployed

Upon running the app causes OpenJPA to print the following:

22:36:11,718 INFO  [Runtime] Starting OpenJPA 1.0.0
22:36:11,812 INFO  [JDBC] Using dictionary class

and that's it, so all appears to be set up correctly.


Jacek Laskowski

View raw message