Questions[fisheye](server)

I'm trying to run a reverse proxy through to a website running locally through IIS to get SSL functioning. I've got all my rules set up so that I can see 90% of the site perfectly. The application is Atlassian's Crucible, but I think my issue is more generic than that.

The bad request has the following format (with sanitized names and paths)

https://bar.foo.com/crucible/cru/CR-4/edit-changelog/~author%3Dtheauthor%2520%253Ctheauthor%254040foo.com%253E/repository/

It appears that the URL re-write is dropping everything after the ~ character in the request.

For my inbound rewrite rule I've tried

crucible(.*)
^crucible(.*)
^/crucible(.*)
^/crucible(.*)$

And about a dozen other variations. I've also done this with the 'apply query string' box both checked and unchecked.

I asked this question at Atlassian but figured serverfault might be more appropriate as it's more of a sysadmin question than an Atlassian question:

I have been attempting to follow this guide to have FishEye+Crucible start at boot. JIRA is already installed and running as it's own user (jira) on Ubuntu at boot, but I cannot get Fisheye+Crucible (aka fecru) to do the same.

I followed the instructions there (and Ubuntu related note in the comments of the page) and rebooted, JIRA started on it's own as usual but fecru did not. Does it have something to do with the RUN_AS variable, which I set to 'jira'? Will that command run at boot without prompting for a password for the user 'jira'? I figured it would not prompt because the program JIRA starts at boot fine as that user...

Using:

Ubuntu 10.04 Lucid

Jira 5.0

Crucible+Fisheye 2.7.11

I have a problem with keytool tool.

I have a FishEye/Crucible server which needed to be connected to my Jira server. My Jira server uses SSL. I'm trying to import ssl certificate using the following command:

 keytool -importcert -alias "JiraCert" -file jira.crt -keystore $JAVA_HOME/jre/lib/security/cacerts
Enter keystore password:  
Keystore password is too short - must be at least 6 characters
Enter keystore password:  
Keystore password is too short - must be at least 6 characters
Enter keystore password:  
Keystore password is too short - must be at least 6 characters
Too many failures - try later

but it asks for password which is empty one as I managed to list available certificates in that keystore with no password, just Enter is pressed.

What do you think, what shall I do?

I have been trying to setup Atlassian Fisheye/Crucible as a service on Win 2K3 R2 for two weeks. I keep getting various "java.lang.OutOfMemoryError: PermGen space" errors, which crash Fisheye and force me to restart the service.

I've followed the example on the Atlassian support site to configure MaxPermSize within the service wrapper. However, when I check SysInfo inside the Fisheye Admin pages and the debug log, I don't see any confirmation. The Java Heap info is in both places, so I'd expect the MaxPermSize setting to show up in both places.

The error is persisting and Atlassian support has been little help.

I appreciate any help.

My company has been running a trial of Atlassian Crucible for some months now. For repositories where it's working properly, users have given very positive feedback about the tool. The problem I'm having is that we have several different projects, each with its own repository, and some of those repositories are very large. One repository in particular has a large number of branches and probably around 9,000 files per branch. Browsing that repository in Crucible is extremely slow.

Crucible is running on a CentOS VM. The VM has 4GB of RAM, and I've set Crucible's maximum at 3GB, of which it is currently using 2GB. I've brought this up in a support ticket with Atlassian, and they suggested the following:

In particular because you have a rather large SVN repository you will likely find that Fisheye will be creating a large index file on disk. To help improve performance a few things you can try are:

• Increasing the available memory available to Fisheye.
• Migrating to an external database.
• Excluding files and directories from your index that aren't needed.

I've tried all of these things to an extent, but so far none have helped greatly. I was originally running Crucible on a Windows box with 2GB of RAM using the built in HSQL DB. Moving to MySQL on CentOS saw a performance increase for some repositories, and made Crucible much more stable, but did not seem to help much with our biggest repository. There are only so many files/branches I can exclude from indexing while maintaining the tool's usefulness.

That being the case, does anyone have any tips on how to speed up Crucible on large repositories, without investing in insanely powerful hardware?

Thanks!

Edit: To clarify, since I didn't mention it explicitly above, I am using FishEye.

Edit 2: Since I originally posted this, performance has improved somewhat with new Crucible releases, but it's still not great by any means. It seems that this issue affects many users, including some with far more powerful hardware than we are using. Thus, I do not believe it is a hardware issue, but rather an issue with inherent inefficiency in Crucible. Atlassian is aware of the issue and will be including further performance improvements in future releases, so hopefully those changes solve our problems.

Edit 3: I'd forgotten how long ago I'd asked this question, so in my previous edit I neglected to mention that our hardware situation has also changed since it was originally asked. We're now running Crucible on a dedicated, physical server, still using CentOS. The hardware is still modest (4GB RAM, quad core CPU and dual 500GB disks in RAID 1 with external backup), but we did see a slight performance increase when we moved away from the VM.