[jbossts-issues] [JBoss JIRA] Updated: (JBTM-389) TransactionStatusManager and Recovery integration without Sockets

Dmitri Voronov (JIRA) jira-events at lists.jboss.org
Tue Aug 5 08:42:57 EDT 2008

     [ https://jira.jboss.org/jira/browse/JBTM-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitri Voronov updated JBTM-389:

    Attachment: jboss-jta-without-sockets.zip

> TransactionStatusManager and Recovery integration without Sockets
> -----------------------------------------------------------------
>                 Key: JBTM-389
>                 URL: https://jira.jboss.org/jira/browse/JBTM-389
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Application Server Integration
>    Affects Versions: 4.2.3
>         Environment: JBoss 4.2.3
>            Reporter: Dmitri Voronov
>         Attachments: jboss-jta-without-sockets.zip
> In the current JBoss integration the communication within arjuna occurs over Sockets whereby the communication is within the same JVM and doesn't need to use any socket or listen on any ports.
> This requires a configuration overhead, if the ports should be determined. If no ports have been configured, the next free port is opened.
> In our environment we manage the port ranges per JBoss instance, e.g.  https, rmi etc.
> My suggestion is to use piped streams (see attachment) ; it would prevent the changes on Arjuna's API and the internal algorithms.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list