Thank you, richard.

But what I want is bind to a PORT which is not equal to $PORT environment, 
because my app need to bind to another PORT.

在 2012年8月19日星期日UTC+8上午10时56分15秒,richard schneeman写道:
>
>  Heroku will give you the port that it is bound to in the $PORT 
> environment variable. Most Heroku applications use this variable in their 
> Procfile to tell their app what port to bind to, for ruby using the unicorn 
> server it would look like this: 
>
> web: bundle exec unicorn -p $PORT -c ./config/unicorn.rb
>
> -- 
> Richard Schneeman
> http://heroku.com
> @schneems <http://twitter.com/schneems>
>
> On Saturday, August 18, 2012 at 9:02 PM, Daniel Qian wrote:
>
> Hi all,
>
> I'm trying to use jbossjta on app. Everything is fine on my local machine, 
> but things go wrong after I deployed to Heroku.
>
> Here is the error log:
>
> ........ irrelvant logs ........
> 2012-08-19T00:24:41+00:00 app[web.1]:  INFO [main] 
> (TransactionStatusManager.java:87) 
> com.arjuna.ats.arjuna.recovery.TransactionStatusManager.addService(TransactionStatusManager.java:87)
>  
> - ARJUNA12163: Starting service 
> com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52173
> 2012-08-19T00:24:41+00:00 app[web.1]:  INFO [main] 
> (TransactionStatusManagerItem.java:326) 
> com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem.<init>(TransactionStatusManagerItem.java:326)
>  
> - ARJUNA12337: TransactionStatusManagerItem host: 127.0.0.1 port: 52173
> 2012-08-19T00:24:41+00:00 app[web.1]:  INFO [main] 
> (TransactionStatusManager.java:137) 
> com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:137)
>  
> - ARJUNA12170: TransactionStatusManager started on port 52173 and host 
> 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> 2012-08-19T00:24:41+00:00 heroku[web.1]: Error R11 (Bad bind) -> Process 
> bound to port 52173, should be 48257 (see environment variable PORT)
> ........ irrelvant logs ........
>
>  
> Apperantly, jbossjta tried to bind port 52173, but Heroku only allows port 
> 48257 to be bound.
>
> So, the question is can I open another PORT on heroku?
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "Heroku" group.
>  
> To unsubscribe from this group, send email to
> [email protected] <javascript:>
> For more options, visit this group at
> http://groups.google.com/group/heroku?hl=en_US?hl=en
>  
>  
> 

-- 
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