[JBoss JIRA] (WFLY-11124) The wildfly-testsuite-shared module brings in all WildFly dependencies
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11124?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11124:
---------------------------------
Fix Version/s: 15.0.0.Final
> The wildfly-testsuite-shared module brings in all WildFly dependencies
> ----------------------------------------------------------------------
>
> Key: WFLY-11124
> URL: https://issues.jboss.org/browse/WFLY-11124
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Critical
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> The {{org.wildfly:wildfly-testsuite-shared}} has a dependency all the main 3 Galleon feature-packs.
> {code:xml}
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>wildfly-galleon-pack</artifactId>
> <type>pom</type>
> </dependency>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>wildfly-servlet-galleon-pack</artifactId>
> <type>pom</type>
> </dependency>
> <dependency>
> <groupId>org.wildfly.core</groupId>
> <artifactId>wildfly-core-galleon-pack</artifactId>
> <type>pom</type>
> </dependency>
> {code}
> This means that all tests that which use the shared module, likely all of them, end up with the entirety of WildFly on the test class path. In most cases this is not an issue. However an issue was uncovered with the IBM JDK in WFLY-10529. The tests should definitely not have a transitive dependency on things like that or for example the {{org.wildfly.core:wildfly-controller}}. If dependencies like those are needed they should be explicitly defined as those are not public API's.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11083) Incorrectly named attribute match-user in authentication-context in Elytron subsystem
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11083?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11083:
---------------------------------
Fix Version/s: 15.0.0.Final
> Incorrectly named attribute match-user in authentication-context in Elytron subsystem
> -------------------------------------------------------------------------------------
>
> Key: WFLY-11083
> URL: https://issues.jboss.org/browse/WFLY-11083
> Project: WildFly
> Issue Type: Bug
> Components: Documentation
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
> Labels: user_experience
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> Rule matcher {{match-user}} in authentication-context in Elytron subsystem internally uses {{org.wildfly.security.auth.client.MatchUserRule}}. This matcher works based on passed userinfo. However naming of {{match-user}} in Elytron subsystem indicates that just user part of userinfo should be used in matching.
> Also description in CLI is not correct, it says: _The user to match against._
> It means one of following should be changed:
> * name of {{match-user}}
> * functionality of {{MatchUserRule}}
> Since Elytron client configuration file includes for the same matcher with name {{match-userinfo}} then I suggest to rename attribute {{match-user}} in {{authentication-context}} in Elytron subsystem to {{match-userinfo}} and improve description in CLI and XSD.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10974) NoClassDefFoundError when set-tx-query-timeout is enabled (followup to JBJCA-1378)
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10974?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10974:
---------------------------------
Fix Version/s: 15.0.0.Final
> NoClassDefFoundError when set-tx-query-timeout is enabled (followup to JBJCA-1378)
> ----------------------------------------------------------------------------------
>
> Key: WFLY-10974
> URL: https://issues.jboss.org/browse/WFLY-10974
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Critical
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> Fix for JBJCA-1378 is incomplete, module "org.wildfly.transaction.client" needs to be added as dependency to "org.jboss.ironjacamar.impl", otherwise ironjacamar won't see org/wildfly/transaction/client/ContextTransactionManager.
> {code}
> 16:25:27,126 WARN [org.jboss.jca.core.connectionmanager.listener.TxConnectionListener] (default task-1) IJ000305: Connection error occured: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@4fc3a65d[state=NORMAL managed connection=org.jboss.jca.adapters.jdbc.local.LocalManagedConnection@5a9822dd connection handles=1 lastReturned=1536071125023 lastValidated=1536071125009 lastCheckedOut=1536071127125 trackByTx=true pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@58ac913 mcp=SemaphoreConcurrentLinkedQueueManagedConnectionPool@6dee9bea[pool=ExampleDS] xaResource=LocalXAResourceImpl@c8022ad[connectionListener=4fc3a65d connectionManager=74e7ef50 warned=false currentXid=< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a28ccdb:5f37fa13:5b8e95a6:36, node_name=1, branch_uid=0:ffff0a28ccdb:5f37fa13:5b8e95a6:3d, subordinatenodename=null, eis_name=java:jboss/datasources/ExampleDS > productName=H2 productVersion=@PROJECT_VERSION@ (2016-10-31) jndiName=java:jboss/datasources/ExampleDS] txSync=TransactionSynchronization@952227486{tx=Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff0a28ccdb:5f37fa13:5b8e95a6:36 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) wasTrackByTx=true enlisted=true cancel=false}]: javax.resource.spi.ResourceAdapterInternalException: Unexpected error
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:664)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.connectionError(BaseWrapperManagedConnection.java:630)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.checkException(WrappedConnection.java:1969)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.checkException(WrappedStatement.java:1436)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:509)
> at com.redhat.thofman.jpa.MyBean.beanMethod(MyBean.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:92)
> at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.interceptorChainCompleted(WeldInvocationContextImpl.java:124)
> at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:143)
> at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInCallerTx(TransactionalInterceptorBase.java:132)
> at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.doIntercept(TransactionalInterceptorRequired.java:55)
> at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.intercept(TransactionalInterceptorBase.java:79)
> at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:47)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73)
> at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.invokeNext(WeldInvocationContextImpl.java:109)
> at org.jboss.weld.interceptor.proxy.WeldInvocationContextImpl.proceed(WeldInvocationContextImpl.java:141)
> at org.jboss.weld.bean.InterceptorImpl.intercept(InterceptorImpl.java:113)
> at org.jboss.as.weld.ejb.DelegatingInterceptorInvocationContext.proceed(DelegatingInterceptorInvocationContext.java:82)
> at org.jboss.as.weld.interceptors.EjbComponentInterceptorSupport.delegateInterception(EjbComponentInterceptorSupport.java:60)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:76)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:88)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:332)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:240)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81)
> at com.redhat.thofman.jpa.MyBean$$$view2.beanMethod(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:433)
> at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:133)
> at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
> at org.jboss.weld.bean.proxy.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:67)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
> at com.redhat.thofman.jpa.MyBean$Proxy$_$$_Weld$EnterpriseProxy$.beanMethod(Unknown Source)
> at com.redhat.thofman.jpa.MyServlet.doGet(MyServlet.java:37)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:65)
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> 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.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1501)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1501)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1501)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1501)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1501)
> 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:330)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NoClassDefFoundError: org/wildfly/transaction/client/ContextTransactionManager
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getTimeLeftBeforeTransactionTimeout(TxConnectionManagerImpl.java:392)
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getTimeLeftBeforeTransactionTimeout(WrapperDataSource.java:201)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.checkConfiguredQueryTimeout(WrappedConnection.java:2043)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.checkConfiguredQueryTimeout(WrappedStatement.java:1456)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:498)
> ... 131 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-10014) Unable to configure comma delimited enabled-protocols in remote-connector
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-10014?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-10014:
---------------------------------
Fix Version/s: 15.0.0.Final
> Unable to configure comma delimited enabled-protocols in remote-connector
> -------------------------------------------------------------------------
>
> Key: WFLY-10014
> URL: https://issues.jboss.org/browse/WFLY-10014
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 12.0.0.Final
> Reporter: Nagaraju Chitimilla
> Assignee: Jeff Mesnil
> Priority: Critical
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> When I want to configure enabled SSL protocols, Netty requires to use comma delimited list to be passed into enabled-protocols param in remote-connector
> {noformat}
> <param name="enabled-protocols" value="TLSv1.1,TLSv1.2"/>
> {noformat}
> But when comma is used in value in configuration string passed into ActiveMQRaUtils.parseConfig, parsing fails:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Invalid expression TLSv1.2 at enabledProtocols=TLSv1.1,TLSv1.2;trustStorePassword=N0tall0wed;keyStorePassword=N0tall0wed;port=61616;localAddress=0.0.0.0;sslEnabled=true;host=localhost;trustStorePath=C:/ActiveMQ/conf/keystore.p12;keyStorePath=C:/ActiveMQ/conf/keystore.p12
> at org.apache.activemq.artemis.ra.ActiveMQRaUtils.parseConfig(ActiveMQRaUtils.java:205)
> at org.apache.activemq.artemis.ra.ActiveMQResourceAdapter.setConnectionParameters(ActiveMQResourceAdapter.java:342)
> ... 18 more
> {code}
> I set this as critical as it prevent setting more then one allowed SSLContext protocol.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11046) Quickstarts JDK11 illegal reflective access warnings in wildfly-maven-plugin
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11046?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11046:
---------------------------------
Fix Version/s: 15.0.0.Final
> Quickstarts JDK11 illegal reflective access warnings in wildfly-maven-plugin
> ----------------------------------------------------------------------------
>
> Key: WFLY-11046
> URL: https://issues.jboss.org/browse/WFLY-11046
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Jan Blizňák
> Assignee: Eduardo Martins
> Priority: Critical
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> Currently when any quickstart using wildfly-maven-plugin (eg jaxws-retail) is executed using JDK11, illegal reflective access warning are printed:
> {code:java}
> [INFO] --- wildfly-maven-plugin:1.2.1.Final:deploy (default-cli) @ jaxws-retail-service ---
> Sep 20, 2018 10:10:32 AM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Sep 20, 2018 10:10:32 AM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.5.1.Final
> Sep 20, 2018 10:10:32 AM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.5.1.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (file:/home/jbliznak/.m2/repository/org/jboss/xnio/xnio-nio/3.5.1.Final/xnio-nio-3.5.1.Final.jar) to constructor sun.nio.ch.EPollSelectorProvider()
> WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Sep 20, 2018 10:10:32 AM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.0.Final
> {code}
> Fix and update is probably expected on plugin side, you can see the version of Xnio is rather old, WF 14 is using 3.6.5 https://github.com/wildfly/wildfly-core/blob/6.0.1.Final/pom.xml#L188 (with possible fix XNIO-322, also check WFCORE-3885).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4254) Impossible to use environment variables or system properties in permissions.xml
by Kabir Khan (Jira)
Kabir Khan created WFCORE-4254:
----------------------------------
Summary: Impossible to use environment variables or system properties in permissions.xml
Key: WFCORE-4254
URL: https://issues.jboss.org/browse/WFCORE-4254
Project: WildFly Core
Issue Type: Feature Request
Components: Security
Reporter: Adrian Boangiu
Assignee: Yeray Borges
Without this feature it is impossible to migrate "variable" Java file permissions such as:
{noformat}
permission java.io.FilePermission "${java.io.tmpdir}","read";
permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete";
permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete";
{noformat}
that were defined in Java policy file in previous verions of JBoss.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11033) mod_cluster custom load metrics fail to load
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
James Perkins reopened WFLY-11033:
----------------------------------
> mod_cluster custom load metrics fail to load
> --------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11033) mod_cluster custom load metrics fail to load
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
James Perkins updated WFLY-11033:
---------------------------------
Fix Version/s: 15.0.0.Final
> mod_cluster custom load metrics fail to load
> --------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 15.0.0.Beta1, 15.0.0.Final
>
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11033) mod_cluster custom load metrics fail to load
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFLY-11033?page=com.atlassian.jira.plugin... ]
James Perkins resolved WFLY-11033.
----------------------------------
Resolution: Done
> mod_cluster custom load metrics fail to load
> --------------------------------------------
>
> Key: WFLY-11033
> URL: https://issues.jboss.org/browse/WFLY-11033
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 14.0.0.Final
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 15.0.0.Final, 15.0.0.Beta1
>
>
> This message shows up if I try to define module attribute for 'custom-load-metric'. It doesn't make sense, since it says both, that 'module' attribute is and isn't allowed. This also means, that the module attribute is not usable.
> {code}
> OPVDX001: Validation error in standalone-ha.xml --------------------------------
> |
> | 448: <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp">
> | 449: <dynamic-load-provider>
> | 450: <custom-load-metric class="biz.karms.modcluster.CustomLoadMetric" module="org.jboss.mod_cluster" weight="1" capacity="1000.0">
> | ^^^^ 'module' isn't an allowed attribute for the 'custom-load-metric'
> | element
> |
> | Attributes allowed here are: capacity, class, module, weight
> |
> | 451: <property name="parseexpression" value="^LOAD: ([0-9]*)$"/>
> | 452: <property name="loadfile" value="/home/virtual/mod_cluster_workspace/loadfileA"/>
> | 453: </custom-load-metric>
> |
> | 'module' is allowed on elements:
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > object-factory
> | - server > profile > {urn:jboss:domain:naming:2.0}subsystem > bindings > external-context
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > minimum-set > permission
> | - server > profile > {urn:jboss:domain:security-manager:1.0}subsystem > deployment-permissions > maximum-set > permission
> | - server > profile > {urn:jboss:domain:datasources:5.0}subsystem > datasources > drivers > driver
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source > class
> | - server > profile > {urn:wildfly:microprofile-config-smallrye:1.0}subsystem > config-source-provider > class
> | - server > extensions > extension
> | - server > vault
> | - server > management > security-realms > security-realm > plug-ins > plug-in
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > cache-container > local-cache
> | - server > profile > {urn:jboss:domain:infinispan:7.0}subsystem > remote-cache-container
> | - server > profile > {urn:jboss:domain:modcluster:4.0}subsystem > proxy > dynamic-load-provider > custom-load-metric
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > login-module-stack > login-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authentication-jaspi > auth-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > authorization > policy-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > acl > acl-module
> | - server > profile > {urn:jboss:domain:security:2.0}subsystem > security-domains > security-domain > mapping > mapping-module
> | (and 26 more)
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[450,21]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months