[ 
https://issues.apache.org/jira/browse/UIMA-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930546#comment-13930546
 ] 

Jerry Cwiklik commented on UIMA-3634:
-------------------------------------

After extended debugging, it looks like the intermittent problems reported are 
caused by AMQ 5.7 Advisory messages. These messages are triggered by AMQ to 
advertise  internal events, some of which are queue creation and queue 
deletion. These events are available to each broker connection. An application 
code may tap into these events (advisories) to monitor internal broker events.

For some reason it appears that these advisories play a role during message 
delivery to a temp queue. The UIMA-AS service code is trying to reply to an 
existing temp queue, yet AMQ thinks that the queue was deleted. JConsole 
connected to the broker confirmed existence of the temp queue when the errors 
started happening. 

After googling the problem I've a found some pointers, especially in 
http://stackoverflow.com/questions/6432672/activemq-how-to-handle-broker-failovers-while-using-temporary-queues

Even though the described scenario does not match mine, there was a hint in 
there about turning off advisories on the connection used for sending replies. 
Once the advisories were turned off, the code began working correctly. 

It looks like there is a bug in AMQ5.7 but I was not able to confirm it looking 
at bug fixes reports of subsequent releases (5.8, 5.9).

In any case, turning off the advisories seems like an acceptable workaround for 
now as the uima-as code doesnt use advisories.  
 

> Jenkins fails UIMA-AS due to missing dependencies
> -------------------------------------------------
>
>                 Key: UIMA-3634
>                 URL: https://issues.apache.org/jira/browse/UIMA-3634
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.4.2AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.5.0AS
>
>
> Jenkins fails UIMA-AS with:
> "Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal 
> on project uimaj-as-activemq: Could not resolve dependencies for project 
> org.apache.uima:uimaj-as-activemq:jar:2.5.0-SNAPSHOT: The following artifacts 
> could not be resolved: net.sf.josql:josql:jar:1.5, 
> net.sf.josql:gentlyweb-utils:jar:1.5: Could not find artifact 
> net.sf.josql:josql:jar:1.5 in eclipsePlugins (http://repo1.maven.org/eclipse) 
> -> [Help 1]"
> looks like the dependencies no longer exist in the Maven repos.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to