no sigar-amd64-winnt.dll in java.library.path

[Joo Lee]

Hello guys,

When I run my test for Service, I am getting this errors and I cannot really do anything about it.. google search doesn't really help:

18:34:09.552 [ScalaTest-run] ERROR o.a.cassandra.service.StartupChecks - cassandra.jmx.local.port missing from cassandra-env.sh, unable to start local JMX service.

Btw, I have copied the newer LocalServiceLocator trait from the Git repository and placed it my project manually as the LocalServiceLocator in M1 snapshot was giving me compilation errors.

This is how my class looks like:

class PortfolioServiceSpec extends AsyncWordSpec with Matchers with BeforeAndAfterAll {


  lazy val server = ServiceTest.startServer(ServiceTest.defaultSetup.withCassandra(true)) { ctx =>
    new PortfolioApplication(ctx) with LocalServiceLocator
  }
  lazy val client = server.serviceClient.implement[PortfolioService]

  private val portfolioId = UUID.randomUUID()
  private val accountId = UUID.randomUUID()
  private val pd= PortfolioData(accountId, LocalDate.now(), "SGD", 1, BigDecimal.valueOf(0))

  "The PortfolioService" should {
    "create portfolio" in {
      client.createPortfolio().invoke(pd).map{
        response => response.riskPreference should ===(1)
      }
    }
  }

  override protected def beforeAll() = server

  override protected def afterAll() = server.stop()
}

Full error message is attached as a text file.

Do you have any ideas?

Regards,

Joo

[James Roper]

Hi Joo,

The line that you've pasted there can be ignored, it's simply Cassandra being noisy about no JMX port being specified, I'm not sure if there's anything we can do to turn that off unless we give it a JMX port, which I'm not sure makes sense.

The first exception in your stack trace is logged at DEBUG and so can be ignored too.

The second exception looks like you've got the wrong version of Guava on your classpath.  Are you using Maven or sbt?  If using Maven, you may need to add the following to your dependencyManagement section:

<dependency>

  <groupId>com.google.guava</groupId>

  <artifactId>guava</artifactId>

  <version>20.0</version>

</dependency>

If you're using sbt, you may want to check your resolution reports, these can be found in the target/resolution-cache/reports directory of your service.  For detail instructions on how to use these reports, see here:

https://www.playframework.com/documentation/2.5.x/SBTDebugging#Debugging-dependencies

What you want to find out is what version of Guava you're using.

Regards,

James

--
You received this message because you are subscribed to the Google Groups "Lagom Framework Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lagom-framework+unsubscribe@googlegroups.com.
To post to this group, send email to lagom-framework@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lagom-framework/f2af2074-fdfe-4be9-a604-26fa734c0e48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

James Roper
Software Engineer

Lightbend – Build reactive apps!
Twitter: @jroper

[Joo Lee]

Thanks again James. 

To unsubscribe from this group and stop receiving emails from it, send an email to lagom-framewo...@googlegroups.com.
To post to this group, send email to lagom-f...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lagom-framework/f2af2074-fdfe-4be9-a604-26fa734c0e48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.