[ 
https://issues.apache.org/jira/browse/FLINK-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211343#comment-16211343
 ] 

Bowen Li commented on FLINK-7864:
---------------------------------

With the latest master branch, I found I cannot run {{SideOutputITCase.java}} 
anymore from both console and intellij. Here's the error stack trace in 
intelliJ:

{code:java}
/Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home/bin/java -ea 
-Dlog.level=WARN -DforkNumber=01 -Dlog4j.configuration=log4j-test.properties 
-Xms256m -Xmx2048m -Dmvn.forkNumber=1 -XX:+UseSerialGC 
-Didea.launcher.port=7532 "-Didea.launcher.bin.path=/Applications/IntelliJ 
IDEA.app/Contents/bin" -classpath 
/private/var/folders/84/d9dx_03d7j13r7r51z7l37dc0000gp/T/classpath.jar 
-Dfile.encoding=UTF-8 com.intellij.rt.execution.application.AppMain 
com.intellij.rt.execution.junit.JUnitStarter -ideVersion5 
org.apache.flink.test.streaming.runtime.SideOutputITCase
Uncaught error from thread [flink-akka.actor.default-dispatcher-4] shutting 
down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[flink]
java.lang.NoSuchMethodError: 
akka.pattern.AskableActorRef$.$qmark$default$3$extension(Lakka/actor/ActorRef;Ljava/lang/Object;)Lakka/actor/ActorRef;
        at 
org.apache.flink.runtime.jobmanager.JobManager$$anonfun$handleMessage$1.applyOrElse(JobManager.scala:394)
        at 
scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
        at 
org.apache.flink.runtime.LeaderSessionMessageFilter$$anonfun$receive$1.applyOrElse(LeaderSessionMessageFilter.scala:38)
        at 
scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
        at 
org.apache.flink.runtime.LogMessages$$anon$1.apply(LogMessages.scala:33)
        at 
org.apache.flink.runtime.LogMessages$$anon$1.apply(LogMessages.scala:28)
        at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
        at 
org.apache.flink.runtime.LogMessages$$anon$1.applyOrElse(LogMessages.scala:28)
        at akka.actor.Actor$class.aroundReceive(Actor.scala:467)
        at 
org.apache.flink.runtime.jobmanager.JobManager.aroundReceive(JobManager.scala:125)
        at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
        at akka.actor.ActorCell.invoke(ActorCell.scala:487)
        at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
        at akka.dispatch.Mailbox.run(Mailbox.scala:220)
        at 
akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at 
scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at 
scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at 
scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

Process finished with exit code 255
{code}


[~aljoscha] Have you run into it?

> Support side-outputs in CoProcessFunction
> -----------------------------------------
>
>                 Key: FLINK-7864
>                 URL: https://issues.apache.org/jira/browse/FLINK-7864
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API
>            Reporter: Aljoscha Krettek
>            Assignee: Bowen Li
>             Fix For: 1.4.0
>
>
> We forgot to add support for side-outputs when we added that to 
> {{ProcessFunction}}. Should be as easy as adding it to the {{Context}} and 
> wiring it in.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to