You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by ymaraner <tp...@gmail.com> on 2013/03/12 20:09:41 UTC
MDB activation broken in 1.5.2-SNAPSHOT-80
I have a number of MDBs that were originally developed as EJB2.1 MDBs. They
were upgraded to 3.x MDBs by modifying the version of the deployment
descriptor.
When I deploy them to 1.5.1 or an early snapshot of 1.5.2, they are invoked
when an appropriate message is posted on the JMS Queue.
When I deploy them to 1.5.2-SNAPSHOT-80, they are never invoked and there
are no errors or warnings produced even though an appropriate message is
posted on the JMS Queue.
What changed in 1.5.2 that would prevent this from working?
Is there a work-around?
My activation-config looks like this in the ejb-jar.xml file:
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
FYI, I just downloaded and
installed apache-tomee-1.6.0-20130312.041113-27-plus.zip on my development
server, and TomEE/ActiveMQ is still working as designed for me as my app
implements TomEE's (very) simple MDB example (without/no consumer, just
producer, MDB w/ onMessage()).
Currently, i have apache-tomee-1.6.0-20130224.041120-11-plus.zip running on
production server, and really i have no need to use latest version of TomEE
1.6.0 SNAPSHOT, but this thread motivated me to download latest snapshot,
test, and wanted to report my test results here.
On Tue, Mar 12, 2013 at 4:47 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> the point is we have unit test on mdbs and they passed so if you have an
> issue we need something concrete to work on it
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/3/12 ymaraner <tp...@gmail.com>
>
> > When I said "it does not work" I meant that the MDB is not invoked. The
> > error is reproduced in all of the snapshots I used, but not in 1.5.1.
> >
> > I do not have a simple self-contained project that reproduces the error.
> If
> > you need that, I can try to come up with something. But it will be at
> lease
> > a few hours before I do.
> >
> > Tim Haley
> >
> >
> > On Tue, Mar 12, 2013 at 4:31 PM, Romain Manni-Bucau [via OpenEJB] <
> > ml-node+s979440n4661458h66@n4.nabble.com> wrote:
> >
> > > hmm, can you reproduce it?
> > >
> > > *Romain Manni-Bucau*
> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > http://rmannibucau.wordpress.com/>
> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > *Github: https://github.com/rmannibucau*
> > >
> > >
> > >
> > > 2013/3/12 ymaraner <[hidden email]<
> > http://user/SendEmail.jtp?type=node&node=4661458&i=0>>
> > >
> > >
> > > > Romain Manni-Bucau wrote
> > > > > can you give it a try on the 1.6.0-SNAPSHOT to check it is not a
> > > > > regression
> > > > > but "a merge error" please?
> > > >
> > > > Unfortunately it does not work in the latest 1.6.0-SNAPSHOT. I also
> > > tried
> > > > in
> > > > 1.6.0-snapshot-19 and 1.5.2-snapshot-59 since I had copies of those,
> > and
> > > it
> > > > does not work on either of them.
> > > >
> > > > It appears to be a regression that occurred sometime prior to the
> build
> > > on
> > > > Feb 4 @ 4:10am. I don't have any snapshots prior to that.
> > > >
> > > >
> > > >
> > > >
> > > > -----
> > > > - Tim
> > > > --
> > > > View this message in context:
> > > >
> > >
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661457.html
> > > > Sent from the OpenEJB User mailing list archive at Nabble.com.
> > > >
> > >
> > >
> > > ------------------------------
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > >
> > >
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661458.html
> > > To unsubscribe from MDB activation broken in 1.5.2-SNAPSHOT-80, click
> > > here<
> >
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4661455&code=dHBoYWxleUBnbWFpbC5jb218NDY2MTQ1NXwxMzE0NDUyOTky
> > >
> > > .
> > > NAML<
> >
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> > >
> > >
> >
> >
> >
> >
> > -----
> > - Tim
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661459.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by ymaraner <tp...@gmail.com>.
It turns out that when I originally configured the queues in tomee.xml, I
specified destination values that were being ignored. They are no longer
ignored and they were incorrect. My messages were being sent to the wrong
queue.
needed to be changed to:
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661510.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by Romain Manni-Bucau <rm...@gmail.com>.
did you check activemq versions, we upgraded (i dont remember if it matches
your dates) and can be the issue
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/13 ymaraner <tp...@gmail.com>
> Well, apparently I came to the wrong conclusion while debugging. I cannot
> duplicate the issue in a self-contained example.
>
> Something changed in the server that causes my code to fail, but apparently
> it was not MDB activation.
>
> I'll have to keep looking for the cause.
>
> Sorry for raising the alarm.
>
>
>
> -----
> - Tim
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661497.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by ymaraner <tp...@gmail.com>.
Well, apparently I came to the wrong conclusion while debugging. I cannot
duplicate the issue in a self-contained example.
Something changed in the server that causes my code to fail, but apparently
it was not MDB activation.
I'll have to keep looking for the cause.
Sorry for raising the alarm.
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661497.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by ymaraner <tp...@gmail.com>.
No problem, I'll see what I can come up with.
Tim Haley
On Tue, Mar 12, 2013 at 4:48 PM, Romain Manni-Bucau [via OpenEJB] <
ml-node+s979440n4661460h28@n4.nabble.com> wrote:
> the point is we have unit test on mdbs and they passed so if you have an
> issue we need something concrete to work on it
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/3/12 ymaraner <[hidden email]<http://user/SendEmail.jtp?type=node&node=4661460&i=0>>
>
>
> > When I said "it does not work" I meant that the MDB is not invoked. The
> > error is reproduced in all of the snapshots I used, but not in 1.5.1.
> >
> > I do not have a simple self-contained project that reproduces the error.
> If
> > you need that, I can try to come up with something. But it will be at
> lease
> > a few hours before I do.
> >
> > Tim Haley
> >
> >
> > On Tue, Mar 12, 2013 at 4:31 PM, Romain Manni-Bucau [via OpenEJB] <
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=4661460&i=1>>
> wrote:
> >
> > > hmm, can you reproduce it?
> > >
> > > *Romain Manni-Bucau*
> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > > *Blog: **http://rmannibucau.wordpress.com/*<
> > > http://rmannibucau.wordpress.com/>
> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > > *Github: https://github.com/rmannibucau*
> > >
> > >
> > >
> > > 2013/3/12 ymaraner <[hidden email]<
> > http://user/SendEmail.jtp?type=node&node=4661458&i=0>>
> > >
> > >
> > > > Romain Manni-Bucau wrote
> > > > > can you give it a try on the 1.6.0-SNAPSHOT to check it is not a
> > > > > regression
> > > > > but "a merge error" please?
> > > >
> > > > Unfortunately it does not work in the latest 1.6.0-SNAPSHOT. I also
> > > tried
> > > > in
> > > > 1.6.0-snapshot-19 and 1.5.2-snapshot-59 since I had copies of those,
> > and
> > > it
> > > > does not work on either of them.
> > > >
> > > > It appears to be a regression that occurred sometime prior to the
> build
> > > on
> > > > Feb 4 @ 4:10am. I don't have any snapshots prior to that.
> > > >
> > > >
> > > >
> > > >
> > > > -----
> > > > - Tim
> > > > --
> > > > View this message in context:
> > > >
> > >
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661457.html
> > > > Sent from the OpenEJB User mailing list archive at Nabble.com.
> > > >
> > >
> > >
> > > ------------------------------
> > > If you reply to this email, your message will be added to the
> discussion
> > > below:
> > >
> > >
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661458.html
> > > To unsubscribe from MDB activation broken in 1.5.2-SNAPSHOT-80, click
> > > here<
> >
> >
> > > .
> > > NAML<
> >
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
>
> > >
> > >
> >
> >
> >
> >
> > -----
> > - Tim
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661459.html
>
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661460.html
> To unsubscribe from MDB activation broken in 1.5.2-SNAPSHOT-80, click
> here<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4661455&code=dHBoYWxleUBnbWFpbC5jb218NDY2MTQ1NXwxMzE0NDUyOTky>
> .
> NAML<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661461.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by Romain Manni-Bucau <rm...@gmail.com>.
the point is we have unit test on mdbs and they passed so if you have an
issue we need something concrete to work on it
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/12 ymaraner <tp...@gmail.com>
> When I said "it does not work" I meant that the MDB is not invoked. The
> error is reproduced in all of the snapshots I used, but not in 1.5.1.
>
> I do not have a simple self-contained project that reproduces the error. If
> you need that, I can try to come up with something. But it will be at lease
> a few hours before I do.
>
> Tim Haley
>
>
> On Tue, Mar 12, 2013 at 4:31 PM, Romain Manni-Bucau [via OpenEJB] <
> ml-node+s979440n4661458h66@n4.nabble.com> wrote:
>
> > hmm, can you reproduce it?
> >
> > *Romain Manni-Bucau*
> > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> > *Blog: **http://rmannibucau.wordpress.com/*<
> > http://rmannibucau.wordpress.com/>
> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> > *Github: https://github.com/rmannibucau*
> >
> >
> >
> > 2013/3/12 ymaraner <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=4661458&i=0>>
> >
> >
> > > Romain Manni-Bucau wrote
> > > > can you give it a try on the 1.6.0-SNAPSHOT to check it is not a
> > > > regression
> > > > but "a merge error" please?
> > >
> > > Unfortunately it does not work in the latest 1.6.0-SNAPSHOT. I also
> > tried
> > > in
> > > 1.6.0-snapshot-19 and 1.5.2-snapshot-59 since I had copies of those,
> and
> > it
> > > does not work on either of them.
> > >
> > > It appears to be a regression that occurred sometime prior to the build
> > on
> > > Feb 4 @ 4:10am. I don't have any snapshots prior to that.
> > >
> > >
> > >
> > >
> > > -----
> > > - Tim
> > > --
> > > View this message in context:
> > >
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661457.html
> > > Sent from the OpenEJB User mailing list archive at Nabble.com.
> > >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661458.html
> > To unsubscribe from MDB activation broken in 1.5.2-SNAPSHOT-80, click
> > here<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4661455&code=dHBoYWxleUBnbWFpbC5jb218NDY2MTQ1NXwxMzE0NDUyOTky
> >
> > .
> > NAML<
> http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> -----
> - Tim
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661459.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by ymaraner <tp...@gmail.com>.
When I said "it does not work" I meant that the MDB is not invoked. The
error is reproduced in all of the snapshots I used, but not in 1.5.1.
I do not have a simple self-contained project that reproduces the error. If
you need that, I can try to come up with something. But it will be at lease
a few hours before I do.
Tim Haley
On Tue, Mar 12, 2013 at 4:31 PM, Romain Manni-Bucau [via OpenEJB] <
ml-node+s979440n4661458h66@n4.nabble.com> wrote:
> hmm, can you reproduce it?
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
> 2013/3/12 ymaraner <[hidden email]<http://user/SendEmail.jtp?type=node&node=4661458&i=0>>
>
>
> > Romain Manni-Bucau wrote
> > > can you give it a try on the 1.6.0-SNAPSHOT to check it is not a
> > > regression
> > > but "a merge error" please?
> >
> > Unfortunately it does not work in the latest 1.6.0-SNAPSHOT. I also
> tried
> > in
> > 1.6.0-snapshot-19 and 1.5.2-snapshot-59 since I had copies of those, and
> it
> > does not work on either of them.
> >
> > It appears to be a regression that occurred sometime prior to the build
> on
> > Feb 4 @ 4:10am. I don't have any snapshots prior to that.
> >
> >
> >
> >
> > -----
> > - Tim
> > --
> > View this message in context:
> >
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661457.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661458.html
> To unsubscribe from MDB activation broken in 1.5.2-SNAPSHOT-80, click
> here<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4661455&code=dHBoYWxleUBnbWFpbC5jb218NDY2MTQ1NXwxMzE0NDUyOTky>
> .
> NAML<http://openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661459.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by Romain Manni-Bucau <rm...@gmail.com>.
hmm, can you reproduce it?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/12 ymaraner <tp...@gmail.com>
> Romain Manni-Bucau wrote
> > can you give it a try on the 1.6.0-SNAPSHOT to check it is not a
> > regression
> > but "a merge error" please?
>
> Unfortunately it does not work in the latest 1.6.0-SNAPSHOT. I also tried
> in
> 1.6.0-snapshot-19 and 1.5.2-snapshot-59 since I had copies of those, and it
> does not work on either of them.
>
> It appears to be a regression that occurred sometime prior to the build on
> Feb 4 @ 4:10am. I don't have any snapshots prior to that.
>
>
>
>
> -----
> - Tim
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661457.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by ymaraner <tp...@gmail.com>.
Romain Manni-Bucau wrote
> can you give it a try on the 1.6.0-SNAPSHOT to check it is not a
> regression
> but "a merge error" please?
Unfortunately it does not work in the latest 1.6.0-SNAPSHOT. I also tried in
1.6.0-snapshot-19 and 1.5.2-snapshot-59 since I had copies of those, and it
does not work on either of them.
It appears to be a regression that occurred sometime prior to the build on
Feb 4 @ 4:10am. I don't have any snapshots prior to that.
-----
- Tim
--
View this message in context: http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455p4661457.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MDB activation broken in 1.5.2-SNAPSHOT-80
Posted by Romain Manni-Bucau <rm...@gmail.com>.
hmm,
can you give it a try on the 1.6.0-SNAPSHOT to check it is not a regression
but "a merge error" please?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/3/12 ymaraner <tp...@gmail.com>
> I have a number of MDBs that were originally developed as EJB2.1 MDBs. They
> were upgraded to 3.x MDBs by modifying the version of the deployment
> descriptor.
>
> When I deploy them to 1.5.1 or an early snapshot of 1.5.2, they are invoked
> when an appropriate message is posted on the JMS Queue.
>
> When I deploy them to 1.5.2-SNAPSHOT-80, they are never invoked and there
> are no errors or warnings produced even though an appropriate message is
> posted on the JMS Queue.
>
> What changed in 1.5.2 that would prevent this from working?
>
> Is there a work-around?
>
> My activation-config looks like this in the ejb-jar.xml file:
>
>
>
>
> -----
> - Tim
> --
> View this message in context:
> http://openejb.979440.n4.nabble.com/MDB-activation-broken-in-1-5-2-SNAPSHOT-80-tp4661455.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.
>