August 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2784) HttpRouter fire java.lang.NullPointerException if the Response is empty (204)

by Kevin Conner (JIRA)

HttpRouter fire java.lang.NullPointerException if the Response is empty (204) ----------------------------------------------------------------------------- Key: JBESB-2784 URL: https://jira.jboss.org/jira/browse/JBESB-2784 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Environment: Debian Reporter: Jurij Assignee: Daniel Bevenius Fix For: 4.6 [2009-04-16 18:04:53,353][DEBUG][pool-61-thread-2][header]<< "HTTP/1.1 204 No Content [\r][\n]" [2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Content-Length: 000000000000000[\r][\n]" [2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Server: IBM_CICS_Transaction_Server/3.1.0(zOS)[\r][\n]" [2009-04-16 18:04:53,383][DEBUG][pool-61-thread-2][header]<< "Date: Thu, 16 Apr 2009 16:04:53 GMT[\r][\n]" java.lang.NullPointerException at org.jboss.soa.esb.actions.routing.http.HttpRouter.process(HttpRouter.java:118) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-2804) Merge JBESB-2548: HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager

by Tom Fennelly (JIRA)

Merge JBESB-2548: HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager -------------------------------------------------------------------------------------------------------------------- Key: JBESB-2804 URL: https://jira.jboss.org/jira/browse/JBESB-2804 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 HttpClientFactory.createHttpClient creates a HttpConnectionManager instance and configures the "max-total-connections". This is somewhat irrelevant however as the HttpClient still has a default limit of 1 (or 2 - I forget) max connections per connected host, so will never use anything like the configured "max-total-connections". One fix is to also set the "default-max-connections-per-host" on the HostConnectionManager params, with a default value of the value returned from a call to HttpConnectionManager.getParams().getMaxTotalConnections(). I think this would be fine because we only ever have 1 host per httpclient, but you could also provide an override config for situations where we have more. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2803) Merge JBESB-2635: Move HTTP Connection configuration code in HttpClientFactory to a Configurator

by Tom Fennelly (JIRA)

Merge JBESB-2635: Move HTTP Connection configuration code in HttpClientFactory to a Configurator ------------------------------------------------------------------------------------------------ Key: JBESB-2803 URL: https://jira.jboss.org/jira/browse/JBESB-2803 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 HttpClient configuration code for configuring the connection settings was added to HttpClientFactory class. This code should have been added in a Configurator (e.g. "ConnectionConfigurator"). This configurator should be one of the default configurators. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2802) HTTPRouter is 4 times slower than SOAPClient under heavy load

by Martin Vecera (JIRA)

HTTPRouter is 4 times slower than SOAPClient under heavy load ------------------------------------------------------------- Key: JBESB-2802 URL: https://jira.jboss.org/jira/browse/JBESB-2802 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP3 Environment: SOA-P 4.3.CP02 CR2, 3x server with 8 CPU cores, tried both Sun JVM 1.6 x86_64 and OpenJDK 1.6 x86_64, RHEL5 Reporter: Martin Vecera Priority: Critical I have a configureation of 3 servers: 1) a client generating HTTP requests in 100 threads (i.e. simulating 100 clients) 2) SOA-P with a EBWS service that forwards requests to 3rd server using either HTTPRouter or SOAPClient 3) a plain helloworld Web Service When there is just one client, HTTPRouter is definitely faster than SOAPClient. But under the heavy load (100 clients, 500 000 messages, 5kB each), HTTPRouter can process 2.5 messages per thread and SOAPClient can process 10 messages per thread. HTTPRouter - Average 19002264ms, messages 44920 (2.363928845531248 msgs/sec) SOAPClient - Average 17586237ms, messages 187705 (10.673403298272392 msgs/sec) I'm futher investigating the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-2793) Threads in InVMTemporaryTransport are waiting 20% of time

by Martin Vecera (JIRA)

Threads in InVMTemporaryTransport are waiting 20% of time --------------------------------------------------------- Key: JBESB-2793 URL: https://jira.jboss.org/jira/browse/JBESB-2793 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP3 Environment: SOA-P 4.3 CP02 CR2, https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/platform/soa_tag... Reporter: Martin Vecera Priority: Critical Threads are waiting 20% of time in org/jboss/internal/soa/esb/couriers/transport/InVMTemporaryTransport.java when the server is under load on line 802: waitingCondition.await(delay, TimeUnit.MILLISECONDS) ; The service has maxThreads set to 100 and there are 100 clients. <service category="PerformanceTest" name="EBWSProxy" description="Proxy WS using EBWS" invmScope="GLOBAL"> <property name="maxThreads" value="100" /> The issue causes similar (20%) performance degradation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2801) Quickstarts: helloworld_sql_action, helloworld_hibernate_action - NullPointerException thrown during undeployment

by Boris Belovic (JIRA)

Quickstarts: helloworld_sql_action, helloworld_hibernate_action - NullPointerException thrown during undeployment ----------------------------------------------------------------------------------------------------------------- Key: JBESB-2801 URL: https://jira.jboss.org/jira/browse/JBESB-2801 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Boris Belovic Priority: Minor I was testing helloworld_sql_action and helloworld_hibernate_action quickstarts. During undeployment (target ant undeploy) I got NullPointerException in both cases: For helloworld_hibernate_action: [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=HelloworldHibernateDB' from JNDI name 'java:HelloworldHibernateDB' 10:17:55,058 ERROR [STDERR] Exception in thread "HSQLDB Connection @3fe9029b" 10:17:55,059 INFO [HypersonicDatabase] Database remote closed clean 10:17:55,059 ERROR [STDERR] java.lang.NullPointerException 10:17:55,059 ERROR [STDERR] at org.hsqldb.ServerConnection.close(Unknown Source) 10:17:55,059 ERROR [STDERR] at org.hsqldb.ServerConnection.run(Unknown Source) 10:17:55,059 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) 10:17:55,061 INFO [STDOUT] [Server@38d5b111]: Initiating shutdown sequence... 10:17:55,061 INFO [STDOUT] [Server@38d5b111]: Shutdown sequence completed in 0 ms. 10:17:55,062 INFO [STDOUT] [Server@38d5b111]: 2009-08-26 10:17:55.061 SHUTDOWN : System.exit() was not called For helloworld_sql_action: [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=HelloworldSqlDB' from JNDI name 'java:HelloworldSqlDB' 10:25:25,447 INFO [HypersonicDatabase] Database remote closed clean 10:25:25,447 ERROR [STDERR] Exception in thread "HSQLDB Connection @738b19ed" 10:25:25,449 ERROR [STDERR] java.lang.NullPointerException 10:25:25,449 ERROR [STDERR] at org.hsqldb.ServerConnection.close(Unknown Source) 10:25:25,449 ERROR [STDERR] at org.hsqldb.ServerConnection.run(Unknown Source) 10:25:25,449 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) 10:25:25,448 INFO [STDOUT] [Server@4800ef96]: Initiating shutdown sequence... 10:25:25,450 INFO [STDOUT] [Server@4800ef96]: Shutdown sequence completed in 2 ms. 10:25:25,450 INFO [STDOUT] [Server@4800ef96]: 2009-08-26 10:25:25.450 SHUTDOWN : System.exit() was not called -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2799) QS helloworld_tx_sql_action fails on deployment in CP02

by Boris Belovic (JIRA)

QS helloworld_tx_sql_action fails on deployment in CP02 ------------------------------------------------------- Key: JBESB-2799 URL: https://jira.jboss.org/jira/browse/JBESB-2799 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Boris Belovic There are two problems with this quickstart: First problem is that quickstart fails during its deployment (target: ant deploy). See exception stack trace in attached file. Problem is probably in HelloworldTxSqlDBDatabaseInitializer, which is unable to create connection to database. I also noticed that this bug was introduced in CP02 release, in CP01 this quickstart worked correctly. The cause of this bug is probably in jar file used to connect to H2 database (database used in this quickstart) in CP02 . In CP01 is used server/config/lib/h2-1.0.68.jar, but in CP02 is used server/config/lib/h2-1.1.114.jar. When I replaced h2-1.1.114.jar with h2-1.0.68.jar, quickstart worked correctly. Second issue I noticed is in build.xml file for this quickstart. There is a driver.jar property set on line 18. This property is set to h2-1.0.68.jar (in CP02), but this jar file does not exist in CP02, there is a h2-1.1.114.jar instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2796) ServiceComponent not collecting bytes failed correctly

by Tom Cunningham (JIRA)

ServiceComponent not collecting bytes failed correctly ------------------------------------------------------ Key: JBESB-2796 URL: https://jira.jboss.org/jira/browse/JBESB-2796 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP2 ServiceComponent not collecting bytes failed correctly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2656) Upgrade JBpmObjectMapper and ObjectMapper to mvel2

by Kevin Conner (JIRA)

Upgrade JBpmObjectMapper and ObjectMapper to mvel2 -------------------------------------------------- Key: JBESB-2656 URL: https://jira.jboss.org/jira/browse/JBESB-2656 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow, Rosetta Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.7 Look at upgrading this usage to mvel2. Drools is already using 2.0.10 and smooks is about to upgrade. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2795) Management console attribute.jsp shows null values

by Tom Cunningham (JIRA)

Management console attribute.jsp shows null values -------------------------------------------------- Key: JBESB-2795 URL: https://jira.jboss.org/jira/browse/JBESB-2795 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP2 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP2 See screenshots in SOA-1456. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2009