neo4j 未修改jdbc驱动中的连接用户名与密码错识-优快云博客

本文记录了一次使用Neo4j JDBC驱动进行单元测试时遇到的失败情况，详细描述了启动Jetty服务器及测试过程中的错误信息，并分析了可能的原因在于未授权的资源异常。

Java代码  

cd C:\Users\cf\Documents\NetBeansProjects\neo4j_jdbc_driver; "JAVA_HOME=D:\\Program Files\\Java\\jdk1.8.0_25" cmd /c "\"\"D:\\Program Files\\NetBeans 8.0.2\\java\\maven\\bin\\mvn.bat\" -Dtest=org.neo4j.jdbc.Neo4jCaseStatementTest -Dmaven.ext.class.path=\"D:\\Program Files\\NetBeans 8.0.2\\java\\maven-nblib\\netbeans-eventspy.jar\" surefire:test\""
Running NetBeans Compile On Save execution. Phase execution is skipped and output directories of dependency projects (with Compile on Save turned on) will be used instead of their jar artifacts.
Scanning for projects...
------------------------------------------------------------------------
Building Neo4j JDBC Driver 2.2-SNAPSHOT
------------------------------------------------------------------------
--- maven-surefire-plugin:2.15:test (default-cli) @ neo4j-jdbc ---
Surefire report directory: C:\Users\cf\Documents\NetBeansProjects\neo4j_jdbc_driver\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.neo4j.jdbc.Neo4jCaseStatementTest
10:46:31.877 [main] INFO org.eclipse.jetty.util.log - Logging initialized @3430ms
10:46:32.049 [main] INFO org.eclipse.jetty.server.Server - jetty-9.2.4.v20141103
10:46:32.080 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.h.MovedContextHandler@1e1e9ef3{/,null,AVAILABLE}
五月 13, 2015 10:46:32 上午 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
信息: Initiating Jersey application, version 'Jersey: 1.18.1 02/19/2014 03:28 AM'
10:46:32.551 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@76e9f00b{/db/manage,null,AVAILABLE}
五月 13, 2015 10:46:32 上午 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
信息: Initiating Jersey application, version 'Jersey: 1.18.1 02/19/2014 03:28 AM'
10:46:32.692 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@20eaeaf8{/db/data,null,AVAILABLE}
10:46:32.755 [main] INFO o.e.j.w.StandardDescriptorProcessor - NO JSP Support for /browser, did not find org.apache.jasper.servlet.JspServlet
10:46:32.755 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.w.WebAppContext@4eaa375c{/browser,jar:file:/C:/Users/cf/.m2/repository/org/neo4j/app/neo4j-browser/2.2.1/neo4j-browser-2.2.1.jar!/browser,AVAILABLE}
五月 13, 2015 10:46:32 上午 com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
信息: Initiating Jersey application, version 'Jersey: 1.18.1 02/19/2014 03:28 AM'
10:46:32.849 [main] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2dbc408c{/,null,AVAILABLE}
10:46:32.880 [main] INFO o.e.jetty.server.ServerConnector - Started ServerConnector@4116f66a{HTTP/1.1}{localhost:7474}
10:46:32.880 [main] INFO org.eclipse.jetty.server.Server - Started @4712ms
Couldn't find any helper support the HTTP_None challenge scheme.
10:46:38.137 [main] INFO o.e.jetty.server.ServerConnector - Stopped ServerConnector@4116f66a{HTTP/1.1}{localhost:7474}
10:46:38.137 [main] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@2dbc408c{/,null,UNAVAILABLE}
10:46:38.137 [main] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.w.WebAppContext@4eaa375c{/browser,jar:file:/C:/Users/cf/.m2/repository/org/neo4j/app/neo4j-browser/2.2.1/neo4j-browser-2.2.1.jar!/browser,UNAVAILABLE}
10:46:38.137 [main] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@20eaeaf8{/db/data,null,UNAVAILABLE}
10:46:38.137 [main] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.ServletContextHandler@76e9f00b{/db/manage,null,UNAVAILABLE}
10:46:38.137 [main] INFO o.e.j.server.handler.ContextHandler - Stopped o.e.j.s.h.MovedContextHandler@1e1e9ef3{/,null,UNAVAILABLE}
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.829 sec <<< FAILURE! - in org.neo4j.jdbc.Neo4jCaseStatementTest
testExecuteStatement[0](org.neo4j.jdbc.Neo4jCaseStatementTest) Time elapsed: 0.016 sec <<< ERROR!
org.restlet.resource.ResourceException: Unauthorized
at org.restlet.resource.ClientResource.doError(ClientResource.java:599)
at org.restlet.resource.ClientResource.handleInbound(ClientResource.java:1165)
at org.restlet.resource.ClientResource.handle(ClientResource.java:1060)
at org.restlet.resource.ClientResource.handle(ClientResource.java:1035)
at org.restlet.resource.ClientResource.handle(ClientResource.java:937)
at org.restlet.resource.ClientResource.get(ClientResource.java:645)
at org.neo4j.jdbc.rest.Resources.readJsonFrom(Resources.java:144)
at org.neo4j.jdbc.rest.Resources$DiscoveryClientResource.readInformation(Resources.java:217)
at org.neo4j.jdbc.rest.Resources.getDiscoveryResource(Resources.java:102)
at org.neo4j.jdbc.Neo4jConnection.createExecutor(Neo4jConnection.java:133)
at org.neo4j.jdbc.Neo4jConnection.<init>(Neo4jConnection.java:81)
at org.neo4j.jdbc.Connections$4.doCreate(Connections.java:64)
at org.neo4j.jdbc.Connections.create(Connections.java:79)
at org.neo4j.jdbc.Driver.connect(Driver.java:76)
at org.neo4j.jdbc.Neo4jJdbcTest.connect(Neo4jJdbcTest.java:128)
at org.neo4j.jdbc.Neo4jJdbcTest.<init>(Neo4jJdbcTest.java:103)
at org.neo4j.jdbc.Neo4jCaseStatementTest.<init>(Neo4jCaseStatementTest.java:47)
Results :
Tests in error:
Neo4jCaseStatementTest.<init>:47->Neo4jJdbcTest.<init>:103->Neo4jJdbcTest.connect:128 ? Resource
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 11.837s
Finished at: Wed May 13 10:46:38 CST 2015
Final Memory: 10M/155M
------------------------------------------------------------------------
Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-cli) on project neo4j-jdbc: There are test failures.
Please refer to C:\Users\cf\Documents\NetBeansProjects\neo4j_jdbc_driver\target\surefire-reports for the individual test results.
-> [Help 1]
To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.
For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException