March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-34) Clients hanging for 60s after closing connection to AS7

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-34: -------------------------------------- Summary: Clients hanging for 60s after closing connection to AS7 Key: REMJMX-34 URL: https://issues.jboss.org/browse/REMJMX-34 Project: Remoting JMX Issue Type: Bug Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 1.0.2.Final Non-daemon threads are keeping the process alive for one minute if the connection is closed - if the connection is not closed it is kept open for much longer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-4211) Make Resolver service publicly available

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4211: ----------------------------------- Summary: Make Resolver service publicly available Key: AS7-4211 URL: https://issues.jboss.org/browse/AS7-4211 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.2.Final Currently, the Resolver service is an API private to the OSGi layer. This should be publicly available to other AS services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-ManifestVersion

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened AS7-3822: --------------------------------- > Unable to deploy without Bundle-ManifestVersion > ----------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Fix For: 7.1.2.Final > > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-ManifestVersion

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-3822: -------------------------------- Fix Version/s: 7.1.2.Final Git Pull Request: https://github.com/jbossas/jboss-as/pull/1842 (was: https://github.com/jbossas/jboss-as/pull/1842) > Unable to deploy without Bundle-ManifestVersion > ----------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Fix For: 7.1.2.Final > > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-153) EJB timer clustering and failover support

by Galder Zamarreno (JIRA)

EJB timer clustering and failover support ----------------------------------------- Key: JBCLUSTER-153 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-153 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry Support for clustered EJB timer service providing failover -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
7
0 / 0

[JBoss JIRA] (AS7-4230) add-user tool prompt for password regardless --silent=true

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-4230: ------------------------------------- Summary: add-user tool prompt for password regardless --silent=true Key: AS7-4230 URL: https://issues.jboss.org/browse/AS7-4230 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security, Server Affects Versions: 7.1.1.Final Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink Priority: Minor If user and password are given as parameter and --silent=true is used it will be prompted for password -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-4229) JBoss AS 7.1 w/ an interface configured to bind to <any-address> causes tests to fail w/ the error: "host must not be null"

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/AS7-4229?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen moved ARQ-825 to AS7-4229: ---------------------------------------- Project: Application Server 7 (was: Arquillian) Key: AS7-4229 (was: ARQ-825) Component/s: Test Suite (was: JBoss AS Containers) Security: (was: Public) > JBoss AS 7.1 w/ an interface configured to bind to <any-address> causes tests to fail w/ the error: "host must not be null" > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-4229 > URL: https://issues.jboss.org/browse/AS7-4229 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Reporter: Brian Leathem > > Running a the JBoss AS kitchensink quickstart test again a JBoss AS 7.1 server with an interface configured to bind to <any-address> causes the test to fail with the error: "host must not be null". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-ManifestVersion

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reopened AS7-3822: --------------------------------- > Unable to deploy without Bundle-ManifestVersion > ----------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-ManifestVersion

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler resolved AS7-3822. --------------------------------- Fix Version/s: (was: 7.1.2.Final) Resolution: Cannot Reproduce Bug Cannot reproduce {code} [tdiesler@tdvaio basic]$ mvn -Dtest=LegacyBundleTestCase install Running org.jboss.as.test.integration.osgi.LegacyBundleTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.216 sec {code} http://mvnrepository.com/artifact/net.sf.jasperreports/jasperreports/3.7.5 is a jar and not a R3 bundle AFAICS. > Unable to deploy without Bundle-ManifestVersion > ----------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-ManifestVersion

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-3822: -------------------------------- Summary: Unable to deploy without Bundle-ManifestVersion (was: Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1) > Unable to deploy without Bundle-ManifestVersion > ----------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Fix For: 7.1.2.Final > > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2012