[
https://issues.jboss.org/browse/JBTM-2345?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2345:
----------------------------------------
Would we need a variant of WFLY-1119 (Assign an unique NodeID automatically) to avoid
conflicts (ie would different images share the same JDBC store).
Also it is possible to point the tooling (ObjStoreBrowser) at a filesystem to manage the
logs although it is unsupported (normally it is done via a JMX browser connected to the TM
process). Do we need similar functionality for accessing the JDBC store directly?
Off image storage for docker transaction service
------------------------------------------------
Key: JBTM-2345
URL:
https://issues.jboss.org/browse/JBTM-2345
Project: JBoss Transaction Manager
Issue Type: Feature Request
Components: Build System, JTS
Affects Versions: 5.0.4
Reporter: Mark Little
Assignee: Tom Jenkinson
Labels: docker
Now we have a docker image for JTS we need to look at making the state available after
the image(s) go away. Remember that docker produces immutable images, so any state change
that occurs within the running instance will be lost when the image dies, is taken out of
service etc. Currently the docker image for JTS we have will store all of the transaction
log information within the image, which is fine for testing purposes but not for a running
deployment.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)