Eclipse and JBoss

Thread view:

tom.simmons@vetco.com - 28 Apr 2008 08:34 GMT

Hi Folks

I'm fairly new to using Eclipse and JBoss, so excuse me if this
question is daft....

I have JBoss (4.2) working fine with Eclipse (3.3.2) when all I want
to do is run/debug stuff locally. The problem I currently have is I
need someone else to point their browser at my development JBoss and
see what I've been working on.

As far as I can make out, the current config only responds to
http://localhost:8080, I can't even use my IP address of machine name
locally. From reading around, it seems I need to add -b <my ip
address> to the arguments list, however when I try this I get an error
towards the end of the server start up about it timing out. (I haven't
found a more detailed output)

Just for info, if I put 127.0.0.1 as my adress is starts fine, though
obviously I still can't access my machine from another.

Tom

Reply to this Message

Matt Humphrey - 28 Apr 2008 19:40 GMT

> Hi Folks
>
[quoted text clipped - 15 lines]
> Just for info, if I put 127.0.0.1 as my adress is starts fine, though
> obviously I still can't access my machine from another.

If you're using a real IP address, how do you know whether it connects back
to your machine? I would expect you (like most people) to be behind a NAT
router or firewall. What address does your machine actually have (what does
ipconfig say) and what is its public IP address (what does whatismyip.com
say)? Also, for residential (non-commericial) users, some ISP block
incoming connections to some standard ports like 80. If you are behind a
NAT router you can probably direct it to forward requests to your machine.
Tell us how your network is configured.

Matt Humphrey http://www.iviz.com/

Reply to this Message

EricF - 29 Apr 2008 03:39 GMT

>Hi Folks
>
[quoted text clipped - 17 lines]
>
>Tom

I think you are right about the -b option if using JBoss 4.2.x. From the
release notes:

* JBossAS now binds its services to localhost (127.0.0.1) *by default*,
instead of binding to all available interfaces (0.0.0.0). This was primarily
done for security reasons because of concerns of users going to production
without having secured their servers properly. To enable remote access by
binding JBoss services to a particular interface, simply run jboss with the -b
option, but be aware you still need to secure you server properly.

Try that, find the error in boot.log or server.log, and post the relevant
errors message from the log, and mention what OS you are running.

Eric

Reply to this Message

Tom - 29 Apr 2008 08:11 GMT

> In article <abf1ebdb-283f-4e3d-8956-f952b8b38...@z72g2000hsb.googlegroups.com>, "tom.simm...@vetco.com" <tom.simm...@vetco.com> wrote:
>
[quoted text clipped - 36 lines]
>
> - Show quoted text -

Thank you, you were spot on with 0.0.0.0.

As for the reply previous to that, the reason I did not supply such
details is because I am talking about JBoss being used with Eclipse on
a development machine, not a mass audience machine.

Tom

Reply to this Message

Eclipse and JBoss

Free Magazines