Recent changes to patches

ShortenLongURIs for dbpedia loading into VOS

2012-03-02T17:10:40Z

When loading DBpedia dataset into VOS 6.1.4, a special setting is needed to fix a problem in the current dumps with some extremely long URIs.

Unfortunately this setting is missing from the current VOS code base. It will be part of the upcoming 6.1.5 release

This patch adds the missing lines in the config reader for:

[SPARQL]
ShortenLongURIs = 1

which will enable the workaround for these long uri in the dumps.

Missing check for invalid stmt handle

2012-01-25T21:30:01Z

In VOS upto version 6.1.4 there is a check missing for an invalid stmt handle which can cause virtuoso to crash. This patch is part of the upcoming 6.1.5 release.

Connection leak in the VirtJDBC3

2011-04-12T12:19:05Z

Hi,

I encountered a connection leak with the VirtuosoXADataSource when long checkpoints (more than 1 minute) occured.
During the checkpoint, the virtuoso response times are slow as explain in the documentation but sometimes the number of max connections is exceeded. (with a minConnection set to 5 and a maxConnection set to 15, I reached more than 40 connections.)

In attachment, you can find a patch to fix this problem.
With this patch, the number of connection is still under the maxConnection value.

I hope this patch will help you.
Regards,
Eric

Concurrent access fix

2011-02-11T15:48:36Z

Hi,

I'm using the virtuoso opensource edition in version 6.1.2.
Sometimes I had a NullPointer during the execution of VirtuosoXAConnection.close().
This NullPointer occured in the method VirtuosoPooledConnection.close().
I think there are a concurrent access on VirtuosoPooledConnection attributes when the PooledConnection is in the CloseHelper and when the XAConnection is closing.

I added a "synchronized " on the close method of the VirtuosoPooledConnection. Since this update, NullPointer doesn't occur.

In attachment the patch file.

Regards,
Eric

Socket Timeout overrided

2010-09-08T09:17:00Z

Hi,

I'm currently using the virtuoso opensource 5.0.14 and the virtjdbc3.jar.
I encountered a problem with the connection timeout.
Even if the loginTimeout is set, the VirtuosoConnection uses the SQL_LOGIN_TIME_OUT defined in the virtuoso configuration file.

I think the SQL_LOGIN_TIME_OUT should be used only if the VirtuosoConnection timeout isn't set ( ie : timeout <= 0)

In attachment, you can find a patch for the version 5.0.14 which fix this problem.

Regards,
Eric

Patch for VirtJena

2010-06-22T15:32:28Z

Hi,

I encountered a bug with the virt_jena proviver when I processed a select query. (I'm using the virtuoso 5.0.14 with the provided virt_jena.jar)
The VResultSet.moveForward method never set the v_finished boolean to true and an infini loop occured.

In attachment you can find a patch for this issue.
This patch adds too the possibility to initialize the VirtDataSource and the VirtGraph using a java.sql.DataSource.

Regards,
Eric

Memory Leak in JDBC Driver

2010-03-26T07:51:01Z

Hi,

I encountered a Memory Leak with the virtuoso JDBC driver ( virtuoso opensource 5-0-14-RC2).
Some VirtuosoFuture objects aren't removed from the futures Hashtablemap in the VirtuosoConnection.

In attachment you can find a patch for this problem.
In addition, this patch allows a Rollback after a End called with the SUCCESS flags.

Regards,
Eric

Fetch size invalid

2010-03-09T16:27:29Z

Hi,

I'm using the virtuoso-5.0.13 and the virtuoso-5.0.14-RC1.
There are a problem with the VirtuosoStatement.setFetchSize();

If a value > 0 is set there aren't problem, however if the value 0 is set, the VirtuosoResultSet.next() freezes.

Here is a patch to fix this problem

Regards,
Eric

Driver Memory Leak

2010-03-03T09:30:12Z

Hi,

There are a memroy leak in the virtjdbc dirver when XA transactions are used.
When a transaction is committed or rolled back, the xid and the XATransaction objects aren't removed from the XAResourceManager map.

In attachment you can find a patch which fixes this problem.
The removeTransaction method is called at the end of the commit and the rollback in the VirtuosoXAResource class.

Regards,
Eric

[JDBC] Connection Pool returns invalid connection

2010-02-19T09:16:11Z

Hi,

In attachment you can find a patch proposal about the Connection Pool.
When the virtuoso server restarts, the getConnection method returns an invalid Connection object.
To avoid this, I checks the connection using a "SELECT 1" request (Perhaps there are a better way to do it...)

Regards,
Eric