January 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2312) Disable jBPM JobExecutorLauncher and ConfigurationCloser JbpmConfigurationCloser servlets

by Kevin Conner (JIRA)

Disable jBPM JobExecutorLauncher and ConfigurationCloser JbpmConfigurationCloser servlets ----------------------------------------------------------------------------------------- Key: JBESB-2312 URL: https://jira.jboss.org/jira/browse/JBESB-2312 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5 The jsf-console.war references two servlets which control the jBPM resources, these need to be disabled. The resources should be controlled by our MBean and, as the jBPM JobExecutor cannot be invoked multiple times, the following exception is seen on shutdown. java.lang.NullPointerException at org.jbpm.job.executor.JobExecutor.stopAndJoin(JobExecutor.java:84) at org.jboss.soa.esb.services.jbpm.configuration.JbpmService.stopService(JbpmService.java:52) -- 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

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2170) Issues to recheck for TP/FP

by Kevin Conner (JIRA)

Issues to recheck for TP/FP --------------------------- Key: JBESB-2170 URL: https://jira.jboss.org/jira/browse/JBESB-2170 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 TP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.2.1 TP3 If we do another FP release for the SOA platform then we need to check the following modifications made to the CP branch. These modifications originally contained support for InVM (not included in CP) and we would need to merge the appropriate changes into our TP branch. JBESB-2155, JBESB-2160. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2309) A couple of readme files in the quickstarts need these updates.

by Neil Wallace (JIRA)

A couple of readme files in the quickstarts need these updates. --------------------------------------------------------------- Key: JBESB-2309 URL: https://jira.jboss.org/jira/browse/JBESB-2309 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Neil Wallace Priority: Minor Fix For: 4.4 CP2 The two attached diff files are for updates from the linked jira. These are readme files in the conf and webservice_bpel folders. -- 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

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2301) Handle wise threading/pooling

by Kevin Conner (JIRA)

Handle wise threading/pooling ----------------------------- Key: JBESB-2301 URL: https://jira.jboss.org/jira/browse/JBESB-2301 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP2 The current wise codebase (in ESB4.4 and SOA 4.3) is not thread safe and needs some changes made. There are also issues with classloading and clearing of clients. The current WSDynamicClientFactory singleton contains a Map which references the WSDynamicClient instances using a name. This map is current implemented as a HashMap but is accessed concurrently. In addition, the name used as the key is specified within the configuration so there is a possibility of clashes with other deployments, especially as this is used to create temporary files on the filesystem. Instantiation ------------- The factory checks this map to see whether a specified client exists and, if not present, creates one but it does this without synchronizing and can lead to multiple threads clashing during the construction of the same client. In addition the context classloader of the first deployment to create the client will be used to create the classes and this can leak into other deployments. Invocation ---------- The invocation of the service is handled through the jax-ws Port api and this is not thread-safe. The wise codebase shares the same client instance with multiple threads and, therefore, can suffer from concurrency problems. Cleanup ------- The clearCache method on the factory singleton removes *all* clients from the map and is not thread-safe. -- 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

17 years, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-2303) Add support for http.proxyHost configuration

by Magesh Kumar B (JIRA)

Add support for http.proxyHost configuration -------------------------------------------- Key: JBESB-2303 URL: https://jira.jboss.org/jira/browse/JBESB-2303 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.4 Reporter: Magesh Kumar B Running a webservice_consumer using SOAPClient that has a wsdl to an external url and running the same behind a firewall with JVM http.proxyHost and http.proxyPort set does not connect to the external server and results in error: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:310) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:176) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:163) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:381) at java.net.Socket.connect(Socket.java:537) at java.net.Socket.connect(Socket.java:487) at java.net.Socket.<init>(Socket.java:384) at java.net.Socket.<init>(Socket.java:258) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(Unknown Source) at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(Unknown Source) at org.apache.commons.httpclient.HttpConnection.open(Unknown Source) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(Unknown Source) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source) at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source) at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source) at org.jboss.soa.esb.services.soapui.EsbWsdlLoader.load(EsbWsdlLoader.java:65) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:62) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:412) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:403) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.cacheWsdl(WsdlLoader.java:116) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext$Loader.construct(WsdlContext.java:200) at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:45) at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:111) at java.lang.Thread.run(Thread.java:636) This shows that the proxHost is never used when connecting to external wsdl urls. -- 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

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2308) jUDDI does not work with MSSQL

by Kevin Conner (JIRA)

jUDDI does not work with MSSQL ------------------------------ Key: JBESB-2308 URL: https://jira.jboss.org/jira/browse/JBESB-2308 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Registry and Repository Affects Versions: 4.2.1 CP2 Reporter: Martin Vecera Assignee: Kevin Conner Priority: Critical Fix For: 4.4 CP2 Add following configuration files to support MSSQL: deploy/jbossesb.esb/message-store-sql/mssql deploy/jbossesb.sar/juddi-sql/mssql deploy/jbossesb.sar/lib/juddi-2.0rc5.jar/juddi-sql/mssql For juddi we are experimenting with files copied from sybase config. The server is able to start with that. We will know more after running the tests. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1721) Add MSSQL config files

by Martin Vecera (JIRA)

Add MSSQL config files ---------------------- Key: JBESB-1721 URL: http://jira.jboss.com/jira/browse/JBESB-1721 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Registry and Repository Affects Versions: 4.2.1 CP2 Reporter: Martin Vecera Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2.1 CP3 Add following configuration files to support MSSQL: deploy/jbossesb.esb/message-store-sql/mssql deploy/jbossesb.sar/juddi-sql/mssql deploy/jbossesb.sar/lib/juddi-2.0rc5.jar/juddi-sql/mssql For juddi we are experimenting with files copied from sybase config. The server is able to start with that. We will know more after running the tests. -- 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

17 years, 3 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-2229) Add the message-store-sql to support DB2 database

by Jim Ma (JIRA)

Add the message-store-sql to support DB2 database -------------------------------------------------- Key: JBESB-2229 URL: https://jira.jboss.org/jira/browse/JBESB-2229 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP1 Reporter: Jim Ma Fix For: 4.4 CP2 -- 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

17 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-2305) JMSRouter hard codes ConnectionFactory

by Kevin Conner (JIRA)

JMSRouter hard codes ConnectionFactory --------------------------------------- Key: JBESB-2305 URL: https://jira.jboss.org/jira/browse/JBESB-2305 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP2 The JMSRouter includes some hardcoded string which override the JNDI ConnectionFactory configuration. This is a consequence of a bug fix which I merged from the 4.2.1 codebase, and missed this setting. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2307) JBoss4ESBDeployment should handle lifecycle associations in create/destroy

by Kevin Conner (JIRA)

JBoss4ESBDeployment should handle lifecycle associations in create/destroy -------------------------------------------------------------------------- Key: JBESB-2307 URL: https://jira.jboss.org/jira/browse/JBESB-2307 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP2 -- 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

17 years, 3 months

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