April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1330) EJB timer service should use a thread pool to avoid OOM

by Galder Zamarreno (JIRA)

EJB timer service should use a thread pool to avoid OOM ------------------------------------------------------- Key: EJBTHREE-1330 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1330 Project: EJB 3.0 Issue Type: Bug Components: pool Affects Versions: AS 4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor The default EJB timer service used by the EJB3 layer is based on org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory which delegates to the standard org.jboss.ejb.txtimer.EJBTimerService. For EJB3 beans using the EJB timer service the thread local pool should not be used. Since the current EJB timer service creates a new thread for each timer being created, the thread local pool will create a matching instance of the bean for that thread. Thus the number of active instances in total can effectively grow unchecked and thus an OOM will occur. -- 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

12 years, 5 months

5
8
0 / 0

[JBoss JIRA] Created: (JBSER-117) Problem with JBoss serializing of dynamic proxies

by Maksym Ivanchenko (JIRA)

Problem with JBoss serializing of dynamic proxies ------------------------------------------------- Key: JBSER-117 URL: https://jira.jboss.org/jira/browse/JBSER-117 Project: JBoss Serialization Issue Type: Bug Affects Versions: 1.0.3 GA Reporter: Maksym Ivanchenko Assignee: Clebert Suconic When we try to serialize a proxy that contains some child entity which points to proxy itself the following exception occurs: org.jboss.serial.exception.SerializationException: Object reference 1 was not found Simple test case for problem reproducing: import java.io.Serializable; import java.lang.reflect.InvocationHandler; import java.lang.reflect.Method; import java.lang.reflect.Proxy; import org.jboss.serial.io.JBossObjectOutputStream; import org.junit.Test; public class StandaloneProxySerializationTest { @Test public void testSerialization() throws Exception { ISampleEntity entity = new SampleEntityImpl(); Class<?>[] interfaces = new Class<?>[] {ISampleEntity.class}; SampleEntityInvocationHandler handler = new SampleEntityInvocationHandler(entity); ISampleEntity proxy = (ISampleEntity) Proxy.newProxyInstance(Thread.currentThread() .getContextClassLoader(), interfaces, handler); ISampleEntity childEntity = new SampleEntityImpl(); proxy.setChild(childEntity); childEntity.setParent(proxy); JBossObjectOutputStream jbossSerializer = new JBossObjectOutputStream(null); jbossSerializer.smartClone(proxy); } private static interface ISampleEntity { public ISampleEntity getParent(); public void setParent(ISampleEntity parent); public ISampleEntity getChild(); public void setChild(ISampleEntity child); } private static class SampleEntityImpl implements ISampleEntity, Serializable { private static final long serialVersionUID = 1L; private ISampleEntity parent; private ISampleEntity child; @Override public ISampleEntity getParent() { return parent; } @Override public void setParent(ISampleEntity parent) { this.parent = parent; } @Override public ISampleEntity getChild() { return child; } @Override public void setChild(ISampleEntity child) { this.child = child; } } private static class SampleEntityInvocationHandler implements InvocationHandler, Serializable { private static final long serialVersionUID = 1L; private ISampleEntity entity; public SampleEntityInvocationHandler(ISampleEntity entity) { this.entity = entity; } @Override public Object invoke(Object proxy, Method method, Object[] args) throws Throwable { return method.invoke(entity, args); } } } Upon ivestigating this issue we found that the problem is in ProxyPersister.readData() method. It reads the handler, the proxy class, constructs a proxy and only then puts it to cache. But if a proxy data contains proxy itself then it tries to find it by reference (which is not in cache yet, because the handler is still being read). So it throws "Object reference not found" exception. We worked around this problem by introducing an InvocationHandler wrapper in ProxyPersister: Patched ProxyPersister.java: /* * JBoss, Home of Professional Open Source * Copyright 2005, JBoss Inc., and individual contributors as indicated * by the @authors tag. See the copyright.txt in the distribution for a * full listing of individual contributors. * * This is free software; you can redistribute it and/or modify it * under the terms of the GNU Lesser General Public License as * published by the Free Software Foundation; either version 2.1 of * the License, or (at your option) any later version. * * This software is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this software; if not, write to the Free * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA * 02110-1301 USA, or see the FSF site: http://www.fsf.org. */ package org.jboss.serial.persister; import java.io.IOException; import java.io.ObjectInput; import java.io.ObjectOutput; import java.lang.reflect.Constructor; import java.lang.reflect.InvocationHandler; import java.lang.reflect.InvocationTargetException; import java.lang.reflect.Method; import java.lang.reflect.Proxy; import org.jboss.serial.classmetamodel.ClassMetaData; import org.jboss.serial.classmetamodel.StreamingClass; import org.jboss.serial.exception.SerializationException; import org.jboss.serial.objectmetamodel.ObjectSubstitutionInterface; import org.jboss.serial.objectmetamodel.ObjectsCache; /** * $Id: ProxyPersister.java,v 1.11 2006/04/24 23:49:40 csuconic Exp $ * * @author <a href="mailto:clebert.suconic@jboss.com">Clebert Suconic</a> */ public class ProxyPersister implements Persister { private byte id; public byte getId() { return id; } public void setId(byte id) { this.id = id; } public void writeData(ClassMetaData metaData, ObjectOutput output, Object obj, ObjectSubstitutionInterface substitution) throws IOException{ Object handler = Proxy.getInvocationHandler(obj); output.writeObject(obj.getClass()); output.writeObject(handler); } static class InvocationHandlerWrapper implements InvocationHandler { private InvocationHandler wrappedHandler; public void setWrappedHandler(InvocationHandler wrappedHandler) { this.wrappedHandler = wrappedHandler; } public Object invoke(Object proxy, Method method, Object[] args) throws Throwable { return wrappedHandler.invoke(proxy, method, args); } } public Object readData (ClassLoader loader, StreamingClass streaming, ClassMetaData metaData, int referenceId, ObjectsCache cache, ObjectInput input, ObjectSubstitutionInterface substitution) throws IOException{ try { Class proxy = (Class)input.readObject(); Constructor constructor = proxy.getConstructor(new Class[] { InvocationHandler.class }); InvocationHandlerWrapper wrapper = new InvocationHandlerWrapper(); Object obj = constructor.newInstance(new Object[]{wrapper}); cache.putObjectInCacheRead(referenceId,obj); Object handler = input.readObject(); wrapper.setWrappedHandler((InvocationHandler) handler); return obj; } catch (ClassNotFoundException e) { throw new SerializationException(e); } catch (NoSuchMethodException e) { throw new SerializationException(e); } catch (IllegalAccessException e) { throw new SerializationException(e); } catch (InstantiationException e) { throw new SerializationException(e); } catch (InvocationTargetException e) { throw new SerializationException(e); } } public boolean canPersist(Object obj) { // not implemented return false; } } -- 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

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2293) Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal

by Steve Ronderos (JIRA)

Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal ------------------------------------------------------------------------------------------------ Key: JBRULES-2293 URL: https://jira.jboss.org/jira/browse/JBRULES-2293 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Environment: Windows XP Java 5 Running in Oracle OC4J 10.1.3.2 Reporter: Steve Ronderos Assignee: Mark Proctor I encountered an issue today with my KnowledgeAgent removing resources from its RuleBase shortly after creating it. I have the ResourceChangeScanner running in my application. I tracked the issue back to the scan() method in ResourceChangeScannerImpl. It appears that the method is trying to identify resources that are no longer available and remove them from both the RuleBase and future scans. To do this it is checking lastModified on the resource and on a result of 0 removing the resource. The resources that I configured in my change-set definitely still exist, but due to URL handler implementation provided by my classloader, getLastModified always returns 0. (The resource I'm retrieving is coming from a jar that is in my application's classpath and the URL handler implementation is oracle.classloader.SharedCodeSourceURL) Full Email Group trail: http://www.nabble.com/Issue-with-ResourceChangeScanner-td25792358.html Michael recommends to never scan classpath resources. -- 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

12 years, 5 months

6
13
0 / 0

[JBoss JIRA] Created: (JBRULES-1880) Can fire rules after disposing the Stateful session

by Sravanthi Tipirneni (JIRA)

Can fire rules after disposing the Stateful session --------------------------------------------------- Key: JBRULES-1880 URL: https://jira.jboss.org/jira/browse/JBRULES-1880 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Sravanthi Tipirneni Assignee: Mark Proctor Priority: Minor I can access the session and fire rules even after the session is disposed using the dispose method -- 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

12 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2124) KnowledgeAgent should load knowledge bases directly from Resource (bypassing the ChangeSet)

by Jürgen Schiewe (JIRA)

KnowledgeAgent should load knowledge bases directly from Resource (bypassing the ChangeSet) ------------------------------------------------------------------------------------------- Key: JBRULES-2124 URL: https://jira.jboss.org/jira/browse/JBRULES-2124 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.0.1.FINAL Reporter: Jürgen Schiewe Assignee: Mark Proctor We develop Drools based applications and use Guvnor as a a repository. Hard-coding the hostname where Guvnor runs is not an option for us because the names are different in each installation and we do not want to modify all the changeset.xml files for each deployment. Instead we would pass one (or more) Resources to the KnowledgeAgent and let it do the monitoring. This would allow us to build URLs dynamically from our system environment configuration. -- 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

12 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-1001) Use ByteMan / Metronome to inject faults for testing

by Bela Ban (JIRA)

Use ByteMan / Metronome to inject faults for testing ---------------------------------------------------- Key: JGRP-1001 URL: https://jira.jboss.org/jira/browse/JGRP-1001 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Use ByteMan (jboss.org/byteman) to simulate issues that can happen at runtime: do this in unit tests. For example: crash of merge leader after initial round (who frees the locks ?) (same for FLUSH) -- 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

12 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1721) Implement @Asynchronous

by Andrew Lee Rubinger (JIRA)

Implement @Asynchronous ------------------------ Key: EJBTHREE-1721 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1721 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: EJB 3.1 Container task for @Asynchronous handling as specified by EJB 3.1 -- 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

12 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-7856) parameter element missing value in profile.xml

by thamizhelango natarajan (JIRA)

parameter element missing value in profile.xml ---------------------------------------------- Key: JBAS-7856 URL: https://jira.jboss.org/jira/browse/JBAS-7856 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: Windows,X86 Reporter: thamizhelango natarajan <bean name="AttachmentStore" class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore"> <constructor><parameter class="java.io.File"><inject bean="BootstrapProfileFactory" property="attachmentStoreRoot" /></parameter></constructor> The parameter element missing class attribute -- 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

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBLOGGING-30) TCLFilter fails to get correct URLs from classloader in AS-5

by jaikiran pai (JIRA)

TCLFilter fails to get correct URLs from classloader in AS-5 -------------------------------------------------------------- Key: JBLOGGING-30 URL: https://jira.jboss.org/jira/browse/JBLOGGING-30 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-logging-log4j Affects Versions: 2.1.0.GA-jboss-logging Reporter: jaikiran pai Assignee: jaikiran pai As explained in JBAS-6532, the TCLFilter doesn't work in AS-5 because it never attempts to use the URLClassLoader while retrieving the Classloader URLs. A patch is attached to that JIRA (details of the patch are in the forum thread) which needs to be applied in jboss-logging-log4j component to get this working. -- 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

12 years, 6 months

5
9
0 / 0

[JBoss JIRA] Created: (JBRULES-443) Release drools binaries with debug information

by Juergen none (JIRA)

Release drools binaries with debug information ---------------------------------------------- Key: JBRULES-443 URL: http://jira.jboss.com/jira/browse/JBRULES-443 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Juergen none Assigned To: Mark Proctor Priority: Trivial Would it be possible to supply a debug-build of the binaries in addition to the existing downloads (where at least the drools jar files are without debug-info)? -- 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

12 years, 6 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2010