11 Replies Latest reply on Dec 10, 2012 12:47 AM by xin.zhang.song

Question about remote lookup the jms connection factory

xin.zhang.song Dec 6, 2012 5:05 AM

Hi All

I met a question during remote lookup the jms connection factory

and my initialContextFactory class is "org.jboss.naming.remote.client.InitialContextFactory"

Here are the error message:

Caused by: java.io.NotSerializableException: org.hornetq.core.client.impl.ClientSessionFactoryImpl
    at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:891)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:585)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1063)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1019)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:998)
    at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:885)
    at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:62)
    at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:119)
    at org.jboss.naming.remote.protocol.v1.Protocol$1$2.write(Protocol.java:138)
    at org.jboss.naming.remote.protocol.v1.WriteUtil.write(WriteUtil.java:61)
    at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:128)
    at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
Caused by: an exception which occurred:
    in field factories
    in field serverLocator
    in object org.hornetq.jms.client.HornetQJMSConnectionFactory@1b5af56

Any idea for this?

Thanks

Xin

1. Re: Question about remote lookup the jms connection factory

jbertram Dec 6, 2012 9:38 AM (in response to xin.zhang.song)

This looks very similiar to AS-4217. Can you read my comment there and see if it matches what you're doing? If not, please elaborate on what version of AS7 you're using and how exactly to reproduce this issue.
1 of 1 people found this helpful
Actions
2. Re: Question about remote lookup the jms connection factory

xin.zhang.song Dec 6, 2012 10:10 PM (in response to jbertram)

Thanks for you fast request!

I will try it follow your comment

Thanks

Xin
Actions
3. Re: Question about remote lookup the jms connection factory

xin.zhang.song Dec 9, 2012 9:58 PM (in response to jbertram)

Hi Justin

Can you told me about how can I get the HornetQ 2.2.18 final?

BTW, Is there a document about how to migrate Hornet to JBoss 7 ?

Thanks

Xin
Actions
4. Re: Question about remote lookup the jms connection factory

jbertram Dec 9, 2012 10:01 PM (in response to xin.zhang.song)

You can pull 2.2.18 and build it from https://github.com/hornetq/hornetq/tags. You might also consider just getting the latest AS7 nightly which has 2.3.0.Beta2.

Also, the problem described in AS-4217 can be solved by not using "java:/RemoteConnectionFactory" from in-container clients (which you shouldn't be doing anyway).
Actions
5. Re: Question about remote lookup the jms connection factory

xin.zhang.song Dec 9, 2012 10:49 PM (in response to jbertram)
I didn't use the java:/RemoteConnectionFactory to lookup the jndi.

Here are my code:

private static final String DEFAULT_CONNECTION_FACTORY = "jms/RemoteConnectionFactory";

also I remove the entry <entry name="RemoteConnectionFactory"/> and it doesn't work,

Ant comment for this?

Thanks

Xin
Actions
6. Re: Question about remote lookup the jms connection factory

jbertram Dec 9, 2012 10:51 PM (in response to xin.zhang.song)

Are you looking up "jms/RemoteConnectionFactory" from a remote, stand-alone client or from a client running within the application server?
Actions
7. Re: Question about remote lookup the jms connection factory

xin.zhang.song Dec 9, 2012 11:57 PM (in response to jbertram)

yes!

I use it both the local client and the remote client.

Thanks

Xin
Actions
8. Re: Question about remote lookup the jms connection factory

jbertram Dec 10, 2012 12:08 AM (in response to xin.zhang.song)

I use it both the local client and the remote client.
Don't do that. That's what my comment I linked previously was all about. Use "java:/ConnectionFactory" or "java:/JmsXA" in your local client. See the messaging subsystem documentation for more information about the connection factories and how each should be used.
1 of 1 people found this helpful
Actions
9. Re: Question about remote lookup the jms connection factory

xin.zhang.song Dec 10, 2012 12:14 AM (in response to jbertram)

Thanks for your advice.

But In our code, it have to use it, because the code of the system was very old. Do you have any advice about it ?

Thanks

Xin
Actions

10. Re: Question about remote lookup the jms connection factory

jbertram Dec 10, 2012 12:26 AM (in response to xin.zhang.song)

This seems strange to me, but if your local client must use "jms/RemoteConnectionFactory" for its JNDI lookup then you can try to reconfigure the connection factories so the client can use the right one. For example:

      <connection-factory name="InVmConnectionFactory">
          <connectors>
              <connector-ref connector-name="in-vm"/>
          </connectors>
          <entries>
              <entry name="java:/ConnectionFactory"/>
              <entry name="jms/RemoteConnectionFactory"/>
          </entries>
      </connection-factory>
      <connection-factory name="RemoteConnectionFactory">
          <connectors>
              <connector-ref connector-name="netty"/>
          </connectors>
          <entries>
              <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
          </entries>
      </connection-factory>

It really makes no sense for a local client to use a "remote" connection factory. I'm not sure why you would have configured it this way to start with.

If you can't get around this with a configuration change then you'll have to upgrade using the links in my previous comment.

11. Re: Question about remote lookup the jms connection factory

xin.zhang.song Dec 10, 2012 12:47 AM (in response to jbertram)

Thanks for your advice.

Thanks

Xin
Actions

Go to original post