CA Service Management

 View Only
  • 1.  QA hostname in DEV after upgrade and migration

    Posted Sep 20, 2019 12:51 AM

    Team,

    We upgraded our Dev system to 17.2 and migrated data from QA system after that we are seeing below error. Can someone suggest what might have gone wrong and how can this be resolved.


    2019/09/19 18.42.00.852 WARN  [triggerStartAsyncNetworkBridgeCreation: remoteBroker=tcp://<<QA secondary hostname>>/<<QA secondary ip address>>:7777@53047, localBroker= vm://brkr-D0A9D26A1E5747E2B8E7BE49127F15FA#390] [TransportConnection] Failed to add Connection brkr-D0A9D26A1E5747E2B8E7BE49127F15FA->brkr-2470E40C751C47088D1A38FC67F95849-50919-1568930950575-197:12019/09/19 18.42.00.852 WARN  [triggerStartAsyncNetworkBridgeCreation: remoteBroker=tcp://UI1Q1AP316X/10.168.58.109:7777@53047, localBroker= vm://brkr-D0A9D26A1E5747E2B8E7BE49127F15FA#390] [TransportConnection] Failed to add Connection brkr-D0A9D26A1E5747E2B8E7BE49127F15FA->brkr-2470E40C751C47088D1A38FC67F95849-50919-1568930950575-197:1javax.jms.InvalidClientIDException: Broker: brkr-D0A9D26A1E5747E2B8E7BE49127F15FA - Client: nc-D0A9D26A1E5747E2B8E7BE49127F15FA_brkr-2470E40C751C47088D1A38FC67F95849_inbound_brkr-D0A9D26A1E5747E2B8E7BE49127F15FA already connected from vm://brkr-D0A9D26A1E5747E2B8E7BE49127F15FA#6 at org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:246) at org.apache.activemq.broker.jmx.ManagedRegionBroker.addConnection(ManagedRegionBroker.java:231) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92) at org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:89) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92) at org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:92) at org.apache.activemq.security.SimpleAuthenticationBroker.addConnection(SimpleAuthenticationBroker.java:103) at org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:97) at org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:764) at org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139) at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148) at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116) at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50) at org.apache.activemq.transport.vm.VMTransport.doDispatch(VMTransport.java:138) at org.apache.activemq.transport.vm.VMTransport.dispatch(VMTransport.java:130) at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:107) at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:68) at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:81) at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:86) at org.apache.activemq.network.DemandForwardingBridgeSupport.startLocalBridge(DemandForwardingBridgeSupport.java:453) at org.apache.activemq.network.DemandForwardingBridgeSupport.doStartLocalAndRemoteBridges(DemandForwardingBridgeSupport.java:420) at org.apache.activemq.network.DemandForwardingBridgeSupport.access$500(DemandForwardingBridgeSupport.java:105) at org.apache.activemq.network.DemandForwardingBridgeSupport$5.run(DemandForwardingBridgeSupport.java:335) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)


  • 2.  RE: QA hostname in DEV after upgrade and migration
    Best Answer

    Broadcom Employee
    Posted Sep 20, 2019 04:14 AM
    Hi Rajasheker,

    I suspect you skipped a few things. Did you follow the steps documented on the link below to the core?

    https://docops.ca.com/ca-service-management/17-2/en/administering/moving-the-ca-mdb-data-from-the-source-to-the-target-systems/moving-the-ca-mdb-database-on-microsoft-sql-server


    ------------------------------
    Kind Regards,
    Brian
    ------------------------------