April 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Assigned: (JBESB-421) In-VM transport

by Tom Fennelly (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-421?page=all ] Tom Fennelly reassigned JBESB-421: ---------------------------------- Assignee: Tom Fennelly > In-VM transport > --------------- > > Key: JBESB-421 > URL: http://jira.jboss.com/jira/browse/JBESB-421 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Reporter: Mark Little > Assigned To: Tom Fennelly > Priority: Critical > Fix For: 4.2.1 TP-FP1 > > -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Work stopped: (JBESB-421) In-VM transport

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-421?page=all ] Work on JBESB-421 stopped by Mark Little. > In-VM transport > --------------- > > Key: JBESB-421 > URL: http://jira.jboss.com/jira/browse/JBESB-421 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Reporter: Mark Little > Assigned To: Mark Little > Priority: Critical > Fix For: 4.2.1 FP1 > > -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (JBESB-421) In-VM transport

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-421?page=all ] Mark Little reassigned JBESB-421: --------------------------------- Assignee: (was: Mark Little) > In-VM transport > --------------- > > Key: JBESB-421 > URL: http://jira.jboss.com/jira/browse/JBESB-421 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Reporter: Mark Little > Priority: Critical > Fix For: 4.2.1 FP1 > > -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1641) Support millisecond "frequency units" on schedule providers

by Tom Fennelly (JIRA)

Support millisecond "frequency units" on schedule providers ----------------------------------------------------------- Key: JBESB-1641 URL: http://jira.jboss.com/jira/browse/JBESB-1641 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly At the moment, the schedule based providers only support "seconds" based schedule triggers. Should also support milliseconds. This has already been done on the "bramley" branch and is backward compatible i.e. default frequency unit is "seconds". -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1642) Add support for a "PipelineProcessingContext"

by Tom Fennelly (JIRA)

Add support for a "PipelineProcessingContext" --------------------------------------------- Key: JBESB-1642 URL: http://jira.jboss.com/jira/browse/JBESB-1642 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly At present, actions in an action pipeline have no way of interacting/collaborating other than through using the Message as a dumping ground for data that should not be visible outside the Service i.e. the Message is getting used as an execution context. The bramley branch has some code that could be used for this. Look for org.jboss.soa.esb.actions.PipelineProcessingContext. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1491) JMSRouter finalize can throw javax.jms.IllegalStateException: The object is closed

by Daniel Bevenius (JIRA)

JMSRouter finalize can throw javax.jms.IllegalStateException: The object is closed ---------------------------------------------------------------------------------- Key: JBESB-1491 URL: http://jira.jboss.com/jira/browse/JBESB-1491 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.3 This error can occur when undeploying a service that contains a JMSRouter. 2008-01-16 08:54:00,764 ERROR [.pooling.JmsConnectionPool] JMSException while calling getAcknowledgeMode javax.jms.IllegalStateException: The object is closed at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:157) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$getAcknowledgeMode_N7774033054566619384.invokeNext(ClientSessionDelegate$getAcknowledgeMode_N7774033054566619384.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.getAcknowledgeMode(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.getAcknowledgeMode(JBossSession.java:159) at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.closeSession(JmsConnectionPool.java:257) at org.jboss.soa.esb.actions.routing.JMSRouter$JMSSendQueueSetup.close(JMSRouter.java:392) at org.jboss.soa.esb.actions.routing.JMSRouter$JMSSendQueueSetup.access$000(JMSRouter.java:322) at org.jboss.soa.esb.actions.routing.JMSRouter.finalize(JMSRouter.java:300) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160) Make checks to avoid the error. -- 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

16 years, 1 month

1
4
0 / 0

[JBoss JIRA] Updated: (JBESB-1633) MBeanServerLocator.locate always returns the first item in the map instead of a lookup

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-1633?page=all ] Kevin Conner updated JBESB-1633: -------------------------------- Component/s: Web Services > MBeanServerLocator.locate always returns the first item in the map instead of a lookup > -------------------------------------------------------------------------------------- > > Key: JBESB-1633 > URL: http://jira.jboss.com/jira/browse/JBESB-1633 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.2.1, 4.2.1 CP1 > Reporter: Narayanan Raghavan > Fix For: 4.3, 4.2.1 CP3 > > > The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. > Affected archive/ file: > soap.esb > services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java > The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean > mbeanServer = MBeanServerLocator.locate(); > The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use > MBeanServerLocator.locateJboss(); > Thanks! -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-1633) MBeanServerLocator.locate always returns the first item in the map instead of a lookup

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-1633?page=all ] Kevin Conner updated JBESB-1633: -------------------------------- Fix Version/s: 4.2.1 CP3 4.3 Affects Version/s: 4.2.1 CP1 Description: The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. Affected archive/ file: soap.esb services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean mbeanServer = MBeanServerLocator.locate(); The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use MBeanServerLocator.locateJboss(); Thanks! was: The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. Affected archive/ file: soap.esb services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean mbeanServer = MBeanServerLocator.locate(); The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use MBeanServerLocator.locateJboss(); Thanks! This is definitely an ESB issue. A quick search of the codebase shows this to be the only location where locate() is used instead of locateJBoss() > MBeanServerLocator.locate always returns the first item in the map instead of a lookup > -------------------------------------------------------------------------------------- > > Key: JBESB-1633 > URL: http://jira.jboss.com/jira/browse/JBESB-1633 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.2.1, 4.2.1 CP1 > Reporter: Narayanan Raghavan > Fix For: 4.3, 4.2.1 CP3 > > > The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. > Affected archive/ file: > soap.esb > services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java > The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean > mbeanServer = MBeanServerLocator.locate(); > The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use > MBeanServerLocator.locateJboss(); > Thanks! -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-1633) MBeanServerLocator.locate always returns the first item in the map instead of a lookup

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-1633?page=comments#action_12406179 ] Dimitris Andreadis commented on JBESB-1633: ------------------------------------------- This is not a JBoss AS issueI so I've moved it in the ESB project. > MBeanServerLocator.locate always returns the first item in the map instead of a lookup > -------------------------------------------------------------------------------------- > > Key: JBESB-1633 > URL: http://jira.jboss.com/jira/browse/JBESB-1633 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.1 > Reporter: Narayanan Raghavan > > The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. > Affected archive/ file: > soap.esb > services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java > The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean > mbeanServer = MBeanServerLocator.locate(); > The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use > MBeanServerLocator.locateJboss(); > Thanks! -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (JBESB-1633) MBeanServerLocator.locate always returns the first item in the map instead of a lookup

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-1633?page=all ] Dimitris Andreadis moved JBAS-5360 to JBESB-1633: ------------------------------------------------- Project: JBoss ESB (was: JBoss Application Server) Key: JBESB-1633 (was: JBAS-5360) Fix Version/s: (was: JBossAS-4.2.1.GA) Affects Version/s: 4.2.1 (was: JBossAS-4.2.1.GA) > MBeanServerLocator.locate always returns the first item in the map instead of a lookup > -------------------------------------------------------------------------------------- > > Key: JBESB-1633 > URL: http://jira.jboss.com/jira/browse/JBESB-1633 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.1 > Reporter: Narayanan Raghavan > > The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. > Affected archive/ file: > soap.esb > services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java > The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean > mbeanServer = MBeanServerLocator.locate(); > The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use > MBeanServerLocator.locateJboss(); > Thanks! -- 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

16 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2008