Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » BIRT » BIRT and MongoDB 3.2
BIRT and MongoDB 3.2 [message #1731982] Wed, 11 May 2016 12:28 Go to next message
Serge Ka is currently offline Serge KaFriend
Messages: 2
Registered: May 2016
Junior Member
Hi, all.

I'm trying to add BIRT Reports to existed MongoDB database(BIRT version 4.5 and 4.6 and MongoDB version are 3.2 with WiredTiger DB Engine). I can create DataSource and ping DB returns OK, but after I create DataSet from that DataSource, I get an empty list of collections. I found a bug in Bugzilla: it describes a similar situation, but this bug still in New status and no changes in it.

So is there any success stories for BIRT with MongoDB 3.2 and WiredTiger DB Engine?
Re: BIRT and MongoDB 3.2 [message #1735153 is a reply to message #1731982] Wed, 15 June 2016 22:07 Go to previous messageGo to next message
Leonid Ripeynih is currently offline Leonid RipeynihFriend
Messages: 150
Registered: February 2012
Senior Member
Hi, Serge!

I'm currently working with BIRT version 4.5 and MongoDB 3.2 with WiredTiger.
You're right that the build-in driver won't work (you will see empty collection list). The reason is actually a MongoDB driver version (2.10) that BIRT MongoDB data source uses - it's just too old to support WiredTiger. You need at least 2.14 driver version to work with WiredTiger using the 2.x driver branch. The java driver compatibility is documented on this page:, where it says

For MongoDB 3.0 deployments using the WiredTiger storage engine, if you run db.getCollectionNames() from a version of the mongo shell before 3.0 or a version of the driver prior to 3.0 compatible version, db.getCollectionNames() will return no data, even if there are existing collections. For more information, see WiredTiger and Driver Version Compatibility.

So, the solution to fix (or rather, to work around) a problem is to monkey-patch a org.eclipse.orbit.mongodb_2.10.1.v20130422-1135 plugin. To do it I
- took it from 'plugins' folder in my Eclipse installation
- unpacked it
- removed e-signatures from manifests
- extracted a new (2.14) driver version inside it
- packed it back to a jar with the same name and dropped it back to plugin folder
- then clean up a plugin cache (remove everything from 'configuration' folder in you Eclipse, except for 'org.eclipse.equinox.simpleconfigurator', 'org.eclipse.update' and 'config' files and folders)

The proper fix would be to upload a newer driver to Eclipse Orbit, and reference an updated version in BIRT MongoDB datasource, I hope BIRT maintainers would find time for this small fix.

Let me know if you have any questions on implementing the solution above.
Hope this helps.
Re: BIRT and MongoDB 3.2 [message #1794255 is a reply to message #1735153] Tue, 28 August 2018 07:26 Go to previous messageGo to next message
Singh Fang is currently offline Singh FangFriend
Messages: 1
Registered: August 2018
Junior Member
Hi, I had the same problem. cound you send me the modified jar to me?
Re: BIRT and MongoDB 3.2 [message #1807111 is a reply to message #1794255] Wed, 22 May 2019 18:31 Go to previous message
Arnoldas Zukauskas is currently offline Arnoldas ZukauskasFriend
Messages: 1
Registered: May 2019
Junior Member
This is fixed file with MongoDB 2.14 driver

Works with

Eclipse Version: 2019-03 (4.11.0)
MongoDB 4.0.4
Previous Topic:Highlighting with multiple conditions in a cross tab
Next Topic:Error while deploying birt.war file on weblogic 12c
Goto Forum:

Current Time: Fri Nov 22 10:12:32 GMT 2019

Powered by FUDForum. Page generated in 0.01692 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top