[JIRA] Created: (GRIZZLY-1414) When Grizzly connection service enabled for both 'jms' and 'admin' services, if MQ broker starts with -useRmiRegistry, JVM terminates soon after broker starts up

  • From: "amyk (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Created: (GRIZZLY-1414) When Grizzly connection service enabled for both 'jms' and 'admin' services, if MQ broker starts with -useRmiRegistry, JVM terminates soon after broker starts up
  • Date: Wed, 23 Jan 2013 06:43:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated

When Grizzly connection service enabled for both 'jms' and 'admin' services,  
if MQ broker starts with -useRmiRegistry,  JVM terminates soon after broker 
starts up
-------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: GRIZZLY-1414
                 URL: http://java.net/jira/browse/GRIZZLY-1414
             Project: grizzly
          Issue Type: Bug
          Components: framework
    Affects Versions: 2.3
            Reporter: amyk


unzip lastest GlassFish 4.0 b72 latest-glassfish.zip
cd glassfish3/mq/bin
start MQ broker with Grizzly connection service enabled for both 'jms' and  
'admin' services:

./imqbrokerd -Dimq.admin.threadpool_model=grizzly 
-Dimq.jms.threadpool_model=grizzly -useRmiRegistry -tty

As soon as the broker starts up, the JVM terminates - actually the JVM 
shutdown hook got called (that log message may or may not be able to show 
up). The imqbrokerd option -useRmiRegistry specifies to use an external RMI 
registry which in this case there is no one, so the broker's jmxrmi connector 
service won't start but the broker should continue running.


[#|2013-01-22T22:05:21.079-0800|FORCE|5.0|imq.log.Logger|_ThreadID=1;_ThreadName=main;|[B1039]:
 Broker "imqbroker@joe-s10-3:7676" ready.
|#]
[#|2013-01-22T22:06:43.069-0800|FORCE|5.0|imq.log.Logger|_ThreadID=18;_ThreadName=Thread-3;|[B1047]:
 Shutting down broker...[brokerShutdownHook:Thread[Thread-3,5,main]]


-- 
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] Created: (GRIZZLY-1414) When Grizzly connection service enabled for both 'jms' and 'admin' services, if MQ broker starts with -useRmiRegistry, JVM terminates soon after broker starts up

amyk (JIRA) 01/23/2013

[JIRA] Resolved: (GRIZZLY-1414) When Grizzly connection service enabled for both 'jms' and 'admin' services, if MQ broker starts with -useRmiRegistry, JVM terminates soon after broker starts up

oleksiys (JIRA) 01/23/2013

[JIRA] Commented: (GRIZZLY-1414) When Grizzly connection service enabled for both 'jms' and 'admin' services, if MQ broker starts with -useRmiRegistry, JVM terminates soon after broker starts up

amyk (JIRA) 01/23/2013

[JIRA] Updated: (GRIZZLY-1414) Add is/setDaemon(...) setting to ThreadPoolConfig

oleksiys (JIRA) 01/25/2013

[JIRA] Reopened: (GRIZZLY-1414) Add is/setDaemon(...) setting to ThreadPoolConfig

oleksiys (JIRA) 01/25/2013

[JIRA] Resolved: (GRIZZLY-1414) Add is/setDaemon(...) setting to ThreadPoolConfig

oleksiys (JIRA) 01/25/2013
Terms of Use; Privacy Policy; Copyright ©2013-2014 (revision 20140418.2d69abc)
 
 
Close
loading
Please Confirm
Close