You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2006/08/09 09:15:23 UTC

[jira] Created: (AMQ-872) Don't monitor activity on vm transports

Don't monitor activity on vm transports
---------------------------------------

                 Key: AMQ-872
                 URL: https://issues.apache.org/activemq/browse/AMQ-872
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
            Reporter: Rob Davies
         Assigned To: Rob Davies
             Fix For: 4.0.3


currently all transport servers montitor transport channels for activity - closing down blocked transports. This can occassionally result in  stranged side-affects for  networks - which use an inbound vm:// channel to the broker in their communications

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (AMQ-872) Don't monitor activity on vm transports

Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-872?page=all ]

Rob Davies resolved AMQ-872.
----------------------------

    Resolution: Fixed

if TransportServer is vm - don't initialize Inactivity Monitor

> Don't monitor activity on vm transports
> ---------------------------------------
>
>                 Key: AMQ-872
>                 URL: https://issues.apache.org/activemq/browse/AMQ-872
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Rob Davies
>         Assigned To: Rob Davies
>             Fix For: 4.0.3
>
>
> currently all transport servers montitor transport channels for activity - closing down blocked transports. This can occassionally result in  stranged side-affects for  networks - which use an inbound vm:// channel to the broker in their communications

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (AMQ-872) Don't monitor activity on vm transports

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQ-872?page=all ]

Hiram Chirino updated AMQ-872:
------------------------------

    Fix Version/s: 4.0.2
                       (was: 4.0.3)

> Don't monitor activity on vm transports
> ---------------------------------------
>
>                 Key: AMQ-872
>                 URL: https://issues.apache.org/activemq/browse/AMQ-872
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Rob Davies
>         Assigned To: Rob Davies
>             Fix For: 4.0.2
>
>
> currently all transport servers montitor transport channels for activity - closing down blocked transports. This can occassionally result in  stranged side-affects for  networks - which use an inbound vm:// channel to the broker in their communications

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira