/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p19972648.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
issue, should go a long way to fixing
it...
--kevan
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p19627799.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
a test using my test apps?
--kevan
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p19554557.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
On Sep 18, 2008, at 10:46 AM, jklcom99 wrote:
Kevan,
Do you see anything wrong with the in-place deployment? Is this an
issue
with openejb not setting the classloader?
Jeff,
I'll give in-place deployment a try. Not sure that I can get to it,
today. If you're able to test in-place
have the module.../module in ear deployment plan. It
still got
the wrong classloader after adding module.../module
Can you (did you) run a test using my test apps?
--kevan
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from
=test/ear/1.0/car] right before the message gets sent by
javax.jms.MessageProducer.
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p19514209.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
On Sep 16, 2008, at 11:24 AM, jklcom99 wrote:
Kevan,
I'm in a process of adding all dependencies to appJMS module. I'm
getting
the following error even with
hidden-classes
filterorg.jdom/filter
/hidden-classes
contextClassLoader in MDB,
*** Thread.currentThread().getContextClassLoader() =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=appJMS/1.0/rar]
[java] javax.jms.JMSException: Failed to build body from bytes. Reason:
java.io.IOException
On Sep 16, 2008, at 2:50 PM, jklcom99 wrote:
contextClassLoader in MDB,
*** Thread.currentThread().getContextClassLoader() =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=appJMS/1.0/rar]
[java] javax.jms.JMSException: Failed to build body from bytes.
Reason
() =
[org.apache.geronimo.kernel.classloader.JarFileClassLoader
id=appJMS/1.0/rar]
[java] javax.jms.JMSException: Failed to build body from bytes.
Reason:
java.io.IOException:
Bingo. That's definitely a bad ClassLoader. Now the question is why...
I split apart our jms-mdb example and rigged up
On Sep 17, 2008, at 12:28 AM, jklcom99 wrote:
I don't have the module.../module in ear deployment plan. It
still got
the wrong classloader after adding module.../module
Can you (did you) run a test using my test apps?
--kevan
]
I'd like to know the id of the contextClassLoader when you get the
javax.jms.JMSException: Failed to build body from bytes error.
--kevan
in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p19457555.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
On Sep 10, 2008, at 4:42 PM, jklcom99 wrote:
Kevan,
Is this classloader problem fixed?
Looks like not -- https://issues.apache.org/jira/browse/OPENEJB-889
I'm having a look.
--kevan
-Failed-to-build-body-from-bytes-tp18404327s134p19422719.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
On Jul 16, 2008, at 6:27 PM, jklcom99 wrote:
Kevan,
Your assumption is correct. I've moved the jms connector into my ear
deployment plan as you suggested. JMS is now happy.
I'll see if I can mock up some artifacts for you.
I spoke with David Blevins about this problem. Looks like OpenEJB
into
your ear deployment plan.
--kevan
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p18465908.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
--
View
plan.
--kevan
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p18465908.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p18465908.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes-tp18404327s134p18452308.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Thanks. Is it possible for you to provide a test case that can
illustrate the problem?
Which version of Geronimo were you using previously? If you want to
try a work-around, you could try moving your connector deployment into
your ear deployment plan.
--kevan
:51 AM, jklcom99 wrote:
I've upgraded to G2.1.2 and activemq-core 4.1.2. Now I'm getting the
following JMS exception:
[java] 13:20:00,099 WARN [AppBrokerImpl] javax.jms.JMSException:
Failed
to build body from bytes. Reason: java.io.IOException:
app.entity.QuartzJobI
ssued
[java] 13:20
and
there's a problem deserializing the message bytes into an Object. The
class app.entity.QuartzJobIssued is not being found. Where is that
class packaged?
--kevan
--
View this message in context:
http://www.nabble.com/javax.jms.JMSException%3A-Failed-to-build-body-from-bytes
I've upgraded to G2.1.2 and activemq-core 4.1.2. Now I'm getting the
following JMS exception:
[java] 13:20:00,099 WARN [AppBrokerImpl] javax.jms.JMSException:
Failed
to build body from bytes. Reason: java.io.IOException:
app.entity.QuartzJobI
ssued
[java] 13:20:00,099 ERROR
24 matches
Mail list logo
