wildfly-8

With the help of a ContainerResponseFilter I am able to apply CORS headers to all outgoing Responses, and with an ExceptionMapper I can do the same on all Errors and Exceptions, except for any authentication related Exceptions that Picketbox/Undertow is supposed to throw in Wildfly. My ExceptionMapper never catches it no matter what I try, and as a result, the frontend can't read the 401 status since the response doesn't have the CORS headers appended (the XHR HTTP status code just becomes 0). I am using this PBKDF2 setup to authenticate against a MySQL database, and at first I thought that

I'm currently searching for a way to stop a deployment on wildfly programmatically. Background: The application does some health checks in its startup phase using an MBean. If the app determines that the environment is not valid because some resources are missing, it needs to stop its own deployment. The way it was: The application was formerly running on JBoss 4 and simply stopped the whole app server calling the shutdown command using JMX. In case this command failed, it simply terminated the whole JVM using System.exit(1). Current problems: Calling shutdown() via JMX does not work on

We use a service orientated architecture approach where we have some core services used by other services. On startup, our services usually load up a cache of data from the core services so that it's available when a request comes in or scheduled tasks run. I'm using Wildfly 8.2.0 and have Project A which depends on Project B (both are .war's). Project A needs to wait for Project B to be loaded in order to start up. Here is jboss-deployment-structure.xml in project B: <?xml version='1.0' encoding='UTF-8'?> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> <deployment>

I have an Infinispan cache embedded in a WildFly 8.2 server. I added to standalone.xml inside <subsystem xmlns="urn:jboss:domain:infinispan:2.0"> : <cache-container name="mycache" default-cache="cachedb"> <transport lock-timeout="600000" /> <replicated-cache name="cachedb" batching="true" mode="SYNC" /> </cache-container> ...and injected the cache container like this: @Singleton @Startup public class CacheManager { @Resource(lookup = "java:jboss/infinispan/container/mycache") private CacheContainer container; . . . . } I can use the cache in my applications. However the requirement is to see

How do I modify the WildFly 8 logging levels, specifically server.log. Currently I suspect they default to INFO and would like to change it to Debug or Error. For reference I've been exploring these articles https://docs.jboss.org/author/display/WFLY8/Logging+Configuration https://docs.jboss.org/author/display/WFLY8/How+To And suspect this is correct; <subsystem xmlns="urn:jboss:domain:logging:2.0"> <console-handler name="CONSOLE"> <level name="DEBUG"/> <formatter> <named-formatter name="COLOR-PATTERN"/> By default the console-handler is set to INFO and the FILE handler does not have a level

My use case involves deployment of two different packages (war files) on a single Wildfly server. In standalone-full.xml my socket-binding-group looks like this after addition of the extra socket as below <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/> <socket-binding name="ajp" port="${jboss.ajp.port:8009}

I am using Eclipse Luna and WildFly 8.1 with JBPM 6.2. Currently, my Eclipse is configured so that I can start both the WildFly 8.1 server and the KIE workbench directly from within Eclipse. Previously, I had created an Evaluation.bpmn workflow from the KIE workbench and was able to succesfully deploy it and see the workflow logs in the database tables. However, is there a way to create a JBPM project in Eclipse and deploy and start the workflow directly from Eclipse? If so, how can I do it? This isn't deploying from eclipse. The best way is: Create a m2e project mentioned by @jl987 Create a