good20087758521 / apjp

Automatically exported from code.google.com/p/apjp
0 stars 0 forks source link

Connection interruption #175

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
I configured "APJP_REMOTE_JAVA-1.0.0" on Openshift. It works perfect for 1 or 2 
minutes but after that i receive this error message:
"Java has encountered a problem and needs to close"
I have to run "APJP_LOCAL.bat" for the second time and after minutes i face the 
above message again. (The log file has been attached)

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

APJP_LOCAL_JAVA-1.0.1
APJP_REMOTE_JAVA-1.0.0
Windows XP

Please provide any additional information below.

Original issue reported on code.google.com by ypg701...@gmail.com on 23 May 2013 at 8:25

Attachments:

GoogleCodeExporter commented 9 years ago
Can you update your JAVA VM 7 to the latest version?
Or try with JAVA VM 6.

You can also use JAP: http://code.google.com/p/jap/

Original comment by jeroen.v...@gmail.com on 23 May 2013 at 10:17

GoogleCodeExporter commented 9 years ago
Hi jeroen.v...@gmail.com
Thank you very much for sparing your busy time.
My Java version is: Version 7 Update 4.

Original comment by ypg701...@gmail.com on 23 May 2013 at 1:20

GoogleCodeExporter commented 9 years ago
Update to Version 7 Update 21

Original comment by jeroen.v...@gmail.com on 23 May 2013 at 1:27

GoogleCodeExporter commented 9 years ago
I upgraded java to Version 7 Update 21, but problem didn't solve. I
think that the connection intercept by the ISP filter. What port does
the remote server use in this program? If i change this port, does the
APJP proxy work? If yes, how can i change it?

Original comment by ypg701...@gmail.com on 23 May 2013 at 3:20

GoogleCodeExporter commented 9 years ago
As far as I can see your JAVA VM crashes (see hs_err_pid3112.log).
Maybe you can test APJP with JAVA VM Version 6 Update 45?

You can also use APPP which is written in PYTHON.
Or you can use JAP which is also written in PYTHON.

Original comment by jeroen.v...@gmail.com on 23 May 2013 at 5:41

GoogleCodeExporter commented 9 years ago
I tried to configure "JAP_REMOTE_WS_NODE_2.0.0" on Openshift. It seems
flawless but when i enter my apllication name in address bar of a
browser (e.g:  www.xxx-yyy.rhcloud.com) ,it doesn't show anything
(timeout). I configured the "JAP_REMOTE_WS.json" as following:

{
    "LOGGER":
    {
        "LEVEL": 10
    },
    "REMOTE_PROXY_SERVER":
    {
        "TYPE": "HTTPS",
        "AUTHENTICATION":
        [
            {
                "USERNAME": "1",
                "PASSWORD": "1"
            }
        ]
    }
}

Original comment by ypg701...@gmail.com on 23 May 2013 at 8:31

GoogleCodeExporter commented 9 years ago
I also entered "https://www.xxx-yyy.rhcloud.com:8443", but anything happened

Original comment by ypg701...@gmail.com on 23 May 2013 at 9:06

GoogleCodeExporter commented 9 years ago
You cannot use JAP_REMOTE_WS_NODE in your browser, JAP_REMOTE_WS_NODE does not 
have a web interface.

Normally the WEBSOCKET protocol uses port 80 or port 443, but , for now, you 
have to use port 8080 or port 8443 (OPENSHIFT support for the WEBSOCKET 
protocol is experimental).
IMPORTANT: when OPENSHIFT applications are not used, OPENSHIFT applications go 
to sleep, and they wake up when the OPENSHIFT application is used.
But that only seems to work with port 80 or port 443, so when your application 
does not work, open https://xxx-yyy.rhcloud.com in your browser! Your 
application will wake up.

Also your configuration is not up to date, LOGGER.LEVEL should be "DEBUG" not 
10:

{
    "LOGGER":
    {
        "LEVEL": "DEBUG"
    },
    "REMOTE_PROXY_SERVER":
    {
        "TYPE": "HTTPS",
        "AUTHENTICATION":
        [
            {
                "USERNAME": "1",
                "PASSWORD": "1"
            }
        ]
    }
}

If you want a UI, you can use JAP_PYTHON-2.1.1

Original comment by jeroen.v...@gmail.com on 24 May 2013 at 6:19

GoogleCodeExporter commented 9 years ago
I'm confused. I don't know what to do anymore.
Anyway, thank you very much for your time and help.

Original comment by ypg701...@gmail.com on 24 May 2013 at 1:09

GoogleCodeExporter commented 9 years ago
1) install JAP_REMOTE_WS
2) install JAP_LOCAL_WS
3) configure your browsers proxy settings (configure the SOCKS5 proxy settings)
4) browse with your browser

the browser connects to JAP_LOCAL_WS, which connects to JAP_REMOTE_WS

on OPENSHIFT, when not used, JAP_REMOTE_WS will go to sleep, to wake up 
JAP_REMOTE_WS, you have to open http://xxx-yyy.rhcloud.com:80 or 
https://xxx-yyy.rhcloud.com:443 in your browser (not using JAP_LOCAL_WS).
OPENSHIFT should do that automatically, but it does not work on port 8080 or 
port 8443, so you have to do it yourself.

How do you know that JAP_REMOTE_WS is sleeping? When you cannot connect to the 
internet with JAP_LOCAL_WS.

MODULUS and NODEJITSU do not have that problem.

JAP_PYTHON-2.1.1 has a UI, which you can open in your browser to 
start/stop/configure proxy servers.

Original comment by jeroen.v...@gmail.com on 24 May 2013 at 1:28

GoogleCodeExporter commented 9 years ago
I tried to configure "JAP_REMOTE_WS_NODE_NODEJITSU-2.0.0", but didn't work.

Original comment by ypg701...@gmail.com on 24 May 2013 at 3:55

GoogleCodeExporter commented 9 years ago
If you attach your JAP_LOCAL_WS.json and JAP_REMOTE_WS.json, I can test your 
configuration.

Original comment by jeroen.v...@gmail.com on 24 May 2013 at 4:49

GoogleCodeExporter commented 9 years ago
These are my JAP_LOCAL_WS.json and JAP_REMOTE_WS.json

Original comment by ypg701...@gmail.com on 24 May 2013 at 7:21

Attachments:

GoogleCodeExporter commented 9 years ago
I have updated attached JAP_LOCAL_WS.json
I have tested with JAP_LOCAL_WS_PYTHON-2.0.0 and everything works!

Original comment by jeroen.v...@gmail.com on 24 May 2013 at 9:57

Attachments:

GoogleCodeExporter commented 9 years ago
I can't access my own application, when i entered its address, nothing
happened at all.

Original comment by ypg701...@gmail.com on 25 May 2013 at 7:03

GoogleCodeExporter commented 9 years ago
JAP_REMOTE_WS does not have a UI for your browser.
When you open JAP_REMOTE_WS in your browser, you will see a blank page (or the 
page keeps loading). That is normal.

Original comment by jeroen.v...@gmail.com on 25 May 2013 at 7:53

GoogleCodeExporter commented 9 years ago
I tested with new "JAP_LOCAL_WS_PYTHON-2.0.0" and it didn't work again

Original comment by ypg701...@gmail.com on 25 May 2013 at 8:05

GoogleCodeExporter commented 9 years ago
correction: tested with new "JAP_LOCAL_WS.json"

Original comment by ypg701...@gmail.com on 25 May 2013 at 8:08

GoogleCodeExporter commented 9 years ago
If you tested "JAP_WS_NODE_NODEJITSU-2.0.0" with my JAP_LOCAL_WS.json
and JAP_REMOTE_WS.json

Original comment by ypg701...@gmail.com on 25 May 2013 at 8:31

GoogleCodeExporter commented 9 years ago
I do not have enough information to help you, can you attach your console 
output?

Original comment by jeroen.v...@gmail.com on 28 May 2013 at 4:52

GoogleCodeExporter commented 9 years ago
My problem with "APJP-JAVA" was solved. I figured out how to overcome
that. Instead of port number 10000, i entered 10200 in my browser and
it worked perfectly and i didn't face any error message again.
But my problem with "JAP_WS" remains the same.

Original comment by ypg701...@gmail.com on 29 May 2013 at 1:41