[ 
https://issues.apache.org/activemq/browse/SM-573?page=comments#action_36932 ] 
            
Alain Knaff commented on SM-573:
--------------------------------

One more thing: when it succeeds, the following is printed to the server's 
stdout:

INFO  - LoanBroker                     - Receiving loan request
INFO  - CreditAgency                   - Receiving credit agency request
INFO  - LoanBroker                     - Receiving credit agency response
INFO  - LenderGateway                  - Receiving lender gateway request
INFO  - LoanBroker                     - Receiving lender gateway response
INFO  - Bank                           - Receiving bank request
INFO  - LoanBroker                     - Receiving loan quote
WARN  - SourceTransformer              - No Source available

That last line (WARN no Source available) worries me.


> LoanBroker example occasionnally hangs
> --------------------------------------
>
>                 Key: SM-573
>                 URL: https://issues.apache.org/activemq/browse/SM-573
>             Project: ServiceMix
>          Issue Type: Bug
>    Affects Versions: 3.0-M2
>         Environment: Linux
>            Reporter: Alain Knaff
>
> Often, the loan-broker example hangs.
> When that happens, the client (launched with "ant") hangs for a while at 
> [java] Sending request and eventually gets a javax.jms.JMSException: 
> EDU.oswego.cs.dl.util.concurrent.TimeoutException
> When that happens, nothing at all is logged on the server (launched with 
> servicemix.xml). Once in that state, it stays like that (until restarted).
> If the server is good at first, it often gets into that state at the second 
> request.
> Occasionnally, 1 request in 2 succeed (i.e. first succeeds, second hangs, 
> third succeeds, fourth hangs...)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to