I am assuming that you use "appserv-tests" infrastructure.
If so, following changes might be of help :
1) modify appserv-tests/derby.properties : db.port
2) modify "startDerby" & "stopDerby" targets in
appserv-tests/config/common.xml to use ${db:port} instead of hard-coded
value of 1527
3) If the ejb tests use "execute-ejb-sql-common" instead of default
"execute-sql-common", then "execute-ejb-sql-common" need to use
${db.url} instead of hard-coded URL.
4) Yes, any of the client/pools that were using 1527 need to be changed
accordingly.
Thanks,
-Jagadish
On Sat, 2010-12-04 at 09:13 +0530, Jagadish Prasath Ramu wrote:
> No.
>
> On Fri, 2010-12-03 at 19:40 -0800, Marina Vatkina wrote:
> > Are there existing common targets for that?
> >
> > thanks,
> > -marina
> >
> > Jagadish Prasath Ramu wrote:
> > > Yes, DerbyPool (used by jdbc/__default) uses 1527. You need to change it
> > > accordingly.
> > >
> > > Thanks,
> > > -Jagadish
> > >
> > > On Fri, 2010-12-03 at 19:16 -0800, Marina Vatkina wrote:
> > >
> > >> Right. But this is will not work with jdbc/__default resource, right?
> > >>
> > >> thanks,
> > >> -marina
> > >>
> > >> Jagadish Prasath Ramu wrote:
> > >>
> > >>> You can use
> > >>> asadmin start-database/stop-database --dbport option
> > >>>
> > >>> Thanks,
> > >>> -Jagadish
> > >>>
> > >>> On Fri, 2010-12-03 at 19:02 -0800, Marina Vatkina wrote:
> > >>>
> > >>>
> > >>>> Latest (2 weeks?) ejb devtests on hudson fail to get a derby connection
> > >>>> (on default port 1527). Is there a generic solution to use some other port?
> > >>>>
> > >>>> thanks,
> > >>>> -marina
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >
> > >