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)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
stack trace (5.76 KB, text/plain)
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.