[JBoss JIRA] Created: (JBAS-6409) Upgrade to jboss-server-manager 1.0.1.GA
by Shelly McGowan (JIRA)
Upgrade to jboss-server-manager 1.0.1.GA
----------------------------------------
Key: JBAS-6409
URL: https://jira.jboss.org/jira/browse/JBAS-6409
Project: JBoss Application Server
Issue Type: Thirdparty Change
Security Level: Public (Everyone can see)
Reporter: Shelly McGowan
Assignee: Shelly McGowan
Fix For: JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
Upgrade to latest jboss-server-manager-release. Minor fixes include:
Release Notes - JBoss AS Server Manager - Version 1.0.1.GA
** Bug
* [JBASM-24] - Incorrect default value for Server.partition
* [JBASM-26] - JBoss AS Server Manager fails to deploy applications and even stop the server against JBossAS-5.0 GA
Will also backout the JBASM-24 workaround in testsuite/imports/server-config.xml
--
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, 6 months
[JBoss JIRA] Created: (JBAS-6276) JmsConnectionRequestInfo needs have defaults set before doing allocateConnection()
by Adrian Brock (JIRA)
JmsConnectionRequestInfo needs have defaults set before doing allocateConnection()
----------------------------------------------------------------------------------
Key: JBAS-6276
URL: https://jira.jboss.org/jira/browse/JBAS-6276
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA
Reporter: Adrian Brock
Assignee: Jesper Pedersen
Fix For: JBossAS-5.0.1.CR1, JBossAS-4.2.4.GA
The default values for the JmsConnectionRequestInfo are being setup too late
for the subpooling to work properly.
The call to JmsConnectionRequestInfo.setDefaults(...)
needs to be moved to JmsSessionFactoryImpl::allocateConnection()
something like:
JmsConnectionRequestInfo info = new JmsConnectionRequestInfo(transacted, acknowledgeMode, sessionType);
info.setUserName(userName);
info.setPassword(password);
info.setClientID(clientID);
+ info.setDefaults(mcf.mcfProperties);
This shows up if you try to configure the clientID property on the jms resource adapter, e.g.
<config-property name="ClientID" type="java.lang.String">xxx</config-property>
--
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, 6 months