It would be nice for that message (and there is one more like it in the driver) to say something more specific about how/where exactly to "report" the situation. I mean, should users file Jira tickets for those two scenarios or simply email to the Java (or other driver) email lists? The message should be specific as to desired process for filing a bug. For example, the Python driver CONTRIBUTING.rst recommends filing a JIRA ticket, but generally on this list and most projects people are encouraged to open a discussion on the user list before concluding than an apparent issue is actually a real issue necessitating a ticket. But in the case of these two explicit cases where the driver itself is directing the user to report, it becomes unclear whether a simple inquiry/report on the driver mailing list is sufficient or whether a full Jira is warranted. Granted, starting on the mailing list is always a good idea, but as we continually see, people have difficulty even discerning the distinction between the Cassandra user list and the driver user lists. In truth, to some (a lot) of us, this distinction between "user" and "driver" is quite baffling. Sorry for the mini-rant!
-- Jack Krupansky On Wed, Mar 23, 2016 at 9:57 AM, Thunder Stumpges < thunder.stump...@gmail.com> wrote: > OK. Thanks. > On Tue, Mar 22, 2016 at 12:56 PM Alex Popescu <al...@datastax.com> wrote: > >> Hi Thunder, >> >> This would be better sent to the Java mailing list >> https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user. >> A quick search revealed >> https://datastax-oss.atlassian.net/browse/JAVA-603 which seem to match >> the Cassandra/DataStax community version but not the driver version. >> >> On Mon, Mar 21, 2016 at 9:33 PM, Thunder Stumpges < >> thunder.stump...@gmail.com> wrote: >> >>> Hi guys, >>> >>> So, quick background, we are using Outworkers (previously WebSudos) >>> Phantom v 1.22.0 Which appears to be using DataStax driver 3.0.0. We are >>> running scala 2.10 inside Samza on Yarn (CDH 5.4.4) with Oracle JDK 8. >>> >>> This is all pointing at a 3 node dev cluster of DataStax Community v >>> 2.1.13 >>> >>> After running for a short time, the following error is thrown by the >>> Datastax driver in the Samza container: >>> >>> Logger: com.datastax.driver.core.Connection >>> Message: >>> "Forcing termination of Connection[<cass-host>/<ip.add.re.ss>:9042-3, >>> inFlight=0, closed=true]. This should not happen and is likely a bug, >>> please report." >>> >>> There aren't really any other logs around this time, so not sure what >>> else I can provide. It said to "please report" so I guess I am. If what I >>> have provided is enough information to actually file a bug report, please >>> let me know and I will. Otherwise, what additional information can I >>> collect for this? >>> >>> Thanks, >>> Thunder >>> >>> >> >> >> -- >> Bests, >> >> Alex Popescu | @al3xandru >> Sen. Product Manager @ DataStax >> >>
