Jeff,

thanks for your hint. First I thought, that's it! - because the system
running web service #2 had a personal firewall. But even when deactivating
the firewall, i get a fault message...

Anymore ideas?

Cheers,

Rick.

---

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.net.ConnectException: Connection refused: connect
 faultActor:
 faultNode:
 faultDetail:
        {http://xml.apache.org/axis/}stackTrace: java.net.ConnectException:
Connection refused: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
        at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
        at java.net.Socket.connect(Socket.java:452)
        at java.net.Socket.connect(Socket.java:402)
        at java.net.Socket.<init>(Socket.java:309)
        at java.net.Socket.<init>(Socket.java:124)
        ....

> -----Ursprüngliche Nachricht-----
> Von: Jeff [mailto:[EMAIL PROTECTED]
> Betreff: Re: no solution for: server-server-webservice
>
>
> Hi Rick,
>
> This looks like a connectivity problem, e.g. proxy server (use
> java.net.Authenticator) or fire wall (reconfigure fire wall).
>
>
> Jeff
>
> ----- Original Message -----
> From: "Richard Alan Herz" <[EMAIL PROTECTED]>
> Subject: no solution for: server-server-webservice
>
>
> > Hiya.
> >
> > Just repeating my question - maybe someone has a solution...
> >
> > i have a client (c) calling a webservice (#1). this webservice
> (#1) needs
> to
> > fulfill the request information from another webservice (#2):
> >
> > c  --->
> >         #1 --->
> >                 #2
> >         #1 <---
> > c  <---
> >
> > now i have programmed the webservice #1 that way, that it creates a
> > servicebindingstub-object (generated by wsdl2java), sets some
> soap-headers,
> > and than calls the method from the servicebindingstub-object.
> just the way
> > my client works - but what's fine with the client, doesn't work with my
> > webservice #1. it comes up with the following fault message:
> >
> > --- --- ---
> > AxisFault
> > faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> > faultSubcode:
> > faultString: java.net-SocketException: Connection reset
> > faultActor:
> > faultNode:
> > faultDetail: ...
> > --- --- ---
> >
> > Any ideas? Need some more information?
> >
> > Thanks in Advance,
> >
> > Rick.
> >
> > ------------
> > Richard Alan Herz, Dipl. Wirtsch. Inf.
> > Ce-bIS, Otto-Friedrich-Universität Bamberg
> > Centre of business information systems
> > Kronacher Straße 41
> > D-96052 Bamberg
> >
> > Phone +49 (0)951 4 07 63-14
> > Fax   +49 (0)951 4 07 63-29
> > Mail  [EMAIL PROTECTED]
> >
> > ** Ce-bIS @ CeBIT Asia 2004 (Shanghai, 26. - 29.4): Future Parc
> > *** Ce-bIS @ CeBIT America 2004 (New York, 24. - 27.5): Future Parc
>
>

Reply via email to