|
| Herlani,
Thanks for the reply. But our SP accepts 31 params and we are retrieving
30th param value. Even if we are accessing out of bounds param, driver code
should not crash, it should give some error code with proper explanation.
Also I am getting the similar problem in so many stored procedures. I dont
know ithese SPs work fine once and the next moment it dumps null pointer in
the driver code. All these are working fine with sql server 2000.
This is one more stack trace.
java.lang. NullPointerException
com.microsoft.sqlserver.jdbc.StreamRetValue.deserialize(Unknown Source)
com.microsoft.sqlserver.jdbc. SQLServerCallableSta
tement. indexOutParams(Unkno
wn Source)
com.microsoft.sqlserver.jdbc. SQLServerCallableSta
tement. getOutParameters(Unk
nown Source)
com.microsoft.sqlserver.jdbc. SQLServerCallableSta
tement. getterGetParam(Unkno
wn Source)
com.microsoft.sqlserver.jdbc. SQLServerCallableSta
tement.getInt(Unknown Source)
com.ibm.ws.rsadapter.jdbc. WSJdbcCallableStatem
ent. getInt(WSJdbcCallabl
eStatement.java:390)
com.xyz.SecurityDAO.logon(SecurityDAO.java:153)
Thanks,
Kotha.
"HERLANI JUNIOR" wrote:
[color=darkred]
> Kotha,
>
> Are you sure, that the call are you doing has 30 output parameters ?
>
> Look the exception:
> com.microsoft.sqlserver.jdbc. SQLServerCallableSta
tement.indexOutParams
>
> Rgds,
>
>
>
> "Kotha" wrote:
>
|
|