Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 816989 - Invoking start() on cache via JMX fails with java.io.StreamCorruptedException
Summary: Invoking start() on cache via JMX fails with java.io.StreamCorruptedException
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.0.0
Assignee: Tristan Tarrant
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-27 12:02 UTC by Martin Gencur
Modified: 2013-10-07 00:25 UTC (History)
1 user (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
stack trace (deleted)
2012-04-27 12:02 UTC, Martin Gencur
no flags Details

Description Martin Gencur 2012-04-27 12:02:49 UTC
Created attachment 580745 [details]
stack trace

Description of problem:

When I start 2 servers in a cluster and invoke sequentially stop() and then start() method on a cache via JMX (on either of the servers), the start operation fails and the server keeps throwing the attached exception.

Comment 1 Tristan Tarrant 2012-05-09 13:40:28 UTC
The start and stop methods will not be exposed via JMX for 6.0.0, as we need to tie in with the AS/EAP service lifecycle. Marking this issue as solved for ER8.


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