[JBoss JIRA] (JBTM-2856) Add a way to register an interposed synchronization without associating the txn
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/JBTM-2856?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2856:
-----------------------------------
Assignee: (was: Amos Feng)
> Add a way to register an interposed synchronization without associating the txn
> -------------------------------------------------------------------------------
>
> Key: JBTM-2856
> URL: https://issues.jboss.org/browse/JBTM-2856
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Application Server Integration
> Reporter: David Lloyd
> Priority: Major
>
> It would be very useful to the application server if there were an API method to register an interposed synchronization on a transaction that was not currently associated with the calling thread, the same way that non-interposed synchronizations can be. Right now the only two options are to use TransactionSynchronizationRegistry, which requires that the existing transaction be suspended and a new one associated, or to use reflection to directly call the registerSynchronizationImple method of the transaction. Neither one is optimal.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-2827) No easy way to acquire node name from JBoss Transaction SPI
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/JBTM-2827?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2827:
-----------------------------------
Assignee: (was: Amos Feng)
> No easy way to acquire node name from JBoss Transaction SPI
> -----------------------------------------------------------
>
> Key: JBTM-2827
> URL: https://issues.jboss.org/browse/JBTM-2827
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Application Server Integration
> Reporter: David Lloyd
> Priority: Minor
>
> There's no good way to get the node identifier string for the local transaction environment using the integration SPIs. I have to use {{com.arjuna.ats.arjuna.common.CoreEnvironmentBean#getNodeIdentifier}} which brings in narayana-jta to make this work.
> It would be nice if this could be gotten from the TransactionManager or perhaps the ExtendedJBossXATerminator.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months
[JBoss JIRA] (JBTM-2877) Linkage errors whilst building BlackTie Admin CLI tool on Fedora 25
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/JBTM-2877?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson reassigned JBTM-2877:
-----------------------------------
Assignee: (was: Amos Feng)
> Linkage errors whilst building BlackTie Admin CLI tool on Fedora 25
> -------------------------------------------------------------------
>
> Key: JBTM-2877
> URL: https://issues.jboss.org/browse/JBTM-2877
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie
> Affects Versions: 5.5.5.Final
> Reporter: Michael Musgrove
> Priority: Major
>
> I get linkage errors when building the admin tool on Fedora 25. Note that I have log4cxx-902683-fc18x64.jar in my local repo. The linker errors are:
> [cc] Starting link
> [cc] cxx/test/lib/libblacktie-codec.so: undefined reference to `log4cxx::helpers::MessageBuffer::str[abi:cxx11](log4cxx::helpers::CharMessageBuffer&)'
> [cc] cxx/test/lib/libblacktie-core.so: undefined reference to `log4cxx::helpers::CharMessageBuffer::str[abi:cxx11](log4cxx::helpers::CharMessageBuffer&)'
> [cc] cxx/test/lib/libblacktie-codec.so: undefined reference to `log4cxx::helpers::MessageBuffer::str[abi:cxx11](std::ostream&)'
> [cc] cxx/test/lib/libblacktie-hybrid.so: undefined reference to `log4cxx::helpers::CharMessageBuffer::operator<<(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
> [cc] cxx/test/lib/libblacktie-codec.so: undefined reference to `log4cxx::Logger::forcedLog(log4cxx::helpers::ObjectPtrT<log4cxx::Level> const&, std::__cxx11::basic_string<char, std::char_traits<char>, std
> ::allocator<char> > const&, log4cxx::spi::LocationInfo const&) const'
> [cc] collect2: error: ld returned 1 exit status
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 11 months