[Mulgara-dev] Mulgara 2.1.9

[Paul Gearon]

Yes, I can see what's happened.

I upgraded to Jetty 7. I was having some problems with HTTP and
thought that this upgrade might help. It had no effect on my problem
(which I eventually solved), and in the meantime I had to fix a few
things that the upgrade broke. All of this was part of the reason for
the long delay with the release.

Anyway, I didn't check what was needed for Jetty 7, but it appears
that it needs Java 1.6. The stack trace you've shown here demonstrates
that Jetty is calling some code that only showed up in Java 1.6. See:
  http://download.oracle.com/javase/6/docs/api/java/util/Collections.html#newSetFromMap(java.util.Map)

Given this, I'm actually surprised that you were able to run the Jetty
Jar up to this point.

I take it that you're on older hardware and can't make the move to Java 1.6?

Anyway, the solution for you is to go back to Jetty 6. Perhaps I
should move everything back to Jetty 6, but it feels like a backward
move for the project.  The code changes I had to make to work with
Jetty 7 are backward compatible with Jetty 6, so that only changes
would be in the Jars and the ant build files. That's easy enough to
undo, but I'm not sure what I should do so that the project can stay
on Jetty 7 while also supporting the move back to Jetty 6.

Any suggestions here are welcome.

Paul

On Sun, Oct 3, 2010 at 1:25 PM, Agustina Martinez <amgcia at gmail.com> wrote:
> Hi Paul,
>
> I have tried to compile for java 1.5. I needed to comment some overridden
> methods from JettyLogger.java and from RDFa...(comment the @override) in
> order to compile successfully. Once I have the generated jar file when I
> execute it I get the following exceptions.
>
> I am running a MAC with JAVA 1.5.X.
>
> Mulgara Semantic Store Version 2.1.9 (Build 2.1.9.local)
>  INFO [main] (EmbeddedMulgaraServer.java:730) - RMI Registry started
> automatically on port 1099
> 0 [main] INFO org.mulgara.server.EmbeddedMulgaraServer  - RMI Registry
> started automatically on port 1099
>  INFO [main] (EmbeddedMulgaraServer.java:753) - java.security.policy set to
> jar:file:/JAVA_PACKAGES/MULGARA/mulgara-2.1.9src/dist/mulgara-2.1.9.jar!/conf/mulgara-rmi.policy
> 3 [main] INFO org.mulgara.server.EmbeddedMulgaraServer  -
> java.security.policy set to
> jar:file:/JAVA_PACKAGES/MULGARA/mulgara-2.1.9src/dist/mulgara-2.1.9.jar!/conf/mulgara-rmi.policy
> Exception in thread "main" java.lang.NoSuchMethodError:
> java.util.Collections.newSetFromMap(Ljava/util/Map;)Ljava/util/Set;
>     at
> org.eclipse.jetty.server.nio.BlockingChannelConnector.<init>(BlockingChannelConnector.java:53)
>     at org.mulgara.server.HttpServices.addConnector(HttpServices.java:352)
>     at
> org.mulgara.server.HttpServices.buildAndConfigure(HttpServices.java:266)
>     at
> org.mulgara.server.HttpServices.createHttpServers(HttpServices.java:192)
>     at org.mulgara.server.HttpServices.<init>(HttpServices.java:139)
>     at
> org.mulgara.server.EmbeddedMulgaraServer.<init>(EmbeddedMulgaraServer.java:382)
>     at
> org.mulgara.server.EmbeddedMulgaraServer.main(EmbeddedMulgaraServer.java:182)
>
> Shutting down server, please wait...
>
> Any idea what is going on?
>
> Thanks,
> Agustina
>
> 2010/10/3 Agustina Martinez <amgcia at gmail.com>
>>
>> Will do. Thanks a lot for the quick response.
>>
>> Cheers,
>> Agustina
>>
>> 2010/10/1 Paul Gearon <gearon at ieee.org>
>>>
>>> Argh. I've probably compiled it with Java 6. Sorry. Yes, Java 5 works
>>> fine.
>>>
>>> I'm on a Mac, which doesn't have Java 5 anymore, and I don't want to
>>> hard code the build to produce Java 5, because Java 6 is better when
>>> you can manage it.
>>>
>>> I'll try to get a Java 5 version out soon, though it may have to be
>>> tomorrow as I have some commitments this afternoon. In the meantime,
>>> are you able to build it yourself?
>>>
>>> Regards,
>>> Paul Gearon
>>>
>>> On Fri, Oct 1, 2010 at 12:45 PM, Agustina Martinez <amgcia at gmail.com>
>>> wrote:
>>> > Hi Paul,
>>> >
>>> > I have tried to run and also build the latest version of Mulgara with
>>> > no
>>> > success art all.
>>> >
>>> > Doesn't it support anymore Java 5? Because I am getting errors related
>>> > with
>>> > the java when executing the jar and also when trying to compile and
>>> > build.
>>> >
>>> > Thanks in advance,
>>> > Agustina
>>> >
>>> > 2010/10/1 Paul Gearon <gearon at ieee.org>
>>> >>
>>> >> After a long hiatus, Mulgara 2.1.9 has been released.
>>> >>
>>> >> The new version has:
>>> >> - Improved read/write performance.
>>> >> - Better datatype handling fro relational databases, particularly
>>> >> Oracle.
>>> >> - RDFa support.
>>> >> - Upgraded from Jetty 6.1.11 to Jetty 7.1.6.
>>> >> - Fixed a problem with blank nodes created for CONSTRUCT queries.
>>> >>
>>> >>
>>> >> Details can be found at:
>>> >>  http://mulgara.org/release.html#v2.1.9
>>> >>
>>> >> Full sources and binaries can be found at:
>>> >>  http://mulgara.org/download.html
>>> >>
>>> >>
>>> >> Part of the reason for the delay was my recent change in jobs.
>>> >> Hopefully future releases will not be spaced so far apart.
>>> >>
>>> >> Paul Gearon
>>> >> _______________________________________________
>>> >> Mulgara-dev mailing list
>>> >> Mulgara-dev at mulgara.org
>>> >> http://lists.mulgara.org/mailman/listinfo/mulgara-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > Mulgara-dev mailing list
>>> > Mulgara-dev at mulgara.org
>>> > http://lists.mulgara.org/mailman/listinfo/mulgara-dev
>>> >
>>> >
>>> _______________________________________________
>>> Mulgara-dev mailing list
>>> Mulgara-dev at mulgara.org
>>> http://lists.mulgara.org/mailman/listinfo/mulgara-dev
>>
>
>
> _______________________________________________
> Mulgara-dev mailing list
> Mulgara-dev at mulgara.org
> http://lists.mulgara.org/mailman/listinfo/mulgara-dev
>
>