March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1600) Deadlock in Infinispan with TCP and use_send_queues=true

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1600?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1600: -------------------------------- Alan, this could have been caused by JGRP-1549. You could try JGroups 3.3.0.Beta, to see if it fixes the problem... > Deadlock in Infinispan with TCP and use_send_queues=true > -------------------------------------------------------- > > Key: JGRP-1600 > URL: https://issues.jboss.org/browse/JGRP-1600 > Project: JGroups > Issue Type: Bug > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.3 > > > https://issues.jboss.org/browse/ISPN-2836 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1599) TP: JGroups internal thread pool

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1599?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1599. ---------------------------- Resolution: Done > TP: JGroups internal thread pool > -------------------------------- > > Key: JGRP-1599 > URL: https://issues.jboss.org/browse/JGRP-1599 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.3 > > > Add an internal thread pool which is used only for JGroups-internal messages (tagges as Flag.INTERNAL). This prevents internal messages (such as credits, heartbeats etc) to be dropped when the OOB thread pool is maxed out. > If enabled, internal messages will get processed by the internal thread pool, otherwise the OOB pool will be used. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6656) Provide stub extensions for removed subsystem configs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6656?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6656: --------------------------------------- This should be fairly straightforward: 1) The Extension impls: a) on a standalone server, throw an UnsupportedOperationException b) on a domain server, do a no-op. Allows the extension:add to be propagated to the server, so no special handling on the HC is needed to stop that. But extension will do nothing. This works because of 2) below. c) on an HC, register different handlers as per 2) below 2) Changes to the subsystem management operation handling a) the "describe" handler throws an UnsupportedOperationException. So if the user configures the HC to use a profile with this subsystem on an AS 8 server, it will fail on the HC b) Other handlers are changed to do nothing in Stage.RUNTIME. ModelOnlyWriteAttributeHandler can be used liberally. A similar class for :add and :remove can be easily written as well. That will handle the great majority of stuff. > Provide stub extensions for removed subsystem configs > ----------------------------------------------------- > > Key: AS7-6656 > URL: https://issues.jboss.org/browse/AS7-6656 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Thomas Diesler > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Some config parser/transform functionality is needed if we don't want to break backward compatibility with AS7x configs. > http://lists.jboss.org/pipermail/jboss-as7-dev/2013-February/007721.html -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-110) Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-110?page=com.atlassian.jira.plugin.s... ] Shelly McGowan edited comment on JBEE-110 at 3/1/13 10:30 AM: -------------------------------------------------------------- https://github.com/jboss/jboss-inject-api_spec was created Dependency Injection APIs. This project provides a pom relocating to javax.inject:javax.inject was (Author: shelly.mcgowan): https://github.com/jboss/jboss-inject-api_spec was created for Dependency Injection APIs > Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts > --------------------------------------------------------------------- > > Key: JBEE-110 > URL: https://issues.jboss.org/browse/JBEE-110 > Project: JBoss JavaEE Spec APIs > Issue Type: Feature Request > Affects Versions: JavaEE 6 Spec APIs 3.0.0.Final > Reporter: Pete Muir > Assignee: Shelly McGowan > Priority: Critical > > For example, we use org.hibernate and javax.enterprise group ids for JPA and CDI. It would be nice if we created stubs with relocations for these under org.jboss.spec so that the new developer can just follow the naming conventions with no exceptions. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6656) Provide stub extensions for removed subsystem configs

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6656?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-6656: ----------------------------------- Just a FYI in case something needs to be implemented at per subsystem level to support this - AS8 has recently removed the JSR-88 subsystem. > Provide stub extensions for removed subsystem configs > ----------------------------------------------------- > > Key: AS7-6656 > URL: https://issues.jboss.org/browse/AS7-6656 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Thomas Diesler > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Some config parser/transform functionality is needed if we don't want to break backward compatibility with AS7x configs. > http://lists.jboss.org/pipermail/jboss-as7-dev/2013-February/007721.html -- 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

13 years, 2 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 resolved JBEE-27. -------------------------------- Assignee: Shelly McGowan Resolution: Done https://github.com/jboss/jboss-inject-api_spec was created with relocation to javax.inject:javax.inject > 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 > Assignee: 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-110) Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-110?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-110: ------------------------------------- https://github.com/jboss/jboss-inject-api_spec was created for Dependency Injection APIs > Add relocations from org.jboss.spec.* to non org.jboss.spec artifacts > --------------------------------------------------------------------- > > Key: JBEE-110 > URL: https://issues.jboss.org/browse/JBEE-110 > Project: JBoss JavaEE Spec APIs > Issue Type: Feature Request > Affects Versions: JavaEE 6 Spec APIs 3.0.0.Final > Reporter: Pete Muir > Assignee: Shelly McGowan > Priority: Critical > > For example, we use org.hibernate and javax.enterprise group ids for JPA and CDI. It would be nice if we created stubs with relocations for these under org.jboss.spec so that the new developer can just follow the naming conventions with no exceptions. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6658) Include Infinispan CDI as a JBoss module

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-6658?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-6658: ------------------------------------- Thanks. We are on the same page then. > Include Infinispan CDI as a JBoss module > ---------------------------------------- > > Key: AS7-6658 > URL: https://issues.jboss.org/browse/AS7-6658 > Project: Application Server 7 > Issue Type: Enhancement > Components: Clustering > Reporter: Avelino Martins > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > CDI has become an invaluable technology on any JavaEE project. I find hard to justify having to include infinispan-cdi as a compile dependency on every project that uses ISPN. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6658) Include Infinispan CDI as a JBoss module

by Avelino Martins (JIRA)

[ https://issues.jboss.org/browse/AS7-6658?page=com.atlassian.jira.plugin.s... ] Avelino Martins commented on AS7-6658: -------------------------------------- Hi Radoslav, while i agree that is good practice to leave cache configuration to the container and inject it using @Resource as in your example, it doesn't hurts being able to use the related functionality provided by the infinispan-cdi module when needed. But indeed the main reason are the JCache annotations. Supposedly, from what i have been reading, JCache is to miss JavaEE 7, and so it makes even more sense to have the module included even if it's only on the new version 8 of JBoss AS. > Include Infinispan CDI as a JBoss module > ---------------------------------------- > > Key: AS7-6658 > URL: https://issues.jboss.org/browse/AS7-6658 > Project: Application Server 7 > Issue Type: Enhancement > Components: Clustering > Reporter: Avelino Martins > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > CDI has become an invaluable technology on any JavaEE project. I find hard to justify having to include infinispan-cdi as a compile dependency on every project that uses ISPN. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6659) Timeout exceptions on OSGified bundle start sometimes occur even if activation works

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/AS7-6659?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori updated AS7-6659: ----------------------------------- Attachment: stack_trace_start_timeout.txt > Timeout exceptions on OSGified bundle start sometimes occur even if activation works > ------------------------------------------------------------------------------------ > > Key: AS7-6659 > URL: https://issues.jboss.org/browse/AS7-6659 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.2.0.Alpha1 > Environment: Windows 7, 64-bit > Reporter: Jarkko Rantavuori > Assignee: Thomas Diesler > Attachments: stack_trace_start_timeout.txt > > > Sometimes activating a complex OSGi-war bundle throws timeout exception, even though activation does work and war answers to requests just fine. It seems exception + message is unjustified and no roll back actually occurs. Stack trace attached. -- 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

13 years, 2 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 March 2013