Mailing-List: contact dev-help@roller.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@roller.apache.org
Received-SPF: pass (athena.apache.org: domain of snoopdave@gmail.com
 designates 74.125.83.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=ZLI7hRgnKxASQrdcWbBIGMGSyXgx/htY/S0xzpn6SLZNgGw6oDRoJ5sdmvTFx0f0ao
         CZEFwLkb5fSLq+Y8Q2syLrD3KLy+88RHnwVnMQopEtvmrGcyqWwZFMT32Nh5pyOznEi+
         AZ/8iL79U9VAtCMwriShOV3Y0SNzWckapldv4=
MIME-Version: 1.0
Date: Sat, 20 Feb 2010 08:49:37 -0500
Message-ID: <8fb9ac721002200549wa04b2a5i6207579136e33914@mail.gmail.com>
Subject: Possible OpenJPA or Derby bug? Re: svn commit: r911806 - in
	/roller/trunk
From: Dave <snoopdave@gmail.com>
To: dev@roller.apache.org
Cc: Craig L Russell <Craig.Russell@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I'm tired of banging my head against this problem, so I'm reaching out
for help...

The Maven build works fine on Mac, but under Windows XP the build
fails during testing. The build starts Derby, creates tables and then
runs a bunch of tests. At some point, the tests start failing with an
exception of type java.net.BindException (see below). It's like
OpenJPA or the Derby client somehow lose the connection to Derby.

I have no idea if this is an OpenJPA bug, a Derby problem or a result
of some sin we are committing in the Roller tests/build process. If I
remove the test that is failing, then some other test will fail with
the same problem, so I don't think the problem is specific to one
test.

Any ideas from the OpenJPA or Derby experts out there? What types of
problems would lead to a bind exception on the client-side? What
should I do to debug this?

Thanks,
Dave


On Fri, Feb 19, 2010 at 8:20 AM,  <snoopdave@apache.org> wrote:
> Author: snoopdave
> Date: Fri Feb 19 13:20:20 2010
> New Revision: 911806
>
> URL: http://svn.apache.org/viewvc?rev=3D911806&view=3Drev
> Log:
> Fixes to make more of the Maven build work on Windows XP. Currently, at l=
east on my machine, the build fails while running weblogger-business tests.=
 After the bind exception below all tests fail. Maybe we are hitting some w=
eird OpenJPA or Derby Client bug?
>
> <openjpa-1.2.1-r752877:753278 nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: java.net.BindExcepti=
on :
> Error connecting to server localhost on port 3219 with message Address al=
ready in use: connect.
> =A0 =A0 =A0 =A0at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDicti=
onary.java:4232)
> [...]
> =A0 =A0 =A0 =A0at org.apache.openjpa.persistence.QueryImpl.getResultList(=
QueryImpl.java:294)
> =A0 =A0 =A0 =A0at org.apache.roller.weblogger.business.jpa.JPAUserManager=
Impl.getUsers(JPAUserManagerImpl.java:309)
> =A0 =A0 =A0 =A0at org.apache.roller.weblogger.business.jpa.JPAUserManager=
Impl.addUser(JPAUserManagerImpl.java:97)
> =A0 =A0 =A0 =A0at org.apache.roller.weblogger.TestUtils.setupUser(TestUti=
ls.java:132)
> =A0 =A0 =A0 =A0at org.apache.roller.weblogger.business.WeblogEntryTest.se=
tUp(WeblogEntryTest.java:76)