Bug 1401565
| Summary: | Attempt to navigate to REST interface while server is not still started causes NullPointerException in the server.log file | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> |
| Component: | Core Server, REST | Assignee: | Ruben Vargas Palma <rvargasp> |
| Status: | CLOSED ERRATA | QA Contact: | Jeeva Kandasamy <jkandasa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | JON 3.3.6 | CC: | fbrychta, jkandasa, rvargasp, spinder |
| Target Milestone: | CR01 | Keywords: | Triaged |
| Target Release: | JON 3.3.9 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-10-02 17:21:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1401568 | ||
| Bug Blocks: | |||
|
Description
bkramer
2016-12-05 15:04:22 UTC
Moving to ON_QA. JON 3.3.9 CR01 artifacts are available for test from here: http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/135/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip *Note: jon-server-patch-3.3.0.GA.zip maps to CR01 build of jon-server-3.3.0.GA-update-09.zip. I do not see any error log in the server.log file. but I see the response message as "Tried to call REST endpoint but the server is not ready - still booting up" with error code "503 - Service unavailable". Version info: ------------- Server OS: RHEL 7.4 64 bit JBoss Operations Network Version: 3.3.0.GA Update 09 Build Number: 44ba698:204e925 GWT Version: 2.5.0 SmartGWT Version: 3.0p Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2846 |