<status event-id="0" level="retry" type="app-connection">

Rewrite @level="retry" to @level="failure"


// Casper


On 6/13/14, 8:54 PM, ccohoon wrote:
>
> We are working with 4.0.2 IDM running on Windows Server 2008.
>
> The driver is working with the destCommandProcessor to trigger a stored
> procedure. Here is ultimately what happens when the driver invokes the
> stored procedure and receives a response (Please note, the stored
> procedure runs and affects the user, but the result set sends the driver
> into a retry loop):
>
>
> Code:
> --------------------
> [06/12/14 15:29:06.861]:MDB App ST: Remote Interface Driver: Sending...
> [06/12/14 15:29:06.861]:MDB App ST:
> <nds>
> <input xmlns:jdbc="urn:dirxml:jdbc">
> <jdbc:statement event-id="0">
> <jdbc:call-procedure jdbc:name="p_CreateLoginJob">
> <jdbcaram>
> <jdbc:value>xtuser</jdbc:value>
> </jdbcaram>
> <jdbcaram>
> <jdbc:value>1</jdbc:value>
> </jdbcaram>
> </jdbc:call-procedure>
> </jdbc:statement>
> </input>
> </nds>
> [06/12/14 15:29:06.861]:MDB App ST: Remote Interface Driver: Document sent.
> [06/12/14 15:29:07.131]:MDB App :Remote Interface Driver: Received.
> [06/12/14 15:29:07.131]:MDB App :
> <nds dtdversion="2.0" ndsversion="8.x" xmlns:jdbc="urn:dirxml:jdbc">
> <source>
> <product build="20130111_0503" instance="MDB App" version="4.0.0.1">DirXML Driver for JDBC</product>
> <contact>Novell, Inc.</contact>
> </source>
> <output>
> <jdbc:result-set event-id="0">
> <jdbc:row jdbc:number="1">
> <jdbc:column jdbc:name="$1" jdbcosition="1" jdbc:type="java.sql.Types.VARCHAR"/>
> </jdbc:row>
> </jdbc:result-set>
> <status event-id="0" level="retry" type="app-connection">
> <description>Unable to obtain value(s) from stored procedure 'p_CreateLoginJob'. Unable to read from result set. There is a connectivity-related problem.</description>
> <jdbc:exception jdbc:class="com.microsoft.sqlserver.jdbc.SQLServer Exception" jdbc:error-code="0" jdbc:sql-state="S1093">
> <jdbc:message>The column name $1 is not valid.</jdbc:message>
> </jdbc:exception>
> </status>
> </output>
> </nds>
> --------------------
>
>
> The stored procedure does not have any output variables, it only has 2
> input variables. Has anyone run into this issue when using the JDBC
> driver to run SQL statements for Microsoft SQL?
>
>