On 1/13/2016 12:18 PM, McDermott, Becky wrote:
My problem has been solved. In the tomcat7w.exe, I had to add the following to
the Java Options:
-Djava.library.path=\PROGRA~1\IBM\JazzTeamServer_601\server\tomcat\lib
I also had to remove:
-Xgc:preferredHeapBase=1
With the removal of
On 1/15/2016 1:02 AM, Rahul Singh wrote:
Dear Christopher,
Thanks for your guidelines, we have big hope from Apache Tomcat Team to solve
this problem as this is show stopper for our application, we have also raise
this question on various forum like stack overflow and other,but no relevant
Please clarify your intent:
By default, tomcat has a /commented/ connector on 8443, which you can
configure You can activate as many connectors on as many ports
as you like. But if you have all applications on the same application
server anyways (and are using the same hostnames): Why bother?
Hi,
Try following. I can't guarantee it works with Jira and Confluence but this
could work.
Set up the cert in Apache and create AJP proxies between Apache and Tomcats
(if running one Tomcat for jira and one for confluence). I have similar
setup with other applications.
-Ari
15.1.2016 21.02
I will have two applications running on my tomcat server
Jira on port 8080 and confluence on port 8090
I'm going to get an ssl cert for the server which I'll call something like
test.mysite.com
Once I get my ssl cert for test.mysite.com how do I go about setting up the
configuration file for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeff,
On 1/15/16 2:01 PM, Jeff Jennings wrote:
> I will have two applications running on my tomcat server
>
> Jira on port 8080 and confluence on port 8090
>
> I'm going to get an ssl cert for the server which I'll call
> something like
Thanks - I understand your questionw. but unfortunately based on further
investigation I've discovered that I cannot run both of my apps on the same
server.
https://confluence.atlassian.com/jira/deploying-multiple-atlassian-applications-in-a-single-tomcat-container-218279138.html
On Fri, Jan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rahul,
On 1/15/16 1:02 AM, Rahul Singh wrote:
> Thanks for your guidelines, we have big hope from Apache Tomcat
> Team to solve this problem as this is show stopper for our
> application, we have also raise this question on various forum like
> stack
