This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 090414 ] [ JDK VERSION : 1.6.* ] After importing the settings from 6.5(.1) two different JBoss app servers registered in the Service tab. During startup the following exception is logged 14 times (servers are not running): INFO [org.netbeans.ProxyClassLoader] java.lang.IllegalStateException: You are trying to access file: log4j.xml from the default package. Please see http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/o penide/modules/doc-files/classpath.html#default_package at org.netbeans.ProxyClassLoader.printDefaultPackageWarning(ProxyClassLoa der.java:576) at org.netbeans.ProxyClassLoader.getResource(ProxyClassLoader.java:343) at java.lang.ClassLoader.getResource(ClassLoader.java:973) at org.apache.log4j.helpers.Loader.getResource(Loader.java:109) at org.apache.log4j.LogManager.<clinit>(LogManager.java:103) at org.jboss.logging.log4j.Log4jLoggerPlugin.init(Log4jLoggerPlugin.java: 70) at org.jboss.logging.Logger.getDelegatePlugin(Logger.java:393) at org.jboss.logging.Logger.<init>(Logger.java:119) at org.jboss.logging.Logger.getLogger(Logger.java:357) at org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:177) at org.jnp.interfaces.NamingContextFactory.getInitialContext(NamingContex tFactory.java:55) at org.jboss.naming.NamingContextFactory.getInitialContext(NamingContextF actory.java:49) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:66 7) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at org.netbeans.modules.j2ee.jboss4.JBDeploymentManager.getRMIServer(JBDe ploymentManager.java:177) at org.netbeans.modules.j2ee.jboss4.JBDeploymentManager.refreshRMIServer( JBDeploymentManager.java:223) at org.netbeans.modules.j2ee.jboss4.nodes.Util.getMBeanParameter(Util.jav a:212) at org.netbeans.modules.j2ee.jboss4.ide.JBStartServer$1.run(JBStartServer .java:236) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:573) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java: 1005) The only log4j.xml file I am aware of is the log4j.xml located in <jboss-install-dir>/server/<domain>/conf. This is the standard location and as there is nothing wrong with that no exception should be reported. Moreover this exceptions shows that the same activity is performed over and over again. Maybe there is an opportunity to reduce the startup time.
[Note aside: the text area in the simplified 67cat submit form should have the same width as this one to avoid this ugly line wrapping...].
If you downgrade the priority of a bug report, please add comment stating the reason.
Not a bug basically - just exception in log.
If you log an exception it indicates to the user that something seriously is wrong which needs investigation. Otherwise there is no point in printing the stack trace. You as the developer may know that the exception is harmless, but the user not. If you are crying fire for no reason it will become hard to decide if actually something is burning. Especially if you spam the output window 14 times with the same stack trace... So I suggest to just log an information or warning message, but not the exception.
I don't think there is any disagreement - just severity is P4. BTW I'm not logging the exception. It is org.netbeans.ProxyClassLoader which is not a thing you should change on will. The warning is caused by log4j that is invoked by jboss code that is invoked by the server plugin code (so my code is not the cause and there is no way how this could be fixed in my code).
Ok, thanks for the explanation (and your patience).
Created attachment 103005 [details] error message log