[JBoss JIRA] (WFLY-5426) Data sources other than h2 cannot be added to domain servers
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/WFLY-5426?page=com.atlassian.jira.plugin.... ]
Stefano Maestri commented on WFLY-5426:
---------------------------------------
it's a regression of linked issue for hot deployed driver (not for module deplyed one)
> Data sources other than h2 cannot be added to domain servers
> ------------------------------------------------------------
>
> Key: WFLY-5426
> URL: https://issues.jboss.org/browse/WFLY-5426
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 9.0.0.Final
> Reporter: James Perkins
> Assignee: Stefano Maestri
> Priority: Blocker
> Fix For: 10.0.0.Final
>
>
> This seems to work okay with the h2 driver, but adding a postgres driver add operations fail.
> The driver is deployed and is on the {{main-server-group}} which defaults to the {{full}} profile.
> {code}
> [domain@localhost:9990 /] /server-group=main-server-group:read-children-resources(child-type=deployment,recursive=true,include-runtime=true)
> {
> "outcome" => "success",
> "result" => {"postgresql-9.4-1201.jdbc41.jar" => {
> "enabled" => true,
> "name" => "postgresql-9.4-1201.jdbc41.jar",
> "runtime-name" => "postgresql-9.4-1201.jdbc41.jar"
> }}
> }
> {code}
> Attempting to add the data source results in the following error:
> {code}
> [domain@localhost:9990 /] /profile=full/subsystem=datasources/data-source=test-pg:add(driver-name=postgresql-9.4-1201.jdbc41.jar, connection-url=jdbc:postgresql://localhost:test,user-name=user,password=password, jndi-name=java:jboss/datasources/test-pg)
> {
> "outcome" => "failed",
> "result" => undefined,
> "failure-description" => {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
> "server-two" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}}
> }}}}}},
> "rolled-back" => true,
> "server-groups" => {"main-server-group" => {"host" => {"master" => {
> "server-one" => {"response" => {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
> "rolled-back" => true
> }},
> "server-two" => {"response" => {
> "outcome" => "failed",
> "failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.data-source.java:jboss/datasources/test-pg" => "org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/datasources/test-pg: WFLYJCA0033: Error during the deployment of test-pg
> Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYJCA0032: Unable to start the ds because it generated more than one cf"}},
> "rolled-back" => true
> }}
> }}}}
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-755) Security Realm Plug-Ins to provide their own configuration parsers.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-755?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse resolved WFLY-755.
-----------------------------------
Release Notes Text: Elytron is bringing custom realm definitions which will be replacing the use of plug-ins
Fix Version/s: 10.0.0.Final
(was: Awaiting Volunteers)
Assignee: Darran Lofthouse
Resolution: Out of Date
> Security Realm Plug-Ins to provide their own configuration parsers.
> -------------------------------------------------------------------
>
> Key: WFLY-755
> URL: https://issues.jboss.org/browse/WFLY-755
> Project: WildFly
> Issue Type: Task
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 10.0.0.Final
>
>
> Security realm plug-ins are currently configured with name / value pairs - to make plug-ins easier to use by those that did not implement them we should consider allowing a custom XML parser to allow new configuration elements to be defined.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (DROOLS-933) Allow to optionally pass a dependency filter when creating KieModuleMetaData
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-933:
----------------------------------
Summary: Allow to optionally pass a dependency filter when creating KieModuleMetaData
Key: DROOLS-933
URL: https://issues.jboss.org/browse/DROOLS-933
Project: Drools
Issue Type: Feature Request
Reporter: Mario Fusco
Assignee: Mario Fusco
When creating the meta data for a given KieModule it is required to optionally filter its dependencies with the following filtering interface:
{code}
public interface DependencyFilter {
boolean accept(ReleaseId releaseId, String scope);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-5154) DenyModulePermissionsTestCase, GrantModulePermissionsTestCase, LimitedModulePermissionsTestCase cannot deploy jar
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-5154?page=com.atlassian.jira.plugin.... ]
Marek Kopecký reopened WFLY-5154:
---------------------------------
This issue is still valid in wildfly 10.0.0.CR2
> DenyModulePermissionsTestCase, GrantModulePermissionsTestCase, LimitedModulePermissionsTestCase cannot deploy jar
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5154
> URL: https://issues.jboss.org/browse/WFLY-5154
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Marek Kopecký
> Assignee: Josef Cacek
> Fix For: 10.0.0.CR2
>
>
> *Description of problem*
> * org.jboss.as.testsuite.integration.secman.module.DenyModulePermissionsTestCase
> ** fails with Cannot deploy: modperm-deny.jar
> * org.jboss.as.testsuite.integration.secman.module.GrantModulePermissionsTestCase
> ** fails with Cannot deploy: modperm-grant.jar
> * org.jboss.as.testsuite.integration.secman.module.LimitedModulePermissionsTestCase
> ** fails with Cannot deploy: modperm-limited.jar
> *How reproducible*
> * 15%
> * OpenJDK, IBM JDK, Oracle JDK
> * Solaris, Windows, RHEL
>
> *Expected results*
> No failures in test case.
> *Additional info*
> See for server logs for DenyModulePermissionsTestCase in attachment
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (ELY-296) Pass through Digest authentication against LDAP
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-296?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse moved WFLY-1217 to ELY-296:
--------------------------------------------
Project: WildFly Elytron (was: WildFly)
Key: ELY-296 (was: WFLY-1217)
Component/s: Realms
(was: Domain Management)
(was: Security)
Fix Version/s: (was: Awaiting Volunteers)
> Pass through Digest authentication against LDAP
> -----------------------------------------------
>
> Key: ELY-296
> URL: https://issues.jboss.org/browse/ELY-296
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Realms
> Reporter: Darran Lofthouse
> Labels: Common_Authentication
>
> It is possible for a client to authenticate against an LDAP server using Digest authentication.
> This task is to make use of this with both our SASL mechanism and HTTP authenticator to provide a pass through check.
> We need AS7-3691 first and then this needs to be implemented in a way that can consistently be used for both SASL and HTTP Digest.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-5430) Rename the EJB3 subsystem to EJB
by David Lloyd (JIRA)
David Lloyd created WFLY-5430:
---------------------------------
Summary: Rename the EJB3 subsystem to EJB
Key: WFLY-5430
URL: https://issues.jboss.org/browse/WFLY-5430
Project: WildFly
Issue Type: Task
Components: EJB
Reporter: David Lloyd
Priority: Minor
I mean, really.
Retain compatibility with all previous configurations, operations, and schema which may use the name "ejb3".
Identify any public APIs under {{org.jboss.as.ejb3}} and ensure they are retained.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-5167) IIOPNamingInContainer*TestCase can not connect to ORB with security manager
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-5167?page=com.atlassian.jira.plugin.... ]
Marek Kopecký reopened WFLY-5167:
---------------------------------
org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase#testStatefulIIOPNamingInvocation fails with this stacktrace:
{noformat}
org.omg.CORBA.UNKNOWN:
at com.sun.corba.se.spi.servicecontext.UEInfoServiceContext.<init>(UEInfoServiceContext.java:52)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at com.sun.corba.se.spi.servicecontext.ServiceContextData.makeServiceContext(ServiceContextData.java:132)
at com.sun.corba.se.spi.servicecontext.ServiceContexts.unmarshal(ServiceContexts.java:216)
at com.sun.corba.se.spi.servicecontext.ServiceContexts.get(ServiceContexts.java:378)
at com.sun.corba.se.spi.servicecontext.ServiceContexts.get(ServiceContexts.java:366)
at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:530)
at com.sun.corba.se.impl.protocol.SharedCDRClientRequestDispatcherImpl.marshalingComplete(SharedCDRClientRequestDispatcherImpl.java:222)
at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:148)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:475)
at org.jboss.as.ejb3.iiop.stub.DynamicIIOPStub.invoke(DynamicIIOPStub.java:127)
at interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPStatefulNamingHome_Stub.create(Unknown Source)
at org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase.testStatefulIIOPNamingInvocation(IIOPNamingInContainerTestCase.java:60)
{noformat}
> IIOPNamingInContainer*TestCase can not connect to ORB with security manager
> ---------------------------------------------------------------------------
>
> Key: WFLY-5167
> URL: https://issues.jboss.org/browse/WFLY-5167
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.0.0.CR1
> Reporter: Marek Kopecký
> Assignee: Tomasz Adamski
> Fix For: 10.0.0.CR2
>
>
> *Description of problem:*
> Two tests can not connect to ORB with security manager. Tests run in "basic-integration-default-full.surefire" execution of basic profile.
> * org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerDDNameTestCase
> * org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # ./integration-tests.sh -fae -Dmaven.test.failure.ignore=true -Dnode0=$MYTESTIP_1 -Dnode1=$MYTESTIP_2 -DfailIfNoTests=false -Dsecurity.manager -Dts.basic -Dts.noSmoke -Dtest=IIOPNamingInContainerDDNameTestCase,IIOPNamingInContainerTestCase
> *Actual results:*
> {noformat}
> avax.naming.NamingException: WFLYIIOP0031: Cannot connect to ORB
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2200)
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2221)
> at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:223)
> at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:236)
> at com.sun.corba.se.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:119)
> at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:187)
> at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:137)
> at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:229)
> at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:130)
> at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.setOrbAndRootContext(CNCtx.java:353)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.initUsingCorbanameUrl(CNCtx.java:335)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.initUsingUrl(CNCtx.java:268)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.initOrbAndRootContext(CNCtx.java:233)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtx.<init>(CNCtx.java:99)
> at org.wildfly.iiop.openjdk.naming.jndi.CNCtxFactory.getInitialContext(CNCtxFactory.java:53)
> at org.wildfly.iiop.openjdk.naming.jndi.WrapperInitialContext.lookup(WrapperInitialContext.java:72)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
> at org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerDDNameTestCase.testIIOPNamingInvocationWithDDOverride(IIOPNamingInContainerDDNameTestCase.java:55)
> {noformat}
> *Expected results:*
> No errors on output
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-5015) RunAs in servlet doesn't work
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5015?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas reopened WFLY-5015:
--------------------------------
Reopen. See JBEAP-512 for details.
> RunAs in servlet doesn't work
> -----------------------------
>
> Key: WFLY-5015
> URL: https://issues.jboss.org/browse/WFLY-5015
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security, Web (Undertow)
> Affects Versions: 10.0.0.Alpha6
> Reporter: Josef Cacek
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 10.0.0.CR1
>
>
> RunAs for servlets doesn't work in Undertow.
> I have unprotected {{@RunAs}}-annotated servlet which calls protected EJB method. The call should succeed, but it throws {{javax.ejb.EJBAccessException}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-5428) Xml files from wildfly don't end with "new line character"
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-5428?page=com.atlassian.jira.plugin.... ]
Marek Kopecký moved JBEAP-1181 to WFLY-5428:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5428 (was: JBEAP-1181)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Build System
(was: Build System)
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.CR2
(was: 7.0.0.DR11 (Alpha))
> Xml files from wildfly don't end with "new line character"
> ----------------------------------------------------------
>
> Key: WFLY-5428
> URL: https://issues.jboss.org/browse/WFLY-5428
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Affects Versions: 10.0.0.CR2
> Reporter: Marek Kopecký
> Assignee: Paul Gier
>
> *Description of problem:*
> * Some of xml files from *wildfly* don't end with "new line character".
> * Each xml file should end with "new line character", because of posix standard:
> ** http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#t...
> * List of affected files:
> ** ./docs/examples/configs/standalone-gossip-ha.xml
> ** ./docs/examples/configs/standalone-ec2-ha.xml
> ** ./docs/examples/configs/standalone-picketlink.xml
> ** ./docs/examples/configs/standalone-ec2-full-ha.xml
> ** ./docs/examples/configs/standalone-rts.xml
> ** ./docs/examples/configs/standalone-jts.xml
> ** ./docs/examples/configs/standalone-xts.xml
> ** ./docs/examples/configs/standalone-genericjms.xml
> ** ./docs/examples/configs/standalone-gossip-full-ha.xml
> ** ./standalone/configuration/standalone.xml
> ** ./standalone/configuration/standalone-ha.xml
> ** ./standalone/configuration/standalone-full.xml
> ** ./standalone/configuration/standalone-full-ha.xml
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # cd EAP_HOME
> # {noformat}
> for xml in `find -type f | grep xml$`; do
> if [ "`cat -E $xml | tail -n 1 |grep -o '.$'`" != "$" ] ; then
> echo $xml
> fi
> done
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months