Ok that looks like a non-critical bug in the EmbeddedMongoDB server,
IMHO you could resolve OGM-467 by pasting that stacktrace as a comment
on the JIRA issue.
On 24 February 2014 12:19, Guillaume SCHEIBEL
<guillaume.scheibel(a)gmail.com> wrote:
Hey Gunnar,
The message error I sent was coming from a -X run.
But I really don't think it's cause by our implementation because in the
full stack trace [1] there is any org.hibernate.ogm reference. Do you want
me to investigate further ?
[1] =>
https://gist.github.com/gscheibel/9187360
Guillaume
2014-02-24 12:11 GMT+01:00 Gunnar Morling <gunnar(a)hibernate.org>:
> Hey Guillaume,
>
> Where do you see this message, in the console output of Maven? I don't see
> it on my machine. You might try to add the "-X" and/or "-e"
parameters when
> running Maven, this may reveal the complete stacktrace.
>
> >
https://hibernate.atlassian.net/browse/OGM-467
>
> Thanks!
>
> --Gunnar
>
>
>
> 2014/2/24 Sanne Grinovero <sanne(a)hibernate.org>
>>
>> I don't know if that's normal, but good catch: might be wise to
>> investigate if all connections are closed appropriately.
>>
>>
https://hibernate.atlassian.net/browse/OGM-467
>>
>>
>> On 24 February 2014 10:10, Guillaume SCHEIBEL
>> <guillaume.scheibel(a)hibernate.org> wrote:
>> > Hi guys,
>> >
>> > I'm working on OGM-303 and after having run the test suite when comes
>> > the
>> > moment to shutdown the embedded mongodb instance I get this:
>> >
>> > *WARNING: sendShutdown /127.0.0.1:27018 <
http://127.0.0.1:27018>*
>> > *java.net.SocketException: Connection reset*
>> >
>> > Is it somehow a normal behavior ?
>> >
>> > Guillaume
>> > _______________________________________________
>> > hibernate-dev mailing list
>> > hibernate-dev(a)lists.jboss.org
>> >
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>