The cause here is that you've got:

application.mode=dev

in application.conf.  I don't see it in the heroku play documentation
anywhere, but the prod server config can be referenced as %prod, so
you can add:

%prod.application.mode=prod

And it should fix this problem.

On Mar 14, 11:09 am, James Ward <[email protected]> wrote:
> The problem is that your Play app is trying to listen on the Java debug
> port.  This shouldn't happen in prod mode.  So maybe there is something
> weird with your application.conf file or something.  You can test this
> locally running the same command:
> play run --http.port=37235 --%prod -Dprecompiled=true
>
> Then try to make it so the debug port isn't used; You don't want to see
> the following message when running in prod mode:
> Listening for transport dt_socket at address: 8000
>
> Hope that helps.
>
> -James
>
> On 03/11/2012 08:39 AM, KenJi_getpowered wrote:
>
>
>
>
>
>
>
> > Hi everybody,
>
> > I am trying to push my play app on heroku but I constantly have an
> > issue with the port to be used.
>
> > I have the following :
>
> > 2012-03-11T14:34:55+00:00 heroku[web.1]: Starting process with command
> > `play run --
> > http.port=37235 --%prod -Dprecompiled=true`
> > 2012-03-11T14:34:57+00:00 app[web.1]: Listening for transport
> > dt_socket at address:
> >   8000
> > 2012-03-11T14:34:59+00:00 heroku[web.1]: Error R11 (Bad bind) ->
> > Process bound to p
> > ort 8000, should be 37235 (see environment variable PORT)
> > 2012-03-11T14:34:59+00:00 heroku[web.1]: Stopping process with SIGKILL
>
> > State:
> > - my apps is functionnal,
> > - no trouble with dependencies
> > - I tried with a Procfile : file named "Procfile" at the app root and
> > containing
> >     web: play run --http.port=$PORT $PLAY_OPTS
> > - I tried witthout Procfile
> > - I git pushed every time I did a modification.
>
> > Canyou help me? Do you have an idea?
>
> > Regards

-- 
You received this message because you are subscribed to the Google
Groups "Heroku" group.

To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en

Reply via email to