Bug 1296634 - [GSS](6.4.z) Interrupt thread on paging could cause: "Critical IO Error, shutting down the server"
Summary: [GSS](6.4.z) Interrupt thread on paging could cause: "Critical IO Error, shut...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: CR1
: EAP 6.4.7
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
URL:
Whiteboard:
Depends On: 1290841 1278334
Blocks: eap647-payload 1299528
TreeView+ depends on / blocked
 
Reported: 2016-01-07 17:18 UTC by Miroslav Novak
Modified: 2019-10-10 10:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 11:56:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miroslav Novak 2016-01-07 17:18:39 UTC
There is unexpected server shutdown during in test scenario - "OOM in remote JCA topology in cluster with restart" 
1. Start EAP servers 1 and 3 in HornetQ cluster (jms cluster) with deployed queues InQueue and OutQueue
2. Start other 2 EAP servers 2 and 4 (mdb servers) which has configured resource adapter to connect to jms cluster
3. Send 50 000 small to InQueue to jms cluster
4. Deploy MDB to mdb servers
   - MDB consumes messages from InQueue and for each message send new message to OutQueue. MDB makes JNDI lookup for OutQueue for each message.
5. During processing of messages by MDB cause out of memory on heap on server 2
6. Wait 5 minutes and restart server 2
7. Wait some time until the rest (if there are some) of messages are consumed from InQueue
8. Receive messages from OutQueue

Test failed in step 6. when "Critical IO Error, shutting down the server." was logged on server-3 and server shuted down. There are set lower values for max-size-bytes (1MB) and max-size-bytes (100KB) to stress paging.

Customer impact:
if client is disconnected in the moment when new page file is being created. It leads to unexpected interrupt of page file creation which as consequence shutdowns the server.

Comment 7 Peter Mackay 2016-03-11 12:54:05 UTC
Verified with EAP 6.4.7.CP.CR2

Comment 8 Petr Penicka 2017-01-17 11:56:09 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.


Note You need to log in before you can comment on or make changes to this bug.