[JBoss JIRA] (JBTM-1975) LogBrowser tool hangs on exit when browsing the HornetqJournalStore
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1975?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1975:
-----------------------------------
Fix Version/s: 5.0.3
(was: 6.0.0)
> LogBrowser tool hangs on exit when browsing the HornetqJournalStore
> --------------------------------------------------------------------
>
> Key: JBTM-1975
> URL: https://issues.jboss.org/browse/JBTM-1975
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Tooling
> Affects Versions: 5.0.0.M5
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.3
>
> Attachments: jstack.LogBrowser
>
>
> Using the LogBrowser tool to look at log records in the HornetqJournalStore hangs on shutdown. Debugging reveals org.hornetq.core.journal.impl.TimedBuffer waiting to aquire a semaphore (spinLimiter) in its run loop - I could not determine which thread (see attached jstack dump) owns the sepaphore
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (JBTM-1975) LogBrowser tool hangs on exit when browsing the HornetqJournalStore
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1975?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1975:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
The root cause is that we aren't calling stop on the journal (org.hornetq.core.server.stop()) before exiting.
> LogBrowser tool hangs on exit when browsing the HornetqJournalStore
> --------------------------------------------------------------------
>
> Key: JBTM-1975
> URL: https://issues.jboss.org/browse/JBTM-1975
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Tooling
> Affects Versions: 5.0.0.M5
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 6.0.0
>
> Attachments: jstack.LogBrowser
>
>
> Using the LogBrowser tool to look at log records in the HornetqJournalStore hangs on shutdown. Debugging reveals org.hornetq.core.journal.impl.TimedBuffer waiting to aquire a semaphore (spinLimiter) in its run loop - I could not determine which thread (see attached jstack dump) owns the sepaphore
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (JBTM-2180) Determine whether or not we should use a specific collections framework
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2180?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2180:
----------------------------------------
As a start on this task I have enabled the Oracle® JRockit Flight Recorder for a subset of the performance tests in the perf CI job (http://172.17.131.2/job/narayana-performance/). Flight data is stored in the maven build directory (target/test-classes/*.jfr) and can be read using the jmc tool available in the standard JDK (edition 7u40 and above).
What is the best way to evaluate other options given that there are many alternatives (and trying out each one involves engineering work):
* JDK Collections (much of our code hasn't been updated to take advantage of newer releases (Jesper has been looking into this);
* Goldman Sachs Collections;
* Google Collections (Guava);
* javolution;
* Highly Scalable Java;
* ...
Tests with flight data currently include:
Core:
com.hp.mwtests.ts.arjuna.performance.Performance1
com.hp.mwtests.ts.arjuna.performance.Performance2
com.hp.mwtests.ts.arjuna.performance.Performance3
com.hp.mwtests.ts.arjuna.performance.Performance4
JTA:
com.arjuna.ats.jta.xa.performance.OnePhase2PCPerformanceDefaultUnitTest
com.arjuna.ats.jta.xa.performance.OnePhase2PCPerformanceVolatileUnitTest
com.arjuna.ats.jta.xa.performance.OnePhasePerformanceDefaultUnitTest
com.arjuna.ats.jta.xa.performance.OnePhasePerformanceVolatileUnitTest
JTS
com.hp.mwtests.ts.jts.local.synchronizations.Performance
com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1
com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2
com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3
> Determine whether or not we should use a specific collections framework
> -----------------------------------------------------------------------
>
> Key: JBTM-2180
> URL: https://issues.jboss.org/browse/JBTM-2180
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTA, JTS, Performance Testing, REST, Transaction Core
> Affects Versions: 5.0.1
> Reporter: Mark Little
> Assignee: Michael Musgrove
>
> We use many of the inbuilt collections implementations (such as Hashtable) which are well known to be suboptimal in certain cases. Should we use a separate collections framework, e.g., https://github.com/goldmansachs/gs-collections
> There are pros and cons of doing this. But first we need to determine whether it really makes sense from a performance perspective.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2226?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2226:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.0.3
Resolution: Done
PR passed
> Issue with MAVEN_OPTS on Debian
> -------------------------------
>
> Key: JBTM-2226
> URL: https://issues.jboss.org/browse/JBTM-2226
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.2
> Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.0.3
>
>
> MAVEN_OPTS unset
> mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore
> ./build.sh: 42: ./build.sh: [[: not found
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2226?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-2226:
----------------------------------------
The problem is that dash does not support the [[ test syntax. We don't need that syntax in this script so we can replace it with the single bracket test as in: if [ -z "$MAVEN_OPTS" ]
> Issue with MAVEN_OPTS on Debian
> -------------------------------
>
> Key: JBTM-2226
> URL: https://issues.jboss.org/browse/JBTM-2226
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Affects Versions: 5.0.2
> Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
> Reporter: Mark Little
> Assignee: Michael Musgrove
> Priority: Minor
>
> MAVEN_OPTS unset
> mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore
> ./build.sh: 42: ./build.sh: [[: not found
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months