[JIRA] Issue Comment Edited: (MQ-194) imqcmd can't connect to broker when conflicting ports are specified

  • From: "amyk (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Issue Comment Edited: (MQ-194) imqcmd can't connect to broker when conflicting ports are specified
  • Date: Sun, 17 Feb 2013 03:09:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


    [ 
http://java.net/jira/browse/MQ-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356331#action_356331
 ] 

amyk edited comment on MQ-194 at 2/17/13 3:09 AM:
--------------------------------------------------

1. As expected, the broker log shows  the 'admin' service is not started 
because of "Address already in use"

[#|2013-02-16T17:26:53.678-0800|SEVERE|5.0|imq.log.Logger|_ThreadID=1;_ThreadName=main;|ERROR
 [B3009]: Unable to start service admin: [B4001]: Unable to open protocol tcp 
for admin service using com.sun.messaging.jmq.jmsserver.net.tcp.TcpProtocol: 
Address already in use

2. As expected, imqcmd using -b <broker-host:portmapper-port> will fail 
immediately with JMSException "[C4098]: Unknown broker service: admin"

Note: imqcmd -b hostName:portNumber option is for broker's portmapper - filed 
MQ-281 to clarify this explicitly in documentation

3. The 'jms' service port works as expected

      was (Author: amyk):
    1. As expected, the broker log shows  the 'admin' service is not started 
because of "Address already in use"

[#|2013-02-16T17:26:53.678-0800|SEVERE|5.0|imq.log.Logger|_ThreadID=1;_ThreadName=main;|ERROR
 [B3009]: Unable to start service admin: [B4001]: Unable to open protocol tcp 
for admin service using com.sun.messaging.jmq.jmsserver.net.tcp.TcpProtocol: 
Address already in use

2. As expected, imqcmd using -b <broker-host:portmapper-port> will fail 
immediately with JMSException "[C4098]: Unknown broker service: admin"

Note: imqcmd -b option is for broker's portmapper 

3. The 'jms' service port work as expected
  
> imqcmd can't connect to broker when conflicting ports are specified
> -------------------------------------------------------------------
>
>                 Key: MQ-194
>                 URL: http://java.net/jira/browse/MQ-194
>             Project: mq
>          Issue Type: Bug
>          Components: broker-core
>         Environment: Glassfish v4.0 b45, Windows
>            Reporter: tak09
>            Assignee: amyk
>            Priority: Minor
>
> Message broker stops responding when conflicting ports are specified.
> To reproduce the problem
> 1.Edit glassfish3\mq\lib\props\broker\default.properties
> imq.admin.tcp.port=1000
> imq.jms.tcp.port=1000
> 2.Start imqbrokerd
> imqbrokerd
> 3.Connect to imqbrokerd from imqcmd
> imqcmd shutdown bkr
> 4.Unable to shutdown as connection to the imqbrokerd is not established.
> The problem can be reproduced by changing the port number after the 
> imqbrokerd has been started.
> 1.Start imqbrokerd.
> 2.imqcmd update svc -n admin -o port=1000
> 3.imqcmd update svc -n jms -o port=1000
> 4.imqcmd shutdown bkr
> Unable to shutdown.
> I opened GLASSFISH-19025 for the same issue, but David asked me to refile 
> the same issue against MQ. 

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

        


[JIRA] Issue Comment Edited: (MQ-194) imqcmd can't connect to broker when conflicting ports are specified

amyk (JIRA) 02/17/2013

<Possible follow-up(s)>

[JIRA] Issue Comment Edited: (MQ-194) imqcmd can't connect to broker when conflicting ports are specified

amyk (JIRA) 02/17/2013
Terms of Use; Privacy Policy; Copyright ©2013-2015 (revision 20150226.965aeb8)
 
 
Close
loading
Please Confirm
Close