WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  WebSphere messaging engine not connecting

    Posted Mon April 08, 2013 10:57 AM
    Hi All,

    Please help me.

    I am getting the below error in WAS 7.0 post creating BUS, messaging engines. I am unable to do test connection.

    SystemOut O 2013/04/08 16:15:00:793 | ERROR | WebContainer : 4 | | EventPublisherService | Exception in Eventpublisher
    java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.RemoteException: ; nested exception is:  javax.ejb.EJBException: nested exception is: com.ptp.impact.common.event.EventServiceException: Error in posting message to Event Subscriber JMS queue
    nested exception is-- javax.jms.JMSException- CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0019E: No suitable messaging engine is available on bus  MESSAGE-BUS that matched the specified connection properties {multicastInterface=none, connectionProximity=Bus, targetSignificance=Preferred, subscriptionProtocol=Unicast, targetType=BusMember, busName=MESSAGE-BUS}. Reason for failure: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=MESSAGE-BUS, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..
    at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDelegateImpl.java:235)
    at com.ibm.CORBA.iiop.UtilDelegateImpl.wrapException(UtilDelegateImpl.java:743)
    at javax.rmi.CORBA.Util.wrapException(Util.java:296)
    at com.ptp.impact.ejb.event._EventSession_Stub.publishEvent(_EventSession_Stub.java:562)
    at com.ptp.impact.common.event.EventPublisherService._publish(EventPublisherService.java:302)
    at com.ptp.impact.common.event.EventPublisherService.publish(EventPublisherService.java:211)
    at com.ptp.eclipse.common.util.SessionData.triggerIDRL(SessionData.java:1618)
    at com.ptp.eclipse.common.util.SessionData.cleanUpLoanLevelData(SessionData.java:213)
    at com.ptp.client.common.web.listeners.ClientSessionListener.cleanUpLoanLevelData(ClientSessionListener.java:71)
    at com.ptp.client.common.web.listeners.ClientSessionListener.sessionDestroyed(ClientSessionListener.java:55)
    at com.ibm.ws.session.http.HttpSessionObserver.sessionDestroyed(HttpSessionObserver.java:179)
    at com.ibm.ws.session.SessionEventDispatcher.sessionDestroyed(SessionEventDispatcher.java:160)
    at com.ibm.ws.session.StoreCallback.sessionInvalidated(StoreCallback.java:126)
    at com.ibm.ws.session.store.memory.MemorySession.invalidate(MemorySession.java:224)
    at com.ibm.ws.session.http.HttpSessionImpl.invalidate(HttpSessionImpl.java:303)
    at com.ibm.ws.session.SessionData.invalidate(SessionData.java:246)
    at com.ibm.ws.session.HttpSessionFacade.invalidate(HttpSessionFacade.java:200)
    at com.ptp.eclipse.contact.action.Logout.execute(Logout.java:138)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
    at com.ptp.eclipse.common.servlets.Controller.process(Controller.java:34)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at



    Thanks,


    Chinna.



  • 2.  WebSphere messaging engine not connecting

    Posted Mon April 08, 2013 11:46 AM
    Please post a screenshot of connection factory and available buses
    1. resources --> JMS -->connection factories --> connection factory name
    2. service integration --> buses


  • 3.  WebSphere messaging engine not connecting

    Posted Mon April 08, 2013 12:55 PM
    Hi Chinna,

      If the ME is up and running.  Check this technote:
     
      CWSIT0019E and CWSIT0103E errors: No suitable messaging engine is available errors returned to application even though Messaging Engine is running
      www-01.ibm.com/support/docview.wss?uid=s...
     
      Hope this helps.  Tell us if you need more support.
     
    regards


  • 4.  WebSphere messaging engine not connecting

    Posted Tue April 09, 2013 05:09 AM
    Hi Joseph/Gabriel,

    Connection not estalished.

    Buses>MESSAGE-BUS>Foreign bus connections> MESSAGE-BUS-VSB>Service integration bus links


    Status is showing : Partial CWSIP0905W: No connection established




    Thanks,

    Chinna.


  • 5.  WebSphere messaging engine not connecting

    Posted Tue April 09, 2013 05:44 AM
    Hi chinna,

       CWSIP0905W: No connection established

     The connection between this messaging engine and the foreign bus is not currently available, possibly due to the link not being started or the messaging engine unable to communicate with the messaging engine in the foreign bus


     


      Review:


      Ensure the link is started and the messaging engines that host the link are active and have a working network connection between them.



    Regards


  • 6.  WebSphere messaging engine not connecting

    Posted Tue April 09, 2013 08:45 AM
    as of now ... Iam able to reproduce your issue
    doing further testing ...


  • 7.  WebSphere messaging engine not connecting

    Posted Tue April 09, 2013 09:09 AM
    Chinna,


      The foreing bus connections is between?

    • Bus in the same cell

    • Bus in other cell

    • WebSphere MQ network



      In any case you need to configure links in both servers, that is from your Bus A to the Bus B and from Bus B to Bus A.

      "When configuring a direct service integration bus link, these links must be configured in both directions in order for the two buses to be able to communicate"

      Have you do?

    regards


  • 8.  WebSphere messaging engine not connecting

    Posted Tue April 09, 2013 09:25 AM
    Hi Gabriel/ Joseph,

    I dont have more knowledge on SIB and JMS conncepts.

    Foreing bus connections is between Bus in the another cell.

    Please help me, how can i check and resolve this.


    Thanks,
    Chinna


  • 9.  WebSphere messaging engine not connecting

    Posted Tue April 09, 2013 09:41 AM
    Chinna,

      Have you configure the foreing bus in your cell?