Service Virtualization

Expand all | Collapse all

Broker Agent issue

  • 1.  Broker Agent issue

    Posted 12-15-2016 11:40 AM

    Hello,

     

    I try to start a java agent:

     

    -javaagent:"D:\opt\CA\DevTest\DevTest-8.4\agent\LisaAgent2.jar=url=tcp://XX.XX.XX.XX:2009,name=JBtest2"

     

    it's started:

    There is no rules.properties and rules.xml file. No custom rules loaded.
    No custom rules loaded from D:\opt\CA\DevTest\DevTest-8.4\agent\rules.xml
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:28:59 CET 2016] Command line: java -Dfile.encoding=Cp1252 -Xmx123m -javaagent:D:\opt\CA\DevTest\DevTest-8.4\agent\LisaAgent2.jar=url=tcp://XX.XX.XX.XX:2009,name=JBtest2 -classpath "D:\DevtestProject\ca-devtest\test_agent_java_sv\bin;D:\opt\CA\DevTest\DevTest-8.4\agent\LisaAgent2.jar" null
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:28:59 CET 2016] Agent Log Path: D:\opt\CA\DevTest\DevTest-8.4\agent\devtest_agent_5732.log
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:28:59 CET 2016] Logging to system out: true
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:28:59 CET 2016] Starting Agent (8.4.0.226)...
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] Broker Connection: tcp://XX.XX.XX.XX:2009
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] Connection to tcp://XX.XX.XX.XX:2009?daemon=true established...
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** Started DevTest Agent
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** Version : 8.4.0.226 [0.0.0.0][5.3.1.2]
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** Name : JBtest2 (-1044428888)
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** OS : Windows 7 6.1 (amd64)
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** VM Version : 1.8.0_51 (25.51-b03)
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** VM Name : 5732@XXXXXXX (Java HotSpot(TM) 64-Bit Server VM)
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** User Dir : D:\DevtestProject\ca-devtest\test_agent_java_sv
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** Agent Dir : D:\opt\CA\DevTest\DevTest-8.4\agent
    [DevTest AGENT:A][INFO][5732][1][main][Thu Dec 15 17:29:00 CET 2016] *** PID : 5732
    [DevTest AGENT:A][INFO][5732][1][main][12/15 17:29:00 (684)] setMainAndArgs - Main class :test_agent_java_sv.test
    [DevTest AGENT:A][INFO][5732][1][main][12/15 17:29:00 (694)] *** FCmd Line : java -Dfile.encoding=Cp1252 -Xmx123m -javaagent:D:\opt\CA\DevTest\DevTest-8.4\agent\LisaAgent2.jar=url=tcp://XX.XX.XX.XX:2009,name=JBtest2 -classpath "D:\DevtestProject\ca-devtest\test_agent_java_sv\bin;D:\opt\CA\DevTest\DevTest-8.4\agent\LisaAgent2.jar" test_agent_java_sv.test
    Retrieve rules from broker with request: return RulesHandler.getAgentRules(-1044428888, true);
    [DevTest AGENT:A][INFO][5732][27][Stats Gathering Thread][12/15 17:29:03 (713)] Starting Dispatching...

     

    in the log in the broker/registry server, in the file log devtest_agent_20753.log:

     

    [DevTest AGENT:C][WARN][20753][159][Agent Info Notifier][Dec 13, 2016 5:08:36 PM] Could not establish connection to Agent broker at tcp://localhost:2009?daemon=true
    [DevTest AGENT:C][WARN][20753][159][Agent Info Notifier][Dec 13, 2016 5:08:48 PM] Could not establish connection to Agent broker at tcp://localhost:2009?daemon=true
    [DevTest AGENT:C][WARN][20753][159][Agent Info Notifier][Dec 13, 2016 5:08:59 PM] Could not establish connection to Agent broker at tcp://localhost:2009?daemon=true
    [DevTest AGENT:C][WARN][20753][159][Agent Info Notifier][Dec 13, 2016 5:09:10 PM] Could not establish connection to Agent broker at tcp://localhost:2009?daemon=true

     

    [DevTest AGENT:C][WARN][20753][825922][qtp988912710-825922][Dec 14, 2016 3:20:19 PM] Broker access failed (com.itko.lisa.remote.plumbing.JMSInvocationException: Cannot reach broker at ssl://localhost:2009?daemon=true). Falling back on direct DB access...
    [DevTest AGENT:C][WARN][20753][821021][qtp988912710-821021][Dec 14, 2016 3:21:15 PM] Broker access failed (com.itko.lisa.remote.plumbing.JMSInvocationException: Cannot reach broker at ssl://localhost:2009?daemon=true). Falling back on direct DB access...
    [DevTest AGENT:C][WARN][20753][821021][qtp988912710-821021][Dec 14, 2016 3:21:15 PM] Broker access failed (com.itko.lisa.remote.plumbing.JMSInvocationException: Cannot reach broker at ssl://localhost:2009?daemon=true). Falling back on direct DB access...

     

    I don't understand Why I have this message.

     

    The agent is visible and in the data base but not running....

     

    TY for your help



  • 2.  Re: Broker Agent issue

    Posted 12-15-2016 02:15 PM

    Please do through "DevTest Java Agent - DevTest Solutions - 8.4 - CA Technologies Documentation " documentation.

     

    Regards,

    -Ankush Sharma



  • 3.  Re: Broker Agent issue

    Posted 12-16-2016 03:43 AM

    Hi, 

     

    Ty but I already saw the documentation, I didn't find the parameter to set the broker url.

     

    The agent and the broker are not on the same machine, in the log you can see it try to connect to localhost.

     

    I tried also to start Broker and agent on the same machine, it's work. So I Think is an issue of configuration.



  • 4.  Re: Broker Agent issue

    Posted 12-16-2016 02:38 AM

    May I know what sort of platform are you trying to install the agent on?



  • 5.  Re: Broker Agent issue

    Posted 12-16-2016 04:05 AM

    The agent's log file looks good as it says that it was able to connect to the broker and to retrieve rules.xml file from broker and starts dispatching. The other log file does not seem to be related to the problem, because its log entries are from Dec, 13th and 14th, while the agent started on Dec, 15th. You may want to check on the log file pfbroker.log on your registry/broker system for any errors or symptoms.



  • 6.  Re: Broker Agent issue

    Posted 12-16-2016 08:11 AM

    Hi Ulrich,

     

    I have this in pfbroker.log:

    2016-12-16 13:04:12,673Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39089] INFO System.out - Dec 16, 2016 1:04:12 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:12,674Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39089] INFO System.out - INFO: Transport failed: java.io.IOException: Unknown data type: -93
    2016-12-16 13:04:12,674Z (13:04) [Async Exception Handler] INFO System.out - Dec 16, 2016 1:04:12 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:12,674Z (13:04) [Async Exception Handler] INFO System.out - INFO: Transport failed: com.itko.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:39089
    2016-12-16 13:04:14,685Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39090] INFO System.out - Dec 16, 2016 1:04:14 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:14,685Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39090] INFO System.out - INFO: Transport failed: java.io.IOException: Unknown data type: -93
    2016-12-16 13:04:14,686Z (13:04) [Async Exception Handler] INFO System.out - Dec 16, 2016 1:04:14 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:14,686Z (13:04) [Async Exception Handler] INFO System.out - INFO: Transport failed: com.itko.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:39090
    2016-12-16 13:04:16,692Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39091] INFO System.out - Dec 16, 2016 1:04:16 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:16,692Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39091] INFO System.out - INFO: Transport failed: java.io.IOException: Unknown data type: -93
    2016-12-16 13:04:16,693Z (13:04) [Async Exception Handler] INFO System.out - Dec 16, 2016 1:04:16 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:16,693Z (13:04) [Async Exception Handler] INFO System.out - INFO: Transport failed: com.itko.activemq.transport.InactivityIOException: Channel was inactive for too long: /127.0.0.1:39091
    2016-12-16 13:04:18,700Z (13:04) [ActiveMQ Transport: tcp:///127.0.0.1:39092] INFO System.out - Dec 16, 2016 1:04:18 PM com.itko.activemq.broker.TransportConnection serviceTransportException
    2016-12-16 13:04:18,700



  • 7.  Re: Broker Agent issue

    Posted 12-16-2016 08:16 AM

    And in my rules.xml, I have this:

     

    <?xml version="1.0" encoding="UTF-8"?><rules>
    <agent guid="-1208215149" name="testAgent">
    <feature name="POJO" weight="4"/>
    <feature name="EJB" weight="4"/>
    <feature name="JDBC" weight="4"/>
    </agent>
    <agent guid="-2032180703" name="DEFAULT"/>
    <!--************ Console ************-->
    <console>
    <property comment="if MQ goes down, wait this many millis before attempting to reconnect." key="MQMIRROR_CONNECT_INTERVAL" value="5005"/>
    <property comment="A regular expression to match queue names we are interested in. By default we will inspect all queues. Be careful to quote any dot characters in the queue names! If this property is left undefined we will include all queue names" key="MQMIRROR_INCLUDE_QUEUES" value=""/>
    </console>
    </rules>



  • 8.  Re: Broker Agent issue

    Posted 12-16-2016 08:57 AM

    I tried to do a netstat on the broker server:

     

    and a telnet from the agent laptop "telnet 10.64.100.52 2009" :



  • 9.  Re: Broker Agent issue

    Posted 01-13-2017 11:04 AM

    Julien,

    Since you opened up a support case (00632628) regarding this issue, we will handle this issue in this case.