Broken pipe in SSO integration

Hi!

I am very Satisfied with the tool, but... I've a problem:

I implemented the class SSO to integrate the login of my application with of the forum and
put my application in a cluster, but, almost always the user access
the forum, an exception is displayed on the screen:

-----------------------------

** BEGIN NESTED EXCEPTION **

java.net.SocketException
MESSAGE: Broken pipe

STACKTRACE:

java.net.SocketException: Broken pipe

(Details of exception...)

** END NESTED EXCEPTION **

Last packet sent to the server was 1 ms ago.

Query being executed when exception was thrown:

SELECT * FROM jforum_users WHERE LOWER(username) = LOWER('testear')

-----------------------------

I yet note that my plugin MySQL is in its correct version!

After display of error, if update the page, the login is done with success!

Please, can you help-me?

Tank's!!
[originally posted on jforum.net by rodrigo.marini]

Hello!

I solved the problem by changing the connector MySQL!

I use JForum 2.1.8, with connector "mysql-connector-java-5.0.3-bin.jar" and I replace it for mysql-connector-java-5.0.4-bin.jar

Very simple!

(S��ooooooo)
[originally posted on jforum.net by rodrigo.marini]

Hello...

Unfortunately the problem continue!

Someone has a better suggestion?

Tank's!

[originally posted on jforum.net by rodrigo.marini]

Which MySQL version are you using? Are you able to test it with a different version?

Rafael
[originally posted on jforum.net by Rafael Steil]

Hi!

I am using My SQL 5.0 and I already tried with other versions!

I don't know if it is correct, but, I changed this:

And I think the problem has been resolved!

What do you think?

Tank's!
[originally posted on jforum.net by rodrigo.marini]

Hmm, you mentioned a clustered environment. Solving your DB connection problems by going to a SimpleConnection implementation indicates to me that sessions are being migrated between cluster VMs (like they probably should).

However, you may have other runtime problems with jForum in a clustered environment. For performance reasons, it uses a set of "repositories" that are loaded into the JVM. With multiple JVMs (like a cluster has), keeping these repositories in sync can become an issue. E.g., someone posts an article in JVM1, the repository in JVM1 gets updated, but the repository in JVM2 doesn't.

There are several threads in the forums here about this sort of issue and how to create code to deal with it.
[originally posted on jforum.net by monroe]

Ok ... I will find! Thank you to all!

[originally posted on jforum.net by rodrigo.marini]