[JBoss JIRA] (JBTM-1312) build-release-pkgs.xml contains 4.17.0.Final version number
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1312:
-----------------------------------
Summary: build-release-pkgs.xml contains 4.17.0.Final version number
Key: JBTM-1312
URL: https://issues.jboss.org/browse/JBTM-1312
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.M2, 4.17.3
See: https://github.com/jbosstm/narayana/blob/master/build-release-pkgs.xml for 4.17 and master.
Notice:
{code}
<!-- The tag as it appears under svnbase -->
<property name="pageName" value="4_17_0_Final"/>
<property name="tag" value="4.17.0.Final"/>
{code}
I assume this should be set to the current release. Also, we need to update the release procedure to understand the '_' notation used in the 'pageName' property.
This is assuming that these properties are even needed? They appear to be svn related, in which case not needed for Narayana 4.17 and 5.
--
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, 6 months
[JBoss JIRA] (JBTM-1308) JBOSS 7.1 TM Quickstart - Missing JAR Files for org.jboss.narayana.txframework.api.annotation.service.ServiceRequest e Transactional Annotations
by Marco Mendes (JIRA)
Marco Mendes created JBTM-1308:
----------------------------------
Summary: JBOSS 7.1 TM Quickstart - Missing JAR Files for org.jboss.narayana.txframework.api.annotation.service.ServiceRequest e Transactional Annotations
Key: JBTM-1308
URL: https://issues.jboss.org/browse/JBTM-1308
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TxBridge
Affects Versions: 5.0.0.M1
Environment: JBOSS 7.1.1; OS/X 10.8
Reporter: Marco Mendes
Assignee: Paul Robinson
I couldn't find the JAR files for the two classes below. I have tried maven dependencies, Nexus repository and also the JBOSS TM 5.0 libraries.
import org.jboss.narayana.txframework.api.annotation.service.ServiceRequest;
import org.jboss.narayana.txframework.api.annotation.transaction.Transactional;
The code excerpt is here:
@Transactional //By default bridge from WS-AT to JTA
@Stateless
@Remote(RestaurantServiceAT.class)
@WebService(serviceName = "RestaurantServiceATService", portName = "RestaurantServiceAT", name = "RestaurantServiceAT", targetNamespace = "http://www.jboss.org/narayana/quickstarts/wsat/simple/Restaurant")
@SOAPBinding(style = SOAPBinding.Style.RPC)
@TransactionAttribute(TransactionAttributeType.MANDATORY) // default is REQUIRED
public class RestaurantServiceATImpl implements RestaurantServiceAT {
....
@WebMethod
@ServiceRequest
public void makeBooking(int numSeats) {
....
Are these annotations (@Transactional/@ServiceRequest) deprecated? If not, which libraries contain these classes.
--
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, 6 months
[JBoss JIRA] (JBTM-1303) WS-AT client can return from commit before all participants have committed
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1303:
-----------------------------------
Summary: WS-AT client can return from commit before all participants have committed
Key: JBTM-1303
URL: https://issues.jboss.org/browse/JBTM-1303
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: later
Normally, when a WS-AT client calls commit, the coordinator will wait until all participants are committed before returning to the client. This ensures that the Client doesn't continue processing until all changes have been made permanent and visible.
If the participant takes longer than 30s to return the 'committed' message, the participant logs the fact and then returns to the client. The recovery mechanism will then handle the sending of the commit message to the participant. As WS-AT doesn't support heuristics, the participant is guaranteed to commit eventually, but after at least one recovery scan. This means that the client may think that the work done, in the transaction, is now visible when in actual fact it is not quite yet.
h4. Potential solutions
h3. Return CommittingException
As a JBoss only solution (it would break the standard), we could throw a CommittingException when the coordinator returns control to the client after delegating to the recovery manager to commit the outstanding participant(s). The client then know that the work will commit, but it's not completed yet. Handling of this exception could be to either ignore it, or poll the resource until the change is visible. This could work for both synchronous and asynchronous clients.
h3. Delay the return until participants really have committed.
This is unlikely to work for the (JBoss only) synchronous client as the connection is unlikely to stay open long enough. However, it could work for the asynchronous scenario, but would require the client to increase the timeout to include the amount of time it takes for the coordinator to give up waiting for committed and delegate to the recovery manager, plus enough time for the recovery scan to occur and receive the committed message. Also, the client endpoint information would need to be stored in the recovery log, so that the recovery manager can attempt notification (which would also need implementing).
h3. Document the issue for now
... and implement a solution if/when we get a user with this problem.
--
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, 6 months
[JBoss JIRA] (JBTM-1300) Improve performance of ArjunaCore
by Mark Little (JIRA)
Mark Little created JBTM-1300:
---------------------------------
Summary: Improve performance of ArjunaCore
Key: JBTM-1300
URL: https://issues.jboss.org/browse/JBTM-1300
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Transaction Core
Affects Versions: 4.17.0
Reporter: Mark Little
Assignee: Tom Jenkinson
Fix For: 6.0.0.Final
There are a number of areas where we can improve the performance of ArjunaCore and get a knock-on improvement in JTA and JTS.
--
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, 6 months
[JBoss JIRA] (JBTM-1280) TXFramework Tests output is mallformed
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1280:
-----------------------------------
Summary: TXFramework Tests output is mallformed
Key: JBTM-1280
URL: https://issues.jboss.org/browse/JBTM-1280
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: TXFramework
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
See:
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.narayana.txframework.functional.ATBridgeTest
Running org.jboss.narayana.txframework.functional.ATStatefullTest
Running org.jboss.narayana.txframework.functional.ATTest
Running org.jboss.narayana.txframework.functional.BACoordinatorCompletionTest
Running org.jboss.narayana.txframework.functional.BAParticipantCompletionTest
Running org.jboss.narayana.txframework.functional.JAXWSHandlerAnnotatonTest
Running org.jboss.narayana.txframework.functional.rest.at.simpleEJB.ClientTXInterceptorTest
Running org.jboss.narayana.txframework.functional.rest.at.simpleEJB.IndirectTXManagementTest
Running org.jboss.narayana.txframework.impl.handlers.wsat.WSATDurable2PCParticipantTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec
Running org.jboss.narayana.txframework.impl.handlers.wsat.WSATVolatile2PCParticipantTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec
Running org.jboss.narayana.txframework.impl.handlers.wsba.WSBACoordinatorCompletionParticipantTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec
Running org.jboss.narayana.txframework.impl.handlers.wsba.WSBAParticipantCompletionParticipantTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.061 sec
Results :
Tests in error:
Tests run: 29, Failures: 0, Errors: 9, Skipped: 0
{code}
Notice that "Tests run: ..." is only shown for the later tests. This is annoying as some tests have failed, but we don't see which as the output is missing.
--
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, 6 months