[JAVA-806] Jndi Object Factory Created: 16/Apr/13  Updated: 19/Sep/19  Resolved: 26/Jun/16

Status: Closed
Project: Java Driver
Component/s: Configuration
Affects Version/s: None
Fix Version/s: 3.4.0

Type: New Feature Priority: Major - P3
Reporter: Juan Luis Melo Assignee: Jeffrey Yemin
Resolution: Done Votes: 11
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by JAVA-1084 Request: JNDI support Closed
Related
Case:

 Description   

Would be nice to have a MongoJndiObjectFactoryBean which implements javax.naming.spi.ObjectFactory to help configuring MongoClient thru Jndi?

see:
https://github.com/juanlmelo/mongo-java-driver/blob/master/src/main/com/mongodb/jndi/MongoJndiObjectFactoryBean.java



 Comments   
Comment by Githook User [ 14/Sep/16 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: JAVA-806: Add an implemenation of a JNDI ObjectFactory for MongoClient instances

Addresses JAVA-2309
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/dee6397441a05cd4121d5e0a91fa541d410a7411

Comment by Githook User [ 24/Jun/16 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: JAVA-806: Create JNDI ObjectFactory reference documentation
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/39db098e195945df8dd2c2156c6122f360d8524d

Comment by Denny Tharian [ 28/Aug/14 ]

HI,

This is not a WebLogic connection pooling specific setting. These are JEE specs that define what a connection pool factory should provide. Main feature we are talking about is the ability to connection pool and provide a JNDI access that multiple applications on the same instance can share.

Thank you
Denny

Comment by Markus Mahlberg [ 05/Aug/14 ]

Hi Jeff,

nevertheless it would be good to have a maintained JNDI object factory. Mutiple apps on one app server / servlet engine could share the connection pool, then. It is quite tricky otherwise to balance the number of executor threads and the connection pool size: a heavily loaded app may have too few connections available, while a less loaded app has loads of connections it doesn't need.

Kind regards,

Markus

Comment by Jeffrey Yemin [ 16/Jul/14 ]

Hi Denny,

In your previous comment you said you are asking for a lot more features than just a JNDI factory. Can you be more explicit about what you are looking for? We don't have any familiarity in house with Weblogic, so it would be useful to get more information.

Note also that the driver can not take and dependencies on Weblogic-specific classes or interfaces. We also don't think it's feasible to expose MongoDB via the JDBC interface, as the programming models are just too different.

Regards,
Jeff

Comment by Denny Tharian [ 05/Jun/14 ]

Jeff, I was referring to the JDBC console interface (GUI) for webLogic that allows basic functionality on Managing the JDBC connections(creating, monitoring, configuring etc...) . I know I am asking for a lot more features than just a JNDI factory but that is our ultimate goal so would be nice to know if there is something in the works for this.

Thank you
Denny

Comment by Jeffrey Yemin [ 03/Jun/14 ]

Hi Denny,

When you mentioned a JDBC interface, did you mean JNDI interface? Otherwise, it's not clear to me how your comment relates to the subject of this ticket.

Regards,
Jeff

Comment by Denny Tharian [ 03/Jun/14 ]

Hi,

We use the MongoDb client for connecting from WebLogic, here are the few benefits to being able to manage MongoDb connection through JDBC interface.
1) Management of the connections that exist.
2) Monitoring of connections within the WebLogic console.
3) Managing encryption of passwords using weblogic's encryption tools instead of having to use external property files to manage.

etc ...

Thank you
Denny

Generated at Thu Feb 08 08:53:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.