September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2059) ServiceMessageCounter bean should aggregate across all listeners associated with a service in the deployment

by Kevin Conner (JIRA)

ServiceMessageCounter bean should aggregate across all listeners associated with a service in the deployment ------------------------------------------------------------------------------------------------------------ Key: JBESB-2059 URL: https://jira.jboss.org/jira/browse/JBESB-2059 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2058) Lifecycle MBean names should be unique

by Kevin Conner (JIRA)

Lifecycle MBean names should be unique -------------------------------------- Key: JBESB-2058 URL: https://jira.jboss.org/jira/browse/JBESB-2058 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 At present these can clash between deployments -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2057) ScheduleListener should include service category/name in config

by Kevin Conner (JIRA)

ScheduleListener should include service category/name in config --------------------------------------------------------------- Key: JBESB-2057 URL: https://jira.jboss.org/jira/browse/JBESB-2057 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-2056) The handling of the wildcard binding is no longer functioning

by Kevin Conner (JIRA)

The handling of the wildcard binding is no longer functioning ------------------------------------------------------------- Key: JBESB-2056 URL: https://jira.jboss.org/jira/browse/JBESB-2056 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The following error is being seen if the binding manager is enabled. java.net.UnknownHostException: ${jboss.esb.bind.address}: ${jboss.esb.bind.address} at java.net.InetAddress.getAllByName0(InetAddress.java:1145) at java.net.InetAddress.getAllByName(InetAddress.java:1072) at java.net.InetAddress.getAllByName(InetAddress.java:1008) at java.net.InetAddress.getByName(InetAddress.java:958) at org.jboss.services.binding.ServiceBinding.setBindAddress(ServiceBinding.java:131) at org.jboss.services.binding.ServiceBinding.<init>(ServiceBinding.java:87) at org.jboss.services.binding.XMLServicesStore.parseBinding(XMLServicesStore.java:220) at org.jboss.services.binding.XMLServicesStore.parseConfig(XMLServicesStore.java:181) at org.jboss.services.binding.XMLServicesStore.parseServer(XMLServicesStore.java:147) at org.jboss.services.binding.XMLServicesStore.load(XMLServicesStore.java:121) at org.jboss.services.binding.ServiceBindingManager.initStore(ServiceBindingManager.java:346) at org.jboss.services.binding.ServiceBindingManager.applyServiceConfig(ServiceBindingManager.java:256) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2042) Add support for encrypted connections in MailInflow Adpater

by Magesh Kumar B (JIRA)

Add support for encrypted connections in MailInflow Adpater ----------------------------------------------------------- Key: JBESB-2042 URL: https://jira.jboss.org/jira/browse/JBESB-2042 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration, Rosetta, Transports Affects Versions: 4.4 Reporter: Magesh Kumar B JBoss 5.0 "Mail Connector" has support for secured connections in mail-ra. We need to allow users to set these additional property/properties that can be configured for Mail-JCA-Gateway egs.,starttls=true/false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2031) Running Destroy operation does not move listener from RUNNING->DESTROYED

by Tom Cunningham (JIRA)

Running Destroy operation does not move listener from RUNNING->DESTROYED ------------------------------------------------------------------------ Key: JBESB-2031 URL: https://jira.jboss.org/jira/browse/JBESB-2031 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Tom Cunningham Assignee: Tom Cunningham Priority: Minor Running the destroy operating on a Listener in the RUNNING state does not work (it doesn't move from RUNNING->STOP->DESTROY). Easy workaround is to run both Stop and Destroy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2034) Seeing ERROR level log mesages for listener state transitions

by Tom Cunningham (JIRA)

Seeing ERROR level log mesages for listener state transitions ------------------------------------------------------------- Key: JBESB-2034 URL: https://jira.jboss.org/jira/browse/JBESB-2034 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: non-project >From Len, via JBMANCON-411 : Testing the embedded console with the SPA-P 4.3 IR4 helloworld quickstart - seeing ERROR level log messages that don't seem to have an operational impact - are these messages just at the wrong logging level? Also - all state transitions generate this type of error: 12:17:04,867 ERROR [OperationInvocation] Plugin error: Operation [start] is defined as returning no results, but it returned non-null results: Configuration[id=0] ------------------------ Test = trying to start a stopped listener. Steps - deploy the quickstart, navigate to this listener: Listener used (hirearchy displayed in console): * : (server name) * : JBossAS Server * : (servername) JBossSOA SOA_4.3.0.GA_IR4 default (1099) * : JBoss ESB Deployment * : Quickstart_helloworld.esb JBoss ESB statistics * : JBoss ESB Services * : SimpleListener JBoss ESB statistics * : JBoss ESB Listeners * : FirstServiceESB Listener Stop the listener, then start it. 12:17:04,264 ERROR [LifecycleController] org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Tasks remain active in executor at org.jboss.soa.esb.listeners.message.MessageAwareListener.checkExecutorTermination(MessageAwareListener.java:403) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doStart(MessageAwareListener.java:225) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.start(AbstractManagedLifecycle.java:169) at org.jboss.soa.esb.listeners.lifecycle.LifecycleController.start(LifecycleController.java:143) at org.jboss.soa.esb.listeners.lifecycle.LifecycleController.invoke(LifecycleController.java:319) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:109) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:424) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:399) at sun.reflect.GeneratedMethodAccessor720.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 12:17:04,867 ERROR [OperationInvocation] Plugin error: Operation [start] is defined as returning no results, but it returned non-null results: Configuration[id=0] Starting a running listener: 12:39:43,386 ERROR [LifecycleController] org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Invalid state change from RUNNING to STARTING at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.changeState(AbstractManagedLifecycle.java:306) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.start(AbstractManagedLifecycle.java:166) at org.jboss.soa.esb.listeners.lifecycle.LifecycleController.start(LifecycleController.java:143) at org.jboss.soa.esb.listeners.lifecycle.LifecycleController.invoke(LifecycleController.java:319) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:109) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:424) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:399) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Initializing a running listener: 12:40:03,839 ERROR [LifecycleController] org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Invalid state change from RUNNING to INITIALISING at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.changeState(AbstractManagedLifecycle.java:306) at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:130) at org.jboss.soa.esb.listeners.lifecycle.LifecycleController.initialise(LifecycleController.java:136) at org.jboss.soa.esb.listeners.lifecycle.LifecycleController.invoke(LifecycleController.java:327) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:109) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:424) at org.rhq.plugins.jmx.MBeanResourceComponent.invokeOperation(MBeanResourceComponent.java:399) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:446) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 12:40:03,840 ERROR [OperationInvocation] Plugin error: Operation [initialise] is defined as returning no results, but it returned non-null results: Configuration[id=0] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2038) Problems with ESB plugin deploying/undeploying/deploying .esb packages

by Tom Cunningham (JIRA)

Problems with ESB plugin deploying/undeploying/deploying .esb packages ----------------------------------------------------------------------- Key: JBESB-2038 URL: https://jira.jboss.org/jira/browse/JBESB-2038 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 >From Burr: If you deploy a jboss-esb.xml/.esb archive with a service called "HelloWorld" and then see that in following areas: http://localhost:8080/web-console http://localhost:8080/jbossesb and JON at http://localhost:7080 then you edit the jboss-esb.xml and redeploy so that service is now called "GoodbyeWorld" then the MBean seems to remember the old name and has the new name. It will appear as if both services are still up and alive when in fact there is only one. 2nd part from Burr: after the AS/SOA-P is restarted then it clears up the jbossesb & web-console but JON still shows the old services as "inactive". the only way to clear that up is to UNINVENTORY the platform (a small button under the platform listing of Browse Resources) and re-import from auto-discovery. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-1983) QS "webservice_consumer_wise*": "readme.txt" files are the same as in "webservice_consumer1"

by Pavel Macik (JIRA)

QS "webservice_consumer_wise*": "readme.txt" files are the same as in "webservice_consumer1" -------------------------------------------------------------------------------------------- Key: JBESB-1983 URL: https://jira.jboss.org/jira/browse/JBESB-1983 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 CP1 Environment: SOA-P 4.3 IR3 Reporter: Pavel Macik There are "readme.txt" files in all "webservice_consumer_wise*" quickstarts: - webservice_consumer_wise - webservice_consumer_wise2 - webservice_consumer_wise3 - webservice_consumer_wise4 that are exactly the same as in "webservice_consumer1" quickstart. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-1981) Unused local variable "greetings" in QS "webservice_consumer_wise2"

by Pavel Macik (JIRA)

Unused local variable "greetings" in QS "webservice_consumer_wise2" ------------------------------------------------------------------- Key: JBESB-1981 URL: https://jira.jboss.org/jira/browse/JBESB-1981 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Environment: JBoss SOA-P 4.3 IR3 Reporter: Pavel Macik QS "webservice_consumer_wise2": There is unused local variable "greetings" in: $(QS)/war/src/org/jboss/soa/esb/samples/quickstart/webservice_consumer_wise2/PingWS.java:37 Either the variable is useless or the webservice method is incomplete. Here is a method source: @WebMethod(operationName = "pingComplexObject", action = "urn:pingComplexObject") @WebResult(name = "ComplexObject") public ComplexObject pingComplexObject( @WebParam(name = "complexObject") ComplexObject arg0) { String greeting = "Ping with " + arg0.toString(); return arg0; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 7 months

4
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2008