Ted Kirby wrote:
> I wonder if this is an openejb problem? See JIRA 2063:
> http://issues.apache.org/jira/browse/GERONIMO-2063
This has been resolved now, and was an openejb problem:
http://issues.apache.org/jira/browse/OPENEJB-287
>
> On 10/20/06, *Prasad Kashyap* <goyathlay.geronimo@gmail.com
> <mailto:goyathlay.geronimo@gmail.com>> wrote:
>
> Rick,
>
> Here is a log with veryverbose option turned on.
>
> Cheers
> Prasad
>
> On 10/19/06, Prasad Kashyap < goyathlay.geronimo@gmail.com
> <mailto:goyathlay.geronimo@gmail.com>> wrote:
> > Here is the geronimo.log which doesn't have anything more than what
> > was captured by the output of the deploy.
> >
> > I should also mention that the same plan deploys fine after a
> server restart.
> >
> > Cheers
> > Prasad
> >
> > On 10/19/06, Prasad Kashyap <goyathlay.geronimo@gmail.com
> <mailto:goyathlay.geronimo@gmail.com>> wrote:
> > > Rick,
> > >
> > > Here's the Yoko bug I was talking about. I deployed a simple
> TSSBean
> > > whose POAName attribute is set. It deployed fine. I then
> undeployed
> > > the plan. That was successfull as well. Now when I go back to
> redeploy
> > > the same plan, I get an adapter already exists exception. I have
> > > attached both the plan and the log for your scrutiny.
> > >
> > > Thanx
> > > Prasad
> > >
> > >
> > >
> >
> >
> >
>
>
>
|