March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1547) deploy directories not cleaned up

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1547?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1547: ------------------------------ Comment: was deleted (was: Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 901210|https://bugzilla.redhat.com/show_bug.cgi?id=901210] from POST to MODIFIED) > deploy directories not cleaned up > --------------------------------- > > Key: WFLY-1547 > URL: https://issues.jboss.org/browse/WFLY-1547 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Alpha1 > Reporter: Shaun Appleton > Assignee: jaikiran pai > Fix For: 8.0.0.Beta1 > > Attachments: deployment_with_hack_no_hook.txt > > > JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories. > The following reproduces this - > i) ensure run.conf has the -Xrs set > ii) ensure deployments has a deployable .ear in it > iii) ./run standalone.sh and allow the deployments to deploy > iv) stop the EAP process ie kill <process_id> > v) observe content tmp/vfs > (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP) > This will eventually cause problems with lack of disk space. > Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems. > It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1547) deploy directories not cleaned up

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1547?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1547: ------------------------------ Comment: was deleted (was: James Livingston <jlivings(a)redhat.com> changed the Status of [bug 901210|https://bugzilla.redhat.com/show_bug.cgi?id=901210] from ASSIGNED to POST) > deploy directories not cleaned up > --------------------------------- > > Key: WFLY-1547 > URL: https://issues.jboss.org/browse/WFLY-1547 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Alpha1 > Reporter: Shaun Appleton > Assignee: jaikiran pai > Fix For: 8.0.0.Beta1 > > Attachments: deployment_with_hack_no_hook.txt > > > JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories. > The following reproduces this - > i) ensure run.conf has the -Xrs set > ii) ensure deployments has a deployable .ear in it > iii) ./run standalone.sh and allow the deployments to deploy > iv) stop the EAP process ie kill <process_id> > v) observe content tmp/vfs > (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP) > This will eventually cause problems with lack of disk space. > Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems. > It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1547) deploy directories not cleaned up

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1547?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1547: ------------------------------ Comment: was deleted (was: Paul Gier <pgier(a)redhat.com> changed the Status of [bug 901210|https://bugzilla.redhat.com/show_bug.cgi?id=901210] from MODIFIED to ON_QA) > deploy directories not cleaned up > --------------------------------- > > Key: WFLY-1547 > URL: https://issues.jboss.org/browse/WFLY-1547 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Alpha1 > Reporter: Shaun Appleton > Assignee: jaikiran pai > Fix For: 8.0.0.Beta1 > > Attachments: deployment_with_hack_no_hook.txt > > > JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories. > The following reproduces this - > i) ensure run.conf has the -Xrs set > ii) ensure deployments has a deployable .ear in it > iii) ./run standalone.sh and allow the deployments to deploy > iv) stop the EAP process ie kill <process_id> > v) observe content tmp/vfs > (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP) > This will eventually cause problems with lack of disk space. > Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems. > It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1547) deploy directories not cleaned up

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1547?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1547: ------------------------------ Comment: was deleted (was: dereed(a)redhat.com changed the Status of [bug 901210|https://bugzilla.redhat.com/show_bug.cgi?id=901210] from CLOSED to ASSIGNED) > deploy directories not cleaned up > --------------------------------- > > Key: WFLY-1547 > URL: https://issues.jboss.org/browse/WFLY-1547 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Alpha1 > Reporter: Shaun Appleton > Assignee: jaikiran pai > Fix For: 8.0.0.Beta1 > > Attachments: deployment_with_hack_no_hook.txt > > > JBoss EAP 6.0.0 (and 6.0.1.ER3) doesn't clean up it's tmp/vfs directories. > The following reproduces this - > i) ensure run.conf has the -Xrs set > ii) ensure deployments has a deployable .ear in it > iii) ./run standalone.sh and allow the deployments to deploy > iv) stop the EAP process ie kill <process_id> > v) observe content tmp/vfs > (The -Xrs parameter is used to "-Xrs" to prevent possible interference when JVM is running as a service and receives CTRL_LOGOFF_EVENT or SIGHUP) > This will eventually cause problems with lack of disk space. > Note if the -Xrs parameter content is removed but the tmp/vfs dirs stills exist. This could potentially cause inode problems. > It would be better if there were any additional code so the temp dirs are cleaned up on start up. That would resolve both the -Xrs problem and the excessive dir creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-417) Turn on Kie-Ci into an OSGI Bundle

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-417?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-417: ------------------------------------------------ Marek Winkler <mwinkler(a)redhat.com> changed the Status of [bug 1067867|https://bugzilla.redhat.com/show_bug.cgi?id=1067867] from ON_QA to VERIFIED > Turn on Kie-Ci into an OSGI Bundle > ---------------------------------- > > Key: DROOLS-417 > URL: https://issues.jboss.org/browse/DROOLS-417 > Project: Drools > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Charles Moulliard > Assignee: Mark Proctor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1950) JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1950?page=com.atlassian.jira.... ] Masafumi Miura updated JBMESSAGING-1950: ---------------------------------------- Steps to Reproduce: 1. Deploy example-servlet.war in the attachment. 2. Start EAP 5 default profile. Then, JBoss start-up hangs infrequently. Component/s: Messaging Core > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBMESSAGING-1950 > URL: https://issues.jboss.org/browse/JBMESSAGING-1950 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Affects Versions: 1.4.8.SP9 > Reporter: Masafumi Miura > Attachments: jstack.out, reproducer.tar.gz > > > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal when calling createTopicSession or createQueueSession in load-on-startup servlet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1950) JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1950?page=com.atlassian.jira.... ] Masafumi Miura updated JBMESSAGING-1950: ---------------------------------------- Comment: was deleted (was: Thread Dumps) > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBMESSAGING-1950 > URL: https://issues.jboss.org/browse/JBMESSAGING-1950 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.8.SP9 > Reporter: Masafumi Miura > Attachments: jstack.out, reproducer.tar.gz > > > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal when calling createTopicSession or createQueueSession in load-on-startup servlet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1950) JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1950?page=com.atlassian.jira.... ] Masafumi Miura updated JBMESSAGING-1950: ---------------------------------------- Attachment: reproducer.tar.gz > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBMESSAGING-1950 > URL: https://issues.jboss.org/browse/JBMESSAGING-1950 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.8.SP9 > Reporter: Masafumi Miura > Attachments: jstack.out, reproducer.tar.gz > > > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal when calling createTopicSession or createQueueSession in load-on-startup servlet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1950) JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1950?page=com.atlassian.jira.... ] Masafumi Miura updated JBMESSAGING-1950: ---------------------------------------- Attachment: jstack.out Thread Dumps > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBMESSAGING-1950 > URL: https://issues.jboss.org/browse/JBMESSAGING-1950 > Project: JBoss Messaging > Issue Type: Bug > Affects Versions: 1.4.8.SP9 > Reporter: Masafumi Miura > Attachments: jstack.out > > > JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal when calling createTopicSession or createQueueSession in load-on-startup servlet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1950) JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal

by Masafumi Miura (JIRA)

Masafumi Miura created JBMESSAGING-1950: ------------------------------------------- Summary: JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal Key: JBMESSAGING-1950 URL: https://issues.jboss.org/browse/JBMESSAGING-1950 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.8.SP9 Reporter: Masafumi Miura JBoss start-up hangs infrequently at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint#createConnectionDelegateInternal when calling createTopicSession or createQueueSession in load-on-startup servlet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014