Installation FAQs

Frequently asked questions

Contact the Behave Pro team if you are experiencing problems not listed here or require further assistance.

License invalid error

Ensure the latest version of the Behave Pro LIC Service plugin is installed in JIRA - this can be found in the installation docs.

SSLHandshakeException

The exception javax.net.ssl.SSLHandshakeException: General SSLEngine problem appears in either the Behave Pro or JIRA log file.

This may indicate a failure by either JVM to recognize the CA (certificate authority) that signed the SSL certificate securing JIRA or Behave Pro with HTTPS. This issue is common when the SSL certificate is signed by an internal CA or is self signed.

In these cases the certificate from either JIRA or Behave Pro (depending on which log the exception appeared) needs to be added to the JVM so that its trusted.

Adding JIRA's certificate to Behave Pro

$ cd ~/
$ echo "" | openssl s_client -connect jiraAddress:443 -showcerts 2>/dev/null | openssl x509 -out jira.cer
$ cd /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/security/
$ sudo keytool -import -keystore cacerts -file ~/jira.cer
$ sudo service behavepro restart

Adding Behave Pro's certificate to JIRA

Caution: JIRA may need to be restarted after adding the certificate to the keystore.

$ cd ~/
$ echo "" | openssl s_client -connect behaveProAddress:443 -showcerts 2>/dev/null | openssl x509 -out behavepro.cer
$ cd /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/security/
$ sudo keytool -import -keystore cacerts -file ~/behavepro.cer

The default passphrase for the java keytool is 'changeit'.

Caution: The JVM path that JIRA is using may differ, you can check the location of the JVM by checking the System details (key: java.home) area from JIRA administration.

Projects missing from Behave Pro

If you are unable to see a specific project from the Behave Pro Specifications page or unable to create/link scenarios from the issue, the cause is usually JIRA project permissions which prevent Behave Pro from reading the project.

From the selected projects administration area, select Permissions from the sidebar. Each permission listed should have a project role called "atlassian-addons-project-access", this allows Behave Pro to access the project and the containing issues.

If the project role is missing from these permissions, they can be added by selecting Grant permission from the top of the page - Select all permissions by selecting the first in the list, scrolling to the bottom of the list and SHIFT+Clicking the last in the list. Then select the "atlassian-addons-project-access" option from the Project role selection.

If you are still unable to see the projects after completing these steps, ensure the "Behave Pro" user is added to the "atlassian-addons-project-access" role, from the Roles page inside the projects administration area.

Log locations

Behave Pro Server writes to a log located at /var/log/behavepro/application.log and /var/log/upstart/behavepro.log, these may be required during the support process.

The JIRA log path can be found from the Systems details page from within the JIRA Administration.

An error has occoured while installing the addon

The error An error has occoured while installing the addon can appear inside JIRA for a number of reasons when attempting to install Behave Pro.

First ensure you're able to access https://<server address>/atlassian/connect/atlassian-jira.json from the JIRA machine, making sure there is nothing blocking the connection between Behave Pro VM and the JIRA instance at network or firewall level.

To check, run a curl command from the JIRA machine and ensure the file downloads properly.

curl https://<server address>/atlassian/connect/atlassian-jira.json

As the error doesn't provide much insight as to why its failed, take a look at the JIRA log to see if there is any additional output.

Ensure the Atlassian Connect plugins are installed as the installation guide describes, refer to the JIRA log after installing them to make sure they were successful. Reinstall if required.

SSLHandshakeException (documented above) also causes this error.

Read only LDAP or Active Directory system

When using a read only LDAP or AD (Active Directory) user management system in JIRA, there are a few issues around installing Behave Pro.

When installing Behave Pro, Atlassian Connect attempts to create Behave Pro's user credentials within JIRA. However with a read only system managing users, this isn't possible and causes the installation to fail.

There are a few ways around this, the first is to switch the user management system to write mode temporarily, so that Atlassian Connect is able to create the required user credentials.

The second possibility is to enable both JIRA's internal directory and the LDAP/AD system and prioritising the latter. This will allow LDAP/AD to function as before, but also allows Atlassian Connect to create the user in the internal directory.

Behave Pro is stuck in a restart loop

If Behave Pro is unavailable, it may mean its stuck in a restart loop. This is usually caused by a configuration issue inside application.conf. Most commonly its caused by the email notification configuration, ensure all 5 lines are uncommented and contain values. Use empty strings if you prefer not to recieve emails, but be sure to disable notifications as in the last part of the installation guide.

smtp.host=""
smtp.port=587
smtp.tls=true
smtp.user=""
smtp.password=""

Contact the Behave Pro team if you are experiencing problems not listed here or require further assistance.

  1. Prev
  2. Next