[JBoss JIRA] (JBTM-1974) Qa tests needs the narayana build being done with parameter idlj-enabled to work
by Ondřej Chaloupka (JIRA)
Ondřej Chaloupka created JBTM-1974:
--------------------------------------
Summary: Qa tests needs the narayana build being done with parameter idlj-enabled to work
Key: JBTM-1974
URL: https://issues.jboss.org/browse/JBTM-1974
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 5.0.0.M5
Reporter: Ondřej Chaloupka
Assignee: Tom Jenkinson
Priority: Minor
When qa tests should be built without compilation errors the prior narayana build has to be run with parameter -Didlj-enabled=true
In the way like
./build.sh clean install -Prelease -DskipTests -Didlj-enabled=true
This fact should be at least documented in REAME.
Plus it would be nice to avoid this dependence (or put idlj-enabled parameter which activates a profile as default).
--
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, 2 months
[JBoss JIRA] (JBTM-1971) Cannot browse logs with the LogBrowser tool
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1971?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1971:
-----------------------------------
I believe I have a fix for the initial problem. If someone wants to split the issues then I can check this in to test.
> Cannot browse logs with the LogBrowser tool
> -------------------------------------------
>
> Key: JBTM-1971
> URL: https://issues.jboss.org/browse/JBTM-1971
> 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: Tom Jenkinson
> Attachments: jstack.LogBrowser
>
>
> I tried browsing some logs using the command:
> {noformat}
> java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
> {noformat}
> This gives an interactive command line. I then had a go at listing some logs using:
> {noformat}
> -> select AtomicAction
> -> ls
> {noformat}
> The tool does not find any logs even though there are entries in the directory:
> {code}
> <path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> {code}
> The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
> Also running the tool to view Hornetq store logs 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)
--
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, 2 months
[JBoss JIRA] (JBTM-1971) Cannot browse logs with the LogBrowser tool
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1971?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1971:
-----------------------------------
Not quite. The DEFAULT_TYPE is always meant to be a shorthand for the log type, so AtomicAction is correct. The issue is that this shorthand should have been mapped to the actual log type when used by the object store. That's what TransactionTypeManager is supposed to do, but isn't in this case.
I suggest separating this issue into two. One concerned with this short-hand and one to do with the HQ log. Assign me the former and someone else will have to look at the HQ issue because I haven't tried that before. Although I suggest working on the second after I've fixed the first in case there are any knock-on consequences.
> Cannot browse logs with the LogBrowser tool
> -------------------------------------------
>
> Key: JBTM-1971
> URL: https://issues.jboss.org/browse/JBTM-1971
> 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: Tom Jenkinson
> Attachments: jstack.LogBrowser
>
>
> I tried browsing some logs using the command:
> {noformat}
> java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
> {noformat}
> This gives an interactive command line. I then had a go at listing some logs using:
> {noformat}
> -> select AtomicAction
> -> ls
> {noformat}
> The tool does not find any logs even though there are entries in the directory:
> {code}
> <path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> {code}
> The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
> Also running the tool to view Hornetq store logs 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)
--
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, 2 months
[JBoss JIRA] (JBTM-1973) wsat-jta jta bridge quickstart failure
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1973:
--------------------------------------
Summary: wsat-jta jta bridge quickstart failure
Key: JBTM-1973
URL: https://issues.jboss.org/browse/JBTM-1973
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 5.0.0.M5
Reporter: Michael Musgrove
Assignee: Paul Robinson
Priority: Critical
Fix For: 5.0.0.M6
JBoss Narayana Quickstarts: Simple WS-AT Web service, bridged to and from JTA. Bridges three server failed - see referenced job
--
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, 2 months
[JBoss JIRA] (JBTM-1971) Cannot browse logs with the LogBrowser tool
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1971?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1971:
-----------------------------------
Attachment: jstack.LogBrowser
Thread dump from running the browser with the command:
{noformat}
java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreType="com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor" -Dcom.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqJournalEnvironmentBean.storeDir=<path to HornetqJournalStore>/com.arjuna.ats.arjuna.tools.log.LogBrowser
{noformat}
> Cannot browse logs with the LogBrowser tool
> -------------------------------------------
>
> Key: JBTM-1971
> URL: https://issues.jboss.org/browse/JBTM-1971
> 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: Tom Jenkinson
> Attachments: jstack.LogBrowser
>
>
> I tried browsing some logs using the command:
> {noformat}
> java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
> {noformat}
> This gives an interactive command line. I then had a go at listing some logs using:
> {noformat}
> -> select AtomicAction
> -> ls
> {noformat}
> The tool does not find any logs even though there are entries in the directory:
> {code}
> <path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> {code}
> The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
> Also running the tool to view Hornetq store logs 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)
--
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, 2 months
[JBoss JIRA] (JBTM-1971) Cannot browse logs with the LogBrowser tool
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1971?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1971:
-----------------------------------
Description:
I tried browsing some logs using the command:
{noformat}
java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
{noformat}
This gives an interactive command line. I then had a go at listing some logs using:
{noformat}
-> select AtomicAction
-> ls
{noformat}
The tool does not find any logs even though there are entries in the directory:
{code}
<path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
{code}
The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
Also running the tool to view Hornetq store logs 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)
was:
I tried browsing some logs using the command:
{noformat}
java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
{noformat}
This gives an interactive command line. I then had a go at listing some logs using:
{noformat}
-> select AtomicAction
-> ls
{noformat}
The tool does not find any logs even though there are entries in the directory:
{code}
<path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
{code}
The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
Also running the tool to view Hornetq store logs 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
> Cannot browse logs with the LogBrowser tool
> -------------------------------------------
>
> Key: JBTM-1971
> URL: https://issues.jboss.org/browse/JBTM-1971
> 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: Tom Jenkinson
>
> I tried browsing some logs using the command:
> {noformat}
> java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
> {noformat}
> This gives an interactive command line. I then had a go at listing some logs using:
> {noformat}
> -> select AtomicAction
> -> ls
> {noformat}
> The tool does not find any logs even though there are entries in the directory:
> {code}
> <path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> {code}
> The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
> Also running the tool to view Hornetq store logs 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)
--
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, 2 months
[JBoss JIRA] (JBTM-1971) Cannot browse logs with the LogBrowser tool
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1971?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1971:
-----------------------------------
Description:
I tried browsing some logs using the command:
{noformat}
java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
{noformat}
This gives an interactive command line. I then had a go at listing some logs using:
{noformat}
-> select AtomicAction
-> ls
{noformat}
The tool does not find any logs even though there are entries in the directory:
{code}
<path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
{code}
The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
Also running the tool to view Hornetq store logs 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
was:
I tried browsing some logs using the command:
{noformat}
java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
{noformat}
This gives an interactive command line. I then had a go at listing some logs using:
{noformat}
-> select AtomicAction
-> ls
{noformat}
The tool does not find any logs even though there are entries in the directory:
{code}
<path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
{code}
The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
> Cannot browse logs with the LogBrowser tool
> -------------------------------------------
>
> Key: JBTM-1971
> URL: https://issues.jboss.org/browse/JBTM-1971
> 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: Tom Jenkinson
>
> I tried browsing some logs using the command:
> {noformat}
> java -Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.objectStoreDir=<path to logs> com.arjuna.ats.arjuna.tools.log.LogBrowser
> {noformat}
> This gives an interactive command line. I then had a go at listing some logs using:
> {noformat}
> -> select AtomicAction
> -> ls
> {noformat}
> The tool does not find any logs even though there are entries in the directory:
> {code}
> <path_ to_logs>/ShadowNoFileLockStore/defaultStore/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
> {code}
> The problem is that the LogBrowser.listLogs operation uses the the type (AtomicAction) as the parameter to the call StoreManager.getRecoveryStore().allObjUids(type, buff)) but the actual type of an AtomicAction log is "/StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction";
> Also running the tool to view Hornetq store logs 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
--
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, 2 months