[MOBY-dev] Problems with Biomoby Ant Script

Michael Gerlich MichaelGerlich at gmx.de
Mon Apr 7 10:52:22 UTC 2008


Hi there,

I'am still having problems getting JMoby to work in Eclipse.
First of all, I run Eclipse on OpenSuse 10.3 with updated Java JDK 1.5 Update 15.
As written here (http://bioinfo.mpiz-koeln.mpg.de/araws/documentation/help/jmoby-step-by-step/writing-biomoby-web-services/known-errors-and-problems)
 Eclipse is started from console with parameter -vmargs and -Djava.home=/usr/lib/jvm/java-1.5.0-sun-1.5.0_update15/jre/.
Though I'am connected through a proxy, I need to specify proxy settings in net.properties with http_proxy tags (system variables set doesn't seem to affect eclipse or java in any way).

Downloading from CVS works fine from Eclipse (even without proxy settings in net.properties), but as soon as I want to call ant scripts (like install), the proxy settings have to be specified or a timeout arises.

When running install ant task, after some time, the following shows up:

[Local cache] The jMoby is now creating a local cache. Depending
[Local cache] on the network speed, it may take several minutes
[Local cache] (usually it should be done within about a minute).
[Local cache] 
[Local cache] [You can check the progress in the jMoby.log file.]
[Local cache]   
[Local cache] ===ERROR===
[Local cache] ===ERROR===
[Local cache] Fault details:
[Local cache] Fault string: java.net.ConnectException: Die Wartezeit für die Verbindung ist abgelaufen
[Local cache] Fault code:   {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
[Local cache] Fault actor:  null
[Local cache] When calling:
[Local cache]     http://moby.ucalgary.ca/moby/MOBY-Central.pl
[Local cache] ===========
[Local cache] ===========
Retrieving namespaces...    

BUILD FAILED
/home/micge/workspace/moby2/xmls/install.xml:99: Java returned: 1

Total time: 4 minutes 49 seconds

Everything before building the cache runs fine, but there is a timeout specified.
I don't know what or where to change a thing because the error is caused by the proxy settings (so I guess).
Anyone who knows an answer to this?

Regards,
Michael



More information about the MOBY-dev mailing list