reading the hsqlServer.stop() javadoc, it states:

On Fri, Dec 27, 2013 at 12:33 AM, Glen Mazza <glen.ma...@gmail.com> wrote:

> JP: My problems were *mostly* solved, the DB error does pop up
> occasionally still.  :)
>
> Another solution might be to switch to the inmemdb Maven plugin that
> Roller uses for its tests and the JSPWiki Selenium tests already use (
> https://github.com/bmatthews68/inmemdb-maven-plugin).
>
> Glen
>
>
> On 12/26/2013 06:19 PM, Adrien Beau wrote:
>
>> Unfortunately I won't be able to test JSPWiki before January 3rd. It seems
>> Marco's patch is a  sufficient solution for now.
>> Le 26 déc. 2013 21:36, "Juan Pablo Santos Rodríguez" <
>> juanpablo.san...@gmail.com> a écrit :
>>
>>  Hi Adrien,
>>>
>>> since Glen said on another thread that his hsqldb related problems where
>>> solved, would you mind replacing lines(95-96) of o.a.w.HsqlDbUtils on
>>> $SVN/jspwiki-war/src/test/java:
>>>          hsqlServer.setSilent(true);   // be quiet during junit tests
>>>          hsqlServer.setLogWriter(null);  // and even more quiet
>>>
>>> with:
>>>          hsqlServer.setSilent(false);   // be quiet during junit tests
>>>          hsqlServer.setLogWriter(new PrintWriter(System.out));  // and
>>> even
>>> more quiet
>>>
>>> to see if that enables some output signaling what's going wrong with the
>>> db-related tests on your environment?
>>>
>>>
>>> thanks & br,
>>> juan pablo
>>>
>>>
>>>
>>> On Sun, Dec 22, 2013 at 8:31 PM, Glen Mazza <glen.ma...@gmail.com>
>>> wrote:
>>>
>>>  Same errors for me on port 9001 as mentioned earlier.  I'm not aware of
>>>> using any firewall, this is just my personal laptop with an Internet
>>>> connection.
>>>>
>>>> Glen
>>>>
>>>>
>>>> On 12/22/2013 02:27 PM, Juan Pablo Santos Rodríguez wrote:
>>>>
>>>>  Hi,
>>>>>
>>>>> I'm on W7-64bits, running fine without problems with both JDK 1.6.0_19
>>>>>
>>>> and
>>>
>>>> 1.7.0_03. Maybe some kind of firewall configuration is stepping by?
>>>>>
>>>> Also,
>>>
>>>> builds.apache.org runs jspwiki jobs on ubuntu boxes. Did reverting to
>>>>> 9001
>>>>> fix the build?
>>>>>
>>>>> The point to switch to 9321 as Harry pointed out was to prevent
>>>>> intermittent errors on builds.a.o, but the same error is persisting on
>>>>> analysis.a.o/jenkins (I'll ask later on infra to see if something
>>>>>
>>>> running
>>>
>>>> on that port on that machine)
>>>>>
>>>>>
>>>>> br,
>>>>> juan pablo
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Dec 22, 2013 at 8:20 PM, Glen Mazza <glen.ma...@gmail.com>
>>>>>
>>>> wrote:
>>>
>>>>   Thanks for the report, so it's not just me.  I may need to check out
>>>>>
>>>>>> older
>>>>>> versions to try and determine the revision that caused this to occur
>>>>>> in
>>>>>> order to identify the problem (ugh).
>>>>>>
>>>>>> Glen
>>>>>>
>>>>>>
>>>>>> On 12/22/2013 11:57 AM, Adrien Beau wrote:
>>>>>>
>>>>>>   For your information, I encountered the same issue on Windows 7
>>>>>>
>>>>>>> 64-bits 2 days ago when I was trying the RC, using JDK 1.7.0_45
>>>>>>> (64-bit server VM). The machine is a somewhat fresh install, Port
>>>>>>> 9321
>>>>>>> is not open. I have not had the time to analyze this further.
>>>>>>>
>>>>>>> On Sun, Dec 22, 2013 at 3:06 PM, Harry Metske <
>>>>>>> harry.met...@gmail.com
>>>>>>> wrote:
>>>>>>>
>>>>>>>   metskem@athena ~/idea-workspace/jspwiki/jspwiki-war $ mvn
>>>>>>> --version
>>>>>>>
>>>>>>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>>>>>> 2013-02-19
>>>>>>>> 14:51:28+0100)
>>>>>>>> Maven home: /usr/local/apache-maven-3.0.5
>>>>>>>> Java version: 1.6.0_29, vendor: Sun Microsystems Inc.
>>>>>>>> Java home: /opt/jdk1.6.0_29/jre
>>>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>>>> OS name: "linux", version: "3.5.0-17-generic", arch: "i386", family:
>>>>>>>> "unix"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 22 December 2013 14:32, Glen Mazza <glen.ma...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>    What Maven version are you running? I'm on 3.1...
>>>>>>>>
>>>>>>>>  Glen
>>>>>>>>>
>>>>>>>>> On 12/22/2013 08:13 AM, Harry Metske wrote:
>>>>>>>>>
>>>>>>>>>    I am running Ubuntu, and have not seen this issue at all.
>>>>>>>>>
>>>>>>>>>  I just ran the test suite again (while looking at the
>>>>>>>>>> jspwiki.policy.file
>>>>>>>>>> issue), and it runs fine here.
>>>>>>>>>>
>>>>>>>>>> regards,
>>>>>>>>>> Harry
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 22 December 2013 14:01, Glen Mazza <glen.ma...@gmail.com>
>>>>>>>>>>
>>>>>>>>> wrote:
>>>
>>>>     No, I wasn't able to find 9321 in use anywhere using the
>>>>>>>>>> "netstat" (
>>>>>>>>>>
>>>>>>>>>>   http://askubuntu.com/a/278455). And same problem when I flipped
>>>>>>>>>>
>>>>>>>>> it
>>>
>>>> back
>>>>>>>>>>> to 9001 in
>>>>>>>>>>>
>>>>>>>>>> jspwiki-war/src/test/resources/jspwiki-custom.properties
>>>
>>>> (both
>>>>>>>>>>> places).   I wonder if our test processes are trying to activate
>>>>>>>>>>> that
>>>>>>>>>>> port
>>>>>>>>>>> twice.  Anybody else using Linux/Ubuntu and can get the build to
>>>>>>>>>>> work?
>>>>>>>>>>>
>>>>>>>>>>> Glen
>>>>>>>>>>>
>>>>>>>>>>> On 12/22/2013 07:20 AM, Harry Metske wrote:
>>>>>>>>>>>
>>>>>>>>>>>     Glen,
>>>>>>>>>>>
>>>>>>>>>>>   since rev 1551279 (16 Dec) the port was changed from 9001 to
>>>>>>>>>>>
>>>>>>>>>> 9321.
>>>
>>>> This
>>>>>>>>>>>> was
>>>>>>>>>>>> done to prevent similar intermittent errors on the apache
>>>>>>>>>>>> Jenkins
>>>>>>>>>>>> machine
>>>>>>>>>>>> (assuming other projects running on the same machine were also
>>>>>>>>>>>> using
>>>>>>>>>>>> HSQLDB
>>>>>>>>>>>> with the same port).
>>>>>>>>>>>> Do you have some running on that 9321 port maybe ?
>>>>>>>>>>>>
>>>>>>>>>>>> regards,
>>>>>>>>>>>> Harry
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 22 December 2013 13:04, Glen Mazza <glen.ma...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>      Hi all, I can't build trunk--doing JDK 1.7.0_25 on Ubuntu.
>>>>>>>>>>>>   With a
>>>>>>>>>>>> fresh
>>>>>>>>>>>>
>>>>>>>>>>>>    checkout of jspwiki from SVN into an empty folder and running
>>>>>>>>>>>> "mvn
>>>>>>>>>>>>
>>>>>>>>>>>>  clean
>>>>>>>>>>>>> install" returns these errors:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Running org.apache.wiki.auth.user.JDBCUserDatabaseTest
>>>>>>>>>>>>> [Server@396352e]: [Thread[main,5,main]]: setSilent(true)
>>>>>>>>>>>>> [Server@34a403c7]: [Thread[main,5,main]]: setSilent(true)
>>>>>>>>>>>>> Looks like your database could not be connected to - please
>>>>>>>>>>>>> make
>>>>>>>>>>>>> sure
>>>>>>>>>>>>> that
>>>>>>>>>>>>> you have started your database, exception:
>>>>>>>>>>>>>
>>>>>>>>>>>> java.sql.SQLException:
>>>
>>>> java.lang.NullPointerException java.lang.NullPointerException
>>>>>>>>>>>>> [Server@69673772]: [Thread[main,5,main]]: setSilent(true)
>>>>>>>>>>>>> [Server@69673772]: [Thread[HSQLDB Server @69673772,5,main]]:
>>>>>>>>>>>>> run()/openServerSocket():
>>>>>>>>>>>>> java.net.BindException: Address already in use
>>>>>>>>>>>>>          at java.net.PlainSocketImpl.socketBind(Native Method)
>>>>>>>>>>>>>          at java.net.AbstractPlainSocketImpl.bind(
>>>>>>>>>>>>> AbstractPlainSocketImpl.java:
>>>>>>>>>>>>> 376)
>>>>>>>>>>>>>
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Looks like your database could not be connected to - please
>>>>>>>>>>>>> make
>>>>>>>>>>>>> sure
>>>>>>>>>>>>> that
>>>>>>>>>>>>> you have started your database, exception:
>>>>>>>>>>>>>
>>>>>>>>>>>> java.sql.SQLException:
>>>
>>>> java.lang.NullPointerException java.lang.NullPointerException
>>>>>>>>>>>>> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed:
>>>>>>>>>>>>> 1.304
>>>>>>>>>>>>> sec
>>>>>>>>>>>>> <<< FAILURE! - in org.apache.wiki.auth.authorize.
>>>>>>>>>>>>> JDBCGroupDatabaseTest
>>>>>>>>>>>>> testSave(org.apache.wiki.auth.authorize.JDBCGroupDatabaseTest)
>>>>>>>>>>>>>    Time
>>>>>>>>>>>>> elapsed: 0.328 sec  <<< ERROR!
>>>>>>>>>>>>> java.sql.SQLException: java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>          at org.hsqldb.error.Error.error(Unknown Source)
>>>>>>>>>>>>>          at org.hsqldb.ClientConnection.<init>(Unknown Source)
>>>>>>>>>>>>>          at org.hsqldb.jdbc.JDBCConnection.<init>(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>          at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>          at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
>>>>>>>>>>>>>          at org.apache.wiki.TestJDBCDataSource.getConnection(
>>>>>>>>>>>>> TestJDBCDataSource.java:100)
>>>>>>>>>>>>>          at org.apache.wiki.TestJDBCDataSource.getConnection(
>>>>>>>>>>>>> TestJDBCDataSource.java:86)
>>>>>>>>>>>>>          at org.apache.wiki.auth.authorize.
>>>>>>>>>>>>> JDBCGroupDatabaseTest.setUp(
>>>>>>>>>>>>> JDBCGroupDatabaseTest.java:83)
>>>>>>>>>>>>>
>>>>>>>>>>>>> testDelete(org.apache.wiki.auth.authorize.
>>>>>>>>>>>>> JDBCGroupDatabaseTest)
>>>>>>>>>>>>> Time
>>>>>>>>>>>>> elapsed: 0.324 sec  <<< ERROR!
>>>>>>>>>>>>> java.sql.SQLException: java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>>          at org.hsqldb.error.Error.error(Unknown Source)
>>>>>>>>>>>>>          at org.hsqldb.ClientConnection.<init>(Unknown Source)
>>>>>>>>>>>>>          at org.hsqldb.jdbc.JDBCConnection.<init>(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>          at org.hsqldb.jdbc.JDBCDriver.getConnection(Unknown
>>>>>>>>>>>>> Source)
>>>>>>>>>>>>>          at org.hsqldb.jdbc.JDBCDriver.connect(Unknown Source)
>>>>>>>>>>>>>          at org.apache.wiki.TestJDBCDataSource.getConnection(
>>>>>>>>>>>>> TestJDBCDataSource.java:100)
>>>>>>>>>>>>>          at org.apache.wiki.TestJDBCDataSource.getConnection(
>>>>>>>>>>>>> TestJDBCDataSource.java:86)
>>>>>>>>>>>>>          at org.apache.wiki.auth.authorize.
>>>>>>>>>>>>> JDBCGroupDatabaseTest.setUp(
>>>>>>>>>>>>> JDBCGroupDatabaseTest.java:83)
>>>>>>>>>>>>>
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Tests in error:
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCUserDatabaseTest.setUp:131 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCGroupDatabaseTest.setUp:90 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCGroupDatabaseTest.setUp:90 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCGroupDatabaseTest.setUp:90 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>        JDBCGroupDatabaseTest.setUp:90 SQL
>>>>>>>>>>>>> java.lang.NullPointerException
>>>>>>>>>>>>> java.lang.Nu...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Tests run: 936, Failures: 0, Errors: 14, Skipped: 0
>>>>>>>>>>>>>
>>>>>>>>>>>>> The problem appears to be the "Address already in use" error
>>>>>>>>>>>>>
>>>>>>>>>>>> above
>>>
>>>> w.r.t.
>>>>>>>>>>>>> HSQLDB.  FWIW, I didn't have Tomcat or other container running
>>>>>>>>>>>>>
>>>>>>>>>>>> on
>>>
>>>> my
>>>>>>>>>>>>> machine at the time of compile, and AFAIK am not running HSQLDB
>>>>>>>>>>>>> separately
>>>>>>>>>>>>> either.  Anybody know what the problem is?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Glen
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>

Reply via email to