[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Updated: (AMQ-1762) Field Type for ID column on table
From:       "Bruce Snyder (JIRA)" <jira () apache ! org>
Date:       2008-09-25 19:12:52
Message-ID: 1150453082.1222369972708.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/activemq/browse/AMQ-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Bruce Snyder updated AMQ-1762:
------------------------------

    Attachment: PostgresqlJDBCAdapter.java.diff.txt

Attaching a patch to add a small change to the ID column type for PostgreSQL from \
INTEGER to BIGINT. 

> 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: 5.3.0
> 
> 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.


[prev in list] [next in list] [prev in thread] [next in thread]