Petals Web-Console

Unable to monitore 2 JBI endpoints with the same endpoint name

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.0.4
  • Fix Version/s: 2.0.6
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    We've got 2 different services with the same endpoint name (and different services and interfaces of course). If we want to monitore them, we have to choose from the endpoint name today (unfortunately, we can't choose from the service QName and or the interface QName, even we can monitore on further...). But into the List Box (see the screenshot), if we choose the first or the second endpoint name (they're equals!), it allways choose the second.
    To reproduce, it's simple :put 2 JBI endpoints with the same endpoint name, and try to monitore the 2 together.

    Show
    We've got 2 different services with the same endpoint name (and different services and interfaces of course). If we want to monitore them, we have to choose from the endpoint name today (unfortunately, we can't choose from the service QName and or the interface QName, even we can monitore on further...). But into the List Box (see the screenshot), if we choose the first or the second endpoint name (they're equals!), it allways choose the second. To reproduce, it's simple :put 2 JBI endpoints with the same endpoint name, and try to monitore the 2 together.
  • Environment:
    RHEL 5, esb 3.1.1

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Adrien Ruffie added a comment - Thu, 9 Dec 2010 - 16:33:44 +0100

I was done, now you can selected each endpoint/service couple if you have
same endpoint name but different service name.

Show
Adrien Ruffie added a comment - Thu, 9 Dec 2010 - 16:33:44 +0100 I was done, now you can selected each endpoint/service couple if you have same endpoint name but different service name.
Hide
Permalink
Adrien Ruffie added a comment - Fri, 3 Dec 2010 - 15:43:03 +0100

I have corrected this issue on 2.0.x branche, it's only need to backport over trunk

Show
Adrien Ruffie added a comment - Fri, 3 Dec 2010 - 15:43:03 +0100 I have corrected this issue on 2.0.x branche, it's only need to backport over trunk
Hide
Permalink
Adrien Ruffie added a comment - Thu, 2 Dec 2010 - 09:09:16 +0100

I try your example, thank.

Show
Adrien Ruffie added a comment - Thu, 2 Dec 2010 - 09:09:16 +0100 I try your example, thank.
Hide
Permalink
Frédéric Gardes added a comment - Thu, 2 Dec 2010 - 08:51:13 +0100

Yes, the manual configuration is an easy way to workaround. So it's a minor bug.
Hum, it always is a little bit difficult to provide you the artifacts :there are sa with a lot of su linked to different se's linked to different sl's linked to files under the file system...So it doesn't work easyly into an ubuntu, with different paths...
I'll be able to provide you the kit if you really want. But to reproduce, it's an easier way to:
1-put the bc-soap 4.0.x into the esb 3.1.1
2-put 2 su provide soap with the same endpoint name and different service QName. Like that:

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:jbi="http://java.sun.com/xml/ns/jbi"
	xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
	xmlns:infocustomer="http://orange.com/isv/services/infocustomer/v1"
	xmlns:soap="http://petals.ow2.org/components/soap/version-4">	
	<jbi:services binding-component="true">		
		<!-- Provide a service -->
		<jbi:provides 		
			interface-name="infocustomer:CustomerInfoService"
			service-name="infocustomer:CustomerInfo"
			endpoint-name="CustomerInfoServicePort">
			<!-- CDK specific elements -->
			<petalsCDK:wsdl>infoCustomer-1.0.wsdl</petalsCDK:wsdl>
			<petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>
			<petalsCDK:timeout>30000</petalsCDK:timeout>
			<!-- Component Specific Fields -->
			<soap:soap-version>1.1</soap:soap-version>
			<soap:add-root>false</soap:add-root>
			<soap:chunked-mode>false</soap:chunked-mode>
			<soap:synchronous-timeout>30000</soap:synchronous-timeout>
			<soap:cleanup-transport>true</soap:cleanup-transport>
			<soap:mode>SOAP</soap:mode>
			<soap:modules></soap:modules>
		</jbi:provides>
	</jbi:services>
</jbi:jbi>
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:jbi="http://java.sun.com/xml/ns/jbi"
	xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
	xmlns:petals-su-soap-provides-customerInfo="http://petals.ow2.org/serviceunits/petals-su-soap-provides-customerInfo/version-1.0"
	xmlns:getcustomerinfo="http://getcustomerinfo.services.stv.orange.com"
	xmlns:impl="http://impl.getcustomerinfo.services.isb.orange.com/"
	xmlns:soap="http://petals.ow2.org/components/soap/version-4">	
	<jbi:services binding-component="true">		
		<!-- Provide a service -->
		<jbi:provides 		
			interface-name="getcustomerinfo:CustomerInfoService"
			service-name="impl:CustomerInfo"
			endpoint-name="CustomerInfoServicePort">
			<!-- CDK specific elements -->
			<petalsCDK:wsdl>CustomerInfo.wsdl</petalsCDK:wsdl>
			<petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>
			<petalsCDK:timeout>30000</petalsCDK:timeout>
			<!-- Component Specific Fields -->
			<soap:soap-version>1.1</soap:soap-version>
			<soap:add-root>false</soap:add-root>
			<soap:chunked-mode>false</soap:chunked-mode>
			<soap:synchronous-timeout>30000</soap:synchronous-timeout>
			<soap:cleanup-transport>true</soap:cleanup-transport>
			<soap:mode>SOAP</soap:mode>
			<soap:modules></soap:modules>
		</jbi:provides>
	</jbi:services>
</jbi:jbi>

3-go to the web console and try to activate the monitoring on the 2 JBI endpoints

Show
Frédéric Gardes added a comment - Thu, 2 Dec 2010 - 08:51:13 +0100 Yes, the manual configuration is an easy way to workaround. So it's a minor bug. Hum, it always is a little bit difficult to provide you the artifacts :there are sa with a lot of su linked to different se's linked to different sl's linked to files under the file system...So it doesn't work easyly into an ubuntu, with different paths... I'll be able to provide you the kit if you really want. But to reproduce, it's an easier way to: 1-put the bc-soap 4.0.x into the esb 3.1.1 2-put 2 su provide soap with the same endpoint name and different service QName. Like that: 
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:jbi="http://java.sun.com/xml/ns/jbi"
	xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
	xmlns:infocustomer="http://orange.com/isv/services/infocustomer/v1"
	xmlns:soap="http://petals.ow2.org/components/soap/version-4">	
	<jbi:services binding-component="true">		
		<!-- Provide a service -->
		<jbi:provides 		
			interface-name="infocustomer:CustomerInfoService"
			service-name="infocustomer:CustomerInfo"
			endpoint-name="CustomerInfoServicePort">
			<!-- CDK specific elements -->
			<petalsCDK:wsdl>infoCustomer-1.0.wsdl</petalsCDK:wsdl>
			<petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>
			<petalsCDK:timeout>30000</petalsCDK:timeout>
			<!-- Component Specific Fields -->
			<soap:soap-version>1.1</soap:soap-version>
			<soap:add-root>false</soap:add-root>
			<soap:chunked-mode>false</soap:chunked-mode>
			<soap:synchronous-timeout>30000</soap:synchronous-timeout>
			<soap:cleanup-transport>true</soap:cleanup-transport>
			<soap:mode>SOAP</soap:mode>
			<soap:modules></soap:modules>
		</jbi:provides>
	</jbi:services>
</jbi:jbi>
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0" 
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:jbi="http://java.sun.com/xml/ns/jbi"
	xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
	xmlns:petals-su-soap-provides-customerInfo="http://petals.ow2.org/serviceunits/petals-su-soap-provides-customerInfo/version-1.0"
	xmlns:getcustomerinfo="http://getcustomerinfo.services.stv.orange.com"
	xmlns:impl="http://impl.getcustomerinfo.services.isb.orange.com/"
	xmlns:soap="http://petals.ow2.org/components/soap/version-4">	
	<jbi:services binding-component="true">		
		<!-- Provide a service -->
		<jbi:provides 		
			interface-name="getcustomerinfo:CustomerInfoService"
			service-name="impl:CustomerInfo"
			endpoint-name="CustomerInfoServicePort">
			<!-- CDK specific elements -->
			<petalsCDK:wsdl>CustomerInfo.wsdl</petalsCDK:wsdl>
			<petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>
			<petalsCDK:timeout>30000</petalsCDK:timeout>
			<!-- Component Specific Fields -->
			<soap:soap-version>1.1</soap:soap-version>
			<soap:add-root>false</soap:add-root>
			<soap:chunked-mode>false</soap:chunked-mode>
			<soap:synchronous-timeout>30000</soap:synchronous-timeout>
			<soap:cleanup-transport>true</soap:cleanup-transport>
			<soap:mode>SOAP</soap:mode>
			<soap:modules></soap:modules>
		</jbi:provides>
	</jbi:services>
</jbi:jbi>
3-go to the web console and try to activate the monitoring on the 2 JBI endpoints
Hide
Permalink
Adrien Ruffie added a comment - Wed, 1 Dec 2010 - 17:20:47 +0100

Hello Fred, can you give me your components and SAs deployed on your container ?
You have a palliative solution check the "manually settings" checkbox, that allows
you to provide yourself endpoint/service/interface ... parameters. With this
checkbox I think you can skip the 2 endpoints problem, for the moment ...

Show
Adrien Ruffie added a comment - Wed, 1 Dec 2010 - 17:20:47 +0100 Hello Fred, can you give me your components and SAs deployed on your container ? You have a palliative solution check the "manually settings" checkbox, that allows you to provide yourself endpoint/service/interface ... parameters. With this checkbox I think you can skip the 2 endpoints problem, for the moment ...
Hide
Permalink
Frédéric Gardes added a comment - Wed, 1 Dec 2010 - 15:00:46 +0100

The 2 endpoints into the administration tab, and the list box into the monitoring tab (where we can't choose the 2 together)

Show
Frédéric Gardes added a comment - Wed, 1 Dec 2010 - 15:00:46 +0100 The 2 endpoints into the administration tab, and the list box into the monitoring tab (where we can't choose the 2 together)

People

Dates

  • Created:
    Wed, 1 Dec 2010 - 14:59:52 +0100
    Updated:
    Thu, 9 Dec 2010 - 16:33:44 +0100
    Resolved:
    Thu, 9 Dec 2010 - 16:33:44 +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.