Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
940
|
Version |
tigase-server-5.2.0
|
Estimation |
32h
|
Issue Votes (0)
Watchers (0)
Type |
Bug
|
Priority |
Normal
|
Assignee | |
RedmineID |
940
|
Version |
tigase-server-5.2.0
|
Estimation |
32h
|
In some cases the Tigase does not reconnect to the database and throws NPE instead. It might be related to a prolonged network outage or concurrent access to prepared statements...
bq. ??So I can reproduce the NPE by just disconnecting the DB and doing some logins. The problem there is that you synchronize on a preparedStatement that cannot be returned because there’s no connection. Generally, just confusing getting the NPE when perhaps it would be better getting a connection problem. So that’s a bit of a red herring. However.. The precipitating factor is that IT CANNOT get a connection… ??
?? here’s a trace ??
??Here’s it still having problems much later… (eg.. 7 HOURS LATER??
??--à Some other problems of interest.. Key issues when adding Offline messages.??
??Here’s another issue I don’t believe is related to the JDBC reconnect problem.. HOWEVER.. it Is trying to inject Offline messages to a -1 nid which causes an out of range exception:??
??And an error on the get??