Messaging doesn`t startup becouse MaxSize has been exceeded

[amalcaraz]

Hi all,
We have a serious problem with Pageable Channel support in JBoss Messaging 1.4.0.GA.

If you send, without consumers, MaxSize+n messages to a queue and you stop the application server it never start again.

When you try to start it, it throws this exception:

java.lang.IllegalStateException: Cannot load channel 2 since the fullSize parameter is too small to load all the required references, fullSize needs to be at least 200 it is currently 101

I think (I have studied your source code) it is because Messaging gets DownSizeCache messages in memory (to improve persistence), and when you stop the AS the number of messages in memory is MaxSize + DownCacheSize.

The test environment is:

JBoss Application Server 4.2.1
JBoss Messaging 1.4.0.GA
JDK 1.5.0 update 12
Windows XP / Linux RedHat
PostgreSQL 8.2.4

Could you help me to solve this issue?

Thanks in advance,
-Abel

[timfox]

You must have changed the fullSize parameter for your destination.

If you change it back to its original value it shoud work.

[amalcaraz]

Hi Tim,

You must have changed the fullSize parameter for your destination

No, I haven't change the fullSize parameter.

I have upgrade to SP1 and the nightmare persist:
If I send fullSize + downCacheSize - 1 messages to a queue (*without consumers) then this queue will not be deployed at next boot.

The test has been performed using a fresh instalation of JBAS 4.2.1.GA and JBM 1.4.0.SP1 with PostgreSQL in a non-clustered environment. I have used the '/queue/testQueue' destination (a test queue deployed in default destination-services.xml) and I have send 200100 messages (1K each one). But the problem.....persist.

Any help will be wellcome,

[timfox]

amalcaraz-

Could you add a JIRA report, with instructions on replication, then someone will take a look?

Thanks.

[amalcaraz]

Hi Tim,
it`s done: JBMESSAGING-1139.

Thanks for your replies,
-Abel