September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-767) Fail more silently when setting node versions

by Owen Taylor (JIRA)

Fail more silently when setting node versions --------------------------------------------- Key: JBCACHE-767 URL: http://jira.jboss.com/jira/browse/JBCACHE-767 Project: JBoss Cache Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Owen Taylor Assigned To: Manik Surtani Priority: Minor Attachments: jbosscache-fail-more-silently-20060912.patch Hibernate's OptimisticTreeCache.writeUpdate does: Option option = new Option(); option.setFailSilently( true ); option.setDataVersion( NonLockingDataVersion.INSTANCE ); cache.remove( new Fqn( regionFqn, key ), "ITEM", option ); Which you would expect would remove the item if it exists, while setting the data version, and silently do nothing otherwise. But it ends up, logging at level INFO: 12:55:38,360 INFO [org.jboss.cache.interceptors.TxInterceptor] (http-127.0.0.1-8080-1): There was a problem handling this request java.lang.NullPointerException at org.jboss.cache.interceptors.OptimisticNodeInterceptor.invoke(OptimisticNodeInterceptor.java:68) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.EvictionInterceptor.invoke(EvictionInterceptor.java:84) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.OptimisticCreateIfNotExistsInterceptor.invoke(OptimisticCreateIfNotExistsInterceptor.java:69) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.invoke(OptimisticValidatorInterceptor.java:75) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:122) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.OptimisticReplicationInterceptor.invoke(OptimisticReplicationInterceptor.java:136) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:345) at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:156) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:183) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:5530) at org.jboss.cache.TreeCache.remove(TreeCache.java:3742) at org.jboss.cache.TreeCache.remove(TreeCache.java:3297) at org.hibernate.cache.OptimisticTreeCache.writeLoad(OptimisticTreeCache.java:76) There are some differences of opinion as to what should be logged at level INFO, but that's pretty clearly too much and too scary looking. My assumption is that any NullPointerException in the logs is a serious problem. What the attached patch does is if the failSiliently option is set and the node doesn't exist, just skip setting the version. If failSilenlty isn't set, then it throws a CacheException rather than the current NullPointerException. -- 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, 7 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-111) JMX support

by Kurt Stam (JIRA)

JMX support ----------- Key: JBESB-111 URL: http://jira.jboss.com/jira/browse/JBESB-111 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Priority: Minor Fix For: 4.0 Support for JMX (the one build into java5) so you can look at the pool and reset connection 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-110) 1 tx per connection config

by Kurt Stam (JIRA)

1 tx per connection config -------------------------- Key: JBESB-110 URL: http://jira.jboss.com/jira/browse/JBESB-110 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Fix For: 4.0 Oracle does not allow multiple tx over 1 connection, however the JCA spec allows this (and most open source dbs support it). So we need some setting you can turn on to block the connection while a tx is in progress. Just for Oracle..as it will send Oracle into a spin lock :). This is not something for beta1. So don't sweat 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-109) DB reconnect after network failure/DB down

by Kurt Stam (JIRA)

DB reconnect after network failure/DB down ------------------------------------------ Key: JBESB-109 URL: http://jira.jboss.com/jira/browse/JBESB-109 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Kurt Stam Assigned To: Mohit Keswani Fix For: 4.0 Add db reconnnect feature (congifurable). Before using a connection check if the connection is still valid, if not clean up this connection and try to use another existing connection, if a connections are removed, try to make a new connection. If this fails give up, throw exception, but next time try again.. -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-149) Refactor Object Store as per design goals for G.A release

by Daniel Brum (JIRA)

Refactor Object Store as per design goals for G.A release --------------------------------------------------------- Key: JBESB-149 URL: http://jira.jboss.com/jira/browse/JBESB-149 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Daniel Brum Assigned To: Daniel Brum Fix For: 4.0 Change Rosetta Object Store implementation to support Re-Architecture Message changes. - remove EJB dependency, standalone service - change DB pool logic (Apache project?) - support persisting and lookup of Message - pluggable persistence engine, i.e: database or file, or other. For G.A only database to be supported -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-120) ObjectStore configured differently from other components

by Mark Little (JIRA)

ObjectStore configured differently from other components -------------------------------------------------------- Key: JBESB-120 URL: http://jira.jboss.com/jira/browse/JBESB-120 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 Why does the object store configuration work differently from other components? Specifically, it doesn't use the ParamsRepository approach. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-90) Refactor base business classes

by Mark Little (JIRA)

Refactor base business classes ------------------------------ Key: JBESB-90 URL: http://jira.jboss.com/jira/browse/JBESB-90 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Esteban Schifman Fix For: 4.0 Beta 1 -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-103) Refactor BobjStdDTO

by Mark Little (JIRA)

Refactor BobjStdDTO ------------------- Key: JBESB-103 URL: http://jira.jboss.com/jira/browse/JBESB-103 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Esteban Schifman Fix For: 4.0 As well as renaming the class, how much of it needs to be seen by developers? The have to provide toXML and fromXML (via constructor), but do they need to see everything else? If there are no other methods that they need to be concerned about, can we not refactor this into an interface that has just the methods developers need and use the rest as the engine for driving implementations of that class? -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-158) Update manuals on EPR and Message changes.

by Mark Little (JIRA)

Update manuals on EPR and Message changes. ------------------------------------------ Key: JBESB-158 URL: http://jira.jboss.com/jira/browse/JBESB-158 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-120) GUI for setting up security in JBForums

by Ryszard Kozmik (JIRA)

GUI for setting up security in JBForums --------------------------------------- Key: JBFORUMS-120 URL: http://jira.jboss.com/jira/browse/JBFORUMS-120 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Ryszard Kozmik Fix For: 1.1.0 Alpha We need a proper GUI for setting up security in forums. It should be much userfriendly than editing xml file. -- 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, 7 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 September 2006