wildfly-10

问题 We have developed a REST API using the resteasy. (deployed in wildfly 10) Basically these REST APIs are called internally from another application and end points are secured with keycloak. But one endpoint is exposed to outside party (that endpoint is also secured with keycloak). But since the outside party can't provide the Keycloak Autherization code, we have done an implementation where client is registerred with application generated auth_key and client will call the endpoint with that

问题 guy, I have a very strange problem. I am setting up some endpoints in my application and I have an endpoints like this: @Path("/ioconfiguration") public class IOConfigurationEndPoint { @EJB private static IOConfigurationDAO ioConfigurationDAO; @GET @Produces(MediaType.APPLICATION_JSON) public Response getAllIoConfigurations() { ioConfigurationDAO = new IOConfigurationDAO(); ioConfigurationDAO.init(); List<IOConfiguration> list = ioConfigurationDAO.findAllIOConfiguration(); ioConfigurationDAO

问题 Wildfly 15.0.1 When I run a simple javaee 6 web application in wildfly 15.0.1 which was build under java 1.8 with netbeans 8.2 give the following error. But when I browse the url application works fine. java.net.MalformedURLException: For input string: "8080undefined" at java.net.URL.<init>(URL.java:627) at java.net.URL.<init>(URL.java:490) at java.net.URL.<init>(URL.java:439) at org.netbeans.modules.ant.browsetask.NbBrowse.execute(NbBrowse.java:92) at org.apache.tools.ant.UnknownElement

问题 I'm getting a weird behavior after securing Wildfly Admin console to use HTTPS, and configuring my pom.xml to deploy over https. (I tried on versions 8.2.1 and 10.1.0, standalone mode). I can only (re)deploy once successfully. After that, I get the error below, and I have to restart the server to (re)deploy again: Change in pom.xml: <plugin> <groupId>org.wildfly.plugins</groupId> <artifactId>wildfly-maven-plugin</artifactId> <version>1.0.2.Final</version> <configuration> <protocol>https

问题 I'm getting a weird behavior after securing Wildfly Admin console to use HTTPS, and configuring my pom.xml to deploy over https. (I tried on versions 8.2.1 and 10.1.0, standalone mode). I can only (re)deploy once successfully. After that, I get the error below, and I have to restart the server to (re)deploy again: Change in pom.xml: <plugin> <groupId>org.wildfly.plugins</groupId> <artifactId>wildfly-maven-plugin</artifactId> <version>1.0.2.Final</version> <configuration> <protocol>https

问题 We're using WildFly 10 as our application server and deploy via Docker (deployment in WF is ordinary hotdeployment). We're not using WildFly's clustering mechanisms but simply have load-balancers (HAProxys) in front. The problem is that WF opens its HTTP port while the EAR deployment is still in progress. This (of course?) leads to HTTP 404 errors which we don't want to handle specifically in the LBs. This could lead to false negatives... Is there a way to allow HTTP connections only after

问题 I am having a very challenging time forcing HTTPS on a Bitnami Ubutnu Wildfly 10 install. The HTTPS works fine (e.g. https://example.com works great) I have tried many different things with no result. Here are some highlights of what I've done: I modified my web.xml to add this (note MYWEBNAME was replaced with my war file name): <security-constraint> <web-resource-collection> <web-resource-name>MYWEBNAME</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data

问题 I have setup wildfly16 cluster,this includes 3 nodes node1-wildfly load balancer node2,node3- deployed application war Now what if load balancer failed? This setup works fine even if one node fails, the load balancer will manage the session. But the problem is what if load balancer fails?? it will become single point failure . I have followed below link https://docs.jboss.org/author/display/WFLY/Using+Wildfly+as+a+Load+Balancer Also is there any other way to do clustering without load

问题 I have upgraded my Jaybird dependency in Wildfly 10 from Jaybird 2.2.11 to Jaybird 3.0.0-alpha-1. When I try to create a connection I now get the following stacktraces The first connection after startup (when testing in the admin console): 2016-08-27 10:50:45,354 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (External Management Request Threads -- 2) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to

问题 I have terrible problems to figure out how to configure logging via logback in my Java EE application on Wildfly 10. I tried to put slf4j-api-1.7.21.jar , logback-classic-1.1.7.jar and logback-core-1.1.7.jar in my ear in /lib/ , add logback.xml to resources in my ejb module and add jboss-deployment-structure.xml into my ear META-INF . It almost works... Logback creates my log files and correctly log into them. Unfortunately logging to console works strange. It looks like wildfly concatenated