November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-133) Hosting trailblazer on docs site

by Mark Little (JIRA)

Hosting trailblazer on docs site -------------------------------- Key: JBESB-133 URL: http://jira.jboss.com/jira/browse/JBESB-133 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Testing Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Daniel Brum Priority: Minor Fix For: 4.0 We should look at hosting the TB here along with some good writeup on it, diagrams explaining each step of the way, etc... http://www.jboss.com/docs/demos -- 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, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (JBADMCON-149) Support JBoss Messaging

by chi lin (JIRA)

Support JBoss Messaging ----------------------- Key: JBADMCON-149 URL: http://jira.jboss.com/jira/browse/JBADMCON-149 Project: JBoss Admin Console Issue Type: Feature Request Components: General Console Affects Versions: 1.1 alpha Reporter: chi lin Assigned To: chi lin Fix For: 1.1 alpha Since JBoss Messaging will be the default JMS provider for JBoss AS 5.x, the Admin Console should support JBoss Messaging instead of (or in addition to) JBossMQ. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-628) Investigate message priority in presence of prefetching

by Tim Fox (JIRA)

Investigate message priority in presence of prefetching ------------------------------------------------------- Key: JBMESSAGING-628 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-628 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 A user has observed non optimal delivery of messages based on priority. We need to investigate to see if there is indeed an issue here, and if/what we need to do about it. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBTM-168) Recovery extensions mentioned more than once in property file.

by Mark Little (JIRA)

Recovery extensions mentioned more than once in property file. -------------------------------------------------------------- Key: JBTM-168 URL: http://jira.jboss.com/jira/browse/JBTM-168 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Minor Fix For: 4.4 -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-616) Race in creating new counters

by Tim Fox (JIRA)

Race in creating new counters ----------------------------- Key: JBMESSAGING-616 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-616 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 When creating a new counter with the same name from different nodes in a clustered config, it is possible they could be created at the same time (since the select.. for update) needs an actual row to lock. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3398) Non exploded sar containing war cannot undeploy the war file properly

by Julien Viet (JIRA)

Non exploded sar containing war cannot undeploy the war file properly --------------------------------------------------------------------- Key: JBAS-3398 URL: http://jira.jboss.com/jira/browse/JBAS-3398 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final Environment: JBoss-4.0.4.GA MacOSX Tiger Java 1.4.2 Reporter: Julien Viet Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.GA A sar file containing a war file non exploded is dropped in AS before startup. Start JBoss Shutdown JBoss The MainDeployer wants to stop() / destroy() the war file. The Web deployer is already gone and it produces an javax.management.InstanceNotFoundException when it tries to stop() / destroy() the war deployer Because the war is nested in a sar file, the web deployer is undeployed before the sar containing the war is undeployed. Note : this does not happen with exploded sar (like http invoker sar that contains the invoker.war) because the war is added to the MainDeployer.deploymentList list. This does not happen with non exploded because the war file is not in the local directory but rather in tmp and thus does not get added to the deployment list. Here are some field values : the string used to discriminate wether it's in local or tmp - file:/Users/julien/java/jboss-4.0.4.GA/server/default/tmp/deploy/ a war in non exploded sar - file:/Users/julien/java/jboss-4.0.4.GA/server/default/tmp/deploy/tmp51485jboss-portal.sar-contents/portal-core.war invoker.war in exploded sar - file:/Users/julien/java/jboss-4.0.4.GA/server/default/deploy/http-invoker.sar/invoker.war/ -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3860) XAManagedConnection should implement LocalTransaction to clean up hanging LocalTransaction

by Weston Price (JIRA)

XAManagedConnection should implement LocalTransaction to clean up hanging LocalTransaction ------------------------------------------------------------------------------------------ Key: JBAS-3860 URL: http://jira.jboss.com/jira/browse/JBAS-3860 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Weston Price Assigned To: Weston Price Fix For: JBossAS-4.2.0.CR1 Currently, XAManagedConnection does not implement the LocalTransaction interface. As a result the following conditions produces an error: @TransactionDemarcation(NotSupported) public void doSomething() { DataSource ds = ... (XADataSource) Connection c = ds.getConnection(); c.setAutoCommit(false); // NOT Managed transaction // do stuff throw EJBException("Container/JCA should rollback uncommitted transaction!"); } Because of the c.setAutoCommit(false), a LocalTransaction is started. When the EJBException is thrown, the transaction is left hanging. Typically this is handled in the TxConnectionEventListener for LocalManagedConnection. However, in the case of XAManagedConnection the get mc.getLocalTransaction() throws a ResourceException and the transaction is never rolled back. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-888) Remove TreeCache.UNITIALIZED, add NodeSPI.get/setDataLoaded()

by Elias Ross (JIRA)

Remove TreeCache.UNITIALIZED, add NodeSPI.get/setDataLoaded() ------------------------------------------------------------- Key: JBCACHE-888 URL: http://jira.jboss.com/jira/browse/JBCACHE-888 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Elias Ross Assigned To: Manik Surtani For 2.0, I believe the intent is to stop having code explicitly reference TreeCache. One thing that strikes me as extremely clumsy is the TreeCache.UNITIALIZED flag that is set in the data map itself. I believe that adding the flag to the node can accomplish the same thing. It might make sense to look at this http://java.sun.com/j2se/1.5.0/docs/api/java/util/EnumSet.html for setting flags, etc. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-889) EvictionPolicy methods for 2.0, consider revising

by Elias Ross (JIRA)

EvictionPolicy methods for 2.0, consider revising ------------------------------------------------- Key: JBCACHE-889 URL: http://jira.jboss.com/jira/browse/JBCACHE-889 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Elias Ross Assigned To: Manik Surtani I noticed that nobody seems to use EvictionPolicy methods such as getChildrenNames(), hasChild(), getCacheData(), etc. It might make sense to simply remove these methods and add a EvictionPolicy { Cache getCache(); } . Change EvictionPolicy.configure() to EvictionPolicy.setCache() to match. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-867) Refactor use of TreeCacheProxyImpl

by Elias Ross (JIRA)

Refactor use of TreeCacheProxyImpl ---------------------------------- Key: JBCACHE-867 URL: http://jira.jboss.com/jira/browse/JBCACHE-867 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani Move methods from TreeCacheProxyImpl to the NodeImpl itself. Consider also removing this class and having TreeCache implement Cache. -- 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, 6 months

2
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 November 2006