October 2013 - jbossts-issues - Jboss List Archives

[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"; 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 (see attached jstack dump) > 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"; -- 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

1
0
0 / 0

[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: ----------------------------------- Assignee: Mark Little (was: Tom Jenkinson) > 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: Mark Little > > 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"; -- 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

1
0
0 / 0

[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: ----------------------------------- Comment: was deleted (was: 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 > > 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

1
0
0 / 0

[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: (was: jstack.LogBrowser) > 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

1
0
0 / 0

[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: ----------------------------------- Attachment: jstack.LogBrowser > 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 > 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) -- 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

1
0
0 / 0

[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 commented on JBTM-1975: ---------------------------------------- The attached thread dump is from running 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} > 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 > 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) -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1975) LogBrowser tool hangs on exit when browsing the HornetqJournalStore

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1975: -------------------------------------- Summary: 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 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) -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1973) wsat-jta jta bridge quickstart failure

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1973?page=com.atlassian.jira.plugin.... ] Gytis Trikleris resolved JBTM-1973. ----------------------------------- Fix Version/s: (was: 5.0.0.M6) Resolution: Rejected > 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 > Attachments: quickstart-output.zip > > > 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1961) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: txstatus=TransactionActive

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1961?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1961: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: txstatus=TransactionActive > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1961 > URL: https://issues.jboss.org/browse/JBTM-1961 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M6 > > > http://172.17.131.2/job/narayana-quickstarts-windows2008-taconic/472/console > CI failure after adding JBTM-1958 (required update) > I suspect that there are multiple RTS participants launching on the same URL from the different servers in this quickstart -- 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

1
0
0 / 0

[JBoss JIRA] (JBTM-1973) wsat-jta jta bridge quickstart failure

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1973?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1973: --------------------------------------- I'm still working on it, and it is just a pull request failure > 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 > > Attachments: quickstart-output.zip > > > 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2013