[JBoss JIRA] Created: (JBCLUSTER-150) CNFE issues with Hibernate and JBoss Cache
by Brian Stansberry (JIRA)
CNFE issues with Hibernate and JBoss Cache
------------------------------------------
Key: JBCLUSTER-150
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-150
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: Q4Y6
Hibernate w/ JBC as 2nd level cache can potentially place instances of custom user classes in the cache. Can happen if the query cache is used, since instances of custom classes can be parameters to queries.
This leads to replication or state transfer problems like the following if the custom classes are not visible to JBC's classloader (i.e. the custom classes aren't in server/all/lib). For regular entity caching, Hibernate stores primitives in the cache, so this is less of an issue. Problem is more with the query cache.
java.lang.ClassNotFoundException: No ClassLoaders found for: services.entities.ProductDemandPK
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:585)
at org.jboss.invocation.MarshalledValueInputStream.resolveClass(MarshalledValueInputStream.j
ava:109)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.cache.Fqn.readExternal(Fqn.java:355)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.cache.loader.NodeData.readExternal(NodeData.java:59)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren(
StateTransferIntegrator_140.java:241)
at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren(
StateTransferIntegrator_140.java:271)
at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren(
StateTransferIntegrator_140.java:271)
at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren(
StateTransferIntegrator_140.java:271)
at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateTransientState(StateTr
ansferIntegrator_140.java:222)
at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateTransientState(StateTr
ansferIntegrator_140.java:97)
at org.jboss.cache.TreeCache._setState(TreeCache.java:2640)
at org.jboss.cache.TreeCache.access$000(TreeCache.java:86)
at org.jboss.cache.TreeCache$MessageListenerAdaptor.setState(TreeCache.java:5306)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.passUp(MessageDispatcher.java:614)
at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:331)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:55
4)
at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691)
at java.lang.Thread.run(Thread.java:595)
JBC's region-based marshalling API is meant for dealing with this kind of thing. Need to see how Hibernate can be configured to work with this API. Expect this will lead to JIRAs in the Hibernate and possible EBJ3 project.
--
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
16 years, 8 months
[JBoss JIRA] Created: (JBAS-3426) Fix org.jboss.test.jacc.test.WebIntegrationUnitTestCase in HEAD
by Anil Saldhana (JIRA)
Fix org.jboss.test.jacc.test.WebIntegrationUnitTestCase in HEAD
---------------------------------------------------------------
Key: JBAS-3426
URL: http://jira.jboss.com/jira/browse/JBAS-3426
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security, Web (Tomcat) service
Environment: org.jboss.test.jacc.test.WebIntegrationUnitTestCase(JACC)
as well as org.jboss.test.jacc.test.WebIntegrationUnitTestCase
Reporter: Anil Saldhana
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta
There is privileges related exception that is showing up in HEAD whereas in Branch_4_0, does not show up.
=======================================================================================
10:37:07,843 INFO [ENCServlet] InitialContext.env:
10:37:07,843 INFO [ENCServlet] Key: java.naming.factory.initial, value: org.jnp.interfaces.NamingContextFactory
10:37:07,843 INFO [ENCServlet] Key: java.naming.factory.url.pkgs, value: org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces
10:37:07,890 ERROR [[invoker]] Allocate exception for servlet invoker
java.lang.SecurityException: Servlet of class org.apache.catalina.servlets.Invok
erServlet is privileged and cannot be loaded by this web application
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
java:1114)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:784)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
=========================================================================================
Something changed in TC6 as to how web apps can invoke the container servlets?
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBCACHE-711) Replication eats out exception on the remote node
by Ben Wang (JIRA)
Replication eats out exception on the remote node
-------------------------------------------------
Key: JBCACHE-711
URL: http://jira.jboss.com/jira/browse/JBCACHE-711
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Replication
Affects Versions: 1.4.0
Reporter: Ben Wang
Assigned To: Manik Surtani
Fix For: 2.0.0
I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication. When the remote node throws an exception like NPE, the originating node will display with NonSerializableException. I don't a unit test for this but I think it should be easy to reproduce.
21:51:32,490 INFO [TxInterceptor] There was a problem handling this request
java.io.NotSerializableException: RpcDispatcher returned a null. This is most often caused by args for _replicate(_put(null, /testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean, org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable.
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114)
at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException
by Anil Saldhana (JIRA)
Redeploy of Tomcat5 Service chokes with RuntimeException
--------------------------------------------------------
Key: JBAS-3517
URL: http://jira.jboss.com/jira/browse/JBAS-3517
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security, Web (Tomcat) service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA
Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens.
You will notice the following Runtime Exception and the tomcat service fails to deploy.
==============================================================================================
13:33:30,421 INFO [Catalina] Initialization processed in 562 ms
13:33:30,421 INFO [StandardService] Starting service jboss.web
13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1
7
13:33:30,453 INFO [StandardHost] XML validation disabled
13:33:30,468 INFO [Catalina] Server startup in 47 ms
13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer
java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl
etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee
at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185)
at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
===================================================================================
Use the following api of PolicyContext in Tomcat5 service
http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h...
--
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
16 years, 9 months