July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-701) JMS Queue Notifier does not have configured message properties attached

by Jiri Pechanec (JIRA)

JMS Queue Notifier does not have configured message properties attached ----------------------------------------------------------------------- Key: JBESB-701 URL: http://jira.jboss.com/jira/browse/JBESB-701 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 3 The configuration Notifier with class NotifyQueues can contain a list of elements "queue" and each of these "queue" can contain a list of "messageProp" elements that contains properties to be attached to message. The properties are not attached. The reason is: Constructor NotifyQueues is populated with ConfigTree that has root at the "target" element and has correctly access to the child "queue" elements from which it initilizes but the same ConfigTree is passed to NofityJMS parent class which can't initialize properties as they are stored not on this level but on the level below under each "queue" element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-729) JBossWS Unit tests to verify WS-Addressing support when running with SOAPProcessor Action

by Burr Sutter (JIRA)

JBossWS Unit tests to verify WS-Addressing support when running with SOAPProcessor Action ----------------------------------------------------------------------------------------- Key: JBESB-729 URL: http://jira.jboss.com/jira/browse/JBESB-729 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Refactor JBossWS Unit Tests that confirm support of WS-Addressing when using the ESB between the consumer and the producer via the SOAPProcessor Action -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-731) Verify MTOM support when running with SOAPProcessor Action

by Burr Sutter (JIRA)

Verify MTOM support when running with SOAPProcessor Action ---------------------------------------------------------- Key: JBESB-731 URL: http://jira.jboss.com/jira/browse/JBESB-731 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Refactor JBossWS Unit Tests that confirm support of MTOM when using the ESB between the consumer and the producer via the SOAPProcessor Action -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-602) ESB Server should be able to deploy .ear files

by Tom Cunningham (JIRA)

ESB Server should be able to deploy .ear files ---------------------------------------------- Key: JBESB-602 URL: http://jira.jboss.com/jira/browse/JBESB-602 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Mark Little Tried to deploy my helloworld_hibernate_action .ear file, which contains some jars, a .war, and a .esb to the ESB Server, and I get the following error - I think .ear deployment is broken in the ESB server : 23:48:37,293 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Packages waiting for a deployer --- org.jboss.deployment.DeploymentInfo@b5294d9 { url=file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear altDD: null lastDeployed: 1181015313405 lastModified: 1181015313000 mbeans: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@b5294d9 { url=file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear } deployer: null status: null state: INIT_WAITING_DEPLOYER watch: file:/Users/tcunning/esb/esbserver/server/default/deploy/Quickstart_helloworld_hibernate_action.ear altDD: null lastDeployed: 1181015313405 lastModified: 1181015313000 mbeans: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-721) Failure on redeployment of helloworld_hibernate_action

by Kevin Conner (JIRA)

Failure on redeployment of helloworld_hibernate_action ------------------------------------------------------ Key: JBESB-721 URL: http://jira.jboss.com/jira/browse/JBESB-721 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2 Redeployment of the helloworld_hibernate_action QS causes a null pointer exception in the repository classloader. The reason for this is that a reference to the detached classloader is still being used after undeploy. To reproduce, deploy, undeploy, deploy then view http://localhost:8080/hibernateaction/list.jsp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-739) jboss-esb-console is registering over an existing MBean

by Tom Cunningham (JIRA)

jboss-esb-console is registering over an existing MBean ------------------------------------------------------- Key: JBESB-739 URL: http://jira.jboss.com/jira/browse/JBESB-739 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 15:23:54,290 WARN [ServiceController] Problem starting service jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update javax.jms.JMSException: This destination has already been added to the server! at org.jboss.mq.server.JMSDestinationManager.addDestination(JMSDestinationManager.java:694) at org.jboss.mq.server.jmx.Topic.startService(Topic.java:76) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:613) 15:23:55,533 INFO [JBoss4ESBDeployer] create esb service, soap.esb 15:23:57,246 INFO [JBoss4ESBDeployer] create esb service, spring.esb 15:23:57,276 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update State: FAILED Reason: javax.jms.JMSException: This destination has already been added to the server! I Depend On: jboss.mq:service=DestinationManager Depends On Me: jboss.esb:service=SmooksService jboss.esb:deployment=smooks.esb --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update State: FAILED Reason: javax.jms.JMSException: This destination has already been added to the server! I Depend On: jboss.mq:service=DestinationManager Depends On Me: jboss.esb:service=SmooksService jboss.esb:deployment=smooks.esb -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-673) Document the "jboss-esb" console (and come up with a better name)

by Tom Fennelly (JIRA)

Document the "jboss-esb" console (and come up with a better name) ----------------------------------------------------------------- Key: JBESB-673 URL: http://jira.jboss.com/jira/browse/JBESB-673 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Documentation, Management Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 Milestone Release 3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-669) Add monitoring for Rules and Transformations

by Tom Cunningham (JIRA)

Add monitoring for Rules and Transformations -------------------------------------------- Key: JBESB-669 URL: http://jira.jboss.com/jira/browse/JBESB-669 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 We need counts for both transformations and rules. Splitting this out from JBESB-544 as I'm not sure that it will make it into MR3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-738) Need a web interface that allows distributed monitoring and management

by Tom Cunningham (JIRA)

Need a web interface that allows distributed monitoring and management ---------------------------------------------------------------------- Key: JBESB-738 URL: http://jira.jboss.com/jira/browse/JBESB-738 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 Need a web interface that does remote monitoring and management. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-710) remoting error messages when running bpm_orchestration2 as standalone

by Kevin Conner (JIRA)

remoting error messages when running bpm_orchestration2 as standalone --------------------------------------------------------------------- Key: JBESB-710 URL: http://jira.jboss.com/jira/browse/JBESB-710 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Priority: Minor Fix For: 4.2 The following errors are repeated on the console when run as a standalone ESB. [java] java.net.SocketException: Socket closed [java] at java.net.SocketInputStream.socketRead0(Native Method) [java] at java.net.SocketInputStream.read(SocketInputStream.java:129) [java] at java.net.SocketInputStream.read(SocketInputStream.java:182) [java] at java.io.FilterInputStream.read(FilterInputStream.java:66) [java] at org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(BisocketServerInvoker.java:652) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007