So now i made an upgrade to SwiftMQ 7.0.1.
I started the broker with
java -server -Xmx768M -Xmn768M -cp ../../jars/swiftmq.jar:../../jars/jndi.jar:../../jars/jms.jar:../../jars/jsse.jar:../../jars/jnet.jar:../../jars/jcert.jar:../../jars/dom4j-full.jar:../../jars/jta-spec1_0_1.jar com.swiftmq.HARouter ../../config/replicated/instance1/routerconfig.xml
(master and slave)
Our developers wrote a test-tool that behaves just like our main application concerning JMS.
It works whithin the specifications and I produced 1500 Kb messages in 25 threads a hundred times.
The active Instance (master) reported
+++ High Availability State: ACTIVE/ACTIVE
Got OutOfMemoryError:
ThreadGroup: store.log
ActiveTask : LogProcessor
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
heartbeat counter reaches 0, closing replication connections
+++ High Availability State: STANDALONE/STANDALONE
the slave reported
Got Exception:
ThreadGroup: hacontroller.stagecontroller
ActiveTask : PipelineQueue, dispatchToken=sys$hacontroller.stagecontroller
Stack Trace:
java.lang.NullPointerException
at com.swiftmq.tools.util.DataByteArrayInputStream.setBuffer(Unknown Source)
at com.swiftmq.impl.store.standard_ha.v600.SinkProxyImpl.newReplicationItem(Unknown Source)
at com.swiftmq.impl.hacontroller.standard.v600.stage.StandbyStage.visit(Unknown Source)
at com.swiftmq.impl.hacontroller.standard.v600.smqpha.UpdateDeliveryRequest.accept(Unknown Source)
at com.swiftmq.impl.hacontroller.standard.v600.stage.StandbyStage.process(Unknown Source)
at com.swiftmq.impl.hacontroller.standard.stage.StageController.visit(Unknown Source)
at com.swiftmq.impl.hacontroller.standard.stage.po.PORequestReceived.accept(Unknown Source)
at com.swiftmq.tools.pipeline.PipelineQueue.process(Unknown Source)
at com.swiftmq.tools.queue.SingleProcessorQueue.dequeue(Unknown Source)
at com.swiftmq.tools.pipeline.PipelineQueue$QueueProcessor.run(Unknown Source)
at com.swiftmq.impl.threadpool.standard.PoolThread.run(Unknown Source)
heartbeat counter reaches 0, closing replication connections
and the memory-monitor reported

I can send the test-application (also the source) and our configuration, whatever you need, by mail.
You know my mail-adress from our last official incident.
Maybe it is a problem that just affects Linux?
What can I do?
TIA
Thomas