qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ganesh Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DISPATCH-246) Router crash when creating connector with same port as existing listener
Date Thu, 31 Mar 2016 01:16:25 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219153#comment-15219153
] 

Ganesh Murthy edited comment on DISPATCH-246 at 3/31/16 1:16 AM:
-----------------------------------------------------------------

Case 1 - In the case when the listener port is the same as the connector port, the router
actually "tries" to communicate with the listening port and crashes in the process because
of a bug in the code. 

Case 2 - In the case when the listener and connector ports are different there is no crash
(as Ernie as correctly noted) because the "actual" communication is has not happened yet.


To reproduce the crash, run qdmanage create connector on a non listening port say 24568

{noformat}
qdmanage CREATE --type connector port=24568
{noformat}

We do not observe any crash yet.

Now, try to create a listener on the same port as above to initiate the communication process
{noformat}
qdmanage CREATE --type listener port=24568
{noformat}

The above command will cause the crash to happen.

After applying the fix, the crash should not happen in either case


was (Author: ganeshmurthy):
Case 1 - In the case when the listener port is the same as the connector port, the router
actually "tries" to communicate with the listening port and crashes in the process because
a bug in the code. 

Case 2 - In the case when the listener and connector ports are different there is no crash
(as Ernie as correctly noted) because the "actual" communication is has not happened yet.
To reproduce the crash, run qdmanage create connector on a non listening port say 23456

{noformat}
qdmanage CREATE --type connector port=24568
{noformat}

We do not observe any crash

Now, try to create a listener on the same port as above to initiate the communication process
{noformat}
qdmanage CREATE --type listener port=24568
{noformat}

The above command will cause the crash to happen.

After applying the fix, the crash should not happen in either case

> Router crash when creating connector with same port as existing listener
> ------------------------------------------------------------------------
>
>                 Key: DISPATCH-246
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-246
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 0.6
>            Reporter: Ernest Allen
>            Assignee: Ganesh Murthy
>
> - Start a router with a listener on a port. The listener's role doesn't seem to matter.
> - After the router is running, attempt to call the CREATE method using the same port
on which the router is listening.
> I'm getting an immediate crash 100% of the time.
> Here is the json passed to the method call:
> {
>   "body": {
>     "type": "connector",
>     "port": "20102",
>     "role": "normal"
>   },
>   "properties": {
>     "to": "_topo/0/QDR.A/$management",
>     "reply_to": "amqp:/_topo/0/QDR.A/temp.ezDGhBZEEg+4LMn",
>     "correlation_id": "16"
>   },
>   "application_properties": {
>     "operation": "CREATE",
>     "type": "connector"
>   }
> } 
> This was done through the console. I'm not sure the syntax to do the same thing through
qdmanage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message