(java-api/scalaris will likely fail)

[Alex]

When running './configure' I get two of the following warnings:

configure: WARNING: "/usr/share/java-utils/java-functions" was not
found (java-api/scalaris will likely fail)
configure: WARNING: "" was not found or is not executable (java-api/
scalaris will likely fail)

And then when running 'make java-test' on the server I get a failure
on scalaris.test:

Nameserver not responding on domU-12-31-39-00-A1-E9.compute-1.internal
when looking up jtest_boot, bad nodes: [jtest_boot@domU-12-31-39-00-A1-
E9.compute-1.internal], good nodes: [], retries: 3

But the FQDN is the same when I run the Java command and the Erlang
command as listed in the FAQ.

ubuntu@cs227-nfs :~/Systems/scalaris/scalaris-trunk/bin$ erl -noinput -
name boot -eval 'io:format("~s~n", [node()]), halt().'
bo...@domU-12-31-39-00-A1-E9.compute-1.internal
ubuntu@cs227-nfs :~/Systems/scalaris/scalaris-trunk$ ./java-api/
scalaris --noconfig --noerl -lh
domU-12-31-39-00-A1-E9.compute-1.internal

I found the 'java-utils/java-functions' library as part of the
''jpackage-utils'' package but this is not explicitly listed anywhere
as being required. I'm a little wary of installing this on a shared
system as I know nothing about it. Is this necessary to use the Java
API?

[Thorsten Schuett]

On Thursday, May 12, 2011, Alex wrote:
> When running './configure' I get two of the following warnings:
>
> configure: WARNING: "/usr/share/java-utils/java-functions" was not
> found (java-api/scalaris will likely fail)

This message tells you, that you probably won't be able to use java-
api/scalaris (the java-based scalaris command-line client)

> configure: WARNING: "" was not found or is not executable (java-api/
> scalaris will likely fail)

The second error message is not very helpful either. configure was checking
for build-classpath, which is also used by java-api/scalaris.

>
> And then when running 'make java-test' on the server I get a failure
> on scalaris.test:
>
> Nameserver not responding on domU-12-31-39-00-A1-E9.compute-1.internal
> when looking up jtest_boot, bad nodes: [jtest_boot@domU-12-31-39-00-A1-
> E9.compute-1.internal], good nodes: [], retries: 3

Do you get any further output from "make java-test"?

And could you please run "epmd -names" after "make java-test" failed?

> But the FQDN is the same when I run the Java command and the Erlang
> command as listed in the FAQ.
>
> ubuntu@cs227-nfs :~/Systems/scalaris/scalaris-trunk/bin$ erl -noinput -
> name boot -eval 'io:format("~s~n", [node()]), halt().'
> bo...@domU-12-31-39-00-A1-E9.compute-1.internal
> ubuntu@cs227-nfs :~/Systems/scalaris/scalaris-trunk$ ./java-api/
> scalaris --noconfig --noerl -lh
> domU-12-31-39-00-A1-E9.compute-1.internal
>
> I found the 'java-utils/java-functions' library as part of the
> ''jpackage-utils'' package but this is not explicitly listed anywhere
> as being required. I'm a little wary of installing this on a shared
> system as I know nothing about it. Is this necessary to use the Java
> API?

No.

Thorsten

[Nico Kruber]

On Monday 16 May 2011 05:04:18 Thorsten Schuett wrote:
> On Thursday, May 12, 2011, Alex wrote:
> > When running './configure' I get two of the following warnings:
> >
> > configure: WARNING: "/usr/share/java-utils/java-functions" was not
> > found (java-api/scalaris will likely fail)
>
> This message tells you, that you probably won't be able to use java-
> api/scalaris (the java-based scalaris command-line client)
>
> > configure: WARNING: "" was not found or is not executable (java-api/
> > scalaris will likely fail)
>
> The second error message is not very helpful either. configure was checking
> for build-classpath, which is also used by java-api/scalaris.

I improved the error messages.
just a clarification:
* java-functions (if present) will be used to setup the java environment which
may not be required for your system
* build-classpath is a script that eases classpath creation especially when a
script is being used on different platforms. If you don't have build-
classpath, our wrapper script will try to locate dependent jar files in
$SCALARIS_JAVA_HOME/lib - these jars include OtpErlang-1.5.4.jar and jakarta-
commons-cli-1.2.jar which you can copy from ./java-api/lib/
if unset, SCALARIS_JAVA_HOME will be set to the client wrapper script's
location

> > And then when running 'make java-test' on the server I get a failure
> > on scalaris.test:
> >
> > Nameserver not responding on domU-12-31-39-00-A1-E9.compute-1.internal
> > when looking up jtest_boot, bad nodes: [jtest_boot@domU-12-31-39-00-A1-
> > E9.compute-1.internal], good nodes: [], retries: 3
>
> Do you get any further output from "make java-test"?
>
> And could you please run "epmd -names" after "make java-test" failed?

please also check that your computer is reachable under the given FQDN as the
Java-API will need to look up that name