March 2008 - esb-issues - Jboss List Archives

[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

16 years, 9 months

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

16 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1596) Update the version of JBossWS to v 2.0.3.GA

by Tom Fennelly (JIRA)

Update the version of JBossWS to v 2.0.3.GA ------------------------------------------- Key: JBESB-1596 URL: http://jira.jboss.com/jira/browse/JBESB-1596 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP2 The ESB Server and AS deployments depend on v2.0.1.SP2, but there's no download for this. So, anyone wanting to run the ESB on the AS and use the Webservices stuff needs to checkout, build and deploy this tag. This is not a reasonable request on users of 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

16 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1600) Update JBossRemoting dependency and install info in install/readme.txt

by Tom Fennelly (JIRA)

Update JBossRemoting dependency and install info in install/readme.txt ---------------------------------------------------------------------- Key: JBESB-1600 URL: http://jira.jboss.com/jira/browse/JBESB-1600 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP2 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1597) Update JBossWS dependency and install info in install/readme.txt

by Tom Fennelly (JIRA)

Update JBossWS dependency and install info in install/readme.txt ---------------------------------------------------------------- Key: JBESB-1597 URL: http://jira.jboss.com/jira/browse/JBESB-1597 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP2 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1577) Merge all CP1 change over to trunk

by Kevin Conner (JIRA)

Merge all CP1 change over to trunk ---------------------------------- Key: JBESB-1577 URL: http://jira.jboss.com/jira/browse/JBESB-1577 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters, Build and Release, Configuration, Content Based Routing, Deployment, Documentation, Examples, JBI, Management, Message Store, Process flow, Registry and Repository, Rosetta, Security, Testing, Tooling, Transformation Service, Transports, Web Services Affects Versions: 4.2.1 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

16 years, 9 months

1
1
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

16 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1592) Add the ability to turn off soap endpoint rewriting on WSDLs delivered via the WebserviceContractPublisher

by Tom Fennelly (JIRA)

Add the ability to turn off soap endpoint rewriting on WSDLs delivered via the WebserviceContractPublisher ---------------------------------------------------------------------------------------------------------- Key: JBESB-1592 URL: http://jira.jboss.com/jira/browse/JBESB-1592 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP2 You don't always want the rewriting to take place e.g. when a load balancer is managing invocations on a clustered endpoint. In this situation, the JBossWS container is configured to write the soap endpoint as being the address of the load balancer. We should be able to turn off rewriting in this 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

16 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1555) Investigate ServiceInvoker/policy behaviour

by Kevin Conner (JIRA)

Investigate ServiceInvoker/policy behaviour ------------------------------------------- Key: JBESB-1555 URL: http://jira.jboss.com/jira/browse/JBESB-1555 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Fix For: 4.2.1 CP2, 4.3 >From Noel. Using the JBESB 4.2.1.GA.CP1, I'm pretty sure that there's an issue in the load balancing behaviour. I've got a very simple use case with a service deployed into 2 nodes and sending 2 messages only. With a debugger, I can see that the two EPR are used by the ServiceInvoker and that the RoundRobin Policy that I've set is used to choose alternatively each one. However, I can see that the same JMS connection properties are reused (by JMSCourier) instead of having the properties extracted from the second EPR. Is there a way for you to check this ? ------------------------------------------------ I forgot to mention that I'm sending messages to esb services from a standalone JSE java application with the ServiceInvoker. Going further, I can see that the EPR's <wsa:address .../> value is not used to initialise the JMS connection. <ReferenceProperties /> are used instead. This problem happens when the jndi-url is not setup for your esb service (because you want to use the default value defined for your esb node in the jbossesb.sar/jbossesb-properties.xml). Then you have two ways to fix this : - when declaring the EPR, reuse the wsa:address values when nothing is defined for the provider (JMS) - when the service invoker is creating the JMS connection to send the message, use the <wsa:address if <ReferenceProperties is not defined (at least for the JNDI-URL part -- 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, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-1593) Tidy up qa classpaths

by Kevin Conner (JIRA)

Tidy up qa classpaths --------------------- Key: JBESB-1593 URL: http://jira.jboss.com/jira/browse/JBESB-1593 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP2 The CI builds have been failing recently because of classpath issues. The linux build was locking up because of a mismatch between the client remoting classes and the server remoting classes. The test which locked could change, suggesting a race, but the stacktrace was always the same [java] [junit] "main" prio=1 tid=0x08615068 nid=0x4dec runnable [0xbf8b7000..0xbf8b8228] [java] [junit] at java.net.SocketInputStream.socketRead0(Native Method) [java] [junit] at java.net.SocketInputStream.read(SocketInputStream.java:129) [java] [junit] at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) [java] [junit] at java.io.BufferedInputStream.read(BufferedInputStream.java:235) [java] [junit] - locked <0x854f7778> (a java.io.BufferedInputStream) [java] [junit] at java.io.FilterInputStream.read(FilterInputStream.java:66) [java] [junit] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:986) [java] [junit] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:572) [java] [junit] at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:353) [java] [junit] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) [java] [junit] at org.jboss.remoting.Client.invoke(Client.java:1550) [java] [junit] at org.jboss.remoting.Client.addCallbackListener(Client.java:1619) [java] [junit] at org.jboss.remoting.Client.addListener(Client.java:913) [java] [junit] at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:226) [java] [junit] at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:301) [java] [junit] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154) The windows qa tests have not been running because the command line used to start them was too long. The result of this was that windows would fail to fork the junit process from the build. -- 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, 9 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2008