Hide Forgot
project_key: SOA This won't be fixed in CP03 most probably - no impact on our tests. To sum it up: Hiya Martin. Martin Vecera wrote: > > Jarek has realized the following changes in service names between 4.2.CP02 and > > 4.2.CP03. Could you have a look on it please? Is that anything expected? It > > doesn't seem to influence our tests so far... These are the management beans so I am unsure how they will affect your tests. > > On Wednesday 03 of December 2008 16:54:51 Jaroslaw Kijanowski wrote: >> >> Hey Martin, >> >> I've ran the management console and noticed that some services changed >> >> their names. >> >> >> >> Renamed services are: >> >> jboss.esb:category=MessageCounter,deployment=jbossesb.esb >> >> -> >> >> jboss.esb:category=MessageCounter,deployment=jbossesb.esb,service-name=Rede >> >> liverService https://jira.jboss.org/jira/browse/JBESB-2164 >> >> jboss.esb:listener-name=redeliver-scheduled-listener >> >> -> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=RedeliverService, >> >> listener-name=listener https://jira.jboss.org/jira/browse/JBESB-2164 https://jira.jboss.org/jira/browse/JBESB-2150 although it suffers from JBESB-2058 The rest are https://jira.jboss.org/jira/browse/JBESB-2150 and also suffer from JBESB-2058. They have swapped one level of non-unique naming for another but I think we should consider fixing this if a respin is required. Kev > On Wednesday 03 of December 2008 16:54:51 Jaroslaw Kijanowski wrote: >> Hey Martin, >> I've ran the management console and noticed that some services changed >> their names. >> >> Renamed services are: >> jboss.esb:category=MessageCounter,deployment=jbossesb.esb >> -> >> jboss.esb:category=MessageCounter,deployment=jbossesb.esb,service-name=Rede >> liverService >> >> >> jboss.esb:listener-name=redeliver-scheduled-listener >> -> >> jboss.esb:service-category=JBossESB-Internal,service-name=RedeliverService, >> listener-name=listener >> >> >> ++++++++++++++++++++++++++++++++++++++++++ >> Renamed listener names: >> >> jboss.esb:service-category=JBossESB-Internal,service-name=DataCollectorServ >> ice,listener-name=JMS-DCQListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=DataCollectorServ >> ice,listener-name=listener >> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=DataFilerService, >> listener-name=JMS-DFListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=DataFilerService, >> listener-name=listener >> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=DeadLetterService >> ,listener-name=JMS-DLQListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=DeadLetterService >> ,listener-name=listener >> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=InvokerFilerServi >> ce,listener-name=JMS-DFListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=InvokerFilerServi >> ce,listener-name=listener >> >> jboss.esb:service-category=JBossESB-Internal,service-name=InvokerService,li >> stener-name=JMS-DCQListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=InvokerService,li >> stener-name=listener >> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=JBpmCallbackServi >> ce,listener-name=JMS-DCQListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=JBpmCallbackServi >> ce,listener-name=listener >> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=OperationsCollect >> orService,listener-name=JMS-DCQListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=OperationsCollect >> orService,listener-name=listener >> >> >> jboss.esb:service-category=JBossESB-Internal,service-name=OperationsFilerSe >> rvice,listener-name=JMS-DFListener -> >> jboss.esb:service-category=JBossESB-Internal,service-name=OperationsFilerSe >> rvice,listener-name=listener
Link: Added: This issue depends JBESB-2244