Bugs item #780914, was opened at 2003-07-31 20:48
Message generated for change (Comment added) made by srivatsanp
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=780914&group_id=22866
Category: JBossMX
Group: None
>Status: Open
Resolution: Works For Me
Pr
I implemented tests and example classes, which work in clustered
environment,
but they were apparently using serializable objects.
I was thinking that it would be sufficien to document this requirement.
How can "this" be replaced with ObjectName generically by
HAServiceMBeanSupport?
-=Ivelin=-
-
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 3-August-2003
JBoss daily test results
SUMMARY
Number of tests run: 1464
Successful tests: 1454
Errors:7
Failures: 3
--
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
There is a race condition i the
DistributedReplicantManager.isMasterReplica(String) that shows up when this
method is called from within a notifyKeyListeners as shown by this stack trace:
Thread "main"@65 status: RUNNING
- isMasterReplica():437,
org.jboss.ha.framework.server.DistributedReplican
Bugs item #782498, was opened at 2003-08-03 21:37
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=782498&group_id=22866
Category: JBossCMP
Group: v3.2
Status: Open
Resolution: No
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
Yes, the HAServiceMBeanSupport.sendNotification(Notification) which calls
sendNotificationRemote is just dumping the notification object to the wire
unchanged.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Juha Lindfors wrote:
The MBeanS
On Sun, 3 Aug 2003, Scott M Stark wrote:
> So the question is why are we not using the ObjectName for the source?
The MBeanServer is supposed to replace the 'this' reference with the
correct object name before the notification is passed on to the listener.
If this is not working there's something
The javax.management.AttributeChangeNotification takes a source equal to the
MBean generating the notification, and we are literally using 'this' of the
MBean implementation rather than its ObjectName. This seems inconsistent with
the decoupled nature of JMX and leads immeadiately to problems wi
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS==
===
===
14 matches
Mail list logo
