March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6618) Upgrade Infinispan to 5.2.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6618?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6618: ---------------------------------------------- Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 901028|https://bugzilla.redhat.com/show_bug.cgi?id=901028] Also affects 6.1.0.ER1, see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-... > Upgrade Infinispan to 5.2.3.Final > --------------------------------- > > Key: AS7-6618 > URL: https://issues.jboss.org/browse/AS7-6618 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Tag: > https://github.com/infinispan/infinispan/tree/5.2.2.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

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6561) JSR-345 EJB 3.2 API Support

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6561?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-6561: ----------------------------------- Once we release EJB 3.2 API to include the changes done for JBEE-128, I'll send a PR containing the EJB 3.2 implementation of the new TimerService#getAllTimers() API, to AS7 upstream. > JSR-345 EJB 3.2 API Support > --------------------------- > > Key: AS7-6561 > URL: https://issues.jboss.org/browse/AS7-6561 > Project: Application Server 7 > Issue Type: Sub-task > Components: EJB > Reporter: David Lloyd > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > Implement EJB 3.2 specification as per Java EE 7 specification. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6568) TimerService.*SecondTestCase often fails intermittently

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/AS7-6568?page=com.atlassian.jira.plugin.s... ] Ivo Studensky resolved AS7-6568. -------------------------------- Resolution: Cannot Reproduce Bug I am closing this. I could not reproduce it outside of the lightning. As stated in the relevant PR the culprit of this was the change of the surefire working directory from '${basedir}/target/workdir' to '${basedir}'. But it is still unclear how such a change can interfere with the second timer testcases. > TimerService.*SecondTestCase often fails intermittently > ------------------------------------------------------- > > Key: AS7-6568 > URL: https://issues.jboss.org/browse/AS7-6568 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > > Two of the timer service tests in AS7 testsuite often fails due to a timeout. At least it looks like a timeout issue unless there is something else rotten in them. The tests wait 30s for the invocation of a timer which seems not to be sufficient sometimes. Need to say that 30s is a quite long timeout. It is weird. See the following PR for an example of such failures at the lightning. > https://github.com/jbossas/jboss-as/pull/4093 > Affected tests: > TimerServicePersistenceSecondTestCase.testTimerServiceCalled > TimerServiceSerializationSecondTestCase.testTimerServiceRestoredWithCorrectInfo > I will try to reproduce it on QE Hudson as the tests pass nicely when running locally on my laptop. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBEE-128) EJB 3.2 API (JSR-345) for EE7

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/JBEE-128?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on JBEE-128: ----------------------------------- A PR containing updates to the project pom and the TimerService API has been issued against upstream https://github.com/jboss/jboss-ejb-api_spec/pull/4 > EJB 3.2 API (JSR-345) for EE7 > ------------------------------ > > Key: JBEE-128 > URL: https://issues.jboss.org/browse/JBEE-128 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-ejb-api, jboss-javaee-specs > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Update the Java EE EJB API to incorporate the EJB 3.2 updates. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBEE-128) EJB 3.2 API (JSR-345) for EE7

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/JBEE-128?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated JBEE-128: ------------------------------ Component/s: jboss-ejb-api > EJB 3.2 API (JSR-345) for EE7 > ------------------------------ > > Key: JBEE-128 > URL: https://issues.jboss.org/browse/JBEE-128 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-ejb-api, jboss-javaee-specs > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > > Update the Java EE EJB API to incorporate the EJB 3.2 updates. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBEE-128) EJB 3.2 API (JSR-345) for EE7

by jaikiran pai (JIRA)

jaikiran pai created JBEE-128: --------------------------------- Summary: EJB 3.2 API (JSR-345) for EE7 Key: JBEE-128 URL: https://issues.jboss.org/browse/JBEE-128 Project: JBoss JavaEE Spec APIs Issue Type: Sub-task Reporter: jaikiran pai Assignee: jaikiran pai Update the Java EE EJB API to incorporate the EJB 3.2 updates. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6655) binding subcontexts with <lookup> does not work

by James Livingston (JIRA)

James Livingston created AS7-6655: ------------------------------------- Summary: binding subcontexts with <lookup> does not work Key: AS7-6655 URL: https://issues.jboss.org/browse/AS7-6655 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.3.Final (EAP) Reporter: James Livingston Assignee: Eduardo Martins If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6357) ejb timer service creates empty directories for all ejbs including those without timers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6357?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6357. --------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Done > ejb timer service creates empty directories for all ejbs including those without timers > --------------------------------------------------------------------------------------- > > Key: AS7-6357 > URL: https://issues.jboss.org/browse/AS7-6357 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Priority: Minor > Labels: directory, ejb, timer > Fix For: 8.0.0.Alpha1 > > > ejb timer service creates empty directories for all ejbs include those without timers > Empty directories are being created for all ejbs, even those that do not use timers. > $JBOSS_HOME/.../data/timer-service-data/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6653) Add clustered database based timers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6653?page=com.atlassian.jira.plugin.s... ] Stuart Douglas reassigned AS7-6653: ----------------------------------- Assignee: Stuart Douglas (was: jaikiran pai) > Add clustered database based timers > ----------------------------------- > > Key: AS7-6653 > URL: https://issues.jboss.org/browse/AS7-6653 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Clustering should be supported for database timers. > The general ideal will be that a single database is shared by all nodes in the cluster. When a timer is created it will be inserted into the database. Periodically at a configured interval nodes will refresh their list of active timers from the database. > When a timer expires a node will attempt to grab ownership of the timer in the database by updating the row. Due to the use of either optimisitic locking or traditional DB locks only 1 node will be successful, and that node will run the task. > We will also support write only nodes, nodes that can create timer tasks, but do not attempt to run them, to allow timer tasks to be run by a subset of the nodes. > So that you don't have hundreds of existing partition name feature will allow clustered timers to be grouped into smaller partitions, so you can limit the number of nodes that are contending for a timer. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-6654) Add ability to migrate timers between data stores

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6654: ----------------------------------- Summary: Add ability to migrate timers between data stores Key: AS7-6654 URL: https://issues.jboss.org/browse/AS7-6654 Project: Application Server 7 Issue Type: Feature Request Components: EJB Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 8.0.0.Alpha1 It should be possible to move timers between data stores, so that timers can be migrated from the legacy file store. -- 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, 4 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