July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4501) JBoss AS won't build with JDK 1.7

by Fernando Nasser (JIRA)

JBoss AS won't build with JDK 1.7 --------------------------------- Key: JBAS-4501 URL: http://jira.jboss.com/jira/browse/JBAS-4501 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Reporter: Fernando Nasser JBoss AS 4.2.0.GA fails to build with JDK 1.6 -- 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

18 years, 2 months

3
15
0 / 0

[JBoss JIRA] Created: (JBAS-4069) Test clustering in an 80 node cluster

by Brian Stansberry (JIRA)

Test clustering in an 80 node cluster ------------------------------------- Key: JBAS-4069 URL: http://jira.jboss.com/jira/browse/JBAS-4069 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, EJB3, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.GA Test in the Tyson's Corner lab (10 8-core boxes) Test web session clustering and EJB3 SFSB and entity clustering. -- 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

18 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-150) CNFE issues with Hibernate and JBoss Cache

by Brian Stansberry (JIRA)

CNFE issues with Hibernate and JBoss Cache ------------------------------------------ Key: JBCLUSTER-150 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-150 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q4Y6 Hibernate w/ JBC as 2nd level cache can potentially place instances of custom user classes in the cache. Can happen if the query cache is used, since instances of custom classes can be parameters to queries. This leads to replication or state transfer problems like the following if the custom classes are not visible to JBC's classloader (i.e. the custom classes aren't in server/all/lib). For regular entity caching, Hibernate stores primitives in the cache, so this is less of an issue. Problem is more with the query cache. java.lang.ClassNotFoundException: No ClassLoaders found for: services.entities.ProductDemandPK at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511) at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:585) at org.jboss.invocation.MarshalledValueInputStream.resolveClass(MarshalledValueInputStream.j ava:109) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.cache.Fqn.readExternal(Fqn.java:355) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.cache.loader.NodeData.readExternal(NodeData.java:59) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren( StateTransferIntegrator_140.java:241) at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren( StateTransferIntegrator_140.java:271) at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren( StateTransferIntegrator_140.java:271) at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateStateTransferChildren( StateTransferIntegrator_140.java:271) at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateTransientState(StateTr ansferIntegrator_140.java:222) at org.jboss.cache.statetransfer.StateTransferIntegrator_140.integrateTransientState(StateTr ansferIntegrator_140.java:97) at org.jboss.cache.TreeCache._setState(TreeCache.java:2640) at org.jboss.cache.TreeCache.access$000(TreeCache.java:86) at org.jboss.cache.TreeCache$MessageListenerAdaptor.setState(TreeCache.java:5306) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.passUp(MessageDispatcher.java:614) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:331) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:55 4) at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691) at java.lang.Thread.run(Thread.java:595) JBC's region-based marshalling API is meant for dealing with this kind of thing. Need to see how Hibernate can be configured to work with this API. Expect this will lead to JIRAs in the Hibernate and possible EBJ3 project. -- 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

18 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3415) Port RARDeployer

by Scott M Stark (JIRA)

Port RARDeployer ---------------- Key: JBAS-3415 URL: http://jira.jboss.com/jira/browse/JBAS-3415 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services, JCA service Reporter: Scott M Stark Assigned To: Weston Price Fix For: JBossAS-5.0.0.Beta The RARDeployer needs to be ported or rewritten for the new VDF -- 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

18 years, 3 months

5
15
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1009) Add configurale defaults on ServerPeer for FullSize, PageSize, and DownCacheSize

by Jay Howell (JIRA)

Add configurale defaults on ServerPeer for FullSize, PageSize, and DownCacheSize -------------------------------------------------------------------------------- Key: JBMESSAGING-1009 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1009 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.3.0.GA Reporter: Jay Howell Assigned To: Tim Fox Priority: Minor I see all the other defaults on the ServerPeer, but there seems to be no way to set the defaults for all the queues for the paging. I would ask that we add the following as properties on the serverpeer DefaultFullSize DefaultPageSize and Default DownCacheSize These constants should probably be taken out of org.jboss.jms.server.destination.ManagedDestination and put into the server peer as defaults. It would be ok to put these defaults in the Serverpeer as default values, but they need to be able to be overridden by default configuration settings. -- 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

18 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3836) Conditional setting of -server may not be supported on sun jdk1.3

by Dimitris Andreadis (JIRA)

Conditional setting of -server may not be supported on sun jdk1.3 ----------------------------------------------------------------- Key: JBAS-3836 URL: http://jira.jboss.com/jira/browse/JBAS-3836 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-3.2.8.SP2 The change in JBAS-3458 conditionally sets -server. Although sun jdk1.3 seems to support -server, it fails with: Unrecognized option: -server (although the forum post refers erroneously to 4.0.5, the error appears in the 3.2 branch, too). -- 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

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-720) Clips Parser

by Mark Proctor (JIRA)

Clips Parser ------------ Key: JBRULES-720 URL: http://jira.jboss.com/jira/browse/JBRULES-720 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 Clips Parser -- 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

18 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4571) local ant config upsets junit spawns in test build

by Andrew Dinn (JIRA)

local ant config upsets junit spawns in test build -------------------------------------------------- Key: JBAS-4571 URL: http://jira.jboss.com/jira/browse/JBAS-4571 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.1.GA Reporter: Andrew Dinn The build.sh script should insert --no_config into ANT_OPTIONS before invoking ant. Otherwise when the user has an ant.conf in $HOME/.ant or there is an ant.conf in /etc this can mess up the creation of junit tasks defined in build.xml -- 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

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4478) ignore local ant options when building

by Dennis Gregorovic (JIRA)

ignore local ant options when building -------------------------------------- Key: JBAS-4478 URL: http://jira.jboss.com/jira/browse/JBAS-4478 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.4.GA Reporter: Dennis Gregorovic Assigned To: Rajesh Rajasekaran Priority: Minor build/build.sh should use --noconfig when invoking Ant so that the local Ant libraries and configurations do not get picked up. -- 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

18 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-120) Add support for an LRU cache to CachingMetaDataContext

by Adrian Brock (JIRA)

Add support for an LRU cache to CachingMetaDataContext ------------------------------------------------------ Key: JBMICROCONT-120 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-120 Project: JBoss MicroContainer Issue Type: Feature Request Components: MetaData Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock The CachingMetaDataContext caches values indefinitely. Support for some kind of LRUCache (maybe across contexts) will help to relieve memory pressure when for example the metadata is actually only retrieved once and used at deployment. -- 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

18 years, 3 months

3
5
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 July 2007