From a CI build, first time I've seen this, Google searches got me nowhere.
Thoughts? What precedes it in the log is ActiveMQ plugin startup, but the
stack trace doesn't imply that ActiveMQ's at fault necessarily.
*[14:11:47]:* [INFO] Loading broker configUri:
broker:(tcp://localhost:61616)
artifacts. According to
logs, this is a ConcurrentModificationException.
Is this a known bug ?
Here is the stacktrace :
2007-04-02 10:11:25,392 [http--1] ERROR [RepositoryServlet]
- Servlet.service() pour la servlet RepositoryServlet a généré une
exception
java.util.ConcurrentModificationException
Hello,
I've setup archiva as proxy to maven central. I'm using a recent snapshot
build.
I get sometimes (?) 500 errors when downloading artifacts. According to
logs, this is a ConcurrentModificationException.
Is this a known bug ?
Here is the stacktrace :
2007-04-02 10:11:25,392 [http--1
What is your version?
Emmanuel
Ryan, Scott D a écrit :
I noticed a posting on JIRA for this issue but no activity since
November. We were getting this problem on some of our projects but it
seems now that non of our projects will build due to this error. Has
anyone found a cause or
I noticed a posting on JIRA for this issue but no activity since
November. We were getting this problem on some of our projects but it
seems now that non of our projects will build due to this error. Has
anyone found a cause or workaround for this issue.
On Apr 8, 2005 10:32 AM, Washusen, Dan [EMAIL PROTECTED] wrote:
Hey All,
I'm trying to access all the current context variables in
my maven.xml,
I do it in this way :
j:scope
!-- I need sorted variables --
j:new var=map className=java.util.TreeMap
j:arg
Hey All,
I'm trying to access all the current context variables in my maven.xml,
using the below jelly script:
j:forEach items=${context.getVariables()} var=variable
echo${variable}/echo
/j:forEach
or
j:forEach items=${context.getVariableNames()} var=variable
echo${variable}/echo
${variable} is actually calling context.getVariable(), which while it
shouldn't modify the map probably triggers this. You may need to make
a copy of the list first.
- Brett
On Apr 8, 2005 10:32 AM, Washusen, Dan [EMAIL PROTECTED] wrote:
Hey All,
I'm trying to access all the current context
