October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2426) Easily accessible static information describing the release

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2426: -------------------------------------- Summary: Easily accessible static information describing the release Key: WFLY-2426 URL: https://issues.jboss.org/browse/WFLY-2426 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Server Reporter: Brian Stansberry Tools that work with a WF installation need to identify what they are working with before they can launch or interact with the server. Specifically, they need to know the version. They likely need to know other information as well, such as the name of the software; e.g. whether it is WildFly itself or some other project based on WildFly. This information should be provided in standard format in a text file in a standard location in the distribution (probably in bin). The text file should be generated as part of the build. The solution to this issue should consider the requirements of other "identities" that may be based on WildFly. See [1] for the definition of an identity. The solution to this issue should consider the needs of products based on WildFly and other non-product identities. For example, can the existing product.conf contain the necessary information for a product, with some differently named but largely equivalent file being used in a non-product distribution? The solution to this issue should consider the implications for the patching tool. [1] https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganiz... for -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1982) NPE in ModelControllerLock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1982?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1982: ----------------------------------------------- Emanuel Muckenhuber <emuckenh(a)redhat.com> changed the Status of [bug 1024862|https://bugzilla.redhat.com/show_bug.cgi?id=1024862] from NEW to POST > NPE in ModelControllerLock > -------------------------- > > Key: WFLY-1982 > URL: https://issues.jboss.org/browse/WFLY-1982 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > Just noticed this in the host-controller.log while looking into a non-progressing RespawnTestCase: > 22:23:50,552 ERROR [org.jboss.as.controller.management-operation] (proxy-threads - 1) JBAS014612: Operation ("register-server") failed - address: ([]): java.lang.NullPointerException > at org.jboss.as.controller.ModelControllerLock$Sync.tryAcquire(ModelControllerLock.java:75) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220) [rt.jar:1.7.0_15] > at org.jboss.as.controller.ModelControllerLock.lockInterruptibly(ModelControllerLock.java:48) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.acquireLock(ModelControllerImpl.java:582) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.OperationContextImpl.takeWriteLock(OperationContextImpl.java:403) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.OperationContextImpl.acquireControllerLock(OperationContextImpl.java:700) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.host.controller.mgmt.ServerToHostProtocolHandler$ServerReconnectRequestHandler$1$1.execute(ServerToHostProtocolHandler.java:268) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:610) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:488) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:257) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:292) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.host.controller.DomainModelControllerService.access$600(DomainModelControllerService.java:148) > at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:899) > at org.jboss.as.host.controller.mgmt.ServerToHostProtocolHandler$ServerReconnectRequestHandler$1.execute(ServerToHostProtocolHandler.java:282) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [wildfly-protocol-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [wildfly-protocol-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2410) composite operation containing a host op does not get rolled out to all hosts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2410?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2410: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1015098|https://bugzilla.redhat.com/show_bug.cgi?id=1015098] from ASSIGNED to POST > composite operation containing a host op does not get rolled out to all hosts > ----------------------------------------------------------------------------- > > Key: WFLY-2410 > URL: https://issues.jboss.org/browse/WFLY-2410 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > If a composite operation contains an operation targeting the domain as well as a single host, it will only get rolled out to the host specified rather than to the complete domain. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-368) It is not possible to set a timeout method for a SingletonBean with the ejb-jar.xml descriptor

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/JBMETA-368?page=com.atlassian.jira.plugin... ] Wolf-Dieter Fink updated JBMETA-368: ------------------------------------ Forum Reference: https://community.jboss.org/thread/234051 > It is not possible to set a timeout method for a SingletonBean with the ejb-jar.xml descriptor > ---------------------------------------------------------------------------------------------- > > Key: JBMETA-368 > URL: https://issues.jboss.org/browse/JBMETA-368 > Project: JBoss Metadata > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ejb > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > > Regarding to the EJB3.1 specification chapter 4.3.8 it is possible to have a timeout method for a SingletonBean. This can be done by annotation but not with the deployment descriptor. > Also the IllegalStateException contain the wrong message -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-368) It is not possible to set a timeout method for a SingletonBean with the ejb-jar.xml descriptor

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created JBMETA-368: --------------------------------------- Summary: It is not possible to set a timeout method for a SingletonBean with the ejb-jar.xml descriptor Key: JBMETA-368 URL: https://issues.jboss.org/browse/JBMETA-368 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ejb Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink Regarding to the EJB3.1 specification chapter 4.3.8 it is possible to have a timeout method for a SingletonBean. This can be done by annotation but not with the deployment descriptor. Also the IllegalStateException contain the wrong message -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2425) Use forked version of slf4j to fix concurrency issue with static binding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2425?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2425: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1011821|https://bugzilla.redhat.com/show_bug.cgi?id=1011821] from ASSIGNED to POST > Use forked version of slf4j to fix concurrency issue with static binding > ------------------------------------------------------------------------ > > Key: WFLY-2425 > URL: https://issues.jboss.org/browse/WFLY-2425 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The slf4j-api static binding is not thread safe. A fork of slf4j-api was needed for EAP so we might as well patch WildFly too. The slf4j bugzilla is http://bugzilla.slf4j.org/show_bug.cgi?id=176. The patch used in the fork is attached to the bz. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2425) Use forked version of slf4j to fix concurrency issue with static binding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2425?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2425: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1011821 > Use forked version of slf4j to fix concurrency issue with static binding > ------------------------------------------------------------------------ > > Key: WFLY-2425 > URL: https://issues.jboss.org/browse/WFLY-2425 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > The slf4j-api static binding is not thread safe. A fork of slf4j-api was needed for EAP so we might as well patch WildFly too. The slf4j bugzilla is http://bugzilla.slf4j.org/show_bug.cgi?id=176. The patch used in the fork is attached to the bz. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2425) Use forked version of slf4j to fix concurrency issue with static binding

by James Perkins (JIRA)

James Perkins created WFLY-2425: ----------------------------------- Summary: Use forked version of slf4j to fix concurrency issue with static binding Key: WFLY-2425 URL: https://issues.jboss.org/browse/WFLY-2425 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor The slf4j-api static binding is not thread safe. A fork of slf4j-api was needed for EAP so we might as well patch WildFly too. The slf4j bugzilla is http://bugzilla.slf4j.org/show_bug.cgi?id=176. The patch used in the fork is attached to the bz. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1726) Bundler: send message batch of 1 as single message

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1726?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1726. ---------------------------- Resolution: Done > Bundler: send message batch of 1 as single message > -------------------------------------------------- > > Key: JGRP-1726 > URL: https://issues.jboss.org/browse/JGRP-1726 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > When the TransferQueueBundler ("new" / default) sends bundled messages, if there is only a single message in the list, the message is still sent as a *batch* (of 1). > Currently, parsing of single messages is done in a separate thread (JGRP-1716) whereas parsing of message batches is done in the thread which received the messages from the socket. > If we therefore send a batch of 1 as a single message, we might get better perf (to be verified). -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2368) env-entry is not injected with @Resource annotation into CDI beans and JAX-RS resources

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2368?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-2368: -------------------------------------- I think this should be resolved, can you re-test against upstream? > env-entry is not injected with @Resource annotation into CDI beans and JAX-RS resources > --------------------------------------------------------------------------------------- > > Key: WFLY-2368 > URL: https://issues.jboss.org/browse/WFLY-2368 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld, REST > Affects Versions: 8.0.0.Beta1 > Reporter: Dmytro Zemnytskiy > Assignee: Stuart Douglas > > I built simple web application to narrow down problem, consisting of war packaged in ear. It attempts to inject env-entry declared in web.xml using @Resource annotation into servlet, jax-rs resource and cdi managed bean. > For now only servlet is injected with env-entry properly. JAX-RS resource requires @ManagedBean annotation in order to work, but still does not work if it is listed explicitly in its Application, rather than autoscanned. CDI bean does not work yet. Same app without modifications work properly in Jboss AS 7.1 > Below is example of CDI bean : > @Named > public class EnvEntryProducer { > @Resource(name="demo") String env; > > @PostConstruct void logMe() { > System.out.print("Env: " + env); > } > > @Produces @Named("enventry") String getEnv() { > return env; > } > } > PostConstruct is not called yet as well -- 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

12 years, 6 months

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 October 2013