[jira] [Updated] (ARTEMIS-1977) ASYNCIO can reduce sys-calls to retrieve I/O events

[ https://issues.apache.org/jira/browse/ARTEMIS-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1977: - Summary: ASYNCIO can reduce sys-calls to retrieve I/O events (was: ASYNCIO can reduce

[jira] [Comment Edited] (ARTEMIS-1977) ASYNCIO can reduce sys-calls to retrieve I/O completion events

[ https://issues.apache.org/jira/browse/ARTEMIS-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539754#comment-16539754 ] Francesco Nigro edited comment on ARTEMIS-1977 at 7/11/18 9:04 AM: ---

[jira] [Comment Edited] (ARTEMIS-1977) ASYNCIO can reduce sys-calls to retrieve I/O completion events

[ https://issues.apache.org/jira/browse/ARTEMIS-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539754#comment-16539754 ] Francesco Nigro edited comment on ARTEMIS-1977 at 7/11/18 9:03 AM: ---

[jira] [Comment Edited] (ARTEMIS-1977) ASYNCIO can reduce sys-calls to retrieve I/O completion events

[ https://issues.apache.org/jira/browse/ARTEMIS-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539754#comment-16539754 ] Francesco Nigro edited comment on ARTEMIS-1977 at 7/11/18 9:02 AM: ---

[jira] [Commented] (ARTEMIS-1977) ASYNCIO can reduce sys-calls to retrieve I/O completion events

[ https://issues.apache.org/jira/browse/ARTEMIS-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539754#comment-16539754 ] Francesco Nigro commented on ARTEMIS-1977: -- Currently there are low-latency DBMS that support

[jira] [Created] (ARTEMIS-1977) ASYNCIO can reduce sys-calls to retrieve I/O completion events

Francesco Nigro created ARTEMIS-1977: Summary: ASYNCIO can reduce sys-calls to retrieve I/O completion events Key: ARTEMIS-1977 URL: https://issues.apache.org/jira/browse/ARTEMIS-1977 Project:

[jira] [Updated] (ARTEMIS-1945) InVMNodeManager shared state should be volatile

[ https://issues.apache.org/jira/browse/ARTEMIS-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1945: - Affects Version/s: 2.6.2 Fix Version/s: 2.7.0 Component/s: Broker >

[jira] [Created] (ARTEMIS-1945) InVMNodeManager shared state should be volatile

Francesco Nigro created ARTEMIS-1945: Summary: InVMNodeManager shared state should be volatile Key: ARTEMIS-1945 URL: https://issues.apache.org/jira/browse/ARTEMIS-1945 Project: ActiveMQ Artemis

[jira] [Work started] (ARTEMIS-1876) InVMNodeManager shouldn't be used if no JDBC HA is configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-1876 started by Francesco Nigro. > InVMNodeManager shouldn't be used if no JDBC HA is configured >

[jira] [Updated] (ARTEMIS-1876) InVMNodeManager shouldn't be used if no JDBC HA is configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1876: - Description: When database persistence and no shared store option is being used,

[jira] [Updated] (ARTEMIS-1876) InVMNodeManager shouldn't be used if no JDBC HA is configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1876: - Summary: InVMNodeManager shouldn't be used if no JDBC HA is configured (was:

[jira] [Created] (ARTEMIS-1876) ARTEMIS-1762 InVMNodeManager shouldn't be used if no JDBC HA is configured

Francesco Nigro created ARTEMIS-1876: Summary: ARTEMIS-1762 InVMNodeManager shouldn't be used if no JDBC HA is configured Key: ARTEMIS-1876 URL: https://issues.apache.org/jira/browse/ARTEMIS-1876

[jira] [Commented] (ARTEMIS-1865) Shared Store Cluster Doesn't Work on CIFS

[ https://issues.apache.org/jira/browse/ARTEMIS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478691#comment-16478691 ] Francesco Nigro commented on ARTEMIS-1865: -- Given that currently it just use one file with [5

[jira] [Commented] (ARTEMIS-1865) Shared Store Cluster Doesn't Work on CIFS

[ https://issues.apache.org/jira/browse/ARTEMIS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474135#comment-16474135 ] Francesco Nigro commented on ARTEMIS-1865: -- How the shared store pairs are configured? There

[jira] [Closed] (ARTEMIS-1852) PageCursorProvider is leaking cleanup tasks while stopping

[ https://issues.apache.org/jira/browse/ARTEMIS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1852. > PageCursorProvider is leaking cleanup tasks while stopping >

[jira] [Resolved] (ARTEMIS-1852) PageCursorProvider is leaking cleanup tasks while stopping

[ https://issues.apache.org/jira/browse/ARTEMIS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro resolved ARTEMIS-1852. -- Resolution: Fixed > PageCursorProvider is leaking cleanup tasks while stopping >

[jira] [Work started] (ARTEMIS-1852) PageCursorProvider is leaking cleanup tasks while stopping

[ https://issues.apache.org/jira/browse/ARTEMIS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-1852 started by Francesco Nigro. > PageCursorProvider is leaking cleanup tasks while stopping >

[jira] [Updated] (ARTEMIS-1852) PageCursorProvider is leaking cleanup tasks while stopping

[ https://issues.apache.org/jira/browse/ARTEMIS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1852: - Description: PageCursorProviderImpl is not handling any pending cleanup tasks on stop,

[jira] [Created] (ARTEMIS-1852) PageCursorProvider is leaking cleanup tasks while stopping

Francesco Nigro created ARTEMIS-1852: Summary: PageCursorProvider is leaking cleanup tasks while stopping Key: ARTEMIS-1852 URL: https://issues.apache.org/jira/browse/ARTEMIS-1852 Project:

[jira] [Updated] (ARTEMIS-1811) NIOSequentialFile should use RandomAccessFile with heap ByteBuffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage and 

[jira] [Updated] (ARTEMIS-1811) NIOSequentialFile should use RandomAccessFile with heap ByteBuffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage and 

[jira] [Updated] (ARTEMIS-1811) NIOSequentialFile should use RandomAccessFile with heap ByteBuffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage and 

[jira] [Closed] (ARTEMIS-1816) OpenWire should avoid ByteArrayOutputStream lazy allocation

[ https://issues.apache.org/jira/browse/ARTEMIS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1816. Resolution: Fixed Fix Version/s: 2.5.1 > OpenWire should avoid

[jira] [Closed] (ARTEMIS-1829) Remove deprecated plugin's messageExpired implementations

[ https://issues.apache.org/jira/browse/ARTEMIS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1829. Resolution: Fixed > Remove deprecated plugin's messageExpired implementations >

[jira] [Closed] (ARTEMIS-1832) HAAutomaticBackupSharedStoreTest::basicDiscovery is dead

[ https://issues.apache.org/jira/browse/ARTEMIS-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1832. Resolution: Fixed > HAAutomaticBackupSharedStoreTest::basicDiscovery is dead >

[jira] [Updated] (ARTEMIS-1811) NIOSequentialFile should use RandomAccessFile with heap ByteBuffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage and 

[jira] [Updated] (ARTEMIS-1832) HAAutomaticBackupSharedStoreTest::basicDiscovery misconfigured

[ https://issues.apache.org/jira/browse/ARTEMIS-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1832: - Summary: HAAutomaticBackupSharedStoreTest::basicDiscovery misconfigured (was:

[jira] [Created] (ARTEMIS-1832) HAAutomaticBackupSharedStoreTest::basicDiscovery is not properly configured

Francesco Nigro created ARTEMIS-1832: Summary: HAAutomaticBackupSharedStoreTest::basicDiscovery is not properly configured Key: ARTEMIS-1832 URL: https://issues.apache.org/jira/browse/ARTEMIS-1832

[jira] [Work stopped] (ARTEMIS-1829) Remove deprecated plugin's messageExpired implementations

[ https://issues.apache.org/jira/browse/ARTEMIS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-1829 stopped by Francesco Nigro. > Remove deprecated plugin's messageExpired implementations >

[jira] [Updated] (ARTEMIS-1829) Remove deprecated plugin's messageExpired implementations

[ https://issues.apache.org/jira/browse/ARTEMIS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1829: - Summary: Remove deprecated plugin's messageExpired implementations (was:

[jira] [Created] (ARTEMIS-1829) ActiveMQServerPlugin::messageExpired deprecated implementations should be updated to the new version

Francesco Nigro created ARTEMIS-1829: Summary: ActiveMQServerPlugin::messageExpired deprecated implementations should be updated to the new version Key: ARTEMIS-1829 URL:

[jira] [Updated] (ARTEMIS-1811) NIOSequentialFile should use RandomAccessFile with heap ByteBuffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage and 

[jira] [Updated] (ARTEMIS-1811) NIOSequentialFile should use RandomAccessFile with heap ByteBuffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Summary: NIOSequentialFile should use RandomAccessFile with heap ByteBuffers (was:

[jira] [Updated] (ARTEMIS-1816) OpenWire should avoid ByteArrayOutputStream lazy allocation

[ https://issues.apache.org/jira/browse/ARTEMIS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1816: - Description: OpenWireMessageConverter::toAMQMessage on bytes messages is lazy

[jira] [Updated] (ARTEMIS-1816) OpenWire should avoid ByteArrayOutputStream lazy allocation

[ https://issues.apache.org/jira/browse/ARTEMIS-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1816: - Priority: Minor (was: Major) > OpenWire should avoid ByteArrayOutputStream lazy

[jira] [Created] (ARTEMIS-1816) OpenWire should avoid ByteArrayOutputStream lazy allocation

Francesco Nigro created ARTEMIS-1816: Summary: OpenWire should avoid ByteArrayOutputStream lazy allocation Key: ARTEMIS-1816 URL: https://issues.apache.org/jira/browse/ARTEMIS-1816 Project:

[jira] [Closed] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1784. Resolution: Fixed > JDBC NodeManager should just use DMBS clock >

[jira] [Updated] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1784: - Description: JdbcNodeManager rely on the correct synchronization between broker

[jira] [Updated] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1784: - Description: It avoid using the system clock to perform the locks logic by using the

[jira] [Closed] (ARTEMIS-1813) DB2 should avoid Blob to append data

[ https://issues.apache.org/jira/browse/ARTEMIS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1813. Resolution: Fixed > DB2 should avoid Blob to append data >

[jira] [Assigned] (ARTEMIS-1813) DB2 should avoid Blob to append data

[ https://issues.apache.org/jira/browse/ARTEMIS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro reassigned ARTEMIS-1813: Assignee: Francesco Nigro > DB2 should avoid Blob to append data >

[jira] [Resolved] (ARTEMIS-1808) LargeServerMessageImpl leaks direct ByteBuffer

[ https://issues.apache.org/jira/browse/ARTEMIS-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro resolved ARTEMIS-1808. -- Resolution: Fixed > LargeServerMessageImpl leaks direct ByteBuffer >

[jira] [Resolved] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check <=0 read length

[ https://issues.apache.org/jira/browse/ARTEMIS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro resolved ARTEMIS-1810. -- Resolution: Fixed > JDBCSequentialFileFactoryDriver should check <=0 read length >

[jira] [Resolved] (ARTEMIS-1788) JDBC HA should use JDBC Network Timeout

[ https://issues.apache.org/jira/browse/ARTEMIS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro resolved ARTEMIS-1788. -- Resolution: Fixed > JDBC HA should use JDBC Network Timeout >

[jira] [Updated] (ARTEMIS-1813) DB2 should avoid Blob to append data

[ https://issues.apache.org/jira/browse/ARTEMIS-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1813: - Summary: DB2 should avoid Blob to append data (was: DB2 BLOB size should be set to

[jira] [Created] (ARTEMIS-1813) DB2 BLOB size should be set to match its SQL definition

Francesco Nigro created ARTEMIS-1813: Summary: DB2 BLOB size should be set to match its SQL definition Key: ARTEMIS-1813 URL: https://issues.apache.org/jira/browse/ARTEMIS-1813 Project: ActiveMQ

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Updated] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

[ https://issues.apache.org/jira/browse/ARTEMIS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1811: - Description: JournalStorageManager::addBytesToLargeMessage is relying on the pooling of

[jira] [Created] (ARTEMIS-1811) JournalStorageManager::addBytesToLargeMessage should not use heap buffers

Francesco Nigro created ARTEMIS-1811: Summary: JournalStorageManager::addBytesToLargeMessage should not use heap buffers Key: ARTEMIS-1811 URL: https://issues.apache.org/jira/browse/ARTEMIS-1811

[jira] [Updated] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check <=0 read length

[ https://issues.apache.org/jira/browse/ARTEMIS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1810: - Summary: JDBCSequentialFileFactoryDriver should check <=0 read length (was:

[jira] [Updated] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check <= read length

[ https://issues.apache.org/jira/browse/ARTEMIS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1810: - Summary: JDBCSequentialFileFactoryDriver should check <= read length (was:

[jira] [Updated] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check zero and negative read length

[ https://issues.apache.org/jira/browse/ARTEMIS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1810: - Summary: JDBCSequentialFileFactoryDriver should check zero and negative read length

[jira] [Created] (ARTEMIS-1810) JDBCSequentialFileFactoryDriver should check negative read length

Francesco Nigro created ARTEMIS-1810: Summary: JDBCSequentialFileFactoryDriver should check negative read length Key: ARTEMIS-1810 URL: https://issues.apache.org/jira/browse/ARTEMIS-1810 Project:

[jira] [Created] (ARTEMIS-1808) LargeServerMessageImpl leaks direct ByteBuffer

Francesco Nigro created ARTEMIS-1808: Summary: LargeServerMessageImpl leaks direct ByteBuffer Key: ARTEMIS-1808 URL: https://issues.apache.org/jira/browse/ARTEMIS-1808 Project: ActiveMQ Artemis

[jira] [Commented] (ARTEMIS-1807) File-based Large Message encoding should use read-only mmap

[ https://issues.apache.org/jira/browse/ARTEMIS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438726#comment-16438726 ] Francesco Nigro commented on ARTEMIS-1807: -- The solution implemented is the less costly from

[jira] [Created] (ARTEMIS-1807) File-based Large Message encoding should use read-only mmap

Francesco Nigro created ARTEMIS-1807: Summary: File-based Large Message encoding should use read-only mmap Key: ARTEMIS-1807 URL: https://issues.apache.org/jira/browse/ARTEMIS-1807 Project:

[jira] [Resolved] (ARTEMIS-1806) JDBC Connection leaks

[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro resolved ARTEMIS-1806. -- Resolution: Fixed > JDBC Connection leaks > - > >

[jira] [Work started] (ARTEMIS-1806) JDBC Connection leaks

[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-1806 started by Francesco Nigro. > JDBC Connection leaks > - > >

[jira] [Updated] (ARTEMIS-1806) JDBC Connection leaks

[ https://issues.apache.org/jira/browse/ARTEMIS-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1806: - Affects Version/s: 2.5.0 Fix Version/s: 2.5.1 Component/s: Broker >

[jira] [Closed] (ARTEMIS-1774) Node Manager Store table name should be configurable

[ https://issues.apache.org/jira/browse/ARTEMIS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1774. Resolution: Fixed > Node Manager Store table name should be configurable >

[jira] [Created] (ARTEMIS-1806) JDBC Connection leaks

Francesco Nigro created ARTEMIS-1806: Summary: JDBC Connection leaks Key: ARTEMIS-1806 URL: https://issues.apache.org/jira/browse/ARTEMIS-1806 Project: ActiveMQ Artemis Issue Type: Bug

[jira] [Closed] (ARTEMIS-1772) Reduce memory footprint and allocations of QueueImpl

[ https://issues.apache.org/jira/browse/ARTEMIS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1772. Resolution: Fixed > Reduce memory footprint and allocations of QueueImpl >

[jira] [Reopened] (ARTEMIS-1774) Node Manager Store table name should be configurable

[ https://issues.apache.org/jira/browse/ARTEMIS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro reopened ARTEMIS-1774: -- It is not finished yet. > Node Manager Store table name should be configurable >

[jira] [Created] (ARTEMIS-1788) JDBC HA should use JDBC Network Timeout

Francesco Nigro created ARTEMIS-1788: Summary: JDBC HA should use JDBC Network Timeout Key: ARTEMIS-1788 URL: https://issues.apache.org/jira/browse/ARTEMIS-1788 Project: ActiveMQ Artemis

[jira] [Work started] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on ARTEMIS-1784 started by Francesco Nigro. > JDBC NodeManager should just use DMBS clock >

[jira] [Updated] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1784: - Affects Version/s: 2.5.0 Fix Version/s: 2.5.1 Component/s: Broker >

[jira] [Assigned] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

[ https://issues.apache.org/jira/browse/ARTEMIS-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro reassigned ARTEMIS-1784: Assignee: Francesco Nigro > JDBC NodeManager should just use DMBS clock >

[jira] [Created] (ARTEMIS-1784) JDBC NodeManager should just use DMBS clock

Francesco Nigro created ARTEMIS-1784: Summary: JDBC NodeManager should just use DMBS clock Key: ARTEMIS-1784 URL: https://issues.apache.org/jira/browse/ARTEMIS-1784 Project: ActiveMQ Artemis

[jira] [Assigned] (ARTEMIS-1653) Allow database tables to be created externally

[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro reassigned ARTEMIS-1653: Assignee: Francesco Nigro > Allow database tables to be created externally >

[jira] [Updated] (ARTEMIS-1772) Reduce memory footprint and allocations of QueueImpl

[ https://issues.apache.org/jira/browse/ARTEMIS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1772: - Description: Each message referenced into QueueImpl is using Atomic* and boxed types

[jira] [Assigned] (ARTEMIS-1772) Reduce memory footprint and allocations of QueueImpl

[ https://issues.apache.org/jira/browse/ARTEMIS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro reassigned ARTEMIS-1772: Assignee: Francesco Nigro > Reduce memory footprint and allocations of QueueImpl

[jira] [Closed] (ARTEMIS-1774) Node Manager Store table name should be configurable

[ https://issues.apache.org/jira/browse/ARTEMIS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1774. Resolution: Fixed > Node Manager Store table name should be configurable >

[jira] [Closed] (ARTEMIS-1771) Porting of JDBC NodeManager into 1.5.5

[ https://issues.apache.org/jira/browse/ARTEMIS-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1771. Resolution: Fixed > Porting of JDBC NodeManager into 1.5.5 >

[jira] [Created] (ARTEMIS-1774) Node Manager Store table name should be configurable

Francesco Nigro created ARTEMIS-1774: Summary: Node Manager Store table name should be configurable Key: ARTEMIS-1774 URL: https://issues.apache.org/jira/browse/ARTEMIS-1774 Project: ActiveMQ

[jira] [Updated] (ARTEMIS-1771) Porting of JDBC NodeManager into 1.5.5

[ https://issues.apache.org/jira/browse/ARTEMIS-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1771: - Description: It includes most of the changes related to the JDBC support, including: -

[jira] [Closed] (ARTEMIS-1757) Improve DB2 compatibility

[ https://issues.apache.org/jira/browse/ARTEMIS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1757. Resolution: Fixed > Improve DB2 compatibility > - > >

[jira] [Created] (ARTEMIS-1772) Reduce memory footprint and allocations of QueueImpl

Francesco Nigro created ARTEMIS-1772: Summary: Reduce memory footprint and allocations of QueueImpl Key: ARTEMIS-1772 URL: https://issues.apache.org/jira/browse/ARTEMIS-1772 Project: ActiveMQ

[jira] [Updated] (ARTEMIS-1771) Porting of JDBC NodeManager into 1.5.5

[ https://issues.apache.org/jira/browse/ARTEMIS-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1771: - Affects Version/s: 1.5.5 Component/s: Broker Summary: Porting of

[jira] [Created] (ARTEMIS-1771) Porting of JDBC NodeManager into 1.x

Francesco Nigro created ARTEMIS-1771: Summary: Porting of JDBC NodeManager into 1.x Key: ARTEMIS-1771 URL: https://issues.apache.org/jira/browse/ARTEMIS-1771 Project: ActiveMQ Artemis

[jira] [Closed] (ARTEMIS-1762) JdbcNodeManager shouldn't be used if no HA is configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1762. Resolution: Fixed > JdbcNodeManager shouldn't be used if no HA is configured >

[jira] [Closed] (ARTEMIS-1760) JDBC HA should have configurable tolerance of DB time misalignment

[ https://issues.apache.org/jira/browse/ARTEMIS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1760. Resolution: Fixed > JDBC HA should have configurable tolerance of DB time misalignment >

[jira] [Closed] (ARTEMIS-1767) JDBC Lock Acquisition Timeout should behave like the file based version

[ https://issues.apache.org/jira/browse/ARTEMIS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro closed ARTEMIS-1767. Resolution: Fixed > JDBC Lock Acquisition Timeout should behave like the file based

[jira] [Created] (ARTEMIS-1767) JDBC Lock Acquisition Timeout should behave like the file based version

Francesco Nigro created ARTEMIS-1767: Summary: JDBC Lock Acquisition Timeout should behave like the file based version Key: ARTEMIS-1767 URL: https://issues.apache.org/jira/browse/ARTEMIS-1767

[jira] [Updated] (ARTEMIS-1762) Jdbc NodeManagers shouldn't be used if HA is not configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Affects Version/s: 2.5.0 Fix Version/s: 2.5.1 Component/s: Broker >

[jira] [Updated] (ARTEMIS-1762) JdbcNodeManager shouldn't be used if no HA is configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Summary: JdbcNodeManager shouldn't be used if no HA is configured (was:

[jira] [Updated] (ARTEMIS-1762) JdbcNodeManager shouldn't be used if HA is not configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Summary: JdbcNodeManager shouldn't be used if HA is not configured (was: Jdbc

[jira] [Updated] (ARTEMIS-1762) Jdbc NodeManagers shouldn't be used if HA is not configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Description: JDBC based journal is using a JdbcNodeManager when no HA is configured:

[jira] [Updated] (ARTEMIS-1762) Jdbc NodeManagers shouldn't be used if HA is not configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Description: JDBC based journal is using a JdbcNodeManager when no HA is configured:

[jira] [Updated] (ARTEMIS-1762) Jdbc NodeManagers shouldn't be used if HA is not configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Summary: Jdbc NodeManagers shouldn't be used if HA is not configured (was: File/Jdbc

[jira] [Updated] (ARTEMIS-1762) File/Jdbc NodeManagers shouldn't be used if HA is not configured

[ https://issues.apache.org/jira/browse/ARTEMIS-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1762: - Summary: File/Jdbc NodeManagers shouldn't be used if HA is not configured (was:

[jira] [Created] (ARTEMIS-1762) NodeManager shouldn't exists if HA is not configured

Francesco Nigro created ARTEMIS-1762: Summary: NodeManager shouldn't exists if HA is not configured Key: ARTEMIS-1762 URL: https://issues.apache.org/jira/browse/ARTEMIS-1762 Project: ActiveMQ

[jira] [Updated] (ARTEMIS-1760) JDBC HA should have configurable tolerance of DB time misalignment

[ https://issues.apache.org/jira/browse/ARTEMIS-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated ARTEMIS-1760: - Affects Version/s: 2.5.0 Fix Version/s: 2.5.1 Component/s: Broker >

[jira] [Created] (ARTEMIS-1760) JDBC HA should have configurable tolerance of DB time misalignment

Francesco Nigro created ARTEMIS-1760: Summary: JDBC HA should have configurable tolerance of DB time misalignment Key: ARTEMIS-1760 URL: https://issues.apache.org/jira/browse/ARTEMIS-1760

[jira] [Created] (ARTEMIS-1757) Improve DB2 compatibility

Francesco Nigro created ARTEMIS-1757: Summary: Improve DB2 compatibility Key: ARTEMIS-1757 URL: https://issues.apache.org/jira/browse/ARTEMIS-1757 Project: ActiveMQ Artemis Issue Type:

<    5   6   7   8   9   10   11   12   >