Bug 928400 - pageSize >= maxSize causing inappropriate server state
Summary: pageSize >= maxSize causing inappropriate server state
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER7
: EAP 6.1.1
Assignee: Clebert Suconic
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-27 15:00 UTC by Dmytro Pogrebniuk
Modified: 2014-05-27 01:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
There was an issue in previous versions of JBoss EAP 6 where an incorrect configuration was allowed. Using a message address configuration where `page-size-bytes` is set larger or equal to `max-size-bytes` resulted in an inappropriate server state, and may have caused a starvation on paging because the server would not be able to depage messages. This issue was fixed by not allowing the server to start with the above incorrect configuration, and will now throw an exception when attempted.
Clone Of:
Environment:
Last Closed: 2013-09-16 20:28:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dmytro Pogrebniuk 2013-03-27 15:00:32 UTC 
Description of problem:
pageSize >= maxSize causes next events:

1. Failure in initialisation: java.lang.IllegalStateException to be thrown
2. HQ121005: JMS Server Manager Caching command for createQueue for Queue1 since the JMS Server is not active yet
3. HQ121005: JMS Server Manager Caching command for createConnectionFactory for InVmConnectionFactory since the JMS Server is not active yet
4. HQ121005: JMS Server Manager Caching command for createConnectionFactory for RemoteConnectionFactory since the JMS Server is not active yet
5. javax.naming.NameNotFoundException: jms/RemoteConnectionFactory -- service jboss.naming.context.java.jboss.exported.jms.RemoteConnectionFactory

Version-Release number of selected component (if applicable):
2.3.0.CR1

Expected results:
Warning ptinted to log

Additional info:
https://community.jboss.org/thread/159908
Comment 4 Miroslav Novak 2013-08-22 09:55:13 UTC 
BZ is in incorrect state. 

Based on info above this is fixed in EAP 6.1.1.ER7. Server won't allow to start HQ when page >= maxSize with error:
11:47:27,971 ERROR [org.hornetq.core.server] (MSC service thread 1-5) HQ224000: Failure in initialisation: java.lang.IllegalStateException: pageSize for address jms.queue.InQueue >= maxSize. Normally pageSize should be significantly smaller than maxSize, ms: 10485760 ps 10485760
        at org.hornetq.core.paging.impl.PagingStoreImpl.<init>(PagingStoreImpl.java:147) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2]
...

Setting as verified in EAP 6.1.1.ER7 (HQ 2.2.5.Final)
Note You need to log in before you can comment on or make changes to this bug.