[JBoss JIRA] Created: (JBESB-2573) SOAPProcessor Programmer Guide Documentation
by Stelios Koussouris (JIRA)
SOAPProcessor Programmer Guide Documentation
--------------------------------------------
Key: JBESB-2573
URL: https://jira.jboss.org/jira/browse/JBESB-2573
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Stelios Koussouris
Priority: Minor
The example in the following section is meant to refer to SOAPProcessor but it has a different example. Some additional info on the paramters to pass in might also come handy
11.7. Webservices/SOAP
Action Configuration
The <action ... /> configuration for this action is very straightforward. The action requires only one mandatory property value, which is the "jbossws-endpoint" property. This property names the JBossWS endpoint that the SOAPProcessor is exposing (invoking).
<action name="PrintAMessage" class="test.PrintMessage">
<property name="information" value="Hello World!" />
<property name="repeatCount" value="5" />
</action>
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBESB-2548) HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager
by Tom Fennelly (JIRA)
HttpClientFactory not configuring the "default-max-connections-per-host" on the connection manager
--------------------------------------------------------------------------------------------------
Key: JBESB-2548
URL: https://jira.jboss.org/jira/browse/JBESB-2548
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.5
Reporter: 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
16 years, 10 months
[JBoss JIRA] Created: (JBESB-2328) JBossWS getPort not thread safe
by Kevin Conner (JIRA)
JBossWS getPort not thread safe
-------------------------------
Key: JBESB-2328
URL: https://jira.jboss.org/jira/browse/JBESB-2328
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.4 CP2, 4.5
This has been seen on the SOA 4.3 GA release when concurrent access are being made to getPort.
Caused by: java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
at java.util.AbstractList$Itr.next(AbstractList.java:420)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:538)
at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:525)
at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:513)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193)
at javax.xml.ws.Service.getPort(Service.java:116)
I reproduced this by updating the Wise-core.jar and jbossesb-soap.jar to the ESB 4.4CP2 versions and modified the webservice_consumer_wise quickstart to send 20 concurrent messages.
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBESB-2564) Change the default value of ExistsSql
by Kevin Conner (JIRA)
Change the default value of ExistsSql
-------------------------------------
Key: JBESB-2564
URL: https://jira.jboss.org/jira/browse/JBESB-2564
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.4 CP2
Reporter: Taro Yasuma
Fix For: 4.4 CP3
Please change the default value of ExistsSql to gain performance to initialize DatabaseInitializer.
The current jbossesb.esb/jbossesb-service.xml is like:
<server>
<mbean code="org.jboss.internal.soa.esb.dependencies.DatabaseInitializer"
name="jboss.esb:service=MessageStoreDatabaseInitializer">
...
<attribute name="ExistsSql">select * from message</attribute>
...
</mbean>
</server>
But it should be "select count(*) from message".
Should also check for other occurrences.
--
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
16 years, 10 months