November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-523) Implement topic hierarchies

by Tim Fox (JIRA)

Implement topic hierarchies --------------------------- Key: JBMESSAGING-523 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-523 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Implement topic hierarchies so a subscription can subscribe to a wildcard, e.g. news.* and will receive all messages sent to topics news.uk, news.usa, news.usa.local etc etc -- 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

15 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (JBAS-4012) ClassLoaderUtils recurses into .war directories

by David (JIRA)

ClassLoaderUtils recurses into .war directories ----------------------------------------------- Key: JBAS-4012 URL: http://jira.jboss.com/jira/browse/JBAS-4012 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-4.0.5.GA Environment: windows xp, java 1.5.0_09 Reporter: David Assigned To: Scott M Stark Priority: Minor ClassLoaderUtils has logic that is supposed to prevent indexing/scanning of .war directories. This was an issue fixed earlier in 3.2.6, reported in a support case: 00002351 The following patch is also needed in order to fully prevent indexing in .war directories: $ diff -u src/org/jboss/mx/loading/ClassLoaderUtils.java /khub/opensource/jboss-4.0.5.GA-src/jmx/src/main/org/jboss/mx/loading/ClassLoaderUtils.java --- src/org/jboss/mx/loading/ClassLoaderUtils.java 2007-01-24 14:27:27.607071000 -0500 +++ /khub/opensource/jboss-4.0.5.GA-src/jmx/src/main/org/jboss/mx/loading/ClassLoaderUtils.java 2006-10-16 23:37:24.000000000 -0400 @@ -472,27 +472,21 @@ String name = start.getName(); // Don't recurse into wars boolean isWar = name.endsWith(".war"); - if( isWar ) { - log.trace("war, not recursing"); + if( isWar ) currentListing = new File[0]; - } - else { + else currentListing = start.listFiles(); - } } FileIterator(File start, FileFilter filter) { String name = start.getName(); // Don't recurse into wars boolean isWar = name.endsWith(".war"); - if( isWar ) { - log.trace("war, not recursing"); + if( isWar ) currentListing = new File[0]; - } - else { + else currentListing = start.listFiles(filter); - this.filter = filter; - } + this.filter = filter; } File getNextEntry() @@ -503,13 +497,7 @@ do { File nextDir = (File) subDirectories.removeFirst(); - if (nextDir.getName().endsWith(".war")) { - log.trace("war, not recursing"); - currentListing = new File[0]; - } - else { - currentListing = nextDir.listFiles(filter); - } + currentListing = nextDir.listFiles(filter); } while( currentListing.length == 0 && subDirectories.size() > 0 ); index = 0; } The stack trace during startup is here: "main" prio=6 tid=0x1bcadc70 nid=0xec4 runnable [0x1c02e000..0x1c02fb18] at java.io.WinNTFileSystem.list(Native Method) at java.io.File.list(File.java:937) at java.io.File.listFiles(File.java:1093) at org.jboss.mx.loading.ClassLoaderUtils$FileIterator.getNextEntry(ClassLoaderUtils.java:500) at org.jboss.mx.loading.ClassLoaderUtils$ClassPathIterator.getNextEntry(ClassLoaderUtils.java:617) at org.jboss.mx.loading.ClassLoaderUtils.updatePackageMap(ClassLoaderUtils.java:319) at org.jboss.mx.loading.ClassLoaderUtils.updatePackageMap(ClassLoaderUtils.java:253) at org.jboss.mx.loading.UnifiedLoaderRepository3.updatePackageMap(UnifiedLoaderRepository3.java:783) at org.jboss.mx.loading.UnifiedLoaderRepository3.addRepositoryClassLoader(UnifiedLoaderRepository3.java:740) - locked <0x07aafcf0> (a EDU.oswego.cs.dl.util.concurrent.CopyOnWriteArraySet) at org.jboss.mx.loading.UnifiedLoaderRepository3.addClassLoader(UnifiedLoaderRepository3.java:662) at org.jboss.mx.loading.UnifiedLoaderRepository3.registerClassLoader(UnifiedLoaderRepository3.java:946) at org.jboss.mx.loading.UnifiedLoaderRepository3.newClassLoader(UnifiedLoaderRepository3.java:168) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.deployment.DeploymentInfo.createClassLoaders(DeploymentInfo.java:280) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:874) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) - locked <0x07e0e0d8> (a org.jboss.deployment.scanner.URLDeploymentScanner) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) - locked <0x07ec9400> (a org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) - locked <0x07af6660> (a org.jboss.system.ServiceController) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:595) with trace logging on you see: -- 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

15 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-340) Major overhaul of GossipRouter

by Bela Ban (JIRA)

Major overhaul of GossipRouter ------------------------------ Key: JGRP-340 URL: http://jira.jboss.com/jira/browse/JGRP-340 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 Things to be done: - Use of Streamable rather than Externalizable - Currently we use 1 thread per request rather than a thread pool, e.g. Executor ! - Better logging and diagnostics (JMX) -- 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

15 years, 7 months

2
18
0 / 0

[JBoss JIRA] Created: (JBBUILD-367) Research using install and site with multi module project.

by Paul Gier (JIRA)

Research using install and site with multi module project. ---------------------------------------------------------- Key: JBBUILD-367 URL: http://jira.jboss.com/jira/browse/JBBUILD-367 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier JBoss rules is having some problems when running install and site:site when there is an empty repository. A small multimodule project should be created to test this behavior. -- 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

15 years, 7 months

1
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-413) Mavenize remoting project

by Paul Gier (JIRA)

Mavenize remoting project ------------------------- Key: JBBUILD-413 URL: http://jira.jboss.com/jira/browse/JBBUILD-413 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Remoting project needs to be properly mavenized so that app server builds can use 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

15 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1511) Renaissance theme should use em instead of px CSS units anywhere possible and avoid defining absolute font size.

by Chris Laprun (JIRA)

Renaissance theme should use em instead of px CSS units anywhere possible and avoid defining absolute font size. ---------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1511 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1511 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Julien Viet Priority: Minor Fix For: 2.6.1 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

15 years, 7 months

5
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-794) NotSerializableException from LdapLoginModule/AD

by Darren Hartford (JIRA)

NotSerializableException from LdapLoginModule/AD ------------------------------------------------ Key: EJBTHREE-794 URL: http://jira.jboss.com/jira/browse/EJBTHREE-794 Project: EJB 3.0 Issue Type: Bug Environment: jboss 4.0.5.GA/JEMS install, Win2000, ActiveDirectory Reporter: Darren Hartford "java.io.NotSerializableException: com.sun.jndi.ldap.LdapCtx" When incorrect credentials are passed from the client, the server swallows with NotSerializableException and the client does not get correct feedback. Test environment was login-config.xml with org.jboss.security.auth.spi.LdapLoginModule talking to an ActiveDirectory server. Note that when correct credentials are passed, everything works fine. -- 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

15 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1131) Add configuration for Remoting servlet transport

by Ron Sigal (JIRA)

Add configuration for Remoting servlet transport ------------------------------------------------ Key: JBMESSAGING-1131 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131 Project: JBoss Messaging Issue Type: Task Reporter: Ron Sigal Assigned To: Tim Fox Fix For: 2.0.0 Alpha In addition to the "http" transport, Remoting also has the http-based "servlet" transport. The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side. In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads. But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850 and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used. In principle, it's the appropriate transport to use when the server is running inside JBossAS. In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet. However, there have been a couple of problems. For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker"). However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. -- 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

15 years, 7 months

8
46
0 / 0

[JBoss JIRA] Created: (JBFORUMS-164) lastPostDate must be persisted in database

by Ryszard Kozmik (JIRA)

lastPostDate must be persisted in database ------------------------------------------ Key: JBFORUMS-164 URL: http://jira.jboss.com/jira/browse/JBFORUMS-164 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha Forums are not efficient mainly because of this very big problem of their module and database schema. There is no place to keep lastPostDates so they have to be generated each time what takes big amounts of time as those are very timetaking sql queries. This is main performance killer at this point. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-249) Make Forums compatible with Portal URLMapper

by Ryszard Kozmik (JIRA)

Make Forums compatible with Portal URLMapper -------------------------------------------- Key: JBFORUMS-249 URL: http://jira.jboss.com/jira/browse/JBFORUMS-249 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements, Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC It is now impossible to overwrite url parameter names of Forums by Portal URLMapper and it should be. -- 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

15 years, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007