[jira] Commented: (AMQ-1762) Field Type for ID column on table activemq_msgs should be increased from integer to bigint for postgres

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

    [ https://issues.apache.org/activemq/browse/AMQ-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61708#action_61708 ] 

Dziugas Baltrunas commented on AMQ-1762:
----------------------------------------

Was this issue fixed in any of 4.1.X or 5.X tree? For systems with some 200 msg / sec throughput, INTEGER reaches it's boundary in few months, so I believe this problem affects quite a lot of heavy users. Our workaround was to ALTER TABLE.

> Field Type for ID column on table activemq_msgs should be increased from integer to bigint for postgres
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1762
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1762
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.1.0
>         Environment: Linux, with Postgres/EnterpriseDB
>            Reporter: Yves Sandfort
>             Fix For: NEEDS_REVIEWED
>
>         Attachments: PostgresqlJDBCAdapter.java.diff.txt
>
>
> As the postgres size for an int is limited to: 2147483647 you can easily reach that number on a loaded ActiveMQ server within weeks. This is very hard to nail issue, as you get an exception like: Batch entry 0 INSERT INTO ACTIVEMQ_MSGS(ID, MSGID_PROD, MSGID_SEQ, CONTAINER, EXPIRATION, MSG) VALUES (2152101302, ID:cnmacoll2.ms.de.cdip.net-2970-1212478745177-0:1397:1:1, 1, queue://CNMACollector_1000474_1000474, 0, <stream of 820 bytes>) was aborted.
> Which gives you no clue about the real issue, so we searched for all kinds of issues around. 
> However we figured out it was the ID column.
> Not sure if this happens on other plattforms too, but at least on all PostgreSQL versions.
> While checking this, someone should make sure that not the ID inside the java code will be the next issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.