Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-37

Unable to successfully RMI call - Unsupported message received with header 0xffffffff

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Critical Critical
    • None
    • 6.1.0.GA
    • EJB, Remoting

      [main] INFO  org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [scheduler.xml]
      [main] INFO  org.springframework.context.support.AbstractApplicationContext - Refreshing org.springframework.context.support.GenericApplicationContext@15e9756: startup date [Fri Nov 01 15:28:47 SGT 2013]; root of context hierarchy
      [main] INFO  org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor - JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
      [main] INFO  org.springframework.beans.factory.support.DefaultListableBeanFactory - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@f6ac0b: defining beans [scheduler,trueProvider,jndiProperties,org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.annotation.internalPersistenceAnnotationProcessor,org.springframework.context.annotation.ConfigurationClassPostProcessor.importAwareProcessor]; root of factory hierarchy
      [main] INFO  org.xnio.Xnio - XNIO Version 3.0.3.GA
      [main] INFO  org.xnio.nio.NioXnio - XNIO NIO Implementation Version 3.0.3.GA
      [main] INFO  org.jboss.remoting3.EndpointImpl - JBoss Remoting version 3.2.3.GA
      [Remoting "JNDI-Endpoint" task-1] INFO  org.jboss.ejb.client.remoting.VersionReceiver - Received server version 1 and marshalling strategies [river]
      [Remoting "JNDI-Endpoint" task-3] WARN  org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver - Unsupported message received with header 0xffffffff
      [main] INFO  org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1381960, receiver=Remoting connection EJB receiver [connection=Remoting connection <64023c>,channel=jboss.ejb,nodename=pc]} on channel Channel ID e9efcdc2 (outbound) of Remoting connection 0198defc to localhost/127.0.0.1:4447
      [main] INFO  org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Initial module availability report for Remoting connection EJB receiver [connection=Remoting connection <64023c>,channel=jboss.ejb,nodename=pc] wasn't received during the receiver context association
      [main] INFO  org.jboss.ejb.client.EJBClient - JBoss EJB Client version 1.0.5.Final
      [Remoting "JNDI-Endpoint" task-4] ERROR org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver - Channel end notification received, closing channel Channel ID 8ac4d6ea (outbound) of Remoting connection 0198defc to localhost/127.0.0.1:4447
      [Remoting "JNDI-Endpoint" task-2] INFO  org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver - Channel Channel ID e9efcdc2 (outbound) of Remoting connection 0198defc to localhost/127.0.0.1:4447 can no longer process messages
      [Remoting "JNDI-Endpoint" task-1] INFO  org.jboss.ejb.client.remoting.VersionReceiver - Received server version 1 and marshalling strategies [river]
      [main] INFO  org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@1474ea, receiver=Remoting connection EJB receiver [connection=Remoting connection <1a80aea>,channel=jboss.ejb,nodename=pc]} on channel Channel ID 8ac59d48 (outbound) of Remoting connection 012922f6 to localhost/127.0.0.1:4447
      [Remoting "JNDI-Endpoint" task-3] WARN  org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver - Unsupported message received with header 0xffffffff
      [main] INFO  org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver - Initial module availability report for Remoting connection EJB receiver [connection=Remoting connection <1a80aea>,channel=jboss.ejb,nodename=pc] wasn't received during the receiver context association
      [Remoting "JNDI-Endpoint" task-4] INFO  org.jboss.ejb.client.remoting.ChannelAssociation$ResponseReceiver - Channel Channel ID 8ac59d48 (outbound) of Remoting connection 012922f6 to localhost/127.0.0.1:4447 can no longer process messages
      [Remoting "JNDI-Endpoint" task-2] ERROR org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1$MessageReceiver - Channel end notification received, closing channel Channel ID a5699d7c (outbound) of Remoting connection 012922f6 to localhost/127.0.0.1:4447
      [Thread-2] INFO  org.springframework.context.support.AbstractApplicationContext - Closing org.springframework.context.support.GenericApplicationContext@15e9756: startup date [Fri Nov 01 15:28:47 SGT 2013]; root of context hierarchy
      [Thread-2] INFO  org.springframework.beans.factory.support.DefaultSingletonBeanRegistry - Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@f6ac0b: defining beans [scheduler,trueProvider,jndiProperties,org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.context.annotation.internalPersistenceAnnotationProcessor,org.springframework.context.annotation.ConfigurationClassPostProcessor.importAwareProcessor]; root of factory hierarchy
      
      	<jee:remote-slsb id="scheduler" 
      	    jndi-name="ejb:run-ball-ear/run-ball-ejb/SchedulerBean!org.quartz.Scheduler"
      		business-interface="org.quartz.Scheduler"
      		environment-ref="jndiProperties"
      		expose-access-context="true"
                      lookup-home-on-startup="false"
                      cache-home="false"
      	>
      	</jee:remote-slsb>
      

      When I make lookup-home-on-startup to false, I will get the above mentioned exception.
      Using jboss-as-7.2.0 Final.

            dlloyd@redhat.com David Lloyd
            junio_jira Junliang Lim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: