Nope, unless you are in a "clustered" mode (i.e. datacenter license), JIRA will not start if 2 instances are trying to access the same database.
But if you point a second installation of JIRA to your jira_db production, any changes in your JIRA test will affect your production database.
What you want to do is to duplicate your database (potentially on the same database server, but a different database, for example jira_db_test ) by dumping&importing your db from jira_db (prod), and have your test instance to point at this one
Hope it helps
Only if you really want to corrupt your data.
The whole point of a test environment is that it is isolated from your production environment so that you can sanity check behaviour before putting your production data at risk. Even within the limited circumstances where this is possible, it's a very bad idea.
Clone your database and point your test instance at the clone, instead. The first time something goes wrong, you'll be very glad that you did.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.