May 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Deleted: (JBREM-1224) Release 2.5.2.SP3

by Ron Sigal (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-1224?page=com.atlassian.jira.plu... ] Ron Sigal deleted JBREM-1224: ----------------------------- > Release 2.5.2.SP3 > ----------------- > > Key: JBREM-1224 > URL: https://jira.jboss.org/jira/browse/JBREM-1224 > Project: JBoss Remoting > Issue Type: Release > Security Level: Public(Everyone can see) > Reporter: Ron Sigal > Assignee: Ron Sigal > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1224) Release 2.5.2.SP3

by Ron Sigal (JIRA)

Release 2.5.2.SP3 ----------------- Key: JBREM-1224 URL: https://jira.jboss.org/jira/browse/JBREM-1224 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2.SP3 (Flounder) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1221) Update jars to match EAP 5.1.0

by Ron Sigal (JIRA)

Update jars to match EAP 5.1.0 ------------------------------ Key: JBREM-1221 URL: https://jira.jboss.org/jira/browse/JBREM-1221 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2.SP3 (Flounder) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBBOOT-133) Update ${version} to ${project.version}

by Andrew Lee Rubinger (JIRA)

Update ${version} to ${project.version} --------------------------------------- Key: JBBOOT-133 URL: https://jira.jboss.org/jira/browse/JBBOOT-133 Project: JBoss Bootstrap Issue Type: Bug Components: api, api-as, api-embedded, api-mc, build, impl-as, impl-base, impl-embedded, impl-mc Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger As reported by Bob: "In some of your POMs (such as jboss-bootstrap-impl-base-2.1.0-alpha-5.pom), you reference property ${version}, which 99% of the time is equiv to ${project.version}, but on the off-chance someone passes -Dversion=1.0.0.Beta19 on the commandline while invoking some plugin, maven quite happily applies it to other POMs it walks sometimes. " Update to "project.version" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7831) Kill the JMX detatched invoker service

by David Lloyd (JIRA)

Kill the JMX detatched invoker service -------------------------------------- Key: JBAS-7831 URL: https://jira.jboss.org/jira/browse/JBAS-7831 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: JBossAS-6.0.0.M3 location: server/src/resources/jmx-invoker-adaptor/META-INF/jboss-service.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2502) Add ability to set http read and connection timeout in millis in RuleAgent/KnowledgeAgent

by Tihomir Surdilovic (JIRA)

Add ability to set http read and connection timeout in millis in RuleAgent/KnowledgeAgent ----------------------------------------------------------------------------------------- Key: JBRULES-2502 URL: https://jira.jboss.org/jira/browse/JBRULES-2502 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.1.0.M1, 4.0.7 Reporter: Tihomir Surdilovic Assignee: Mark Proctor Currently users have to set sun.net.client.defaultConnectTimeout and sun.net.client.defaultReadTimeout system properties to a reasonable value to account for network/connection issues when rule resources are being checked for updates by RuleAgent/KnowledgeAgent. This is requesting ability to set both the read and connection timeouts through property/configuration options in RuleAgent and KnowledgeAgent to be able to specify user-defined settings. The code should also log any information about the tried connection (how long it took, if it timed out, or was successful) for debugging purposes by users. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-249) CacheManager destroys caches when it stops

by Brian Stansberry (JIRA)

CacheManager destroys caches when it stops ------------------------------------------ Key: JBCLUSTER-249 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-249 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: HA-Server-Cache-JBC Affects Versions: HA-Server-Cache-JBC 2.1.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Server-Cache-JBC 2.1.1.GA CacheManager.stop() destroys all running caches. This is incorrect; since it didn't create them in start(). It should just call releaseCache for all eager-start caches to reduce the ref count. Then make the releaseCache method usable after stop() so if anyone has a ref to the CacheManager they can still release the cache. This is essentially a workaround-type solution for JBAS-7228 and JBAS-7229. The correct solution for those is to have services using the CacheManager depend on it, so they stop first. But the MC may not be aware of everything using CacheManager (e.g. a Hibernate SessionFactory created by a ServletContextListener) so it can't always enforce dependencies. And, the ^^^ behavior of stop only undoing what start did is correct anyway. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-241) Clean up Fqn creation

by Brian Stansberry (JIRA)

Clean up Fqn creation --------------------- Key: JBCLUSTER-241 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-241 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Server-Cache-JBC Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Server-Cache-JBC 2.1.0.GA Look at all creation of Fqns, make sure the most efficient static factory method is used, typically Fqn.fromElements(T... elements). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1735) Implement EJB 3.1 bean concurrency

by Carlo de Wolf (JIRA)

Implement EJB 3.1 bean concurrency ---------------------------------- Key: EJBTHREE-1735 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1735 Project: EJB 3.0 Issue Type: Task Components: concurrency Reporter: Carlo de Wolf Assignee: Carlo de Wolf Priority: Critical Fix For: EJB 3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7998) HornetQ clustered configuration is copied to AS default profile

by Jeff Mesnil (JIRA)

HornetQ clustered configuration is copied to AS default profile --------------------------------------------------------------- Key: JBAS-7998 URL: https://jira.jboss.org/jira/browse/JBAS-7998 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (HornetQ) Affects Versions: 6.0.0.M3 Reporter: Jeff Mesnil Assignee: Clebert Suconic hornetq uses a non-clustered config for AS "default" profile and a clustered config for "all" profile. However AS build script overrides default profile with all (build/build.xml:219). deploy/hornetq/** must be added to the exclude list to prevent its non-clustered config to be overridden. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
2
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 2010