Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>It looks like you are using the CE JDBC transport. If this is correct then that is your problem.</p> <p>The CE version can not handle resultsets in calls to stored procedures. See the Feature table in the JDBC Transport documentation [1].</p> <p>The reason it works in MuleStudio is that for some reason it seems that studio uses the EE JDBC transport even when the CE runtime is selected. I have reported this as a issue [2].</p> <p>You can also see in the JDBC transport code[3] see that for a SQL statement that begins with CALL will result in a update on the QueryRunner.</p> <p>You should be able to override this by defining your own Sqlstatementstrategyfactory[4].</p> <p>[1] <a href="http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Reference" rel="nofollow">http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Reference</a><br> [2] <a href="https://www.mulesoft.org/jira/browse/STUDIO-3817" rel="nofollow">https://www.mulesoft.org/jira/browse/STUDIO-3817</a><br> [3] <a href="https://github.com/mulesoft/mule/blob/mule-3.x/transports/jdbc/src/main/java/org/mule/transport/jdbc/sqlstrategy/DefaultSqlStatementStrategyFactory.java" rel="nofollow">https://github.com/mulesoft/mule/blob/mule-3.x/transports/jdbc/src/main/java/org/mule/transport/jdbc/sqlstrategy/DefaultSqlStatementStrategyFactory.java</a><br> [4] <a href="http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Configuration+Reference" rel="nofollow">http://www.mulesoft.org/documentation/display/current/JDBC+Transport+Configuration+Reference</a></p> <p>// Pontus</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload