Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1688362

Summary:	(6.4.z) HORNETQ-1559 Page.write() should throw exception if file is closed
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Tomas Hofman <thofman>
Component:	RESTEasy	Assignee:	Tomas Hofman <thofman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.21	CC:	bmaxwell, weli
Target Milestone:	CR1
Target Release:	EAP 6.4.22
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:42:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1613417, 1631773

Description Tomas Hofman 2019-03-13 15:39:55 UTC

This is clone of https://issues.jboss.org/browse/HORNETQ-1559

=============================================================

In Page.write(final PagedMessage message) if the page file is closed it returns silently. The caller has no way to know that if the message is paged to file or not.
It should throw an exception so that the caller can handle it correctly.
This causes random failure in test org.hornetq.tests.integration.client.PagingTest#testExpireLargeMessageOnPaging().

Comment 1 Tomas Hofman 2019-03-13 15:45:25 UTC

This is to account for a code change in linked component upgrade.

Comment 2 Tomas Hofman 2019-03-13 15:47:53 UTC

@Brad will you ack?

Comment 3 Tomas Hofman 2019-03-13 15:48:55 UTC

@Brad ^

Comment 4 Tomas Hofman 2019-03-13 15:49:29 UTC

PR: https://github.com/hornetq/hornetq/commit/f388b3056b6e4cb0181f2797ac131893ddb956ab

No upstream required.

Comment 5 Peter Mackay 2019-05-08 20:29:05 UTC

Regression tests passed
Verified with EAP 6.4.22.CP.CR1