Petals BC JMS

JMS component deployed as an engine instead binding component

Details

  • Type: Bug Bug
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 3.1.1
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    I have deployed a bc jms 3.1.1 and the component appears as an engine instead binding
    component in my jconsole.

    <component type="service-engine"
    component-class-loader-delegation="parent-first">

    The previous type must be changed with "binding-component" value

    Show
    I have deployed a bc jms 3.1.1 and the component appears as an engine instead binding component in my jconsole. <component type="service-engine" component-class-loader-delegation="parent-first"> The previous type must be changed with "binding-component" value
  • Environment:
    bc jms 3.1.1, petals plateform 3.2-SNAPSHOT

People

Dates

  • Created:
    Fri, 10 Dec 2010 - 14:00:28 +0100
    Updated:
    Fri, 10 Dec 2010 - 14:00:28 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.