You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Ron Gavlin (JIRA)" <ji...@apache.org> on 2008/09/18 05:39:52 UTC

[jira] Created: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
--------------------------------------------------------------------------------------------------------

                 Key: SM-1581
                 URL: https://issues.apache.org/activemq/browse/SM-1581
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-cxf-bc
    Affects Versions: 3.2.2
            Reporter: Ron Gavlin
         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip

I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
I have lowWaterMark=2 and highWaterMark=4.
I send 10 requests which results in 10 temporary queues being allocated. 
I expected the highWaterMark=4 to bound the number of temp queues allocated.
This appears to be a bug.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang resolved SM-1581.
------------------------------

    Fix Version/s: 3.2.3
                   3.3
       Resolution: Fixed

> cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1581
>                 URL: https://issues.apache.org/activemq/browse/SM-1581
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Freeman Fang
>            Priority: Critical
>             Fix For: 3.2.3, 3.3
>
>         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip
>
>
> I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
> I have lowWaterMark=2 and highWaterMark=4.
> I send 10 requests which results in 10 temporary queues being allocated. 
> I expected the highWaterMark=4 to bound the number of temp queues allocated.
> This appears to be a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated SM-1581:
--------------------------------

    Fix Version/s: servicemix-cxf-bc-2008.01

> cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1581
>                 URL: https://issues.apache.org/activemq/browse/SM-1581
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Freeman Fang
>            Priority: Critical
>             Fix For: 3.2.3, 3.3, servicemix-cxf-bc-2008.01
>
>         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip
>
>
> I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
> I have lowWaterMark=2 and highWaterMark=4.
> I send 10 requests which results in 10 temporary queues being allocated. 
> I expected the highWaterMark=4 to bound the number of temp queues allocated.
> This appears to be a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/SM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45887#action_45887 ] 

Freeman Fang commented on SM-1581:
----------------------------------

Hi Ron,
I believe my fix for SM-1593 also fix this issue, would you please verify it?

Thanks
Freeman

> cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1581
>                 URL: https://issues.apache.org/activemq/browse/SM-1581
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Freeman Fang
>            Priority: Critical
>         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip
>
>
> I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
> I have lowWaterMark=2 and highWaterMark=4.
> I send 10 requests which results in 10 temporary queues being allocated. 
> I expected the highWaterMark=4 to bound the number of temp queues allocated.
> This appears to be a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Work started: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on SM-1581 started by Freeman Fang.

> cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1581
>                 URL: https://issues.apache.org/activemq/browse/SM-1581
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Freeman Fang
>            Priority: Critical
>         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip
>
>
> I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
> I have lowWaterMark=2 and highWaterMark=4.
> I send 10 requests which results in 10 temporary queues being allocated. 
> I expected the highWaterMark=4 to bound the number of temp queues allocated.
> This appears to be a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

Posted by "Ron Gavlin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Gavlin updated SM-1581:
---------------------------

    Priority: Critical  (was: Major)

Raising this to critical since I know of no workaround.

> cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1581
>                 URL: https://issues.apache.org/activemq/browse/SM-1581
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Freeman Fang
>            Priority: Critical
>         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip
>
>
> I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
> I have lowWaterMark=2 and highWaterMark=4.
> I send 10 requests which results in 10 temporary queues being allocated. 
> I expected the highWaterMark=4 to bound the number of temp queues allocated.
> This appears to be a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (SM-1581) cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation

Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang reassigned SM-1581:
--------------------------------

    Assignee: Freeman Fang

> cxf-bc provider jms conduit session pool highWaterMark does not bound replyTo temporary queue allocation
> --------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1581
>                 URL: https://issues.apache.org/activemq/browse/SM-1581
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-cxf-bc
>    Affects Versions: 3.2.2
>            Reporter: Ron Gavlin
>            Assignee: Freeman Fang
>         Attachments: cxf-wsdl-first-http2jms-bridge-20080917.zip
>
>
> I did some testing with the cxf-bc provider jms.conduit sessionPool highWaterMark.
> I have lowWaterMark=2 and highWaterMark=4.
> I send 10 requests which results in 10 temporary queues being allocated. 
> I expected the highWaterMark=4 to bound the number of temp queues allocated.
> This appears to be a bug.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.