May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4775) Cannot deploy EJB's if the remoting subsystem is not installed

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4775: ----------------------------------- Summary: Cannot deploy EJB's if the remoting subsystem is not installed Key: AS7-4775 URL: https://issues.jboss.org/browse/AS7-4775 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Stuart Douglas Assignee: jaikiran pai Priority: Critical Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-3772) Regularize expression handling in the interface resources

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-3772: ------------------------------------- Summary: Regularize expression handling in the interface resources Key: AS7-3772 URL: https://issues.jboss.org/browse/AS7-3772 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The interface resource code predates the evolution of the AttributeDefinition classes. Convert it over to that and make sure the xml parsers, operation step handlers and ParsedInterfaceCriteria follow the standard practices. Basically, 1) Use AD.parseAndSet() in the parsers. This will ensure parsing any criteria type that supports expressions will result in values of type EXPRESSION if appropriate. 2) Use AD.validateAndSet() in the MODEL stage of the OSH. This will ensure reading in input values from the CLI/console etc for any criteria type that supports expressions will result in values of type EXPRESSION if appropriate. 3) Pass the OperationContext into ParsedInterfaceCriteria and use AD.resolveModelAttribute() for resolution. This may not be entirely possible, as interface criteria as a bit unusual types of attributes. But the general intent here should be followed. -- 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

13 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1976) WAR file using WAR_BUNDLES_JSF_IMPL embedded in an EAR file fails deployment

by Oren Samuel (JIRA)

WAR file using WAR_BUNDLES_JSF_IMPL embedded in an EAR file fails deployment ---------------------------------------------------------------------------- Key: AS7-1976 URL: https://issues.jboss.org/browse/AS7-1976 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.2.Final, 7.0.1.Final Reporter: Oren Samuel Assignee: Remy Maucherat EAR file containing a WAR file that bundles Myfaces 1.2.7 fails deployment (trying to load JSF 2 libraries although WAR_BUNDLES_JSF_IMPL is set) 15:27:59,585 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."MyFacesTest.ear"."myfacesTest.war".INSTALL: org .jboss.msc.service.StartException in service jboss.deployment.subunit."MyFacesTest.ear"."myfacesTest.war".INSTALL: Failed to process phase INSTALL of subdeployment "myfacesTest.war " of deployment "MyFacesTest.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Caused by: java.lang.RuntimeException: Failed to load class com.sun.faces.config.ConfigureListener at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:141) at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:122) at org.jboss.as.ee.component.LazyValue.get(LazyValue.java:40) at org.jboss.as.ee.component.EEApplicationDescription.getClassConfiguration(EEApplicationDescription.java:183) at org.jboss.as.ee.component.ComponentDescription.createConfiguration(ComponentDescription.java:153) at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:70) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final] ... 5 more Caused by: java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener from [Module "deployment.MyFacesTest.ear.myfacesTest.war:main" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103) at java.lang.Class.forName0(Native Method) [:1.6.0_21] at java.lang.Class.forName(Class.java:247) [:1.6.0_21] at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:139) ... 11 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] (JBAS-9461) problem with jboss 5.1.0.GA log4j to separate log using appender filtering on war name

by William Diaz Pabón (JIRA)

[ https://issues.jboss.org/browse/JBAS-9461?page=com.atlassian.jira.plugin.... ] William Diaz Pabón commented on JBAS-9461: ------------------------------------------ lines in the log files are printed several times, for example if you have 3 log files configured, it prints each line 3 times > problem with jboss 5.1.0.GA log4j to separate log using appender filtering on war name > --------------------------------------------------------------------------------------- > > Key: JBAS-9461 > URL: https://issues.jboss.org/browse/JBAS-9461 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Environment: Jboss server 5.1.0.GA > Linux Red Hat > Library upgraded from 2.1.0GA to 2.1.1.GA : > jboss-logging-log4j.jar > jboss-logging-jdk.jar > jboss-logging-spi.jar > Reporter: Stéphane Raban > > When several applications are deployed on the default instance server on jboss 5.1.0.GA it is not possible to separate logs in different files with log4j > All applications will log in all different files. > The filter TCLMCFIlter doesn't work, it lets everything through (like the old TCLFilter). > Does anyone have a solution? > Relatives issues : > --------------------------- > https://issues.jboss.org/browse/ORG-1260 > Forum: > http://community.jboss.org/wiki/SeparatingApplicationLogs#comment-8603 -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3502) Deadlock trying to do concurrent insertions on the same KnowledgeSession

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3502: ------------------------------------ Summary: Deadlock trying to do concurrent insertions on the same KnowledgeSession Key: JBRULES-3502 URL: https://issues.jboss.org/browse/JBRULES-3502 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Concurrent insertions on the same KnowledgeSession ends up in a deadlock with 2 threads waiting each other as it follows: Thread-1@1667 daemon, prio=5, in group 'main', status: 'WAIT' at sun.misc.Unsafe.park(Unsafe.java:-1) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:172) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:888) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:847) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:269) Thread-0@1666 daemon, prio=5, in group 'main', status: 'WAIT' at sun.misc.Unsafe.park(Unsafe.java:-1) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178) at java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:807) at org.drools.common.UpgradableReentrantReadWriteLock.lowPriorityWriteLock(UpgradableReentrantReadWriteLock.java:105) at org.drools.common.UpgradableReentrantReadWriteLock.writeLock(UpgradableReentrantReadWriteLock.java:88) at org.drools.common.AbstractRuleBase.lock(AbstractRuleBase.java:472) at org.drools.reteoo.builder.PatternBuilder.attachObjectTypeNode(PatternBuilder.java:266) at org.drools.reteoo.ClassObjectTypeConf.<init>(ClassObjectTypeConf.java:99) at org.drools.common.ObjectTypeConfigurationRegistry.getObjectTypeConf(ObjectTypeConfigurationRegistry.java:71) at org.drools.reteoo.Rete.assertObject(Rete.java:107) at org.drools.reteoo.ReteooRuleBase.assertObject(ReteooRuleBase.java:286) at org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertAction.execute(ReteooWorkingMemory.java:435) at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:977) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:322) at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:298) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:888) at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:847) at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:269) -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4766) Implement aliases in the controller

by Kabir Khan (JIRA)

Kabir Khan created AS7-4766: ------------------------------- Summary: Implement aliases in the controller Key: AS7-4766 URL: https://issues.jboss.org/browse/AS7-4766 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.2.0.Alpha1 It should be possible to map a path address onto another one -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4767) Test transformation of web subsystem between 7.1.1 and 7.2.0

by Kabir Khan (JIRA)

Kabir Khan created AS7-4767: ------------------------------- Summary: Test transformation of web subsystem between 7.1.1 and 7.2.0 Key: AS7-4767 URL: https://issues.jboss.org/browse/AS7-4767 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.2.0.Alpha1 -- 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

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4765) CLONE - Add <cluster-password> attribute to stanalone-full-ha.xml

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/AS7-4765?page=com.atlassian.jira.plugin.s... ] Miroslav Novak moved JBPAPP-8981 to AS7-4765: --------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-4765 (was: JBPAPP-8981) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.1.Final (was: EAP 6.0.0 ER 7) Component/s: JMS (was: HornetQ) Security: (was: Public) Fix Version/s: 7.1.3.Final (EAP) (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Add <cluster-password> attribute to stanalone-full-ha.xml > ------------------------------------------------------------------ > > Key: AS7-4765 > URL: https://issues.jboss.org/browse/AS7-4765 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.1.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 7.1.3.Final (EAP) > > > When two servers are started in cluster (standalone-full-ha.xml profile) then HQ throw lots of exceptions to log. It's because default password for cluster connection is used and is necessary to change it. For simplicity we should add attribute cluster-password to messaging subsystem. > This should be added to messaging-subsystem: > {code} > <subsystem xmlns="urn:jboss:domain:messaging:1.2"> > <hornetq-server> > ... > <cluster-password>CHANGE ME!!</cluster-password> > ... > </hornetq-server> > </subsystem> > {code} > This also applies for domain.xml configuration (for full-ha profile) -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4258) Add option to :read-resource to only get the base attributes, but nothing at lover levels

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4258: ------------------------------- Summary: Add option to :read-resource to only get the base attributes, but nothing at lover levels Key: AS7-4258 URL: https://issues.jboss.org/browse/AS7-4258 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.1.Final Reporter: Heiko Rupp Assignee: Brian Stansberry I want to read the release-name, release-version, name attributes . Either I need to 3 times call :read-attribute or I can use :read-resource. But :read-resource returns a lot more [standalone@localhost:9999 /] :read-resource(recursive-depth=0) { "outcome" => "success", "result" => { "management-major-version" => 1, "management-minor-version" => 1, ... }, "deployment" => {"test-distributed.war" => undefined}, "extension" => { "org.jboss.as.ejb3" => undefined, ... }, "interface" => { "unsecure" => undefined, "public" => undefined, "management" => undefined }, "socket-binding-group" => {"standard-sockets" => undefined}, "subsystem" => { "jca" => undefined, which is all not needed and just needs to be transferred over the wire and parsed on clients It would be good to have an option "base-only" that restricts :read-resource to the resource itself and does not show children information -- 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

13 years, 11 months

4
4
0 / 0

[JBoss JIRA] (AS7-4677) Better name for directory=>configuration

by Kabir Khan (JIRA)

Kabir Khan created AS7-4677: ------------------------------- Summary: Better name for directory=>configuration Key: AS7-4677 URL: https://issues.jboss.org/browse/AS7-4677 Project: Application Server 7 Issue Type: Feature Request Components: Web Reporter: Kabir Khan Assignee: Remy Maucherat Related to AS7-3309 we need to implement the aliases for the web subsystem so ["subsystem" => "web", "virtual-server" => "default-host", "access-log" => "configuration", "directory" => "configuration"] becomes ["subsystem" => "web", "virtual-server" => "default-host", "configuration" => "access-log", "configuration" => "directory"] The old addresses will still be kept/aliased while the "real" model lives under the real address. The problem with the new address is that there are two levels that both have the key "configuration", so this needs changing to something better. Any ideas? -- 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

13 years, 11 months

1
4
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 May 2012