Bug 51595 - org.apache.tomcat.jdbc.pool.jmx.ConnectionPool should be Serializeable
Summary: org.apache.tomcat.jdbc.pool.jmx.ConnectionPool should be Serializeable
Status: NEEDINFO
Alias: None
Product: Tomcat Modules
Classification: Unclassified
Component: jdbc-pool (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-01 10:19 UTC by Patric Rufflar
Modified: 2012-03-20 14:15 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patric Rufflar 2011-08-01 10:19:15 UTC
org.apache.tomcat.jdbc.pool.jmx.ConnectionPool should be Serializeable,
otherwise it's impossible to retrieve remote JMX notifications:

WARNUNG: Failed to deserialize a notification: java.io.NotSerializableException: org.apache.tomcat.jdbc.pool.jmx.ConnectionPool

(from jconsole output console)
Comment 1 Filip Hanik 2012-03-20 14:15:31 UTC
hi Patric,
you can still subscribe to JMX events even without retrieving this object by itself. Am I missing something?
If I serialize that object, you wont get much back, as the actual implementation would be marked transient, and you just get an empty shell