You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Eric (JIRA)" <ji...@apache.org> on 2008/01/24 17:31:24 UTC

[jira] Created: (AMQ-1568) Temporary queues, Network of Brokers, Embedded VM

Temporary queues, Network of Brokers, Embedded VM
-------------------------------------------------

                 Key: AMQ-1568
                 URL: https://issues.apache.org/activemq/browse/AMQ-1568
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 4.1.0
         Environment: Linux
            Reporter: Eric


Context

A simple question/answer mechanism between a client process with an embedded broker, and a server process with an embedded broker, on two different servers. The two embedded brokers are linked with a "double" network broker (client broker referenced on the server, server broker referenced on the client)

The server process 
 - listens on a fixed "JNDI defined" queue.
 - sends an answer, on the JMSReplyTo queue defined by the received message.

The client process enter a loop (5 times)
    - it generates 100 threads. 
    - Each thread 
         - creates a temporary queue. 
         - waits 5 seconds
         - enter a loop (10 times)
                  - send a message on the fixed "JNDI defined" queue with a setJMSReplyTo defined with the temporary queue
                  - wait for the answer on the temporary queue
         - delete the temporary queue

During the test, some threads are blocked on their temporary queue, waiting for the answer.
When I look the two embedded brokers with web site, I could find the temporary queue created on each embedded broker, and message enqueued on the server side and not sent to the client side.

The same test seems to be OK, when I use standalone ActiveMQ instances and tcp transport connector to link client and server process to their own ActiveMQ instance.

Eric

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

[jira] Commented: (AMQ-1568) Temporary queues, Network of Brokers, Embedded VM

Posted by "Eric (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQ-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41204#action_41204 ] 

Eric commented on AMQ-1568:
---------------------------

I would like to close this issue. 

I upgraded to 5.0.0 and had the same problems.

ttmdev helped me to resolve this problem. I had to add temporisation before freeing resources.

Thank you.

> Temporary queues, Network of Brokers, Embedded VM
> -------------------------------------------------
>
>                 Key: AMQ-1568
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1568
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>         Environment: Linux
>            Reporter: Eric
>
> Context
> A simple question/answer mechanism between a client process with an embedded broker, and a server process with an embedded broker, on two different servers. The two embedded brokers are linked with a "double" network broker (client broker referenced on the server, server broker referenced on the client)
> The server process 
>  - listens on a fixed "JNDI defined" queue.
>  - sends an answer, on the JMSReplyTo queue defined by the received message.
> The client process enter a loop (5 times)
>     - it generates 100 threads. 
>     - Each thread 
>          - creates a temporary queue. 
>          - waits 5 seconds
>          - enter a loop (10 times)
>                   - send a message on the fixed "JNDI defined" queue with a setJMSReplyTo defined with the temporary queue
>                   - wait for the answer on the temporary queue
>          - delete the temporary queue
> During the test, some threads are blocked on their temporary queue, waiting for the answer.
> When I look the two embedded brokers with web site, I could find the temporary queue created on each embedded broker, and message enqueued on the server side and not sent to the client side.
> The same test seems to be OK, when I use standalone ActiveMQ instances and tcp transport connector to link client and server process to their own ActiveMQ instance.
> Eric

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

[jira] Closed: (AMQ-1568) Temporary queues, Network of Brokers, Embedded VM

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

Eric closed AMQ-1568.
---------------------

    Resolution: Fixed

It was a global problem of freeing resources too quickly. Such problem seems to happen more often, with embedded brokers than with distinct instance connected with tcp transport.

> Temporary queues, Network of Brokers, Embedded VM
> -------------------------------------------------
>
>                 Key: AMQ-1568
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1568
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>         Environment: Linux
>            Reporter: Eric
>
> Context
> A simple question/answer mechanism between a client process with an embedded broker, and a server process with an embedded broker, on two different servers. The two embedded brokers are linked with a "double" network broker (client broker referenced on the server, server broker referenced on the client)
> The server process 
>  - listens on a fixed "JNDI defined" queue.
>  - sends an answer, on the JMSReplyTo queue defined by the received message.
> The client process enter a loop (5 times)
>     - it generates 100 threads. 
>     - Each thread 
>          - creates a temporary queue. 
>          - waits 5 seconds
>          - enter a loop (10 times)
>                   - send a message on the fixed "JNDI defined" queue with a setJMSReplyTo defined with the temporary queue
>                   - wait for the answer on the temporary queue
>          - delete the temporary queue
> During the test, some threads are blocked on their temporary queue, waiting for the answer.
> When I look the two embedded brokers with web site, I could find the temporary queue created on each embedded broker, and message enqueued on the server side and not sent to the client side.
> The same test seems to be OK, when I use standalone ActiveMQ instances and tcp transport connector to link client and server process to their own ActiveMQ instance.
> Eric

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