qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8257) Sybase message store not supporting empty messages
Date Tue, 06 Nov 2018 10:19:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676506#comment-16676506

Alex Rudyy commented on QPID-8257:

Hi Olivier,
Could you please provide Sybase exception stack trace for adding a message with an empty body?

I am a bit confused here as JDBC message store is not setting explicitly content column to
null for an empty message content. A  binary stream is always written for a message content
(see {{org.apache.qpid.server.store.jdbc.AbstractJDBCMessageStore#addContent}}).

It seems your patch cannot be applied as JDBC store tests are failing with Derby on attempt
to declare nullable blob field (content blob null). We need to look for a bit different solution.

> Sybase message store not supporting empty messages
> --------------------------------------------------
>                 Key: QPID-8257
>                 URL: https://issues.apache.org/jira/browse/QPID-8257
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-7.0.3
>            Reporter: Olivier VERMEULEN
>            Priority: Major
> Unlike other databases Sybase default nullability for a column is "NOT NULL".
> And since we don't specify anything when creating the QPID_MESSAGE_CONTENT table, the
"content" column defaults to "NOT NULL".
> So when we send an empty message, this constraint is broken and we receive a SybSQLException...

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message