October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7291) Reduce memory usuage

by Scott Marlow (JIRA)

Reduce memory usuage -------------------- Key: JBAS-7291 URL: https://jira.jboss.org/jira/browse/JBAS-7291 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.2.0.Beta1 Reporter: Scott Marlow Fix For: JBossAS-6.0.0.Alpha1 This is an umbrella jira for all projects that are part of the application server. 6mb of memory used by 109, 552 instances of org.jboss.logging.Logger (these numbers include objects referenced by the Logger instances) 65.5mb org.jboss.mx.server.MBeanServerImpl 30mb org.jboss.virtual.plugins.context.zip.ZipEntryContext$EntryInfo Other details to be added -- 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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8449) DomainController to ServerManagerProtocol

by Jason Greene (JIRA)

DomainController to ServerManagerProtocol ----------------------------------------- Key: JBAS-8449 URL: https://jira.jboss.org/browse/JBAS-8449 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Jason Greene Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2725) Business Rules may not be handling Java Enums Correctly, DRL Generated does not work and Running Test Scenarios fails

by Daniel Cruver (JIRA)

Business Rules may not be handling Java Enums Correctly, DRL Generated does not work and Running Test Scenarios fails --------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2725 URL: https://jira.jboss.org/browse/JBRULES-2725 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Environment: Windows 7 (64 Bit) Sun JDK 1.6.0 Update 21 Reporter: Daniel Cruver Assignee: Mark Proctor I have created POJO Model Jar for importing into Guvnor. I can create A Business Rule (Guided Editor), it correctly allows me to set enumeration values and it validates correctly. But when I go to view source: In the when clause, it shows that it has converted the enumeration of VehicleType.AIR to "0" which is the cardinal value in quotes. In the then clause, it shows that it has converted the enumeration of VehicleType.AIR to 0 which is the cardinal value as an integer. Whenever I create a unit test with this rules and define facts I get this error: Unable to run the scenario. [Error: could not access/write property (type) in: com.example.model.Vehicle] [Near : {... __fact__.type = __val_ ....}] ^ [Line: 1, Column: 0] I have taken these generated DRL as given be Guvnor and tried to run them in a test driver. Using the rules as given it will not activate the rules, I have to replace the "0" and 0 with VehicleType.AIR in order for it to fire the rules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-301) Session bean and message driven bean metadata does not merge (auto) timer metadata correctly

by jaikiran pai (JIRA)

Session bean and message driven bean metadata does not merge (auto) timer metadata correctly -------------------------------------------------------------------------------------------- Key: JBMETA-301 URL: https://jira.jboss.org/browse/JBMETA-301 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ejb Affects Versions: jboss-metadata-ejb-2.0.0-alpha-18 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: jboss-metadata-ejb-2.0.0-alpha-19 MessageDrivenBean31MetaData, JBossMessageDrivenBean31MetaData, JBossSessionBean31MetaData, SessionBean31MetaData don't merge timer metadata correctly leading to incorrect timer information when a deployment contains both xml dd and annotations for the bean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8492) org.jboss.test.security.test.authorization.XACMLEJBIntegrationUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.security.test.authorization.XACMLEJBIntegrationUnitTestCase -------------------------------------------------------------------------- Key: JBAS-8492 URL: https://jira.jboss.org/browse/JBAS-8492 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Shelly McGowan Assignee: Marcus Moyses Fix For: 6.0.0.CR1 This regressions in test methods testJBAS6067 and testMethodAccess occurred after the PicketBox 3.0.0.CR2 upgrade. http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2722) Bug in VariablePersistenceStrategy when chosing a Variable Persister

by Nicolas Loriente (JIRA)

Bug in VariablePersistenceStrategy when chosing a Variable Persister -------------------------------------------------------------------- Key: JBRULES-2722 URL: https://jira.jboss.org/browse/JBRULES-2722 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.1.FINAL Reporter: Nicolas Loriente Assignee: Mark Proctor drools-persistence-jpa-5.1.1 has a bug in VariablePersistenceStrategy. When looking at "interfaces" to find a Variable Persister Drools currently doesn't find the persister for classes that extend a variable persister type. e.g. java.language.Long which extends Number which implements Serializable. By inheritance Long is a Serializable and shold be persited with SerializableVariablePersister if the persister is registered. The following block of code is found in the class "org.drools.persistence.processinstance.VariablePersistenceStrategy" in the method "private String getVariablePersistenceType(Object o)": // at last for interfaces Class<?>[] interfaces = o.getClass().getInterfaces(); if (interfaces != null) { for (Class<?> clazz : interfaces) { persisterFQN = types.get(clazz.getName()); if (persisterFQN != null && !persisterFQN.equals("")) { return persisterFQN; } } } Problem: This approach works ONLY when the interfaces are implemented directly but does NOT work when there is inheritance because o.getClass().getInterfaces() returns only the interfaces the class "o" implements directly but does NOT return the interfaces it's parent (and parent's parent, etc) implement. For example in considering SerializableVariablePersister: it WILL work when having a Serializable in the form of: class DummySerializable implements Serializable {.....} But it will NOT work if the serializable is in the form of: class ChildDummySerializable extends DummySerializable {.....} It will neither for any class that participates in the hierarchy (e.g. GrandChildDummySerializable extends ChildDummySerializable {.....}, etc.) If the variable that doesn't implement the Variable Persisted Type directly it will NOT be persisted with the "expected" variable persister. Suggested Fix: Class<?> clazz = o.getClass(); do { Class<?>[] interfaces = clazz.getInterfaces(); for(Class<?> interfaze : interfaces) { persisterFQN = types.get(interfaze.getName()); if (persisterFQN != null && !persisterFQN.equals("")) { System.out.println("Persistence strategy returns: " + persisterFQN); return persisterFQN; } } } while ( (clazz = clazz.getSuperclass() ) != null); The fix pointed above will walk through each class in the inheritance chain and will pull ALL interfaces until it finds one that is of a Variable Persisted Type and has a corresponding Variable Persister -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBJCA-436) Ant jar task fails due to missing repo property.

by Jeremy Whiting (JIRA)

Ant jar task fails due to missing repo property. ------------------------------------------------ Key: JBJCA-436 URL: https://jira.jboss.org/browse/JBJCA-436 Project: IronJacamar Issue Type: Task Components: Performance Environment: All Reporter: Jeremy Whiting Assignee: Jesper Pedersen Priority: Minor Attachments: build-diff.txt Running the Ant jar task fails due to missing 'fungal.repo' property. Need to add the property to 'performance/build.xml' allowing the ivy dependency resolution to work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-1240) TCP: add physical address of peer to physical address cache (bypassing discovery)

by Bela Ban (JIRA)

TCP: add physical address of peer to physical address cache (bypassing discovery) --------------------------------------------------------------------------------- Key: JGRP-1240 URL: https://jira.jboss.org/browse/JGRP-1240 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.11 When we use TCP, the physical address information of a peer P connecting to us should always be available ! E.g.currently, if we have A and B, and A wants to send a message to B, but doesn't have B's physical address, if A is connected to B, then we can get that information from the connection map in TCP ! We should therefore add the physical address information for B when B connects to us, or we connect to B ! Issues: - What if B binds to address 10.1.1.1, but - when B connects to us (A: 192.16.8.1.5) - its peer address is 192.168.1.3 ? Is this possible at all ? Does the routing table force a different peer address of B: 192.168.x.x rather than 10.1.x.x ? - Although we might be able to get the physical address of B, we don't get its logical name ! How would we do that, discovery ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JASSIST-123) Explicit class import support for compiler (not whole packages)

by Ivan Prisiazhnyy (JIRA)

Explicit class import support for compiler (not whole packages) --------------------------------------------------------------- Key: JASSIST-123 URL: https://jira.jboss.org/browse/JASSIST-123 Project: Javassist Issue Type: Patch Reporter: Ivan Prisiazhnyy Assignee: Shigeru Chiba This is patch for MemberResolver class for Javassist 3.12.GA It adds support for compiler to understand importing of certain classes in packages, not the whole packages. With this patch the following code will do its job: ClassPool x = ClassPool.getDefault(); x.importPackage("java.io.File"); Patch it self: *** MemberResolver.java 2010-06-10 14:38:03.000000000 +0300 *************** *** 429,445 **** } catch (NotFoundException e) { classPool.recordInvalidClassName(fqName); - - try { - if (pac.endsWith(orgName)) { - CtClass cc = classPool.get(pac); - // if the class is found, - classPool.recordInvalidClassName(orgName); - return cc; - } - } catch (NotFoundException ee) { - classPool.recordInvalidClassName(pac); - } } } } --- 429,434 ---- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JASSIST-121) CtClass getNestedClasses() returns the same class when applied to an anonymous class

by Dam Dam (JIRA)

CtClass getNestedClasses() returns the same class when applied to an anonymous class ------------------------------------------------------------------------------------ Key: JASSIST-121 URL: https://jira.jboss.org/browse/JASSIST-121 Project: Javassist Issue Type: Bug Affects Versions: 3.11.0.GA Environment: Windows Vista, JRE 1.6.0_20 Reporter: Dam Dam Assignee: Shigeru Chiba When calling the method getNestedClasses() on a CtClass that is an anonymous class, it returns the CtClass itself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2010