NPE in BeanComponent - checkEndOfRequest
----------------------------------------

                 Key: SM-941
                 URL: https://issues.apache.org/activemq/browse/SM-941
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-bean
    Affects Versions: 3.1.1
         Environment: Linus Redhat 4 VmWare
            Reporter: Noseda Anne


ERROR - BeanComponent                  - Error processing exchange InOut[
  id: ID:127.0.0.1-111af5697f3-3:12
  status: Done
  role: provider
  interface: { http://www.etnic.be/janus/fase}receiver
  service: {http://www.etnic.be/janus}Orchestration
  endpoint: endpoint
  operation: { http://www.etnic.be/janus/fase}receiver
  in: <?xml version="1.0" encoding="UTF-8"?><fase:FaseRequete 
xmlns:fase="http://www.etnic.be/janus/fase ">
                        <fase:Organisation>
                                <fase:Type>PO</fase:Type>
                                <fase:Identifiant>10</fase:Identifiant>
                        </fase:Organisation>
                        <fase:Organisation>
                                <fase:Type>ETAB</fase:Type>
                                <fase:Identifiant/>
                        </fase:Organisation>
                        <fase:Dmd>LST_ETAB</fase:Dmd>
                </fase:FaseRequete>
  out: <?xml version="1.0" encoding="UTF-8"?><description xmlns=" 
http://www.etnic.be/janus/fase";>fatal error back-end fase</description>
]
java.lang.NullPointerException
        at org.apache.servicemix.bean.BeanEndpoint.checkEndOfRequest 
(BeanEndpoint.java:390)
        at 
org.apache.servicemix.bean.BeanEndpoint.onProviderExchange(BeanEndpoint.java:258)
        at 
org.apache.servicemix.bean.BeanEndpoint.process(BeanEndpoint.java:201)
        at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess 
(AsyncBaseLifeCycle.java:489)
        at 
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
        at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java 
:46)
        at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
        at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
        at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
        at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
        at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
 (ThreadPoolExecutor.java:665)
        at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
        at java.lang.Thread.run(Thread.java:595)
ERROR - BeanComponent                  - Error setting exchange status to ERROR
javax.jbi.messaging.MessagingException: illegal call to send / sendSync
        at 
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.handleSend(MessageExchangeImpl.java:571)
        at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend 
(DeliveryChannelImpl.java:372)
        at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:419)
        at 
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java 
:58)
        at 
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:595)
        at 
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
        at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
        at 
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
        at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask
 (ThreadPoolExecutor.java:665)
        at 
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
        at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to