[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2308.
-------------------------------
> New JTS record types are not showing up in the tooling
> ------------------------------------------------------
>
> Key: JBTM-2308
> URL: https://issues.jboss.org/browse/JBTM-2308
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Tooling
> Affects Versions: 4.17.23, 5.0.3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 4.17.27, 5.2.0
>
>
> When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record.
> I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it).
> What is missing is instrumentation for new types:
> {code}
> AssumedCompleteHeuristicTransaction
> AssumedCompleteHeuristicServerTransaction
> AssumedCompleteTransaction
> AssumedCompleteServerTransaction
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (JBTM-2365) Create feature choice helper on narayana.io
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2365?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2365.
-------------------------------
> Create feature choice helper on narayana.io
> -------------------------------------------
>
> Key: JBTM-2365
> URL: https://issues.jboss.org/browse/JBTM-2365
> Project: JBoss Transaction Manager
> Issue Type: Task
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.2.0
>
>
> It would be useful to have something on our homepage that lists all the different transports we use and what features are available when you select each of those transport. Mainly all features are available which allows us to list those too.
> Ideally in the future it might replace our current landing page so we should try to include all details from that too where possible - so you could include an axis that said "commercial support available" STM = No, XTS = yes and so on.
> Needs experimentation to see what will work best.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months
[JBoss JIRA] (JBTM-2452) External Queues BlackTie quickstart no longer works with Artemis
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2452?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2452.
-------------------------------
> External Queues BlackTie quickstart no longer works with Artemis
> ----------------------------------------------------------------
>
> Key: JBTM-2452
> URL: https://issues.jboss.org/browse/JBTM-2452
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie, Demonstrator
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 5.2.0
>
>
> Current failures:
> http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts/224/console
> http://albany.eng.hst.ams2.redhat.com/job/narayana-quickstarts-catelyn/79...
> This is currently preventing release.
> {code}
> [exec] /home/hudson/workspace/narayana-quickstarts/blacktie
> [exec] Quickstart: Running externally managed queue quickstart
> [exec]
> [exec] BUILD SUCCESSFUL
> [exec] Total time: 3 seconds
> [exec] 2015-07-06 16:26:57,606 [0x7f32e8031760] WARN (HybridSocketSessionImpl :490 ) - Got an error: javax.naming.NameNotFoundException: queue/BTR_TestOne -- service jboss.naming.context.java.queue.BTR_TestOne
> [exec] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
> [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> [exec] at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235)
> [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> [exec] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417)
> [exec] at javax.naming.InitialContext.lookup(InitialContext.java:417)
> [exec] at org.codehaus.stomp.jms.StompSession.convertDestination(StompSession.java:119)
> [exec] at org.codehaus.stomp.jms.StompSession.sendToJms(StompSession.java:97)
> [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompSend(ProtocolConverter.java:262)
> [exec] at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:135)
> [exec] at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:101)
> [exec] at java.lang.Thread.run(Thread.java:744)
> [exec]
> [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] WARN (XATMIc :95 ) - Queue Session failure
> [exec] 2015-07-06 16:26:57,607 [0x7f32e8031760] INFO (AtmiBrokerLogc :60 ) - tpacall error: -1 6
> [exec] Unable to queue all messages
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 4 months