February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- 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

2 weeks, 6 days

2
3
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- 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

6 months, 1 week

3
10
0 / 0

[JBoss JIRA] (AS7-6044) NullPointerException when dependent jar is (re)deployed.

by Ste Gr (JIRA)

[ https://issues.jboss.org/browse/AS7-6044?page=com.atlassian.jira.plugin.s... ] Ste Gr commented on AS7-6044: ----------------------------- fyi 7.2.0.Final has also a "bug" of this kind. The EE subsystem populates some data during the STRUCTURE phase (EEModuleInitialProcessor > EEModuleDescription) which is used by the JPA subsystem during the FIRST_MODULE_USE phase (JPAInterceptorProcessor). But the STRUCTURE phase is only invoked for complete deploy operations, not for partial ones like it is happening when a dependency is being re-deployed. > NullPointerException when dependent jar is (re)deployed. > -------------------------------------------------------- > > Key: AS7-6044 > URL: https://issues.jboss.org/browse/AS7-6044 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Environment: OS: > CentOS 6.2 (64 bit) > Java: > java version "1.7.0_07" > Java(TM) SE Runtime Environment (build 1.7.0_07-b10) > Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) > Reporter: Corey Puffalt > > I have an ear containing an ejb-jar with a dependency on a jar file external to the ear but also deployed to JBoss (both files below are deployed to $JBOSS_HOME/standalone/deployments). > The structure looks like this: > {code} > kdmmailservice-ear.ear > |-- META-INF > | |-- application.xml > | `-- MANIFEST.MF > `-- kdmmailservice-service.jar > |-- com > | `-- kdm > | `-- mailservice > | `-- ... > `-- META-INF > |-- beans.xml > |-- ejb-jar.xml > `-- MANIFEST.MF > > kdmmailservice-templates.jar > |-- META-INF > | |-- MANIFEST.MF > `-- templates > `-- ... > {code} > The MANIFEST.MF in the ejb-jar above (kdmmailservice-service.jar) indicates its dependency on the kdmmailservice-templates.jar via a Dependencies entry: > {code} > Dependencies: deployment.kdmmailservice-templates.jar > {code} > As long as care is taken to deploy the jar file first, followed by the ear file everything is fine. But I need to be able to re-deploy the dependent jar (kdmmailservice-templates.jar) and when I do so, the ear file is undeployed and remains so due to a NullPointerException: > {code} > 08:50:50,640 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011908: Unregister module: Module "deployment.kdmmailservice-templates.jar:main" from Service Module Loader > 08:50:50,642 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011908: Unregister module: Module "deployment.kdmmailservice-ear.ear:main" from Service Module Loader > 08:50:50,643 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011908: Unregister module: Module "deployment.kdmmailservice-ear.ear.kdmmailservice-service.jar:main" from Service Module Loader > 08:50:50,699 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016009: Stopping weld service for deployment kdmmailservice-ear.ear > 08:50:50,713 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment kdmmailservice-templates.jar in 73ms > 08:50:50,715 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "kdmmailservice-templates.jar" > 08:50:50,718 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."kdmmailservice-ear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kdmmailservice-ear.ear".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "kdmmailservice-ear.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.2.Final.jar:7.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04] > Caused by: java.lang.NullPointerException > at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:43) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.2.Final.jar:7.1.2.Final] > ... 5 more > 08:50:50,726 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.kdmmailservice-templates.jar:main" from Service Module Loader > 08:50:50,911 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "kdmmailservice-templates.jar" with deployment "kdmmailservice-templates.jar" > 08:50:50,911 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."kdmmailservice-ear.ear".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kdmmailservice-ear.ear".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "kdmmailservice-ear.ear" > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-127) Java EE Connector Architecture (JSR-322)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-127?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-127: ------------------------------------- Released for testing and verification: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... > Java EE Connector Architecture (JSR-322) > ---------------------------------------- > > Key: JBEE-127 > URL: https://issues.jboss.org/browse/JBEE-127 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-connector-api > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Project repo exists: > https://github.com/jboss/jboss-connector-api_spec > Need updates to for v1.7. > {code} > <groupId>org.jboss.spec.javax.resource</groupId> > <artifactId>jboss-connector-api_1.7_spec</artifactId> > <version>1.0.0-SNAPSHOT</version> > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-990) TestConnection override with CRI and Subject

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-990?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-990: ---------------------------------- Labels: (was: eap6) Fix Version/s: 1.1.0.Beta5 > TestConnection override with CRI and Subject > -------------------------------------------- > > Key: JBJCA-990 > URL: https://issues.jboss.org/browse/JBJCA-990 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.13.Final > Environment: JBoss EAP 6.0.1 > JBoss AS 7.1.3 > Reporter: Anurag Debnath > Assignee: Jesper Pedersen > Fix For: 1.1.0.Beta5 > > > Create an override of the test connection method which operates on passed in ConnectionRequestInfo and Subject objects -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-990) TestConnection override with CRI and Subject

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-990?page=com.atlassian.jira.plugin.... ] Jesper Pedersen resolved JBJCA-990. ----------------------------------- Resolution: Done > TestConnection override with CRI and Subject > -------------------------------------------- > > Key: JBJCA-990 > URL: https://issues.jboss.org/browse/JBJCA-990 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.0.13.Final > Environment: JBoss EAP 6.0.1 > JBoss AS 7.1.3 > Reporter: Anurag Debnath > Assignee: Jesper Pedersen > Labels: eap6 > > Create an override of the test connection method which operates on passed in ConnectionRequestInfo and Subject objects -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-27) Add inject-api_1.0_spec

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-27?page=com.atlassian.jira.plugin.sy... ] Shelly McGowan commented on JBEE-27: ------------------------------------ Have relocation working: [WARNING] The artifact org.jboss.spec.javax.inject:jboss-inject-api_1.0_spec:jar:1.0.0.Alpha1-SNAPSHOT has been relocated to javax.inject:javax.inject:jar:1 > Add inject-api_1.0_spec > ----------------------- > > Key: JBEE-27 > URL: https://issues.jboss.org/browse/JBEE-27 > Project: JBoss JavaEE Spec APIs > Issue Type: Feature Request > Reporter: Shelly McGowan > > <dependency> > <groupId>org.jboss.spec.javax.inject</groupId> > <artifactId>jboss-inject-api_1.0_spec</artifactId> > <version>${version.org.jboss.spec.javaee}</version> > </dependency> -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6651) Fix marshalling of domain controller discovery options

by Farah Juma (JIRA)

Farah Juma created AS7-6651: ------------------------------- Summary: Fix marshalling of domain controller discovery options Key: AS7-6651 URL: https://issues.jboss.org/browse/AS7-6651 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Farah Juma Assignee: Farah Juma The marshalling code for domain controller discovery options currently assumes that any static-discovery elements will be provided before any discovery-option elements and writes the discovery options to the XML file in this order. This needs to be fixed since static-discovery and discovery-option elements can actually be provided in any order, any number of times. The discovery options need to be written to the XML file in the order they were provided in. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-4246) Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-4246?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated AS7-4246: -------------------------------- Fix Version/s: 8.0.0.Alpha1 > Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli > --------------------------------------------------------------------------------------------------- > > Key: AS7-4246 > URL: https://issues.jboss.org/browse/AS7-4246 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Ondřej Chaloupka > Assignee: Richard Achmatowicz > Labels: eap6_need_triage > Fix For: 8.0.0.Alpha1 > > > Setting attribute passivate-events-on-replicate via drm or cli does not take affect until operation :reload is used. > In case that the attribute ( <cluster-passivation-store name="infinispan" cache-container="ejb" passivate-events-on-replicate="false" />) is set directly in standalone*.xml configuration file the supposed functionality is working. > The test for this could be checked on: > https://github.com/ochaloup/jboss-as/blob/JBQA-5855-test-migration-passiv... -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6650) Don't have arquillian create a boot.log

by James Perkins (JIRA)

James Perkins created AS7-6650: ---------------------------------- Summary: Don't have arquillian create a boot.log Key: AS7-6650 URL: https://issues.jboss.org/browse/AS7-6650 Project: Application Server 7 Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins Arquillian is still creating a boot.log at start up. -- 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, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2013