January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2661) Build Number needs to be inserted into the build process so people can know which version they have

by Jim Tyrrell (Created) (JIRA)

Build Number needs to be inserted into the build process so people can know which version they have --------------------------------------------------------------------------------------------------- Key: AS7-2661 URL: https://issues.jboss.org/browse/AS7-2661 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Jim Tyrrell Assignee: Paul Gier I found a few issues, and developers asked for what version I am using. In the response it was discovered there is no way to grab the "version" of what was built. It would be great to inject a build time, and the version of the current git repo in some file somewhere. Might it be a good idea to grab and label all of the projects that make up the release. Support might want this information also. -- 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

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-3485) Transient deadlocking in StatefulFailoverTestCase and SingletonServiceTestCase

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-3485: --------------------------------- Summary: Transient deadlocking in StatefulFailoverTestCase and SingletonServiceTestCase Key: AS7-3485 URL: https://issues.jboss.org/browse/AS7-3485 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.0.Final Attachments: org.jboss.as.test.clustering.unmanaged.ejb3.stateful.StatefulFailoverTestCase-output.txt, org.jboss.as.test.clustering.unmanaged.singleton.SingletonTestCase-output.txt Seems to be a race condition when we try to perform cache operations within a view change event. Logs attached. -- 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

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] (JBRULES-3362) Declared types formatting error not detected at compile time

by James Walker (JIRA)

James Walker created JBRULES-3362: ------------------------------------- Summary: Declared types formatting error not detected at compile time Key: JBRULES-3362 URL: https://issues.jboss.org/browse/JBRULES-3362 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core, drools-eclipse Affects Versions: 5.4.0.Beta1 Reporter: James Walker Assignee: Mark Proctor If you declare a type like this: {noformat} declare Wrapper Text: String #Field name starts with a capital letter - not a java bean! metrics : Metrics end {noformat} It doesn't notice it at compile time or in the eclipse plugin, but errors at run-time. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3361) Salience format error (Salience - 150) so

by James Walker (JIRA)

James Walker created JBRULES-3361: ------------------------------------- Summary: Salience format error (Salience - 150) so Key: JBRULES-3361 URL: https://issues.jboss.org/browse/JBRULES-3361 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Walker Assignee: Mark Proctor -- 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

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-3484) Update OSGi Core Framework to 1.1.x

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3484: ----------------------------------- Summary: Update OSGi Core Framework to 1.1.x Key: AS7-3484 URL: https://issues.jboss.org/browse/AS7-3484 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Final -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3194) Improper handling of load metric add/remove in mod_cluster subsystem

by Brian Stansberry (Created) (JIRA)

Improper handling of load metric add/remove in mod_cluster subsystem -------------------------------------------------------------------- Key: AS7-3194 URL: https://issues.jboss.org/browse/AS7-3194 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Web Affects Versions: 7.1.0.CR1b Reporter: Brian Stansberry Assignee: Jean-Frederic Clere Fix For: 7.1.0.Final The ModClusterAddMetric and ModClusterAddCustomMetric handlers have two problems: 1) They only run if (context.getType() == OperationContext.Type.SERVER) This means a client updating the subsystem config on a domain controller will not be able to have the change reflected in the domain wide model (and it won't be persisted to domain.xml) 2) If they are run on the server, they don't modify the runtime or call context.reloadRequired(). So the runtime services are out of sync with the configuration but the server state doesn't reflect that. -- 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

12 years, 8 months

6
6
0 / 0

[JBoss JIRA] Created: (AS7-779) AS should allow deploying a non-jar deployment descriptor

by Tobias Crawley (JIRA)

AS should allow deploying a non-jar deployment descriptor --------------------------------------------------------- Key: AS7-779 URL: https://issues.jboss.org/browse/AS7-779 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.0.Beta3 Reporter: Tobias Crawley Assignee: Jason Greene With TorqueBox, we allow deploying a text based deployment descriptor that points to either an archive of the app, or the app directory tree. To support this, AS7 needs to support deploying non-jar resources. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-3245) Convert xts subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert xts subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ------------------------------------------------------------------------------ Key: AS7-3245 URL: https://issues.jboss.org/browse/AS7-3245 Project: Application Server 7 Issue Type: Task Components: Transactions Reporter: Brian Stansberry Assignee: Jason Greene Fix For: 7.1.0.Final The XtsAsLogger and XtsAsMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-3482) Clustering code expects a public default constructor

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-3482: ----------------------------------- Summary: Clustering code expects a public default constructor Key: AS7-3482 URL: https://issues.jboss.org/browse/AS7-3482 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Stuart Douglas Assignee: Paul Ferraro Fix For: 7.1.0.Final org.jboss.as.ejb3.component.stateful.StatefulSessionBeanObjectResolver.SerializableAdapter#readObject does a targetClass.newInstance(), which will fail if there is not a public default constructor. -- 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

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-3483) unable to deploy icescrum_R4_3.1

by Philippe FICHET (JIRA)

Philippe FICHET created AS7-3483: ------------------------------------ Summary: unable to deploy icescrum_R4_3.1 Key: AS7-3483 URL: https://issues.jboss.org/browse/AS7-3483 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.CR1b Environment: Ubuntu 11.10 64 bits 12Go DDR3 java version "1.6.0_23" OpenJDK Runtime Environment (IcedTea6 1.11pre) (6b23~pre11-0ubuntu1.11.10.1) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Reporter: Philippe FICHET Assignee: Jason Greene I use jboss in standalone mode (unzip only, not modified) I deploy icescrum_R4_3.1.war, but can't access by url "http://localhost:8080/icescrum_R4_3.1/" (http code 404) deply command : [standalone@localhost:9999 /] deploy ../../../tools/icescrum_R4_3.1.war Logs : 21:58:16,778 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "icescrum_R4_3.1.war" 21:58:20,767 INFO [org.jboss.web] (MSC service thread 1-8) registering web context: /icescrum_R4_3.1 21:58:20,784 INFO [org.jboss.as.server] (management-handler-threads - 3) JBAS018559: Deployed "icescrum_R4_3.1.war" -- 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

12 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012