March 2008 - esb-issues - Jboss List Archives

[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

16 years, 8 months

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

16 years, 8 months

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

16 years, 8 months

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-1585) Merge https (jbr server and HttpRouter) code from the "tfennelly_https" workspace

by Tom Fennelly (JIRA)

Merge https (jbr server and HttpRouter) code from the "tfennelly_https" workspace --------------------------------------------------------------------------------- Key: JBESB-1585 URL: http://jira.jboss.com/jira/browse/JBESB-1585 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Fix For: 4.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

16 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1584) Add support for millisecond schedules

by Tom Fennelly (JIRA)

Add support for millisecond schedules ------------------------------------- Key: JBESB-1584 URL: http://jira.jboss.com/jira/browse/JBESB-1584 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Fix For: 4.3 Current 4.2.x codebase only supports second based time units. Code for this is on the bramley branch. -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1589) Unify Notifier property substitution with ObjectMapper

by Kevin Conner (JIRA)

Unify Notifier property substitution with ObjectMapper ------------------------------------------------------ Key: JBESB-1589 URL: http://jira.jboss.com/jira/browse/JBESB-1589 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1, 4.2.1 Reporter: Kevin Conner Fix For: 4.2.1 FP1, 4.3 The FTP notifier contains a mechanism for handling property substitution but it is different from the ObjectMapper. This should be unified with ObjectMapper and then applied to the other notifier targets as appropriate.. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1391) NTLMConfigurator

by Faisal Azizullah (JIRA)

NTLMConfigurator ---------------- Key: JBESB-1391 URL: http://jira.jboss.com/jira/browse/JBESB-1391 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: JBOSS ESB 4.2.1 GA Reporter: Faisal Azizullah Fix For: 4.2.1 package org.jboss.soa.esb.http.configurators; /* * *@ author: Faisal Azizullah *@ company : Lewisville ISD * */ import org.apache.commons.httpclient.HttpClient; import org.apache.commons.httpclient.Credentials; import org.apache.commons.httpclient.NTCredentials; import org.apache.commons.httpclient.auth.AuthScope; import org.jboss.soa.esb.ConfigurationException; import org.jboss.soa.esb.http.Configurator; import java.util.Properties; /** * HTTP NTLM Authentication Configurator. * * Properties: * <ul> * <li>username: See {@link NTCredentials}. (Required)</li> * <li>password: See {@link NTCredentials}. (Required)</li> * <li>authscope-host: See {@link AuthScope}. (Required)</li> * <li>authscope-port: See {@link AuthScope}. (Required)</li> * <li>authscope-domain: See {@link AuthScope}. (Required)</li> * <li>authscope-realm: See {@link AuthScope}. (Optional)</li> * </ul> * * See <a href="http://jakarta.apache.org/commons/httpclient/authentication.html">HttpClient Authentication Guide</a>. * * */ public class AuthNTLM extends Configurator { public void configure(HttpClient httpClient, Properties properties) throws ConfigurationException { String username = properties.getProperty("ntauth-username"); String password = properties.getProperty("ntauth-password"); String authScopeHost = properties.getProperty("ntauthscope-host"); String authScopePort = properties.getProperty("ntauthscope-port"); String authScopeRealm = properties.getProperty("ntauthscope-realm"); String authScopeDomain = properties.getProperty("ntauthscope-domain"); assertPropertySetAndNotBlank(username, "ntauth-username"); assertPropertySetAndNotBlank(password, "ntauth-password"); assertPropertySetAndNotBlank(authScopeHost, "ntauthscope-host"); assertPropertyIsInteger(authScopePort, "ntauthscope-port"); assertPropertySetAndNotBlank(authScopeDomain, "ntauthscope-domain"); Credentials creds = new NTCredentials(username, password,authScopeHost,authScopeDomain); AuthScope authScope; if(authScopeRealm != null && !authScopeRealm.trim().equals("")) { authScope = new AuthScope(authScopeHost, Integer.parseInt(authScopePort), authScopeRealm); } else { authScope = new AuthScope(authScopeHost, Integer.parseInt(authScopePort)); } httpClient.getState().setCredentials(authScope, creds); } } -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1412) Ability to send message payload as an attachment

by Kenneth Larsen (JIRA)

Ability to send message payload as an attachment ------------------------------------------------ Key: JBESB-1412 URL: http://jira.jboss.com/jira/browse/JBESB-1412 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kenneth Larsen Attachments: NotifyEmailPatch.patch It would be nice to have the option of sending the message payload as an attachment when using the EMailNotifier instead of always having to include the message payload into the mail body. In some cases the payload might be binary content which is inappropriate in the mail body. By specifying an additional attribute for the target the payload should be attached to the mail: <target class="NotifyEmail" from="sender(a)domain.com" sendTo="recipient(a)anotherdomain.com" subject="subject for message" msgAttachmentName="attachmentname.ext"> In the example above a new attribute has been introduced (msgAttachmentName). If specified the payload is created as an attachment with the specified filename instead of being part of the mail body. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1623) NotifySqlTable.java generates SQL with syntax error for NotifySqlTable

by Len DiMaggio (JIRA)

NotifySqlTable.java generates SQL with syntax error for NotifySqlTable ---------------------------------------------------------------------- Key: JBESB-1623 URL: http://jira.jboss.com/jira/browse/JBESB-1623 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP1 Environment: revision 19254 Reporter: Len DiMaggio JBESB_4_2_1_SOA_4_2/product/rosetta/src/org/jboss/soa/esb/notification/NotifySqlTable.java At revision 19254. [ldimaggi@ldimaggi notification]$ diff NotifySqlTable.java.new NotifySqlTable.java 66a67 > 126,127c127 < sbCol.append(sIn).append(sCurrCol); < --- > sbCol.append(sIn).append("\"").append(sCurrCol).append("\""); Without this change, this type of Exception is raised: 15:58:55,176 ERROR [NotifySqlTable] SqlException while trying to notify table. Insert statement : insert into notifications ("Column2","Column1","MessageContents") values ('2','1','Hello from ESB-unaware JMS Client') The column names cannot be enclosed in "" (verified this with both MySQL and PostgreSQL). ===================== Notifiers used - from SOA-P notifications QuickStart: MySQL    <target class="NotifySqlTable" driver-class="com.mysql.jdbc.Driver" connection-url="jdbc:mysql://localhost:3306/notifytest" user-name="soaesb1" password="soaesb1" table="notifications" dataColumn="MessageContents"> <column name="Column1" value="1"/> <column name="Column2" value="2"/> </target> PostgreSQL    <target class="NotifySqlTable" driver-class="org.postgresql.Driver" connection-url="jdbc:postgresql:testdb" user-name="soap_user" password="soap_user" table="notifications" dataColumn="MessageContents"> <column name="Column1" value="1"/> <column name="Column2" value="2"/> </target> -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1350) Action for invoking SLSB methods

by Dominik Kunz (JIRA)

Action for invoking SLSB methods -------------------------------- Key: JBESB-1350 URL: http://jira.jboss.com/jira/browse/JBESB-1350 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Dominik Kunz Attachments: EJBProcessor.java Action for invoking SLSB methods using the reflection API. Configurable through jboss-esb.xml. -- 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, 8 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008