August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-444) Release 1.2.0.Alpah1

by Ovidiu Feodorov (JIRA)

Release 1.2.0.Alpah1 -------------------- Key: JBMESSAGING-444 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-444 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-525) postgresql-persistence-service.xml contains invalid SQL syntax

by Takayoshi Kimura (JIRA)

postgresql-persistence-service.xml contains invalid SQL syntax -------------------------------------------------------------- Key: JBMESSAGING-525 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-525 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Affects Versions: 1.0.1.CR4 Environment: JBoss 4.0.4.GA, JBoss Messaging 1.0.1.CR4, PostgreSQL 8.1 Reporter: Takayoshi Kimura Assigned To: Ovidiu Feodorov Attachments: postgresql-persistence-service.xml.patch The UPDATE_UNRELIABLE_CHANNELCOUNT SQL in postgresql-persistence-service.xml uses "UPDATE tablename alias" syntax but PostgreSQL does not support this syntax. http://www.postgresql.org/docs/8.1/static/sql-update.html http://www.postgresql.org/docs/7.4/static/sql-update.html To fix this, simply remove the aliases from the SQL. -- 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, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-744) Expand CacheLoader API to support streaming state transfer

by Vladimir Blagojevic (JIRA)

Expand CacheLoader API to support streaming state transfer ---------------------------------------------------------- Key: JBCACHE-744 URL: http://jira.jboss.com/jira/browse/JBCACHE-744 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0, 1.3.0, 1.2 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.0.0 CacheLoader API prior to 2.0 does not support streaming state transfer feature implemented in Jgroups 2.4. In order to transfer application state to a receiving cache node we currently have to load entire state into memory and send it to a receiving cache node. Major limitation of this approach is that the state transfer that is very large (>total memory allocated by JVM) would result in OutOfMemoryException. For example, if a cacheloader is pointing to a huge DOM tree, whose aggregate size is 2GB (and which has partly been passivated to disk), then the state provider cacheloader node can simply iterate over the DOM tree (activating the parts which have been passivated out to disk), and write it to the OutputStream as it traverses the tree. The receiving cacheloader will simply read from the InputStream and reconstruct the tree on its side, possibly again passivating parts to disk. Rather than having to provide a 2GB byte[] buffer (besides the state, so the needed memory is ca 4GB temporarily), streaming state transfer transfers the state in chunks of N bytes (user configurable). In order to accomodate this feature CacheLoader API will be expanded to include the following methods: void storeEntireState(InputStream s); void storeState(Fqn subtree,InputStream s); void loadEntireState(OutputStream s); void loadState(Fqn subtree,OutputStream s); -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-518) Implement distributed destinations

by Tim Fox (JIRA)

Implement distributed destinations ---------------------------------- Key: JBMESSAGING-518 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-518 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-517) Implement intelligent balancer

by Tim Fox (JIRA)

Implement intelligent balancer ------------------------------ Key: JBMESSAGING-517 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-517 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 Implement intelligent balancer as described in http://wiki.jboss.org/wiki/Wiki.jsp?page=NewClusteringDesign -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3454) Unable to set negative values for MBean attributes using Twiddle command

by Sakthi Samabsivam (JIRA)

Unable to set negative values for MBean attributes using Twiddle command -------------------------------------------------------------------------- Key: JBAS-3454 URL: http://jira.jboss.com/jira/browse/JBAS-3454 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.3 SP1 Reporter: Sakthi Samabsivam Priority: Minor When a customer tries to execute twiddle to set a negative value for one of the attributes, it throws the exception. For example when I try to set a Scheduler MBean InitialRepitions value to -1, it fails. Command: twiddle set "jboss:service=Scheduler" "InitialRepetitions" "-1". Possible problem might be, GetOpt class used in the org.jboss.console.twiddle.SetCommand Class is not accepting the -ve values.It consider the -ve numbers as an invalid option. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-956) "no selection" for Theme Leads to Null Pointer Exception

by Richard Mitchell (JIRA)

"no selection" for Theme Leads to Null Pointer Exception -------------------------------------------------------- Key: JBPORTAL-956 URL: http://jira.jboss.com/jira/browse/JBPORTAL-956 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: Fedora Core 5 Reporter: Richard Mitchell I was experimenting with theme selection in 2.4.0-CR1. I tried each of the four defined ones which each worked great. I then tried "no selection" to see how that behaved. I received an HTTP 500 error with a Null Pointer Exception whenever I went to a page from that point forward. I hadn't really "customized" much yet so that, after suggested in the user forum, I blew away the database. All is fine now. I am avoiding that "no selection" entry though. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-117) release notes for JTS talk about context interceptor

by Mark Little (JIRA)

release notes for JTS talk about context interceptor ---------------------------------------------------- Key: JBTM-117 URL: http://jira.jboss.com/jira/browse/JBTM-117 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, JTS Implementation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 Should update to talk about interposition interceptor. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-123) Remove hardcoded class names

by Mark Little (JIRA)

Remove hardcoded class names ---------------------------- Key: JBESB-123 URL: http://jira.jboss.com/jira/browse/JBESB-123 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Class oCls = Class.forName("org.jboss.soa.esb.util.BobjStdDTO"); -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBFORUMS-99) Jira Shows Real Name Rather than Alias After Create New Issue

by Sascha Goldsmith (JIRA)

Jira Shows Real Name Rather than Alias After Create New Issue ------------------------------------------------------------- Key: JBFORUMS-99 URL: http://jira.jboss.com/jira/browse/JBFORUMS-99 Project: JBoss Forums Issue Type: Bug Environment: Browsing with Firefox 1.5 Reporter: Sascha Goldsmith Assigned To: Ryszard Kozmik Priority: Minor After posting a JIRA issue, I was shown a page summarizing my post. On the left navigation area, it indicates 'author' with my real name, rather than my nic/alias. Nearly everywhere else in the forums/site/etc., I am referred to by my alias/nic. Having people's actual names posted seems a bit invasive from a privacy perspective. - Saish -- 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, 9 months

2
1
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 August 2006