It sounds like jax-ws issue, we can reproduce issue with simple test
case we can work with Meto guys.
Regards
Murali
jsexton0 wrote:
Hello -
I'll try to assemble some information and send it to you separately. The
process at the moment, is really chewing up CPU. Profiling reports that it
is spending all it's time in:
com.sun.enterprise.server.ss.provider.ASSelector.select(long)
10, 20 minutes at a time, with the CPU max'ed out. I believe it to be right
at the trouble point while this is going on.
That VisualVM is a really nice tool, thanks for the tip.
Murali Pottlapelli wrote:
Hi
60 MB logs would not help. So let us try simulating the issue.
Here is my understating of your scenario.
SOAP-UI->EJB-WS->HTTP-BC->BPEL
EJB-WS is packaged as separate SA. How EJB calls service? Will you
share screen shot this SA?
If I create a BPEL as below, is this sufficient?
Receive
Assign (sets value on the PL from variable & sets value for Invoke)
Invoke (external service)
How do I simulate time-out? shall I put huge time out after Invoke?
Is it possible for you to share the WSDL/XSDs/payload? I can use the
artifacts supplied by you or could fabricate myself. I like to be
create scenario that as real as possible.
Regards
Murali
