[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)
7 years, 6 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)
7 years, 6 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)
7 years, 6 months
[JBoss JIRA] (WFLY-9824) Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9824?page=com.atlassian.jira.plugin.... ]
David Lloyd resolved WFLY-9824.
-------------------------------
Resolution: Rejected
Please see http://wildfly.org/gethelp/ for how to get help.
> Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9824
> URL: https://issues.jboss.org/browse/WFLY-9824
> Project: WildFly
> Issue Type: Bug
> Components: EE, EJB
> Affects Versions: 11.0.0.Beta1, 11.0.0.Final
> Reporter: shubhashish dash
> Priority: Critical
> Attachments: EAR.ear, server.log
>
>
> I have deployed a EAR in wildfly 11.0.0 Final. The EAR has two sub deplyoment one is a .rar and another is a .war . The both the deployment contains below code
> ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> final InitialContext initialContext = new InitialContext();
> final ManagementHome mejb = (ManagementHome) initialContext.lookup("ejb/mgmt/MEJB");
> final ObjectName searchpattern = new ObjectName("*:j2eeType=J2EEServer,*");
> final Management management = mejb.create();
> final Set<ObjectName> set = management.queryNames(searchpattern, null);
> if (set != null && set.size() != 0) {
> final String s = management.getAttribute(set.iterator().next(), "serverVendor").toString();
> System.out.println(s);
> }
> ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> But while running the application I am getting "javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB"" error. This error only comes in case of rar and not in the war.
> I have attached the sample app with this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-9824) Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
by shubhashish dash (JIRA)
[ https://issues.jboss.org/browse/WFLY-9824?page=com.atlassian.jira.plugin.... ]
shubhashish dash commented on WFLY-9824:
----------------------------------------
Please respond to my above concern .
Thanks,
Shubhashish
> Getting javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB" in resourceadpater
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9824
> URL: https://issues.jboss.org/browse/WFLY-9824
> Project: WildFly
> Issue Type: Bug
> Components: EE, EJB
> Affects Versions: 11.0.0.Beta1, 11.0.0.Final
> Reporter: shubhashish dash
> Priority: Critical
> Attachments: EAR.ear, server.log
>
>
> I have deployed a EAR in wildfly 11.0.0 Final. The EAR has two sub deplyoment one is a .rar and another is a .war . The both the deployment contains below code
> ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> final InitialContext initialContext = new InitialContext();
> final ManagementHome mejb = (ManagementHome) initialContext.lookup("ejb/mgmt/MEJB");
> final ObjectName searchpattern = new ObjectName("*:j2eeType=J2EEServer,*");
> final Management management = mejb.create();
> final Set<ObjectName> set = management.queryNames(searchpattern, null);
> if (set != null && set.size() != 0) {
> final String s = management.getAttribute(set.iterator().next(), "serverVendor").toString();
> System.out.println(s);
> }
> ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
> But while running the application I am getting "javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB EJBHomeLocator for "jsr-77/jsr-77/EJB"" error. This error only comes in case of rar and not in the war.
> I have attached the sample app with this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 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:
------------------------------------
> libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag.
I don't understand your comment.
the lib in EAP is the same than the one from Artemis 2.5.0.Final tag
I downloaded the http://central.maven.org/maven2/org/apache/activemq/artemis-native/2.5.0/... and checksummed the lib in it:
{code}
$ shasum lib/linux-x86_64/libartemis-native-64.so
e54de22dbc33f65dcec31f4a2be3b07907c7359b lib/linux-x86_64/libartemis-native-64.so
{code}
that's the same lib that is in https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-...:
{code}
$ shasum jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so
e54de22dbc33f65dcec31f4a2be3b07907c7359b jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so
{code}
I can't run libaio on my mac but the issue is not having a different library file
> [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)
7 years, 6 months
[JBoss JIRA] (WFLY-10286) Consider to add secmgr options to CLI and JDR
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-10286?page=com.atlassian.jira.plugin... ]
Jean-Francois Denise commented on WFLY-10286:
---------------------------------------------
In both cases (CLI, JDR), if we don't have a strong requirement for it, I would not invest in making changes to scripts. User can make changes directly in existing scripts if he has such an (un-common?) need.
Enabling the security-manager can have large side effect on the CLI. But here we are speaking about the JBOSS Module Security-Manager setup. All builtin modules are granted all permissions, so we are safe.
I would say that it makes sense to have this option to allow to start an embedded server with JBOSS module security manager enabled. Doing so you can reproduce a standalone context.
I would be on the same line as https://issues.jboss.org/browse/WFLY-10242?focusedCommentId=13561804&page...
An explicit -secmgr option (with the proper help to explain the embedded use-case) and SECMGR env.
For JDR, if it makes sense to have it enabled then same approach should be chosen. [~bmaxwell]?
> Consider to add secmgr options to CLI and JDR
> ---------------------------------------------
>
> Key: WFLY-10286
> URL: https://issues.jboss.org/browse/WFLY-10286
> Project: WildFly
> Issue Type: Bug
> Components: CLI, Scripts
> Reporter: Marek Kopecký
> Assignee: Jean-Francois Denise
>
> Wildfly standalone/domain/appclient scripts allows two ways for start EAP with security manager:
> * -secmgr command line argument ({{./standalone.sh -secmgr}})
> ** This is described in documentation only in Configuration guide in "A.1. Server Runtime Arguments"
> * SECMGR=true env property
> ** This is not described in documentation at all.
> Does it make sence to add secmgr parameter to CLI script? CLI allows to start embedded server, and standalone.sh (non-embedded server) script has the secmgr option. Does it make sence to add secmgr parameter to the jdr script too? JDR tool uses embedded cli server too in some cases.
> Cc: [~eduda], [~mnovak])
> See [this my command|https://issues.jboss.org/browse/WFLY-10242?focusedCommentId=13561...]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months