History | Log In     View a printable version of the current page. Get help!  
Issue Details (XML | Word)

Key: HJMS-121
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Colin Crist
Reporter: Adam
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Allow HermesJMS to use large Topics

Created: 15/Mar/10 01:00 PM   Updated: 01/Apr/10 07:09 PM
Component/s: FIX
Affects Version/s: 1.13
Fix Version/s: 1.14

Environment: DAtabase

 Description  « Hide
In my environment, I have topic sizes up to 5000 characters. This is because SonicMQ allows for the use of MULTITOPICS. ie... If you could like to publish to multiple topics, the topic name would be "TOPIC1|TOPIC2|TOPIC3..etc..."

If you could increase the size of the topic field, that would be great, thanks.


Is there a simple way for me to increase the maximum topic size in the message store. The current size limit is 256. Unfortunately I have topics which are larger than this (due to the use of MULTITOPICS in SonicMQ implementation).

Can I increase the size? or is this something that needs to fixed in the code?

java.sql.SQLException: A truncation error was encountered trying to shrink VARCHAR '.......' to length 256. Query: insert into stores values (?, ?, ?, ?) Parameters: [....]
at org.apache.commons.dbutils.QueryRunner.rethrow(QueryRunner.java:330)
at org.apache.commons.dbutils.QueryRunner.update(QueryRunner.java:399)
at hermes.store.schema.DefaultJDBCAdapter.insert(DefaultJDBCAdapter.java:149)
at hermes.store.SingleUserMessageStore.store(SingleUserMessageStore.java:230)
at hermes.browser.tasks.RecordDestinationTask.invoke(RecordDestinationTask.java:85)
at hermes.browser.tasks.TaskSupport.run(TaskSupport.java:175)
at hermes.browser.tasks.ThreadPool.run(ThreadPool.java:170)
at java.lang.Thread.run(Thread.java:619)

 All   Comments   Change History      Sort Order:
Colin Crist [17/Mar/10 12:31 PM]
Build of 1.14 updated at http://hermesjms.com/patches

Adam [01/Apr/10 07:09 PM]
I can confirm this is working as described.

Thanks for fixing this Colin.