Reloading GBeans during development

[Stefan Arentz <st...@gmail.com>]

I'm developing my first Geronimo plugin and so far all goes well,
mostly thanks to all the great hints people are giving me here :-)

My workflow is this: write code, mvn package, deployer.jar redeploy
target/plugin.jar. This works most of the time, but what I see a lot
is that I'm running old code, even though the redeploy happened
without warnings or errors.

The problem is rather vague and not reproducable but it does happen.
I've seen my code print stuff to the log that simply isn't in the last
version anymore.

What helps is to do a full geronimo restart.

Oh, my GBean only has a reference to the Kernel and the MBeanServer.
Nobody references me. I think.

Does this sound familiar? Anything I can do about it?

 S.

Re: Reloading GBeans during development

[Aaron Mulder <am...@alumni.princeton.edu>]

On 6/17/06, Stefan Arentz <st...@gmail.com> wrote:
> That is not going to make a difference, I know for sure that the jar
> is up to date. I checked that a couple of times already. I'll try to
> investigate the Geronimo side next time it happens.

Can you post the full output of the redeploy command?

Also, are you saying that after a redeploy the code is bad, but then
if you restart Geronimo without any more deployment activity then the
code turns good?  Or are you saying that if you restart and then
redeploy again the redeploy works?

You could try increasing the memory and perm gen space in case it's a
problem with repeated class loading blowing through some kind of JVM
resource.

Thanks,
    Aaron

Re: Reloading GBeans during development

[Stefan Arentz <st...@gmail.com>]

On 6/17/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> I haven't seen this before.  Perhaps it would help to do "mvn clean
> package" instead of "mvn package" to make sure you always have the
> latest code in your JAR?

That is not going to make a difference, I know for sure that the jar
is up to date. I checked that a couple of times already. I'll try to
investigate the Geronimo side next time it happens.

 S.

Re: Reloading GBeans during development

[Aaron Mulder <am...@alumni.princeton.edu>]

I haven't seen this before.  Perhaps it would help to do "mvn clean
package" instead of "mvn package" to make sure you always have the
latest code in your JAR?

Thanks,
    Aaron

On 6/17/06, Stefan Arentz <st...@gmail.com> wrote:
> I'm developing my first Geronimo plugin and so far all goes well,
> mostly thanks to all the great hints people are giving me here :-)
>
> My workflow is this: write code, mvn package, deployer.jar redeploy
> target/plugin.jar. This works most of the time, but what I see a lot
> is that I'm running old code, even though the redeploy happened
> without warnings or errors.
>
> The problem is rather vague and not reproducable but it does happen.
> I've seen my code print stuff to the log that simply isn't in the last
> version anymore.
>
> What helps is to do a full geronimo restart.
>
> Oh, my GBean only has a reference to the Kernel and the MBeanServer.
> Nobody references me. I think.
>
> Does this sound familiar? Anything I can do about it?
>
>  S.
>