Use Conversations AND jdbc together

Hey Guys.
I have a little problem with the Conversation API.
I have to work with SQLConnections in the "acceptInput" Method.
But at this point the Connection to the player is closing and he becomes an End of Stream Message.

Example:

Code:java

 
@Override
    public Prompt acceptInput(ConversationContext arg0, String arg1) {
        if(!arg1.equals("...")){
            try {
                PreparedStatement sql=getC().prepareStatement("UPDATE `ActivationData` SET `Land`=? WHERE `Name`=?");
                sql.setString(1, arg1);
                sql.setString(2, ((Player)arg0).getName());
                sql.executeUpdate();
            } catch (SQLException e) {
                e.printStackTrace();
            }
            closeConnection();
            return new CityPrompt();
        }
        else{
            try {
                PreparedStatement sql=getC().prepareStatement("UPDATE `ActivationData` SET `Land`=? WHERE `Name`=?");
                sql.setString(1, "KEINS");
                sql.setString(2, ((Player)arg0).getName());
                sql.executeUpdate();
            } catch (SQLException e) {
                e.printStackTrace();
            }
            closeConnection();
            return new ServerPrompt();
        }
    }
 

The first question is: Why?
and the second : How can I avoid this strage "Error"

Thank YOU for your answers.

EDIT: I forgot, to say, that there isn't any Error massage. I know that the ConversationAPI is very sensitive. If there is any Exception in it, it kicks the player from ther server. But not this time.

Looks like a new Enigma of the Bukkit API , doesn't it...

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Does it have to be "instantly" updated when making a choice?

As you can chain choices the end could be "forget what i said" then you would have to rollback everything.

What i would do is collect choices made and bind them to actions.

That way you could even switch the backend from sql to text or whatever. I also think using this method you probably will get many connection timeouts when closing the connection after each choice made as it seems you dont use Pooled Connections (which avoids this and automatically reuses a connection if not needed).

Anyways i would try to store choices made first before implementing sql queries to it. Check if that works and then try to implement the backend.

 

Thats a great Idea. Thank you!

That's Bullshit. Of course there is an Exception-message which says, that I can't cast a conversationContext to Player (or the other way).
Sorry.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.