February 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (BAM-124) Hibernate concurrency mod exception appears to stop activity event collection

by Gary Brown (JIRA)

Gary Brown created BAM-124: ------------------------------ Summary: Hibernate concurrency mod exception appears to stop activity event collection Key: BAM-124 URL: https://issues.jboss.org/browse/BAM-124 Project: Business Activity Monitoring Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 1.0.0.M4 When the following exception occurred, it appeared to stop further activity events from being sent to the activity server. {noformat} 02:46:17,493 SEVERE [org.overlord.bam.activity.collector.BatchedActivityUnitLogger] (Timer-5) Failed to send Activity Unit: java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:819) [rt.jar:1.7.0_07] at java.util.ArrayList$Itr.next(ArrayList.java:791) [rt.jar:1.7.0_07] at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:263) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:190) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:326) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:52) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1081) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:973) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final] at org.overlord.bam.activity.store.jpa.JPAActivityStore.store(JPAActivityStore.java:197) [activity-store-jpa-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] at org.overlord.bam.activity.server.impl.ActivityServerImpl.store(ActivityServerImpl.java:91) [activity-server-impl-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] at org.overlord.bam.activity.collector.activity.server.ActivityServerLogger.sendMessage(ActivityServerLogger.java:92) [collector-activity-server-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] at org.overlord.bam.activity.collector.BatchedActivityUnitLogger$1.run(BatchedActivityUnitLogger.java:108) [activity-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT] at java.util.TimerThread.mainLoop(Timer.java:555) [rt.jar:1.7.0_07] at java.util.TimerThread.run(Timer.java:505) [rt.jar:1.7.0_07] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-150) Add documentation to the distro

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-150?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-150. --------------------------- > Add documentation to the distro > ------------------------------- > > Key: SRAMP-150 > URL: https://issues.jboss.org/browse/SRAMP-150 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Distro > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.1.1 > > > First release the documentation by running a mvn release build in the s-ramp.wiki/guide directory. This will create documentation in target/docbook/publish. > Copy the PDF documentation into s-ramp/docs. Also the documentation should be published on jboss.org. We should create a wiki page with detailed instructions on our process. > Run the release of s-ramp. > Run the release of the s-ramp distro which should contain the docs in PDF (and maybe also HTML version) > Finally Publish javadoc to gh-pages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-150) Add documentation to the distro

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-150?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-150. ----------------------------- Resolution: Done > Add documentation to the distro > ------------------------------- > > Key: SRAMP-150 > URL: https://issues.jboss.org/browse/SRAMP-150 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Distro > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.1.1 > > > First release the documentation by running a mvn release build in the s-ramp.wiki/guide directory. This will create documentation in target/docbook/publish. > Copy the PDF documentation into s-ramp/docs. Also the documentation should be published on jboss.org. We should create a wiki page with detailed instructions on our process. > Run the release of s-ramp. > Run the release of the s-ramp distro which should contain the docs in PDF (and maybe also HTML version) > Finally Publish javadoc to gh-pages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-151) Cannot add classifier to artifact when multiple ontologies are installed

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-151?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-151. ------------------------------- > Cannot add classifier to artifact when multiple ontologies are installed > ------------------------------------------------------------------------ > > Key: SRAMP-151 > URL: https://issues.jboss.org/browse/SRAMP-151 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.1.0 - Milestone 3 (Workflow and Relationships) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.1.1 > > > This can be reproduced by installing from the s-ramp distro and then running the classification demo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-151) Cannot add classifier to artifact when multiple ontologies are installed

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-151?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-151. --------------------------------- Resolution: Done Now all ontologies are checked before failing with "invalid classifier". > Cannot add classifier to artifact when multiple ontologies are installed > ------------------------------------------------------------------------ > > Key: SRAMP-151 > URL: https://issues.jboss.org/browse/SRAMP-151 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.1.0 - Milestone 3 (Workflow and Relationships) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.1.1 > > > This can be reproduced by installing from the s-ramp distro and then running the classification demo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-151) Cannot add classifier to artifact when multiple ontologies are installed

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-151?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-151: -------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/196 > Cannot add classifier to artifact when multiple ontologies are installed > ------------------------------------------------------------------------ > > Key: SRAMP-151 > URL: https://issues.jboss.org/browse/SRAMP-151 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.1.0 - Milestone 3 (Workflow and Relationships) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.1.1 > > > This can be reproduced by installing from the s-ramp distro and then running the classification demo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-151) Cannot add classifier to artifact when multiple ontologies are installed

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-151?page=com.atlassian.jira.plugin.... ] Work on SRAMP-151 started by Eric Wittmann. > Cannot add classifier to artifact when multiple ontologies are installed > ------------------------------------------------------------------------ > > Key: SRAMP-151 > URL: https://issues.jboss.org/browse/SRAMP-151 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 0.1.0 - Milestone 3 (Workflow and Relationships) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.1.1 > > > This can be reproduced by installing from the s-ramp distro and then running the classification demo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-151) Cannot add classifier to artifact when multiple ontologies are installed

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-151: ----------------------------------- Summary: Cannot add classifier to artifact when multiple ontologies are installed Key: SRAMP-151 URL: https://issues.jboss.org/browse/SRAMP-151 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: 0.1.0 - Milestone 3 (Workflow and Relationships) Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.1.1 This can be reproduced by installing from the s-ramp distro and then running the classification demo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-150) Add documentation to the distro

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-150?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-150: ---------------------------- Fix Version/s: 0.1.1 Affects Version/s: (was: 0.1.1) > Add documentation to the distro > ------------------------------- > > Key: SRAMP-150 > URL: https://issues.jboss.org/browse/SRAMP-150 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Distro > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.1.1 > > > First release the documentation by running a mvn release build in the s-ramp.wiki/guide directory. This will create documentation in target/docbook/publish. > Copy the PDF documentation into s-ramp/docs. Also the documentation should be published on jboss.org. We should create a wiki page with detailed instructions on our process. > Run the release of s-ramp. > Run the release of the s-ramp distro which should contain the docs in PDF (and maybe also HTML version) > Finally Publish javadoc to gh-pages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-150) Add documentation to the distro

by Kurt Stam (JIRA)

Kurt Stam created SRAMP-150: ------------------------------- Summary: Add documentation to the distro Key: SRAMP-150 URL: https://issues.jboss.org/browse/SRAMP-150 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Distro Affects Versions: 0.1.1 Reporter: Kurt Stam Assignee: Kurt Stam First release the documentation by running a mvn release build in the s-ramp.wiki/guide directory. This will create documentation in target/docbook/publish. Copy the PDF documentation into s-ramp/docs. Also the documentation should be published on jboss.org. We should create a wiki page with detailed instructions on our process. Run the release of s-ramp. Run the release of the s-ramp distro which should contain the docs in PDF (and maybe also HTML version) Finally Publish javadoc to gh-pages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2013