You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Jukka Zitting <jz...@adobe.com> on 2011/02/09 16:03:23 UTC
[VOTE] Release Apache Jackrabbit 2.2.4
Hi,
A candidate for the Jackrabbit 2.2.4 release is available at:
http://people.apache.org/~jukka/jackrabbit/2.2.4/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/jackrabbit/tags/2.2.4/
The SHA1 checksum of the archive is
210a5056a4ceb711e1e66995aafefbab51753c5a.
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-048/
Please vote on releasing this package as Apache Jackrabbit 2.2.4.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[ ] +1 Release this package as Apache Jackrabbit 2.2.4
[ ] -1 Do not release this package because...
My vote is +1.
--
Jukka Zitting
[RESULT] [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Wed, Feb 9, 2011 at 4:03 PM, Jukka Zitting <jz...@adobe.com> wrote:
> Please vote on releasing this package as Apache Jackrabbit 2.2.4.
This vote passes as follows:
+1 Claus Köll
+1 Jukka Zitting
+1 Serge Huber
+1 Thomas Müller
Thanks for voting! I'll push the release out.
BR,
Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Serge Huber <sh...@jahia.com>.
I agree, let's cut 2.2.4 as it is. Here's my vote : +1 :)
And I hope, for my sake and other's with non-standard configs, that 2.2.5 will be right behind :)
Regards,
Serge...
On 14 févr. 2011, at 14:18, Jukka Zitting wrote:
> Hi,
>
> On 02/14/2011 01:45 PM, Serge Huber wrote:
>> I must say I'm not very familiar with the process. Is it possible to
>> release a 2.2.4 that includes this fix or is it too late in the
>> process ? Otherwise I would say let's cut 2.2.4 as it is and prepare
>> this for 2.2.5.
>
> I like to upgrade the version number whenever a new release candidate is made to avoid confusion. For example we cancelled the 2.2.3 release vote and cut the 2.2.4 candidate instead to get the somewhat critical deadlock and database journal fixes included.
>
> Version numbers are cheap and it's not a big deal to re-cut a release, but in this case I think the benefit is not worth the trouble of a separate vote.
>
> --
> Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 02/14/2011 01:45 PM, Serge Huber wrote:
> I must say I'm not very familiar with the process. Is it possible to
> release a 2.2.4 that includes this fix or is it too late in the
> process ? Otherwise I would say let's cut 2.2.4 as it is and prepare
> this for 2.2.5.
I like to upgrade the version number whenever a new release candidate is
made to avoid confusion. For example we cancelled the 2.2.3 release vote
and cut the 2.2.4 candidate instead to get the somewhat critical
deadlock and database journal fixes included.
Version numbers are cheap and it's not a big deal to re-cut a release,
but in this case I think the benefit is not worth the trouble of a
separate vote.
--
Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Thomas Mueller <mu...@adobe.com>.
+1
I think the change in the test case is not relevant for most users; first,
because it's just a test case, and second, because it will only appear in
specific (non-standard) configurations. (Of course it's still a nuisance
and I will fix it.)
Regards,
Thomas
On 2/14/11 1:45 PM, "Serge Huber" <sh...@jahia.com> wrote:
>
>Hello Jukka,
>
>I must say I'm not very familiar with the process. Is it possible to
>release a 2.2.4 that includes this fix or is it too late in the process ?
>Otherwise I would say let's cut 2.2.4 as it is and prepare this for 2.2.5.
>
>Regards,
> Serge Huber.
>
>On 14 févr. 2011, at 13:34, Jukka Zitting wrote:
>
>> Hi,
>>
>> On 02/14/2011 11:19 AM, Serge Huber wrote:
>>> I just tested the patch and this works fine here.
>>
>> With that sorted out, do you think we should cut a 2.2.5 release with
>>this fix included, or can we go forward with 2.2.4 as-is (I still need
>>one +1)? It's just a test issue that occurs in a specific environment,
>>so I think we should be fine to release 2.2.4 like this.
>>
>> --
>> Jukka Zitting
>
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Serge Huber <sh...@jahia.com>.
Hello Jukka,
I must say I'm not very familiar with the process. Is it possible to release a 2.2.4 that includes this fix or is it too late in the process ? Otherwise I would say let's cut 2.2.4 as it is and prepare this for 2.2.5.
Regards,
Serge Huber.
On 14 févr. 2011, at 13:34, Jukka Zitting wrote:
> Hi,
>
> On 02/14/2011 11:19 AM, Serge Huber wrote:
>> I just tested the patch and this works fine here.
>
> With that sorted out, do you think we should cut a 2.2.5 release with this fix included, or can we go forward with 2.2.4 as-is (I still need one +1)? It's just a test issue that occurs in a specific environment, so I think we should be fine to release 2.2.4 like this.
>
> --
> Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 02/14/2011 11:19 AM, Serge Huber wrote:
> I just tested the patch and this works fine here.
With that sorted out, do you think we should cut a 2.2.5 release with
this fix included, or can we go forward with 2.2.4 as-is (I still need
one +1)? It's just a test issue that occurs in a specific environment,
so I think we should be fine to release 2.2.4 like this.
--
Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Serge Huber <sh...@jahia.com>.
Hello Thomas,
I just tested the patch and this works fine here. Thanks a lot, I suggest you commit it also on the 2.2 branch if that's ok ?
Best regards,
Serge Huber.
On 14 févr. 2011, at 10:50, Thomas Mueller wrote:
> Hi,
>
> The H2 database server thinks that the localhost connection is actually
> coming from another machine, and therefore reject it (for security
> reasons). To disable this check, apply the following patch:
>
> ### Eclipse Workspace Patch 1.0
> #P jackrabbit-core
> Index: src/test/java/org/apache/jackrabbit/core/cluster/DbClusterTest.java
> ===================================================================
> ---
> src/test/java/org/apache/jackrabbit/core/cluster/DbClusterTest.java (revisi
> on 1067983)
> +++
> src/test/java/org/apache/jackrabbit/core/cluster/DbClusterTest.java (workin
> g copy)
> @@ -37,9 +37,9 @@
> public void setUp() throws Exception {
> deleteAll();
> server1 = Server.createTcpServer("-tcpPort", "9001", "-baseDir",
> - "./target/dbClusterTest/db1").start();
> + "./target/dbClusterTest/db1", "-tcpAllowOthers").start();
> server2 = Server.createTcpServer("-tcpPort", "9002", "-baseDir",
> - "./target/dbClusterTest/db2").start();
> + "./target/dbClusterTest/db2", "-tcpAllowOthers").start();
> FileUtils.copyFile(
> new
> File("./src/test/resources/org/apache/jackrabbit/core/cluster/repository-h2
> .xml"),
> new File("./target/dbClusterTest/node1/repository.xml"));
>
>
>
> I will apply it in the trunk if this solves the problem for you.
>
> Regards,
> Thomas
>
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Thomas Mueller <mu...@adobe.com>.
Hi,
The H2 database server thinks that the localhost connection is actually
coming from another machine, and therefore reject it (for security
reasons). To disable this check, apply the following patch:
### Eclipse Workspace Patch 1.0
#P jackrabbit-core
Index: src/test/java/org/apache/jackrabbit/core/cluster/DbClusterTest.java
===================================================================
---
src/test/java/org/apache/jackrabbit/core/cluster/DbClusterTest.java (revisi
on 1067983)
+++
src/test/java/org/apache/jackrabbit/core/cluster/DbClusterTest.java (workin
g copy)
@@ -37,9 +37,9 @@
public void setUp() throws Exception {
deleteAll();
server1 = Server.createTcpServer("-tcpPort", "9001", "-baseDir",
- "./target/dbClusterTest/db1").start();
+ "./target/dbClusterTest/db1", "-tcpAllowOthers").start();
server2 = Server.createTcpServer("-tcpPort", "9002", "-baseDir",
- "./target/dbClusterTest/db2").start();
+ "./target/dbClusterTest/db2", "-tcpAllowOthers").start();
FileUtils.copyFile(
new
File("./src/test/resources/org/apache/jackrabbit/core/cluster/repository-h2
.xml"),
new File("./target/dbClusterTest/node1/repository.xml"));
I will apply it in the trunk if this solves the problem for you.
Regards,
Thomas
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Serge Huber <sh...@jahia.com>.
Thank you very much for your detailed answer, I did indeed have something strange in my etc/hosts file but once removed it didn't change anything.
Here is the information you requested :
localhost:h2 loom$ cat /etc/hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
./build.sh testNetwork
localhost:localhost/10.X.37.XXX
localhost/10.X.37.XXX
localhost/10.X.129.2
localhost/10.X.55.2
localhost/192.168.74.1
localhost/192.168.223.1
localhost/fe80:0:0:0:225:4bff:fea6:8410%4
localhost/fe80:0:0:0:21c:42ff:fe00:0%7
localhost/fe80:0:0:0:21c:42ff:fe00:1%8
getLocalHost:localhost/127.0.0.1
/127.0.0.1
byName:/127.0.0.1
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=59901]
server accepting
client:/127.0.0.1:59901
server accepted:Socket[addr=/127.0.0.1,port=59902,localport=59901]
client:Socket[addr=/127.0.0.1,port=59901,localport=59902]
server read:123
client read:234
done
Done in 1430 ms
server closing
server done
I have VMWare and ShareTool installed, which are probably why all these interfaces are present. I also obscured some adresses just to be on the same side :)
I would prefer not to disable the test case, but rather improve it so that it handles this configuration.
cheers,
Serge...
On 14 févr. 2011, at 09:48, Thomas Mueller wrote:
> Hi,
>
>> Remote connections to this server are not allowed, see -tcpAllowOthers
>> [90117-149]
>
> This looks more like a network problem with the H2 database than a problem
> with Jackrabbit. It might be a network configuration problem, or another
> service is already running on the ports 9001 or 9002. This test case
> starts two H2 servers on port 9001 and 9002, and then tries to connect to
> them over the local IP address (not localhost). To find out if it's a
> network config problem, could you check your /etc/hosts file for weird
> entries? I saw similar problems before, but I don't know the root cause.
> One option, of course, is to disable this test case, but that would be a
> bit sad, because it's the only clustering test case. To find out if it's
> really a network config problem, please download the H2 database
> (h2database.com), and run "./build.sh testNetwork" and send me the result
> (only the last part; the system properties are not relevant). See below
> for what I get on my machine (Mac OS X as well). It might be possible to
> work around the problem by setting the system property "h2.bindAddress" to
> "localhost" (but I didn't actually test this).
>
> cat /etc/hosts
>
> 127.0.0.1 localhost
> 255.255.255.255 broadcasthost
> ::1 localhost
> fe80::1%lo0 localhost
>
>
>
> ./build.sh testNetwork
>
> localhost:localhost/127.0.0.1
> localhost/127.0.0.1
> localhost/0:0:0:0:0:0:0:1
> localhost/fe80:0:0:0:0:0:0:1%1
> getLocalHost:Thomas-Muellers-MacBook-Pro.local/10.131.197.10
> /10.131.197.10
> byName:/10.131.197.10
> ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=63643]
> server accepting
> client:/10.131.197.10:63643
> server accepted:Socket[addr=/10.131.197.10,port=63644,localport=63643]
> client:Socket[addr=/10.131.197.10,port=63643,localport=63644]
> server read:123
> client read:234
> server closing
> server done
> done
> Done in 1742 ms
>
>
> Regards,
> Thomas
>
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Thomas Mueller <mu...@adobe.com>.
Hi,
> Remote connections to this server are not allowed, see -tcpAllowOthers
>[90117-149]
This looks more like a network problem with the H2 database than a problem
with Jackrabbit. It might be a network configuration problem, or another
service is already running on the ports 9001 or 9002. This test case
starts two H2 servers on port 9001 and 9002, and then tries to connect to
them over the local IP address (not localhost). To find out if it's a
network config problem, could you check your /etc/hosts file for weird
entries? I saw similar problems before, but I don't know the root cause.
One option, of course, is to disable this test case, but that would be a
bit sad, because it's the only clustering test case. To find out if it's
really a network config problem, please download the H2 database
(h2database.com), and run "./build.sh testNetwork" and send me the result
(only the last part; the system properties are not relevant). See below
for what I get on my machine (Mac OS X as well). It might be possible to
work around the problem by setting the system property "h2.bindAddress" to
"localhost" (but I didn't actually test this).
cat /etc/hosts
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
./build.sh testNetwork
localhost:localhost/127.0.0.1
localhost/127.0.0.1
localhost/0:0:0:0:0:0:0:1
localhost/fe80:0:0:0:0:0:0:1%1
getLocalHost:Thomas-Muellers-MacBook-Pro.local/10.131.197.10
/10.131.197.10
byName:/10.131.197.10
ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=63643]
server accepting
client:/10.131.197.10:63643
server accepted:Socket[addr=/10.131.197.10,port=63644,localport=63643]
client:Socket[addr=/10.131.197.10,port=63643,localport=63644]
server read:123
client read:234
server closing
server done
done
Done in 1742 ms
Regards,
Thomas
Re: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by Serge Huber <sh...@jahia.com>.
I'm having a strange issue when compiling rev 1068882 (which should be the same as 2.2.4).
One of the cluster test fails :
-------------------------------------------------------------------------------
Test set: org.apache.jackrabbit.core.cluster.TestAll
-------------------------------------------------------------------------------
Tests run: 10, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.266 sec <<< FAILURE!
test(org.apache.jackrabbit.core.cluster.DbClusterTest) Time elapsed: 0.159 sec <<< ERROR!
javax.jcr.RepositoryException: File system initialization failure.
at org.apache.jackrabbit.core.config.RepositoryConfigurationParser$6.getFileSystem(RepositoryConfigurationParser.java:1060)
at org.apache.jackrabbit.core.config.RepositoryConfig.getFileSystem(RepositoryConfig.java:911)
at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:285)
at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:605)
at org.apache.jackrabbit.core.cluster.DbClusterTest.test(DbClusterTest.java:62)
Caused by: org.apache.jackrabbit.core.fs.FileSystemException: failed to initialize file system
at org.apache.jackrabbit.core.fs.db.DatabaseFileSystem.init(DatabaseFileSystem.java:210)
at org.apache.jackrabbit.core.config.RepositoryConfigurationParser$6.getFileSystem(RepositoryConfigurationParser.java:1057)
... 31 more
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Remote connections to this server are not allowed, see -tcpAllowOthers [90117-149])
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at org.apache.jackrabbit.core.util.db.ConnectionHelper.getExtraNameCharacters(ConnectionHelper.java:163)
at org.apache.jackrabbit.core.util.db.ConnectionHelper.prepareDbIdentifier(ConnectionHelper.java:118)
at org.apache.jackrabbit.core.fs.db.DatabaseFileSystem.init(DatabaseFileSystem.java:193)
... 32 more
Caused by: org.h2.jdbc.JdbcSQLException: Remote connections to this server are not allowed, see -tcpAllowOthers [90117-149]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
at org.h2.message.DbException.get(DbException.java:167)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.message.DbException.get(DbException.java:133)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:69)
at java.lang.Thread.run(Thread.java:680)
at org.h2.engine.SessionRemote.done(SessionRemote.java:543)
at org.h2.engine.SessionRemote.initTransfer(SessionRemote.java:109)
at org.h2.engine.SessionRemote.connectServer(SessionRemote.java:376)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:271)
at org.h2.engine.SessionRemote.createSession(SessionRemote.java:265)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:110)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:94)
at org.h2.Driver.connect(Driver.java:62)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247)
at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221)
... 36 more
I should mention that I am testing with Mac OS X.
Is anyone else seeing this issue ?
Best regards,
Serge Huber.
On 9 févr. 2011, at 16:03, Jukka Zitting wrote:
> Hi,
>
> A candidate for the Jackrabbit 2.2.4 release is available at:
>
> http://people.apache.org/~jukka/jackrabbit/2.2.4/
>
> The release candidate is a zip archive of the sources in:
>
> http://svn.apache.org/repos/asf/jackrabbit/tags/2.2.4/
>
> The SHA1 checksum of the archive is 210a5056a4ceb711e1e66995aafefbab51753c5a.
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachejackrabbit-048/
>
> Please vote on releasing this package as Apache Jackrabbit 2.2.4.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit 2.2.4
> [ ] -1 Do not release this package because...
>
> My vote is +1.
>
> --
> Jukka Zitting
AW: [VOTE] Release Apache Jackrabbit 2.2.4
Posted by KÖLL Claus <C....@TIROL.GV.AT>.
+1
greets
claus