Ignite Realtime: Database connection error handling issue ...

Up to Discussions in Openfire Support

This thread is archived

7 Replies Last post: Jul 22, 2005 10:45 AM by Matt Tucker

John Nothingmore

9 posts since
May 11, 2005

Currently Being Moderated

Jul 19, 2005 7:04 AM

Database connection error handling issue

It''s quite annoying bug (database is PostgreSQL 7.4.7)

1) Make some users connected and authenticated

2) Turn off database for few minutes (in my case for backup...)

3) Try to login another user (it will fail but that is OK, since database is down) - few exceptions will be thrown (one nested if I correctly recall)

4) Turn database on

5) Messenger will reconnect to database BUT trying to connect with another client will fail... Those already connected will have jabber running, those not will never connect. Moreover - admin console will be dead...

Not trying to connect during database inactivity will make server behave correctly...

Ryan Graham

1,756 posts since
Jan 17, 2003

Currently Being Moderated

Jul 19, 2005 10:19 AM

in response to: John Nothingmore

Re: Database connection error handling issue

Hi mnemonic,

5) Messenger will reconnect to database BUT trying to
connect with another client will fail... Those
already connected will have jabber running, those not
will never connect. Moreover - admin console will be
dead...

It sounds to me as if Messenger never reconnects to the database. How are you checking to see that Messenger has reconnected?

Thanks,

Ryan

Report Abuse

John Nothingmore

9 posts since
May 11, 2005

Currently Being Moderated

Jul 20, 2005 12:35 AM

in response to: Ryan Graham

Re: Database connection error handling issue

1) I''m turning off database every night for few minutes. So if your assumption (Messenger never reconnects) were true, problem would be every morning... But problem arises sometimes only...

2) Running ps command in shell shows persistent connections to right database...

So, Messenger reconnects - but has big mess in internal structures and is working incorrectly....

Report Abuse

Ryan Graham

1,756 posts since
Jan 17, 2003

Currently Being Moderated

Jul 20, 2005 8:35 AM

in response to: John Nothingmore

Re: Database connection error handling issue

Hi mnemonic,

Ah, you didn''t originally mention that the problem was intermintent. Are you seeing any messages in the logs on the mornings when Messenger fails to reconnect?

Thanks,

Ryan

Report Abuse

John Nothingmore

9 posts since
May 11, 2005

Currently Being Moderated

Jul 22, 2005 12:11 AM

in response to: Ryan Graham

Re: Database connection error handling issue

Here we go:

1) ps afx

24478 ? S 0:02 /bin/java -server -Dinstall4j.jvmDir= -Dinstall4j.appDir=/opt/jive_messenger -Dexe4j.moduleName=/opt/jive_messenger/bin/messenge

24479 ? S 0:01 \_ /bin/java -server -Dinstall4j.jvmDir= -Dinstall4j.appDir=/opt/jive_messenger -Dexe4j.moduleName=/opt/jive_messenger/bin/mess

24480 ? S 0:22 \_ /bin/java -server -Dinstall4j.jvmDir= -Dinstall4j.appDir=/opt/jive_messenger -Dexe4j.moduleName=/opt/jive_messenger/bin/

...

24766 ? S 0:00 \_ /bin/java -server -Dinstall4j.jvmDir= -Dinstall4j.appDir=/opt/jive_messenger -Dexe4j.moduleName=/opt/jive_messenger/bin/

...

24585 ? S 0:00 \_ postgres: jabber jabber 127.0.0.1 idle

...

24612 ? S 0:00 \_ postgres: jabber jabber 127.0.0.1 idle

so connection to database was established, messenger was running (morning state...) but no single person could connect to messenger

2) messenger logs:

2005.07.22 01:04:27 org.jivesoftware.messenger.auth.DefaultAuthProvider.authenticate(DefaultAuthProv ider.java:98) Exception in DbAuthProvider

org.postgresql.util.PSQLException: An I/O error has occured while flushing the output - Exception: java.net.SocketException: Broken pipe

Stack Trace:

java.net.SocketException: Broken pipe

at java.net.SocketOutputStream.socketWrite0(Native Method)

at java.net.SocketOutputStream.socketWrite(Unknown Source)

at java.net.SocketOutputStream.write(Unknown Source)

at java.io.BufferedOutputStream.flushBuffer(Unknown Source)

at java.io.BufferedOutputStream.flush(Unknown Source)

at org.postgresql.core.PGStream.flush(PGStream.java:411)

at org.postgresql.core.QueryExecutor.sendQueryV3(QueryExecutor.java:338)

at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:121)

at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100)

at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43)

at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java :517)

at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java :50)

at org.postgresql.jdbc1.AbstractJdbc1Statement.executeQuery(AbstractJdbc1Statement .java:233)

at org.jivesoftware.messenger.auth.DefaultAuthProvider.authenticate(DefaultAuthPro vider.java:83)

at org.jivesoftware.messenger.auth.AuthFactory.authenticate(AuthFactory.java:118)

at org.jivesoftware.messenger.handler.IQAuthHandler.login(IQAuthHandler.java:224)

at org.jivesoftware.messenger.handler.IQAuthHandler.handleIQ(IQAuthHandler.java:14 1)

at org.jivesoftware.messenger.handler.IQHandler.process(IQHandler.java:48)

at org.jivesoftware.messenger.IQRouter.handle(IQRouter.java:202)

at org.jivesoftware.messenger.IQRouter.route(IQRouter.java:73)

at org.jivesoftware.messenger.PacketRouter.route(PacketRouter.java:65)

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:285)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:105)

End of Stack Trace

at org.postgresql.core.PGStream.flush(PGStream.java:415)