Bug 777713 (SOA-229) - It is possible to store message to message store with null classification but it is not possible to remove it
Summary: It is possible to store message to message store with null classification but...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-229
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 IR8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 Beta 2
Assignee: Mark Little
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-13 08:47 UTC by Jiri Pechanec
Modified: 2008-01-21 09:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-21 09:41:36 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-229 0 None None None Never

Description Jiri Pechanec 2007-12-13 08:47:15 UTC 
project_key: SOA

See description of JBESB-1405
Comment 1 Jiri Pechanec 2007-12-13 08:47:25 UTC 
Link: Added: This issue depends JBESB-1405
Comment 2 Jiri Pechanec 2007-12-20 09:26:35 UTC 
Fails on MySQL

2007-12-20 10:22:34,756 ERROR [org.jboss.soa.esb.actions.MessagePersister] Could not store message.
org.jboss.soa.esb.services.persistence.MessageStoreException: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'classification' at row 1
        at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.addMessage(DBMessageStoreImpl.java:101)
        at org.jboss.soa.esb.actions.MessagePersister.process(MessagePersister.java:68)
        at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
        at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'classification' at row 1
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2983)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
        at com.mysql.jdbc.Connection.execSQL(Connection.java:3256)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1313)
        at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:874)
        at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execute(WrappedPreparedStatement.java:209)
        at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.insert(DBMessageStoreImpl.java:468)
        at org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl.addMessage(DBMessageStoreImpl.java:96)
        ... 6 more
Comment 3 Jiri Pechanec 2008-01-21 09:41:36 UTC 
Verified in beta 2
Note You need to log in before you can comment on or make changes to this bug.