Quantcast

Database BC Exception Unable to convert normalized message to prepared sql statement

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

Database BC Exception Unable to convert normalized message to prepared sql statement

Akshay
This post has NOT been accepted by the mailing list yet.
Hello All, I tried configuring a OpenESB DB project with Join and update operation, while performing the execution of this project I am getting below exception, 2016-04-18T01:15:33.229+0530 SEVERE [sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor] (pool-5-thread-9) Failed to write message:. java.lang.Exception: Failed to denormalize message. 92516556609391-34244-136802151331990192 . at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:737) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:273) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:153) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: javax.jbi.messaging.MessagingException: Error occured while executing SQL.update ORDHEAD set ORHSTA = 'P' where ORHSEQ = ? Reason: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1876) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:703) ... 5 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:135) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1860) ... 6 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.populatePreparedStatement(JDBCDenormalizer.java:617) at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:123) ... 7 more 2016-04-18T01:15:33.229+0530 INFO [sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor] (pool-5-thread-9) Finished processing outbound messages. 2016-04-18T01:15:33.269+0530 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-1) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is Failed to denormalize message. 92516556609391-34244-136802151331990192 . com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ProcessUpdate, portType={http://j2ee.netbeans.org/wsdl/RetekOrderToOTM_bepl/src/processUpdate}jdbcPortType, operation=update) BPCOR-6129: Line Number is 123 BPCOR-6130: Activity Name is Inv_Update at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:969) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:566) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:185) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:163) at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1088) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:280) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1338) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241) at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193) Caused by: java.lang.Exception: Failed to denormalize message. 92516556609391-34244-136802151331990192 . at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:737) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:273) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:153) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: javax.jbi.messaging.MessagingException: Error occured while executing SQL.update ORDHEAD set ORHSTA = 'P' where ORHSEQ = ? Reason: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1876) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:703) ... 5 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:135) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1860) ... 6 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.populatePreparedStatement(JDBCDenormalizer.java:617) at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:123) ... 7 more Below is my WSDL for Database : ================================================================ ========================================= I have tried passing the same number of parameter which are there in where clause but still getting exception. Any help would be greatly appreciated. Regards, Akshay
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Akshay
This post has NOT been accepted by the mailing list yet.
Reformatting the Post :

Hello All,

I tried configuring a OpenESB DB project with Join and update operation, while performing the execution of this project I am getting below exception,
-----------------------------------------------------------------------------------------------------------------------------------------
 2016-04-18T01:15:33.229+0530 SEVERE [sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor] (pool-5-thread-9) Failed to write message:. java.lang.Exception: Failed to denormalize message. 92516556609391-34244-136802151331990192 . at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:737) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:273) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:153) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: javax.jbi.messaging.MessagingException: Error occured while executing SQL.update ORDHEAD set ORHSTA = 'P' where ORHSEQ = ? Reason: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1876) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:703) ... 5 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:135) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1860) ... 6 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.populatePreparedStatement(JDBCDenormalizer.java:617) at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:123) ... 7 more 2016-04-18T01:15:33.229+0530 INFO [sun-database-binding.org.glassfish.openesb.databasebc.OutboundMessageProcessor] (pool-5-thread-9) Finished processing outbound messages. 2016-04-18T01:15:33.269+0530 WARNING [com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.BPELProcessInstanceImpl] (sun-bpel-engine-thread-1) BPCOR-6151: The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is Failed to denormalize message. 92516556609391-34244-136802151331990192 . com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131: An Error status was received while doing an invoke (partnerLink=ProcessUpdate, portType={http://j2ee.netbeans.org/wsdl/RetekOrderToOTM_bepl/src/processUpdate}jdbcPortType, operation=update) BPCOR-6129: Line Number is 123 BPCOR-6130: Activity Name is Inv_Update at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:969) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:566) at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:185) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:163) at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1088) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:280) at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1338) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:384) at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:241) at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:193) Caused by: java.lang.Exception: Failed to denormalize message. 92516556609391-34244-136802151331990192 . at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:737) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.execute(OutboundMessageProcessor.java:273) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.run(OutboundMessageProcessor.java:153) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: javax.jbi.messaging.MessagingException: Error occured while executing SQL.update ORDHEAD set ORHSTA = 'P' where ORHSEQ = ? Reason: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1876) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:703) ... 5 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:135) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1860) ... 6 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.populatePreparedStatement(JDBCDenormalizer.java:617) at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:123) ... 7 more
-----------------------------------------------------------------------------------------------------------------------------------------

Below is my WSDL for Database :
============================================================================
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="processUpdate" targetNamespace="http://j2ee.netbeans.org/wsdl/RetekOrderToOTM_bepl/src/processUpdate" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns="http://j2ee.netbeans.org/xsd/tableSchema" xmlns:plink="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:tns="http://j2ee.netbeans.org/wsdl/RetekOrderToOTM_bepl/src/processUpdate" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
  <types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/">
            <xsd:import namespace="http://j2ee.netbeans.org/xsd/tableSchema" schemaLocation="ORDHEAD.xsd"/>
        </xsd:schema>
  </types>
  <message name="RetMsg">
    <part name="part" type="xsd:int"/>
  </message>
  <message name="outputMsg">
    <part name="part" element="ns:ORDHEAD"/>
  </message>
  <message name="inputMsg">
    <part name="part" element="ns:ORDHEAD"/>
  </message>
  <portType name="jdbcPortType">
    <operation name="insert">
      <input name="inputInsert" message="tns:inputMsg"/>
      <output name="outputInsert" message="tns:RetMsg"/>
    </operation>
    <operation name="update">
      <input name="inputUpdate" message="tns:inputMsg"/>
      <output name="outputUpdate" message="tns:RetMsg"/>
    </operation>
    <operation name="delete">
      <input name="inputDelete" message="tns:inputMsg"/>
      <output name="outputDelete" message="tns:RetMsg"/>
    </operation>
    <operation name="find">
      <input name="inputFind" message="tns:inputMsg"/>
      <output name="outputFind" message="tns:outputMsg"/>
    </operation>
    <operation name="pollrecords">
      <input name="inputPoll" message="tns:inputMsg"/>
    </operation>
  </portType>
  <binding name="binding" type="tns:jdbcPortType">
    <jdbc:binding xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/"/>
    <operation name="insert">
    <jdbc:operation xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/"/>
      <input name="inputInsert">
    <jdbc:input xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" MarkColumnName="" MarkColumnValue="" MoveRowToTableName="" PKName="ORHSEQ" PollMilliSeconds="5000" PollingPostProcessing="MoveRow" TableName="ORDHEAD" Transaction="NOTransaction" numberOfRecords="" operationType="insert" paramOrder="ORHSEQ,ORHTCD,ORHNUM,ORHRNM,ORHTYP,ORHPLC,ORHDLC,ORHPDT,ORHDDT,ORHTWT,ORHWUM,ORHTVL,ORHVUM,ORHPCT,ORHSCT,ORHIDT,ORHPCD,ORHSTA,ORHTAK" sql="insert into ORDHEAD (ORHSEQ,ORHTCD,ORHNUM,ORHRNM,ORHTYP,ORHPLC,ORHDLC,ORHPDT,ORHDDT,ORHTWT,ORHWUM,ORHTVL,ORHVUM,ORHPCT,ORHSCT,ORHIDT,ORHPCD,ORHSTA,ORHTAK) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)"/>
      </input>
      <output name="outputInsert">
    <jdbc:output xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" returnPartName="part"/>
      </output>
    </operation>
    <operation name="update">
    <jdbc:operation xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/"/>
      <input name="inputUpdate">
    <jdbc:input xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" MarkColumnName="" MarkColumnValue="" MoveRowToTableName="" PKName="ORHSEQ" PollMilliSeconds="5000" PollingPostProcessing="MoveRow" TableName="ORDHEAD" Transaction="NOTransaction" numberOfRecords="" operationType="update" paramOrder="ORHSEQ" sql="update ORDHEAD set ORHSTA  = &apos;P&apos; where  ORHSEQ  = ?"/>
      </input>
      <output name="outputUpdate">
    <jdbc:output xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" returnPartName="part"/>
      </output>
    </operation>
    <operation name="delete">
    <jdbc:operation xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/"/>
      <input name="inputDelete">
    <jdbc:input xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" MarkColumnName="" MarkColumnValue="" MoveRowToTableName="" PKName="ORHSEQ" PollMilliSeconds="5000" PollingPostProcessing="MoveRow" TableName="ORDHEAD" Transaction="NOTransaction" numberOfRecords="" operationType="delete" paramOrder="" sql="delete from ORDHEAD"/>
      </input>
      <output name="outputDelete">
    <jdbc:output xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" returnPartName="part"/>
      </output>
    </operation>
    <operation name="find">
    <jdbc:operation xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/"/>
      <input name="inputFind">
    <jdbc:input xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" MarkColumnName="" MarkColumnValue="" MoveRowToTableName="" PKName="ORHSEQ" PollMilliSeconds="5000" PollingPostProcessing="MoveRow" TableName="ORDHEAD" Transaction="NOTransaction" numberOfRecords="" operationType="find" paramOrder="" sql="select ORHSEQ,ORHTCD,ORHNUM,ORHRNM,ORHTYP,ORHPLC,ORHDLC,ORHPDT,ORHDDT,ORHTWT,ORHWUM,ORHTVL,ORHVUM,ORHPCT,ORHSCT,ORHIDT,ORHPCD,ORHSTA,ORHTAK from ORDHEAD"/>
      </input>
      <output name="outputFind">
    <jdbc:output xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" returnPartName="part"/>
      </output>
    </operation>
    <operation name="pollrecords">
    <jdbc:operation xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/"/>
      <input name="inputPoll">
    <jdbc:input xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" MarkColumnName="" MarkColumnValue="" MoveRowToTableName="" PKName="ORHSEQ" PollMilliSeconds="5000" PollingPostProcessing="Delete" TableName="ORDHEAD" Transaction="NOTransaction" numberOfRecords="" operationType="poll" paramOrder="" sql="select ORHSEQ,ORHTCD,ORHNUM,ORHRNM,ORHTYP,ORHPLC,ORHDLC,ORHPDT,ORHDDT,ORHTWT,ORHWUM,ORHTVL,ORHVUM,ORHPCT,ORHSCT,ORHIDT,ORHPCD,ORHSTA,ORHTAK from ORDHEAD"/>
      </input>
    </operation>
  </binding>
  <service name="service">
    <port name="port" binding="tns:binding">
    <jdbc:address xmlns:jdbc="http://schemas.sun.com/jbi/wsdl-extensions/jdbc/" jndiName="Local_OracleDB"/>
    </port>
  </service>
    <plink:partnerLinkType xmlns:plink="http://docs.oasis-open.org/wsbpel/2.0/plnktype" name="jdbcpartner">
        <plink:role name="jdbcPortTypeRole" portType="tns:jdbcPortType"/>
    </plink:partnerLinkType>
</definitions>

===========================================================================

Regards,
Akshay
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Paul Perez
Administrator
In reply to this post by Akshay
Hello

As far as I understand your log trace you have an issue with the number of parameter.  
By the way what DB do you use? Is it MS SQL Server ?


it is written

update ORDHEAD set ORHSTA = 'P' where ORHSEQ = ? Reason: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1876) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:703) ... 5 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:135) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1860) ... 6 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.populatePreparedStatement(JDBCDenormalizer.java:617) at

regards

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

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Akshay
This post has NOT been accepted by the mailing list yet.

Hello Paul,

I am using Oracle 10g Database. But I really do not understand what parameter it is missing even though I am passing parameters in BPEL assign activity.

Regards,
Akshay

On Apr 18, 2016 2:20 AM, "Paul Perez [via OpenESB Community Forum]" <[hidden email]> wrote:
Hello

As far as I understand your log trace you have an issue with the number of parameter.  
By the way what DB do you use? Is it MS SQL Server ?


it is written

update ORDHEAD set ORHSTA = 'P' where ORHSEQ = ? Reason: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1876) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.processInOut(OutboundMessageProcessor.java:703) ... 5 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message content to prepared statement, Error occured during populating PreparedStatement.Reason: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.denormalizeOutbound(JDBCDenormalizer.java:135) at org.glassfish.openesb.databasebc.OutboundMessageProcessor.executeOutboundSQL(OutboundMessageProcessor.java:1860) ... 6 more Caused by: javax.jbi.messaging.MessagingException: Unable to convert normalized message to prepared sql statement. input ParamOrder attribute does not have same number of columns as needed in the given sql prepared statement. at org.glassfish.openesb.databasebc.JDBCDenormalizer.populatePreparedStatement(JDBCDenormalizer.java:617) at

regards

Paul
www.pymma.com The best services on OpenESB



To unsubscribe from Database BC Exception Unable to convert normalized message to prepared sql statement, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Paul Perez
Administrator
Akshay

Please check on how your procstock works exactly.
In some cases the first parameter is the Response of your Request and consequently one parameter would be missing. It is the Case in some procstock in MS SQL

Let me know

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

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Akshay
This post has NOT been accepted by the mailing list yet.

Hello Paul,

Just simply, I have hard coded the input parameter of my update statement in BPEL assign activity using string literal and then deploy the project but still had the same issue.

Shall I show you the screen shot ?

Regards,
Akshay

On Apr 18, 2016 2:26 AM, "Paul Perez [via OpenESB Community Forum]" <[hidden email]> wrote:
Akshay

Please check on how your procstock works exactly.
In some cases the first parameter is the Response of your Request and consequently one parameter would be missing. It is the Case in some procstock in MS SQL

Let me know

PPe
www.pymma.com The best services on OpenESB



To unsubscribe from Database BC Exception Unable to convert normalized message to prepared sql statement, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Paul Perez
Administrator
Akshay

The best would be to have a project to run + a SQL script on Oracle to create the table and the proc stock
With this, we would be able to Go further.
Let me know
Bed time in London
see you tomorrow
Bye

PPe

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

Re: Database BC Exception Unable to convert normalized message to prepared sql statement

Akshay
This post has NOT been accepted by the mailing list yet.

Hello Paul,

Actually I need to update several tables based on my logic in BPEL so I have replaced the update statements with procedure call and it worked well.

Regards,
Akshay

On Apr 18, 2016 3:13 AM, "Paul Perez [via OpenESB Community Forum]" <[hidden email]> wrote:
Akshay

The best would be to have a project to run + a SQL script on Oracle to create the table and the proc stock
With this, we would be able to Go further.
Let me know
Bed time in London
see you tomorrow
Bye

PPe

www.pymma.com The best services on OpenESB



To unsubscribe from Database BC Exception Unable to convert normalized message to prepared sql statement, click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Database BC Exception Unable to convert normalized message to prepared sql statement

param.singh
This post has NOT been accepted by the mailing list yet.
Is it possible to send your code for review? This is a very normal code/xsd/mapping error which should be very easy to fix.

Param
[Logicoy]
-------- Original Message --------
Subject: Re: Database BC Exception Unable to convert normalized message
to prepared sql statement
From: "Akshay [via OpenESB Community Forum]"
<[hidden email]>
Date: Sun, April 17, 2016 9:02 pm
To: "param.singh" <[hidden email]>

Hello Paul,
Actually I need to update several tables based on my logic in BPEL so I have replaced the update statements with procedure call and it worked well.
Regards,
Akshay
On Apr 18, 2016 3:13 AM, "Paul Perez [via OpenESB Community Forum]" <[hidden email]> wrote:
Akshay

The best would be to have a project to run + a SQL script on Oracle to create the table and the proc stock
With this, we would be able to Go further.
Let me know
Bed time in London
see you tomorrow
Bye

PPe

www.pymma.com The best services on OpenESB



To unsubscribe from Database BC Exception Unable to convert normalized message to prepared sql statement, click here.
NAML



To start a new topic under OpenESB Community Forum, email [hidden email]
To unsubscribe from OpenESB Community Forum, click here.
NAML
Param
Logicoy Inc.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Database BC Exception Unable to convert normalized message to prepared sql statement

Akshay
This post has NOT been accepted by the mailing list yet.
Hello Param,

Please find attached entire project along with DB objects creation script.
I am using Oracle XE for this project, please you can create Composite application and deploy this project to see the error which I am facing.

Regards,
AkshayProject.zip
Loading...