[jira] [Created] (SAMZA-211) Process hangs with remote debugging enabled

["Chris Riccomini (JIRA)" <ji...@apache.org>]

Chris Riccomini created SAMZA-211:
-------------------------------------

             Summary: Process hangs with remote debugging enabled
                 Key: SAMZA-211
                 URL: https://issues.apache.org/jira/browse/SAMZA-211
             Project: Samza
          Issue Type: Bug
          Components: container
    Affects Versions: 0.6.0
            Reporter: Chris Riccomini
             Fix For: 0.7.0


SamzaContainer appears to hang when remote debugging is enabled. This means that the [remote debugging tutorial|http://samza.incubator.apache.org/learn/tutorials/0.7.0/remote-debugging-samza.html] no longer works

To reproduce, set these settings in your job file:

{noformat}
job.factory.class=org.apache.samza.job.local.LocalJobFactory
task.opts=-Xmx1G -agentlib:jdwp=transport=dt_socket,address=localhost:9009,server=y,suspend=y
task.command.class=org.apache.samza.job.ShellCommandBuilder
{noformat}

The job.factory.class will set your job to run locally without YARN. The task.command.class will tell the LocalJobFactory to use a ProcessJob, not a ThreadJob, so that task.opts gets picked up. The task.opts switch is what turns on the remote debugging.

When you execute run-job.sh with this, you'll see that the SamzaContainer is running, but can't be connected to. No log is produced. You can't connect via JMX. Running `jps` shows:

{noformat}
$ jps
22003 JobRunner
20100 QuorumPeerMain
Could not synchronize with target
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)