Announcement Announcement Module
Collapse
No announcement yet.
Problems creating EJB with Spring Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems creating EJB with Spring

    Hello,

    I have some problems creating a stateless SessionBean with spring. My code is this:

    public void ejbCreate() throws CreateException {
    System.out.println("ejbCreate");
    super.ejbCreate();
    }
    public void onEjbCreate() throws CreateException {
    System.out.println("onEjbCreate");
    }
    public void setSessionContext(SessionContext arg0)
    throws EJBException {
    try{
    super.setSessionContext(arg0);
    } catch (Exception e) {
    System.out.println(e);
    throw new EJBException(e.getMessage());
    }
    }

    <session >
    <description><![CDATA[]]></description>
    <ejb-name>BookLoanEJB</ejb-name>
    <home>com.geccodummy.ejb.BookLoanEJBHome</home>
    <remote>com.geccodummy.ejb.BookLoanEJBRemote</remote>
    <ejb-class>com.geccodummy.ejb.BookLoanEJB</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Bean</transaction-type>
    <env-entry> <env-entry-name>ejb/BeanFactoryPath</env-entry-name> <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>beanRefFactory.xml</env-entry-value>
    </env-entry>

    </session>
    </enterprise-beans>
    <session >
    <description><![CDATA[]]></description>
    <ejb-name>BookLoanEJB</ejb-name>
    <home>com.geccodummy.ejb.BookLoanEJBHome</home>
    <remote>com.geccodummy.ejb.BookLoanEJBRemote</remote>
    <ejb-class>com.geccodummy.ejb.BookLoanEJB</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Bean</transaction-type>
    <env-entry>
    <env-entry-name>ejb/BeanFactoryPath</env-entry-name>
    <env-entry-type>java.lang.String</env-entry-type>
    <env-entry-value>beanRefFactory.xml</env-entry-value>
    </env-entry>
    </session>
    </enterprise-beans>


    beanRefFactory.xml:
    <bean id="global.spring.ejb.context" class="org.springframework.context.support.ClassPa thXmlApplicationContext"
    lazy-init="true">
    <constructor-arg>
    <list>
    <value>userapplication.xml</value>
    </list>
    </constructor-arg>
    </bean>
    If I call the EJB, I get this exception:

    $ 08:32:12,917 INFO [STDOUT] ejbCreate
    08:32:12,927 INFO [ContextJndiBeanFactoryLocator] BeanFactoryPath from JNDI is [beanRefFactory.xml]
    08:32:13,017 INFO [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [beanRefFactory.xml]
    08:32:13,017 ERROR [LogInterceptor] EJBException in method: public abstract com.geccodummy.ejb.BookLoanEJBRemote com.gec
    codummy.ejb.BookLoanEJBHome.create() throws java.rmi.RemoteException,javax.ejb.CreateException :
    javax.ejb.EJBException: Could not instantiate bean
    at org.jboss.ejb.plugins.AbstractInstancePool.get(Abs tractInstancePool.java:180)
    Changing the code has no effect:

    public void setSessionContext(SessionContext arg0) { setBeanFactoryLocatorKey("global.spring.ejb.contex t");
    setBeanFactoryLocator(ContextSingletonBeanFactoryL ocator.getInstance());
    }

    $ 08:42:55,161 INFO [STDOUT] ejbCreate
    08:42:55,161 ERROR [LogInterceptor] EJBException in method: public abstract com.geccodummy.ejb.BookLoanEJBRemote com.gec
    codummy.ejb.BookLoanEJBHome.create() throws java.rmi.RemoteException,javax.ejb.CreateException :
    javax.ejb.EJBException: Could not instantiate bean
    at org.jboss.ejb.plugins.AbstractInstancePool.get(Abs tractInstancePool.java:180)

    Any idea what the failire is?

    nort

  • #2
    Can you provide the full stacktrace?

    Regards,
    Andreas

    Comment


    • #3
      08:49:55,635 ERROR [LogInterceptor] EJBException in method: public abstract com.geccodummy.ejb.BookLoanEJBRemote com.gec
      codummy.ejb.BookLoanEJBHome.create() throws java.rmi.RemoteException,javax.ejb.CreateException :
      javax.ejb.EJBException: Could not instantiate bean
      at org.jboss.ejb.plugins.AbstractInstancePool.get(Abs tractInstancePool.java:180)
      at org.jboss.ejb.plugins.StatelessSessionInstanceInte rceptor.invokeHome(StatelessSessionInstanceInterce ptor.java
      :78)
      at org.jboss.ejb.plugins.SecurityInterceptor.invokeHo me(SecurityInterceptor.java:116)
      at org.jboss.ejb.plugins.LogInterceptor.invokeHome(Lo gInterceptor.java:121)
      at org.jboss.ejb.plugins.ProxyFactoryFinderIntercepto r.invokeHome(ProxyFactoryFinderInterceptor.java:93 )
      at org.jboss.ejb.SessionContainer.internalInvokeHome( SessionContainer.java:613)
      at org.jboss.ejb.Container.invoke(Container.java:894)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invok e(ReflectedDispatcher.java:141)
      at org.jboss.mx.server.Invocation.dispatch(Invocation .java:80)
      at org.jboss.mx.server.Invocation.invoke(Invocation.j ava:72)
      at org.jboss.mx.server.AbstractMBeanInvoker.invoke(Ab stractMBeanInvoker.java:249)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanSe rverImpl.java:644)
      at org.jboss.invocation.jrmp.server.JRMPInvoker$MBean ServerAction.invoke(JRMPInvoker.java:805)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.invok e(JRMPInvoker.java:406)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at sun.rmi.server.UnicastServerRef.dispatch(UnicastSe rverRef.java:294)
      at sun.rmi.transport.Transport$1.run(Transport.java:1 53)
      at java.security.AccessController.doPrivileged(Native Method)
      at sun.rmi.transport.Transport.serviceCall(Transport. java:149)
      at sun.rmi.transport.tcp.TCPTransport.handleMessages( TCPTransport.java:460)
      at sun.rmi.transport.tcp.TCPTransport$ConnectionHandl er.run(TCPTransport.java:701)
      at java.lang.Thread.run(Thread.java:595)

      Comment


      • #4
        Unfortunately that seems not very meaningful to me, as only internal JBoss methods are mentioned. Are there further interesting informations in the JBoss log concerning your EJB?

        If not, maybe you can post the full code of your EJB class (if not too large) and the relevant part of your ejb-jar.xml file.

        Regards,
        Andreas

        Comment


        • #5
          Hello Andreas,

          unfortunatelly I do not have more stack. But I provide you the source code, it is a simle dummy-try of spring.

          public class BookLoanEJB extends AbstractStatelessSessionBean
          implements BookLoanEJBServiceInterface {

          private static final long serialVersionUID = 1L;
          private BookLoanServiceInterface bookService;

          public BookLoanEJB() {
          super();
          }

          public void ejbActivate() throws EJBException {
          }

          public void ejbPassivate() throws EJBException {
          }

          public void ejbRemove() throws EJBException {
          }

          public void ejbCreate() throws CreateException {
          System.out.println("ejbCreate");
          super.ejbCreate();
          }

          public void onEjbCreate() throws CreateException {
          System.out.println("onEjbCreate");
          try {
          bookService = (BookLoanServiceInterface) getBeanFactory().getBean(
          "bookService");
          } catch (Exception e) {
          System.out.println(e);
          throw new CreateException(e.getMessage());
          }

          }

          public void setSessionContext(SessionContext arg0)
          throws EJBException {
          super.setSessionContext(arg0);
          try{
          setBeanFactoryLocatorKey("global.spring.ejb.contex t");
          setBeanFactoryLocator(ContextSingletonBeanFactoryL ocator.getInstance());
          } catch (Exception e) {
          System.out.println(e);
          throw new EJBException(e.getMessage());
          }
          }

          public String sayHello() {
          System.out.println("sayHello");
          System.out.println("bookService: " + bookService);

          // return bookService.sayHello();
          return "a";
          }

          }

          <enterprise-beans>

          <!-- Session Beans -->
          <session >
          <description><![CDATA[]]></description>
          <ejb-name>BookLoanEJB</ejb-name>
          <home>com.geccodummy.ejb.BookLoanEJBHome</home>
          <remote>com.geccodummy.ejb.BookLoanEJBRemote</remote>
          <ejb-class>com.geccodummy.ejb.BookLoanEJB</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Bean</transaction-type>
          <env-entry>
          <env-entry-name>ejb/BeanFactoryPath</env-entry-name>
          <env-entry-type>java.lang.String</env-entry-type>
          <env-entry-value>beanRefFactory.xml</env-entry-value>
          </env-entry>
          </session>
          </enterprise-beans>
          <bean id="global.spring.ejb.context"
          class="org.springframework.context.support.ClassPa thXmlApplicationContext"
          lazy-init="true">
          <constructor-arg>
          <list>
          <value>userapplication.xml</value>
          </list>
          </constructor-arg>
          </bean>
          I post it also as attachments.

          Thank you.

          Comment


          • #6
            Maybe you should remove the try/catch blocks inside setSessionContext() and onEjbCreate(), just letting exceptions pass through. That way, nested exceptions should appear in the log.
            Besides that, you could get rid of ejbRemove(), ejbCreate(), ejbActivate() and ejbPassivate() methods, as they are implemented in your superclass. One point in using the Spring superclass is to relieve the developer from implementing these methods.

            If you can produce a more detailed log without your exception handling code, please provide that also.

            Regards,
            Andreas

            Comment


            • #7
              okay here we go. I have solved the problem it is running now.

              First I have changed my EJB to a simple EJB implementing this within the business method:

              ApplicationContext appContext =
              new ClassPathXmlApplicationContext(
              "/userapplication.xml");
              System.out.println("appContext: "+appContext);

              BeanFactory bf = (BeanFactory) appContext;
              System.out.println("BeanFactory: "+bf);

              bookService = (BookLoanServiceInterface)
              bf.getBean("bookService");
              So I was able to run my spring service. After this tep I have extended AbstractStatelessSessionBean and used these methods:

              public void onEjbCreate() throws CreateException {
              bookService = (BookLoanServiceInterface)
              getBeanFactory().getBean("bookService");
              }

              public void setSessionContext(SessionContext arg0) {
              super.setSessionContext(arg0);
              setBeanFactoryLocatorKey("global.spring.ejb.contex t");
              setBeanFactoryLocator(
              ContextSingletonBeanFactoryLocator.getInstance());
              }
              First I got the exception that the bean "global.spring.ejb.context" could not be found in the beanRefContext.xml configuration. So I have created this file and stored in my app.jar (in EAR) with the following content:

              <bean id="global.spring.ejb.context"
              class="org.springframework.context.support.ClassPa thXmlApplicationContext"
              lazy-init="true">
              <constructor-arg>
              <list>
              <value>userapplication.xml</value>
              </list>
              </constructor-arg>
              </bean>
              No I wonder why the env-entry in the EJB deployment descriptor has no effect. I have used this content:

              <session >
              <description><![CDATA[]]></description>
              <ejb-name>BookLoanEJB</ejb-name>
              <home>com.geccodummy.ejb.BookLoanEJBHome</home>
              <remote>com.geccodummy.ejb.BookLoanEJBRemote</remote>
              <ejb-class>com.geccodummy.ejb.BookLoanEJB</ejb-class>
              <session-type>Stateless</session-type>
              <transaction-type>Bean</transaction-type>
              <env-entry>
              <env-entry-name>ejb/BeanFactoryPath</env-entry-name>
              <env-entry-type>java.lang.String</env-entry-type>
              <env-entry-value>beanRefReference.xml</env-entry-value>
              </env-entry>
              </session>
              My expectation was that the BeanFactory will search for this file. But instead to search the "beanRefReference.xml" was the "beanRefContext.xml" requested.

              Thank you.

              Comment


              • #8
                Originally posted by nort
                My expectation was that the BeanFactory will search for this file. But instead to search the "beanRefReference.xml" was the "beanRefContext.xml" requested.
                "java:comp/env/ejb/BeanFactoryPath" is the default BeanFactoryLocatorKey. Actually you overrode that key with your own value, also specifying another BeanFactoryLocator. Therefore the entry you provided in your ejb environment entry is not used.

                Have a look at the sources of AbstractEnterpriseBean, if you are curious about the lookup.

                Regards,
                Andreas

                Comment


                • #9
                  I will, thank you Andreas

                  Comment


                  • #10
                    Hi all,
                    I am new in spring, when I try to create an MDB I got the same some issue as well, but i got it at the appserver startup moment.
                    Looks like it try to invoke MessageListener.onMessage(Message msg) method at the startup.

                    Here is error log:

                    2006-05-25 15:44:49,092 DEBUG [org.springframework.beans.factory.xml.XmlBeanDefin itionReader] Using JAXP implementation [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@ 1292d12]
                    2006-05-25 15:44:49,092 INFO [org.springframework.beans.factory.xml.XmlBeanDefin itionReader] Loading XML bean definitions from class path resource [applicationContext.xml]
                    2006-05-25 15:44:49,112 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract void javax.jms.MessageListener.onMessage(javax.jms.Mess age), causedBy:
                    javax.ejb.EJBException: Could not instantiate bean
                    at org.jboss.ejb.plugins.AbstractInstancePool.get(Abs tractInstancePool.java:180)
                    at org.jboss.ejb.plugins.MessageDrivenInstanceInterce ptor.invoke(MessageDrivenInstanceInterceptor.java: 67)
                    at org.jboss.ejb.plugins.CallValidationInterceptor.in voke(CallValidationInterceptor.java:48)
                    at org.jboss.ejb.plugins.AbstractTxInterceptor.invoke Next(AbstractTxInterceptor.java:105)
                    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTran sactions(TxInterceptorCMT.java:335)
                    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxIn terceptorCMT.java:166)
                    at org.jboss.ejb.plugins.RunAsSecurityInterceptor.inv oke(RunAsSecurityInterceptor.java:94)
                    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInt erceptor.java:192)
                    at org.jboss.ejb.plugins.ProxyFactoryFinderIntercepto r.invoke(ProxyFactoryFinderInterceptor.java:122)
                    at org.jboss.ejb.MessageDrivenContainer.internalInvok e(MessageDrivenContainer.java:389)
                    at org.jboss.ejb.Container.invoke(Container.java:873)
                    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invo ke(JMSContainerInvoker.java:1090)
                    at org.jboss.ejb.plugins.jms.JMSContainerInvoker$Mess ageListenerImpl.onMessage(JMSContainerInvoker.java :1392)
                    at org.jboss.jms.asf.StdServerSession.onMessage(StdSe rverSession.java:256)
                    at org.jboss.mq.SpyMessageConsumer.sessionConsumerPro cessMessage(SpyMessageConsumer.java:904)
                    at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMess ageConsumer.java:160)
                    at org.jboss.mq.SpySession.run(SpySession.java:333)
                    at org.jboss.jms.asf.StdServerSession.run(StdServerSe ssion.java:180)
                    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(PooledExecutor.java:743)
                    at java.lang.Thread.run(Thread.java:595)
                    This is my MDB code:

                    public class TestMDBBean extends AbstractJmsMessageDrivenBean {

                    private Logger logger = Logger.getLogger(TestMDBBean.class);

                    protected void onEjbCreate() {
                    // TODO Auto-generated method stub
                    logger.info("%%%===>> It's try to initiate TestMDBBean!");
                    }

                    public void onMessage(Message arg0) {
                    // TODO Auto-generated method stub
                    logger.info("%%%===>> It's try to Send TestMDBBean!");
                    }

                    }
                    and here is my ejb-jar.xml and jboss.xml

                    ======>ejb-jar.xml
                    <ejb-jar>
                    <enterprise-beans>
                    <message-driven>
                    <ejb-name>TestMDBBean</ejb-name>
                    <ejb-class>TestMDBBean</ejb-class>
                    <transaction-type>Container</transaction-type>
                    <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
                    <message-driven-destination>
                    <destination-type>javax.jms.Queue</destination-type>
                    </message-driven-destination>
                    <env-entry>
                    <env-entry-name>ejb/BeanFactoryPath</env-entry-name>
                    <env-entry-type>java.lang.String</env-entry-type>
                    <env-entry-value>applicationContext.xml</env-entry-value>
                    </env-entry>
                    <resource-ref>
                    <res-ref-name>java:/XAConnectionFactory</res-ref-name>
                    <res-type>javax.jms.QueueConnectionFactory</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Unshareable</res-sharing-scope>
                    </resource-ref>
                    </message-driven>
                    </enterprise-beans>
                    </ejb-jar>

                    ======> jboss.xml
                    <jboss>
                    <enterprise-beans>
                    <message-driven>
                    <ejb-name>TestMDBBean</ejb-name>
                    <destination-jndi-name>queue/testQueue</destination-jndi-name>
                    <resource-ref>
                    <res-ref-name>java:/XAConnectionFactory</res-ref-name>
                    <jndi-name>XAConnectionFactory</jndi-name>
                    </resource-ref>
                    </message-driven>
                    </enterprise-beans>
                    </jboss>

                    Comment


                    • #11
                      Have a closer look at the server.log file of your JBoss. The reason why the bean could not be instantiated should be there.

                      Regards,
                      Andreas

                      Comment


                      • #12
                        I have did that at first, and i just did that again when you ask, but still all the exception was at org.jboss.ejb, org.jboss.jms and org.jboss.mq classes, it did not occur on any of my class nor spring's. Here i attach the full error log.

                        Thanks..

                        Comment


                        • #13
                          Maybe try to deploy a vanilla MDB (without Spring) and try to get that running. Afterwards you could extend from AbstractJmsMessageDrivenBean and add the stuff you need. That should reveal if the problem is related to Spring or some other configuration issue with JBoss.

                          Regards,
                          Andreas

                          Comment


                          • #14
                            Hi Andreas,

                            Maybe try to deploy a vanilla MDB (without Spring) and try to get that running. Afterwards you could extend from AbstractJmsMessageDrivenBean and add the stuff you need. That should reveal if the problem is related to Spring or some other configuration issue with JBoss.
                            I just try to use a coventional MDB, without using Spring at all and it runs flawlessly, what I did is try to send a JMS via the login.jsp in the /jsp directory(I create a testing-mdb.ear for that), I attach all the source code into here.

                            Then I retry my Spring version(platform.ear),
                            but this time instead of using the JmsTemplate(AbtractJmsGateway),
                            I switch it to the same logic I used in the Login.jsp, and the same error message occurs

                            One thing i forget to mention is now I got the exception on the attemp to invoke jmsTemplate.convertAndSend(), not on the appserver startup anymore.

                            Another thing worth to mention is when I used my platform.ear (with JsmTemplate) I got this message:

                            2006-05-26 16:57:21,276 INFO [STDOUT] @@@@@ ===> Try to call JMS
                            2006-05-26 16:57:21,276 DEBUG [org.springframework.beans.factory.support.DefaultL istableBeanFactory] Returning cached instance of singleton bean 'jmsEasySender'
                            2006-05-26 16:57:21,276 INFO [STDOUT] ?/?/? Queue is QUEUE.testQueue
                            2006-05-26 16:57:21,276 DEBUG [org.springframework.jms.connection.SingleConnectio nFactory] Created single connection: Connection@7462871[token=ConnectionToken:null/b97ff2c277a0a09f2776891247db0bfc rcvstate=STOPPED]
                            2006-05-26 16:57:21,296 DEBUG [org.springframework.jms.connection.SingleConnectio nFactory] Returning single connection: Connection@7462871[token=ConnectionToken:null/b97ff2c277a0a09f2776891247db0bfc rcvstate=STOPPED]
                            2006-05-26 16:57:21,306 DEBUG [org.springframework.jms.core.JmsTemplate] Executing callback on JMS Session [SpySession@11103930[tx=false ack=AUTO txid=null RUNNING connection=Connection@7462871[token=ConnectionToken:ID:3/b97ff2c277a0a09f2776891247db0bfc rcvstate=STOPPED]]] from connection [Connection@7462871[token=ConnectionToken:ID:3/b97ff2c277a0a09f2776891247db0bfc rcvstate=STOPPED]]
                            2006-05-26 16:57:21,306 DEBUG [org.springframework.jms.core.JmsTemplate]
                            Sending created message [SpyTextMessage {
                            Header {
                            jmsDestination : null
                            jmsDeliveryMode : -1
                            jmsExpiration : 0
                            jmsPriority : -1
                            jmsMessageID : null
                            jmsTimeStamp : 0
                            jmsCorrelationID: null
                            jmsReplyTo : null
                            jmsType : null
                            jmsRedelivered : false
                            jmsProperties : {}
                            jmsPropReadWrite: true
                            msgReadOnly : false
                            producerClientId: ID:3
                            }
                            Body {
                            text :HELLO 123
                            }
                            }]
                            plus this:

                            2006-05-26 16:31:47,040 WARN [org.jboss.ejb.plugins.jms.DLQHandler] Message resent too many times; sending it to DLQ; message id=ID:3-11486863063891
                            The queue is not null when I print to the log, but on the header it displays as jmsDestination : null, and here is what i get when using the testing-mdb.ear:

                            2006-05-26 17:04:03,514 INFO [STDOUT] @@@ routingQueue QUEUE.testQueue
                            2006-05-26 17:04:03,514 INFO [STDOUT] @@@ Send JSM 2
                            2006-05-26 17:04:03,524 INFO [STDOUT] @@@ queueSender : SpyMessageProducer@15701285[ dest=QUEUE.testQueue delivery=persist priority=4 ttl=0 disableMessageID=false disableTS=false session=SpySession@28191855[tx=false ack=AUTO txid=null RUNNING connection=Connection@19458313[token=ConnectionToken:ID:3/74193d44004f149d7bc77a330c1c2214 rcvstate=STOPPED]]]
                            2006-05-26 17:04:03,524 INFO [STDOUT] @@@ Send JSM 3
                            2006-05-26 17:04:03,654 INFO [STDOUT] constructor
                            2006-05-26 17:04:03,654 INFO [STDOUT] set MessageDrivenContext org.jboss.ejb.MessageDrivenEnterpriseContext$Messa geDrivenContextImpl@1c83354
                            2006-05-26 17:04:03,664 INFO [STDOUT] ejb create
                            2006-05-26 17:04:03,694 INFO [STDOUT] onMessage.jmsMessage -->SpyTextMessage {
                            Header {
                            jmsDestination : QUEUE.testQueue
                            jmsDeliveryMode : 2
                            jmsExpiration : 1148690043524
                            jmsPriority : 4
                            jmsMessageID : ID:3-11486882435241
                            jmsTimeStamp : 1148688243524
                            jmsCorrelationID: null
                            jmsReplyTo : null
                            jmsType : null
                            jmsRedelivered : false
                            jmsProperties : {message_pk=123}
                            jmsPropReadWrite: false
                            msgReadOnly : true
                            producerClientId: ID:3
                            }
                            Body {
                            text :Hello 123 World
                            }
                            }
                            Kind Regards,
                            k-yo

                            Comment


                            • #15
                              How is this jmsEasySender bean defined and configured?

                              Regards,
                              Andreas

                              Comment

                              Working...
                              X