[
https://issues.apache.org/jira/browse/QPID-8257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676577#comment-16676577
]
Olivier VERMEULEN commented on QPID-8257:
-----------------------------------------
Hello Alex,
Here is (part of) the stack we get when sending a message with an empty body:
2018-10-23 14:45:23,927 ERROR [IO-/10.25.1.142:34140]
(o.a.q.s.u.ServerScopedRuntimeException) - Error adding content for message 1:
Attempt to insert NULL value into column 'content', table
'TPK0002630_321682_01666C53613C.MUREXDB.broker2_QPID_MESSAGE_CONTENT'; column
does not allow nulls. Update fails.
com.sybase.jdbc4.jdbc.SybSQLException: Attempt to insert NULL value into column
'content', table
'TPK0002630_321682_01666C53613C.MUREXDB.broker2_QPID_MESSAGE_CONTENT'; column
does not allow nulls. Update fails.
Regarding Derby I saw that and pushed another patch this morning to support
both use cases.
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
