November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-816) Create a CacheProxy to allow cache replication across WANs

by Manik Surtani (JIRA)

Create a CacheProxy to allow cache replication across WANs ---------------------------------------------------------- Key: JBCACHE-816 URL: http://jira.jboss.com/jira/browse/JBCACHE-816 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.3.0 This has to do with multiple JBoss Cache clusters deployed on LANs as islands, requiring a bridge between such islands. An ideal use case is where a cluster spans multiple data centres and would need to replicate across a WAN. The ideal strategy would be to allow for async bridging, since most calls would be colocated to a single LAN, but may fail over to a remote LAN (pretty much the same idea of async repl within a LAN, except that now we treat an entire LAN as a host. Sort of a meta-cluster). For more details and some brainstorming ideas, see: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres -- 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, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-711) Replication eats out exception on the remote node

by Ben Wang (JIRA)

Replication eats out exception on the remote node ------------------------------------------------- Key: JBCACHE-711 URL: http://jira.jboss.com/jira/browse/JBCACHE-711 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0 Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.0.0 I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication. When the remote node throws an exception like NPE, the originating node will display with NonSerializableException. I don't a unit test for this but I think it should be easy to reproduce. 21:51:32,490 INFO [TxInterceptor] There was a problem handling this request java.io.NotSerializableException: RpcDispatcher returned a null. This is most often caused by args for _replicate(_put(null, /testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean, org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable. at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166) at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113) at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88) at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114) at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException

by Anil Saldhana (JIRA)

Redeploy of Tomcat5 Service chokes with RuntimeException -------------------------------------------------------- Key: JBAS-3517 URL: http://jira.jboss.com/jira/browse/JBAS-3517 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens. You will notice the following Runtime Exception and the tomcat service fails to deploy. ============================================================================================== 13:33:30,421 INFO [Catalina] Initialization processed in 562 ms 13:33:30,421 INFO [StandardService] Starting service jboss.web 13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1 7 13:33:30,453 INFO [StandardHost] XML validation disabled 13:33:30,468 INFO [Catalina] Server startup in 47 ms 13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185) at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) =================================================================================== Use the following api of PolicyContext in Tomcat5 service http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h... -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3527) Tomcat 6 fixes needed for JSF

by Stan Silvert (JIRA)

Tomcat 6 fixes needed for JSF ----------------------------- Key: JBAS-3527 URL: http://jira.jboss.com/jira/browse/JBAS-3527 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta Reporter: Stan Silvert Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.GA This JIRA task is for tracking the Tomcat 6 bugs that need to be fixed for JSF in JBoss AS 5.0.0 http://issues.apache.org/bugzilla/show_bug.cgi?id=39803 http://issues.apache.org/bugzilla/show_bug.cgi?id=39805 http://issues.apache.org/bugzilla/show_bug.cgi?id=40279 We have a workaround for this one, but it would be nice if it were fixed: http://issues.apache.org/bugzilla/show_bug.cgi?id=39804 -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-3775) org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly

by David Kilzer (JIRA)

org.jboss.net.protocol.file.FileURLConnection does not handle opening InputStreams to UNC paths properly -------------------------------------------------------------------------------------------------------- Key: JBAS-3775 URL: http://jira.jboss.com/jira/browse/JBAS-3775 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.2 Final Environment: Microsoft Windows XP [Version 5.1.2600] java version "1.5.0_07" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode) Xerces-J 2.6.2 Reporter: David Kilzer Attempting to parse a document using Xerces-J 2.6.2 by passing in a java.io.File object containing a UNC path fails when run under JBossAS 4.0.2 Final, but works fine when run outside of JBoss. The particular code run under JBoss was started through a Spring-1.2.8-controlled Quartz-1.4.5 job (all deployed within a WAR within an EAR), but the stack trace clearly shows that org.jboss.net.protocol.file.FileURLConnection is the culprit (file path changed to protect the innocent): java.io.FileNotFoundException: \c$\path\to\file.xml at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:80) at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:89) at java.net.URL.openStream(URL.java:1007) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172) [...] Here is some sample code that should reproduce the issue. Note the path used to create the java.io.File object. File xmlFile = new File("\\\\127.0.0.1\\c$\\path\\to\\file.xml"): DocumentBuilderFactory factory = new org.apache.xerces.jaxp.DocumentBuilderFactoryImpl(); factory.setNamespaceAware(false); factory.setValidating(false); DocumentBuilder builder = factory.newDocumentBuilder(); Document document = builder.parse(xmlFile); // exception thrown under JBossAS The FileURLConnection class is loaded from jboss-4.0.2/client/jboss-common-client.jar. -- 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, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-983) Upload of large files fails.

by Peter Johnson (JIRA)

Upload of large files fails. ---------------------------- Key: JBPORTAL-983 URL: http://jira.jboss.com/jira/browse/JBPORTAL-983 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: Windows XP, JDK 1.5, JBoss AS 4.0.4GA Reporter: Peter Johnson Fix For: 2.4 Final Using the CMS Admin portlet, I attempted to upload a zip file into a directory, as per section 3.2.9 of the User Guide. Initially I tried a zip ofabout 6MB containing many files, and eventually got down to a a zip file of about 500M with only a single Word document inside. The upload failed and an "SQLException: could not reset reader" error appeared (see forum post for stack trace). I am, however, able to upload very small zip files. -- 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, 1 month

8
23
0 / 0

[JBoss JIRA] Created: (JBAS-3402) Web Console and Firefox

by Vladimir Gendler (JIRA)

Web Console and Firefox ----------------------- Key: JBAS-3402 URL: http://jira.jboss.com/jira/browse/JBAS-3402 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Affects Versions: JBossAS-4.0.4.GA Environment: MS W2000 SP4 Reporter: Vladimir Gendler Assigned To: Dimitris Andreadis Web Console output in Mozilla Firefox (and Seamonkey) is messed up. Compare the attached archive with snapshots from Mozilla Firefox and MSIE. -- 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, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-746) Ascertain whether any methods and attributes exposed by TreeCacheMBean can be marked serializable

by Jerry Gauthier (JIRA)

Ascertain whether any methods and attributes exposed by TreeCacheMBean can be marked serializable ------------------------------------------------------------------------------------------------- Key: JBCACHE-746 URL: http://jira.jboss.com/jira/browse/JBCACHE-746 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jerry Gauthier Assigned To: Jerry Gauthier Priority: Minor When TreeCacheMBean is accessed remotely via an mbean server such as jconsole, numerous attributes and methods are marked as problematic because they aren't serializable. While many are undoubtedly not serializable, it's worth reviewing the list to see if it would be appropriate to mark any additional attributes or method parameters as serializable. -- 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, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-633) Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase

by Ron Sigal (JIRA)

Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase ------------------------------------------------------------------------------------------------------- Key: JBREM-633 URL: http://jira.jboss.com/jira/browse/JBREM-633 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Occurred on 11/4/06 and 11/5/06 for jdk 1.4. -- 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
8
0 / 0

[JBoss JIRA] Created: (JBREM-628) Find source of EOFException in multiplex unit tests on cruisecontrol.

by Ron Sigal (JIRA)

Find source of EOFException in multiplex unit tests on cruisecontrol. --------------------------------------------------------------------- Key: JBREM-628 URL: http://jira.jboss.com/jira/browse/JBREM-628 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Some multiplex unit tests, seemingly at random, are failing with EOFException. E.g., org.org.jboss.test.remoting.transport.multiplex.config.ConfigurationByMapDiffStaticObjectsTestServer. -- 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
8
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 November 2006