Sign-up our Newsletter  Register on our LinkedIn  Follow us on Twitter  Check out our Facebook  Follow us on Google+
Follow

I cannot make XStudio work from the web server. What Am I doing wrong?

    • First thing is to check your firewall authorizes you to connect to outbound port 3306. To verify this, you can runPortQryV2. (it's a free port scanner made available for free by Microsoft) with the following command line
      PortQry.exe -n <server name or IP address> -e 3306.
      If you firewall is correctly configured you should get an output similar to:

      c:\PortQryV2>PortQry.exe -n 176.58.90.219 -e 3306
      Querying target system called:
      176.58.90.219
      Attempting to resolve IP address to a name...
      IP address resolved to xqual7.xqual.com
      querying...
      TCP port 3306 (unknown service): LISTENING
      


      Alternatively, you can also use the command telnet <server name or IP address> 3306. If you get garbage characters it means the firewall is ok.

 

    • Check in the xstudio.conf file that you're using a real resolvable name or a valid IP address for the database_serverparameter. Do NOT use localhost or 127.0.0.1

    • Check that the database_server parameter in xstudio.conf and the codebase attribute in xstudio.jnlp are identical.

    • Check you do not have extra leading or ending space in the parameter's values in xstudio.conf

    • If the standalone version works fine (you can start XStudio, login and use it), you can:
      • Copy xstudio.conf to your web server install (overwrite the default one in the bin directory)
      • Copy the JDBC driver you're using in the standalone version to the web server as well (in bin/jdbc directory)


    • This can be due to one or several corrupted packages (i.e. because of a network failure during the download), so you can try to clear the Java cache to force the system to download all the resources again:
      Windows start menu > Control Panel > Programs > Java > General > Temporary Internet Files > View...
      Select "Applications" in the "Show" drop-down menu, select all the XStudio instances, delete them
      Select "Resources"in the "Show" drop-down menu, select everything and delete
      Restart XStudio normally...

    • In some cases, this may be due to DNS issues. Of course the proper solution is to fix the problem on your company DNS server but a workaround is to insert the server anem into your local /etc/hosts (on linux) or%systemroot%\system32\drivers\etc\hosts
    • (on Windows) file.



  • It can also be due to networking issue. One thing people sometimes need to do is to change the network settings of their Java client:
    Windows start menu > Control Panel > Programs > Java > General > Network Settings > Network Settings....
    It may be needed to select Direct Connection instead of Use Browser Settings or vice-versa. In some other cases, it may be necessary to set the company proxy settings manually.

  • If your client computer does not have much RAM you can reduce the maximum heap size in the JNLP configuration on the server.
    Edit xstudio.jnlp and lower the max-heap-size value. i.e. max-heap-size="512m".

  • In some computers, JNLP may prefer to use the IPv4 stack to communicate with the server. You can try to editxstudio.jnlp and set the java.net.preferIPv4Stack to true. i.e. your j2se parameter may look like: j2se version="1.7" href="http://java.sun.com/products/autodl/j2se" java-vm args="-Djava.net.preferIPv4Stack=true".

  • You may also try to uninstall your jre and reinstall it from http://www.java.com.



The instructions related to xstudio.conf are also valid for bugtracking.conf.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.