[JBoss JIRA] (AS7-6079) EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)
by Tiago Frazão (JIRA)
[ https://issues.jboss.org/browse/AS7-6079?page=com.atlassian.jira.plugin.s... ]
Tiago Frazão edited comment on AS7-6079 at 1/29/13 7:20 AM:
-------------------------------------------------------------
//---
was (Author: tiagoff):
Hi Guys,
I do still have the issue ... and i had to change a little bit the Jboss code to overcome the problem.
When we define the configurations (sync-on-commin-only, insert-after-ejb-post-create, call-ejb-store-on-clean) in "jbosscmp-jdbc.xml" like bellow :
<jbosscmp-jdbc>
<defaults>
<datasource>java:jboss/datasources/XptoDS</datasource>
<datasource-mapping>Oracle9i</datasource-mapping>
<create-table>false</create-table>
<remove-table>false</remove-table>
<sync-on-commit-only>true</sync-on-commit-only>
<insert-after-ejb-post-create>true</insert-after-ejb-post-create>
<call-ejb-store-on-clean>true</call-ejb-store-on-clean>
</defaults>
<entity>
<ejb-name>User</ejb-name>
<table-name>USER</table-name>
<cmp-field><field-name>name</field-name>
<column-name>NAME</column-name></cmp-field>
</entity>
...
</jbosscmp-jdbc>
During the lifecycle of org.jboss.as.cmp.processors.CmpParsingProcessor, the default values previously settled (in <defaults>) are been replaced for the one defined in <entity> scope, but if we do not define anything like above, the CmpParsinProcessor is using the default values of the CmpConfig. (primitive values)
I had to change 2 classes to skip this problem and I would like to know if is applicable or make sense for you.
public class CmpConfig {
private boolean syncOnCommitOnly;
private boolean insertAfterEjbPostCreate;
private boolean callEjbStoreOnClean = true;
private boolean wasSyncOnCommitOnlyChanged = false;
private boolean wasInsertAfterEjbPostCreateChanged = false;
private boolean wasCallEjbStoreOnCleanChanged = false;
public boolean isSyncOnCommitOnly() {
return syncOnCommitOnly;
}
public void setSyncOnCommitOnly(boolean syncOnCommitOnly) {
this.syncOnCommitOnly = syncOnCommitOnly;
this.wasSyncOnCommitOnlyChanged = true;
}
public boolean isInsertAfterEjbPostCreate() {
return insertAfterEjbPostCreate;
}
public void setInsertAfterEjbPostCreate(boolean insertAfterEjbPostCreate) {
this.insertAfterEjbPostCreate = insertAfterEjbPostCreate;
this.wasInsertAfterEjbPostCreateChanged = true;
}
public boolean isCallEjbStoreOnClean() {
return callEjbStoreOnClean;
}
public void setCallEjbStoreOnClean(boolean callEjbStoreOnClean) {
this.callEjbStoreOnClean = callEjbStoreOnClean;
this.wasCallEjbStoreOnCleanChanged = true;
}
public boolean wasSyncOnCommitOnlyChanged() {
return wasSyncOnCommitOnlyChanged;
}
public boolean wasInsertAfterEjbPostCreateChanged() {
return wasInsertAfterEjbPostCreateChanged;
}
public boolean wasCallEjbStoreOnCleanChanged() {
return wasCallEjbStoreOnCleanChanged;
}
}
and
public JDBCEntityMetaData(JDBCApplicationMetaData jdbcApplication, ParsedEntity parsed, JDBCEntityMetaData defaultValues) {
....
....
localHomeClass = defaultValues.getLocalHomeClass();
localClass = defaultValues.getLocalClass();
cmpConfig = defaultValues.getCmpConfig(); // --> added
....
....
// cmpConfig = parsed.getCmpConfig(); -- removed
// -- added
if (parsed.getCmpConfig().wasSyncOnCommitOnlyChanged()) {
cmpConfig.setSyncOnCommitOnly(parsed.getCmpConfig().isSyncOnCommitOnly());
}
// -- added
if (parsed.getCmpConfig().wasInsertAfterEjbPostCreateChanged()) {
cmpConfig.setInsertAfterEjbPostCreate(parsed.getCmpConfig().isInsertAfterEjbPostCreate());
}
// -- added
if (parsed.getCmpConfig().wasCallEjbStoreOnCleanChanged()) {
cmpConfig.setCallEjbStoreOnClean(parsed.getCmpConfig().isCallEjbStoreOnClean());
}
}
Regards
> EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6079
> URL: https://issues.jboss.org/browse/AS7-6079
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.0.Alpha1, 7.1.3.Final (EAP)
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 7.2.0.CR1, 7.1.4.Final (EAP)
>
>
> In JBoss AS 7, EJB 2.1 CMP beans cannot configure some options such as sync-on-commit-only and insert-after-ejb-post which were configurable in previous versions of JBoss.
> Should also confirm how to configure the rest of the options that were available previously.
> <container-configuration>
> <container-name>Clustered CMP 2.x EntityBean</container-name>
> <call-logging>false</call-logging>
> <invoker-proxy-binding-name>clustered-entity-rmi-invoker</invoker-proxy-binding-name>
> <sync-on-commit-only>false</sync-on-commit-only>
> <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
> <container-interceptors>
> ...
> </container-interceptors>
> <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
> <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
> <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
> <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
> <container-cache-conf>
> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
> <cache-policy-conf>
> <min-capacity>50</min-capacity>
> <max-capacity>1000000</max-capacity>
> <overager-period>300</overager-period>
> <max-bean-age>600</max-bean-age>
> <resizer-period>400</resizer-period>
> <max-cache-miss-period>60</max-cache-miss-period>
> <min-cache-miss-period>1</min-cache-miss-period>
> <cache-load-factor>0.75</cache-load-factor>
> </cache-policy-conf>
> </container-cache-conf>
> <container-pool-conf>
> <MaximumSize>100</MaximumSize>
> </container-pool-conf>
> <commit-option>B</commit-option>
> </container-configuration>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6079) EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)
by Tiago Frazão (JIRA)
[ https://issues.jboss.org/browse/AS7-6079?page=com.atlassian.jira.plugin.s... ]
Tiago Frazão commented on AS7-6079:
------------------------------------
Hi Guys,
I do still have the issue ... and i had to change a little bit the Jboss code to overcome the problem.
When we define the configurations (sync-on-commin-only, insert-after-ejb-post-create, call-ejb-store-on-clean) in "jbosscmp-jdbc.xml" like bellow :
<jbosscmp-jdbc>
<defaults>
<datasource>java:jboss/datasources/XptoDS</datasource>
<datasource-mapping>Oracle9i</datasource-mapping>
<create-table>false</create-table>
<remove-table>false</remove-table>
<sync-on-commit-only>true</sync-on-commit-only>
<insert-after-ejb-post-create>true</insert-after-ejb-post-create>
<call-ejb-store-on-clean>true</call-ejb-store-on-clean>
</defaults>
<entity>
<ejb-name>User</ejb-name>
<table-name>USER</table-name>
<cmp-field><field-name>name</field-name>
<column-name>NAME</column-name></cmp-field>
</entity>
...
</jbosscmp-jdbc>
During the lifecycle of org.jboss.as.cmp.processors.CmpParsingProcessor, the default values previously settled (in <defaults> are been replaced for the one defined in <entity> scope, but if we do not define anything like above, the CmpParsinProcessor is using the default values of the CmpConfig. (primitive values)
I had to change 2 classes to skip this problem and I would like to know if is applicable or make sense for you.
public class CmpConfig {
private boolean syncOnCommitOnly;
private boolean insertAfterEjbPostCreate;
private boolean callEjbStoreOnClean = true;
private boolean wasSyncOnCommitOnlyChanged = false;
private boolean wasInsertAfterEjbPostCreateChanged = false;
private boolean wasCallEjbStoreOnCleanChanged = false;
public boolean isSyncOnCommitOnly()
{ return syncOnCommitOnly; }
public void setSyncOnCommitOnly(boolean syncOnCommitOnly)
{ this.syncOnCommitOnly = syncOnCommitOnly; this.wasSyncOnCommitOnlyChanged = true; }
public boolean isInsertAfterEjbPostCreate()
{ return insertAfterEjbPostCreate; }
public void setInsertAfterEjbPostCreate(boolean insertAfterEjbPostCreate)
{ this.insertAfterEjbPostCreate = insertAfterEjbPostCreate; this.wasInsertAfterEjbPostCreateChanged = true; }
public boolean isCallEjbStoreOnClean()
{ return callEjbStoreOnClean; }
public void setCallEjbStoreOnClean(boolean callEjbStoreOnClean)
{ this.callEjbStoreOnClean = callEjbStoreOnClean; this.wasCallEjbStoreOnCleanChanged = true; }
public boolean wasSyncOnCommitOnlyChanged()
{ return wasSyncOnCommitOnlyChanged; }
public boolean wasInsertAfterEjbPostCreateChanged()
{ return wasInsertAfterEjbPostCreateChanged; }
public boolean wasCallEjbStoreOnCleanChanged()
{ return wasCallEjbStoreOnCleanChanged; }
}
and
public JDBCEntityMetaData(JDBCApplicationMetaData jdbcApplication, ParsedEntity parsed, JDBCEntityMetaData defaultValues) {
....
....
localHomeClass = defaultValues.getLocalHomeClass();
localClass = defaultValues.getLocalClass();
cmpConfig = defaultValues.getCmpConfig(); // --> added
....
....
// cmpConfig = parsed.getCmpConfig(); – removed
// – added
if (parsed.getCmpConfig().wasSyncOnCommitOnlyChanged())
{ cmpConfig.setSyncOnCommitOnly(parsed.getCmpConfig().isSyncOnCommitOnly()); }
// – added
if (parsed.getCmpConfig().wasInsertAfterEjbPostCreateChanged())
{ cmpConfig.setInsertAfterEjbPostCreate(parsed.getCmpConfig().isInsertAfterEjbPostCreate()); }
// – added
if (parsed.getCmpConfig().wasCallEjbStoreOnCleanChanged())
{ cmpConfig.setCallEjbStoreOnClean(parsed.getCmpConfig().isCallEjbStoreOnClean()); }
}
Regards
> EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6079
> URL: https://issues.jboss.org/browse/AS7-6079
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.0.Alpha1, 7.1.3.Final (EAP)
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 7.2.0.CR1, 7.1.4.Final (EAP)
>
>
> In JBoss AS 7, EJB 2.1 CMP beans cannot configure some options such as sync-on-commit-only and insert-after-ejb-post which were configurable in previous versions of JBoss.
> Should also confirm how to configure the rest of the options that were available previously.
> <container-configuration>
> <container-name>Clustered CMP 2.x EntityBean</container-name>
> <call-logging>false</call-logging>
> <invoker-proxy-binding-name>clustered-entity-rmi-invoker</invoker-proxy-binding-name>
> <sync-on-commit-only>false</sync-on-commit-only>
> <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
> <container-interceptors>
> ...
> </container-interceptors>
> <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
> <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
> <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
> <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
> <container-cache-conf>
> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
> <cache-policy-conf>
> <min-capacity>50</min-capacity>
> <max-capacity>1000000</max-capacity>
> <overager-period>300</overager-period>
> <max-bean-age>600</max-bean-age>
> <resizer-period>400</resizer-period>
> <max-cache-miss-period>60</max-cache-miss-period>
> <min-cache-miss-period>1</min-cache-miss-period>
> <cache-load-factor>0.75</cache-load-factor>
> </cache-policy-conf>
> </container-cache-conf>
> <container-pool-conf>
> <MaximumSize>100</MaximumSize>
> </container-pool-conf>
> <commit-option>B</commit-option>
> </container-configuration>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6079) EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)
by Tiago Frazão (JIRA)
[ https://issues.jboss.org/browse/AS7-6079?page=com.atlassian.jira.plugin.s... ]
Tiago Frazão commented on AS7-6079:
------------------------------------
Hi Guys,
I do still have the issue ... and i had to change a little bit the Jboss code to overcome the problem.
When we define the configurations (sync-on-commin-only, insert-after-ejb-post-create, call-ejb-store-on-clean) in "jbosscmp-jdbc.xml" like bellow :
<jbosscmp-jdbc>
<defaults>
<datasource>java:jboss/datasources/XptoDS</datasource>
<datasource-mapping>Oracle9i</datasource-mapping>
<create-table>false</create-table>
<remove-table>false</remove-table>
<sync-on-commit-only>true</sync-on-commit-only>
<insert-after-ejb-post-create>true</insert-after-ejb-post-create>
<call-ejb-store-on-clean>true</call-ejb-store-on-clean>
</defaults>
<entity>
<ejb-name>User</ejb-name>
<table-name>USER</table-name>
<cmp-field><field-name>name</field-name>
<column-name>NAME</column-name></cmp-field>
</entity>
...
</jbosscmp-jdbc>
During the lifecycle of org.jboss.as.cmp.processors.CmpParsingProcessor, the default values previously settled (in <defaults>) are been replaced for the one defined in <entity> scope, but if we do not define anything like above, the CmpParsinProcessor is using the default values of the CmpConfig. (primitive values)
I had to change 2 classes to skip this problem and I would like to know if is applicable or make sense for you.
public class CmpConfig {
private boolean syncOnCommitOnly;
private boolean insertAfterEjbPostCreate;
private boolean callEjbStoreOnClean = true;
private boolean wasSyncOnCommitOnlyChanged = false;
private boolean wasInsertAfterEjbPostCreateChanged = false;
private boolean wasCallEjbStoreOnCleanChanged = false;
public boolean isSyncOnCommitOnly() {
return syncOnCommitOnly;
}
public void setSyncOnCommitOnly(boolean syncOnCommitOnly) {
this.syncOnCommitOnly = syncOnCommitOnly;
this.wasSyncOnCommitOnlyChanged = true;
}
public boolean isInsertAfterEjbPostCreate() {
return insertAfterEjbPostCreate;
}
public void setInsertAfterEjbPostCreate(boolean insertAfterEjbPostCreate) {
this.insertAfterEjbPostCreate = insertAfterEjbPostCreate;
this.wasInsertAfterEjbPostCreateChanged = true;
}
public boolean isCallEjbStoreOnClean() {
return callEjbStoreOnClean;
}
public void setCallEjbStoreOnClean(boolean callEjbStoreOnClean) {
this.callEjbStoreOnClean = callEjbStoreOnClean;
this.wasCallEjbStoreOnCleanChanged = true;
}
public boolean wasSyncOnCommitOnlyChanged() {
return wasSyncOnCommitOnlyChanged;
}
public boolean wasInsertAfterEjbPostCreateChanged() {
return wasInsertAfterEjbPostCreateChanged;
}
public boolean wasCallEjbStoreOnCleanChanged() {
return wasCallEjbStoreOnCleanChanged;
}
}
and
public JDBCEntityMetaData(JDBCApplicationMetaData jdbcApplication, ParsedEntity parsed, JDBCEntityMetaData defaultValues) {
....
....
localHomeClass = defaultValues.getLocalHomeClass();
localClass = defaultValues.getLocalClass();
cmpConfig = defaultValues.getCmpConfig(); // --> added
....
....
// cmpConfig = parsed.getCmpConfig(); -- removed
// -- added
if (parsed.getCmpConfig().wasSyncOnCommitOnlyChanged()) {
cmpConfig.setSyncOnCommitOnly(parsed.getCmpConfig().isSyncOnCommitOnly());
}
// -- added
if (parsed.getCmpConfig().wasInsertAfterEjbPostCreateChanged()) {
cmpConfig.setInsertAfterEjbPostCreate(parsed.getCmpConfig().isInsertAfterEjbPostCreate());
}
// -- added
if (parsed.getCmpConfig().wasCallEjbStoreOnCleanChanged()) {
cmpConfig.setCallEjbStoreOnClean(parsed.getCmpConfig().isCallEjbStoreOnClean());
}
}
Regards
> EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6079
> URL: https://issues.jboss.org/browse/AS7-6079
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.0.Alpha1, 7.1.3.Final (EAP)
> Reporter: Brad Maxwell
> Assignee: Brad Maxwell
> Fix For: 7.2.0.CR1, 7.1.4.Final (EAP)
>
>
> In JBoss AS 7, EJB 2.1 CMP beans cannot configure some options such as sync-on-commit-only and insert-after-ejb-post which were configurable in previous versions of JBoss.
> Should also confirm how to configure the rest of the options that were available previously.
> <container-configuration>
> <container-name>Clustered CMP 2.x EntityBean</container-name>
> <call-logging>false</call-logging>
> <invoker-proxy-binding-name>clustered-entity-rmi-invoker</invoker-proxy-binding-name>
> <sync-on-commit-only>false</sync-on-commit-only>
> <insert-after-ejb-post-create>false</insert-after-ejb-post-create>
> <container-interceptors>
> ...
> </container-interceptors>
> <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
> <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
> <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
> <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
> <container-cache-conf>
> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
> <cache-policy-conf>
> <min-capacity>50</min-capacity>
> <max-capacity>1000000</max-capacity>
> <overager-period>300</overager-period>
> <max-bean-age>600</max-bean-age>
> <resizer-period>400</resizer-period>
> <max-cache-miss-period>60</max-cache-miss-period>
> <min-cache-miss-period>1</min-cache-miss-period>
> <cache-load-factor>0.75</cache-load-factor>
> </cache-policy-conf>
> </container-cache-conf>
> <container-pool-conf>
> <MaximumSize>100</MaximumSize>
> </container-pool-conf>
> <commit-option>B</commit-option>
> </container-configuration>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6414) Management Console - LDAP authentication fails
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-6414?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse reassigned AS7-6414:
-------------------------------------
Assignee: Darran Lofthouse
> Management Console - LDAP authentication fails
> ----------------------------------------------
>
> Key: AS7-6414
> URL: https://issues.jboss.org/browse/AS7-6414
> Project: Application Server 7
> Issue Type: Bug
> Environment: JBoss 7.1.1 on windows xp 32 / jboss 7.1.2 on cent os 6.3, x86_64, standalone.xml
> Reporter: narayana b
> Assignee: Darran Lofthouse
>
> 1) security realms
> <!-- nari start -->
> <security-realm name="my_Ldap_Realm">
> <authentication>
> <ldap connection="my_Ldap_Connection" base-dn="dc=example,dc=com">
> <username-filter attribute="sAMAccountName"/>
> <!--
> <advanced-filter filter="(sAMAccountName={0})"/> -->
> </ldap>
> </authentication>
> </security-realm>
> <!-- nari end -->
> 2) outbound connections
> <!--nari start -->
> <outbound-connections>
> <ldap name="my_Ldap_Connection"
> url="ldap://localhost:10389/"
> search-dn="cn=jboss,ou=People,dc=example,dc=com" search-credential="admin123" />
> </outbound-connections>
> <!--nari end -->
> 3) Management console info config
> <!-- nari -->
> <native-interface security-realm="my_Ldap_Realm">
> <socket-binding native="management-native"/>
> </native-interface>
> <http-interface security-realm="my_Ldap_Realm">
> <socket-binding http="management-http"/>
> <!-- nari disabled [http] and enabled [https]
> <socket-binding https="management-console-https"/> -->
>
> </http-interface>
> <!-- nari end -->
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6414) Management Console - LDAP authentication fails
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-6414?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated AS7-6414:
----------------------------------
Complexity: (was: High)
> Management Console - LDAP authentication fails
> ----------------------------------------------
>
> Key: AS7-6414
> URL: https://issues.jboss.org/browse/AS7-6414
> Project: Application Server 7
> Issue Type: Bug
> Environment: JBoss 7.1.1 on windows xp 32 / jboss 7.1.2 on cent os 6.3, x86_64, standalone.xml
> Reporter: narayana b
> Assignee: Darran Lofthouse
>
> 1) security realms
> <!-- nari start -->
> <security-realm name="my_Ldap_Realm">
> <authentication>
> <ldap connection="my_Ldap_Connection" base-dn="dc=example,dc=com">
> <username-filter attribute="sAMAccountName"/>
> <!--
> <advanced-filter filter="(sAMAccountName={0})"/> -->
> </ldap>
> </authentication>
> </security-realm>
> <!-- nari end -->
> 2) outbound connections
> <!--nari start -->
> <outbound-connections>
> <ldap name="my_Ldap_Connection"
> url="ldap://localhost:10389/"
> search-dn="cn=jboss,ou=People,dc=example,dc=com" search-credential="admin123" />
> </outbound-connections>
> <!--nari end -->
> 3) Management console info config
> <!-- nari -->
> <native-interface security-realm="my_Ldap_Realm">
> <socket-binding native="management-native"/>
> </native-interface>
> <http-interface security-realm="my_Ldap_Realm">
> <socket-binding http="management-http"/>
> <!-- nari disabled [http] and enabled [https]
> <socket-binding https="management-console-https"/> -->
>
> </http-interface>
> <!-- nari end -->
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6415) Access Log directory - XML Parse issue
by narayana b (JIRA)
narayana b created AS7-6415:
-------------------------------
Summary: Access Log directory - XML Parse issue
Key: AS7-6415
URL: https://issues.jboss.org/browse/AS7-6415
Project: Application Server 7
Issue Type: Bug
Environment: Jboss 7.1.1 win xp 32 bit
Reporter: narayana b
step1)
<!-- -->
<paths>
<path path="E:/jboss/jboss-as-7.1.1.Final/standalone" name="access-log-dir" />
</paths>
step2) created a "access-log" dir under E:/jboss/jboss-as-7.1.1.Final/standalone
<virtual-server name="default-host" enable-welcome-root="true">
<alias name="localhost"/>
<alias name="example.com"/>
<acesss-log pattern="Time Taken: %T %h %l %u %t %r %s %b" resolve-hosts="false" extended="false" prefix="access_log." rotate="true">
<directory path ="access-log" relative-to="access-log-dir" />
</acesss-log>
</virtual-server>
Parse Error
-----------
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[351,5]
Message: JBAS014789: Unexpected element '{urn:jboss:domain:web:1.1}acesss-log' encountered
at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.web.WebSubsystemParser.parseHost(WebSubsystemParser.java:582)
at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:329)
at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:65)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Fi.........
Please let me know is this fixed? ready to release??
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] (AS7-6408) Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar reassigned AS7-6408:
--------------------------------
Assignee: Tomaz Cerar (was: Richard Achmatowicz)
> Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT
> ---------------------------------------------------------------------------
>
> Key: AS7-6408
> URL: https://issues.jboss.org/browse/AS7-6408
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.2.0.Alpha1
> Environment: Git checkout of JBossAS 7.2.0.ALPHA1 from today (28/Jan/2013)
> Reporter: Bernd Koecke
> Assignee: Tomaz Cerar
> Attachments: standalone-ha-jgroups.cli, standalone-jgroups-fragment.xml
>
>
> When I try to configure extension and subsystem JGroups with a CLI script, the attribute "protocols" of the stack=tcp- or stack=udp-node contains the list of configured protocols twice. The result is that the list of protocols is doubled in the standalone.xml. But having a protocol twice in one stack results in an error at next server startup. I will attach the CLI script and the resulting XML fragment.
> When I shutdown the server, remove the doubled second part of each protocol list, the server comes up and all is working fine. But I can't configure it only with a CLI script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months