[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
by Clebert Suconic (JIRA)
[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ]
Clebert Suconic commented on WFLY-10094:
----------------------------------------
We have stopped compiling 32 bits upstream. People still use it ?
> [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
> -----------------------------------------------------------------
>
> Key: WFLY-10094
> URL: https://issues.jboss.org/browse/WFLY-10094
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> LibAIO does not get loaded on RHEL 6 x86_64:
> {code}
> [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /tmp/jboss-eap
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> ...
> 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance.
> 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging)
> 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal
> ...
> {code}
> libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-9978) resource adapter sometimes fails to start when it uses legacy security-domain
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9978?page=com.atlassian.jira.plugin.... ]
Martin Simka edited comment on WFLY-9978 at 4/25/18 12:05 PM:
--------------------------------------------------------------
It looks like this is caused by WFLY-8323.
{code:java|title=RaServicesFactory.java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
builder.addDependency(SubjectFactoryService.SERVICE_NAME, SubjectFactory.class,
service.getSubjectFactoryInjector())
.addDependency(SimpleSecurityManagerService.SERVICE_NAME,
ServerSecurityManager.class, service.getServerSecurityManager());
}
{code}
the part
{code:java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
{code}
is what causes troubles. {{raxml}} might not be available yet because some services aren't started ({{ConnectionDefinitionService}} or {{CDConfigPropertiesService}}). {{ModifiableResourceAdapter}} doesn't contain all data yet. So there is no full {{raxml}} with security definitions.
-I'm not sure if that code is needed in {{RaServicesFactory.java}}. Dependency on SubjectFactoryService is added on other places.- (It fails, so obviously it is needed. On other places it is added for different services). Also what I don't understand is direction of dependencies. {{ConnectionDefinitionService}} depends on {{ResourceAdapterService}}, shouldn't it be opposite or shouldn't they depend on each other?
In short, {{raxml}} doesn't contain full RA configuration -> {{ActivationSecurityUtil.isLegacySecurityRequired(raxml)}} returns false -> dependency on {{SubjectFactoryService}} isn't added
was (Author: simkam):
It looks like this is caused by WFLY-8323.
{code:java|title=RaServicesFactory.java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
builder.addDependency(SubjectFactoryService.SERVICE_NAME, SubjectFactory.class,
service.getSubjectFactoryInjector())
.addDependency(SimpleSecurityManagerService.SERVICE_NAME,
ServerSecurityManager.class, service.getServerSecurityManager());
}
{code}
the part
{code:java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
{code}
is what causes troubles. {{raxml}} might not be available yet because some services aren't started ({{ConnectionDefinitionService}} or {{CDConfigPropertiesService}}). {{ModifiableResourceAdapter}} doesn't contain all data yet. So there is no full {{raxml}} with security definitions.
I'm not sure if that code is needed in {{RaServicesFactory.java}}. Dependency on SubjectFactoryService is added on other places. Also what I don't understand is direction of dependencies. {{ConnectionDefinitionService}} depends on {{ResourceAdapterService}}, shouldn't it be opposite or shouldn't they depend on each other?
In short, {{raxml}} doesn't contain full RA configuration -> {{ActivationSecurityUtil.isLegacySecurityRequired(raxml)}} returns false -> dependency on {{SubjectFactoryService}} isn't added
> resource adapter sometimes fails to start when it uses legacy security-domain
> -----------------------------------------------------------------------------
>
> Key: WFLY-9978
> URL: https://issues.jboss.org/browse/WFLY-9978
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Environment: WildFly 11
> JBoss EAP 7.1.0
> Reporter: Martin Simka
> Assignee: Stefano Maestri
> Priority: Blocker
> Attachments: bad.txt, good.txt, standalone.xml
>
>
> When resource adapter is configured with legacy security domain, it sometimes fails to start.
> Error:
> {noformat}
> 2018-03-07 16:04:34,300 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/tmp/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/genericjms/main/
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)
> ... 10 more
> {noformat}
> Full logs for good and bad start with enabled trace logging for {{org.jboss.as.connector}}, {{org.jboss.as.security}} and {{org.jboss.security}} are attached.
> Priority set to blocker because it seems to be regression against WildFly 10 (and JBoss EAP 7.0.0) where I wasn't able to reproduce this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-9978) resource adapter sometimes fails to start when it uses legacy security-domain
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9978?page=com.atlassian.jira.plugin.... ]
Martin Simka edited comment on WFLY-9978 at 4/25/18 11:59 AM:
--------------------------------------------------------------
It looks like this is caused by WFLY-8323.
{code:java|title=RaServicesFactory.java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
builder.addDependency(SubjectFactoryService.SERVICE_NAME, SubjectFactory.class,
service.getSubjectFactoryInjector())
.addDependency(SimpleSecurityManagerService.SERVICE_NAME,
ServerSecurityManager.class, service.getServerSecurityManager());
}
{code}
the part
{code:java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
{code}
is what causes troubles. {{raxml}} might not be available yet because some services aren't started ({{ConnectionDefinitionService}} or {{CDConfigPropertiesService}}). {{ModifiableResourceAdapter}} doesn't contain all data yet. So there is no full {{raxml}} with security definitions.
I'm not sure if that code is needed in {{RaServicesFactory.java}}. Dependency on SubjectFactoryService is added on other places. Also what I don't understand is direction of dependencies. {{ConnectionDefinitionService}} depends on {{ResourceAdapterService}}, shouldn't it be opposite or shouldn't they depend on each other?
In short, {{raxml}} doesn't contain full RA configuration -> {{ActivationSecurityUtil.isLegacySecurityRequired(raxml)}} returns false -> dependency on {{SubjectFactoryService}} isn't added
was (Author: simkam):
It looks like this is caused by WFLY-8323.
{code:java|title=RaServicesFactory.java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
builder.addDependency(SubjectFactoryService.SERVICE_NAME, SubjectFactory.class,
service.getSubjectFactoryInjector())
.addDependency(SimpleSecurityManagerService.SERVICE_NAME,
ServerSecurityManager.class, service.getServerSecurityManager());
}
{code}
the part
{code:java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
{code}
is what causes troubles. {{raxml}} might not be available yet because some services aren't started ({{ConnectionDefinitionService}} or {{CDConfigPropertiesService}}). {{ModifiableResourceAdapter}} doesn't contain all data yet. So there is no full {{raxml}} with security definitions.
I'm not sure if that code is needed in {{RaServicesFactory.java}}. Dependency on SubjectFactoryService is added on other places. Also what I don't understand is direction of dependencies. {{ConnectionDefinitionService}} depends on {{ResourceAdapterService}}, shouldn't it be opposite or shouldn't they depend on each other?
> resource adapter sometimes fails to start when it uses legacy security-domain
> -----------------------------------------------------------------------------
>
> Key: WFLY-9978
> URL: https://issues.jboss.org/browse/WFLY-9978
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Environment: WildFly 11
> JBoss EAP 7.1.0
> Reporter: Martin Simka
> Assignee: Stefano Maestri
> Priority: Blocker
> Attachments: bad.txt, good.txt, standalone.xml
>
>
> When resource adapter is configured with legacy security domain, it sometimes fails to start.
> Error:
> {noformat}
> 2018-03-07 16:04:34,300 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/tmp/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/genericjms/main/
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)
> ... 10 more
> {noformat}
> Full logs for good and bad start with enabled trace logging for {{org.jboss.as.connector}}, {{org.jboss.as.security}} and {{org.jboss.security}} are attached.
> Priority set to blocker because it seems to be regression against WildFly 10 (and JBoss EAP 7.0.0) where I wasn't able to reproduce this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-9978) resource adapter sometimes fails to start when it uses legacy security-domain
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9978?page=com.atlassian.jira.plugin.... ]
Martin Simka commented on WFLY-9978:
------------------------------------
It looks like this is caused by WFLY-8323.
{code:java|title=RaServicesFactory.java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
builder.addDependency(SubjectFactoryService.SERVICE_NAME, SubjectFactory.class,
service.getSubjectFactoryInjector())
.addDependency(SimpleSecurityManagerService.SERVICE_NAME,
ServerSecurityManager.class, service.getServerSecurityManager());
}
{code}
the part
{code:java}
if (ActivationSecurityUtil.isLegacySecurityRequired(raxml)) {
{code}
is what causes troubles. {{raxml}} might not be available yet because some services aren't started ({{ConnectionDefinitionService}} or {{CDConfigPropertiesService}}). {{ModifiableResourceAdapter}} doesn't contain all data yet. So there is no full {{raxml}} with security definitions.
I'm not sure if that code is needed in {{RaServicesFactory.java}}. Dependency on SubjectFactoryService is added on other places. Also what I don't understand is direction of dependencies. {{ConnectionDefinitionService}} depends on {{ResourceAdapterService}}, shouldn't it be opposite or shouldn't they depend on each other?
> resource adapter sometimes fails to start when it uses legacy security-domain
> -----------------------------------------------------------------------------
>
> Key: WFLY-9978
> URL: https://issues.jboss.org/browse/WFLY-9978
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Environment: WildFly 11
> JBoss EAP 7.1.0
> Reporter: Martin Simka
> Assignee: Stefano Maestri
> Priority: Blocker
> Attachments: bad.txt, good.txt, standalone.xml
>
>
> When resource adapter is configured with legacy security domain, it sometimes fails to start.
> Error:
> {noformat}
> 2018-03-07 16:04:34,300 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 62) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/tmp/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/genericjms/main/
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)
> at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)
> at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)
> ... 10 more
> {noformat}
> Full logs for good and bad start with enabled trace logging for {{org.jboss.as.connector}}, {{org.jboss.as.security}} and {{org.jboss.security}} are attached.
> Priority set to blocker because it seems to be regression against WildFly 10 (and JBoss EAP 7.0.0) where I wasn't able to reproduce this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-10297) Datasource clearStatistics operation clears things it shouldn't
by Rich DiCroce (JIRA)
Rich DiCroce created WFLY-10297:
-----------------------------------
Summary: Datasource clearStatistics operation clears things it shouldn't
Key: WFLY-10297
URL: https://issues.jboss.org/browse/WFLY-10297
Project: WildFly
Issue Type: Bug
Affects Versions: 12.0.0.Final
Reporter: Rich DiCroce
Assignee: Jason Greene
Executing the clearStatistics operation on a datasource pool seems to zero everything, but there are some attributes that should not be affected. For example, after clearing statistics, ActiveCount, InUseCount, and IdleCount all report zero even though my database clearly shows some active connections.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (ELY-1537) PolicyContext.getContext("javax.security.auth.Subject.container")
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1537?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1537:
---------------------------------------
I can see how out public / private module approach could cause confusion, maybe we need to add a comment to the private module pointing out that there is a module exposing the public API.
> PolicyContext.getContext("javax.security.auth.Subject.container")
> -----------------------------------------------------------------
>
> Key: ELY-1537
> URL: https://issues.jboss.org/browse/ELY-1537
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.2.3.Final
> Reporter: Ilia Vassilev
> Assignee: Darran Lofthouse
>
> PolicyContext.getContext("javax.security.auth.Subject.container") returns null when using elytron to protect a web application.
> This should return the authenticated subject.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ]
Jeff Mesnil commented on WFLY-10094:
------------------------------------
Some further information.
The linux-x86_64/libartemis-native-64.so is the same in Artemis 2.5.0.Final and 1.5.5.jbossorg-010 (from https://repository.jboss.org/nexus/content/repositories/releases/org/apac...)
However, in 1.5.5.jbossorg-010, there is another lib that is *not* present in 2.5.0.Final:
{code}
$ shasum lib/linux-i686/libartemis-native-32.so
62022822bce6906cb918e4703767bf5a1573fbd3 lib/linux-i686/libartemis-native-32.so
{code}
[~clebertsuconic] is it normal that this linux-i686/libartemis-native-32.so is missing from Artemis 2.5.0.Final?
> [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64
> -----------------------------------------------------------------
>
> Key: WFLY-10094
> URL: https://issues.jboss.org/browse/WFLY-10094
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
>
> LibAIO does not get loaded on RHEL 6 x86_64:
> {code}
> [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /tmp/jboss-eap
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> ...
> 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance.
> 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging)
> 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal
> ...
> {code}
> libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag.
> Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a)
> Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFCORE-3748) Copying lot of commands into CLI prompt fails
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3748?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-3748:
----------------------------------------------
I confirm, this is a bug in aesh-readline. I am working on a fix.
> Copying lot of commands into CLI prompt fails
> ---------------------------------------------
>
> Key: WFCORE-3748
> URL: https://issues.jboss.org/browse/WFCORE-3748
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 5.0.0.Alpha3
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
>
> Running commands with --file option works OK. Copying commands one by one works OK
> Seems to me as something is beeing overflowed.
> {code}
> [standalone@localhost:9990 /] # prepare server and client key materials
> [standalone@localhost:9990 /] # generate server keystore
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:add(type=PKCS12, credential-reference={clear-text=secret},path=/tmp/server.keystore)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:generate-key-pair(alias=server, distinguished-name="CN=server")
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:export-certificate(alias=server,path=/tmp/server.certificate.pem,pem=true)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] # generate client keystore
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:add(type=PKCS12, credential-reference={clear-text=secret},path=/tmp/client.keystore)
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:generate-key-pair(alias=client, distinguished-name="CN=client")
> {"outcome" => "success"}
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:export-certificate(alias=clieytron/key-store=client_truststore:import-certificate(alias=server,path=/tmp/server.certificate.pem,validate=false
> Closing ')' is missing.
> [standalone@localhost:9990 /] # save it all
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_keystore:store()
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_keystore:store()
> {
> "outcome" => "success",
> "result" => undefined
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=server_truststore:store()
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0216: Management resource '[
> (\"subsystem\" => \"elytron\"),
> (\"key-store\" => \"server_truststore\")
> ]' not found",
> "rolled-back" => true
> }
> [standalone@localhost:9990 /] /subsystem=elytron/key-store=client_truststore:store()
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-10296) Wildscribe: last operation in list does not expand
by Rich DiCroce (JIRA)
Rich DiCroce created WFLY-10296:
-----------------------------------
Summary: Wildscribe: last operation in list does not expand
Key: WFLY-10296
URL: https://issues.jboss.org/browse/WFLY-10296
Project: WildFly
Issue Type: Bug
Components: Documentation
Affects Versions: 12.0.0.Final
Reporter: Rich DiCroce
On wildscribe.github.io, the last item (on any page) listed under Operations doesn't expand when you click on it.
Apologies if this is not the right place to report a Wildscribe bug. It doesn't seem to have a separate JIRA project, and the GitHub issue tracker looks unused.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months