B4J Question Problem running in debug mode

Discussion in 'B4J Questions' started by BeneBarros, May 21, 2015.

Thread Status:
Not open for further replies.
  1. BeneBarros

    BeneBarros Active Member Licensed User

    I am having problem running in debug mode.
    I get the error message below

    An error occurred.
    Rapid Debugger failed to connect to process. Please try to run again.
    Make sure that no firewall or antivirus block the following ports:8937, 8938, and 59812

    I ran the b4j with the -log option and received the "log.txt" attachment.


    already I tried disabling the firewall and continue generating the same mistake.

    in release mode it works perfectly.

    someone help me ???
     

    Attached Files:

    • log.txt
      File size:
      4.8 KB
      Views:
      48
  2. DarkMann

    DarkMann Member Licensed User

    I don't have a solution to the problem but would add that I've the same issue on one of my PCs.

    My main PC at home works fine, but the one in my work office gives exactly the same problem. It worked fine one day, but simply stopped working in debug with this error the next day.

    Like you I disabled the firewall, reinstalled B4J and even JAVA with no effect.

    David
     
  3. BeneBarros

    BeneBarros Active Member Licensed User

    the strange thing is that some programs run in debug mode and others generate this message.
     
  4. Erel

    Erel Administrator Staff Member Licensed User

  5. DarkMann

    DarkMann Member Licensed User

  6. BeneBarros

    BeneBarros Active Member Licensed User

    updated to the new version.
    congratulations for the excellent work.

    but the problem remains.
     

    Attached Files:

  7. Erel

    Erel Administrator Staff Member Licensed User

    Can you try to temporary disable the anti virus and firewall?
     
  8. BeneBarros

    BeneBarros Active Member Licensed User

    I tested now with avast and disabled the firewall and the result was the same.

    I'll try on another PC I have here.
    inform shortly after the result has
     
  9. DarkMann

    DarkMann Member Licensed User

    Still no luck. Disabled AV and windows firewall. I still get the same error even with Beta7.

    Just to re-iterate: it was working fine on this PC one day, when I came to use it again the next then it simply didn't work any more. as far as I'm aware, no updates to anything on the Pc happened in the time between it working and not working, although there was probably an AV update. That would have happened on my hmoe PC as well, but everything still works there.

    David
     
  10. giga

    giga Well-Known Member Licensed User

    Do you recall what day this started happening? You could try system restore as a worst cause scenario inside system restore if you look at the previous dates it will show you what windows updates were conducted.
     
  11. BeneBarros

    BeneBarros Active Member Licensed User

    I tried on another PC but also returned the same error only in debug mode, in release mode works normally ..
    The other programs I have work perfectly in all modes.
    I will try to dismantle the project step by step, and test at each step.
     
  12. Erel

    Erel Administrator Staff Member Licensed User

  13. DarkMann

    DarkMann Member Licensed User

    Attached Files:

    • log.txt
      File size:
      5.2 KB
      Views:
      37
  14. Erel

    Erel Administrator Staff Member Licensed User

    Thank you.

    All that we can see from the logs is that the rapid debugger engine failed to connect to the app process. Does it happen with every app you try?
     
  15. DarkMann

    DarkMann Member Licensed User

    Yes Erel, it happens for every app that I've tested with. As they are all similar GUI-based apps, I can't really see any pattern. I'd expect them all to fail if one does as they share quite a lot of lower-level code and similar libs are enabled.

    David
     
  16. Erel

    Erel Administrator Staff Member Licensed User

    I will track this issue. It does seem like some network issue (maybe anti virus or something).
     
  17. BeneBarros

    BeneBarros Active Member Licensed User

    after solving
    ref: http: //www.b4x.com/android/forum/threads/version-3-0-beta-7-solved.54019/
    in which the names of the image files were wrong in fxml files, the application went on to run in debug mode.
    running normally in 2.80 and Beta 7.
     
    Erel likes this.
  18. DarkMann

    DarkMann Member Licensed User

    Having just updated all three systems to Beta #8, the two desktops now both work fine in debug, but the laptop still doesn't work. It is as if it is something to do with signatures on the files that the AV is detecting, but as I'm using different versions of windows, different AV software and it still fails with the AV and Firewalls turned off, I can't explain it.

    Now my two desktops are working fine with debug, I'm not too worried about the laptop, but I do hate those unsolved mysteries.
     
  19. Erel

    Erel Administrator Staff Member Licensed User

    The problem might be in windows firewall. Maybe it is blocking java.exe or something like this.
     
  20. Tony Daly

    Tony Daly Member Licensed User

    I had a similar problem in B4J.

    "Rapid Debugger failed to connect to process. Please try to run again.
    Make sure that no firewall or antivirus block the following ports:8937, 8938, and 59812"


    After looking at the error log messages, which also reported that the classes in the wrapper were of an unsupported version I tracked the problem to the version of JAVA on my PC being older than the one that was used to create the library. Once I updated the JAVA sdk and pointed the path to the new version in B4J all was fine.

    This may explain why the problem occurs on some machines and not others.

    Hope this helps.
     
    Erel likes this.
Thread Status:
Not open for further replies.
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice