You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Monika Adamczyk (JIRA)" <ji...@apache.org> on 2009/01/14 23:22:59 UTC
[jira] Created: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
ServixMix leaves active endpoint after undeploying service assembly
-------------------------------------------------------------------
Key: SM-1767
URL: https://issues.apache.org/activemq/browse/SM-1767
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.3
Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
Reporter: Monika Adamczyk
Attachments: hello.tar
While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
To make sure the problem is not specific to our project, I have used 2 hello example SA projects
Here are steps required to reproduce the problem
1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
5. start jconsole and connect to ServiceMix
6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
The problem is that when the same SA are redeployed again, ServiceMix throws an error:
javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
The only way I managed to remove the offending endpoint was by restarting service mix.
I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48715#action_48715 ]
Freeman Fang commented on SM-1767:
----------------------------------
Hi Monika,
Thanks for your testcase and detailed description, I can exactly reproduce the problem you saw.
One of the Ode endpoint can't be removed successfully.
I'm not an expert of bpel, I guess the issue comes from your two bpel endpoint refer to same bpel process, this MAY cause problem.
For me this issue is more likely an OdeEngine component issue. Could you please aslo post this problem to apache Ode project?
Thanks
Freeman
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-1767) ServixMix leaves active endpoint
after undeploying service assembly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SM-1767 started by Freeman Fang.
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Monika Adamczyk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48724#action_48724 ]
Monika Adamczyk commented on SM-1767:
-------------------------------------
I have reported the same issue to the ODE team: https://issues.apache.org/jira/browse/ODE-489
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48722#action_48722 ]
Freeman Fang commented on SM-1767:
----------------------------------
Hi,
The error is
javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
the internal endpoint {urn:/HelloWorld2.wsdl}HelloService is ode engine endpoint, it' can't be unregistered.
The http endpoint is external endpoint, and the serviceName for the http endpoint is HelloReceiver. It can be registered and unregistered successfully.
So it's should be ODE engine issue IMO.
Freeman
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SM-1767:
--------------------------------
Assignee: Freeman Fang
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved SM-1767.
------------------------------
Resolution: Won't Fix
Hi Monika,
You can reopen it if it's a real servicemix side issue.
Freeman
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Monika Adamczyk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Monika Adamczyk updated SM-1767:
--------------------------------
Attachment: hello.tar
hello.tar contains two simple hello SA examples used for reproducing problem with unregistered endpoints
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1767) ServixMix leaves active endpoint after
undeploying service assembly
Posted by "Monika Adamczyk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48721#action_48721 ]
Monika Adamczyk commented on SM-1767:
-------------------------------------
I will post the problem to the ODE project as well, but I am not 100% convinced this is ODE issue. Looks more like servicemix-http issue (everything BUT http endpoint gets unregistered).
> ServixMix leaves active endpoint after undeploying service assembly
> -------------------------------------------------------------------
>
> Key: SM-1767
> URL: https://issues.apache.org/activemq/browse/SM-1767
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3
> Environment: Mac OS 10.5, java version "1.6.0_07", ServiceMix 3.3
> Reporter: Monika Adamczyk
> Assignee: Freeman Fang
> Attachments: hello.tar
>
>
> While I was testing configuration for a project I work on (multiple SA with http soap consumer proxy which represent the same abstract WSDL), I have noticed that one of the http endpoints doesn't get unregistered after corresponding SA is undeployed.
> To make sure the problem is not specific to our project, I have used 2 hello example SA projects
> Here are steps required to reproduce the problem
> 1. unzip the hello.tar attached to this issue, you should have two subdirectories: ode-jbi-hello and ode-jbi-hello1.
> 2. cd to ode-jbi-hello, run mvn install and then copy hello-sa/target/hello-sa-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 3. cd to ode-jbi-hello1, run mvn install and then copy hello-sa1/target/hello-sa1-0.0.1-SNAPSHOT.zip to $SERVICEMIX_HOME/hotdeploy directory
> 4. Both SA should deploy without any errors (different urls, endpoints and service names were used to ensure there is no conflict)
> 5. start jconsole and connect to ServiceMix
> 6. expand org.apache.servicemix/ServiceMix/Endpoint - you should see 4 http endpoints (2 internal and 2 external) for HelloWorld2.wsdl
> 7. rm $SERVICEMIX_HOME/hotdeploy/hello-sa-0.0.1-SNAPSHOT.zip, there will be now 3 http endpoints (2 internal, 1 external) for HelloWorld2.wsdl
> 8. rm $SERVICEMIX_HOME/hotdeploy/hello-sa1-0.0.1-SNAPSHOT.zip, there will be now 1 http endpoint (1 internal) for HelloWorld2.wsdl
> ServiceMix log output doesn't report any errors while both SA are undeployed and $SERVICEMIX_HOME/data/smx/service-assemblies/ directory is empty (assuming no other SA were deployed).
> The problem is that when the same SA are redeployed again, ServiceMix throws an error:
> javax.jbi.JBIException: An internal endpoint for service {urn:/HelloWorld2.wsdl}HelloService and endpoint HelloPort is already registered
> The only way I managed to remove the offending endpoint was by restarting service mix.
> I have repeated the same tests with just one hello SA and if I deployed/undeployed the zip file, then redeploying the same SA doesn't generate any errors, nor there are any unregistered endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.