October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4874) Track JBoss and thirdparty dependencies for JBossAS 4.2.3

by Dimitris Andreadis (JIRA)

Track JBoss and thirdparty dependencies for JBossAS 4.2.3 --------------------------------------------------------- Key: JBAS-4874 URL: http://jira.jboss.com/jira/browse/JBAS-4874 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.3.GA Use subtasks to track component updates in AS 4.2.3.GA -- 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

16 years, 6 months

3
6
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

16 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4854) Duplicate Content-Type charset attribute causes exception

by Joni Niemi (JIRA)

Duplicate Content-Type charset attribute causes exception --------------------------------------------------------- Key: JBAS-4854 URL: http://jira.jboss.com/jira/browse/JBAS-4854 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Environment: Windows XP, JBOSS AS 4.2.1.GA Reporter: Joni Niemi Assigned To: Remy Maucherat New maemo Mozilla browser has a "feature" which sends duplicate charset parameter in the POST Content-type header. This causes following exception: java.io.UnsupportedEncodingException: UTF-8;charset=UTF-8 at java.lang.StringCoding.decode(StringCoding.java:170) at java.lang.String.<init>(String.java:444) at java.lang.String.<init>(String.java:516) at org.apache.catalina.connector.Request.setCharacterEncoding(Request.java:1469) at org.apache.catalina.connector.RequestFacade.setCharacterEncoding(RequestFacade.java:307) at com.sun.faces.context.ExternalContextImpl.setRequestCharacterEncoding(ExternalContextImpl.java:167) at javax.faces.application.ViewHandler.initView(ViewHandler.java:259) at org.ajax4jsf.application.ViewHandlerWrapper.initView(ViewHandlerWrapper.java:138) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:208) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at com.jamonapi.http.JAMonTomcatValve.invoke(JAMonTomcatValve.java:72) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419) at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:393) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1513) at java.lang.Thread.run(Thread.java:619) The erraneous* Content-Type header causing this is "Content-Type: application/x-www-form-urlencoded; charset=UTF-8;charset=UTF-8" ("User-agent: Mozilla/5.0 (X11; U; Linux armv6l; en-GB; rv:1.9a6pre) Gecko/20070810 Firefox/3.0a1 Tablet browser 0.1.16 RX-34_2007SE_4.2007.38-2") Windows version of Mozilla causes no problems: "Content-Type: application/x-www-form-urlencoded; charset=UTF-8" (User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fi; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0" * I don't think RFC2616 strictly speakings prohibits duplicate attributes. This seems to be Catalina issue, but I don't know which version JBOSS AS 4.2.1.GA is using, so I'm submitting this here. -- 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

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4876) Re-enable JGroups message bundling

by Brian Stansberry (JIRA)

Re-enable JGroups message bundling ---------------------------------- Key: JBAS-4876 URL: http://jira.jboss.com/jira/browse/JBAS-4876 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.3.GA For 4.2.0 JGroups message bundling was disabled pending investigation of JGRP-497. That is fixed in JGroups 2.4.1.SP4. Message bundling improves performance, so we should re-enable it. -- 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

16 years, 6 months

2
2
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

16 years, 6 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

16 years, 6 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

16 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4877) Upgrade JSF to 1.2_05

by Frank Langelage (JIRA)

Upgrade JSF to 1.2_05 --------------------- Key: JBAS-4877 URL: http://jira.jboss.com/jira/browse/JBAS-4877 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Frank Langelage JSF 1.2_05 is out for a few days. Upgrade to this from 1.2_04_P02. -- 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

16 years, 6 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4933) Upgrade to jbossxb 1.0.0.SP2 (from 1.0.0.SP1)

by Dimitris Andreadis (JIRA)

Upgrade to jbossxb 1.0.0.SP2 (from 1.0.0.SP1) --------------------------------------------- Key: JBAS-4933 URL: http://jira.jboss.com/jira/browse/JBAS-4933 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: XML services Affects Versions: JBossAS-4.2.2.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.3.GA Needed for fixing JBXB-115 (and anything else that pops 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

16 years, 6 months

2
3
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

16 years, 6 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007