History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-1051
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Ronald Brindl
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Getting latest buid via REST does not work anymore

Created: 22/Sep/11 04:54 PM   Updated: 04/Oct/11 03:43 PM
Component/s: None
Affects Version/s: 3.1.59
Fix Version/s: 4.0.0-M3, 3.1.60, 4.0.0

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
since recently, i get the following errormessage:
{code}
$ curl -v "http://buildmaster2:8810/rest/latest_builds/17532"
* About to connect() to buildmaster2 port 8810 (#0)
* Trying 192.168.16.220... connected
* Connected to buildmaster2 (192.168.16.220) port 8810 (#0)
> GET /rest/latest_builds/17532 HTTP/1.1
> User-Agent: curl/7.20.1 (i686-pc-cygwin) libcurl/7.20.1 OpenSSL/0.9.8r zlib/1.2.5 libidn/1.18 libssh2/1.2.5
> Host: buildmaster2:8810
> Accept: */*
>
< HTTP/1.1 500 Internal Server Error
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Set-Cookie: JSESSIONID_8810=131jy8tcrack9;Path=/
< Content-Type: text/plain
< Transfer-Encoding: chunked
< Server: Jetty(6.1.x)
<
* Connection #0 to host buildmaster2 left intact
* Closing connection #0
The validated object is null
{code}

I also tried using a user with -u (using Basic Authentication) flag to curl, did not work either.
How can i access this again?



 All   Comments   Work Log   Change History      Sort Order:
Ronald Brindl [22/Sep/11 05:01 PM]
Do I need admin privileges for this?
when i enter above url in my browser, i get:

HTTP ERROR 500

Problem accessing /rest/latest_builds/17532. Reason:

    User not found or password incorrect.

Caused by:

com.pmease.quickbuild.AuthenticationException: User not found or password incorrect.
at com.pmease.quickbuild.security.SecurityHelper.authenticate(SecurityHelper.java:292)
at com.pmease.quickbuild.security.SecurityHelper.authenticate(SecurityHelper.java:449)
at com.pmease.quickbuild.rest.RestServlet.service(RestServlet.java:41)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at com.pmease.quickbuild.web.HttpServiceProvider$1$1.service(HttpServiceProvider.java:86)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:865)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:540)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:213)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)


Ronald Brindl [22/Sep/11 05:07 PM]
The Problem was something different (a strange coincident, which led me into the wrong direction):

This problem does not occur with all configs, but only with those that do not have builds. I copied a config with several sub configs shortly after we upgraded yesterday, which led to the misunderstanding.

But this is still a problem, i do not want to get an Error 500 just because there are no builds.

Severity should be reduced.

Thank you...

Robin Shen [23/Sep/11 12:21 AM]
Next patch release will return http status code 204 (no content) upon this.