MSSQL Stored procedure call problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

MSSQL Stored procedure call problem

szdezso
Hi There!

I have a BPLE flow with MSSQL (jdbc) adapter, I likeo call a MSSQL StoreProcedure.
This SP works fine in MSSQL management studio



But when I runs the BPEL flow then I have got an error.

The SP parameters filled with constant values by an Assing component.


<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;Exception in processing SQL.exec  i_ES_addPartner_sp ?, ? Reason: The value is not set for the parameter number 1. SQLState: null ErrorCode: 0&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance]]>
</faultstring>
         <faultactor>sun-bpel-engine</faultactor>
         <detail>
            <detailText>
<![CDATA[BPCOR-6135: A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;jbi:message xmlns:sxeh=&quot;http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling&quot; type=&quot;sxeh:faultMessage&quot; version=&quot;1.0&quot; xmlns:jbi=&quot;http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper&quot;&gt;&lt;jbi:part&gt;Exception in processing SQL.exec  i_ES_addPartner_sp ?, ? Reason: The value is not set for the parameter number 1. SQLState: null ErrorCode: 0&lt;/jbi:part&gt;&lt;/jbi:message&gt;. Sending errors for the pending requests in the process scope before terminating the process instance
   Caused by: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=PartnerLink2, portType={http://j2ee.netbeans.org/wsdl/MSSQL_SP_Process/src/MSSQL_SP_CALLER}jdbcPortType, operation=execute)
BPCOR-6129: Line Number is 37
BPCOR-6130: Activity Name is Invoke1
   Caused by: Exception in processing SQL.exec  i_ES_addPartner_sp ?, ? Reason: The value is not set for the parameter number 1. SQLState: null ErrorCode: 0]]>
</detailText>
         </detail>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

What's maybe the problem?

Thanks in advance.

Rgds.

D.

ps: the Insert and update (as adapter) works fine.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MSSQL Stored procedure call problem

Paul Perez
Administrator
Hello,
How are you since our last chat on Friday.
Sorry I had no time to follow up.
Did you do any progress this last days ?

regards

Paul
www.pymma.com The best services on OpenESB
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: MSSQL Stored procedure call problem

szdezso
Hello Paul,

No. I have no new developments.

Can you try out a sample BPEL flow with SP caller but to MSSQL DB.

Rgds.

D.
Loading...