February 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1349) ESB test suite hardcoded for hsqldb

by Len DiMaggio (JIRA)

ESB test suite hardcoded for hsqldb ----------------------------------- Key: JBESB-1349 URL: http://jira.jboss.com/jira/browse/JBESB-1349 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 Reporter: Len DiMaggio Assigned To: Kevin Conner ESB Project issue for SOA-150 ESB test suite seems hardcoded to use hsqldb. And I don't see it easily changing few properties and get it running against another database. Let Aleksandar Kostadinov <akostadi(a)redhat.com> know if you need access to databases in the QA Lab. -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1313) There is no way to say, what edge to take, when asynchrously executed esb service fails (service action throws an exception)

by Pavel Kadlec (JIRA)

There is no way to say, what edge to take, when asynchrously executed esb service fails (service action throws an exception) ---------------------------------------------------------------------------------------------------------------------------- Key: JBESB-1313 URL: http://jira.jboss.com/jira/browse/JBESB-1313 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Pavel Kadlec Imagine process graph.... I would like to have two edges going from the service node. One edge would mean that the work was done (service did its work correctly, without problems). The other edge would mean, that service action processing pipeline did not finish its work correctly (some action threw ActionProcessingPipeline exception). Can I model this behaviour? If I take a look at EsbActionHandler.java, it seems to me, that jBPM can not be notified, when esb service throws exception, because message field "FaultTo" is never set. If I call esb service asynchronously, jBPM waits for signalCommand with name of the edge to take. But if esb service fails, esb service does not call signalCommand. ActionProcessingPipeline is terminated, I do not have opportunity to send signalCommand with the name of the fault edge... -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1241) test suite execute against server bound to specified local IP

by Aleksandar Kostadinov (JIRA)

test suite execute against server bound to specified local IP ------------------------------------------------------------- Key: JBESB-1241 URL: http://jira.jboss.com/jira/browse/JBESB-1241 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Mark Little Currently test suite can execute only against server bound to "localhost". It makes sense to be able to execute it against a server running on a selected IP probably an ant property supplied. -- 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

13 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-659) 2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed

by James Williams (JIRA)

2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed ---------------------------------------------------------------------------------------------- Key: JBESB-659 URL: http://jira.jboss.com/jira/browse/JBESB-659 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBossAS 4.2GA, JBossESB - Head as of 07/05.2007. Reporter: James Williams Assigned To: Mark Little I am trying to get 2 JBossAS instances to share the same JMS Server for gateways. There's a lot of moving parts, but I'll try to explain the configurations: 1. JBossAS 4.2.0-GA default config with all .ESB archives, minus the quickstart_helloworld.esb. This server is started using the "-b localhost -c node0" startup parameters. 2. JBossAS 4.2.0-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues. This server is started using the "-b 192.168.200.1 -c node1" startup parameters. 3. JBossAS 4.2-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues that are different from the gateways/listeners in #2. This server is started using the "-b 192.168.200.2 -c node2" startup parameters. I'm not having any problems with nodes #2 and #3 sharing the JMS service that's running on #1, so long as JBossMQ isn't installed on node #2 or #3. If JMS is installed, quickstart_helloworld.esb archive fails to deploy on both #2 or #3. It complains that the Gateway queue does not exist, but it most certainly does. Worse yet, when I run the SendJMSMessage test class, it cannot find the queue either. It's as if jbossesb.sar is somehow screwing up all jndi lookups for the queue. There are a couple things I've done to try to rule out other potential root causes: 1. I tried running #1, #2, #3 w/out any .ESB archives or jbossesb.sar to verify that a JMS client can indeed drop requests into queues on all servers. To me, this validates that 3 unclustered JBossAS instances can each have their own JMS queues that are all accessible on a single machine, like my test environment, just by having the app servers bootstrapped by unique config and ip address. I was worried that the JMS service might be the culprit, but that doesn't appear to be the case. 2. I removed JMS from #2 and #3 to verify that the queues are setup correctly on #1 and to verify that #2 and #3 can indeed share the same JMS service provided they do not have JMS running themselves. -- 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

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-502) Blocking Gateway - in and out.

by Kurt Stam (JIRA)

Blocking Gateway - in and out. ------------------------------ Key: JBESB-502 URL: http://jira.jboss.com/jira/browse/JBESB-502 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 I do think we should make an option for a blocking gateway, where the gateway waits for a a reply from an ESB Service. Basically we set the 'replyTO' on the message and route to a 'replyTO' service which replies back to the gateway. This is another argument for gateways to be in and out. -- 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

13 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1531) Sometimes the message delivery fails for the first time

by Jiri Pechanec (JIRA)

Sometimes the message delivery fails for the first time ------------------------------------------------------- Key: JBESB-1531 URL: http://jira.jboss.com/jira/browse/JBESB-1531 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Environment: standalone-soa-4.2.0.CR2.zip Reporter: Jiri Pechanec Assigned To: Mark Little Attachments: server.log.gz Sometimes it happens that message is sent to GW but it goes to RDLQ because of unresponsive EPR. On the second attempt whel delivery is tried from RDLQ then it succeds. The log says 2008-02-05 11:17:58,037 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Badly formed EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [FirstServiceESB:SimpleListener] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-37377 ]]. java.lang.NullPointerException Why there is NullPointerException thrown in the courrier first time bu not on redelivery? -- 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

13 years, 11 months

4
16
0 / 0

[JBoss JIRA] Created: (JBESB-1537) Examine alternatives to hypersonic

by Kevin Conner (JIRA)

Examine alternatives to hypersonic ---------------------------------- Key: JBESB-1537 URL: http://jira.jboss.com/jira/browse/JBESB-1537 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.3 We are currently using hypersonic for DBs within the ESB project but are now at the point where we need to consider replacing the DB. The new DB should be java based, support embedding and fully support transaction isolation. h2 is being used within jBPM until this issue is resolved. -- 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

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1238) Decrease code duplication in the Quickstarts.

by Kurt Stam (JIRA)

Decrease code duplication in the Quickstarts. ---------------------------------------------- Key: JBESB-1238 URL: http://jira.jboss.com/jira/browse/JBESB-1238 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 IR1 Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 The quickstarts use classes like Send- and ReceiveJMSMessage. These classes are copied across many QSs, and are starting to lead their own life, which makes it hard to maintain them. We should extract these common classes. -- 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

13 years, 11 months

5
12
0 / 0

[JBoss JIRA] Created: (JBESB-807) JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)

by Tom Fennelly (JIRA)

JBossRemotingGateway doesn't support Http BASIC Auth (and probably more) ------------------------------------------------------------------------ Key: JBESB-807 URL: http://jira.jboss.com/jira/browse/JBESB-807 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Talked with Ron Sigal and he thinks we might have to explicitly use the Servlet transport (i.e. the CoyoteInvoker might not be configurable for BASIC auth). Here's what Ron said exactly..... "1. HTTPServerInvoker is obsolete. It's been replaced by CoyoteInvoker. 2. According to my O'Reilly Tomcat book, BASIC authorization is configured in the web.xml file by the <login-config> element. But CoyoteInvoker doesn't use the full Tomcat implementation, just the Coyote adapter. I'm really not sure if the Coyote adapter has anything to do with the web.xml file. 3. There is another Remoting transport, the servlet transport, which really does use Tomcat. It uses a servlet as a front end to the server invoker. There's even a web.xml file: src\etc\web\web.xml in the Remoting project 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

13 years, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default

by Tom Fennelly (JIRA)

Make action, listener etc configuration setting by setter method the default ---------------------------------------------------------------------------- Key: JBESB-476 URL: http://jira.jboss.com/jira/browse/JBESB-476 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 We currently configure everything by constructor. This is not great for a number of reasons: 1. It can't be compile time validated. 2. Not as "obvious" to someone developing against the API. If in an interface, their IDE (or at least compiler - if using a stone ax) will complain immediately that they're not implementing the interface correctly. 3. Makes our code a little bit more complicated re the reflection code that needs to be implemented. So I suggest making the interface (that all these things implement) contain a setter method that takes the config. The mandate on the implementation is that they contain a public default constructor. -- 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

13 years, 11 months

4
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2008