INT-2184 Lifecycle Problem With TCP OB Adapter
Autostartup defaulted to false and isRunning() returned the status of the associated connection factory instead of its own status. Precluded it being started because LifeCycle processor thought it was already started.
This commit is contained in:
committed by
Mark Fisher
parent
559bab4750
commit
7c3f2ee8c4
@@ -57,7 +57,7 @@ public class TcpSendingMessageHandler extends AbstractMessageHandler implements
|
||||
|
||||
private Map<String, TcpConnection> connections = new ConcurrentHashMap<String, TcpConnection>();
|
||||
|
||||
private volatile boolean autoStartup;
|
||||
private volatile boolean autoStartup = true;
|
||||
|
||||
private volatile int phase;
|
||||
|
||||
@@ -233,9 +233,7 @@ public class TcpSendingMessageHandler extends AbstractMessageHandler implements
|
||||
}
|
||||
|
||||
public boolean isRunning() {
|
||||
boolean cfRunning = this.clientConnectionFactory != null ? this.clientConnectionFactory.isRunning() : false;
|
||||
boolean sfRunning = this.serverConnectionFactory != null ? this.serverConnectionFactory.isRunning() : false;
|
||||
return cfRunning | sfRunning;
|
||||
return this.active;
|
||||
}
|
||||
|
||||
public int getPhase() {
|
||||
|
||||
Reference in New Issue
Block a user