November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1185) Reduce logging level when a lifecycle operation is performed twice

by Brian Stansberry (JIRA)

Reduce logging level when a lifecycle operation is performed twice ------------------------------------------------------------------ Key: JBCACHE-1185 URL: http://jira.jboss.com/jira/browse/JBCACHE-1185 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.1.0.GA We log a WARN when, for example, stop() is invoked when the cache is already stopped. But this can happen easily (and validly) when the JMX wrappers are used with the microcontainer. MC stops the Cache and then the wrapper is stopped, which calls through to the Cache. This kind of thing is normal and we handle it properly, so we shouldn't log a warn. Perhaps having the wrappers test the cache status before invoking on it would be better; that way we can still warn in other situations. -- 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, 8 months

1
1
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.2.0.GA (was: 2.1.0.GA) > 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.2.0.GA > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (GPD-185) CLONE -Exception in New Page Flow wizard

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-185?page=all ] Koen Aers updated GPD-185: -------------------------- Component/s: jpdl > CLONE -Exception in New Page Flow wizard > ---------------------------------------- > > Key: GPD-185 > URL: http://jira.jboss.com/jira/browse/GPD-185 > Project: JBoss jBPM GPD > Issue Type: Bug > Components: jpdl > Reporter: Koen Aers > Assigned To: Koen Aers > Fix For: jBPM jPDL Designer 3.1.0.SP1 > > > EXECUTE: Invoke 'New Page Flow' wizard. > EXECUTE: Click 'Browse...' button. > EXECUTE: Click 'Cancel' in 'Folder Selection' dialog. > FAILURE: Log contains exception java.lang.IllegalArgumentException: Argument cannot be null. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Moved: (GPD-185) CLONE -Exception in New Page Flow wizard

by Koen Aers (JIRA)

[ http://jira.jboss.com/jira/browse/GPD-185?page=all ] Koen Aers moved JBIDE-1319 to GPD-185: -------------------------------------- Project: JBoss jBPM GPD (was: JBoss Tools) Key: GPD-185 (was: JBIDE-1319) Issue Type: Bug (was: Feature Request) Component/s: (was: jbpm) Fix Version/s: jBPM jPDL Designer 3.1.0.SP1 (was: 2.0.0.GA) Affects Version/s: (was: 2.0.0.CR1) > CLONE -Exception in New Page Flow wizard > ---------------------------------------- > > Key: GPD-185 > URL: http://jira.jboss.com/jira/browse/GPD-185 > Project: JBoss jBPM GPD > Issue Type: Bug > Reporter: Koen Aers > Assigned To: Koen Aers > Fix For: jBPM jPDL Designer 3.1.0.SP1 > > > EXECUTE: Invoke 'New Page Flow' wizard. > EXECUTE: Click 'Browse...' button. > EXECUTE: Click 'Cancel' in 'Folder Selection' dialog. > FAILURE: Log contains exception java.lang.IllegalArgumentException: Argument cannot be null. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2235) Server Controller Tasks: Throw error if normal shutdown fails

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2235?page=all ] Ryan Campbell reopened JBAS-2235: --------------------------------- This issue requires further discussion. I'll open a forum posting so we can clear it up there. > Server Controller Tasks: Throw error if normal shutdown fails > ------------------------------------------------------------- > > Key: JBAS-2235 > URL: http://jira.jboss.com/jira/browse/JBAS-2235 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Environment: jboss-4.0 tip > Reporter: Ryan Campbell > Assigned To: Martin Vecera > Fix For: JBossAS-5.0.0.Beta3 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Currently, when a server fails to respond to a shutdown request, the process is killed and the tests continue. > There should be an error thrown if the server fails to shutdown within the timeout period. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1081) Simulation query with stddev not supported on HSQL

by Ronald van Kuijk (JIRA)

Simulation query with stddev not supported on HSQL -------------------------------------------------- Key: JBPM-1081 URL: http://jira.jboss.com/jira/browse/JBPM-1081 Project: JBoss jBPM Issue Type: Bug Components: Simulation Affects Versions: jBPM jPDL 3.2.3 Environment: N/A Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.3 According to a user in the forum, stddev is not supported in the HSQLDialect on the hibernate version that comes with jBPM. I have not had the opportunity to verify this. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-1079) Put jBPM jPDL releases into the JBoss Maven Repo

by Matthew Lieder (JIRA)

Put jBPM jPDL releases into the JBoss Maven Repo ------------------------------------------------ Key: JBPM-1079 URL: http://jira.jboss.com/jira/browse/JBPM-1079 Project: JBoss jBPM Issue Type: Task Affects Versions: jBPM jPDL 3.2.2 Reporter: Matthew Lieder Assigned To: Tom Baeyens You have v3.2.1 in repository.jboss.org/maven2, but not v3.2.2. -- 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, 8 months

3
7
0 / 0

[JBoss JIRA] Resolved: (JBAS-2235) Server Controller Tasks: Throw error if normal shutdown fails

by Martin Vecera (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2235?page=all ] Martin Vecera resolved JBAS-2235. --------------------------------- Resolution: Done > Server Controller Tasks: Throw error if normal shutdown fails > ------------------------------------------------------------- > > Key: JBAS-2235 > URL: http://jira.jboss.com/jira/browse/JBAS-2235 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Environment: jboss-4.0 tip > Reporter: Ryan Campbell > Assigned To: Martin Vecera > Fix For: JBossAS-5.0.0.Beta3 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Currently, when a server fails to respond to a shutdown request, the process is killed and the tests continue. > There should be an error thrown if the server fails to shutdown within the timeout period. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2235) Server Controller Tasks: Throw error if normal shutdown fails

by Martin Vecera (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2235?page=comments#action_12387542 ] Martin Vecera commented on JBAS-2235: ------------------------------------- org.jboss.test.util.server.ServerController.stopServer() is not throwing a IOException (ServerShutdownException) when the server is not shutdown properly. I grepped through the sources of test project and AS and it doesn't change any actual behaviour. > Server Controller Tasks: Throw error if normal shutdown fails > ------------------------------------------------------------- > > Key: JBAS-2235 > URL: http://jira.jboss.com/jira/browse/JBAS-2235 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Test Suite > Environment: jboss-4.0 tip > Reporter: Ryan Campbell > Assigned To: Martin Vecera > Fix For: JBossAS-5.0.0.Beta3 > > > Currently, when a server fails to respond to a shutdown request, the process is killed and the tests continue. > There should be an error thrown if the server fails to shutdown within the timeout period. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1435) JCA Interceptors

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1435?page=all ] Anil Saldhana updated JBAS-1435: -------------------------------- Summary: JCA Interceptors (was: Interceptors) > JCA Interceptors > ---------------- > > Key: JBAS-1435 > URL: http://jira.jboss.com/jira/browse/JBAS-1435 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Shelly McGowan > Priority: Minor > Fix For: JBossAS-5.0.1.CR1 > > > Forums discussion thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48683 > This is really a major rewrite of the JCA implementation to be less monolithic > so this will need some careful design and consideration and > breaking up into more fine grained tasks. > The idea is to provide containers/interceptors for the components within the JCA module > such that these components can be more easily customised and developed according to > the needs of each user. > There are three main interceptor stacks that I can think of: > 1) ConnectionManager (connection allocation) > This provides an interceptor stack behind the ConnectionFactory/DataSource proxy > to process the allocateConnection invocation. > It will look something like: > ConnectionFactory proxy -> ConnectionManager interceptor -> Pooling interceptor > 2) ManagedConnection/ConnectionEventListener (connection management) > This stack provides most of the features that are currently performed by the > BaseManagerConnection2$ConnectionListener and their supporting methods, > but as an interceptor stack. > As now they will largely be driven by the events from the resource adapter, > and it this object that is actually pooled. > 3) Resource Adaptors > The JDBC and JMS adaptors should be implemented as interceptor stacks > to allow optional interceptors like statistics collection, custom behaviour > and also to perform vendor specific processing/workarounds. > Where AOP can be used, we could actually instrument the vendor classes so > we can also expose vendor specific methods, not just the JDBC interfaces. > This would remove the requirement to do things like getUnderlyingConection() by user code. -- 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, 8 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 November 2007