Hi All!
As usual, Turbine and PostgreSQL do not love each other!
In this time I have problem with scheduler service! Each time the
servise is trying to start I obtain this pretty exception (the
TURBINE_SCHEDULED_JOB has one job registered):
Exception: org.apache.turbine.services.InitializationException:
TurbineSchedulerService failed to initialize:
FastPath call returned ERROR: lo_tell: invalid large object
descriptor (0)
Stack Trace follows:
java.sql.SQLException: FastPath call returned ERROR: lo_tell: invalid
large object descriptor (0)
at com.workingdogs.village.DataSet.fetchRecords(DataSet.java:549)
at com.workingdogs.village.DataSet.fetchRecords(DataSet.java:467)
at com.workingdogs.village.DataSet.fetchRecords(DataSet.java:452)
at
org.apache.turbine.om.peer.BasePeer.getSelectResults(BasePeer.java:1376)
at org.apache.turbine.om.peer.BasePeer.executeQuery(BasePeer.java:1289)
at org.apache.turbine.om.peer.BasePeer.executeQuery(BasePeer.java:1251)
at org.apache.turbine.om.peer.BasePeer.executeQuery(BasePeer.java:1202)
at org.apache.turbine.om.peer.BasePeer.doSelect(BasePeer.java:1131)
at
org.apache.turbine.services.schedule.JobEntryPeer.doSelect(JobEntryPeer.java:124)
at
org.apache.turbine.services.schedule.TurbineSchedulerService.init(TurbineSchedulerService.java:121)
rethrown as org.apache.turbine.services.InitializationException:
TurbineSchedulerService failed to initialize:
FastPath call returned ERROR: lo_tell: invalid large object
descriptor (0)
at
org.apache.turbine.services.schedule.TurbineSchedulerService.init(TurbineSchedulerService.java:139)
I know that this expception concering JDBC driver. I use patched one!
Did any of you solve this problem...?
P.S. It would be wonderfull if Turbine where written with PostgreSQL
not MySQL...:-)
______________________________________
Leksiu ([EMAIL PROTECTED])
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
