[JIRA] Issue Comment Edited: (MQ-225) Imqbrokerd fails to start on a different port, if kill -9 the broker process then occupies the broker port by another application

  • From: "amyk (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Issue Comment Edited: (MQ-225) Imqbrokerd fails to start on a different port, if kill -9 the broker process then occupies the broker port by another application
  • Date: Sun, 17 Feb 2013 06:11:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated


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

amyk edited comment on MQ-225 at 2/17/13 6:11 AM:
--------------------------------------------------

1. 'kill process' will send TERM signal to the process on Linux.  In that 
case, the broker shutdown hook will be invoked and it will clean up the 
broker lock file.  So assuming you were using kill -9 

2. If you kill -9 the broker process, and re-use the broker port to run for 
other application, and at same time expect to restart the broker on a 
different port using the same broker data store, you should remove the broker 
instance's lock file first.   This is by design to protect the broker 
instance's data store. 

      was (Author: amyk):
    1. 'kill process' will send TERM signal to the process on Linux.  In that 
case, the broker shutdown hook will be invoked and it will clean up the 
broker lock file.  So assuming you were using kill -9 

2. If you kill -9 the broker process, and re-use the broker port to run for 
other application, you should remove the broker instance's lock file first.   
This is by design to protect the broker instance's data store. 
  
> Imqbrokerd fails to start on a different port, if kill -9 the broker 
> process then occupies the broker port by another application
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MQ-225
>                 URL: http://java.net/jira/browse/MQ-225
>             Project: mq
>          Issue Type: Bug
>         Environment: Glassfish v4 b45 Linux
>            Reporter: tak09
>            Assignee: Ed Bratt
>            Priority: Trivial
>
> Imqbrokerd fails to start even if an available port number is specified.
>  
> 1.Start imqbrokerd with an instance name and port number. (Lock file is 
> generated.)
> For example, execute the following command.
> {code}
> # imqbrokerd -port 8000 -name instance1
> {code}
> 2.Kill the Java process for the imqbrokerd. 
> For  example, execute the following commands. 
> {code}
> # ps -eH
> # kill processnumber
> {code}
> (Use -H option which displays the process hierarchy to identify the parent 
> java process for imqbrokerd. )
> 3. Confirm that there is lock file remaining. 
> {code}
> # ls -l glassfish/domains/domain1/imq/instances/instance1/lock
> {code}
> 4. Occupy the port 8000 with another application. For example, start any 
> other user application that uses port 8000. 
> 5. Start imqbrokerd with the same instance name and different port number. 
> (Lock file is generated.)
> For example, execute the following command. 
> {code}
> # imqbrokerd -port 8001 -name instance1
> {code}
> This fails with the following error even though an available port is 
> specified.
> {code}
> [#|2012-10-25T10:09:03.377+1100|SEVERE|5.0|imq.log.Logger|_ThreadID=1;_ThreadName=main;|ERROR
>  [B3087]: The broker has detected an active lock file:
> /usr/local/glassfish3/glassfish/domains/domain1/imq/instances/instance1/lock
> This file indicates that there is another copy of the broker running
> on localhost.localdomain:8000 that is also using the instance name 
> "instance1".
> Please use a different instance name or terminate the broker on 
> localhost.localdomain:8000.
> |#]
> {code}

-- 
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-225) Imqbrokerd fails to start on a different port, if kill -9 the broker process then occupies the broker port by another application

amyk (JIRA) 02/17/2013

<Possible follow-up(s)>

[JIRA] Issue Comment Edited: (MQ-225) Imqbrokerd fails to start on a different port, if kill -9 the broker process then occupies the broker port by another application

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