Jetty-web.xml causes Fisheye 2.7.5 to crash

[Andrew Borntreger]

The server is Fisheye-Crucible 2.7.5 running on Server 2008R2.  Recently updated Java to 1.7 runtime (from 1.6).  Attempting to remove the SSLv3 POODLE vulnerability by creating a custom jetty-web.xml in /WEB-INF/.  However, this causes the Fisheye service to shutdown after 30 seconds.  Extending the timeout does not resolve the issue.  Attempted multiple times, and nothing works. 

If there is any jetty-web.xml or web-jetty.xml file  in /WEB-INF/, even if the file is empty, it causes Fisheye to shutdown.

This appears to be the important output from wrapper.log:

STATUS | wrapper  | 2014/11/13 14:23:57 | --> Wrapper Started as Service
STATUS | wrapper  | 2014/11/13 14:23:57 | Launching a JVM...
INFO   | jvm 1    | 2014/11/13 14:23:57 | java version "1.7.0_71"
INFO   | jvm 1    | 2014/11/13 14:23:57 | Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
INFO   | jvm 1    | 2014/11/13 14:23:57 | Java HotSpot(TM) Server VM (build 24.71-b01, mixed mode)
INFO   | jvm 1    | 2014/11/13 14:23:57 |
INFO   | jvm 1    | 2014/11/13 14:23:57 | JDK 1.5 detected, registering Java Service Wrapper MBean
INFO   | jvm 1    | 2014/11/13 14:23:57 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2014/11/13 14:23:57 |
INFO   | jvm 1    | 2014/11/13 14:23:57 | WARN: your default encoding (windows-1252) does not support unicode.
INFO   | jvm 1    | 2014/11/13 14:23:57 | This is likely to cause problems if any of the filenames, branch names or tag names in one of your repositories contain unicode characters.
INFO   | jvm 1    | 2014/11/13 14:23:57 | Update your locale settings or start with the -Dfile.encoding=UTF-8 option to avoid these problems.
INFO   | jvm 1    | 2014/11/13 14:23:58 | 2014-11-13 14:23:58,281 INFO  - FishEye/Crucible 2.7.5 (20111021003431), Built on 2011-10-21
INFO   | jvm 1    | 2014/11/13 14:23:58 | 2014-11-13 14:23:58,281 INFO  - Starting UpgradeManager ...
INFO   | jvm 1    | 2014/11/13 14:24:01 | 2014-11-13 14:24:00,964 INFO  - Crucible: Commercial License registered to XXXXXXXX.
INFO   | jvm 1    | 2014/11/13 14:24:02 | 2014-11-13 14:24:02,103 INFO  - Server started on XXX.XXX.XXX.XXX:8060 (http), XXX.XXX.XXX.XXX:443 (https) (control port on 127.0.0.1:8059)
INFO   | jvm 1    | 2014/11/13 14:24:02 | 2014-11-13 14:24:02,103 ERROR - Could not start DefaultReviewItemIndexer schedule: Application Context not initialised.

INFO   | jvm 1    | 2014/11/13 14:24:03 | INFO  - FishEye arguments: []
ERROR  | wrapper  | 2014/11/13 14:24:36 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2014/11/13 14:24:36 | JVM did not exit on request, terminated
STATUS | wrapper  | 2014/11/13 14:24:37 | <-- Wrapper Stopped

[Andrew Borntreger]

The sample file you link to is the one I used as a basis for creating my own.  However, no matter what I do with that file, even if it is completely blank, the mere presence of it in the WEB-INF directory causes Fisheye to fail.

[lpater]

Hi Andrew,

please check the log file (in FISHEYE_INST/var/log) for more accurate error messages. It'd also be useful to have the content of the jetty-web.xml file you've created in WEB-INF.

There's a sample jetty-web.xml file with settings to disable SSLv3 here. FishEye/Crucible versions starting with 3.6.0 also allow configuring disabled SSL protocols/ciphersuites directly in the config file.

If the problem keeps occurring you'll probably want to raise a support request, attaching the files I've mentioned above.