#1896 ✓resolved
Robert Rettig

play daemon [re]start-stop (python traceback)

Reported by Robert Rettig | December 18th, 2014 @ 10:42 AM | in 1.5.1 (closed)

http://www.screencast.com/t/Vrfl9FXi

Framework version: 1.3.0RC3
Platform you're using:

Betriebssystemname:                            Microsoft Windows 7 Professional
Betriebssystemversion:                         6.1.7601 Service Pack 1 Build 7601
Systemtyp:                                     x64-based PC
Prozessor(en):                                 1 Prozessor(en) installiert.
                                               [01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~3401 MHz
Systemgebietsschema:                           de;Deutsch (Deutschland)
Eingabegebietsschema:                          de;Deutsch (Deutschland)
Zeitzone:                                      (UTC+01:00) Amsterdam, Berlin, Bern, Rom, Stockholm, Wien
Gesamter physikalischer Speicher:              32.647 MB

Reproduction steps:

play deps samples-and-tests\yabe
play start samples-and-tests\yabe --%prod
OUTPUT:~ pid is 1348

Now something really bad with java! I simulate a crash with pskill from sysinternals.

pskill -t 1348
OUTPUT: Process 1348 killed.

Now a monitoring process want to restart (stop and start) the app.

play stop samples-and-tests\yabe
OUTPUT: ~ Cannot kill the process with pid 1348 (ERROR 6)

Ok nothing wrong here! Nice to have this information. Start application again.

play start samples-and-tests\yabe --%prod

OUTPUT:

Traceback (most recent call last):
  File "c:\play1-1.3.0RC3\play", line 156, in <module>
    status = cmdloader.commands[play_command].execute(command=play_command, app=play_app, args=remaining_args, env=play_env, cmdloader=cmdloader)
  File "c:\play1-1.3.0RC3\framework\pym\play\commands\daemon.py", line 25, in execute
    start(app, args)
  File "c:\play1-1.3.0RC3\framework\pym\play\commands\daemon.py", line 39, in start
    if process_running(pid):
  File "c:\play1-1.3.0RC3\framework\pym\play\commands\daemon.py", line 159, in process_running
    return process_running_nt(pid)
  File "c:\play1-1.3.0RC3\framework\pym\play\commands\daemon.py", line 192, in process_running_nt
    if process_list_nt().get(pid,"") != "":
  File "c:\play1-1.3.0RC3\framework\pym\play\commands\daemon.py", line 170, in process_list_nt
    junk, instances = win32pdh.EnumObjectItems(None,None,'process', win32pdh.PERF_DETAIL_WIZARD)
pywintypes.error: (-1073738824, 'EnumObjectItems for buffer size', 'Das angegebene Objekt wurde nicht auf dem Computer gefunden.')

Details:
I tried to explain the problem in #1860 and provided a patch. But I think the problem was not clear. Plz close #1860 and use this in stead.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Referenced by

Pages