[
https://issues.apache.org/jira/browse/FLINK-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037269#comment-14037269
]
ASF GitHub Bot commented on FLINK-949:
--------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/incubator-flink/pull/28#issuecomment-46550964
This is what you get:
```java
java.lang.Exception: Cannot instantiate local instance manager: Failed to
instantiate ChannelManager.
at
eu.stratosphere.nephele.jobmanager.JobManager.<init>(JobManager.java:223)
at
eu.stratosphere.client.minicluster.NepheleMiniCluster.start(NepheleMiniCluster.java:197)
at
eu.stratosphere.test.util.AbstractTestBase.startCluster(AbstractTestBase.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
at
com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
at
com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:202)
at
com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
Caused by: java.lang.Exception: Failed to instantiate ChannelManager.
at
eu.stratosphere.nephele.taskmanager.TaskManager.<init>(TaskManager.java:328)
at
eu.stratosphere.nephele.instance.local.LocalInstanceManager.<init>(LocalInstanceManager.java:170)
at
eu.stratosphere.nephele.jobmanager.JobManager.<init>(JobManager.java:221)
... 28 more
Caused by: java.io.IOException: Failed to instantiate GlobalBufferPool.
at
eu.stratosphere.runtime.io.network.ChannelManager.<init>(ChannelManager.java:85)
at
eu.stratosphere.nephele.taskmanager.TaskManager.<init>(TaskManager.java:325)
... 30 more
Caused by: java.lang.OutOfMemoryError: Tried to allocate 32768 buffers of
size 32768 bytes each (total: 1024 MB) and ran out of memory after 30009
buffers (937 MB).
at
eu.stratosphere.runtime.io.network.bufferprovider.GlobalBufferPool.<init>(GlobalBufferPool.java:70)
at
eu.stratosphere.runtime.io.network.ChannelManager.<init>(ChannelManager.java:83)
... 31 more
```
> ChannelManager startup exception not reported in TaskManager
> ------------------------------------------------------------
>
> Key: FLINK-949
> URL: https://issues.apache.org/jira/browse/FLINK-949
> Project: Flink
> Issue Type: Bug
> Affects Versions: pre-apache-0.5.1
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> While debugging a problem with [~rmetzger], we noticded that exception in the
> constructor of the {{ChannelManager}} are not properly forwarded to the
> {{TaskManager}}.
> The concrete problem was the following: num network buffers was misconfigured
> and tried to allocate more memory than available on the machine. The
> respective exception was hiden in the stdout file instead of the log.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
