wildfly

I am trying to configure an security domain in Wildfly (8.2.1) for binding to our Active Directory. I need to try to find a way to encrypt the bindCredential password. I am able to encrypt the data source passwords just fine using Picketbox. I only could find out to do this encryption for JBoss V6.x or before and the method employed doesn't seem to exist any longer in Wildfly. Has anyone done this and willing to share how it can be accomplished. Here is my security domain: <security-domain name="ADDomain" cache-type="default"> <authentication> <login-module code="org.jboss.security.auth.spi

I'm trying to set up a JMS Bridge between Artemis (Running in WildFly 10) and ActiveMQ 5.14 In general the process seems to work smoothly, but unfortunately I'm getting stuck on the XA configuration that is necessary to get ONCE_AND_ONLY_ONCE QoS to work. Although messages do arrive on the ActiveMQ side, I get the following error in the WildFly log: 11:25:57,920 WARN [org.apache.activemq.artemis.jms.bridge] (Thread-97) AMQ342009: JMS Bridge failed to send + acknowledge batch, closing JMS objects: javax.jms.IllegalStateException: Not a transacted session at org.apache.activemq.ActiveMQSession

I am working with WildFly 10.1 which ships with Artemis as the new JMS provider but I am unable to find how to dynamically change the number of consumer threads for a specific MDB. I have a queue, and a message listener (MDB) consuming messages from the queue, now I want to dynamically control the maximum number of consumers threads the domain must start. How can I do it using CLI? Rémi Bantos As you want to do this configuration for a specific MDB you could firstly assign it to a dedicated pool. See this answer . Then to dynamically update your pool attributes you could take a look at this

Still no Java 8 (JDK) support for the OpenShift Wildfly 8.1 cartridge? Is this a limitation of the SELinux gear? Or can I just create a Java 8 JDK cartridge and a modified Wildfly 8 cartridge and combine them in the same gear? As of june 3rd, there is JDK 8 support for wildfly. See https://www.openshift.com/content/support-for-jdk-8#comment-39656 As can be read here: https://community.jboss.org/people/fjuma/blog/2014/06/03/wildfly-810final-on-openshift--with-jdk-8-support new wildfly instances from scratch will default to JDK 8. OpenShift currently does not support JDK8 yet. Once it will be

I am developing a straightforward maven-based JavaEE application in IntelliJ IDEA, and obviously I would like to use Wildfly 8 for both development and production. I simply need to expose some entities through some RESTful web services. Those entities have bidirectional relationships, which leads to a loop when they are going to be serialized into JSON. Newer versions of Jackson are able to handle this kind of situation with a special annotation. To get that to work, I need to exclude Wildfly's built-in JSON serializer / jackson provider / whatever it is and use the newer version that comes

Im working on a Java Webservices Project Using the Jersey Servlet (1.18.1). When deploying my EAR file to Jboss WildFly (8.1.0) I'm Getting the following Error and im unsure why its breaking as this same EAR file deployed and worked 100% in JBoss7 (7.1.1). The Error stacktrace: java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126) at org.jboss.as.naming.WritableServiceBasedNamingStore.createSubcontext(WritableServiceBasedNamingStore.java:116) at org.jboss.as

目前网络上罕有近期版本的配置，本人经多次尝试网络中不同方式配置，在Testing Connection一步中尽皆失败后，查询官方文档未果，摸索出一条可行之路，在此分享于诸位朋友。 　　【../wildfly-16.0.0.Final\modules\system\layers\base\com\mysql\main】目录中存放 mysql-connector-java-5.1.39-bin.jar 文件，（当然，版本你可以根据你的环境选择，存在一些版本会导致数据库连接失败）和module.xml文件。 上述文件中的mysql文件夹以及main文件夹是自定义文件夹，main文件夹名字不要任性。module文件中配置如下内容： 1 <?xml version="1.0" encoding="UTF-8"?> 2 <module name="com.mysql" xmlns="urn:jboss:module:1.5"> 3 <resources> 4 <resource-root path="mysql-connector-java-5.1.39-bin.jar"/> 5 </resources> 6 <dependencies> 7 <module name="javax.api"/> 8 <module name="javax.transaction.api"/> 9

I have some troubles with injecting POJOs via @Inject using Wildfly. The documentation clearly states: @Dependent - The default scope if none is specified; it means that an object exists to serve exactly one client (bean) and has the same lifecycle as that client (bean). However, when I have two classes: @Singleton @Startup public class A{ @Inject private B b; } public class B{ public B(){} } I keep getting: Unsatisfied dependencies for type B with qualifiers @Default at injection point [BackedAnnotatedField] @Inject [...] When I add @Dependent everything works like a charm. Am I missing

A part of this question. In attempt to using WildFly 9.0.2 final with NetBeans IDE 8.1 (the final release), some serious consequences are still seen. The IDE (the integrated plugin) never auto-deploys the application even though the "Deploy on Save" option on the IDE is enabled (checked / turned on). This always happens correctly while using GlassFish Server. It was already reported and its status is "RESOLVED FIXED" for NetBeans 8.0 but it is difficult to rely upon (sorry). I have migrated the most part of a relatively sizable Java EE application from GlassFish 4.1 to WildFly 9.0.2 final