5 Replies Latest reply on Aug 3, 2007 9:23 PM by ldimaggio

    Seeing a new problem with target class=

    ldimaggio

      I started seeing this error today - downloaded from SVN this morning - the recipientList quickstart causes it to happen. As near as I can tell - it worked as of July 27-28.

      Where is this property set/used?


      16:03:04,432 ERROR [NotificationList] Can't instantiate target <target class="NotifyQueues">
       <queue jndiName="queue/qsrecipientlist_regular_Request">
       <messageProp name="quickstart" value="regular_output"/>
       </queue>
       </target>
      java.lang.IllegalArgumentException: The property name 'org.jboss.soa.esb.message.time.dod' is not a valid java identifier.
       at org.jboss.jms.message.JBossMessage.checkProperty(JBossMessage.java:1083)
       at org.jboss.jms.message.JBossMessage.setObjectProperty(JBossMessage.java:912)
       at org.jboss.jms.message.MessageProxy.setObjectProperty(MessageProxy.java:414)
       at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setProperties(DefaultJMSPropertiesSetter.java:96)
       at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setJMSProperties(DefaultJMSPropertiesSetter.java:64)
       at org.jboss.soa.esb.notification.NotifyJMS.setJMSProperties(NotifyJMS.java:225)
       at org.jboss.soa.esb.notification.NotifyJMS.sendNotification(NotifyJMS.java:200)
       at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:164)
       at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:91)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:585)
       at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processSuccess(ActionProcessorMethodInfo.java:154)
       at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(OverriddenActionLifecycleProcessor.java:108)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:574)
       at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:317)
       at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
       at java.lang.Thread.run(Thread.java:595)
      


        • 1. Re: Seeing a new problem with target class=NotifyQueues
          ldimaggio

           

          "ldimaggi@redhat.com" wrote:
          I started seeing this error today - downloaded from SVN this morning - the recipientList quickstart causes it to happen. As near as I can tell - it worked as of July 27-28.

          Where is this property set/used?


          16:03:04,432 ERROR [NotificationList] Can't instantiate target <target class="NotifyQueues">
           <queue jndiName="queue/qsrecipientlist_regular_Request">
           <messageProp name="quickstart" value="regular_output"/>
           </queue>
           </target>
          java.lang.IllegalArgumentException: The property name 'org.jboss.soa.esb.message.time.dod' is not a valid java identifier.
           at org.jboss.jms.message.JBossMessage.checkProperty(JBossMessage.java:1083)
           at org.jboss.jms.message.JBossMessage.setObjectProperty(JBossMessage.java:912)
           at org.jboss.jms.message.MessageProxy.setObjectProperty(MessageProxy.java:414)
           at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setProperties(DefaultJMSPropertiesSetter.java:96)
           at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setJMSProperties(DefaultJMSPropertiesSetter.java:64)
           at org.jboss.soa.esb.notification.NotifyJMS.setJMSProperties(NotifyJMS.java:225)
           at org.jboss.soa.esb.notification.NotifyJMS.sendNotification(NotifyJMS.java:200)
           at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:164)
           at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:91)
           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
           at java.lang.reflect.Method.invoke(Method.java:585)
           at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processSuccess(ActionProcessorMethodInfo.java:154)
           at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.processSuccess(OverriddenActionLifecycleProcessor.java:108)
           at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.notifySuccess(ActionProcessingPipeline.java:574)
           at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:317)
           at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
           at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
           at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
           at java.lang.Thread.run(Thread.java:595)
          


          • 2. Re: Seeing a new problem with target class=
            beve

            Hi,

            this was an error that I introduced when modifying JMS routing and have fixed it a few hours ago.
            Could you update and retry this?

            Sorry about this.

            Thanks,

            /Daniel

            • 3. Re: Seeing a new problem with target class=
              marklittle

              Can you make sure we have an integration test that covers this case? Thanks.

              • 4. Re: Seeing a new problem with target class=
                beve

                I added the test before I fixed the issue (DefaultJMSPropertiesSetterUnitTest.setJMSProperties_with_set_properties_negative)

                /Daniel

                • 5. Re: Seeing a new problem with target class=
                  ldimaggio

                  All set - thanks...