March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCOMMON-107) CVE-2009-2693

by Mike Millson (JIRA)

CVE-2009-2693 ------------- Key: JBCOMMON-107 URL: https://jira.jboss.org/jira/browse/JBCOMMON-107 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-old (1.x) Affects Versions: 1.0.0.GA Reporter: Mike Millson Assignee: Mike Millson CVE-2009-2693,: When deploying WAR files, the WAR files were not checked for directory traversal attempts. This allows an attacker to create arbitrary content outside of the web root by including entries such as ../../bin/catalina.sh in the WAR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2066) factoryProxy.toString() fails if called before registration in the Dispatcher

by Carlo de Wolf (JIRA)

factoryProxy.toString() fails if called before registration in the Dispatcher ----------------------------------------------------------------------------- Key: EJBTHREE-2066 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2066 Project: EJB 3.0 Issue Type: Bug Components: core Environment: Running with -Dsun.io.serialization.extendedDebugInfo=true Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: as-int 1.1.23, EJB3_1 1.0.6 org.jboss.aop.NotFoundInDispatcherException: Object with oid: org.jboss.ejb3.test.consumer.QueueTestRemotePRODUCER_FACTORY was not found in the Dispatcher at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:85) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1927) at org.jboss.remoting.Client.invoke(Client.java:770) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:48) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy128.toString(Unknown Source) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1379) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at java.rmi.MarshalledObject.<init>(MarshalledObject.java:101) at org.jnp.interfaces.MarshalledValuePair.<init>(MarshalledValuePair.java:65) at org.jnp.interfaces.NamingContext.createMarshalledValuePair(NamingContext.java:1429) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:569) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:542) at javax.naming.InitialContext.rebind(InitialContext.java:408) at org.jboss.util.naming.Util.rebind(Util.java:131) at org.jboss.util.naming.Util.rebind(Util.java:117) at org.jboss.ejb3.mdb.RemoteProducerFactory.start(RemoteProducerFactory.java:89) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-301) JBoss JCA 1.0.0.Alpha10

by Jesper Pedersen (JIRA)

JBoss JCA 1.0.0.Alpha10 ----------------------- Key: JBJCA-301 URL: https://jira.jboss.org/jira/browse/JBJCA-301 Project: JBoss JCA Issue Type: Release Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-294) Validate as early as possible

by Jesper Pedersen (JIRA)

Validate as early as possible ----------------------------- Key: JBJCA-294 URL: https://jira.jboss.org/jira/browse/JBJCA-294 Project: JBoss JCA Issue Type: Patch Components: Validator Reporter: Stefano Maestri Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha10 Do validation of the resource adapter classes as early as possible. Also create a test suite for the validator chain. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-300) Promote Stefano Maestri to committer

by Jesper Pedersen (JIRA)

Promote Stefano Maestri to committer ------------------------------------ Key: JBJCA-300 URL: https://jira.jboss.org/jira/browse/JBJCA-300 Project: JBoss JCA Issue Type: Task Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1171) Address cache in TP protocol never removes inactive members, which causes enourmous delays sending multicast messages using TCP

by Fedor Cherepanov (JIRA)

Address cache in TP protocol never removes inactive members, which causes enourmous delays sending multicast messages using TCP ------------------------------------------------------------------------------------------------------------------------------- Key: JGRP-1171 URL: https://jira.jboss.org/jira/browse/JGRP-1171 Project: JGroups Issue Type: Bug Affects Versions: 2.9, 2.8 Reporter: Fedor Cherepanov Assignee: Bela Ban org.jgroups.blocks.LazyRemovalCache used in org.jgroups.protocols.TP removes marked cache items only when it's size exceeds max_elements size, which is set to 20 in TP. I'm using jgroups (tried 2.8 and 2.9) with jboss-cache 3.2.1, using TCP protocol. I've tried to investigate why when any node leaves the cluster, replication time increases by a second (around 50ms initially). Here's what I found: What a node leaves the cluster and view changes: 1. TP calls logical_addr_cache.retainAll(members); 2. LazyRemovalCache.retainAll updates the map, setting removable flag to true on those members that are not in the view. 3. LazyRemovalCache.checkMaxSizeExceeded NEVER removes them from the cache because it's size is always less than max_elements, which is 20. 1. BasicTCP.sendMulticast calls TP.sendToAllPhysicalAddresses 2. TP.sendToAllPhysicalAddresses iterates through all values in logical_addr_cache calling sendUnicast for each 3. logical_addr_cache contains all the nodes including those killed, and tries to connect to each if them, which causes enormous delays This is causing replication time to increase for connection timeout for every node removed from cluster -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREFLECT-16) Fix the serialization for the javassist based ClassInfo implementation

by Adrian Brock (JIRA)

Fix the serialization for the javassist based ClassInfo implementation ---------------------------------------------------------------------- Key: JBREFLECT-16 URL: http://jira.jboss.com/jira/browse/JBREFLECT-16 Project: JBoss Reflection Issue Type: Task Components: Javassist Affects Versions: JBossReflection.2.2.0.Beta1 Reporter: Adrian Brock Make and test the javassist ClassInfo implementation Serializable -- 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

14 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-1147) TP: make logical_addr_cache's timeout configurable

by Bela Ban (JIRA)

TP: make logical_addr_cache's timeout configurable -------------------------------------------------- Key: JGRP-1147 URL: https://jira.jboss.org/jira/browse/JGRP-1147 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 [email Maher Al Kilani] I am using jgroups lib. I noticed that when one of the nodes is down, the lazyRemovalCache class tags it removable and all the nodes stay in logical_addr_cache (in TP.java). So when sending a message we are actually sending to all the removable and the alive ones. How can configure the lazyRemovalCache class to not tag as removable but rather remove the dead nodes? Bela: let's make the timeout and max size configurable. Plus, possibly add a getter, so we can hard-flush the caceh programmatically -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-577) Optimize adding aspect bindings to instance advisors

by Kabir Khan (JIRA)

Optimize adding aspect bindings to instance advisors ---------------------------------------------------- Key: JBAOP-577 URL: http://jira.jboss.com/jira/browse/JBAOP-577 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.1.0.GA With the changes from JBAOP-575, it seems that the chains are still fully calculated when woven with GeneratedAdvisorInstrumentor if added for an instance. Run org.jboss.test.aop.dynamicgenadvisor.DynamicTester.testSimpleInstanceUsingDomainForMethod() and testInstanceUsingDomainForMethod() in a debugger to see what I mean -- 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

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-777) Remove aop.xml from asintegration/src/etc

by Flavia Rainone (JIRA)

Remove aop.xml from asintegration/src/etc ----------------------------------------- Key: JBAOP-777 URL: https://jira.jboss.org/jira/browse/JBAOP-777 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone The aop.xml file is being added to the jboss-60-install-jboss-aop-build.xml script as part of JBAOP-772. This file can be removed as soon as the bootstrap version in AS is updated with the classpool changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010