Re[2]: PostgreSQL and Scheduler

[Maciej Leks <ml...@zeus.polsl.gliwice.pl>]

>> P.S. It would be wonderfull if Turbine where written with PostgreSQL
>> not MySQL...:-)

WS> I've been using Turbine for almost a year on DB2/400, DB2 UDB (Win2k), MySQL
WS> and HypersonicSQL a little (when playing with Jetspeed).  I have run into
WS> only very minor issues that were easily fixed or patched.  From what I have
WS> seen on this list, it appears that either the PostgreSQL JDBC driver or
WS> PostgresSQL itself is the culprit not Turbine (Torque).

As I wrote I know that problem is located on the postgres side
(PostgreSQL RDBMS or JDBC driver) not Turbine! The point was that
writing and testing something with more demanding software (like Postgres)
couses that product can be much easier used with "developer friendly" one (like
MySQL, Oracle).

>> 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)

WS> If I'm not mistaken, this appears to be an issue using BLOB type.  Which,
WS> someone correct me if I'm wrong, seems to be the biggest sticking point when
WS> it comes to using Turbine with PostgreSQL.

What to do?
I will hang myself:-) But seriously if I will not find a solution I
will have to cut the PROPERTY column from the TURBINE_SCHEDULED_JOB
and adjust scheduler code to the new structure.

>> -----Original Message-----
>> From: Maciej Leks [mailto:mleks@zeus.polsl.gliwice.pl]
>> Sent: Wednesday, May 01, 2002 6:21 AM
>> To: Turbine Users List
>> Subject: PostgreSQL and Scheduler
>> 
>> 
>> 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(Job
>> EntryPeer.java:124)
>>                 at 
>> org.apache.turbine.services.schedule.TurbineSchedulerService.i
>> nit(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.i
>> nit(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 (mleks@zeus.polsl.gliwice.pl)
>> 
>> 
>> --
>> To unsubscribe, e-mail:   
WS> <ma...@jakarta.apache.org>
WS> For additional commands, e-mail:
WS> <ma...@jakarta.apache.org>




______________________________________
 Leksiu (mleks@zeus.polsl.gliwice.pl)


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Re[2]: PostgreSQL and Scheduler

[Daniel Rall <dl...@finemaltcoding.com>]

Maciej Leks <ml...@zeus.polsl.gliwice.pl> writes:

> What to do?
> I will hang myself:-) But seriously if I will not find a solution I
> will have to cut the PROPERTY column from the TURBINE_SCHEDULED_JOB
> and adjust scheduler code to the new structure.

There was recently some discussion about integrating a new scheduler,
as the old one is too brittle and the cause of tons of problems like
this.  You might be better off asking on the dev list about the status
of this rumored scheduler.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>