[jira] [Created] (AMQ-4644) informix Routine (empty_blob) can not be resolved

["Stefan (JIRA)" <ji...@apache.org>]

Stefan created AMQ-4644:
---------------------------

             Summary: informix Routine (empty_blob) can not be resolved
                 Key: AMQ-4644
                 URL: https://issues.apache.org/jira/browse/AMQ-4644
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.8.0
         Environment: Solaris
            Reporter: Stefan


Using the following Setup:

Solaris x64  / Informix: 11.70FC7DE

broker configuration:

<amq:broker  useJmx="true" brokerName="jdbcBroker" persistent="true" xmlns="http://activemq.apache.org/schema/core">

	<amq:destinations>
	      <queue physicalName="jms/myque" />
	</amq:destinations>

    <amq:persistenceAdapter>
    	<amq:jdbcPersistenceAdapter 
           adapter="#informixAdapter" dataDirectory="${activemq.data}" dataSource="#informix-ds" lockKeepAlivePeriod="10000" createTablesOnStartup="true">
    	     <amq:locker>
    	        <amq:database-locker lockAcquireSleepInterval="5000"/>
    	     </amq:locker>
    	 </amq:jdbcPersistenceAdapter>
	</amq:persistenceAdapter>

    <amq:transportConnectors>
       <amq:transportConnector name="default" uri="tcp://0.0.0.0:61616"/>
    </amq:transportConnectors>
</amq:broker>

<bean id="informixAdapter" class="org.apache.activemq.store.jdbc.adapter.InformixJDBCAdapter"/>


If a message is sent to the broker, I get the following error:

Routine (empty_blob) can not be resolved.



InformixJDBCAdapter extends BlobJDBCAdapter
-->
In org.apache.activemq.store.jdbc.adapter.BlobJDBCAdapter, I saw the following code that issues the error:

    @Override
    public void setStatements(Statements statements) {

        String addMessageStatement = "INSERT INTO "
            + statements.getFullMessageTableName()
            + "(ID, MSGID_PROD, MSGID_SEQ, CONTAINER, EXPIRATION, PRIORITY, MSG, XID) VALUES (?, ?, ?, ?, ?, ?, empty_blob(), empty_blob())";





--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira