Description:
Description:
============
Users can specify the following two properties to set the Transaction Log configuration in a Node.
amf.node.txlogsize - The log size in KB, per log file. The minimum setting is 20.
amf.node.txlognum - The number of log files. The minimum setting is 2.
These properties can be set either in the node TRA file or in the Node configuration screen in the Admininstrator UI. There is a known limitation with the use of these properties. They can only be specified at the time the Node is created.

Environment:
==========
  •  AMSG 3.1.2 with ActiveMatrix Platform 3.1.2 HF4 and higher
  •  AMSG 3.1.3 with ActiveMatrix Platform 3.1.3 HF1 and higher
  •  AMSG 3.1.5 with or without ActiveMatrix Platform 3.1.5 hotfixes
  •  AMSB 3.1.2 with ActiveMatrix Platform 3.1.2 HF4 and higher
  •  AMSB 3.1.5 with or without ActiveMatrix Platform 3.1.5 hotfixes
  •  BPM 1.1.x with ActiveMatrix Platform 3.1.2 HF4 and higher
  •  BPM 1.2.x with ActiveMatrix Platform 3.1.3 HF1 and higher
  •  BPM 1.3.x with or without ActiveMatrix Platform 3.1.5 hotfixes
  •  BWSE 5.9.2 with ActiveMatrix Platform 3.1.2 HF4 and higher
  •  BWSE 5.9.3 with or without ActiveMatrix Platform 3.1.5 hotfixes

Symptoms:
=========
If a user tries to modify the value of these properties after a Node has been created, they will see the following error:
BPM.log:       org.objectweb.howl.log.LogConfigurationException: Configured file size [50000] blocks not equal previous file size [2147483647] blocks
BPM.log:        at org.objectweb.howl.log.LogFileManager.validateFileHeader(LogFileManager.java:1072)
BPM.log:        at org.objectweb.howl.log.LogFileManager.init(LogFileManager.java:901)
BPM.log:        at org.objectweb.howl.log.Logger.open(Logger.java:314)
BPM.log:        at org.objectweb.howl.log.xa.XALogger.open(XALogger.java:893)
BPM.log:        at org.apache.geronimo.transaction.log.HOWLLog.doStart(HOWLLog.java:224)

Resolution:
=========
The resolution for this issue is to revert the Transaction Log configuration settings back to the original values.
Symptoms:

Cause:

There is a known limitation when using amf.node.txlogsize and amf.node.txlognum properties to set the Transaction Log configuration in a Node.