Hi,
I have a similar problem to issue: CLOSE WAIT and socket.close(),
My problem consist in this:
I have a Job that runs every 10 seconds, and every time uses a web service
client maded with JBossWS. This web service does a operations over a remote
server.
The problem is that each request opens
Hi,
I have a similar problem,
My problem consist in this:
I have a Job that runs every 10 seconds, and every time uses a web service
client maded with JBossWS. This web service does a operations over a remote
server.
The problem is that each request opens a socket and this socket is not always
Hi friend,
i have the same problem and i think that the jbossws do it a bad parse to some
documents WSDL.
If you know something thereon, i thank you very much, for several days working
on it...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4109400#4109400
Thanks alessio,
but perhaps that step, simple and intuitive,
I still do not understand.
I show you my strategy, and maybe you can give me another hand:
perhaps quite usual:
I have
- a SEI class: QMWISeSoap
- a class that extend of class javax.xml.ws.Service, and provide the getter
The class objectFactory provide methods for create objects how:
CreateParticipant.
in the SEI there is this:
/**
* This method creates a participant from the participant information
supplied and returns the Participant ID of the new participant. If the
Participant Name does not already
Hi all, Im have a problem with SOAP headers, because i dont know how see it in
endpoint. Explain:
first im consume de webservice, and i see this and more:
a class SEI: QMWISeSoap
a class that provide constructors: ObjectFactory
The server requires two soap headers, these are build by
Hi all, Im have a problem with SOAP headers, because i dont know how see it in
endpoint. Explain:
first im consume de webservice, and i see this and more:
a class SEI: QMWISeSoap
a class that provide constructors: ObjectFactory
The server requires two soap headers, these are build by
