You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Doug Fischer <dg...@dfischer.com> on 2006/05/10 18:03:06 UTC
Jetty configuration
I am configuring an http endpoint using the following:
...
<http:endpoint service=²aaa:receiver²
endpoint=²receiver²
role=²consumer²
locationURI=²http://localhost:8192/service²
defaultMep=²http://www.w3.org/2004/08/wsdl/in-out²
soap=²false² />
...
This works just fine and opens the port on localhost. What I would like to
do is set it up so that someone from outside can connect to it, this does
not seem to be the case with this configuration. This also does not seem to
work if I change localhost to my external ip address. Can anyone tell me
how I can simply open up a socket and have the ability to connect to it from
any machine using my external ip address?
Thank you very much.
Doug
Re: Jetty configuration
Posted by Guillaume Nodet <gn...@gmail.com>.
HTTP GET (and REST services) will be supported by the servicemix-http
component in the future...
Cheers,
Guillaume Nodet
On 5/10/06, Doug Fischer <dg...@dfischer.com> wrote:
> Thank you Peter. I was able to set it up with my internal ip address and
> therefore have access from external clients, since my it's in the NAT.
>
> Is there somehow to setup the servicemix-http SU endpoint to allow HTTP GET?
> Or some other way to do it? I will need to allow a GET at some point down
> the road and figured I would ask.
>
> Thanks,
> Doug
>
>
> On 5/10/06 2:01 PM, "Peter Klotz" <pe...@blue-elephant-systems.com>
> wrote:
>
> > Hi Doug,
> >
> > it should work if you use your local hostname instead of localhost. I had also
> > some problems in this area, when you have localhost I couldn't even connect
> > from
> > localhost. But when I had the local hostname in the config it worked. External
> > IP address should be ok too.
> > What does netstat -an |grep 8192 show?
> > (hope you are on Unix :-))
> > Try to telnet to this port and write
> > POST / HTTP/1.1
> > <return>
> > and see whether you get an connection or your server answers. HTTP GET will
> > not
> > work with the servicemix-http SU http endpoint.
> >
> >
> > Peter
> >
> > Doug Fischer wrote:
> >> I am configuring an http endpoint using the following:
> >>
> >> ...
> >> <http:endpoint service=²aaa:receiver²
> >> endpoint=²receiver²
> >> role=²consumer²
> >> locationURI=²http://localhost:8192/service²
> >> defaultMep=²http://www.w3.org/2004/08/wsdl/in-out²
> >> soap=²false² />
> >> ...
> >>
> >> This works just fine and opens the port on localhost. What I would like to
> >> do is set it up so that someone from outside can connect to it, this does
> >> not seem to be the case with this configuration. This also does not seem to
> >> work if I change localhost to my external ip address. Can anyone tell me
> >> how I can simply open up a socket and have the ability to connect to it from
> >> any machine using my external ip address?
>
>
>
Re: Jetty configuration
Posted by Doug Fischer <dg...@dfischer.com>.
Thank you Peter. I was able to set it up with my internal ip address and
therefore have access from external clients, since my it's in the NAT.
Is there somehow to setup the servicemix-http SU endpoint to allow HTTP GET?
Or some other way to do it? I will need to allow a GET at some point down
the road and figured I would ask.
Thanks,
Doug
On 5/10/06 2:01 PM, "Peter Klotz" <pe...@blue-elephant-systems.com>
wrote:
> Hi Doug,
>
> it should work if you use your local hostname instead of localhost. I had also
> some problems in this area, when you have localhost I couldn't even connect
> from
> localhost. But when I had the local hostname in the config it worked. External
> IP address should be ok too.
> What does netstat -an |grep 8192 show?
> (hope you are on Unix :-))
> Try to telnet to this port and write
> POST / HTTP/1.1
> <return>
> and see whether you get an connection or your server answers. HTTP GET will
> not
> work with the servicemix-http SU http endpoint.
>
>
> Peter
>
> Doug Fischer wrote:
>> I am configuring an http endpoint using the following:
>>
>> ...
>> <http:endpoint service=²aaa:receiver²
>> endpoint=²receiver²
>> role=²consumer²
>> locationURI=²http://localhost:8192/service²
>> defaultMep=²http://www.w3.org/2004/08/wsdl/in-out²
>> soap=²false² />
>> ...
>>
>> This works just fine and opens the port on localhost. What I would like to
>> do is set it up so that someone from outside can connect to it, this does
>> not seem to be the case with this configuration. This also does not seem to
>> work if I change localhost to my external ip address. Can anyone tell me
>> how I can simply open up a socket and have the ability to connect to it from
>> any machine using my external ip address?
Re: Jetty configuration
Posted by Peter Klotz <pe...@blue-elephant-systems.com>.
Hi Doug,
it should work if you use your local hostname instead of localhost. I had also
some problems in this area, when you have localhost I couldn't even connect from
localhost. But when I had the local hostname in the config it worked. External
IP address should be ok too.
What does netstat -an |grep 8192 show?
(hope you are on Unix :-))
Try to telnet to this port and write
POST / HTTP/1.1
<return>
and see whether you get an connection or your server answers. HTTP GET will not
work with the servicemix-http SU http endpoint.
Peter
Doug Fischer wrote:
> I am configuring an http endpoint using the following:
>
> ...
> <http:endpoint service=²aaa:receiver²
> endpoint=²receiver²
> role=²consumer²
> locationURI=²http://localhost:8192/service²
> defaultMep=²http://www.w3.org/2004/08/wsdl/in-out²
> soap=²false² />
> ...
>
> This works just fine and opens the port on localhost. What I would like to
> do is set it up so that someone from outside can connect to it, this does
> not seem to be the case with this configuration. This also does not seem to
> work if I change localhost to my external ip address. Can anyone tell me
> how I can simply open up a socket and have the ability to connect to it from
> any machine using my external ip address?