Hi,
I don't think the problem is related to the operating system. Does
your application install the fulltext methods? This is done by
executing CREATE ALIAS FT_INIT ... and CALL FT_INIT(). This should be
documented I believe.
Regards,
Thomas
On Sunday, August 8, 2010, clint wrote:
> I seriously
Hi,
Thanks! Unfortunately I don't have time right now to analyse it,
sorry. I will do that in about one week.
Regards,
Thomas
On Wednesday, August 4, 2010, qayx wrote:
> Hi,
> I'm using Version 1.2.140 (2010-07-25)
>
> 08-04 11:36:28 jdbc[2]:
> /*SQL */set trace_level_system_out=3;
> 08-04 11:3
Hi,
Thanks! I will have a look and reply in about one week.
Regards,
Thomas
On Thursday, August 5, 2010, Kerry Sainsbury wrote:
> Hi Thomas,
>
> How do you like this example. It's very simple. Basically you copy and paste
> Java code and call it a "MODULE". The class can then be called from wh
Hi again,
We've updated to version 1.2.140 two weeks ago and haven't seen the
error again.
Thanks a lot for your help!
On Jul 15, 1:45 pm, Borja wrote:
> Hi,
>
> As I've said, we're using the DB through JBoss messaging. We have
> several queues (each one with their own tables), but all in the s
Problem solved.
One of our applications left a transaction uncommitted and that
connection was not closed either.
So it just held some read locks on tables.
Thus preventing (as it should) the update operations on those tables (in
other words exclusive or write locks).
It seems that if transac
