Yes, this worked for me too, thanks!
Leander
On 22-mrt-2007, at 15:31, Christopher Hartung wrote:
Hi there,
i tried this solution in our envorinment and it works fine. BIG THX
for your help!
Greetz
Chris
Emmanuel Cecchet schrieb:
Hi,
Not sure if this is the same problem but I found that by adding
the postgres JDBC driver to the classpath of all sequoia
controllers the client recieves the message straight away. I
traced this problem back in the sequoia 2.4 days to be related to
the fact that the group software couldn't serialize the
SQLException to transmit accross the cluster because it couldn't
load the exeception class and thus caused a runtime error on the
remote controller...
Dave is right, if you have any database specific object that gets
returned through the group communication (SQLException or
ResultSet), then the database driver should be in the classpath.
Thanks for your interest in Sequoia,
Emmanuel
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
