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

Bug 855359

Summary:	org.infinispan.remoting.RemoteExceptionHandlingWithStateTransferTest.testThrowExceptionFromRemoteInterceptor fails randomly
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Anna Manukyan <amanukya>
Component:	Infinispan	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	jdg-bugs
Target Milestone:	ER12
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:20:47 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:

Description Anna Manukyan 2012-09-07 13:59:36 UTC

You can find the log here:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPORTS-FUNC/job/edg-60-ispn-testsuite-rhel/jdk=java16_default,label=RHEL5_x86/26/testReport/org.infinispan.remoting/RemoteExceptionHandlingWithStateTransferTest/testThrowExceptionFromRemoteInterceptor/

Comment 1 Anna Manukyan 2012-09-12 12:47:55 UTC

The bug doesn't appear when the test is run separately.

Comment 2 mark yarborough 2012-09-12 13:24:18 UTC

Per ttarrant and mgencur, these are related to tests running in non-representative loading environments and will likely not occur in actual customer deployments. These are not regressions or blockers so will be moved to 6.1. They do not need to be release noted for 6.0.

Comment 3 mark yarborough 2012-11-14 14:42:13 UTC

ttarrant will add jira links as appropriate.

Comment 4 JBoss JIRA Server 2012-12-04 08:04:59 UTC

Galder Zamarreño <galder.zamarreno> made a comment on jira ISPN-2511

[~amanukyan], the test report is gone (404), can we find a better way to attach failure information? 

Seems like the QE jenkins instance is very aggressive with removing old builds.

Comment 5 Martin Gencur 2012-12-04 08:13:57 UTC

Anna, whenever we provide a link to Jenkins, we should lock that particular build so that it does not disappear when Jenkins is cleaned up (on regular basis). Howevever, we cannot lock the build forever -> it might be better to just attach the stacktrace and not the link. Thanks

Comment 6 JBoss JIRA Server 2012-12-05 08:36:57 UTC

Anna Manukyan <amanukya> made a comment on jira ISPN-2511

Hi,

sorry, I still cannot provide new logs, as the mead repo is still not recovered after update to the EAP 6.0.1 tag, and I was not able to run the testsuit.

Sorry for inconvenience.

Best regards,
Anna.

Comment 8 Tristan Tarrant 2013-02-22 09:14:09 UTC

amanukya reports the issue hasn't happened recently, so it might be safe to assume it is resolved

Comment 9 JBoss JIRA Server 2013-03-04 08:49:12 UTC

Anna Manukyan <amanukya> updated the status of jira ISPN-2511 to Resolved

Comment 10 JBoss JIRA Server 2013-03-04 08:49:12 UTC

Anna Manukyan <amanukya> made a comment on jira ISPN-2511

The bug doesn't appear any more.

Comment 11 Anna Manukyan 2013-03-04 08:49:46 UTC

This bug doesn't appear anymore. Is verified for JDG 6.1.0.ER12.

Comment 13 Red Hat Bugzilla 2025-02-10 03:20:47 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.