June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4246) JBoss logo not displayed for web status when accessed from web console

by Stephen Burdeau (JIRA)

JBoss logo not displayed for web status when accessed from web console ---------------------------------------------------------------------- Key: JBAS-4246 URL: http://jira.jboss.com/jira/browse/JBAS-4246 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.0.5.GA Environment: Found on Windows XP; should exist everywhere. Reporter: Stephen Burdeau Assigned To: Darran Lofthouse This is a minor issue to be sure. Run web console and navigate to Monitoring - Web Status - Connector scoreboard in the left frame. The right frame displays the Tomcat status, but it does not include the JBoss logo on the top and it does not use the JBoss style sheet. Navigating to Monitoring - Web Status - Full status also shows the same problem. When accessing the same Tomcat status pages from the main page (e.g., http://localhost:8080), this problem does not occur. It appears that logo.gif and jboss.css are located in the "root" directory for Tomcat. However, for the web console, logo.gif is located in the "images" subdirectory and jboss.css is located in the "css" subdirectory, so they are not found when using the web console. An easy workaround is to copy the files logo.gif and jboss.css into the directory deploy/management/console-mgr.sar/web-console.war. -- 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
7
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: (JBMICROCONT-179) VFS caches old jar files

by Carlo de Wolf (JIRA)

VFS caches old jar files ------------------------ Key: JBMICROCONT-179 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-179 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Reporter: Carlo de Wolf Priority: Critical New jar files are not being picked up by VFS. Somehow the cached ones -- 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

6
15
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-164) JarEntry as VFS root does not return empty vfspath

by Bill Burke (JIRA)

JarEntry as VFS root does not return empty vfspath -------------------------------------------------- Key: JBMICROCONT-164 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-164 Project: JBoss MicroContainer Issue Type: Bug Components: VFS Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Bill Burke Fix For: JBossMC_2_0_0_CR1 There's a test already in SVN. Just don't know how to fix cleanly at the moment: JARVFSContextUnitTestCase.testPathIsEmptryForJarEntryAsRoot -- 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
11
0 / 0

[JBoss JIRA] Created: (JBAS-4156) [jmx-console] Add additional informatin to page header

by Kenny MacLeod (JIRA)

[jmx-console] Add additional informatin to page header ------------------------------------------------------ Key: JBAS-4156 URL: http://jira.jboss.com/jira/browse/JBAS-4156 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX, Web Console Affects Versions: JBossAS-4.0.4.GA Reporter: Kenny MacLeod Assigned To: Dimitris Andreadis Priority: Trivial The main page of the jmx-console currently displays the hostname of the localhost. In cases where multiple jboss instances are running on a single host, this isn't particularly useful. I'd like to request that as well as the hostname, it also displays the hostname of the IP address to which the jboss instance is bound. -- 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

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-4388) Place all management web applications, web invokers, etc under a common context root

by Jeff Schnitzer (JIRA)

Place all management web applications, web invokers, etc under a common context root ------------------------------------------------------------------------------------ Key: JBAS-4388 URL: http://jira.jboss.com/jira/browse/JBAS-4388 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Reporter: Jeff Schnitzer Assigned To: Darran Lofthouse In any enterprise environment, administrative interfaces are blocked from the public even if they require a password; administrative interfaces can only be accessed through the internal network or a SSL-secured VPN. This means the load balancer (or whatever) must block out all the possible management/invocation web apps: /jmx-console /web-console /invoker /jbossmq-httpil These paths sometimes change between JBoss versions without any significant announcement, plus services are occasionally added. This could easily result in unsecured or poorly secured (basic auth) services exposed to the public. Please put all JBoss-provided webapps under a base context that can easily be blocked to the public: /jboss/jmx-console /jboss/web-console /jboss/invoker /jboss/jbossmq-httpil -- 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
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-820) Hardcoded Destination Manager Reference

by Juha Lindfors (JIRA)

Hardcoded Destination Manager Reference --------------------------------------- Key: EJBTHREE-820 URL: http://jira.jboss.com/jira/browse/EJBTHREE-820 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: JBoss AS 4.0.5.GA + EJB 3.0 RC9 + JBoss Messaging Reporter: Juha Lindfors Priority: Minor When deploying an MDB that has been configured wrongly with a non existing destination the dubious feature that creates a temporary destination automatically fails due to hard coded destination manager reference that no longer exists if JBoss Messaging is used instead of JBossMQ. MessagingContainer: protected void createTemporaryDestination(Class type, String jndiSuffix) throws Exception 513 ObjectName destinationManagerName = new ObjectName("jboss.mq:service=DestinationManager"); Apologies, did not check if this issue exists still with the current code in the head/trunk, just needed to write it down before I forget 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

18 years, 1 month

2
2
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: (JBRULES-687) General purpose BRMS query functionality

by Michael Neale (JIRA)

General purpose BRMS query functionality ---------------------------------------- Key: JBRULES-687 URL: http://jira.jboss.com/jira/browse/JBRULES-687 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

1
4
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 June 2007