[
https://issues.apache.org/jira/browse/FLINK-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308983#comment-16308983
]
Raymond Tay commented on FLINK-8327:
------------------------------------
Yes, the fat-jar does contain Akka classes and like yourself, i naturally
assumed that the configuration file is not present but it turns out it was
present (i could run it via {{run}} while in {{sbt}} just to print out that
settings belonging to {{akka.http}}) and hence i came to the conclusion that it
_might_ be a class-loading problem. I'll need to investigate how Akka
classloading works in this situation and i'll come back a little later this
week.
Thanks for that suggestion, i'll try that suggestion out and see how things go
and i'll come back to this issue later today.
Sbt is complicated in the manner that there're multiple classloaders and i dont
know the full story about how they work cohesively.
> ClassLoader resolution of child-first does not appear to work
> -------------------------------------------------------------
>
> Key: FLINK-8327
> URL: https://issues.apache.org/jira/browse/FLINK-8327
> Project: Flink
> Issue Type: Bug
> Components: Queryable State
> Affects Versions: 1.4.0
> Environment: h3. Environment
> * Local flink cluster version 1.4.0
> * {{classloader.resolve-order: child-first}} in {{conf/flink-conf.yaml}}.
> * scala 2.11.11
> * oracle jdk 1.8.0
> h3. Library version
> * akka actors 2.4.20
> * akka http 10.0.10
> Reporter: Raymond Tay
>
> h2. Description
> Was trying out the {{Queryable State}} and ran into a problem where the
> submitted job starts regular Akka actors and making external HTTP calls via
> {{akka-http}} libraries and the flink runtime was complaining that it was not
> able to read the key {{akka.http}} (this key is held in the configuration
> file for {{akka-http}}).
> When i ran our app on the {{sbt}} shell locally, it was able to see the key
> {{akka.http}} but when we submitted the fatjar (via {{sbt-assembly}}) to
> flink, it was throwing the error message (see below). Looks like a class
> loader issue but i'm not sure.
> Any help is much appreciated !
> h2. Error message
> {noformat}
> Caused by: com.typesafe.config.ConfigException$Missing: No configuration
> setting found for key 'akka.http'
> at
> com.typesafe.config.impl.SimpleConfig.findKeyOrNull(SimpleConfig.java:152)
> at
> com.typesafe.config.impl.SimpleConfig.findOrNull(SimpleConfig.java:170)
> at
> com.typesafe.config.impl.SimpleConfig.findOrNull(SimpleConfig.java:176)
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:184)
> at com.typesafe.config.impl.SimpleConfig.find(SimpleConfig.java:189)
> at
> com.typesafe.config.impl.SimpleConfig.getObject(SimpleConfig.java:258)
> at
> com.typesafe.config.impl.SimpleConfig.getConfig(SimpleConfig.java:264)
> at com.typesafe.config.impl.SimpleConfig.getConfig(SimpleConfig.java:37)
> at akka.http.scaladsl.Http$.createExtension(Http.scala:843)
> at akka.http.scaladsl.Http$.createExtension(Http.scala:719)
> at akka.actor.ActorSystemImpl.registerExtension(ActorSystem.scala:917)
> at akka.actor.ExtensionId$class.apply(Extension.scala:79)
> at akka.http.scaladsl.Http$.apply(Http.scala:838)
> at akka.http.scaladsl.Http$.apply(Http.scala:719)
> at org.example.state.A.<init>(Simple.scala:158)
> ... 18 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
