Bugzilla – Full Text Bug Listing
| Summary: | Agent Controller crash | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Stoiko Avdjiev <stoiko.avdjiev> |
| Component: | TPTP | Assignee: | Igor Alelekov <igor.alelekov> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P1 | CC: | jkubasta, karla.callaghan, samwai, steven.wasleski, umarkova |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=166504 | ||
| Whiteboard: | closed471 | ||
Changed component to Platform.Communication as the problem to be addressed here is not with the agent, but with the Agent Controller crashing. Bug 166504 should resolve the issue with the timeout. This bug is intended to address the issue of the AC crashing when the timeout occurs. Note that the AC is running on Windows XP (the java client is on zOS). Added effort estimate: 3 days (difficulty will likely be in reproducing the failure w/o access to zOS system). We are ready to provide access to our test machines. The needed machines are one z/OS test machine and one Windows machine. Both machines are located in the IBM network and BSO firewall authentication is needed in order for the machines to be used. Could you please provide an IBM contact on your team who could use these machines? URGENT: Please provide a fix for this bug as soon as possible because we can’t exit our System Verification Testing phase without it. Thanks. Joanna/Samson, Can you assist in debugging this issuse on the zOS per Stoiko's request? Stoiko, You have a Severity setting of "normal" and thus we have set a Target of the 4.4 release. What release are you expecting a fix in? We found the problem with Agent Controller 4.3. We could benefit if you can put the fix for as earlier release as you can. I changed the severity to blocker since it blocks our SVT exit. Thanks. Great, please attach the patch or describe the fix so that we can access the risk. There is some misunderstanding. By “found the problem” I mean “experienced the problem”, not that we have debugged it. So unfortunately we don’t have a solution for it. Thanks. Please set priority to P1. Setting priority P1 Updated effort estimate to use Igor's estimate: 5 days. Since this is a zOS bug, need to also allocate time of someone at IBM to assist in the investigation. Hi Stoiko. When you mention the Agent Controller crashed, do you mean the Windows side AC crashes? Igor, if the above is true, I think this can be reproduced using a Windows client running the "ACTest" program provided across a slow network connection. The other bug 166504 is caused by a slow connection and is resolved by adding a method for setting socket timeout. I am just wondering if this is also timing related. When the network connection from the client to the Agent Controller (on Windows) is slow, the client times out and the AC crashes. *** This bug has been marked as a duplicate of bug 171418 *** As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |
Build ID: I20050401-1645 Steps To Reproduce: 1. Sample client of Agent Controller running on z/OS (or with slow enough connection) 2.Agent Controller 4.2 running on Windows XP 3.The client prints "Error while creating the data connectionjava.net.SocketTimeoutException: Read timed out" on the console and the Agent Controller crashes. More information: The problem could be recreated with any Java client running on z/OS connected to Agent Controller running on Windows for example with logging agent, registered by GLA. Example client: import java.net.InetAddress; import org.eclipse.tptp.platform.execution.client.agent.IAgent; import org.eclipse.tptp.platform.execution.client.core.*; import org.eclipse.tptp.platform.execution.util.TPTPDataPath; public class ACTest { public static final String AGENT_CONTROLLER_HOST = "9.182.191.77"; public static final int AGENT_CONTROLLER_PORT = 10006; public static final String AGENT_NAME = "org.eclipse.tptp.legacy.myagent"; public static void main(String args[]) throws Exception { INode acNode = null; ConnectionInfo connInfo = new ConnectionInfo(); acNode = NodeFactory.createNode(AGENT_CONTROLLER_HOST); connInfo.setHostName(AGENT_CONTROLLER_HOST); connInfo.setPort(AGENT_CONTROLLER_PORT); IAgentController ac = acNode.connect(connInfo); IAgent remoteLoggingAgent = ac.getAgent(AGENT_NAME, "org.eclipse.tptp.platform.execution.client.agent.IAgent"); remoteLoggingAgent.startMonitoring(TPTPDataPath.DATA_PATH_RECEIVE, new LoggingAgentDataProcessor()); Thread.sleep(5000); remoteLoggingAgent.releaseAccess(); ac.disconnect(); } private static class LoggingAgentDataProcessor implements IDataProcessor { public void incomingData(byte ignore1[], int ignore2, InetAddress ignore3) {} public void incomingData(char ignore1[], int ignore2, InetAddress ignore3) {} public void invalidDataType(byte ignore1[], int ignore2, InetAddress ignore3) {} public void waitingForData() {} } } We don’t observe the timeout with Windows and Linux clients.