January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1170) Unregister an EPR during bootstrapper shutdown does not work

by Burr Sutter (JIRA)

Unregister an EPR during bootstrapper shutdown does not work ------------------------------------------------------------ Key: JBESB-1170 URL: http://jira.jboss.com/jira/browse/JBESB-1170 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 IR1 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2.1 Steps to reproduce: - Using the quickstart helloworld: ant run, 3 windows, 3 times - Review the number of EPRs for this service in your registry. You might use a UDDI GUI tool and you will see all 3 instances - Shutdown the bootstrapper via Ctrl-C, you'll see the Stopping JBossESB... message - however, those EPRs were not removed from UDDI -- 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 month

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-454) Allow no inputSuffix on the FileGateway

by Kurt Stam (JIRA)

Allow no inputSuffix on the FileGateway --------------------------------------- Key: JBESB-454 URL: http://jira.jboss.com/jira/browse/JBESB-454 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Make the suffix on input Files optional so that it simply picks up all the files in the directory. Check to see that in this case the output directory is not the same as the input directory. -- 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 month

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1344) Not all gateways are using ServiceInvoker

by Jiri Pechanec (JIRA)

Not all gateways are using ServiceInvoker ----------------------------------------- Key: JBESB-1344 URL: http://jira.jboss.com/jira/browse/JBESB-1344 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Critical Few gateways do not use Service Invoker. It means that they do not provide load balancing facility right now. This needs to be documented and fixed later. The guilty gateways are JmsGatewayListener.java HibernateInterceptor.java SqlTableGatewayListener.java -- 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 month

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1110) Need a two-servers-on-one-machine quickstart

by Tom Cunningham (JIRA)

Need a two-servers-on-one-machine quickstart -------------------------------------------- Key: JBESB-1110 URL: http://jira.jboss.com/jira/browse/JBESB-1110 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Tom Cunningham We need a quickstart that involves sending messages from one ESB on a single machine to another. Such a quickstart would demonstrate the servicebindings capabilities and other issues with running multiple ESB's on the same machine. -- 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 month

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1329) Collections (unbounded xs:elements) can't be first element in xs:sequence

by Per-Anders Backstrom (JIRA)

Collections (unbounded xs:elements) can't be first element in xs:sequence ------------------------------------------------------------------------- Key: JBESB-1329 URL: http://jira.jboss.com/jira/browse/JBESB-1329 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Environment: JBoss 4.2.GA Reporter: Per-Anders Backstrom Collections can't be the first element in a xs:sequence or else the OGNL-mapping will fail. I have narrowed the bug down to the org.jboss.internal.soa.esb.soap.OGNLUtils class and the getOGNLExpression() method. The bug is easily reproduced, in the soapui-client test-cases, in file orderprocessing/OrderProcessingSchema.xsd, just see to that the element name "lineItems" gets positioned first in complexType named "order". Btw, collections are asserted in OGNLUtils.java by checking for the first occurrence of a comment-string containing "1 or more repetitions" at the parent node of the actual element, but as far as I can see my collections are always commented with "Zero or more repetitions". If the first comment is rather "Optional", e.g the collection isn't first element in the parent node, this assertion would probably fail anyway? -- 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 month

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1072) JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger

by Mark Little (JIRA)

JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger ------------------------------------------------------------------------------------------- Key: JBESB-1072 URL: http://jira.jboss.com/jira/browse/JBESB-1072 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Minor 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1475) 'Table not found' errors when using management console with MySQL on Linux

by Bernard Tison (JIRA)

'Table not found' errors when using management console with MySQL on Linux -------------------------------------------------------------------------- Key: JBESB-1475 URL: http://jira.jboss.com/jira/browse/JBESB-1475 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Environment: OS: Fedora 8 RDBMS: MySQL v5.0.45 Reporter: Bernard Tison When deploying the management console (management.esb) on the ESB, using MySQl as RDBMS (OS = Linux), 'Table not found' errors appear. Reason: the org.jboss.soa.esb.monitoring.server.StaticsHelper and org.jboss.soa.esb.monitoring.server.OperationsHelper classes use native SQL queries, in which the table names are referred in proper case. The Hibernate mapping files use upper case for the table names. Mysql on Linux is case sensitive. Attached are versions of the two classes where the table names in the native SQL queries use upper case. -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1417) bpm_orchestration1 needs to be updated

by Jiri Pechanec (JIRA)

bpm_orchestration1 needs to be updated -------------------------------------- Key: JBESB-1417 URL: http://jira.jboss.com/jira/browse/JBESB-1417 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec See warnings in log 2007-12-20 14:31:20,131 INFO [STDOUT] 1********** Begin Service 1 *********** 2007-12-20 14:31:20,196 INFO [STDOUT] In: Start It Up 2007-12-20 14:31:20,196 INFO [STDOUT] Out: Service 1 Start It Up 2007-12-20 14:31:20,196 INFO [STDOUT] ************ End Service 1 ************ 2007-12-20 14:31:20,406 INFO [org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 2007-12-20 14:31:20,644 INFO [STDOUT] 2********** Begin Service 2 *********** 2007-12-20 14:31:20,644 INFO [STDOUT] In: Service 1 Start It Up 2007-12-20 14:31:20,645 INFO [STDOUT] Out: Service 2 Service 1 Start It Up 2007-12-20 14:31:20,645 INFO [STDOUT] ************ End Service 2 ************ 2007-12-20 14:31:20,789 INFO [org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 2007-12-20 14:31:21,020 INFO [STDOUT] 3********** Begin Service 3 *********** 2007-12-20 14:31:21,028 INFO [STDOUT] In: Service 2 Service 1 Start It Up 2007-12-20 14:31:21,028 INFO [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up 2007-12-20 14:31:21,029 INFO [STDOUT] ************ End Service 3 ************ 2007-12-20 14:31:21,184 INFO [STDOUT] Executed by the process, not by the 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

18 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (JBESB-768) Quickstart that demos JMS custom_correlation

by Daniel Bevenius (JIRA)

Quickstart that demos JMS custom_correlation -------------------------------------------- Key: JBESB-768 URL: http://jira.jboss.com/jira/browse/JBESB-768 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Optional Burr suggested that we add a quickstart that demos a custom correlation using jms. An example could be an application that creates a custom correlation id which it sets on the JMSMessage before posting to the ESB. It then needs to wait for a response and use a selector for that that specific correlation id. This would call for them to create a custom JMSRouter/JMSNotifier. -- 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, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1492) "JMSException: Failed to route Reference" during failover

by Martin Vecera (JIRA)

"JMSException: Failed to route Reference" during failover --------------------------------------------------------- Key: JBESB-1492 URL: http://jira.jboss.com/jira/browse/JBESB-1492 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Environment: SOA-P 4.2.1.beta1, Oracle DB Reporter: Martin Vecera First see atached archive for all the referenced files. Problem: I deployed the same service to two nodes in JMS cluster (see scen1_supported.png). Then I started to generate messages to the queue quickstart_helloworld_Request_gw. I tried several times to undeploy and deploy again the service on both nodes (not at both nodes at the same time). It isn't so easy to reproduce this issue when I start with clean DB and fresh server instances. But once the error appeared you can reach it 100%. The node where the service is currently undeployed shows the errors (see below and node1.log) unfinitely (for more then 1 minute). The second node stops processing the messages during the errors. Once the service is deployed again on the first node the normal processing continues. 2008-01-16 14:24:56,028 ERROR [org.jboss.messaging.util.ExceptionUtil] SessionEndpoint[yeg-zagowhbf-1-45evvhbf-5vn4jb-a4wya] send [c3j-c4sowhbf-1-45evvhbf-5vn4jb-a4wya] javax.jms.JMSException: Failed to route Reference[62704]:RELIABLE to quickstart_helloworld_Request_esb at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:743) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:383) at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java) at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157) at sun.reflect.GeneratedMethodAccessor143.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java) at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java) at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:795) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) I also tried scen1_unsupported.png configuration with the same result. I was not able to reach this problem when all the queues were deployed independently on the server. For instructions on how to switch ESB to use Oracle DB see dbinstall.howto.txt. To be able to deploy the Performance1 service you need to deploy test-result-service.sar first. -- 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, 2 months

7
21
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008