You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/05/02 14:42:55 UTC
[jira] Commented: (QPID-997) AMQBrokerManagerMBeanTest takes more
than 60seconds to run
[ https://issues.apache.org/jira/browse/QPID-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593764#action_12593764 ]
Martin Ritchie commented on QPID-997:
-------------------------------------
Ah, realise now was looking at the old log files.
As we've seen before this is due to the log4j trying to download a DTD but not using my proxy server.
Testsuite: org.apache.qpid.server.AMQBrokerManagerMBeanTest
Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 50.829 sec
------------- Standard Error -----------------
log4j:ERROR Could not parse url [file://C:/dev/ApacheProjects/Qpid-clean/trunk/qpid/java/log4j-test.xml].
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.NetworkClient.openServer(NetworkClient.java:118)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:488)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:475)
at sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.java:270)
at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:352)
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.XML11Configuration.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:180)
at org.apache.log4j.xml.DOMConfigurator$2.parse(DOMConfigurator.java:612)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:711)
at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
at org.apache.log4j.Logger.getLogger(Logger.java:117)
at org.apache.qpid.server.registry.ApplicationRegistry.<clinit>(ApplicationRegistry.java:39)
at org.apache.qpid.server.AMQBrokerManagerMBeanTest.setUp(AMQBrokerManagerMBeanTest.java:88)
at junit.framework.TestCase.runBare(TestCase.java:128)
> AMQBrokerManagerMBeanTest takes more than 60seconds to run
> ----------------------------------------------------------
>
> Key: QPID-997
> URL: https://issues.apache.org/jira/browse/QPID-997
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Reporter: Martin Ritchie
>
> Summary:
> The AMQBrokerManagerMBeanTest takes more tha 60 seconds to run tends to suggest an error has occurred but no problems are logged out.
> [junit] Running org.apache.qpid.server.AMQBrokerManagerMBeanTest
> [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 68.658 sec
> surefire report:
> $ cat org.apache.qpid.server.AMQBrokerManagerMBeanTest.txt
> -------------------------------------------------------------------------------
> Test set: org.apache.qpid.server.AMQBrokerManagerMBeanTest
> -------------------------------------------------------------------------------
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.