July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1301) Update OSGi to be compatible with JBoss Modules 1.1 series

by David Lloyd (JIRA)

Update OSGi to be compatible with JBoss Modules 1.1 series ---------------------------------------------------------- Key: AS7-1301 URL: https://issues.jboss.org/browse/AS7-1301 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: David Lloyd Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 JBoss Modules 1.1 has two significant changes. First, jaxpmodule is eliminated. Second, the system module is no more - instead there's a dependency type for the system class loader. I currently have an updated AS in my http://github.com/dmlloyd/jboss-as/tree/upgrades branch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
19
0 / 0

[JBoss JIRA] Created: (AS7-1376) Implement EE.10 Application Clients

by Carlo de Wolf (JIRA)

Implement EE.10 Application Clients ----------------------------------- Key: AS7-1376 URL: https://issues.jboss.org/browse/AS7-1376 Project: Application Server 7 Issue Type: Task Components: EE Reporter: Carlo de Wolf Assignee: David Lloyd Priority: Critical Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBLOGGING-52) Use of system property for proxy generation setting is too inflexible

by Dan Allen (JIRA)

Use of system property for proxy generation setting is too inflexible --------------------------------------------------------------------- Key: JBLOGGING-52 URL: https://issues.jboss.org/browse/JBLOGGING-52 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-spi Affects Versions: 3.0.0.Beta4-jboss-logging Reporter: Dan Allen Assignee: David Lloyd Fix For: 3.0.0.Beta5-jboss-logging JBoss Logging uses a system property to configure whether or not proxies are generated for type-safe loggers. This approach is very inflexible. The main issue is that the value of this system property is being cached too aggressively. In CDI extensions, we are forced to use a static code block to set the property so it is assigned early enough that JBoss Logging caches the correct value. However, with multiple extensions loading in a non-deterministic order, we end up having to put this static block in multiple places. [1] We need a better way to apply this setting. Perhaps a static method on a configuration API to assign the value before any logging takes place. [1] https://github.com/seam/solder/blob/master/impl/src/main/java/org/jboss/s... https://github.com/seam/servlet/blob/master/impl/src/main/java/org/jboss/... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

5
12
0 / 0

[JBoss JIRA] Created: (JBAS-9316) Indentation of multiline text content in standalone.xml keeps increasing on rewrites

by David Bosschaert (JIRA)

Indentation of multiline text content in standalone.xml keeps increasing on rewrites ------------------------------------------------------------------------------------ Key: JBAS-9316 URL: https://issues.jboss.org/browse/JBAS-9316 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: XML Services/Frameworks Affects Versions: 7.0.0.Beta3 Reporter: David Bosschaert Assignee: Jason Greene Priority: Minor The standalone.xml file contains some XML tags that contain multi-line XML text, e.g.: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} The problem is that every automatic rewrite of the standalone.xml (e.g. when you deploy a new thing) the indentation increases from the 2nd line of the text, so after the first rewrite it looks like this: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} after a few deploys it ends up looking like this: {code}<property name="org.jboss.osgi.system.modules"> org.apache.log4j, org.jboss.as.osgi, javax.inject.api, ...{code} Pretty ugly :( Would be nice if the indentation could be left untouched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

6
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3072) CCE due to non-boolean constraint expression

by Wolfgang Laun (JIRA)

CCE due to non-boolean constraint expression -------------------------------------------- Key: JBRULES-3072 URL: https://issues.jboss.org/browse/JBRULES-3072 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.CR1 Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0 (Possibly related to JBRULES-3011) class Person { String name; } when $p1: Person( name + name ) This is compiled, and execution fails with: Caused by: org.drools.RuntimeDroolsException: Exception executing predicate name + name at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:298) at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:130) at org.drools.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:59) at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:193) at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:143) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:332) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:293) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:905) at org.drools.base.DefaultKnowledgeHelper.insert(DefaultKnowledgeHelper.java:119) at org.drools.base.DefaultKnowledgeHelper.insert(DefaultKnowledgeHelper.java:113) at freeform.Rule_ins_0.defaultConsequence(Rule_ins_0.java:9) at freeform.Rule_ins_0DefaultConsequenceInvoker.evaluate(Rule_ins_0DefaultConsequenceInvoker.java:23) at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:905) ... 7 more Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean at org.drools.base.mvel.MVELPredicateExpression.evaluate(MVELPredicateExpression.java:101) at org.drools.rule.PredicateConstraint.isAllowed(PredicateConstraint.java:291) ... 19 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-9327) Ensure "add" operation handlers are storing default values

by Brian Stansberry (JIRA)

Ensure "add" operation handlers are storing default values ---------------------------------------------------------- Key: JBAS-9327 URL: https://issues.jboss.org/browse/JBAS-9327 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 In discussion on the dev list we decided to store default values in the model even if not present in XML or in "add" operation params coming from CLI/console. This task is to review the handlers for compliance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-961) AS 7 standalone instance doesn't shutdown

by Marek Novotny (JIRA)

AS 7 standalone instance doesn't shutdown ----------------------------------------- Key: AS7-961 URL: https://issues.jboss.org/browse/AS7-961 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Environment: Ubuntu 11.04, java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Reporter: Marek Novotny After failed deployment server standalone instance doesn't shutdown. I have pushed CTRL+C and it tried to shutdown: {code} 21:11:24,194 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120) started 21:11:25,026 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."jboss-seam-jpa.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-seam-jpa.war".PARSE: Failed to process phase PARSE of deployment "jboss-seam-jpa.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse "/content/jboss-seam-jpa.war/WEB-INF/jboss-web.xml" at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:66) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,3] Message: Unexpected element 'class-loading' encountered at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109) at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:182) at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64) ... 5 more ^C21:12:05,801 INFO [org.jboss.as.logging] Restored bootstrap log handlers 21:12:05,818 INFO [org.jboss.as.connector.subsystems.datasources] Removed JDBC Data-source [java:/H2DS] 21:12:05,833 INFO [org.jboss.as.server.deployment] Stopped deployment jboss-seam-jpa.war in 52ms 21:12:05,832 INFO [com.arjuna.ats.jbossatx] ARJUNA-32018 Destroying TransactionManagerService 21:12:05,834 INFO [com.arjuna.ats.jbossatx] ARJUNA-32014 Stopping transaction recovery manager 21:12:05,845 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped {code} The above was last line of shutdown and it didn't return to terminal prompt. I have tried also {{./jboss-admin.sh --connect command=:shutdown}} but it logs only: {code} Connected to localhost:9999 Communication error: Connection refused Closed connection to localhost:9999 {code} I have to kill manually AS 7 process by kill -9 <procid> I also tried to start new standalone instance and tried to stop by {{./jboss-admin.sh --connect command=:shutdown}} after failed deployment. Both terminals hang up and didn't shutdown. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-794) Booting slave host controller only makes a single attempt to contact master

by Brian Stansberry (JIRA)

Booting slave host controller only makes a single attempt to contact master --------------------------------------------------------------------------- Key: AS7-794 URL: https://issues.jboss.org/browse/AS7-794 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.CR1 RemoteDomainConnectionService tries once to connect; if it fails it gives up immediately and the node switches into slave mode. This needs to be more robust, particularly to handle cases where the master and the slave are starting concurrently (i.e. what should ideally be happening in integration tests). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1094) Get rid of the ping hack used my DomainModelControllerService to detect crashed slaves

by Kabir Khan (JIRA)

Get rid of the ping hack used my DomainModelControllerService to detect crashed slaves -------------------------------------------------------------------------------------- Key: AS7-1094 URL: https://issues.jboss.org/browse/AS7-1094 Project: Application Server 7 Issue Type: Task Components: Domain Management, Remoting Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.1.0.Alpha1 Remove the hacks in DomainModelControllerService to detect if a slave is still registered -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-9317) Detect crashed DC slave in protocol to avoid errors when restarting crashed slave

by Kabir Khan (JIRA)

Detect crashed DC slave in protocol to avoid errors when restarting crashed slave --------------------------------------------------------------------------------- Key: JBAS-9317 URL: https://issues.jboss.org/browse/JBAS-9317 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.0.0.Beta4 This could be possible with what we have but deferring until we have JBAS-9101 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011