Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

This issue can't be edited

Because it belongs to an archived project. Jira admins can restore projects from the archive.

Verify that the testsuite does not leak connections to MongoDB

Description

Gauillaume noticed these messages at the end of the MongoDB tests:

WARNING: sendShutdown /127.0.0.1:27018 <http://127.0.0.1:27018>
java.net.SocketException: Connection reset

We would need to at least verify if this is a test issue or a potential leak of our implementation.

Environment

None

Activity

Show:

Guillaume Scheibel February 24, 2014 at 12:46 PM

It's an non-critical internal embedded mongodb server issue. see:
https://gist.github.com/gscheibel/9187360

Guillaume Scheibel February 24, 2014 at 12:45 PM

This is coming from the Embedded server but there is any impact on our test suite see:

WARNING: sendShutdown /127.0.0.1:27018
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:189)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.net.SocketInputStream.read(SocketInputStream.java:107)
at de.flapdoodle.embed.mongo.runtime.Mongod.sendShutdown(Mongod.java:87)
at de.flapdoodle.embed.mongo.AbstractMongoProcess.sendStopToMongoInstance(AbstractMongoProcess.java:114)
at de.flapdoodle.embed.mongo.AbstractMongoProcess.stop(AbstractMongoProcess.java:90)
at com.github.joelittlejohn.embedmongo.StopEmbeddedMongoMojo.execute(StopEmbeddedMongoMojo.java:38)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

Fixed

Details

Assignee

Reporter

Participants

Guillaume Scheibel
Sanne Grinovero

Components

Fix versions

Priority

Created February 24, 2014 at 11:03 AM
Updated April 15, 2014 at 10:48 PM
Resolved February 24, 2014 at 12:46 PM

Flag notifications