I could not reproduce this any more; I got the same message as I ran it in shell:
   Script error on line 4:
   •Query not sent: server is disconnected

I reviewed source code, it seems that this situation has been properly handled.

Tested the issue again using ADStudio 12 Dev 43 on Ubuntu 12.04 calling runfluidscript-bundled.sh with a MySQL connection.

There are two situations appearing, if only calling \disconnect followed by select 123 and \go, most of the times a null message appears, the MySQLNonTransientConnectionException appears now very rarely in this case, however the Query not sent: server is disconnected message has not appeared.

INPUT:
\disconnect
select 123
\go

OUTPUT:
Script error on line 2:
null<---Unexpected null message

The second situation is when the above \disconnect command is preceded by another select 123 and \go, in this situation the MySQLNonTransientConnectionException appears all the time at every test run, additionally the exception is preceded by a  varying error message.

INPUT:
select 123
\go
\disconnect
select 123
\go

OUTPUT VARIANT 1:
>[Error] Script lines: 1-2 --------------------------
Connection.close() has already been called. Invalid operation in this state.
[Executed: 6/6/2012 9:08:46 PM] [Execution: 0ms]
*Followed by the exception mentioned in the first post*

OUTPUT VARIANT 2:
>[Error] Script lines: 0-0 --------------------------
No operations allowed after connection closed.
*Followed by the exception mentioned in the first post*

OUTPUT VARIANT 3:
Statement failed: java.lang.NullPointerException
*Followed by the exception mentioned in the first post*

A workaround for this issue would be to call the \sleep command after \disconnect. If doing so, the expected error message is printed.

INPUT:
select 123
go
disconnect
sleep <--- Workaround
select 123
go

OUTPUT:
* First select 123 output goes here
Script error on line 6:
go: Query not sent: server is disconnected.

I just tried this and I get ...

\disconnect
select 123
go
•disconnect: Disconnected
Script error on line 3:
java.lang.NullPointerException

I guess we should not get a NullPointerException ... but instead get "Query not sent: server is disconnected."

--- run.sql ---

\disconnect
select 123
go
 

I was not able to reproduce this problem if my test script only contains 3 lines:
   disconnect
   select 123
   go
The output always is:
   disconnect
   select 123
   go
   Script error on line 3:
   •go: •Query not sent: server is disconnected.


I will receive the MySQLNonTransientConnectionException exception if my test script contains the followings:
   connect path-to-a-server-file
   select 123
   go
   disconnect
   select 123
   go

The root cause of the problem is \disconnect is not implemented correctly, it uses Swing EDT to close the current connection that causes some delay. And, that is why josekibold can work around the problem by add the 'sleep' command.


In Niels case, if you take a look the generated output, you will see
   •disconnect: Disconnected
is displayed after
   select 123
   go
which tells you \disconnect and \go are not executed sequentially.


After this fix, the correct output should be:
   disconnect
   •disconnect: Disconnected
   select 123
   go
   Script error on line 6:
   •go: •Query not sent: server is disconnected.
 

Verified using ADStudio 12 Alpha 55, works as expected now.

Closed.