powered by Jive Software

Problems after upgrade to 4.6.6

I’ve added an admin page …
If you click on manuel… then you should see sth like


2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Restart Connection Listener now
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Stopped.
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Done restarting...
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Started.
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Done restarting...
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Stopped.
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Done restarting...
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Started.
2022.01.04 18:21:43 INFO  [Jetty-QTP-AdminConsole-111789]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Done restarting...

in the logs… the button triggers the same method as the timer does…

Sorry there was a copy & paste error… i fixed it in 1.1.1
i have it running on 4.5 and 4.6.6
but should work on 4.7 too

Now there is no error and seems it working. we will see what happen tomorrow.

Thanks a lot @totzkotz for this pluggin. Really usefull.

2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Stopped.
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Done restarting…
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Started.
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Done restarting…
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Stopped.
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Done restarting…
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Started.
2022.01.04 19:02:54 INFO [Jetty-QTP-AdminConsole-10082]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s-legacyMode] - Done restarting…

2022.01.04 19:05:09 WARN [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 19 invalid sessions

2022.01.04 19:16:09 INFO [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Checking Sessions…
2022.01.04 19:16:09 WARN [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found invalid session on jid: xxx@jabber.ofisat.net/Spark
2022.01.04 19:16:09 WARN [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found invalid session on jid: xxxx@jabber.ofisat.net/Spark

2022.01.04 19:16:09 WARN [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 19 invalid sessions

@totzkotz sorry to say that seems that is not working. At least with 4.7 version.

The message appear within log but not really executing the process.

2022.01.05 09:09:09 WARN [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 11 invalid sessions
2022.01.05 09:10:09 WARN [Timer-9]:
org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 22 invalid sessions

2022.01.05 09:10:58 ^[[32mINFO ^[[m [Jetty-QTP-AdminConsole-16519]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Stopped.
2022.01.05 09:10:58 ^[[32mINFO ^[[m [Jetty-QTP-AdminConsole-16519]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Started.
2022.01.05 09:10:58 ^[[32mINFO ^[[m [Jetty-QTP-AdminConsole-16519]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Done restarting…
2022.01.05 09:10:58 ^[[32mINFO ^[[m [Jetty-QTP-AdminConsole-16519]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Stopped.
2022.01.05 09:10:58 ^[[32mINFO ^[[m [Jetty-QTP-AdminConsole-16519]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Started.
2022.01.05 09:10:58 ^[[32mINFO ^[[m [Jetty-QTP-AdminConsole-16519]: org.jivesoftware.openfire.spi.ConnectionListener[socket_c2s] - Done restarting…

2022.01.05 09:11:09 ^[[33mWARN ^[[m [Timer-9]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 54 invalid sessions

hm i did a test with 4.6.6. When i manually triggered the reconnect via admin console and switched to the sessions tab i could see that clients which where connected to 5222 got the detached state (stream management active). What about 4.7.? Same behavior?

With 4.7 launched manually or automatically the processes are still appearing as invalid in session tab and the number or Invalid sessions are increasing.

The behaviour using your plugin seems diferent as if I force the “same” process using openfire in the original way.

My only option is to force it manually. Once done in this way the Invalid conection starts disappearing

ok i think just stopping and reenabling the Connection Listener is not enough in 4.7.
Strange…
The only thing i can do is to reinit the listener with a configuration…

Thanks @totzkotz I am going to test with last 4.6.7.

We will see what happen.

@totzkotz Now I am testing in 4.6.7.

Works if I execute your plugin manually but seem is not launched automatically.

2022.01.05 12:53:59 INFO [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Checking Sessions…
2022.01.05 12:53:59 WARN [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found invalid session on jid: XXX
2022.01.05 12:53:59 INFO [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - No invalid sessions found…

2022.01.05 12:54:59 INFO [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Checking Sessions…

2022.01.05 12:54:59 WARN [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 4 invalid sessions

2022.01.05 12:55:59 INFO [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Checking Sessions…
2022.01.05 12:55:59 WARN [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 7 invalid sessions

2022.01.05 12:56:59 INFO [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Checking Sessions…
2022.01.05 12:56:59 WARN [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 15 invalid sessions

2022.01.05 12:57:59 WARN [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 20 invalid sessions

Execute manually:

2022.01.05 13:02:59 WARN [Timer-1]: org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Found 3 invalid sessions

i have moved some outputs to debuglog … you could enable the extra logging switch and enable debug logging in openfire to see all logs…
otherwhise it now only logs if restarting the listener…

1.1.3 now sets the config values again… hope it will help

No luck. Just:

2022.01.05 14:28:17 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Start sessioncheck
2022.01.05 14:29:17 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Start sessioncheck
2022.01.05 14:30:17 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Start sessioncheck
2022.01.05 14:31:17 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Start sessioncheck
2022.01.05 14:32:11 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Restart Connection Listener now
2022.01.05 14:32:11 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Restart plain listener

But not:

2022.01.05 14:32:11 org.igniterealtime.openfire.plugin.sessioncheck.SessionCheckPlugin - Restart Connection Listener now

Could you add another option within your plugin to restart service every x minutes?

Thanks.

Thanks a lot @totzkotz .Works perfect!.

But should still be used as an workaround…
Could you provide more details:
OS, Java Version, use of StartTsl / legacy ssl / …, ssl cert is wildcard / self signed …?
I think as much Infos as possible is needed to
track down the problem
Maybe some Screenshots of the configpage for client connections… do you use all krypt algos…?

We seem to have identified one server that is having this issue, but which is also suffering from a corrupted HSQL (embedded) database. I wonder if those problems are related.

I’m not sure how to properly check for database corruption. What we found was that, using the “DB Access” plugin, executing this query would result in an (almost) blank screen:

select payload from ofPubsubItem;

The logs contained an error that included the wording: “lob is no longer valid”

This leads me to believe that the HSQLDB file that stores LOBs is no longer ‘in sync’ with the rest of the database files for HSQLDB.

Can someone using the embedded database check for the same issue?

i am using sql server and have theese issues with invalid sessions too … using OF 4.5.x branch so i think it is not absolutely related to the embedded database

1 Like

hi Guus, it’s me, vladimir, from conference. i told you about this problem earlier. in 4.6.3 i have not this problem, but in one time at nightless before 4.6.4 it happened. closer to 4.6.4 release.
i use ubuntu, mysql, freessl.

I have gone over all changes between 4.6.3 and 4.6.4, but nothing stands out as a likely cause for this. I’m somewhat at a loss. Some long shots:

Can someone please check if setting the system property xmpp.client.version-query.enabled to false will prevent the problem?

Do people, long before the problem occurs, see this in their log files?
Rejecting stanza from client that has not (yet?) established an authenticated session

I have created issue OF-2367 to track this problem.

need i restart OF or just change to false?