Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of mail2jimma@gmail.com
 designates 209.85.212.172 as permitted sender)
MIME-Version: 1.0
Reply-To: mail2jimma@gmail.com
In-Reply-To: <D225CD69196F3F4A9F4174B2FCA06F881208E256@S10BE002.SH10.lan>
References: 
 <CAAvMoHkKj6WvXyoQxza2dzU9Cwiv+BZ7ONBEwQ7EGa-FKGOOUQ@mail.gmail.com>
	<CAF8t5Xs7cc+tBJTq5rE076ydOOVtg14+uc2w5fR--pjmvcz1Mg@mail.gmail.com>
	<D225CD69196F3F4A9F4174B2FCA06F881208E256@S10BE002.SH10.lan>
Date: Fri, 28 Nov 2014 16:04:06 +0800
Message-ID: 
 <CAAvMoHnvrX5dhBz1U1G6PtJU4uOBmTO3zg9UVUCYqyMNparg+g@mail.gmail.com>
Subject: Re: xkms test failures
From: Jim Ma <mail2jimma@gmail.com>
To: Andrei Shakirin <ashakirin@talend.com>
Cc: "dev@cxf.apache.org" <dev@cxf.apache.org>
Content-Type: multipart/alternative; boundary=f46d044289da72c6bb0508e6b453

--f46d044289da72c6bb0508e6b453
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Andrei and Aki. Before the test running, I checked and didn't find
any process is listening port 1099. I didn't look at these test in depth,
Is it possible that karaf container is not shutdown successfully in
previous test teardown ?
BTW, port 1099 is usually started as the RMI registry port, can we
configured karaf to start with a higher number port ?

On Thu, Nov 27, 2014 at 9:58 PM, Andrei Shakirin <ashakirin@talend.com>
wrote:

> Exactly, the message "Caused by: java.rmi.server.ExportException: Port
> already in use: 1099; nested exception is:
>         java.net.BindException: Address already in use" shows some port
> conflicts.
>
> Either you have more than one Karaf container running or this port is use=
d
> by other software on your machine.
>
> Regards,
> Andrei.
>
>
> > -----Original Message-----
> > From: Aki Yoshida [mailto:elakito@gmail.com]
> > Sent: Donnerstag, 27. November 2014 11:23
> > To: dev@cxf.apache.org; jim ma
> > Subject: Re: xkms test failures
> >
> > I think you have another karaf instance running on your box.
> >
> > Exception in thread "JMX Connector Thread
> > [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root]"
> > java.lang.RuntimeException:
> > Port already in use: 44444;
> >
> > 2014-11-27 3:28 GMT+01:00 Jim Ma <mail2jimma@gmail.com>:
> > > Hi,
> > > Does anyone hit these failures when run xkms integration tests ? I
> > > tried these tests from cxf 2.7.13 tag  in different machines(Fedora
> > > 20/oracle
> > > jdk7) and got the same failures.It looks the karaf container didn't
> > > start well and there are connections timeout. Full error stacktrace,
> > > please see the attached file.
> > > Do we have to involve karaf and bundle things for the xkms test ? Is
> > > there something we can improve to make these test more robust ?
> > >
> > > ValidatorCRLTest.org.apache.cxf.xkms.itests.handlers.validator.Valida=
t
> > > orCRLTest
> > > =C2=BB Runtime
> > >   JUnit4Provider.invoke:124->executeTestSet:153->execute:264 =C2=BB R=
untime
> > > Container...
> > >
> > > ValidatorTest.org.apache.cxf.xkms.itests.handlers.validator.Validator=
T
> > > est
> > > =C2=BB Runtime
> > >   JUnit4Provider.invoke:124->executeTestSet:153->execute:264 =C2=BB R=
untime
> > > Container...
> > >   XKMSServiceTest.org.apache.cxf.xkms.itests.service.XKMSServiceTest =
=C2=BB
> > > Runtime C...
> > >   JUnit4Provider.invoke:124->executeTestSet:153->execute:264 =C2=BB R=
untime
> > > Container...
> > >   XKRSSDisableTest.org.apache.cxf.xkms.itests.service.XKRSSDisableTes=
t
> > > =C2=BB Runtime
> > >   JUnit4Provider.invoke:124->executeTestSet:153->execute:264 =C2=BB R=
untime
> > > Container...
> > >
> > > Cheers,
> > > Jim
>

--f46d044289da72c6bb0508e6b453--