[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
[JBoss JIRA] Commented: (JBAS-3350) NPE on <service-ref> in web.xml
by Remy Maucherat (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3350?page=comments#action_12345496 ]
Remy Maucherat commented on JBAS-3350:
--------------------------------------
To save you time, you can set the "org.apache.catalina.STRICT_SERVLET_COMPLIANCE" system property to "false".
> NPE on <service-ref> in web.xml
> -------------------------------
>
> Key: JBAS-3350
> URL: http://jira.jboss.com/jira/browse/JBAS-3350
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assigned To: Remy Maucherat
> Priority: Critical
> Fix For: JBossAS-5.0.0.Beta
>
>
> tdiesler@TDDELL /cygdrive/d/svn/jbossws/trunk/src/test
> $ ant -Dtest=org.jboss.test.ws.wsse.WebClientTestCase one-test
> 2006-06-29 11:02:35,953 ERROR [org.apache.catalina.startup.ContextConfig] Parse error in application web.xml file at jndi:/localhost/jbossws-wsse-rpc/WEB-INF/web.xml
> java.lang.NullPointerException
> at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2725)
> at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2751)
> at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1060)
> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
> <web-app version='2.4' xmlns='http://java.sun.com/xml/ns/j2ee' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd'>
> <servlet>
> <servlet-name>Hello</servlet-name>
> <servlet-class>org.jboss.ws.integration.jboss.JBossServiceEndpointServlet</servlet-class>
> <init-param>
> <param-name>ServiceEndpointImpl</param-name>
> <param-value>org.jboss.test.ws.wsse.HelloJavaBean</param-value>
> </init-param>
> </servlet>
> <servlet>
> <servlet-name>RpcTestClientServlet</servlet-name>
> <servlet-class>org.jboss.test.ws.wsse.RpcTestClientServlet</servlet-class>
> </servlet>
> <servlet-mapping>
> <servlet-name>Hello</servlet-name>
> <url-pattern>/Hello</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>RpcTestClientServlet</servlet-name>
> <url-pattern>/RpcTestClientServlet</url-pattern>
> </servlet-mapping>
> <service-ref>
> <service-ref-name>service/HelloService</service-ref-name>
> <service-interface>javax.xml.rpc.Service</service-interface>
> <wsdl-file>WEB-INF/wsdl/HelloService.wsdl</wsdl-file>
> <jaxrpc-mapping-file>WEB-INF/jaxrpc-mapping.xml</jaxrpc-mapping-file>
> <port-component-ref>
> <service-endpoint-interface>org.jboss.test.ws.wsse.Hello</service-endpoint-interface>
> </port-component-ref>
> </service-ref>
> </web-app>
--
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
[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
[JBoss JIRA] Created: (JBAS-3772) JBossCache classes fail serialization compatibility tests
by Ryan Campbell (JIRA)
JBossCache classes fail serialization compatibility tests
---------------------------------------------------------
Key: JBAS-3772
URL: http://jira.jboss.com/jira/browse/JBAS-3772
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Ryan Campbell
Assigned To: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-4.0.5.GA
The serialVersionUID's changed for the following classes between JBoss 4.0.4 & JBoss 4.0.5:
serialVersionUID error for org.jboss.cache.OptimisticTreeNode, 404 -5988969949899616983, current: 7000622696587912654
serialVersionUID error for org.jboss.cache.ReplicationException, 404 1652498986885131620, current: -2141504272926290430
Please confirm if these classes are serialized in any way, and if customers will experience faults if running both versions of JBoss, or using 4.0.4 client jars against a 4.0.5 server.
--
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
[JBoss JIRA] Created: (JBSEAM-427) contactlist example nonfunctional with JSF 1.2 RI
by Chuck Adams (JIRA)
contactlist example nonfunctional with JSF 1.2 RI
-------------------------------------------------
Key: JBSEAM-427
URL: http://jira.jboss.com/jira/browse/JBSEAM-427
Project: JBoss Seam
Issue Type: Bug
Reporter: Chuck Adams
I'm using the JSF 1.2 RI in JBoss, and to get any example to run, I have to move el-api.jar and el-impl.jar to the jsf-libs directory and remove them from the war, or else the ConfigureListener bombs. No big deal, once I do that, the booking example works fine.
The same isn't the case for the contactlist example however: the search page works, but view and edit just bring up a blank contact. When I switched back to myfaces, it worked perfectly (even though I forgot to set jbossHasMyFacesLifecycleBug back to true)
--
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