On 4/16/07, Hans J. Prueller <[EMAIL PROTECTED]> wrote:
363 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.jdbc.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 openjpa.jdbc.DBDictionary configuration property to the appropriate value for your database (see the documentation for available values). 449 lbsims INFO [RMI TCP Connection(3)-127.0.1.1] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.MySQLDictionary" (MySQL 5.0.24a-Debian_9ubuntu2-log ,MySQL-AB JDBC Driver mysql-connector-java-5.0.4 ( $Date: 2006-10-19 17:47:48 +0200 (Thu, 19 Oct 2006) $, $Revision: 5908 $ )).
Use <property name="" value="mysql" /> in the persistence.xml of yours to avoid the info message. You may use it to further fine-tune the jpa provider and its underlaying resources like database connections. I haven't tried it out myself, though so use it on your own risk ;-) @see http://incubator.apache.org/openjpa/docs/latest/manual/manual.html#ref_guide_dbsetup_dbsupport
2180 lbsims WARN [RMI TCP Connection(3)-127.0.1.1] openjpa.MetaData - Found duplicate query "PositionLog.byId" in "class com.lbslogics.ims.model.PositionLog". Ignoring.
Could you show the PositionLog entity and the corresponding persistence.xml file with other referenced files (like orm.xml and other mapping files if such exist)? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
