Confluence is using the H2 embedded database. You should migrate to a supported database to ensure your data is safe.
i want to stay on embedded db, but confluence told me error something about healty db.
This article don't help me. What should i do for correct working on embedded database without difficult actions?
the embedded database can fail any time, it's not as secure as MySQL. It's just a basic DB for testing purposes. When your Jira instance grows you'll experience performance problems as well.
I'd definitely suggest to use a separate, proper DB for production use and set up a backup solution for it.
I hope this help, let me know if you have any followup questions.
this should help you getting started: https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-a-database-938846850.html
Ideally, it's perfectly fine to start with H2 and then move onto something more permanent.
Just as a last thought: your DB can be on a different machine but H2 is always in the Jira folder on the same hard drive.
@Krisztian KovacsHi Krisz, I just want to add question about embedded DB. You mentioned that it is fine to start with H2. In case JIRA will only be used on a limited period of time, do you have idea if H2 database can hold around 2000 tickets/QA? What is the maximum capacity for the bundled DB?
Since you appear to have a starter license I am assuming your instance is not huge. All you need to do is install the same version of Confluence, using an external database, and then import an XML site backup from your instance that is currently using the H2 evaluation database. @Sergei Cherevko Please see Migrating to Another Database for more Confluence db details.
I created another database on Microsoft SQL Server. I connect to this server with domain windows account. (I add the linux computer to AD) I use connection string : jdbc:jtds:sqlserver://XXX:1433/confluence;domain=XXX
Test passed succesfull and it's freeze. What i do wrong? Empty page :((( please help
I hope this helps:
If you are on Linux or Solaris
logs/catalina.outin your JIRA Installation Directory, or for JIRA WAR, under your Tomcat installation directory.
There should be some sort of error in cataline.out
you can use
tail -f catalina.out
(in the relevant directory) when restarting Jira, or just scroll manually until you find some errors.
You can try to switch off the collaboration feature.
Also you can check if that port is open:
Synchrony runs on port 8091 by default, and an internal Synchrony proxy means that you shouldn't need to open this additional port.
Yes. Disabling collaboration resolv the problem, but how to repair this feature? May be i download the xml log files and send to technical support? may i do that? because we pay money (we have license) to atlassian and may be we have official support to helping resolve problems?
hi @Sergei Cherevko,
To answer your question: you can definitely contact Atlassian. It's part of the service.
However, first I would check if there is a network issue (port closed maybe) because Synchrony is quite sensitive to network issues.
There is a whole page at Atlassian, dedicated to this: https://confluence.atlassian.com/confkb/collaborative-editing-and-synchrony-troubleshooting-858584399.html
If you have strict network policies, you might have to disable collaborative editing altogether. It wouldn't be ideal though, as collaboration is a big selling point.
I hope this all makes sense, not just to me.
P.S.: if you find my answer useful, would you please consider accepting it. It helps a lot, as I'm going for the high score. :)
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events