Bug 1010952 – JON server plugin is exposing TRANSACTION child element under caches

Bug 1010952 - JON server plugin is exposing TRANSACTION child element under caches

Summary:	JON server plugin is exposing TRANSACTION child element under caches

Status:	NEW

Aliases:	None

Product:	JBoss Data Grid 6
Classification:	JBoss
Component:	JON Plugin (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity low
Target Milestone:	CR1
Target Release:	6.4.0
Assigned To:	Tristan Tarrant
QA Contact:	Martin Gencur
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-23 07:17 EDT by Tomas Sykora
Modified:	2014-11-06 11:33 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Known Issue
Doc Text:	A bug in the JBoss Data Grid server plug-in for JBoss Operation Network causes an unnecessary TRANSACTION child element under Infinispan caches started within a JBoss Data Grid server. </para> <para> As a result, users will see a TRANSACTION element under JBoss Data Grid server caches. This can lead to confusion as JBoss Data Grid server does not support transactions.
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
probablyWronglyExposedTransactionChildElement.png (169.46 KB, image/png) 2013-09-23 07:34 EDT, Tomas Sykora	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tomas Sykora 2013-09-23 07:17:40 EDT

I suppose, JDG in client-server (remote) mode still does not support transactions.

However, we can see exposed and "clickable" (+ operations) element under each of JDG caches. 

I hope, we need to remove it totally to not confuse customers etc. about functionality which does not really exists.

See attached picture.

Out of curiosity: This operation invocation is failing of course, and with error:

java.lang.Exception: JBAS011002: Failed to invoke operation: null, rolled-back=true
	at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)

Comment 2 Tomas Sykora 2013-09-23 07:34:50 EDT

Created attachment 801582 [details]
probablyWronglyExposedTransactionChildElement.png

Comment 5 Tomas Sykora 2014-11-06 11:33:08 EST

This is rather cosmetic but also confusing for customers. Get rid of it for 6.4.0.

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