-
1. Re: configuring remote access
jaikiran Jul 24, 2009 9:22 PM (in response to somakd)How are you trying to access the application? What are the errors you see on accessing? And what kind of application are you trying to access?
-
2. Re: configuring remote access
somakd Jul 29, 2009 4:43 PM (in response to somakd)Thanks for the reply.
Its a web application and I am positive that its getting deployed properly - the reason for that is I can see the application name listed in the Jboss web console which I can access locally from server as well as remotely.So when I try to access http://server_ip:9080/myapp it gives a HTTP 404 error. -
3. Re: configuring remote access
peterj Jul 29, 2009 5:25 PM (in response to somakd)Post the console log entries that show your app being deployed, and the entry that shows the HTTP port. Here is an example of each:
14:23:54,629 INFO [TomcatDeployment] deploy, ctxPath=/vote
14:23:54,697 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
Also, is 9080 a typo??? -
4. Re: configuring remote access
somakd Jul 29, 2009 5:57 PM (in response to somakd)21:42:43,375 INFO [TomcatDeployment] org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:163) deploy, ctxPath=/images_bak
21:42:43,432 INFO [TomcatDeployment] org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:163) deploy, ctxPath=/images_empty
21:42:43,497 INFO [TomcatDeployment] org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:163) deploy, ctxPath=/jmx-console
21:42:43,537 INFO [TomcatDeployment] org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:163) deploy, ctxPath=/maitai
21:42:43,615 INFO [STDOUT] org.jboss.logging.util.LoggerStream.write(LoggerStream.java:156) Quartz Initializer Servlet loaded, initializing Scheduler...
Above is a portion of servler.log file, and my app name is maitai.
No, 9080 is not a typo, I am trying to run Jboss on that port only, so I changed the values in ../jbossweb.sar/server.xml -
5. Re: configuring remote access
peterj Jul 29, 2009 6:24 PM (in response to somakd)Are you sure it is running on port 9080? You did not post the "[Http11Protocol] Starting Coyote HTTP/1.1" log entry, so I cannot tell. AS 5.x uses a centralized port binding manager, so chances are the port was overridden. Please post that log entry.
Also, the url should be http://server_ip:9080/maitai (not /myapp). Or was that purposeful obfuscation on your part (like the use of 'server_ip')? -
6. Re: configuring remote access
somakd Jul 29, 2009 6:34 PM (in response to somakd)Only reason I am sure of that is I can access http://localhost:9080/status in that box, but I couldnot find any ".....Starting Coyote HTTP/1.1" log entry in the log file. Is that the problem ?
Yeah, /myapp was purposeful. -
7. Re: configuring remote access
peterj Jul 29, 2009 7:58 PM (in response to somakd)It could be a problem - if the port was not reported in the log it might not be open. Was the logging changed to suppress that output? Without seeing that entry I'm not sure what the actually binding is. What OS are you using?
-
8. Re: configuring remote access
somakd Jul 29, 2009 8:24 PM (in response to somakd)I am not sure if the logging has been suppressed. How can I check that ?
I am running this on Mac OS X 10.5 -
9. Re: configuring remote access
peterj Jul 30, 2009 8:51 AM (in response to somakd)Logging is configured in server/xxx/conf/jboss-log4j.xml. If you haven't changed that file, then that particular log entry should show up. You can also check the server/xxx/log/server.log file - it might be there - search for "started in".
Is netstat available on OS X? You'll want to run it with the options to show all ports and the associated applications (usually: netstat -ap)
Can you access your app using http://localhost:9080/maitai?
Could it be a firewall issue? Is port 9080 open in the firewall? -
10. Re: configuring remote access
somakd Jul 30, 2009 1:34 PM (in response to somakd)Sorry, it was a symlink mistake I did in Mac. Files were not getting copied to the right directory. Everything's good now.
Thanks for all your help, Peter.