activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Lewis (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APLO-93) Support initial read/write interval in heartbeat monitor
Date Wed, 30 Nov 2011 21:05:40 GMT

     [ https://issues.apache.org/jira/browse/APLO-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stan Lewis updated APLO-93:
---------------------------

    Attachment: 0001-Add-initial-write-read-check-delay-remove-check-in-p.patch

Here's a patch, the current openwire tests still work.  However I notice there's an occasional
NPE:

Exception in thread "hawtdispatch-DEFAULT-1" java.lang.NullPointerException
	at org.apache.activemq.apollo.broker.protocol.HeartBeatMonitor.schedual_check_writes(HeartBeatMonitor.scala:43)
	at org.apache.activemq.apollo.broker.protocol.HeartBeatMonitor$$anonfun$start$1.apply$mcV$sp(HeartBeatMonitor.scala:71)
	at org.fusesource.hawtdispatch.package$$anon$4.run(hawtdispatch.scala:347)
	at org.fusesource.hawtdispatch.internal.TimerThread$2.run(TimerThread.java:153)
	at org.fusesource.hawtdispatch.internal.SerialDispatchQueue.run(SerialDispatchQueue.java:83)
	at org.fusesource.hawtdispatch.internal.pool.SimpleThread.run(SimpleThread.java:61)

Think it would be safe to break out of the schedual_check_read/schedual_check_write loop in
this case?  I suspect this is just because the connection is torn down before the monitor
has checked the connection.
                
> Support initial read/write interval in heartbeat monitor
> --------------------------------------------------------
>
>                 Key: APLO-93
>                 URL: https://issues.apache.org/jira/browse/APLO-93
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>          Components: apollo-broker
>    Affects Versions: 1.0-beta5
>            Reporter: Stan Lewis
>         Attachments: 0001-Add-initial-write-read-check-delay-remove-check-in-p.patch
>
>
> Currently an openwire client can only specify equal values for maxInactivityDuration
and maxInactivityDurationInitialDelay when connecting to the broker, be good to add support
for the second item into HeartBeatMonitor so this restriction can be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message