December 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1154) Integrate remaining QSes into the Ci system

by Kevin Conner (JIRA)

Integrate remaining QSes into the Ci system ------------------------------------------- Key: JBESB-1154 URL: http://jira.jboss.com/jira/browse/JBESB-1154 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 Some of the QSes are now integrated into the CI system. We need to look at the remaining ones and integrate those as well. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1422) CreateNewProcess does not propagate token/processId

by Jiri Pechanec (JIRA)

CreateNewProcess does not propagate token/processId --------------------------------------------------- Key: JBESB-1422 URL: http://jira.jboss.com/jira/browse/JBESB-1422 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Environment: FC7/PostgreSQL Reporter: Jiri Pechanec When CreateNew Process command is called it does not propagate anywhere processId/tokenId. It means that it is not possible to send signal to created process. -- 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, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-1124) Incorporate Notifier quickstart

by Mark Little (JIRA)

Incorporate Notifier quickstart ------------------------------- Key: JBESB-1124 URL: http://jira.jboss.com/jira/browse/JBESB-1124 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1419) SQLGatewayListener has problems when uses lowercase values in process fields

by Jiri Pechanec (JIRA)

SQLGatewayListener has problems when uses lowercase values in process fields ---------------------------------------------------------------------------- Key: JBESB-1419 URL: http://jira.jboss.com/jira/browse/JBESB-1419 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Environment: FC7/PostgreSQL Reporter: Jiri Pechanec Fix For: 4.2.1 CP1 Contents of the table soaesb1=> select * from gateway_table where upper(status_col) like 'P%'; unique_id | data_column | status_col -----------+------------------+------------ 1 | Hello ESB World! | p 2 | How why ya? | p 3 | Thanks. | p 4 | Cya! | p 5 | Bye ESB World | p Log messages 2007-12-21 07:01:56,925 WARN [org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener] Cannot change row state from Pending to Working. Number of rows in state Pending = 0 -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1267) Some unittests throw non-lethal null pointers

by Kurt Stam (JIRA)

Some unittests throw non-lethal null pointers --------------------------------------------- Key: JBESB-1267 URL: http://jira.jboss.com/jira/browse/JBESB-1267 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Priority: Minor Fix For: 4.2.1 triage Ever since we added the DLS/Redelivery functionality to the ServiceInvoker, some unittests now throw null pointers, when doing a lookup in the registry. The MockRegistry should handle this if correctly configured in the test, but in some cases it is not. -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1392) Unable to use message store after removing application

by Jiri Pechanec (JIRA)

Unable to use message store after removing application ------------------------------------------------------ Key: JBESB-1392 URL: http://jira.jboss.com/jira/browse/JBESB-1392 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Critical If an ESB app writes a message to message store either intentionally or unintentionally, is later undeployed and the message class was soted in ESb file then the message store can't be iterated. The reason is that for iteration only getAllMessages etc methods can be used which throes ClassNotFoundException. There should be methods to iterate only over UUID of message store or this situation must be handled in other way not not prevent message store from use. -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1423) No copyright statements on some files in management console

by Mark Little (JIRA)

No copyright statements on some files in management console ----------------------------------------------------------- Key: JBESB-1423 URL: http://jira.jboss.com/jira/browse/JBESB-1423 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Tom Cunningham Priority: Trivial Fix For: 4.2.1 CP1 -- 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 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1404) Support for JMS authentication

by mwax (JIRA)

Support for JMS authentication ------------------------------ Key: JBESB-1404 URL: http://jira.jboss.com/jira/browse/JBESB-1404 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: mwax ESB currently does not provide explicit support for JMS authentication. In real production systems, authentication is typically manadatory. Potential solutions: In cases where JNDI authentication only is required, adding JNDI properties to the jms-provider definition will work, as in the following example for TIBCO: <jms-provider name="TIBCOJMSProvider" connection-factory="QueueConnectionFactory" jndi-context-factory="com.tibco.tibjms.naming.TibjmsInitialContextFactory" jndi-pkg-prefix="com.tibco.tibjms.naming" jndi-URL="tcp://myhost:7222"> <property name="java.naming.security.principal" value="username"/> <property name="java.naming.security.credentials" value="password"/> ... However, for consistency it might be better to either create new attributes for the jms-provider element, e.g., jndi-security-principal, or to deprecate the jndi attributes and replace them with properties, such as: <jms-provider name="TIBCOJMSProvider" connection-factory="QueueConnectionFactory"> <property name="java.naming.factory.initial" value="com.tibco.tibjms.naming.TibjmsInitialContextFactory"/> <property name="java.naming.provider.url" value="tcp://myhost:7222"/> <property name="java.naming.security.principal" value="username"/> <property name="java.naming.security.credentials" value="password"/> This latter alternative would simplify the code, which currently needs to translate from, e.g., jndi-URL to java.naming.provider.url. In cases where authentication is required to after the JNDI lookup, changes to the code are needed. The following change to the JmsConnectionPool addAnotherSession method works when the JMS username and password are the same as the JNDI principal and credentials: String username = poolKey.get(Context.SECURITY_PRINCIPAL); String password = poolKey.get(Context.SECURITY_CREDENTIALS); if (JMSEpr.QUEUE_TYPE.equals(destinationType)) { QueueConnectionFactory factory = (QueueConnectionFactory) factoryConnection; if (username != null || password != null) { jmsConnection = factory.createQueueConnection(username, password); } else { jmsConnection = factory.createQueueConnection(); } } else { TopicConnectionFactory factory = (TopicConnectionFactory) factoryConnection; if (username != null || password != null) { jmsConnection = factory.createTopicConnection(username, password); } else { jmsConnection = factory.createTopicConnection(); } } This does not work if the JMS username and password are distinct from the JNDI values. I tried simply creating new keys to store the username and password, but this requires additional code changes, as methods such as JmsConnectionPool.getPool only have access to the java.naming.xxx properties of the EPR. -- 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 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-1283) Add transactional context to SQL listener

by Kevin Conner (JIRA)

Add transactional context to SQL listener ----------------------------------------- Key: JBESB-1283 URL: http://jira.jboss.com/jira/browse/JBESB-1283 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 IR2 Reporter: Kevin Conner Assigned To: Kevin Conner 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

18 years, 4 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-1366) Server shutdown timeouts during product CI runs

by Kevin Conner (JIRA)

Server shutdown timeouts during product CI runs ----------------------------------------------- Key: JBESB-1366 URL: http://jira.jboss.com/jira/browse/JBESB-1366 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Jeff and Kurt have both reported errors with the CI build when running on Windows. In both cases the shutdown of the server used for the product tests has taken longer than 2 mins to shutdown, therefore causing the build to fail. -- 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 months

4
18
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2007