Opened 9 years ago
Closed 9 years ago
#996 closed defect (fixed)
Jetty does not start when rasdaman is configured with --with-wardir
| Reported by: | Alex Toader | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | undecided | Version: | development |
| Keywords: | Cc: | ||
| Complexity: | Easy |
Description
When rasdaman is configured with —with-wardir, Jetty fails to start.
Change History (3)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 9 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
When I first did this task, I used @wardir@ in start_rasdaman.sh.in so as you can see if use choose wardir is /var/lib/tomcat/wardir then it could not start because Jetty is installed in $RMANHOME/share/rasdaman/war.
From now, it will depend on configPath=@sysconfdir@; so it will belonged to wardir anymore (even if you set wardir to any directory). My latest patch for ticket 960 has already done for this. Thanks for your repoting, I will close this ticket in here.
Note:
See TracTickets
for help on using tickets.
When upgrade to using Jetty, there will be no Tomcat anymore, so user don't have to specific the "wardir" of Petascope when install Rasdaman again. So I think we could leave it there until next version of Rasdaman officially announced and install guides are rewritten.