bigdata-developers — List for bigdata developers

Re: [Bigdata-developers] Sesame 2.7.x

[Bryan T. <br...@sy...>]

Anton,

I'd like to repeat my offer to help if you want to try preparing a patch for a sesame 2.7.x migration….

Right now, we are focused on getting out the 1.3.1 release with support for the HA load balancer, reification done right, RDF graph mining, and a new workbench for the bigdata platform.  2.7.x could go into a 1.3.2 release.

Thanks,
Bryan

From: Anton Kulaga <ant...@gm...<mailto:ant...@gm...>>
Reply-To: Anton Kulaga <ant...@gm...<mailto:ant...@gm...>>
Date: Tuesday, April 29, 2014 3:30 AM
To: "Big...@li...<mailto:Big...@li...>" <Big...@li...<mailto:Big...@li...>>
Subject: [Bigdata-developers] Sesame 2.7.x

Hi All,

I wonder when are you going to migrate to Sesame 2.7.x ?
I am developing a generic semantic-web lib for Scala ( https://github.com/scalax/semweb )
 and bigdata-s usage of outdated version of Sesame creates a lot of problem there as I cannot write code that works both for bigdata and for current major version of sesame.
Outdated sesame also creates a lot of problems outside of my lib as most of current sesame-compatible libs with useful features are already using Sesame 2.7.x


I also wonder if anybody has already made Elastic integration to Bigdata as current bigdata text search indexes only literals and opensahara seems to be more dead than alive ( I failed to register there and nobody there responded to my emails).

I also wonder if there are Scala developers there who made some extensions ( like nice Implicit classes and AST factories) to Bigdata that can be (or already are) opensourced for the benefit of everyone.


--
Best regards,
Anton Kulaga

Re: [Bigdata-developers] Sesame 2.7.x

[Antoni M. <ant...@qu...>]

----- Ursprüngliche Mail -----
> Von: "Anton Kulaga" <ant...@gm...>
> 
> Hi All,
> 
> 
> I wonder when are you going to migrate to Sesame 2.7.x ?

You can add yourself to the cc list on

http://trac.bigdata.com/ticket/714

This question has popped up on this list already. AFAIU there are currently no plans.

> I am developing a generic semantic-web lib for Scala (
> https://github.com/scalax/semweb )
> and bigdata-s usage of outdated version of Sesame creates a lot of
> problem there as I cannot write code that works both for bigdata and
> for current major version of sesame.
> Outdated sesame also creates a lot of problems outside of my lib as
> most of current sesame-compatible libs with useful features are
> already using Sesame 2.7.x

... I would add the ability to use SPARQLRepository that supports writing, as well as reading. 

It seems that this migration isn't that simple though, see trac. 

Antoni

[Bigdata-developers] Sesame 2.7.x

[Anton K. <ant...@gm...>]

Hi All,

I wonder when are you going to migrate to Sesame 2.7.x ?
I am developing a generic semantic-web lib for Scala (
https://github.com/scalax/semweb )
 and bigdata-s usage of outdated version of Sesame creates a lot of problem
there as I cannot write code that works both for bigdata and for current
major version of sesame.
Outdated sesame also creates a lot of problems outside of my lib as most of
current sesame-compatible libs with useful features are already using
Sesame 2.7.x


I also wonder if anybody has already made Elastic integration to Bigdata as
current bigdata text search indexes only literals and opensahara seems to
be more dead than alive ( I failed to register there and nobody there
responded to my emails).

I also wonder if there are Scala developers there who made some extensions
( like nice Implicit classes and AST factories) to Bigdata that can be (or
already are) opensourced for the benefit of everyone.


-- 
Best regards,
Anton Kulaga

Re: [Bigdata-developers] Content-Type not recognized as RDF: application/x-www-form-urlencoded

[Jeremy J C. <jj...@sy...>]

I just got this.

The root cause was my error!

I was doing
time /usr/bin/curl  -H 'Accept: text/csv' -s --data-urlencode query@term-completion-ex2.sparql.txt http://localhost:2333/sparql 

where I got the file name wrong and there was no file term-completion-ex2.sparql.txt, once I correctly named the file I got the answer I expected!

Jeremy

On Apr 22, 2014, at 1:15 PM, Bryan Thompson <br...@sy...> wrote:

> Has anyone seen this in the RDR branch?  I just updated and finally accepted the new workbench as index.html and I am testing the HA load balancer.  I am hitting this message only on one of the two servers.  I am curious whether there has been any change to the HTML FORM and the handling of that FORM in the RDR branch.  I actually use a file that I have held back (indexLBS.html) to test the HA load balancer — it is willing to post to bigdata/LBS/sparql (the load balancer) rather than to bigdata/sparql (the non-load balanced end point).
> Thanks,
> Bryan
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform_______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers

[Bigdata-developers] Fwd: [Bigdata] #896: poor optimizer choice: split query into separate components?

[Jeremy J C. <jj...@sy...>]

Well I have reduced my problems from yesterday to a simple query optimizer issue, (with an easy work-around) which I am happy to handle; although I won't attend to it with any haste.
Please feel free to reassign (or not) to someone who may work on this faster

Jeremy


Begin forwarded message:

> From: "TRAC Bigdata" <no...@sy...>
> Subject: Re: [Bigdata] #896: poor optimizer choice: split query into separate components?
> Date: April 22, 2014 4:41:26 PM PDT
> 
> #896: poor optimizer choice: split query into separate components?
> -------------------------------------+---------------------------
>  Reporter:  jeremycarroll           |      Owner:  jeremycarroll
>      Type:  defect                  |     Status:  accepted
>  Priority:  minor                   |  Milestone:
> Component:  Static Query Optimizer  |    Version:
> Resolution:                          |   Keywords:
> -------------------------------------+---------------------------
> Changes (by jeremycarroll):
> 
> * owner:  thompsonbry => jeremycarroll
> * priority:  major => minor
> * status:  new => accepted
> * component:  B+Tree => Static Query Optimizer
> 
> 
> -- 
> Ticket URL: <http://trac.bigdata.com/ticket/896#comment:1>
> Bigdata <trac.bigdata.com>
> Bigdata Triple Store

[Bigdata-developers] Content-Type not recognized as RDF: application/x-www-form-urlencoded

[Bryan T. <br...@sy...>]

Has anyone seen this in the RDR branch?  I just updated and finally accepted the new workbench as index.html and I am testing the HA load balancer.  I am hitting this message only on one of the two servers.  I am curious whether there has been any change to the HTML FORM and the handling of that FORM in the RDR branch.  I actually use a file that I have held back (indexLBS.html) to test the HA load balancer — it is willing to post to bigdata/LBS/sparql (the load balancer) rather than to bigdata/sparql (the non-load balanced end point).
Thanks,
Bryan

Re: [Bigdata-developers] three new trac items to do with large update

[Bryan T. <br...@sy...>]

Yes, I think so too.  The question is how to scale what you need to accomplish. Bryan

-------- Original message --------
From: Jeremy Carroll
Date:04/21/2014 8:05 PM (GMT-05:00)
To: Bryan Thompson
Cc: Big...@li...
Subject: Re: [Bigdata-developers] three new trac items to do with large update


On Apr 21, 2014, at 4:09 PM, Bryan Thompson <br...@sy...<mailto:br...@sy...>> wrote:

The original UPDATE request is not a reasonable way to approach your goal.

There is certainly some truth in that!
On a smaller scale it was fine, and you stick a load of query generation code together and it just gets big! without any thought!

It actually does pretty well, all things considered.


Jeremy

Re: [Bigdata-developers] three new trac items to do with large update

[Jeremy C. <jj...@gm...>]

On Apr 21, 2014, at 4:09 PM, Bryan Thompson <br...@sy...> wrote:

> The original UPDATE request is not a reasonable way to approach your goal.

There is certainly some truth in that!
On a smaller scale it was fine, and you stick a load of query generation code together and it just gets big! without any thought!

It actually does pretty well, all things considered.


Jeremy

[Bigdata-developers] Merge of main branch to RDR branch.

[Bryan T. <br...@sy...>]

All, I will be merging the main branch into the RDR branch over the next few days to catch up the RDR branch with changes in the main branch.  We are not quite ready to bring back the RDR branch (per an email earlier this week), but I would like everyone to focus on bringing the features in the RDR branch to completion and hardening them so we are ready to bring those changes back for our next release.

Thanks,
Bryan

[Bigdata-developers] HA1 support now in the main development branch + status on RDR branch

[Bryan T. <br...@sy...>]

The HA1 deployment model support is now in the main development branch.  This provides online backups (with concurrent read/write operations) and transaction logs for a single-server Journal using the same deployment model as the highly available replication cluster.

We will be working to bring back the RDR branch soon as well.  The RDR branch currently has support for Reification Done Right (efficient link attributes / statements about statements), RDF Graph Mining using the GAS abstraction, a new workbench look and feel, and a new load balancer for the HA cluster deployment.  We are not quite done with all of those features.  Some remaining steps are:

 *   Documentation on the wiki for new GAS features
 *   Documentation on the wiki for the RDR features (there is currently no documentation for RDR on the wiki…)
 *   Stripping out the old SIDs mode in favor of the RDR mode.
 *   RDR support in scale-out (primarily in the scale-out data loader).
 *   Performance tuning for the HA load balancer and integration into the HA cluster deployment models.

Thanks,
Bryan

Re: [Bigdata-developers] BigdataSailRepository connections

[Mike P. <mi...@sy...>]

Definitely use the read only connection then.


On 4/10/14 3:43 PM, "Jim Balhoff" <ba...@gm...> wrote:

>Thank you this is really good to know. I am only querying, not updating.
>
>On Apr 10, 2014, at 2:34 PM, Mike Personick <mi...@sy...> wrote:
>
>> getConnection() tries to return the unisolated connection - this is a
>> blocking operation (only one write connection to bigdata is available).
>> 
>> If you want to support concurrent writers you should set up a queuing
>> system, have writers put writes on a queue and have a single thread
>> draining the queue and writing to the database.
>> 
>> Use getReadOnlyConnection() for read-only operations - this is a
>> non-blocking operation.
>> 
>> One writer, many readers.
>> 
>> 
>> 
>> On 4/10/14 2:28 PM, "Jim Balhoff" <ba...@gm...> wrote:
>> 
>>> I would like to embed Bigdata within my web service application. I am a
>>> little unsure of whether I'll be using it correctly and get equivalent
>>> performance to  queries in NanoSparqlServer. I am having trouble with
>>> HTTP connections from my app to NanoSparqlServer because I generate too
>>> many simultaneous connections.
>>> 
>>> The Bigdata wiki states "The Sesame Server does not use the
>>>non-blocking
>>> query mode of bigdata. This can significantly limit the query
>>>throughput.
>>> The NanoSparqlServer andHAJournalServer both deliver non-blocking
>>>query."
>>> 
>>> I am not using the Sesame server, rather directly loading the Bigdata
>>> journal into my application using Sesame like this (Scala):
>>> 
>>> val sail = new BigdataSail(bigdataProperties)
>>> val repository = new BigdataSailRepository(sail)
>>> repository.initialize()
>>> 
>>> Will this repository object be providing non-blocking query when
>>> connections are opened from different web service instances (using
>>> Jersey)? Is there a limit to the number of connections I can open at
>>> once? Is there any problem calling the repository object from multiple
>>> threads? I'm getting connections like this:
>>> 
>>> val connection = repository.getConnection
>>> connection.setAutoCommit(false)
>>> val bigdataQuery = connection.prepareTupleQuery(QueryLanguage.SPARQL,
>>> builtQuery.toString)
>>> val result = bigdataQuery.evaluate
>>> // do stuff
>>> result.close()
>>> connection.commit()
>>> connection.close()
>>> 
>>> Thank you,
>>> Jim
>>> 
>>> 
>>> 
>>>------------------------------------------------------------------------
>>>--
>>> ----
>>> Put Bad Developers to Shame
>>> Dominate Development with Jenkins Continuous Integration
>>> Continuously Automate Build, Test & Deployment
>>> Start a new project now. Try Jenkins in the cloud.
>>> http://p.sf.net/sfu/13600_Cloudbees
>>> _______________________________________________
>>> Bigdata-developers mailing list
>>> Big...@li...
>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>> 
>

Re: [Bigdata-developers] BigdataSailRepository connections

[Bryan T. <br...@sy...>]

In the RDR branch, the nano sparql server web app is completely configured through jetty.xml and wen.xml.  The jetty.xml file is used by the embedded and HAJournalServer deployment modes.  Web.xml only is used for tomcat or other war deployments.  This should make it much easier to either extend the bigdata web app or to deploy your own web app along side in the same servlet container and same jvm.

Bryan

> On Apr 10, 2014, at 2:29 PM, "Jim Balhoff" <ba...@gm...> wrote:
> 
> I would like to embed Bigdata within my web service application. I am a little unsure of whether I'll be using it correctly and get equivalent performance to  queries in NanoSparqlServer. I am having trouble with HTTP connections from my app to NanoSparqlServer because I generate too many simultaneous connections.
> 
> The Bigdata wiki states "The Sesame Server does not use the non-blocking query mode of bigdata. This can significantly limit the query throughput. The NanoSparqlServer andHAJournalServer both deliver non-blocking query."
> 
> I am not using the Sesame server, rather directly loading the Bigdata journal into my application using Sesame like this (Scala):
> 
> val sail = new BigdataSail(bigdataProperties)
> val repository = new BigdataSailRepository(sail)
> repository.initialize()
> 
> Will this repository object be providing non-blocking query when connections are opened from different web service instances (using Jersey)? Is there a limit to the number of connections I can open at once? Is there any problem calling the repository object from multiple threads? I'm getting connections like this:
> 
> val connection = repository.getConnection
> connection.setAutoCommit(false)
> val bigdataQuery = connection.prepareTupleQuery(QueryLanguage.SPARQL, builtQuery.toString)
> val result = bigdataQuery.evaluate
> // do stuff
> result.close()
> connection.commit()
> connection.close()
> 
> Thank you,
> Jim
> 
> 
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment 
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers

Re: [Bigdata-developers] BigdataSailRepository connections

[Jim B. <ba...@gm...>]

Thank you this is really good to know. I am only querying, not updating.

On Apr 10, 2014, at 2:34 PM, Mike Personick <mi...@sy...> wrote:

> getConnection() tries to return the unisolated connection - this is a
> blocking operation (only one write connection to bigdata is available).
> 
> If you want to support concurrent writers you should set up a queuing
> system, have writers put writes on a queue and have a single thread
> draining the queue and writing to the database.
> 
> Use getReadOnlyConnection() for read-only operations - this is a
> non-blocking operation.
> 
> One writer, many readers.
> 
> 
> 
> On 4/10/14 2:28 PM, "Jim Balhoff" <ba...@gm...> wrote:
> 
>> I would like to embed Bigdata within my web service application. I am a
>> little unsure of whether I'll be using it correctly and get equivalent
>> performance to  queries in NanoSparqlServer. I am having trouble with
>> HTTP connections from my app to NanoSparqlServer because I generate too
>> many simultaneous connections.
>> 
>> The Bigdata wiki states "The Sesame Server does not use the non-blocking
>> query mode of bigdata. This can significantly limit the query throughput.
>> The NanoSparqlServer andHAJournalServer both deliver non-blocking query."
>> 
>> I am not using the Sesame server, rather directly loading the Bigdata
>> journal into my application using Sesame like this (Scala):
>> 
>> val sail = new BigdataSail(bigdataProperties)
>> val repository = new BigdataSailRepository(sail)
>> repository.initialize()
>> 
>> Will this repository object be providing non-blocking query when
>> connections are opened from different web service instances (using
>> Jersey)? Is there a limit to the number of connections I can open at
>> once? Is there any problem calling the repository object from multiple
>> threads? I'm getting connections like this:
>> 
>> val connection = repository.getConnection
>> connection.setAutoCommit(false)
>> val bigdataQuery = connection.prepareTupleQuery(QueryLanguage.SPARQL,
>> builtQuery.toString)
>> val result = bigdataQuery.evaluate
>> // do stuff
>> result.close()
>> connection.commit()
>> connection.close()
>> 
>> Thank you,
>> Jim
>> 
>> 
>> --------------------------------------------------------------------------
>> ----
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> 

Re: [Bigdata-developers] BigdataSailRepository connections

[Mike P. <mi...@sy...>]

getConnection() tries to return the unisolated connection - this is a
blocking operation (only one write connection to bigdata is available).

If you want to support concurrent writers you should set up a queuing
system, have writers put writes on a queue and have a single thread
draining the queue and writing to the database.

Use getReadOnlyConnection() for read-only operations - this is a
non-blocking operation.

One writer, many readers.



On 4/10/14 2:28 PM, "Jim Balhoff" <ba...@gm...> wrote:

>I would like to embed Bigdata within my web service application. I am a
>little unsure of whether I'll be using it correctly and get equivalent
>performance to  queries in NanoSparqlServer. I am having trouble with
>HTTP connections from my app to NanoSparqlServer because I generate too
>many simultaneous connections.
>
>The Bigdata wiki states "The Sesame Server does not use the non-blocking
>query mode of bigdata. This can significantly limit the query throughput.
>The NanoSparqlServer andHAJournalServer both deliver non-blocking query."
>
>I am not using the Sesame server, rather directly loading the Bigdata
>journal into my application using Sesame like this (Scala):
>
>val sail = new BigdataSail(bigdataProperties)
>val repository = new BigdataSailRepository(sail)
>repository.initialize()
>
>Will this repository object be providing non-blocking query when
>connections are opened from different web service instances (using
>Jersey)? Is there a limit to the number of connections I can open at
>once? Is there any problem calling the repository object from multiple
>threads? I'm getting connections like this:
>
>val connection = repository.getConnection
>connection.setAutoCommit(false)
>val bigdataQuery = connection.prepareTupleQuery(QueryLanguage.SPARQL,
>builtQuery.toString)
>val result = bigdataQuery.evaluate
>// do stuff
>result.close()
>connection.commit()
>connection.close()
>
>Thank you,
>Jim
>
>
>--------------------------------------------------------------------------
>----
>Put Bad Developers to Shame
>Dominate Development with Jenkins Continuous Integration
>Continuously Automate Build, Test & Deployment
>Start a new project now. Try Jenkins in the cloud.
>http://p.sf.net/sfu/13600_Cloudbees
>_______________________________________________
>Bigdata-developers mailing list
>Big...@li...
>https://lists.sourceforge.net/lists/listinfo/bigdata-developers

[Bigdata-developers] BigdataSailRepository connections

[Jim B. <ba...@gm...>]

I would like to embed Bigdata within my web service application. I am a little unsure of whether I'll be using it correctly and get equivalent performance to  queries in NanoSparqlServer. I am having trouble with HTTP connections from my app to NanoSparqlServer because I generate too many simultaneous connections.

The Bigdata wiki states "The Sesame Server does not use the non-blocking query mode of bigdata. This can significantly limit the query throughput. The NanoSparqlServer andHAJournalServer both deliver non-blocking query."

I am not using the Sesame server, rather directly loading the Bigdata journal into my application using Sesame like this (Scala):

val sail = new BigdataSail(bigdataProperties)
val repository = new BigdataSailRepository(sail)
repository.initialize()

Will this repository object be providing non-blocking query when connections are opened from different web service instances (using Jersey)? Is there a limit to the number of connections I can open at once? Is there any problem calling the repository object from multiple threads? I'm getting connections like this:

val connection = repository.getConnection
connection.setAutoCommit(false)
val bigdataQuery = connection.prepareTupleQuery(QueryLanguage.SPARQL, builtQuery.toString)
val result = bigdataQuery.evaluate
// do stuff
result.close()
connection.commit()
connection.close()

Thank you,
Jim

Re: [Bigdata-developers] trac maintenance

[Bryan T. <br...@sy...>]

Ok – trac.bigdata.com is back online.
Bryan

From: Bryan Thompson <br...@sy...<mailto:br...@sy...>>
Date: Tuesday, April 8, 2014 10:33 AM
To: "Big...@li...<mailto:Big...@li...>" <Big...@li...<mailto:Big...@li...>>
Subject: [Bigdata-developers] trac maintenance

trac.bigdata.com is temporarily down.  We are doing maintenance for an OpenSSH vulnerability.
Bryan

[Bigdata-developers] trac maintenance

[Bryan T. <br...@sy...>]

trac.bigdata.com is temporarily down.  We are doing maintenance for an OpenSSH vulnerability.
Bryan

Re: [Bigdata-developers] Fwd: [Bigdata] #870: OneOrMorePath SPARQL property path expression ignored

[Jim B. <ba...@ne...>]

Yes the problem exists there as well.

On Mar 26, 2014, at 11:55 AM, Bryan Thompson <br...@sy...> wrote:

> The RDR branch is for the reification done right feature (efficient link attributes with a nice syntax, to replace the SIDS mode).  It will be brought back to the 1.3.0 maintenance and development branch, which is branches/BIGDATA_RELEASE_1_3_0
> 
> Bryan
> 
>> On Mar 26, 2014, at 9:53 AM, "Jim Balhoff" <ba...@ne...> wrote:
>> 
>> Yes, that's BIGDATA_RELEASE_1_3_0, right? I tried revision 8018.
>> 
>> Thanks,
>> Jim
>> 
>>> On Mar 26, 2014, at 11:38 AM, Bryan Thompson <br...@sy...> wrote:
>>> 
>>> Is the problem also in the main development branch? Bryan
>>> 
>>>> On Mar 26, 2014, at 9:36 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I just opened this ticket, but don't have permission to attach the dataset. I also need to modify the ticket to change the referenced SVN revision to 8017 on the RDR branch. I attached the dataset.
>>>> 
>>>> Thank you,
>>>> Jim
>>>> <property_paths.owl>
>>>> <ATT00001.c>
>>>> <ATT00002.c>
>>>> <ATT00003.c>
>>> 
>>> ------------------------------------------------------------------------------
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!
>>> http://p.sf.net/sfu/13534_NeoTech
>>> _______________________________________________
>>> Bigdata-developers mailing list
>>> Big...@li...
>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>> 

Re: [Bigdata-developers] Fwd: [Bigdata] #870: OneOrMorePath SPARQL property path expression ignored

[Bryan T. <br...@sy...>]

The RDR branch is for the reification done right feature (efficient link attributes with a nice syntax, to replace the SIDS mode).  It will be brought back to the 1.3.0 maintenance and development branch, which is branches/BIGDATA_RELEASE_1_3_0

Bryan

> On Mar 26, 2014, at 9:53 AM, "Jim Balhoff" <ba...@ne...> wrote:
> 
> Yes, that's BIGDATA_RELEASE_1_3_0, right? I tried revision 8018.
> 
> Thanks,
> Jim
> 
>> On Mar 26, 2014, at 11:38 AM, Bryan Thompson <br...@sy...> wrote:
>> 
>> Is the problem also in the main development branch? Bryan
>> 
>>> On Mar 26, 2014, at 9:36 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>> 
>>> Hi,
>>> 
>>> I just opened this ticket, but don't have permission to attach the dataset. I also need to modify the ticket to change the referenced SVN revision to 8017 on the RDR branch. I attached the dataset.
>>> 
>>> Thank you,
>>> Jim
>>> <property_paths.owl>
>>> <ATT00001.c>
>>> <ATT00002.c>
>>> <ATT00003.c>
>> 
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/13534_NeoTech
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> 

Re: [Bigdata-developers] Fwd: [Bigdata] #870: OneOrMorePath SPARQL property path expression ignored

[Jim B. <ba...@ne...>]

Yes, that's BIGDATA_RELEASE_1_3_0, right? I tried revision 8018.

Thanks,
Jim

On Mar 26, 2014, at 11:38 AM, Bryan Thompson <br...@sy...> wrote:

> Is the problem also in the main development branch? Bryan
> 
>> On Mar 26, 2014, at 9:36 AM, "Jim Balhoff" <ba...@ne...> wrote:
>> 
>> Hi,
>> 
>> I just opened this ticket, but don't have permission to attach the dataset. I also need to modify the ticket to change the referenced SVN revision to 8017 on the RDR branch. I attached the dataset.
>> 
>> Thank you,
>> Jim
>> <property_paths.owl>
>> <ATT00001.c>
>> <ATT00002.c>
>> <ATT00003.c>
> 
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers

Re: [Bigdata-developers] Fwd: [Bigdata] #870: OneOrMorePath SPARQL property path expression ignored

[Bryan T. <br...@sy...>]

Is the problem also in the main development branch? Bryan

> On Mar 26, 2014, at 9:36 AM, "Jim Balhoff" <ba...@ne...> wrote:
> 
> Hi,
> 
> I just opened this ticket, but don't have permission to attach the dataset. I also need to modify the ticket to change the referenced SVN revision to 8017 on the RDR branch. I attached the dataset.
> 
> Thank you,
> Jim
> <property_paths.owl>
> <ATT00001.c>
> <ATT00002.c>
> <ATT00003.c>

[Bigdata-developers] Fwd: [Bigdata] #870: OneOrMorePath SPARQL property path expression ignored

[Jim B. <ba...@ne...>]

Hi,

I just opened this ticket, but don't have permission to attach the dataset. I also need to modify the ticket to change the referenced SVN revision to 8017 on the RDR branch. I attached the dataset.

Thank you,
Jim

Re: [Bigdata-developers] RDR branch builds

[Bryan T. <br...@sy...>]

Ok. Try again. Works for me now. At r8018. Bryan

> On Mar 26, 2014, at 9:09 AM, "Bryan Thompson" <br...@sy...> wrote:
> 
> The problem is in the BigdataServlet at line 80. Working on it.
> 
>> On Mar 26, 2014, at 9:08 AM, "Jim Balhoff" <ba...@ne...> wrote:
>> 
>> This didn't fix the issue for me, but for the time being I have copied jetty-proxy-9.1.3.v20140225.jar to WEB-INF/lib and it seems to be working.
>> 
>> Thank you,
>> Jim
>> 
>> 
>>> On Mar 26, 2014, at 10:48 AM, Bryan Thompson <br...@sy...> wrote:
>>> 
>>> Try again.  There was a jetty import in
>>> com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener that was
>>> causing a failure.
>>> 
>>> Committed revision r8017.
>>> 
>>> 
>>> bryan
>>> 
>>> 
>>>> On 3/26/14 8:42 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>>> 
>>>> That line is commented out in my web.xml. From tomcat 7 I have this in
>>>> the log:
>>>> 
>>>> SEVERE: Exception sending context initialized event to listener instance
>>>> of class com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener
>>>> java.lang.NoClassDefFoundError: org/eclipse/jetty/proxy/ProxyServlet
>>>>   at java.lang.ClassLoader.defineClass1(Native Method)
>>>>   at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
>>>>   at
>>>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>>>>   at
>>>> org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClass
>>>> Loader.java:2888)
>>>>   at
>>>> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.j
>>>> ava:1172)
>>>>   at
>>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>>> ava:1680)
>>>>   at
>>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>>> ava:1558)
>>>>   at
>>>> com.bigdata.rdf.sail.webapp.BigdataServlet.<clinit>(BigdataServlet.java:80
>>>> )
>>>>   at
>>>> com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener.contextInitia
>>>> lized(BigdataRDFServletContextListener.java:411)
>>>>   at
>>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.jav
>>>> a:4797)
>>>>   at
>>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.jav
>>>> a:5291)
>>>>   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>>   at
>>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java
>>>> :901)
>>>>   at
>>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>>>>   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>>>>   at
>>>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:111
>>>> 4)
>>>>   at
>>>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java
>>>> :1673)
>>>>   at
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>>>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>>>   at
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
>>>> 1145)
>>>>   at
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
>>>> :615)
>>>>   at java.lang.Thread.run(Thread.java:744)
>>>> Caused by: java.lang.ClassNotFoundException:
>>>> org.eclipse.jetty.proxy.ProxyServlet
>>>>   at
>>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>>> ava:1713)
>>>>   at
>>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>>> ava:1558)
>>>>   ... 22 more
>>>> 
>>>> 
>>>>> On Mar 26, 2014, at 10:32 AM, Bryan Thompson <br...@sy...> wrote:
>>>>> 
>>>>> If you uncomment this line in web.xml then it will attempt to resolve
>>>>> the
>>>>> HALoadBalancerServlet and that would drag in the ProxyServlet.
>>>>> 
>>>>> 
>>>>> 
>>>>> <servlet-class>com.bigdata.rdf.sail.webapp.HALoadBalancerServlet</servlet
>>>>> -c
>>>>> lass>
>>>>> 
>>>>> 
>>>>> 
>>>>> Bryan
>>>>> 
>>>>>> On 3/26/14 8:30 AM, "Bryan Thompson" <br...@sy...> wrote:
>>>>>> 
>>>>>> There are several new jars for jetty 9.  One of them includes this
>>>>>> servlet
>>>>>> (jetty-proxy).  Make sure that these are in place when using jetty.
>>>>>> 
>>>>>> These jars should not be required for the tomcat war.  Can you send the
>>>>>> full exception?  I'd like to see where the exception is being thrown
>>>>>> from.
>>>>>> 
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-rewrite-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-proxy-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-webapp-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/servlet-api-3.1.0.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-xml-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-io-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-continuation-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-util-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-client-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-security-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-http-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-servlet-9.1.3.v20140225.jar
>>>>>> 
>>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>>> /j
>>>>>> e
>>>>>> tty/jetty-server-9.1.3.v20140225.jar
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Bryan
>>>>>> 
>>>>>>> On 3/26/14 8:26 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>>>>>> 
>>>>>>> I am having trouble running the RDR branch bigdata.war in both tomcat
>>>>>>> and
>>>>>>> jetty. I get the error:
>>>>>>> 
>>>>>>> java.lang.ClassNotFoundException: org.eclipse.jetty.proxy.ProxyServlet
>>>>>>> 
>>>>>>> Is this something I need to add to my web app container?
>>>>>>> 
>>>>>>> Thank you,
>>>>>>> Jim
>>>>>>> 
>>>>>>>> On Mar 12, 2014, at 6:52 AM, Bryan Thompson <br...@sy...> wrote:
>>>>>>>> 
>>>>>>>> I've fixed the builds in this branch.  The problems all go back to
>>>>>>>> the
>>>>>>>> changes to support configuration of jetty using jetty.xml and
>>>>>>>> web.xml.
>>>>>>>> 
>>>>>>>> I am still looking at eliminating the manual configuration of the NSS
>>>>>>>> and making code paths rely on web.xml, even for embedded use. I think
>>>>>>>> that is will work out and allowing override of the jetty.xml file
>>>>>>>> location will provide an option for complete customization.  You will
>>>>>>>> also be able to override properties in jetty.xml using environment
>>>>>>>> variables and init parameters in web.xml using the NSS command line
>>>>>>>> options.
>>>>>>>> 
>>>>>>>> Hopefully this will put an end to this aspect of the jetty
>>>>>>>> refactoring.
>>>>>>>> 
>>>>>>>> I have added a dependency on the jetty rewrite jar in preparation for
>>>>>>>> introducing load balancing into the HA cluster.  It looks like we
>>>>>>>> can do
>>>>>>>> this using the ProxyServlet in jetty.  I will also be changing the
>>>>>>>> dependencies to jetty 9.1.
>>>>>>>> 
>>>>>>>> Bryan
>>>>>>>> 
>>>>>>>> 
>>>>>>>> ----------------------------------------------------------------------
>>>>>>>> --
>>>>>>>> -
>>>>>>>> -----
>>>>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>>>>> their
>>>>>>>> applications. Written by three acclaimed leaders in the field,
>>>>>>>> this first edition is now available. Download your free book today!
>>>>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>>>>> _______________________________________________
>>>>>>>> Bigdata-developers mailing list
>>>>>>>> Big...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ------------------------------------------------------------------------
>>>>>> --
>>>>>> ----
>>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>>> their
>>>>>> applications. Written by three acclaimed leaders in the field,
>>>>>> this first edition is now available. Download your free book today!
>>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>>> _______________________________________________
>>>>>> Bigdata-developers mailing list
>>>>>> Big...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> 
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers

Re: [Bigdata-developers] RDR branch builds

[Bryan T. <br...@sy...>]

The problem is in the BigdataServlet at line 80. Working on it.

> On Mar 26, 2014, at 9:08 AM, "Jim Balhoff" <ba...@ne...> wrote:
> 
> This didn't fix the issue for me, but for the time being I have copied jetty-proxy-9.1.3.v20140225.jar to WEB-INF/lib and it seems to be working.
> 
> Thank you,
> Jim
> 
> 
>> On Mar 26, 2014, at 10:48 AM, Bryan Thompson <br...@sy...> wrote:
>> 
>> Try again.  There was a jetty import in
>> com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener that was
>> causing a failure.
>> 
>> Committed revision r8017.
>> 
>> 
>> bryan
>> 
>> 
>>> On 3/26/14 8:42 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>> 
>>> That line is commented out in my web.xml. From tomcat 7 I have this in
>>> the log:
>>> 
>>> SEVERE: Exception sending context initialized event to listener instance
>>> of class com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener
>>> java.lang.NoClassDefFoundError: org/eclipse/jetty/proxy/ProxyServlet
>>>    at java.lang.ClassLoader.defineClass1(Native Method)
>>>    at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
>>>    at 
>>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>>>    at 
>>> org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClass
>>> Loader.java:2888)
>>>    at 
>>> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.j
>>> ava:1172)
>>>    at 
>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>> ava:1680)
>>>    at 
>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>> ava:1558)
>>>    at 
>>> com.bigdata.rdf.sail.webapp.BigdataServlet.<clinit>(BigdataServlet.java:80
>>> )
>>>    at 
>>> com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener.contextInitia
>>> lized(BigdataRDFServletContextListener.java:411)
>>>    at 
>>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.jav
>>> a:4797)
>>>    at 
>>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.jav
>>> a:5291)
>>>    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>>    at 
>>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java
>>> :901)
>>>    at 
>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>>>    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>>>    at 
>>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:111
>>> 4)
>>>    at 
>>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java
>>> :1673)
>>>    at 
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>>    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>>    at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
>>> 1145)
>>>    at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
>>> :615)
>>>    at java.lang.Thread.run(Thread.java:744)
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.eclipse.jetty.proxy.ProxyServlet
>>>    at 
>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>> ava:1713)
>>>    at 
>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>>> ava:1558)
>>>    ... 22 more
>>> 
>>> 
>>>> On Mar 26, 2014, at 10:32 AM, Bryan Thompson <br...@sy...> wrote:
>>>> 
>>>> If you uncomment this line in web.xml then it will attempt to resolve
>>>> the
>>>> HALoadBalancerServlet and that would drag in the ProxyServlet.
>>>> 
>>>> 
>>>> 
>>>> <servlet-class>com.bigdata.rdf.sail.webapp.HALoadBalancerServlet</servlet
>>>> -c
>>>> lass>
>>>> 
>>>> 
>>>> 
>>>> Bryan
>>>> 
>>>>> On 3/26/14 8:30 AM, "Bryan Thompson" <br...@sy...> wrote:
>>>>> 
>>>>> There are several new jars for jetty 9.  One of them includes this
>>>>> servlet
>>>>> (jetty-proxy).  Make sure that these are in place when using jetty.
>>>>> 
>>>>> These jars should not be required for the tomcat war.  Can you send the
>>>>> full exception?  I'd like to see where the exception is being thrown
>>>>> from.
>>>>> 
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-rewrite-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-proxy-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-webapp-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/servlet-api-3.1.0.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-xml-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-io-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-continuation-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-util-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-client-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-security-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-http-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-servlet-9.1.3.v20140225.jar
>>>>> 
>>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>>> /j
>>>>> e
>>>>> tty/jetty-server-9.1.3.v20140225.jar
>>>>> 
>>>>> 
>>>>> 
>>>>> Bryan
>>>>> 
>>>>>> On 3/26/14 8:26 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>>>>> 
>>>>>> I am having trouble running the RDR branch bigdata.war in both tomcat
>>>>>> and
>>>>>> jetty. I get the error:
>>>>>> 
>>>>>> java.lang.ClassNotFoundException: org.eclipse.jetty.proxy.ProxyServlet
>>>>>> 
>>>>>> Is this something I need to add to my web app container?
>>>>>> 
>>>>>> Thank you,
>>>>>> Jim
>>>>>> 
>>>>>>> On Mar 12, 2014, at 6:52 AM, Bryan Thompson <br...@sy...> wrote:
>>>>>>> 
>>>>>>> I've fixed the builds in this branch.  The problems all go back to
>>>>>>> the
>>>>>>> changes to support configuration of jetty using jetty.xml and
>>>>>>> web.xml.
>>>>>>> 
>>>>>>> I am still looking at eliminating the manual configuration of the NSS
>>>>>>> and making code paths rely on web.xml, even for embedded use. I think
>>>>>>> that is will work out and allowing override of the jetty.xml file
>>>>>>> location will provide an option for complete customization.  You will
>>>>>>> also be able to override properties in jetty.xml using environment
>>>>>>> variables and init parameters in web.xml using the NSS command line
>>>>>>> options.
>>>>>>> 
>>>>>>> Hopefully this will put an end to this aspect of the jetty
>>>>>>> refactoring.
>>>>>>> 
>>>>>>> I have added a dependency on the jetty rewrite jar in preparation for
>>>>>>> introducing load balancing into the HA cluster.  It looks like we
>>>>>>> can do
>>>>>>> this using the ProxyServlet in jetty.  I will also be changing the
>>>>>>> dependencies to jetty 9.1.
>>>>>>> 
>>>>>>> Bryan
>>>>>>> 
>>>>>>> 
>>>>>>> ----------------------------------------------------------------------
>>>>>>> --
>>>>>>> -
>>>>>>> -----
>>>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>>>> their
>>>>>>> applications. Written by three acclaimed leaders in the field,
>>>>>>> this first edition is now available. Download your free book today!
>>>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>>>> _______________________________________________
>>>>>>> Bigdata-developers mailing list
>>>>>>> Big...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>>>> 
>>>>> 
>>>>> 
>>>>> ------------------------------------------------------------------------
>>>>> --
>>>>> ----
>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>> their
>>>>> applications. Written by three acclaimed leaders in the field,
>>>>> this first edition is now available. Download your free book today!
>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>> _______________________________________________
>>>>> Bigdata-developers mailing list
>>>>> Big...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> 

Re: [Bigdata-developers] RDR branch builds

[Jim B. <ba...@ne...>]

This didn't fix the issue for me, but for the time being I have copied jetty-proxy-9.1.3.v20140225.jar to WEB-INF/lib and it seems to be working.

Thank you,
Jim


On Mar 26, 2014, at 10:48 AM, Bryan Thompson <br...@sy...> wrote:

> Try again.  There was a jetty import in
> com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener that was
> causing a failure.
> 
> Committed revision r8017.
> 
> 
> bryan
> 
> 
> On 3/26/14 8:42 AM, "Jim Balhoff" <ba...@ne...> wrote:
> 
>> That line is commented out in my web.xml. From tomcat 7 I have this in
>> the log:
>> 
>> SEVERE: Exception sending context initialized event to listener instance
>> of class com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener
>> java.lang.NoClassDefFoundError: org/eclipse/jetty/proxy/ProxyServlet
>> 	at java.lang.ClassLoader.defineClass1(Native Method)
>> 	at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
>> 	at 
>> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
>> 	at 
>> org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClass
>> Loader.java:2888)
>> 	at 
>> org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.j
>> ava:1172)
>> 	at 
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>> ava:1680)
>> 	at 
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>> ava:1558)
>> 	at 
>> com.bigdata.rdf.sail.webapp.BigdataServlet.<clinit>(BigdataServlet.java:80
>> )
>> 	at 
>> com.bigdata.rdf.sail.webapp.BigdataRDFServletContextListener.contextInitia
>> lized(BigdataRDFServletContextListener.java:411)
>> 	at 
>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.jav
>> a:4797)
>> 	at 
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.jav
>> a:5291)
>> 	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> 	at 
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java
>> :901)
>> 	at 
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>> 	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
>> 	at 
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:111
>> 4)
>> 	at 
>> org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java
>> :1673)
>> 	at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> 	at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
>> 1145)
>> 	at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
>> :615)
>> 	at java.lang.Thread.run(Thread.java:744)
>> Caused by: java.lang.ClassNotFoundException:
>> org.eclipse.jetty.proxy.ProxyServlet
>> 	at 
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>> ava:1713)
>> 	at 
>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.j
>> ava:1558)
>> 	... 22 more
>> 
>> 
>> On Mar 26, 2014, at 10:32 AM, Bryan Thompson <br...@sy...> wrote:
>> 
>>> If you uncomment this line in web.xml then it will attempt to resolve
>>> the
>>> HALoadBalancerServlet and that would drag in the ProxyServlet.
>>> 
>>> 
>>> 
>>> <servlet-class>com.bigdata.rdf.sail.webapp.HALoadBalancerServlet</servlet
>>> -c
>>> lass>
>>> 
>>> 
>>> 
>>> Bryan
>>> 
>>> On 3/26/14 8:30 AM, "Bryan Thompson" <br...@sy...> wrote:
>>> 
>>>> There are several new jars for jetty 9.  One of them includes this
>>>> servlet
>>>> (jetty-proxy).  Make sure that these are in place when using jetty.
>>>> 
>>>> These jars should not be required for the tomcat war.  Can you send the
>>>> full exception?  I'd like to see where the exception is being thrown
>>>> from.
>>>> 
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-rewrite-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-proxy-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-webapp-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/servlet-api-3.1.0.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-xml-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-io-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-continuation-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-util-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-client-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-security-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-http-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-servlet-9.1.3.v20140225.jar
>>>> 
>>>> file://localhost/Users/bryan/Documents/workspace/RDR_NEW_SVN/bigdata/lib
>>>> /j
>>>> e
>>>> tty/jetty-server-9.1.3.v20140225.jar
>>>> 
>>>> 
>>>> 
>>>> Bryan
>>>> 
>>>> On 3/26/14 8:26 AM, "Jim Balhoff" <ba...@ne...> wrote:
>>>> 
>>>>> I am having trouble running the RDR branch bigdata.war in both tomcat
>>>>> and
>>>>> jetty. I get the error:
>>>>> 
>>>>> java.lang.ClassNotFoundException: org.eclipse.jetty.proxy.ProxyServlet
>>>>> 
>>>>> Is this something I need to add to my web app container?
>>>>> 
>>>>> Thank you,
>>>>> Jim
>>>>> 
>>>>> On Mar 12, 2014, at 6:52 AM, Bryan Thompson <br...@sy...> wrote:
>>>>> 
>>>>>> I've fixed the builds in this branch.  The problems all go back to
>>>>>> the
>>>>>> changes to support configuration of jetty using jetty.xml and
>>>>>> web.xml.
>>>>>> 
>>>>>> I am still looking at eliminating the manual configuration of the NSS
>>>>>> and making code paths rely on web.xml, even for embedded use. I think
>>>>>> that is will work out and allowing override of the jetty.xml file
>>>>>> location will provide an option for complete customization.  You will
>>>>>> also be able to override properties in jetty.xml using environment
>>>>>> variables and init parameters in web.xml using the NSS command line
>>>>>> options.
>>>>>> 
>>>>>> Hopefully this will put an end to this aspect of the jetty
>>>>>> refactoring.
>>>>>> 
>>>>>> I have added a dependency on the jetty rewrite jar in preparation for
>>>>>> introducing load balancing into the HA cluster.  It looks like we
>>>>>> can do
>>>>>> this using the ProxyServlet in jetty.  I will also be changing the
>>>>>> dependencies to jetty 9.1.
>>>>>> 
>>>>>> Bryan
>>>>>> 
>>>>>> 
>>>>>> ----------------------------------------------------------------------
>>>>>> --
>>>>>> -
>>>>>> -----
>>>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>>>> their
>>>>>> applications. Written by three acclaimed leaders in the field,
>>>>>> this first edition is now available. Download your free book today!
>>>>>> http://p.sf.net/sfu/13534_NeoTech
>>>>>> _______________________________________________
>>>>>> Bigdata-developers mailing list
>>>>>> Big...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------
>>>> --
>>>> ----
>>>> Learn Graph Databases - Download FREE O'Reilly Book
>>>> "Graph Databases" is the definitive new guide to graph databases and
>>>> their
>>>> applications. Written by three acclaimed leaders in the field,
>>>> this first edition is now available. Download your free book today!
>>>> http://p.sf.net/sfu/13534_NeoTech
>>>> _______________________________________________
>>>> Bigdata-developers mailing list
>>>> Big...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>> 
>> 
>