October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1097) InitialContextFactory doesn't always create a new InitialContext

by Carlo de Wolf (JIRA)

InitialContextFactory doesn't always create a new InitialContext ---------------------------------------------------------------- Key: EJBTHREE-1097 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1097 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Carlo de Wolf InitialContextFactory is not really a factory, it doesn't always create a new InitialContext. This can lead to interesting situations if someone closes an InitialContext which doesn't have any properties and then tries to reuse 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

17 years, 11 months

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

17 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAOP-461) Resolve outstanding issues on Linux

by Kabir Khan (JIRA)

Resolve outstanding issues on Linux ----------------------------------- Key: JBAOP-461 URL: http://jira.jboss.com/jira/browse/JBAOP-461 Project: JBoss AOP Issue Type: Sub-task Reporter: Kabir Khan -- 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

17 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1018) ClassCastException on concurrent EJB3 method invocation from different beans

by Michael Pfeiffer (JIRA)

ClassCastException on concurrent EJB3 method invocation from different beans ---------------------------------------------------------------------------- Key: EJBTHREE-1018 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1018 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA, AS 4.2.0 GA Environment: Java: JDK 1.5.0_11 Eclipse: SDK 3.2.2 Reporter: Michael Pfeiffer Two different EJB3 stateless session beans A and B packaged into separate EAR files deployed on the same JBoss instance invoke a method of another stateless session bean C on another JBoss instance that returns an object of a user defined class Value. There seems to be a multi-threading issue. Sometimes when both beans concurrently call the method of C an ClassCastException Value is thrown within the remote interface proxy before the result object is returned to the calling bean. The class Value and the remote interface for C are packaged into a JAR file within each EAR file inside a "lib" folder. If this JAR file is deployed instead and not packaged into the EAR files of bean A and B 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

17 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4621) error deploying admin-consoles in deploy is a link

by davide pasinato (JIRA)

error deploying admin-consoles in deploy is a link -------------------------------------------------- Key: JBAS-4621 URL: http://jira.jboss.com/jira/browse/JBAS-4621 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.2.1.GA Environment: linux RH-4 Sun jdk 1.5 jboss 4.2.1 server: all with jbossws-2.0.1 Reporter: davide pasinato Assigned To: Darran Lofthouse Priority: Minor I have a cluster of two jboss 4.2.1 servers. They run on the same machine. For this reason the server B links the directories deploy and lib of the server A when I start server A everything run smoothly. When I start server B I get an exception deploying the administration consoles. Looks like the directory management doesnt like symbolic links. This is the exception I get on server B (the root directory of server B is /var/opt/jboss/stress1b): org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@e5f0d2 on mbean jboss.admin:service=DeploymentFileRepository; - nested throwable: (java.lang.IllegalArgumentException: child './deploy/management' should be a child of parent '/var/opt/jboss/stress1b') at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698) at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:460) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) at org.jboss.system.ServiceController.install(ServiceController.java:226) 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.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.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) 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 $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.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) at sun.reflect.GeneratedMethodAccessor10.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:508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: child './deploy/management' should be a child of parent '/var/opt/jboss/stress1b' at org.jboss.console.manager.DeploymentFileRepository.getFile(DeploymentFileRepository.java:151) at org.jboss.console.manager.DeploymentFileRepository.setBaseDir(DeploymentFileRepository.java:124) 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.AttributeDispatcher.invoke(AttributeDispatcher.java:136) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:103) at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:608) at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:694) ... 84 more -- 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

17 years, 11 months

4
6
0 / 0

[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

17 years, 11 months

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

17 years, 11 months

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

17 years, 11 months

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

17 years, 11 months

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

17 years, 11 months

5
10
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 October 2007