JBoss on Fedora/Linux ... cannot establish a connection thru a browser : jboss

May 17, 2008 12:17am pdt

1. ramazanyich 9,950
2. J4M3S_UK 8,450
3. PascalHe... 3,500
4. Ajay-Singh 2,250
5. CEHJ 2,100
6. girionis 2,000
6. successc... 2,000
6. zrgiu 2,000
6. DaveyEss 2,000
10. TimYates 1,500
10. cedlinx 1,500
12. blu 1,000
12. julianop... 1,000
12. contactk... 1,000
15. RadioAct... 900

1. ramazanyich 15,950
2. J4M3S_UK 8,450
3. CEHJ 7,720
4. rama_kri... 7,000
5. mayankeagle 5,500
6. Ajay-Singh 4,250
7. objects 3,780
8. PascalHe... 3,500
9. contactk... 3,000
10. DaveyEss 2,200
11. girionis 2,000
11. schwertner 2,000
11. karanw 2,000
11. giltjr 2,000
11. gibu_george 2,000
11. mhunts 2,000
11. zrgiu 2,000
11. successc... 2,000
11. Kuldeepc... 2,000
11. CSecurity 2,000

06.21.2007 at 04:29PM PDT, ID: 22650117

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.2

JBoss on Fedora/Linux ... cannot establish a connection thru a browser

Zones: Jboss Application Server, Linux, Linux Networking

Tags: jboss

Using JBoss on Fedora 6.

From a browser using a direct IP connection to the JBoss Server, http://10.46.136.10:8080/ Firefox tells me "Firefox can't establish a connection to the server at 10.46.136.32:8080."

This happens whether I am connecting from a different computer, or even locally from the same computer.
But locally when I connect to LOCALHOST I get JBoss to respond.

What configuration setting in Fedora / LInux do I need to make to allow computers to connect to the Linux/JBoss Server?

Thanks

Start your free trial to view this solution

Question Stats

Zone: Software

Question Asked By: fshtank

Solution Provided By: CSecurity

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

06.21.2007 at 05:08PM PDT, ID: 19338068

Rank: Master

Luxana:

did you try change bindaddress, it seems that your server is listenning on local host 127.0.0.1

http://www.jboss.org/wiki/Wiki.jsp?page=ConfigUIL2

06.21.2007 at 05:36PM PDT, ID: 19338147

fshtank:

Thanks for the response. I read this article and it appears to be associated with MQ only.

Article Text: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
JBossMQ connector using a single tcp/ip connection between the server and the client.
The configuration can be found in uil2-service.xml In older versions of JBoss it was in jbossmq-service.xml
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I can understand binding a message queue to the IP, but given the nature of an App Server, shouldn't it come out of the package ready to listen on a port? ie. 8080.

Would Linux be standing in the way of allowing communication?

In the mean time I am searching for the "uil2-service.xml " file to see about updating that. Andirectory suggestions?

Thank you very much.

06.21.2007 at 06:30PM PDT, ID: 19338388

Rank: Master

Luxana:

can you try run this command on your linuxbox:

# netstat -ant

this will show all ports and ip addresses on which your box is listenning on...

06.21.2007 at 10:07PM PDT, ID: 19339112

CSecurity:

Check your listening ports and make sure you installed JBoss properly and apache tomcat also...And some system environment variables such as CATALINA_HOME and some other (I don't remember) need to be set before installation. Check them from manual or readme files in JBoss

06.21.2007 at 10:17PM PDT, ID: 19339136

fshtank:

Apache needs to be running for JBoss to access a port?
JBoss does start correctly, I am able to deploy, and locally I can acces the deployed app (simple JSP, Servlet, DAO app with a Datasource.)

Thanks.

06.21.2007 at 10:18PM PDT, ID: 19339144

CSecurity:

Have you checked netstat -na | grep LISTEN to check listening ports?

06.21.2007 at 10:21PM PDT, ID: 19339153

CSecurity:

And please tell us if there is 8080 port listening and if yes 8080 port listening on which IP? It should be 0.0.0.0 to be accessible via all IP addresses of your PC. otherwise you should enter IP address you see there in your browser with 8080 port. For example if it is listenint on 127.0.0.1, you should enter this in Firefox:
http://127.0.0.1:8080

06.22.2007 at 09:05AM PDT, ID: 19342526

fshtank:

After starting JBoss - Port 8080 is being listened to on the local IP (listing is below)
How can I get it to listen on the External Network IP?

Someone here at work (via Google Research) is suggesting using Apache Mod_JK.
Will I have to use Apache to handle the traffic routing to the different ports?
Being someone used to windows this seems a bit restrictive (yeahI know -- Linux vs. Windows security. ;-) )

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3873 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:50437 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8009 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:1098 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:1099 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:44590 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8083 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:43060 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:50713 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:730 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4444 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8093 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4445 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4446 0.0.0.0:* LISTEN
tcp 1 0 10.46.136.32:44430 209.xxx.xxx.xxx:80 CLOSE_WAIT
tcp 1 0 10.46.136.32:53747 131.xxx.xxx.xxx:80 CLOSE_WAIT
tcp 1 0 10.46.136.32:56810 129.xxx.xxx.xxx:80 CLOSE_WAIT
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 ::1:631 :::* LISTEN

I purposely added the xxx.xxx.xxx to the above address (just in case ;-)

Thanks

06.22.2007 at 09:17AM PDT, ID: 19342630

CSecurity:

Start JBoss with this command:

./run.sh -c all -b 0.0.0.0

06.22.2007 at 09:19AM PDT, ID: 19342642

CSecurity:

Or with this switch:
./run.sh -Djboss.bind.address=0.0.0.0

This different is in version difference.

06.22.2007 at 09:20AM PDT, ID: 19342653

CSecurity:

But abit I'm sure you need -b switch:
./run.sh -b 0.0.0.0

Accepted Solution

06.22.2007 at 09:36AM PDT, ID: 19342757

fshtank:

I actually modified the JBoss server.xml, replacing port 8080 $jboss.bind.address as 0.0.0.0 and It worked. But this seems like a cluge.

Also, I reverted back to jboss.bind.address and passed in the -b 0.0.0.0 [-Djboss.bind.address also] and every JBoss service failed:
- - - - - - - - - - - - - - - - - - -

The list of failures "For Reference Only"

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@5aa20ff1 { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/jboss-web.deployer/ROOT.war/ }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jboss-web.deployer/ROOT.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/jboss-web.deployer/ROOT.war/WEB-INF/web.xml
altDD: null
lastDeployed: 1182529964099
lastModified: 1178919840000
mbeans:

org.jboss.deployment.DeploymentInfo@1032a7cc { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/http-invoker.sar/invoker.war/ }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/http-invoker.sar/invoker.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/http-invoker.sar/invoker.war/WEB-INF/web.xml
altDD: null
lastDeployed: 1182529964840
lastModified: 1178919734000
mbeans:

org.jboss.deployment.DeploymentInfo@ff81a7d6 { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/jbossws.sar/jbossws-context.war }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48554jbossws-context-exp.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/jbossws.sar/jbossws-context.war
altDD: null
lastDeployed: 1182529965017
lastModified: 1182529964000
mbeans:

org.jboss.deployment.DeploymentInfo@584c9ae4 { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/WEB-INF/web.xml
altDD: null
lastDeployed: 1182529965171
lastModified: 1178919768000
mbeans:

org.jboss.deployment.DeploymentInfo@abf66cbf { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/jmx-console.war/ }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jmx-console.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/jmx-console.war/WEB-INF/web.xml
altDD: null
lastDeployed: 1182529970438
lastModified: 1178919842000
mbeans:

org.jboss.deployment.DeploymentInfo@da852034 { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/CoxAdmin.ear }
deployer: org.jboss.deployment.EARDeployer@95f290
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48584CoxAdmin.ear-contents/CoxAdminWeb-exp.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/CoxAdmin.ear
altDD: null
lastDeployed: 1182529971294
lastModified: 1182529970000
mbeans:

org.jboss.deployment.DeploymentInfo@1c4fc00b { url=file:/opt/jboss-4.2.0.GA/server/default/deploy/Template.ear }
deployer: org.jboss.deployment.EARDeployer@95f290
status: Deployment FAILED reason: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48585Template.ear-contents/TemplateWeb-exp.war/ deployment failed
state: FAILED
watch: file:/opt/jboss-4.2.0.GA/server/default/deploy/Template.ear
altDD: null
lastDeployed: 1182529972789
lastModified: 1182529971000
mbeans:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.web.deployment:war=ROOT.war,id=1520570353
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jboss-web.deployer/ROOT.war/ deployment failed

ObjectName: jboss.web.deployment:war=invoker.war,id=271755212
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/http-invoker.sar/invoker.war/ deployment failed

ObjectName: jboss.web.deployment:war=jbossws-context.war,id=-8280106
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48554jbossws-context-exp.war/ deployment failed

ObjectName: jboss.web.deployment:war=jbossmq-httpil.war,id=1481415396
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ deployment failed

ObjectName: jboss.web.deployment:war=web-console.war,id=1202128999
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/management/console-mgr.sar/web-console.war/ deployment failed
I Depend On:
jboss.admin:service=PluginManager

ObjectName: jboss.web.deployment:war=jmx-console.war,id=-1409913665
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jmx-console.war/ deployment failed

ObjectName: jboss.web.deployment:war=CoxAdminWeb.war,id=-1176708569
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48584CoxAdmin.ear-contents/CoxAdminWeb-exp.war/ deployment failed

ObjectName: jboss.web.deployment:war=TemplateWeb.war,id=1399407512
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48585Template.ear-contents/TemplateWeb-exp.war/ deployment failed

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.web.deployment:war=invoker.war,id=271755212
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/http-invoker.sar/invoker.war/ deployment failed

ObjectName: jboss.web.deployment:war=ROOT.war,id=1520570353
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jboss-web.deployer/ROOT.war/ deployment failed

ObjectName: jboss.web.deployment:war=jbossws-context.war,id=-8280106
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48554jbossws-context-exp.war/ deployment failed

ObjectName: jboss.web.deployment:war=web-console.war,id=1202128999
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/management/console-mgr.sar/web-console.war/ deployment failed
I Depend On:
jboss.admin:service=PluginManager

ObjectName: jboss.web.deployment:war=CoxAdminWeb.war,id=-1176708569
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48584CoxAdmin.ear-contents/CoxAdminWeb-exp.war/ deployment failed

ObjectName: jboss.web.deployment:war=jbossmq-httpil.war,id=1481415396
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ deployment failed

ObjectName: jboss.web.deployment:war=TemplateWeb.war,id=1399407512
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp48585Template.ear-contents/TemplateWeb-exp.war/ deployment failed

ObjectName: jboss.web.deployment:war=jmx-console.war,id=-1409913665
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/opt/jboss-4.2.0.GA/server/default/deploy/jmx-console.war/ deployment failed

09:32:53,105 WARN [JBossWeb] Failed to startConnectors
javax.management.InstanceNotFoundException: jboss.web:type=Service,serviceName=jboss.web is not registered.

06.22.2007 at 09:39AM PDT, ID: 19342777

CSecurity:

No another solution I was going to suggest you was editing config .xml files... That works, you can change bind addresses to 0.0.0.0... Why not?

06.22.2007 at 09:41AM PDT, ID: 19342795

CSecurity:

And you also passed -c all parameter with -b ?

06.22.2007 at 09:53AM PDT, ID: 19342893

fshtank:

Yeah, i passed in the -c all -b 0.0.0.0

But doesn't that just execute the ALL server instead of default?

06.22.2007 at 09:54AM PDT, ID: 19342908

CSecurity:

yeah, and you passed without -b ?

06.22.2007 at 09:54AM PDT, ID: 19342916

CSecurity:

sorry without -c all

06.22.2007 at 09:56AM PDT, ID: 19342929

CSecurity:

and make sure you returned correct value of config file after you edited them and then test with my parameters with and without -c all... But don't forget -b 0.0.0.0 parameter

06.22.2007 at 10:25AM PDT, ID: 19343177

fshtank:

Well, I did something to my JBoss installation, but I just downloaded again, and overlaid the existing copy -
then Iran command: ./run.sh -b 0.0.0.0

All errors magically disappeared and the App Server is externally available.

Thanks for persevering. Your answer was correct.

06.22.2007 at 10:27AM PDT, ID: 19343193

CSecurity:

You are welcome... ;)

20080236-EE-VQP-29