April 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1610) Update AS support to 4.2.2GA

by Kevin Conner (JIRA)

Update AS support to 4.2.2GA ---------------------------- Key: JBESB-1610 URL: http://jira.jboss.com/jira/browse/JBESB-1610 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Kevin Conner Priority: Blocker Fix For: 4.3 We need to move our supported platform to AS 4.2.2GA. -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1598) Provide support for SFTP/FTPS

by Kevin Conner (JIRA)

Provide support for SFTP/FTPS ----------------------------- Key: JBESB-1598 URL: http://jira.jboss.com/jira/browse/JBESB-1598 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner 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

17 years, 12 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-1612) SFTP does not use passive mode option

by Mark Little (JIRA)

SFTP does not use passive mode option ------------------------------------- Key: JBESB-1612 URL: http://jira.jboss.com/jira/browse/JBESB-1612 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transports Affects Versions: 4.2.1 CP1 Reporter: Mark Little Fix For: 4.3 Comment in SecureFtpImpl.java // TODO set connection Mode [PASSIVE|ACTIVE]using m_bPassive ? -- 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, 12 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-1680) Make sure the official Smooks v1.0 jars are in the product before we release

by Tom Fennelly (JIRA)

Make sure the official Smooks v1.0 jars are in the product before we release ---------------------------------------------------------------------------- Key: JBESB-1680 URL: http://jira.jboss.com/jira/browse/JBESB-1680 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Fennelly Assigned To: Daniel Bevenius Priority: Blocker Fix For: 4.2.1 TP-FP1 Just a double check :-) -- 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, 12 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1621) Change size of VARCHAR2 fields in management console (Oracle)

by Tom Cunningham (JIRA)

Change size of VARCHAR2 fields in management console (Oracle) ------------------------------------------------------------- Key: JBESB-1621 URL: http://jira.jboss.com/jira/browse/JBESB-1621 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Change size of VARCHAR2 MBean name fields to 2000 in Oracle to support long names. -- 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, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1605) Management console Hibernate mapping mismatch

by Mika Leino (JIRA)

Management console Hibernate mapping mismatch --------------------------------------------- Key: JBESB-1605 URL: http://jira.jboss.com/jira/browse/JBESB-1605 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Environment: Windows Server 2003 Oracle 9i Reporter: Mika Leino The columns of table JMXOPERATION defined in /console/management-esb/src/main/resources/oracle do not match the Hibernate configuration in /console/management/src/main/resources/oracle/monitoring-mappings.hbm.xml. In the Hibernate mapping the property "operation" is mapped to a nonexistent column "attribute". The value of the column property should be updated to reflect the actual column name. -- 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

18 years

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-1604) JBESB-1476 applies also to other databases

by Mika Leino (JIRA)

JBESB-1476 applies also to other databases ------------------------------------------ Key: JBESB-1604 URL: http://jira.jboss.com/jira/browse/JBESB-1604 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Environment: Windows Server 2003 Oracle 9i Reporter: Mika Leino Issue JBESB-1476 has been marked as closed but the fix is done only to the MySQL script as per the issue description. This issue does how ever affect also other databases and a similar change should be made also to the other database creation scripts. -- 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

18 years

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-1460) jms-jca-provider doesn't read from queues on different node

by Martin Vecera (JIRA)

jms-jca-provider doesn't read from queues on different node ----------------------------------------------------------- Key: JBESB-1460 URL: http://jira.jboss.com/jira/browse/JBESB-1460 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Environment: 2x RHEL5, SOA-P 4.2.0 beta 1, Oracle 10g Reporter: Martin Vecera Priority: Blocker While I was trying ESB load balancing and failover I found out the following issue... Scenario: 1. Two nodes (hostnames: jawa02, jawa04), sharing the same DB, different ServerPeerIDs but no JMS clustering. 2. I generated a message backlog on jawa02 queue/A (10,000 messages). 3. See my simple service configuration: <providers> <jms-jca-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa02:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" transacted="false"> <jms-bus busid="quickstartGwChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/A" /> </jms-bus> </jms-jca-provider> <jms-jca-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa04:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces" transacted="false"> <jms-bus busid="quickstartEsbChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/C" /> </jms-bus> </jms-jca-provider> </providers> <services> <service category="FirstServiceESB" name="SimpleListener" description="Hello World"> <listeners> <jms-listener name="ESB-Gateway" busidref="quickstartGwChannel" maxThreads="4" is-gateway="true" /> <jms-listener name="helloWorld" busidref="quickstartEsbChannel" maxThreads="4" /> </listeners> <actions mep="OneWay"> <action name="notificationAction" class="org.jboss.soa.esb.actions.Notifier"> <property name="okMethod" value="notifyOK" /> <property name="notification-details"> <NotificationList type="OK"> <target class="NotifyConsole" /> </NotificationList> </property> </action> </actions> </service> </services> 4. I deployed the described service to jawa04 and expected it to start processing the messages from jawa02 queue/A but this didn't happen. 5. When I changed the GW provider from jms-jca-provider to jms-provider: <jms-provider name="JBossMessaging" connection-factory="XAConnectionFactory" jndi-URL="jnp://jawa02:1099" jndi-context-factory="org.jnp.interfaces.NamingContextFactory" jndi-pkg-prefix="org.jboss.naming:org.jnp.interfaces"> It worked as expected. Unfortunatelly jms-provider doesn't use ServiceInvoker and thus no load balancing/failover is possible. This makes the ESB failover impossible using JMS. Solution: 1) make jms-jca-provider read the messages from different nodes in the way jms-provider does it. or 2) make jms-provider use ServiceInvoker -- 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

18 years

4
13
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.3 4.2.1 CP3 (was: 4.4) > 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 > Assigned To: Tom Cunningham > 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

18 years

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.4 (was: 4.3) (was: 4.2.1 CP3) > 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 > Assigned To: Tom Cunningham > Fix For: 4.4 > > > 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

18 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2008