May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (HIBERNATE-83) Create release notes for Hibernate

by Gail Badner (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-83?page=comments#action_12412064 ] Gail Badner commented on HIBERNATE-83: -------------------------------------- There is another expected unit test failure which is only on MSSQL2005: org.hibernate.test.legacy.MasterDetailTest.testCachedCollectionRefresh The certified DBs are oracle 9i, 10g, mssql 2005, postgresql, mysql. > Create release notes for Hibernate > ---------------------------------- > > Key: HIBERNATE-83 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-83 > Project: Hibernate > Issue Type: Task > Reporter: Gail Badner > Assigned To: Bawany Satgunanathan > > Create release notes for the standalone application that includes: > 1) expected unit test failures > 2) if "non-supported" dependencies are not included in the distribution, then unit tests using those dependencies will fail out of the box; this should be documented > 3) JDK 1.4 is not supported; no testing done using JDK 1.4; only JDK 1.5 is supported > Does anything else need to be put in the release notes for the standalone product? > Should there be release notes for Hibernate embedded in EAP? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1279) Replace JNDI lookups of HAPartition with HAPartitionLocator

by Brian Stansberry (JIRA)

Replace JNDI lookups of HAPartition with HAPartitionLocator ----------------------------------------------------------- Key: EJBTHREE-1279 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1279 Project: EJB 3.0 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: AS 5.0.0.CR1 The ha-server-api lib now has a locator class; the clustered bean containers should use it instead of doing a JNDI lookup. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1311) Installer must remove jboss-ejb3-core.jar from $JBOSS_HOME/client

by Andrew Lee Rubinger (JIRA)

Installer must remove jboss-ejb3-core.jar from $JBOSS_HOME/client ----------------------------------------------------------------- Key: EJBTHREE-1311 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1311 Project: EJB 3.0 Issue Type: Task Components: installer Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.CR1 -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1258) serialising a package breaks function removal

by Mark Proctor (JIRA)

serialising a package breaks function removal ---------------------------------------------- Key: JBRULES-1258 URL: http://jira.jboss.com/jira/browse/JBRULES-1258 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1 Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: FUTURE DynamicRulesTest.testDynamicFunction breaks if you serialise the package first before use. On inspection I cannot initially see what is going wrong. The code seems to be successfully recreating the new classloader and re-writing all invokers, yet it still fails :( -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1095) Deserializing Package Objects Consumes Large Amount of Memory

by Ming Jin (JIRA)

Deserializing Package Objects Consumes Large Amount of Memory ------------------------------------------------------------- Key: JBRULES-1095 URL: http://jira.jboss.com/jira/browse/JBRULES-1095 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Environment: Windows Reporter: Ming Jin Assigned To: Mark Proctor Deserializing the Package objects from storage to memory consumes large amount of memory. My tests showed that for a serialized size of 1MB, 18MB of memory would be consumed during deserialization, mostly from the method org.drools.rule.Package.readExternal. A test program with resulting profile data would be uploaded. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-5501) CacheManager to support aliasing of caches

by Brian Stansberry (JIRA)

CacheManager to support aliasing of caches ------------------------------------------ Key: JBAS-5501 URL: http://jira.jboss.com/jira/browse/JBAS-5501 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Support injection of a map of alternate names for caches; allow code that requests a particular cache to be given another. Example is clustered sso can request its default clustered-sso cache but be given the ha-partition 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2007) resp.signOut() fails

by Thomas Heute (JIRA)

resp.signOut() fails -------------------- Key: JBPORTAL-2007 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2007 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.4 Final Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.5 Final -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5404) Updated session maxInactiveInterval not respected on backup nodes

by Brian Stansberry (JIRA)

Updated session maxInactiveInterval not respected on backup nodes ----------------------------------------------------------------- Key: JBAS-5404 URL: http://jira.jboss.com/jira/browse/JBAS-5404 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA, JBossAS-4.2.1.GA, JBossAS-4.2.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 The algorithm for evicting backup copies of sessions from the distributed cache uses the session timeout value from web.xml to evaluate whether a backup copy of a session is overage. It does not take into consideration the fact that an individual session may have had its maxInterval changed. The session is expired appropriately on the node where it is active; it's just that the backup copy doesn't get flushed from the cache as promptly. If there is a failover after the maxInterval has elapsed, JBossWeb will see that and expire the session; it won't provide it to a client. Fixing this requires adding a mechanism to make the CacheListener aware when an imcoming replicated session has had its maxInterval changed. In 4.x, the session is an opaque object (MarshalledValue for which the CacheListener lacks the appropriate classloader) so a fix in 4.x would require passing the maxInterval as an attribute in the JBC node. Checking for this would be highly non-performant. In AS 5 I want to make the session more transparent, plus the JBC 2.x API provides the CacheListener with a lot more information about what events are happening. So a better fix is possible there. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Assigned: (JBAS-1728) Statement.getConnection not working for remote client

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1728?page=all ] Dimitris Andreadis reassigned JBAS-1728: ---------------------------------------- Assignee: Jeff Zhang (was: Jesper Pedersen) Jesper, didn't you want Jeff to look at this? > Statement.getConnection not working for remote client > ----------------------------------------------------- > > Key: JBAS-1728 > URL: http://jira.jboss.com/jira/browse/JBAS-1728 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Jeff Zhang > > the org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService is not handling Statement.getConnection. It returns the real thing instead of a proxy --> Serialization exception!!. > This is related to JBAS-1678. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1728) Statement.getConnection not working for remote client

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1728?page=all ] Dimitris Andreadis updated JBAS-1728: ------------------------------------- Comment: was deleted > Statement.getConnection not working for remote client > ----------------------------------------------------- > > Key: JBAS-1728 > URL: http://jira.jboss.com/jira/browse/JBAS-1728 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Assigned To: Jesper Pedersen > > the org.jboss.resource.adapter.jdbc.remote.WrapperDataSourceService is not handling Statement.getConnection. It returns the real thing instead of a proxy --> Serialization exception!!. > This is related to JBAS-1678. -- 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, 8 months

1
0
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 May 2008