[jira] Updated: (GERONIMO-2737) Server shutdown time has increased significantly because of ActiveMQ v4
[ https://issues.apache.org/jira/browse/GERONIMO-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn updated GERONIMO-2737: --- Fix Version/s: (was: 2.0.x) Server shutdown time has increased significantly because of ActiveMQ v4 --- Key: GERONIMO-2737 URL: https://issues.apache.org/jira/browse/GERONIMO-2737 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, startup/shutdown Affects Versions: 2.0-M2 Environment: Tomcat6 JEE5 assembly from 2.0 trunk Rev496565 on Core Duo system w/ WinXP and logging set to DEBUG level Reporter: Donald Woods Server shutdowns (either Ctrl+C or with shutdown script) is taking a lot longer in 2.0 than it did in 1.1.1. The ActiveMQ.stomp.default and ActiveMQ.tcp.default gbeans are taking 11 secs. to shutdown, while everything else only takes 5 secs. - 15:13:29,921 DEBUG [BasicKernel] Starting kernel shutdown . . . 15:13:30,390 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSServer,name=ActiveMQ State changed from running to stopping 15:13:30,390 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.stomp.default State changed from running to stopping 15:13:36,093 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.stomp.default State changed from stopping to stopped 15:13:36,093 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.tcp.default State changed from running to stopping 15:13:41,125 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.tcp.default State changed from stopping to stopped . . . 15:13:46,265 DEBUG [BasicKernel] Kernel shutdown complete -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2737) Server shutdown time has increased significantly because of ActiveMQ v4
[ https://issues.apache.org/jira/browse/GERONIMO-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-2737: --- Fix Version/s: (was: 2.0) 2.0.x Server shutdown time has increased significantly because of ActiveMQ v4 --- Key: GERONIMO-2737 URL: https://issues.apache.org/jira/browse/GERONIMO-2737 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, startup/shutdown Affects Versions: 2.0-M2 Environment: Tomcat6 JEE5 assembly from 2.0 trunk Rev496565 on Core Duo system w/ WinXP and logging set to DEBUG level Reporter: Donald Woods Fix For: 2.0.x Server shutdowns (either Ctrl+C or with shutdown script) is taking a lot longer in 2.0 than it did in 1.1.1. The ActiveMQ.stomp.default and ActiveMQ.tcp.default gbeans are taking 11 secs. to shutdown, while everything else only takes 5 secs. - 15:13:29,921 DEBUG [BasicKernel] Starting kernel shutdown . . . 15:13:30,390 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSServer,name=ActiveMQ State changed from running to stopping 15:13:30,390 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.stomp.default State changed from running to stopping 15:13:36,093 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.stomp.default State changed from stopping to stopped 15:13:36,093 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.tcp.default State changed from running to stopping 15:13:41,125 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.tcp.default State changed from stopping to stopped . . . 15:13:46,265 DEBUG [BasicKernel] Kernel shutdown complete -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2737) Server shutdown time has increased significantly because of ActiveMQ v4
[ https://issues.apache.org/jira/browse/GERONIMO-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasad Kashyap updated GERONIMO-2737: - Fix Version/s: (was: 2.0-M5) 2.0 Server shutdown time has increased significantly because of ActiveMQ v4 --- Key: GERONIMO-2737 URL: https://issues.apache.org/jira/browse/GERONIMO-2737 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: ActiveMQ, startup/shutdown Affects Versions: 2.0-M2 Environment: Tomcat6 JEE5 assembly from 2.0 trunk Rev496565 on Core Duo system w/ WinXP and logging set to DEBUG level Reporter: Donald Woods Fix For: 2.0 Server shutdowns (either Ctrl+C or with shutdown script) is taking a lot longer in 2.0 than it did in 1.1.1. The ActiveMQ.stomp.default and ActiveMQ.tcp.default gbeans are taking 11 secs. to shutdown, while everything else only takes 5 secs. - 15:13:29,921 DEBUG [BasicKernel] Starting kernel shutdown . . . 15:13:30,390 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSServer,name=ActiveMQ State changed from running to stopping 15:13:30,390 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.stomp.default State changed from running to stopping 15:13:36,093 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.stomp.default State changed from stopping to stopped 15:13:36,093 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.tcp.default State changed from running to stopping 15:13:41,125 DEBUG [GBeanInstanceState] GBeanInstanceState for: org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-broker/2.0-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.tcp.default State changed from stopping to stopped . . . 15:13:46,265 DEBUG [BasicKernel] Kernel shutdown complete -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
