nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Subhash Parise <subhash.paris...@gmail.com>
Subject Re: getmongo processor exception
Date Tue, 17 Nov 2015 11:19:01 GMT
Hi NiFi experts,

Do any one know how to pass --sslInvalidCertifcates option to mongodb URI
getmongo processor ??


On Mon, Nov 16, 2015 at 8:52 PM, 林家銘 <robin890650@gmail.com> wrote:

> Hi
>
> I am sorry that, I am not familiar with enable the SSL in MongoDB,
> but I find the documents,
>
> http://mongodb.github.io/mongo-java-driver/3.0/driver/reference/connecting/ssl/?_ga=1.178196645.1092355907.1447682441
> It seems that one can only specify the flag
> "sslInvalidHostNameAllowed" in source code when using Java to connect
> to Mongo.
>
> But when I search the NiFI source code, there is no any match code so far.
> I think it needs more improvements.
>
> On 16/11/2015, Subhash Parise <subhash.parise36@gmail.com> wrote:
> > Hi robin,
> >
> > thank you for replying my post. Mongodb is listening with 27017 port. But
> > in my environment ssl is configured. Could you please let me know how to
> > make mongodb URI with --sslAllowInvalidCertificates option.
> >
> >
> > On Mon, Nov 16, 2015 at 4:44 PM, 林家銘 <robin890650@gmail.com> wrote:
> >
> >> Hi
> >>
> >> I think you need to check the MongoDB is listening to the port 27017
> >> at your Nifi host.
> >> On the Nofi host, if you are using Linux system, use the command below
> to
> >> check
> >> "netstat -nlp | grep 27017"
> >>
> >> On 16/11/2015, Subhash Parise <subhash.parise36@gmail.com> wrote:
> >> > Hi Team,
> >> >
> >> > I am very new to Apache NiFi and i am trying to create some sample
> >> > flows
> >> > using getmongo, putmongo processors. In my env i am getting fallowing
> >> > exception.
> >> >
> >> >
> >> > 2015-11-16 09:54:43,413 ERROR [Timer-Driven Process Thread-1]
> >> > o.a.nifi.processors.mongodb.GetMongo
> >> > GetMongo[id=e2e489f1-0a6f-4da7-897b-4d6df74a7de7] Failed to execute
> >> > query
> >> > Document{{text=test}} due to com.mongodb.MongoTimeoutException: Timed
> >> > out
> >> > after 30000 ms while waiting for a server that matches
> >> > ReadPreferenceServerSelector{readPreference=primary}. Client view of
> >> > cluster state is {type=UNKNOWN, servers=[{address=localhost:27017,
> >> > type=UNKNOWN, state=CONNECTING,
> >> > exception={com.mongodb.MongoSocketReadException: Prematurely reached
> >> > end
> >> of
> >> > stream}}]: com.mongodb.MongoTimeoutException: Timed out after 30000 ms
> >> > while waiting for a server that matches
> >> > ReadPreferenceServerSelector{readPreference=primary}. Client view of
> >> > cluster state is {type=UNKNOWN, servers=[{address=localhost:27017,
> >> > type=UNKNOWN, state=CONNECTING,
> >> > exception={com.mongodb.MongoSocketReadException: Prematurely reached
> >> > end
> >> of
> >> > stream}}]
> >> >
> >>
> >
>

Mime
View raw message