[JBoss JIRA] (WFLY-9214) Remove experimental Hibernate Search / JGroups integration
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-9214?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on WFLY-9214:
---------------------------------------
This component should be removed to un-entangle the dependency matrix: there is no replacement compatible with JGroups 4 yet and WildFly needs to upgrade to JGroups 4 to benefit from the newer Infinispan.
> Remove experimental Hibernate Search / JGroups integration
> ----------------------------------------------------------
>
> Key: WFLY-9214
> URL: https://issues.jboss.org/browse/WFLY-9214
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 11.0.0.CR1
>
>
> The {{<artifactId>hibernate-search-backend-jgroups</artifactId>}} has never matured from its experimental status, and should not have been included in WildFly.
> We never supported it, it's presence is not documented in EAP docs, and should simply be removed as it was a mistake to include it in the first place.
> I'll keep the reference to it as an optional dependency from the module, so that people can still drop in the module if they want to. I just don't believe this should be shipped by default.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9228) CXF Fediz library cannot be included into the application
by Zoltán Takács (JIRA)
Zoltán Takács created WFLY-9228:
-----------------------------------
Summary: CXF Fediz library cannot be included into the application
Key: WFLY-9228
URL: https://issues.jboss.org/browse/WFLY-9228
Project: WildFly
Issue Type: Bug
Affects Versions: 10.0.0.Final
Reporter: Zoltán Takács
Assignee: Jason Greene
We use Apache CXF Fediz (http://cxf.apache.org/fediz.html) libraries in our application. It is a subproject of Apache CXF, but independent of it. We cannot create a wildfly module from this, because the library has a lot of dependecies and these dependencies could cause other class loading problems. So we need to add it into our war file.
In *org.jboss.as.webservices.deployers.WSLibraryFilterProcessor* class wildfly deployer filter all classes from org.apache.cxf package, including classes in org.apache.cxf.fediz.
We suggest to modify this filter to allow us to use CXF subproject (primarily Fediz).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ELY-1226) Elytron dir-context referral mode THROW results to LdapReferralException for MS Active Directory
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/ELY-1226?page=com.atlassian.jira.plugin.s... ]
Jiri Ondrusek reassigned ELY-1226:
----------------------------------
Assignee: Jiri Ondrusek (was: Darran Lofthouse)
> Elytron dir-context referral mode THROW results to LdapReferralException for MS Active Directory
> ------------------------------------------------------------------------------------------------
>
> Key: ELY-1226
> URL: https://issues.jboss.org/browse/ELY-1226
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta47
> Reporter: Ondrej Lukas
> Assignee: Jiri Ondrusek
>
> When Elytron dir-context is configured to use referral mode THROW and MS Active Directory is used and ldap-realm attributes {{identity-mapping.search-base-dn}} or {{identity-mapping.attribute-mapping.filter-base-dn}} is configured to referral domain (i.e. domain which is referred through crossRef of LDAP server configured in related {{dir-context}}) then LdapReferralException is thrown and authentication is failed.
> In correct behavior ldap-realm with THROW referral mode should be able to authenticate user from referral correctly.
> Thrown Exception:
> {code}
> BASIC: org.wildfly.security.http.HttpAuthenticationException: org.wildfly.security.http.HttpAuthenticationException: org.wildfly.security.auth.server.RealmUnavailableException: ELY01108: Ldap-backed realm identity search failed
> at org.wildfly.security.http.impl.BasicAuthenticationMechanism.evaluateRequest(BasicAuthenticationMechanism.java:176)
> at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:114)
> at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77)
> at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:115)
> at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:94)
> at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:78)
> at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:100)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
> at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:211)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.wildfly.security.http.HttpAuthenticationException: org.wildfly.security.auth.server.RealmUnavailableException: ELY01108: Ldap-backed realm identity search failed
> at org.wildfly.security.http.impl.UsernamePasswordAuthenticationMechanism.authenticate(UsernamePasswordAuthenticationMechanism.java:79)
> at org.wildfly.security.http.impl.BasicAuthenticationMechanism.evaluateRequest(BasicAuthenticationMechanism.java:152)
> ... 37 more
> Caused by: org.wildfly.security.auth.server.RealmUnavailableException: ELY01108: Ldap-backed realm identity search failed
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapSearch.search(LdapSecurityRealm.java:1138)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.getIdentity(LdapSecurityRealm.java:689)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.verifyEvidence(LdapSecurityRealm.java:601)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1859)
> at org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:665)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:877)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:787)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:928)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:735)
> at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$SecurityIdentityCallbackHandler.handle(SecurityIdentityServerMechanismFactory.java:113)
> at org.wildfly.security.http.impl.UsernamePasswordAuthenticationMechanism.authenticate(UsernamePasswordAuthenticationMechanism.java:73)
> ... 38 more
> Caused by: com.sun.jndi.ldap.LdapReferralException: [LDAP: error code 10 - 0000202B: RefErr: DSID-03100781, data 0, 1 access points
> ref 1: 'eap-vm002.mw.lab.eng.bos.redhat.com'
> \00]; remaining name 'ou=SimpleADReferralTestCasea4e11461,OU=secondary,O=eapqe,DC=JBOSS3,DC=test2'
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2975)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
> at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1846)
> at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1769)
> at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1786)
> at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:418)
> at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:396)
> at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:297)
> at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:297)
> at org.wildfly.security.auth.realm.ldap.DelegatingLdapContext.search(DelegatingLdapContext.java:330)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapSearch.searchWithPagination(LdapSecurityRealm.java:1158)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapSearch.search(LdapSecurityRealm.java:1052)
> ... 48 more
> {code}
> Similar issue for referral mode THROW is also included in older version of application server, see JBEAP-3027 and JBEAP-3029.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9227) XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
by Marius Schmidt (JIRA)
[ https://issues.jboss.org/browse/WFLY-9227?page=com.atlassian.jira.plugin.... ]
Marius Schmidt updated WFLY-9227:
---------------------------------
Description:
I expected the this to work, but I does not seem to:
{noformat}
GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
<xa-datasource-property name="URL">
${source.db.url:undefined}
</xa-datasource-property>
<driver>OracleJDBCDriver</driver>
<xa-pool>
<min-pool-size>0</min-pool-size>
<max-pool-size>10</max-pool-size>
<is-same-rm-override>false</is-same-rm-override>
<no-tx-separate-pools>true</no-tx-separate-pools>
</xa-pool>
<security>
<user-name>${source.db.user:user}</user-name>
<password>${source.db.password:password}</password>
</security>
<recovery no-recovery="true"/>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
<stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
</validation>
</xa-datasource>
</datasources>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>
</subsystem>
AND a /full/path/to/file.properties file fitting a database connection, containing
source.db.enabled=true
source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
source.db.user=USER
source.db.password=PASSWORD
WHEN the server is started with --properties=/full/path/to/file.properties
THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
{noformat}
was:
I expected the this to work, but I does not seem to:
GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
<xa-datasource-property name="URL">
${source.db.url:undefined}
</xa-datasource-property>
<driver>OracleJDBCDriver</driver>
<xa-pool>
<min-pool-size>0</min-pool-size>
<max-pool-size>10</max-pool-size>
<is-same-rm-override>false</is-same-rm-override>
<no-tx-separate-pools>true</no-tx-separate-pools>
</xa-pool>
<security>
<user-name>${source.db.user:user}</user-name>
<password>${source.db.password:password}</password>
</security>
<recovery no-recovery="true"/>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
<stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
</validation>
</xa-datasource>
</datasources>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>
</subsystem>
AND a /full/path/to/file.properties file fitting a database connection, containing
source.db.enabled=true
source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
source.db.user=USER
source.db.password=PASSWORD
WHEN the server is started with --properties=/full/path/to/file.properties
THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
> XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-9227
> URL: https://issues.jboss.org/browse/WFLY-9227
> Project: WildFly
> Issue Type: Bug
> Components: ConfigAdmin
> Affects Versions: 10.1.0.Final
> Reporter: Marius Schmidt
> Assignee: Thomas Diesler
>
> I expected the this to work, but I does not seem to:
> {noformat}
> GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
> <xa-datasource-property name="URL">
> ${source.db.url:undefined}
> </xa-datasource-property>
> <driver>OracleJDBCDriver</driver>
> <xa-pool>
> <min-pool-size>0</min-pool-size>
> <max-pool-size>10</max-pool-size>
> <is-same-rm-override>false</is-same-rm-override>
> <no-tx-separate-pools>true</no-tx-separate-pools>
> </xa-pool>
> <security>
> <user-name>${source.db.user:user}</user-name>
> <password>${source.db.password:password}</password>
> </security>
> <recovery no-recovery="true"/>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
> <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
> </validation>
> </xa-datasource>
> </datasources>
> <drivers>
> <driver name="h2" module="com.h2database.h2">
> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
> </driver>
> <driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
> </driver>
> </drivers>
> </subsystem>
> AND a /full/path/to/file.properties file fitting a database connection, containing
> source.db.enabled=true
> source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
> source.db.user=USER
> source.db.password=PASSWORD
> WHEN the server is started with --properties=/full/path/to/file.properties
> THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9227) XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
by Marius Schmidt (JIRA)
[ https://issues.jboss.org/browse/WFLY-9227?page=com.atlassian.jira.plugin.... ]
Marius Schmidt updated WFLY-9227:
---------------------------------
Priority: Minor (was: Major)
> XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-9227
> URL: https://issues.jboss.org/browse/WFLY-9227
> Project: WildFly
> Issue Type: Bug
> Components: ConfigAdmin
> Affects Versions: 10.1.0.Final
> Reporter: Marius Schmidt
> Assignee: Thomas Diesler
> Priority: Minor
>
> I expected the this to work, but I does not seem to:
> {noformat}
> GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
> <subsystem xmlns="urn:jboss:domain:datasources:4.0">
> <datasources>
> <xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
> <xa-datasource-property name="URL">
> ${source.db.url:undefined}
> </xa-datasource-property>
> <driver>OracleJDBCDriver</driver>
> <xa-pool>
> <min-pool-size>0</min-pool-size>
> <max-pool-size>10</max-pool-size>
> <is-same-rm-override>false</is-same-rm-override>
> <no-tx-separate-pools>true</no-tx-separate-pools>
> </xa-pool>
> <security>
> <user-name>${source.db.user:user}</user-name>
> <password>${source.db.password:password}</password>
> </security>
> <recovery no-recovery="true"/>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
> <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
> </validation>
> </xa-datasource>
> </datasources>
> <drivers>
> <driver name="h2" module="com.h2database.h2">
> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
> </driver>
> <driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
> </driver>
> </drivers>
> </subsystem>
> AND a /full/path/to/file.properties file fitting a database connection, containing
> source.db.enabled=true
> source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
> source.db.user=USER
> source.db.password=PASSWORD
> WHEN the server is started with --properties=/full/path/to/file.properties
> THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9227) XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
by Marius Schmidt (JIRA)
Marius Schmidt created WFLY-9227:
------------------------------------
Summary: XA-Datasources not shown in admin console when using expressions (${some.thing}) in xml config
Key: WFLY-9227
URL: https://issues.jboss.org/browse/WFLY-9227
Project: WildFly
Issue Type: Bug
Components: ConfigAdmin
Affects Versions: 10.1.0.Final
Reporter: Marius Schmidt
Assignee: Thomas Diesler
I expected the this to work, but I does not seem to:
GIVEN a Wildfly 10.1.0.Final subsystem datasources configuration as
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<xa-datasource jndi-name="java:/datasources/SOURCE" pool-name="SOURCE" enabled="${source.db.enabled:false}">
<xa-datasource-property name="URL">
${source.db.url:undefined}
</xa-datasource-property>
<driver>OracleJDBCDriver</driver>
<xa-pool>
<min-pool-size>0</min-pool-size>
<max-pool-size>10</max-pool-size>
<is-same-rm-override>false</is-same-rm-override>
<no-tx-separate-pools>true</no-tx-separate-pools>
</xa-pool>
<security>
<user-name>${source.db.user:user}</user-name>
<password>${source.db.password:password}</password>
</security>
<recovery no-recovery="true"/>
<validation>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
<stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
</validation>
</xa-datasource>
</datasources>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="OracleJDBCDriver" module="com.oracle.ojdbc7">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>
</subsystem>
AND a /full/path/to/file.properties file fitting a database connection, containing
source.db.enabled=true
source.db.url=jdbc:oracle:thin:@sample.de:1521:MY_SID
source.db.user=USER
source.db.password=PASSWORD
WHEN the server is started with --properties=/full/path/to/file.properties
THEN the webadmin console shows the xa-datasource SOURCE within the datasources subsytem
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9223) fix comment formatting for "concurrent" cache in *ha.xml profiles
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9223?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-9223 at 8/15/17 6:22 AM:
---------------------------------------------------------------
+1 for removing, the right place is in the documentation or a bundled CLI script to add that part of config.
was (Author: rhusar):
+1 for removing, the right place is in the documentation.
> fix comment formatting for "concurrent" cache in *ha.xml profiles
> -----------------------------------------------------------------
>
> Key: WFLY-9223
> URL: https://issues.jboss.org/browse/WFLY-9223
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Labels: eap7.1-ok-for-CR1
> Fix For: 11.0.0.CR1
>
>
> The current state (taken from standalone-ha.xml):
> {code:xml}
> <cache-container name="web" default-cache="dist" module="org.wildfly.clustering.web.infinispan">
> ...
> <!-- Alternate configuration to reduce lock contention for applications that make use of concurrent access to a web session -->
> <!-- Web sessions will be locked more frequently, but for shorter periods of time -->
> <!--
> ~ distributed-cache name="concurrent">
> ~ <file-store/>
> ~ </distributed-cache
> -->
> </cache-container>
> {code}
> After uncommenting, the resulting text is not a valid xml file.
> Please change it to:
> {code:xml}
> <cache-container name="web" default-cache="dist" module="org.wildfly.clustering.web.infinispan">
> ...
> <!-- Alternate configuration to reduce lock contention for applications that make use of concurrent access to a web session -->
> <!-- Web sessions will be locked more frequently, but for shorter periods of time -->
> <!--
> <distributed-cache name="concurrent">
> <file-store/>
> </distributed-cache>
> -->
> </cache-container>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-9223) fix comment formatting for "concurrent" cache in *ha.xml profiles
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9223?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-9223:
--------------------------------------
+1 for removing, the right place is in the documentation.
> fix comment formatting for "concurrent" cache in *ha.xml profiles
> -----------------------------------------------------------------
>
> Key: WFLY-9223
> URL: https://issues.jboss.org/browse/WFLY-9223
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Beta1
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Labels: eap7.1-ok-for-CR1
> Fix For: 11.0.0.CR1
>
>
> The current state (taken from standalone-ha.xml):
> {code:xml}
> <cache-container name="web" default-cache="dist" module="org.wildfly.clustering.web.infinispan">
> ...
> <!-- Alternate configuration to reduce lock contention for applications that make use of concurrent access to a web session -->
> <!-- Web sessions will be locked more frequently, but for shorter periods of time -->
> <!--
> ~ distributed-cache name="concurrent">
> ~ <file-store/>
> ~ </distributed-cache
> -->
> </cache-container>
> {code}
> After uncommenting, the resulting text is not a valid xml file.
> Please change it to:
> {code:xml}
> <cache-container name="web" default-cache="dist" module="org.wildfly.clustering.web.infinispan">
> ...
> <!-- Alternate configuration to reduce lock contention for applications that make use of concurrent access to a web session -->
> <!-- Web sessions will be locked more frequently, but for shorter periods of time -->
> <!--
> <distributed-cache name="concurrent">
> <file-store/>
> </distributed-cache>
> -->
> </cache-container>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (DROOLS-1694) Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1694?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1694.
---------------------------------
Fix Version/s: 6.4.0.Final
Resolution: Done
This issue has been fixed from 6.4.0.Final. We tested 6.4.0.Final, 6.5.0.Final, 7.3.0-SNAPSHOT and master and all work as expected.
> Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-1694
> URL: https://issues.jboss.org/browse/DROOLS-1694
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.3.0.Final
> Reporter: Alistair Black
> Assignee: Massimiliano Dessi
> Fix For: 6.4.0.Final
>
>
> I am working on a multi-module BRMS project, with each module encapsulating a set of rules forming a single knowledge base. There is a "packaging" module which inherits each of these modules in order to generate a KJAR for deployment purposes. The application then utilises this KJAR via the KieScanner/ReleaseId approach to facilitate dynamic rule loading at runtime and decoupling of application/rules.
> Having taken the above approach I have encountered an issue where the master build fails when building the "packaging" module as part of the main project build. If the module is built on it's own, then it completes without error.
> The error reported is:
> {{[ERROR] Failed to execute goal org.kie:kie-maven-plugin:6.3.0.Final:build (default-build) on project rules: Execution default-build of goal org.kie:kie-maven-plugin:6.3.0.Final:build failed: Illegal class for global. Expected [org.drools.template.parser.DefaultGenerator], found [org.drools.template.parser.DefaultGenerator]. -> [Help 1]}}
> Having liased with Maciej Swiderski he has asked me to report it as a bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months