Registered a statement as closed which wasn't known to be open. This could happen if you close a statement twice

Openfire Openfire Support
1

I got a lot of these junk messages in the debug log. What’s wrong? Could it be fixed, so these messages are not logged or could the messages be changed to some more meaningful ones pointing out what the problem is?

2008.04.25 11:05:01 000065 (01/04/00) - #4 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:01 000068 (01/04/00) - #2 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:01 000069 (01/04/00) - #3 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:01 000070 (01/04/00) - #4 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:01 000071 (01/04/00) - #1 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:28 000149 (01/04/00) - #3 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:28 000151 (01/04/00) - #1 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:28 000153 (02/04/00) - #2 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:28 000154 (01/04/00) - #4 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:28 000156 (02/04/00) - #1 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2008.04.25 11:05:28 000158 (02/04/00) - #3 registered a statement as closed which wasn’t known to be open. This

could happen if you close a statement twice.

2

For now, I would recommend disabling your debug log if they’re bothering you. =) We haven’t tracked down where the double close is occurring, or if there even is one occurring at this point. That error is coming from proxool. If you happen to be interested in investigating it and providing a patch we’d be all for it! =) I went through every database connection I could find and couldn’t find a place where a double close was occurring though. =/

3

Thanks for the reply. I like to keep the debug log on just in case. It bothered me, because I had no idea what does this message refers to (it’s a bit sloppy), now at least I know it’s about some DB stuff. I am using it with HSQLDB if that matters (it’s not a production installation with low traffic and I didn’t bother to config it with mysql). If you didn’t get to the bottom of this problem I don’t think I’ll try (I am not an Openfire developer at all).

4

Huh, that’s actually weirder. I’ve seen proxool bring it up, but if you are using the embedded db — no proxool. Odd. =) Anyway, if we ever figure out why it’s occurring we’ll shut it up. For now, try to ignore. =)

5

Using the XIFF 3.0 Flash XMPP library I get this frequently. I have an active connection that can receive messages, but is unable to send messages. I use the following set of statements to try to send a message and get the same error in my debug log file.

var jid:JID = new JID(“user” + “@” + “foo.com”, true);
var msg:Message = new Message(jid, null, “Hi Bob.”, “Hi Bob.”, Message.CHAT_TYPE);
connection.send(msg);

‘connection’ is of type XMPPConnection, and can receive messages from users in the same “foo.com” domain.

If the error is benign, but someone could help me with why the message is not sent I would welcome the assistance.

Thanks!

6

it doesnt seem that this debug was ever fixed.

2010.05.12 14:24:02 230574 (01/05/00) - #15 registered a statement as closed which wasn’t known to be open. This could happen if you close a statement twice.
2010.05.12 14:24:02 230574 (01/05/00) - Connection #15 tested: OK

im trying to track down what these issues are.