October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4865) Validate the JBM clustered config

by Clebert Suconic (JIRA)

Validate the JBM clustered config --------------------------------- Key: JBAS-4865 URL: http://jira.jboss.com/jira/browse/JBAS-4865 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: JBossAS-5.0.0.Beta3 This is just a link to a JBM task : JBMESSAGING-1093 I'm just double checking the clustered configuration is okay for jboss-messaging and doing some minor adjustments, and wanted a JIRA on the JBAS for the committs I'm doing. -- 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

18 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1093) Verify/Update the "all" configuration on JBossHead

by Clebert Suconic (JIRA)

Verify/Update the "all" configuration on JBossHead -------------------------------------------------- Key: JBMESSAGING-1093 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1093 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic 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

18 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1113) Post office and message updates at failover need to be transactional

by Tim Fox (JIRA)

Post office and message updates at failover need to be transactional -------------------------------------------------------------------- Key: JBMESSAGING-1113 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1113 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.GA Reporter: Tim Fox Assigned To: Ovidiu Feodorov At failover updates are made via the JDBCPersistenceManager (mergeQueues) and the post office. If the failing over server is itself killed during this process, then the system can enter an inconsistent state. Need to make sure all database updates are performed in a single transaction. -- 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

18 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-987) display non GMT+0 time zones

by Jean-Louis Rastapoc (JIRA)

display non GMT+0 time zones ---------------------------- Key: JBPM-987 URL: http://jira.jboss.com/jira/browse/JBPM-987 Project: JBoss jBPM Issue Type: Feature Request Components: Web Interface Affects Versions: jBPM jPDL 3.2 Reporter: Jean-Louis Rastapoc Assigned To: Tom Baeyens The web-console currently uses the default JSF timezone conversion and displays GMT+0. Other time zones should be read from the client or be configurable. -- 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

18 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1174) Add further passivation docs

by Brian Stansberry (JIRA)

Add further passivation docs ---------------------------- Key: JBCACHE-1174 URL: http://jira.jboss.com/jira/browse/JBCACHE-1174 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.1.0.GA Add discussion a la http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077805#4077805. I've already done this in my local checkout but can't figure out how to get the maven jdocbook stuff to run so I can validate. This task is just a reminder to finish up once a more urgent need drives me to figure this stuff out. -- 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

18 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1154) Introduce ability to mark nodes as immortal - i.e., they never get considered for eviction

by Manik Surtani (JIRA)

Introduce ability to mark nodes as immortal - i.e., they never get considered for eviction ------------------------------------------------------------------------------------------ Key: JBCACHE-1154 URL: http://jira.jboss.com/jira/browse/JBCACHE-1154 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA -- 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

18 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-1176) Bad performance when deleting a large tree from JDBCCacheLoader

by gmeroz (JIRA)

Bad performance when deleting a large tree from JDBCCacheLoader ---------------------------------------------------------------- Key: JBCACHE-1176 URL: http://jira.jboss.com/jira/browse/JBCACHE-1176 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.0.0.CR1 Reporter: gmeroz Assigned To: Manik Surtani When using JDBCCacheLaoder and trying to delete the hole tree: using: cache.getCache().removeNode(Fqn.ROOT) it takes a long time which may cause transaction timeouts when running on application server. it seems that each node is deleted seperately instead of using one sql command. -- 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

18 years, 9 months

3
3
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-375: ------------------------------------- Jeff- Feel free to implement another way if you wish. You don't have to use the patch. > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-486) Optimize activations

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-486?page=all ] Manik Surtani updated JBCACHE-486: ---------------------------------- Fix Version/s: 2.1.0.CR1 > Optimize activations > -------------------- > > Key: JBCACHE-486 > URL: http://jira.jboss.com/jira/browse/JBCACHE-486 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Jerry Gauthier > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.1.0.GA, 2.1.0.CR1 > > > JBCACHE-420 notes that activation processing is performed excessively. The resolution of JBCACHE-420 eliminates the excessive activations but it doesn't resolve the following optimization issue. > The ActivationInterceptor can't readily determine whether a node has been passivated because the cache loading operation occurs in the CacheLoaderInterceptor. Consequently the activation interceptor invokes loader.exists(node) to ascertain whether the node has been passivated. This works properly but is an unnecessary operation as the CacheLoader interceptor executes immediately prior to the Activation interceptor and it makes a similar determination. This determination can be expensive as itmay involve performing database operations (e.g., for a JDBC cache loader). > It's desirable to eliminate the loader.exists(node) invocation in the Activation interceptor to optimize performance. One possible way to accomplish this would be to add a pesudo attribute __PASSIVATED__ > to the node's hashmap (similar to __INITIALIZED__) whenever a node has been passivated, and remove it again when > activated. -- 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

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBAS-4855) jboss-web with 4.0 dtd does not deploy

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4855?page=all ] Thomas Diesler deleted JBAS-4855: --------------------------------- > jboss-web with 4.0 dtd does not deploy > -------------------------------------- > > Key: JBAS-4855 > URL: http://jira.jboss.com/jira/browse/JBAS-4855 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assigned To: Alexey Loubyansky > > [tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.context.WebServiceContextJSETestCase one-test > Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) > at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:153) > at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:71) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:86) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223) > ... 66 more > Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd > at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:306) > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402) > at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) > at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) > at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) -- 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

18 years, 9 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 October 2007