Re: Data streamer has been closed.

2019-05-07 Thread yangjiajun
Hello. I forget to add 'ordered' somewhere so that breaks this workaround.I think 'SET STREAMING ON ALLOW_OVERWRITE ON ORDERED;' works for me if I always use it. yangjiajun wrote > Hello. > > How to use this workaround when allow overwrite? > > I try 'SET STREAMING ON ALLOW_OVERWRITE ON

Re: Data streamer has been closed.

2019-05-07 Thread yangjiajun
Hello. How to use this workaround when allow overwrite? I try 'SET STREAMING ON ALLOW_OVERWRITE ON ORDERED;' and 'SET STREAMING ON ORDERED ALLOW_OVERWRITE ON;' but don't works. Taras Ledkov wrote > Hi, > > Workaround: use ordered streaming: > SET STREAMING ON ORDERED > > There is a bug at

Re: Data streamer has been closed.

2019-02-20 Thread Taras Ledkov
Hi, Workaround: use ordered streaming: SET STREAMING ON ORDERED There is a bug at the Ignite server on not ordered mode. The fix will be at the master soon. 20.01.2019 14:11, ilya.kasnacheev пишет: Hello! I have filed an issue https://issues.apache.org/jira/browse/IGNITE-10991 Regards,

Re: Data streamer has been closed.

2019-01-20 Thread ilya.kasnacheev
Hello! I have filed an issue https://issues.apache.org/jira/browse/IGNITE-10991 Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Data streamer has been closed.

2019-01-18 Thread Ilya Kasnacheev
t;> > reproduce > >> > on 2.7. Have you considered upgrading? > >> > > >> > Regards, > >> > -- > >> > Ilya Kasnacheev > >> > > >> > > >

Re: Data streamer has been closed.

2019-01-17 Thread yangjiajun
- >> > Ilya Kasnacheev >> > >> > >> > ср, 16 янв. 2019 г. в 14:14, yangjiajun < >> >> > 1371549332@ >> >> >>: >> > >> >> Hello. >> >> >> >> I do test on a ignite 2.6 node with persis

Re: Data streamer has been closed.

2019-01-17 Thread Ilya Kasnacheev
t an > >> exception: > >> > >> Exception in thread "main" java.sql.BatchUpdateException: class > >> org.apache.ignite.IgniteCheckedException: Data streamer has been closed. > >> at > >> > >> > org.apache.ign

Re: Data streamer has been closed.

2019-01-16 Thread yangjiajun
"main" java.sql.BatchUpdateException: class >> org.apache.ignite.IgniteCheckedException: Data streamer has been closed. >> at >> >> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamState.readResponses(JdbcThinConnection.java:1017) &

Re: Data streamer has been closed.

2019-01-16 Thread Ilya Kasnacheev
enabled and get an > exception: > > Exception in thread "main" java.sql.BatchUpdateException: class > org.apache.ignite.IgniteCheckedException: Data streamer has been closed. > at > > org.apache.ignite.internal.jdbc.thin.JdbcThinConnection$StreamSt

Data streamer has been closed.

2019-01-16 Thread yangjiajun
Hello. I do test on a ignite 2.6 node with persistence enabled and get an exception: Exception in thread "main" java.sql.BatchUpdateException: class org.apache.ignite.IgniteCheckedException: Data streamer has been closed. at org.apache.ignite.internal.jdbc.thin.JdbcThin

Re: java.lang.IllegalStateException: Data streamer has been closed.

2017-07-20 Thread zbyszek
Thank you for confirming Valentin! zb From: vkulichenko [via Apache Ignite Users] <ml+s70518n15190...@n6.nabble.com> To: zbyszek <zbab...@yahoo.com> Sent: Thursday, July 20, 2017 8:13 PM Subject: Re: java.lang.IllegalStateException: Data streamer has been closed.

Re: java.lang.IllegalStateException: Data streamer has been closed.

2017-07-20 Thread vkulichenko
Hi Zbyszek, You're subscribed now, all good. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Data-streamer-has-been-closed-tp15059p15190.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: java.lang.IllegalStateException: Data streamer has been closed.

2017-07-20 Thread zbyszek
y (say the second server is started 1 sec. after the first one). Very often, say with the 25% chance, the first server's addData(DataStreamerImpl.java:665) call fails with the error "java.lang.IllegalStateException: Data streamer has been closed". Looking at the log one can see that this

Re: java.lang.IllegalStateException: Data streamer has been closed.

2017-07-18 Thread vkulichenko
gt; started 1 sec. after the first one). Very often, say with the 25% chance, > the first server's addData(DataStreamerImpl.java:665) call fails with the > error "java.lang.IllegalStateException: Data streamer has been closed". > Looking at the log one can see that this

Re: java.lang.IllegalStateException: Data streamer has been closed

2017-07-18 Thread zbyszek
Thank you Mikhail, Your answer is very helpful. Just needed confirmation that this was a known issue. Regards, Zbyszek -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/java-lang-IllegalStateException-Data-streamer-has-been-closed-tp15061p15067.html Sent from

Re: java.lang.IllegalStateException: Data streamer has been closed

2017-07-18 Thread mcherkasov
-IllegalStateException-Data-streamer-has-been-closed-tp15061p15065.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

java.lang.IllegalStateException: Data streamer has been closed

2017-07-18 Thread zbyszek
is started 1 sec. after the first one). Very often, say with the 25% chance, the first server's addData(DataStreamerImpl.java:665) call fails with the error "java.lang.IllegalStateException: Data streamer has been closed". Looking at the log one can see that this error is always