March 2007 - jboss-jira - Jboss List Archives

[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

17 years, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (JGRP-310) Update training to use latest version

by Bela Ban (JIRA)

Update training to use latest version ------------------------------------- Key: JGRP-310 URL: http://jira.jboss.com/jira/browse/JGRP-310 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 - Include 2.5 - Change the labs/slides to use the Receiver (push approach) - Possibly include a Multiplexer example -- 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

17 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAOP-347) ClassCastException in MarshalledValue.java

by Tim McCune (JIRA)

ClassCastException in MarshalledValue.java ------------------------------------------ Key: JBAOP-347 URL: http://jira.jboss.com/jira/browse/JBAOP-347 Project: JBoss AOP Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 1.5.3.GA Environment: JBoss 4.0.4, Whatever version of JBossAOP is bundled in with JBoss EJB 3.0-RC9-FD, JDK 1.6 Reporter: Tim McCune I tried enabling JBoss serialization with EJB 3 remoting for the first time today, by changing the line <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute> to <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?serializationtype=jboss</attribute> in ejb3.deployer/META-INF/jboss-service.xml. When I do this, any remote call to my EJB results in the following exception on the client: java.lang.ClassCastException: org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput at org.jboss.aop.util.MarshalledValue.writeExternal(MarshalledValue.java:190) at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) at org.jboss.aop.metadata.SimpleMetaData.writeExternal(SimpleMetaData.java:226) at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) at org.jboss.aop.joinpoint.MethodInvocation.writeExternal(MethodInvocation.java:321) at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithFields(RegularObjectPersister.java:182) at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:90) at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:298) at org.jboss.remoting.serialization.impl.jboss.JBossSerializationManager.sendObject(JBossSerializationManager.java:87) at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:84) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:273) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.remoting.ClusterChooserInterceptor.invoke(ClusterChooserInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessClusteredProxy.invoke(StatelessClusteredProxy.java:100) ... Looking at the code for MarshalledValue.java in the writeExternal method, the following line casts the ObjectOutput parameter to an OutputStream in order to take advantage of ByteArrayOutputStream's writeTo method: baos.writeTo((OutputStream)out); However, the assumption that the "out" parameter may be cast to an OutputStream in not a valid one. When using jboss serialization instead of java serialization, the "out" parameter that is passed in is of type org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput, which implements ObjectOutput, but does not extends OutputStream. A simple fix is to change the line above to: out.write(baos.toByteArray()); I don't know if the writeTo method gives noticeably better performance. If it does, it might be worth it to do an instanceof check first. -- 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

17 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-158) Non-existent manifest Class-Path refs produce vfs IllegalStateException

by Scott M Stark (JIRA)

Non-existent manifest Class-Path refs produce vfs IllegalStateException ----------------------------------------------------------------------- Key: JBMICROCONT-158 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-158 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark Assigned To: Scott M Stark When the structure deployers parse a top-level jboss-test-entity.jar with a manifest like: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.6.5 Created-By: 1.5.0_09-b01 (Sun Microsystems Inc.) Class-Path: ejb.jar jnp-client.jar jboss-client.jar jndi.jar jboss-jmx .jar junit.jar deploy.jar it fails with: Caused by: java.lang.IllegalStateException: JarHandler@28271403[path= context=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar real=file:/C:/home/svn/JBossHead/jboss-head/testsuite/output/lib/jboss-test-entity.jar] has no parent. at org.jboss.virtual.VFSUtils.addManifestLocations(VFSUtils.java:116) at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.processContext(DefaultStructureBuilder.java:131) at org.jboss.deployers.plugins.structure.DefaultStructureBuilder.populateContext(DefaultStructureBuilder.java:89) The invalid references should at most produce debug level warnings. -- 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

17 years, 10 months

5
11
0 / 0

[JBoss JIRA] Created: (JBCACHE-971) Eviction policy based on adaptive replacement

by Manik Surtani (JIRA)

Eviction policy based on adaptive replacement --------------------------------------------- Key: JBCACHE-971 URL: http://jira.jboss.com/jira/browse/JBCACHE-971 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Quote from Mircea Markus: There is an eviction policy algorithm more efficient than LRU (which I found quite popular) - Adaptive Replacement Policy. The basic idea is to not rely only on the time of last access to the node, but also on the number of time(frequency) a given node was accessed. Here it is a nice description of how it works: http://en.wikipedia.org/wiki/Adaptive_Replacement_Cache. -- 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

17 years, 10 months

2
10
0 / 0

[JBoss JIRA] Created: (JBREM-677) Compression marshalling fails intermittently.

by Ron Sigal (JIRA)

Compression marshalling fails intermittently. --------------------------------------------- Key: JBREM-677 URL: http://jira.jboss.com/jira/browse/JBREM-677 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Boon) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta2 (Boon) When used with EJB's, CompressingUnMarshaller intermittently throws java.io.IOException: Not in GZIP format. -- 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

17 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-968) Test on 80 node cluster

by Manik Surtani (JIRA)

Test on 80 node cluster ----------------------- Key: JBCACHE-968 URL: http://jira.jboss.com/jira/browse/JBCACHE-968 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.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

17 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1011) memory based eviction policy

by Mircea Markus (JIRA)

memory based eviction policy ---------------------------- Key: JBCACHE-1011 URL: http://jira.jboss.com/jira/browse/JBCACHE-1011 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 2.1.0.GA As with Java5 java offers support for determining the size of objects. An memory based eviction policy can be written for this java version only. The basic idea is to let the user to specify the amount of memory he wants to use. -- 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

17 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-816) Create a CacheProxy to allow cache replication across WANs

by Manik Surtani (JIRA)

Create a CacheProxy to allow cache replication across WANs ---------------------------------------------------------- Key: JBCACHE-816 URL: http://jira.jboss.com/jira/browse/JBCACHE-816 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.3.0 This has to do with multiple JBoss Cache clusters deployed on LANs as islands, requiring a bridge between such islands. An ideal use case is where a cluster spans multiple data centres and would need to replicate across a WAN. The ideal strategy would be to allow for async bridging, since most calls would be colocated to a single LAN, but may fail over to a remote LAN (pretty much the same idea of async repl within a LAN, except that now we treat an entire LAN as a host. Sort of a meta-cluster). For more details and some brainstorming ideas, see: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres -- 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

17 years, 11 months

3
4
0 / 0

[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

17 years, 11 months

3
6
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 March 2007