Menu

#910 Fordiac-IDE freeze at Deployment in Linux

1.6
closed-fixed
nobody
deployment (5)
4DIAC-IDE
Bug
5
2014-09-18
2014-09-02
No

I have followed the instruction in the help document to build Fordiac-IDE form source. I need forte and Fordiac-IDE 64bit build on Linux. I am closely monitoring the development. I was able to build the system and was able to deploy applications. But after few mercurial pull's and updates this system broke and freezes when try to deploy,

Related

Issues: #937

Discussion

  • Zoitl Alois

    Zoitl Alois - 2014-09-02

    I'm using a 64-bit Linux maschine as my main development and testing machine. Could you give more details what you are downloading and where it freezes. So that I could try to reproduce the issue.

     
  • Ashish Gupta

    Ashish Gupta - 2014-09-03

    Here are the details of the system I am using.

    OS: 14.04LTS 64bit
    Kernel: 3.13.0-35-generic
    GNU-GCC: 4.8.2
    JDK: 1.7.0_65 (OpenJDK) 64-Bit
    Eclipse: Eclipse Modeling Tools version Luna Release (4.4.0) with the plugins needed as described in ehelp document.

    Forte:
    I have built forte using cmake with modbus module.

    Fordiac:
    There are about 75 warnings when I build the the project. I have checked all the product dependencies which are 64 in total and all are satisfied.

    1) Clicked on Synchronize
    2) Launched 4DIAC-IDE (Check)
    3) Exported the Eclipse Product to some build directory
    4) Copied the runtime, typelibrary in the build folder for mercurial.
    5) Launched the new 4DIAC-IDE build
    5) Imprted Xplus3 into the workspace
    6) Set the runtime paths for fbrt and forte
    7) In Deployment page: selected the application Xplus3, launched the fbrt at 61505 as required, launched forte at 61499.
    8) Click on Deploy button ... FREEEEEZZZZ.
    9) 2 min later kill the 4DIAC, fbrt and forte.

    Hope this details might help. I tried to debug the code it hangs exactly in deployment part of code.

     
  • Ashish Gupta

    Ashish Gupta - 2014-09-03

    This are the following warning that I get, I thought it might help.

    Description Resource Path Location Type
    "schema/org.fordiac.monitoring.monitoringmanager.exsd" does not reference a schema file. plugin.xml /org.fordiac.monitoring line 4 Plug-in Problem
    Discouraged access: The field 'IExternalToolConstants.ATTR_TOOL_ARGUMENTS' is not API (restriction on required library '/apps/IDE/eclipse/modeling/plugins/org.eclipse.ui.externaltools_3.2.300.v20140327-1949.jar') TestingUtils.java /org.fordiac.fbtester/src/org/fordiac/fbtester/configuration line 58 Java Problem
    Discouraged access: The type 'IExternalToolConstants' is not API (restriction on required library '/apps/IDE/eclipse/modeling/plugins/org.eclipse.ui.externaltools_3.2.300.v20140327-1949.jar') TestingUtils.java /org.fordiac.fbtester/src/org/fordiac/fbtester/configuration line 14 Java Problem
    Discouraged access: The type 'IExternalToolConstants' is not API (restriction on required library '/apps/IDE/eclipse/modeling/plugins/org.eclipse.ui.externaltools_3.2.300.v20140327-1949.jar') TestingUtils.java /org.fordiac.fbtester/src/org/fordiac/fbtester/configuration line 58 Java Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.application line 166 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.application line 176 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.deployment.ui line 46 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.deployment.ui line 52 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.deployment.ui line 62 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 10 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 20 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 30 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.resourceediting line 29 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.util line 25 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.ide.util line 33 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 10 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 24 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 36 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 47 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 61 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 73 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 85 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 100 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 115 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 126 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.monitoring line 140 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 52 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 63 Plug-in Problem
    Element 'action' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 75 Plug-in Problem
    Element 'actionSet' is deprecated plugin.xml /org.fordiac.ide.util line 21 Plug-in Problem
    Element 'actionSet' is deprecated plugin.xml /org.fordiac.monitoring line 136 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.application line 162 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.application line 172 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.deployment.ui line 43 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.deployment.ui line 59 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 6 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 16 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 26 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.ide.resourceediting line 25 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 7 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 21 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 32 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 44 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 58 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 70 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 82 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 96 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 111 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.monitoring line 122 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 49 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 60 Plug-in Problem
    Element 'objectContribution' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 71 Plug-in Problem
    Element 'visibleWhen' is not legal as a child of element 'handler'. plugin.xml /org.fordiac.monitoring line 245 Plug-in Problem
    Referenced class 'org.fordiac.monitoring.object1' in attribute 'objectClass' is not on the plug-in classpath plugin.xml /org.fordiac.monitoring line 125 Plug-in Problem
    Referenced resource 'icons/compositefb16.png' in attribute 'icon' cannot be found plugin.xml /org.fordiac.ide.fbt.typeeditor.network line 10 Plug-in Problem
    Referenced resource 'model/lib.genmodel' in attribute 'genModel' cannot be found plugin.xml /org.fordiac.ide.model line 26 Plug-in Problem
    The extension point 'org.eclipse.ui.actionSets' is deprecated plugin.xml /org.fordiac.ide.util line 20 Plug-in Problem
    The extension point 'org.eclipse.ui.actionSets' is deprecated plugin.xml /org.fordiac.monitoring line 135 Plug-in Problem
    The extension point 'org.eclipse.ui.popupMenus' is deprecated plugin.xml /org.fordiac.ide.application line 161 Plug-in Problem
    The extension point 'org.eclipse.ui.popupMenus' is deprecated plugin.xml /org.fordiac.ide.deployment.ui line 42 Plug-in Problem
    The extension point 'org.eclipse.ui.popupMenus' is deprecated plugin.xml /org.fordiac.ide.onlineedit line 5 Plug-in Problem
    The extension point 'org.eclipse.ui.popupMenus' is deprecated plugin.xml /org.fordiac.ide.resourceediting line 24 Plug-in Problem
    The extension point 'org.eclipse.ui.popupMenus' is deprecated plugin.xml /org.fordiac.monitoring line 6 Plug-in Problem
    The extension point 'org.eclipse.ui.popupMenus' is deprecated plugin.xml /org.fordiac.systemManagement.ui line 48 Plug-in Problem
    The field IExternalToolConstants.ATTR_TOOL_ARGUMENTS is deprecated TestingUtils.java /org.fordiac.fbtester/src/org/fordiac/fbtester/configuration line 58 Java Problem
    The method addAnnotationType(Object) from the type AnnotationPainter is deprecated Output.java /org.fordiac.ide.deployment.ui/src/org/fordiac/ide/deployment/ui/views line 259 Java Problem
    The method evaluateBreakpointResponse(AutomationSystem, Device, String) from the type TCPCommunicationObject is never used locally TCPCommunicationObject.java /org.fordiac.monitoring/src/org/fordiac/monitoring/communication line 259 Java Problem
    The value of the field EthernetDeviceManagementCommunicationHandler.MgrInformation.origMgrID is not used EthernetDeviceManagementCommunicationHandler.java /org.fordiac.ide.deployment.iec61499/src/org/fordiac/ide/deployment/iec61499 line 38 Java Problem
    The value of the field MapToCommand.editor is not used MapToCommand.java /org.fordiac.ide.application/src/org/fordiac/ide/application/commands line 40 Java Problem
    The value of the field SegmentSetConstraintCommand.oldBounds is not used SegmentSetConstraintCommand.java /org.fordiac.ide.systemconfiguration/src/org/fordiac/ide/systemconfiguration/commands line 31 Java Problem
    The value of the field StructuredTextFormatter.grammarAccess is not used StructuredTextFormatter.java /org.fordiac.ide.model/src/org/fordiac/ide/model/structuredtext/formatting line 22 Java Problem
    The value of the field TestElement.historySec is not used TestElement.java /org.fordiac.fbtester/src/org/fordiac/fbtester/model line 45 Java Problem
    The value of the field TestElement.historyUSec is not used TestElement.java /org.fordiac.fbtester/src/org/fordiac/fbtester/model line 46 Java Problem
    The value of the field TestElement.monitoringElementAsArray is not used TestElement.java /org.fordiac.fbtester/src/org/fordiac/fbtester/model line 104 Java Problem
    The value of the local variable lower is not used StructuredTextEmitter.java /org.fordiac.ide.export.forte_1.0.x/src/org/fordiac/ide/export/forte1_0_x line 576 Java Problem

     
  • Zoitl Alois

    Zoitl Alois - 2014-09-03

    I have the same warnings. I think we can ignore them for now. I tried the same steps as you and for me it worked. Therefore I would kindly ask you if you could look in the .metadata directory of your workspace (where your 1499 applications are) and locate the .log file. Maybe there is more information in it.

    One thing that could be is that a firewall or another network issues is blocking the communication between the IDE and the devices.

    Furthermore it would be great if you could run 4DIAC in debug mode and when it blocks try to pause it in the Java debugger and let us know where the threads are hanging.

     
  • Ashish Gupta

    Ashish Gupta - 2014-09-03

    I have tried to debug the code to isolate the Freeze issue.

    I found that code hangs in the file:
    src/org/fordiac/ide/deployment/DeploymentCoordinator.java

    at about line 829 in try catch region. If I comment this try catch region, I get no freeze of code but nothing happens.

    I do get Progress Monitor Dialog if code is not commented but freeze exactly at this line:

    new ProgressMonitorDialog(Display.getDefault().getActiveShell())
    .run(true, true, download);

    Hope it helps.

    Ashish

     
  • Zoitl Alois

    Zoitl Alois - 2014-09-04

    Dear Ashish,

    I just noted that I missed one thing in your system description. You are using Eclipse Luna. As you can see in this post: https://sourceforge.net/p/fordiac/discussion/708250/thread/77c8b345/ we have been investigating Luna but sofar we couldn't get a proper 4DIAC version running on it. Could you for now please switch back to Eclipse Keppler?

    If you like to investigate this issue further (which would be a great help for us): The line you are mentioning should lead to the execution of the function

    public void run(final IProgressMonitor monitor)

    which you can find in line 291 in the same file. Maybe you can step through it so that we can find more clearly where it hangs.

    Thanks,
    Alois

     
  • Zoitl Alois

    Zoitl Alois - 2014-09-09

    Today I finally found some time to resemble your case with Eclipse Luna. I didn't experience any issues here. Therefore it really would be great if we could have your .log file maybe we can see more there.

     
  • Ashish Gupta

    Ashish Gupta - 2014-09-15

    Thanks for looking into this matter. I started investigating this issue futher and found the following difference.
    I was running the whole system withing vmware vm and probably due to network issues processes might not be communicationg with each other. So I tried the same build with same environment on linux hosted system and found that whole system also works fine when build with eclipse luna.

    I hope this freeze problem may be virtual machine issue all time long.

    Thanks

     
  • Zoitl Alois

    Zoitl Alois - 2014-09-15
    • labels: --> deployment
    • status: open --> closed-invalid
    • Group: FORTE --> 4DIAC-IDE
    • Milestone: 1.5.x --> 1.6
     
  • Zoitl Alois

    Zoitl Alois - 2014-09-15

    I also want to thank you for spending quite some time in tracking it down. It gave me some reason for further testing Eclipse Luna, which seems to work quite fine now. at least on my machine.

    I closed this issue for now. Although it is rather strange that the IDE freezes because there are several time outs in this code which should fire when there communication problems. Please come back to us if you are experiencing similar issues.

     
  • Ashish Gupta

    Ashish Gupta - 2014-09-16

    Hello Aoitl,
    Finally I decided to tackle this problem and found that in file

    org.fordiac.ide.deployment.iec61499/src/org/fordiac/ide/deployment/iec61499/EthernetDeviceManagementCommunicationHandler.java

    Code hangs because it is not able to create socket in connect method. It hangs at 
    socket = new Socket(mgrInfo.iP, mgrInfo.port);
    

    which is completely out of my understanding, Parameters are correct and this line is also not throwing IOException, but hangs.

    This may give some light why I am experiencing the freeze problem.
    

    Thanks
    Ashish

     
  • Zoitl Alois

    Zoitl Alois - 2014-09-17

    Hi,

    I googled quite some time and it also not clear for me why it is hanging. During deployment there should be a progress dialog with a cancle button. What happens when you press the cancle button?

    Cheers,
    Alois

     
  • Ashish Gupta

    Ashish Gupta - 2014-09-17

    Good News ! Solved the problem. Good news it is not related to code. It was the network proxy issue which was causing Socket constructor to hang. I am now able to build and run the system on both Kepler and Luna eclipse environment.

    I am wondering where can I find the FBRT latest runtime which comes with the packaged released.

     
  • Zoitl Alois

    Zoitl Alois - 2014-09-18
    • status: closed-invalid --> closed-fixed
     
  • Zoitl Alois

    Zoitl Alois - 2014-09-18

    These are great news. In addition I dug further and I found out that we are using a connection method in the 4DIAC-IDE which may block for a very long time. Therefore I have rewritten the connection code so that it will also use the timeout value from the preferences. Now even in network configuration errors the IDE should not block any more.

    The fix is available in cset [fordiac-ide:8a0a6f]

    Regarding your fbrt question could you please put this in a separate post into the forum so that we don't mix up different topics in one thread.

     

    Related

    Commit: [8a0a6f]


Log in to post a comment.