running trunk 930580 using postgresql 8.1 CentOS Linux 5.4 OpenJDK Runtime Environment (build 1.6.0-b09)
========================= BJ Freeman http://bjfreeman.elance.com Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93> Specialtymarket.com <http://www.specialtymarket.com/> Systems Integrator-- Glad to Assist Chat Y! messenger: bjfr33man Linkedin <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> Matt Warnock sent the following on 5/24/2010 11:10 PM: > Trying to get trunk working with postgresql 8.3 under Debian stable, sun > java 1.6.0_12-b04, and I get several similar errors in the logs: > > ---- exception report > ---------------------------------------------------------- > Could not convert field value for the field: > [newEntity.accountingQuantityDiff] to the [BigDecimal] type for the > value [0]: org.ofbiz.base.util.GeneralException: Conversion from > java.lang.String to BigDecimal not currently supported > > ---- exception report > ---------------------------------------------------------- > Exception: java.lang.ClassNotFoundException > Message: No converter found for java.math.BigDecimal->java.lang.Long > > Exception: org.ofbiz.base.util.GeneralException > Message: Conversion from java.lang.String to BigDecimal not currently > supported > > Is there something I need to do to add the needed library? > > I also get errors like the following: > > ---- exception report > ---------------------------------------------------------- > Error storing value > Exception: org.ofbiz.entity.GenericDataSourceException > Message: SQL Exception occurred on commit (Commit can not be set while > enrolled in a transaction) > ---- cause > --------------------------------------------------------------------- > Exception: java.sql.SQLException > Message: Commit can not be set while enrolled in a transaction > > This last one sounds like "Auto-Commit can not be set while in a > transaction", which would make sense if auto-commit was not being turned > off properly, but how could that be? > > Alternatively, is this somehow related to the nested transactions issue > we found with Mysql last week? > > > Anybody have any ideas, or at least have trunk working with Postgresql? > >
