November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-721) persistence unit in embeddable ejb3 doesn't deploy when datasource has leading JNDI path

by Levi Purvis (JIRA)

persistence unit in embeddable ejb3 doesn't deploy when datasource has leading JNDI path ---------------------------------------------------------------------------------------- Key: EJBTHREE-721 URL: http://jira.jboss.com/jira/browse/EJBTHREE-721 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD, EJB 3.0 RC10 - FD Environment: jboss-EJB-3.0_Embeddable_ALPHA_9, Eclipse 3.2, Sun JVM 1.5.0_08 Reporter: Levi Purvis Priority: Minor This problem only appears to happen with the embeddable release. A JNDI path such as the following will cause the persistence unit deployment to silently fail with no exception: <jta-data-source>java:/foo/bar/mydatasource</jta-data-source> Whereas this will succeed: <jta-data-source>java:/mydatasource</jta-data-source> -- 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

19 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-569) Update clustering design documentation wiki

by Tim Fox (JIRA)

Update clustering design documentation wiki ------------------------------------------- Key: JBMESSAGING-569 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-569 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 The design doc wiki should be updated to reflect the state of the clustering implementation. Some parts, especially the intelligent balancer are out of date. -- 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

19 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-130) Add JBoss Forums to Portal demo.

by Ryszard Kozmik (JIRA)

Add JBoss Forums to Portal demo. -------------------------------- Key: JBFORUMS-130 URL: http://jira.jboss.com/jira/browse/JBFORUMS-130 Project: JBoss Forums Issue Type: Task Reporter: Ryszard Kozmik Assigned To: Roy Russo Priority: Minor Fix For: 1.0.0 Beta It would be cool to have Forums deployed on JBoss Portal demo - http://portal.demo.jboss.com/ . -- 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

19 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-554) False "Duplicate declaration for variable" error when doing "Match( homeTeam == $team) || Match( awayTeam == $team)"

by Geoffrey De Smet (JIRA)

False "Duplicate declaration for variable" error when doing "Match( homeTeam == $team) || Match( awayTeam == $team)" -------------------------------------------------------------------------------------------------------------------- Key: JBRULES-554 URL: http://jira.jboss.com/jira/browse/JBRULES-554 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Reporter: Geoffrey De Smet Assigned To: Mark Proctor Priority: Minor [Maybe assign to Edson, he asked me to open in mailing list thread "Yet another or question"] On the 3.0.x branch (update from this time) when declaring this rule: query "multipleMatchesPerTeamPerDay" $team : Team(); Match( $id : id, homeTeam == $team, $day : day ) || Match( $id : id, awayTeam == $team, $day : day ); exists Match( id > $id, homeTeam == $team, day == $day ) || exists Match(id > $id, awayTeam == $team, day == $day ); end It reports an error: org.drools.rule.InvalidRulePackage: Duplicate declaration for variable '$day' in the rule 'multipleMatchesPerTeamPerDay' Testcase patch coming up. -- 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

19 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-582) Modify and test release-admin.xml so it is capable of creating clustered configurations using a different database than mysql

by Ovidiu Feodorov (JIRA)

Modify and test release-admin.xml so it is capable of creating clustered configurations using a different database than mysql ----------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-582 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-582 Project: JBoss Messaging Issue Type: Task Components: Build System Affects Versions: 1.2.0.Alpha1 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha2 This should allow the user to run release-admin.xml with -Ddatabase=[mysql|oracle|postgres|...] -- 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

19 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (EJBTHREE-716) Add a flag to disable replication event notification

by Ben Wang (JIRA)

Add a flag to disable replication event notification ---------------------------------------------------- Key: EJBTHREE-716 URL: http://jira.jboss.com/jira/browse/EJBTHREE-716 Project: EJB 3.0 Issue Type: Sub-task Components: Clustering Reporter: Ben Wang This came up from an email thread: (1) By default, passivation events get called during replication cycle (2) There is a config setting to disable this (3) We should introduce JBoss-specific replication-only and passivation-only events that actually let you directly write/read the bytestream (4) I will work to get two sets of events into the next EJB spec, ie. introduce @PreReplicate / @PostReplicate or something like that We should now tie the replication to passivation events (there is no concrete spec but everyone else is doing it). But we should also have a flag to disable it if needs to. -- 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

19 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3873) EJB 2.1 - 17.6.2.8 - setRollbackOnly must throw IllegalStateException when called from EJB with transaction attribute of Supports, NotSupported or Never

by Darran Lofthouse (JIRA)

EJB 2.1 - 17.6.2.8 - setRollbackOnly must throw IllegalStateException when called from EJB with transaction attribute of Supports, NotSupported or Never -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3873 URL: http://jira.jboss.com/jira/browse/JBAS-3873 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA Reporter: Darran Lofthouse Assigned To: Scott M Stark Fix For: JBossAS-4.2.0.CR1 EJB 2.1 - 17.6.2.8 - setRollbackOnly must throw IllegalStateException when called from EJB with transaction attribute of Supports, NotSupported or Never. However for an EJB with a transaction attribute of Supports if it is called with a transaction calls to setRollbackOnly succeed. -- 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

19 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-3892) Replace TxManager with JBoss Transactions 4.2.2

by Dimitris Andreadis (JIRA)

Replace TxManager with JBoss Transactions 4.2.2 ----------------------------------------------- Key: JBAS-3892 URL: http://jira.jboss.com/jira/browse/JBAS-3892 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Transaction Manager Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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

19 years, 5 months

2
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-858) Investigate POJOCACHE failures

by Manik Surtani (JIRA)

Investigate POJOCACHE failures ------------------------------ Key: JBCACHE-858 URL: http://jira.jboss.com/jira/browse/JBCACHE-858 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 2.0.0.ALPHA1 Reporter: Manik Surtani Assigned To: Ben Wang Fix For: 2.0.0.ALPHA2 Ben, This pertains to the following tests: org.jboss.cache.pojo.collection.ReplicatedSyncMapTest org.jboss.cache.pojo.collection.ReplicatedSyncSetTest org.jboss.cache.pojo.region.LocalConcurrentTest These have been marked as "known issues" as of 2.0.0.Alpha1 so you won't see them in CC builds until you un-mark them as "known issues" in build.xml. -- 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

19 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-593) Analyse current JGroups stack usage

by Tim Fox (JIRA)

Analyse current JGroups stack usage ----------------------------------- Key: JBMESSAGING-593 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-593 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR5 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 Need to tune our JGroups stack config to get the best performance possible. Also we need to consider whether we really need to two stacks and if we do, then which protocols we can safely omit from one. We need Brian and/or Bela's help with this one. -- 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

19 years, 5 months

4
5
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 November 2006