The goal for the release lifecycle of this library is to provide fully compatible version with the most recent Jira Server version at the time of its release plug provide backward compatibility for officially supported Jira Server versions.
#JIRA CLIENT PYTHON CODE#
Javadoc is not overwhelmingly rich, but the code and the object model is rather self-explanatory and follows clear naming convention. JRJC should be useful for integrating systems using JVM-based languages (like Java) with JIRA and specifically for integrating Atlassian products with themselves. In the future though JRJC may be extended to handle things like caching (conditional GET, metadata) or provide a higher level of abstraction on top of existing REST API - completely shielding the user from the specifics of REST. It provides a domain object model of JIRA entities on the client side - objects representing issues, priorities, resolutions, statuses, users, etc. JRJC currently provides a thin layer of abstraction on top of REST API and related HTTP(S) communication. Tada! – the error disappears, and your program starts to run, instead of failing and waiting 30 seconds to tell you.Jira REST Java Client is a Java library (usable from any JVM language) which allows to easily talk to any Jira Server 4.2+ instance using new (and still evolving) REST API. Thus, I have the parent thread create one instance of MongoWrapper, and then pass that as a parameter to the processes. In my case, I solved the issue by ensuring that each thread does not initialize a new instance of MongoWrapper. That’s cool… except when the issue is actually not related to the database going down. You can rate examples to help us improve the quality of examples. When it finally does fail, you’ll get the error above… 30 seconds after your database went down. These are the top rated real world Python examples of jiraclient.JIRA extracted from open source projects. If you don’t put it there, the default value is 30 seconds… Which means your application sits there, waiting to see if the mongo database will connect for 30 seconds, once it realizes that the database is missing. Oddly enough, it's especially hard to track down because of the serverSelectionTimeoutMS parameter. In this case, pymongo 3.0.2 REALLY doesn’t like it, and you’ll get the “No Servers found yet” error when you try to retrieve results from your database.
#JIRA CLIENT PYTHON SERIES#
Indeed, I’ve done that before with 2.8.x series of pymongo, and it worked well. However, if you’re doing multiprocessing, the temptation is to allow each of your threads to launch a new instance of the MongoWrapper.
You say:Īnd they go off and do a non-blocking initialization of everything pymongo needs to start the server.
#JIRA CLIENT PYTHON DRIVERS#
Pymongo drivers (3.0.2) appear to have changed their initialization (compared to 2.8.x), so that they no longer actually create the connection pool when you initialize them. ServerSelectionTimeoutError: No servers found yet Server = self._get_topology().select_server(selector)įile "/Users/afejes/sandboxes/pipeline4/lib/python2.7/site-packages/pymongo/topology.py", line 121, in select_serverįile "/Users/afejes/sandboxes/pipeline4/lib/python2.7/site-packages/pymongo/topology.py", line 97, in select_servers With client._socket_for_writes() as sock_info:įile "/usr/local/Cellar/python/2.7.10/Frameworks/amework/Versions/2.7/lib/python2.7/contextlib.py", line 17, in _enter_įile "/Users/afejes/sandboxes/pipeline4/lib/python2.7/site-packages/pymongo/mongo_client.py", line 663, in _get_socket Return self._bulk.execute(write_concern)įile "/Users/afejes/sandboxes/pipeline4/lib/python2.7/site-packages/pymongo/bulk.py", line 430, in execute File "/Users/afejes/sandboxes/pipeline4/lib/python2.7/site-packages/pymongo/bulk.py", line 582, in execute
0 kommentar(er)
