wildfly-8

问题 We have upgraded jboss to wildfly , in older version we were facing some issue like this Maximum number of parameter passed in a post. In older version of jboss we got this error message 2015-02-10 20:04:34,582 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/sf].[action]] (http-- 127.0.0.1-8080-38) Servlet.service() for servlet action threw exception: java.lang.IllegalStateException: More than the maximum number of request parameters (GET plus POST) for a single

问题 We used to query the active session count by using the following code up to JBoss 7: ObjectName name = new ObjectName(jboss.web:type=Manager,path=/MyWebApp,host=default-host); MBeanServer jboss = MBeanServerLocator.locateJBoss(); this.sessions = new Long((Integer) jboss.getAttribute(name, "activeSessions")); That no longer works with JBoss Wildfly. I can't really find the proper documentation to access the same information with the current version of JBoss AS. I've come across some links like

问题 I would like Maven to start up a wildfly server which is available in my target-folder at /path/to/project/target/wildfly-8.1.2-Final. The plugin is supposed to deploy a war-artifact during pre-integration-test phase. That very artifact was created by maven-war-plugin during package-phase right before wildfly-maven-plugin starts. When running the maven build, wildfly starts up, however does not deploy anything. It just hangs after starting up and lets the Maven build fail after a timeout of

问题 I am migrating from glassfish 4 to wildfly 8.1 Problem is in login using security domain of Wilfly. I cannot find solution for hours. here is my standalone-full.xml security domain configuration: <security-domain name="aisRealm" cache-type="default"> <authentication> <login-module code="Database" flag="required"> <module-option name="dsJndiName" value="java:/jdbc/ais"/> <module-option name="principalsQuery" value="select password from users where email='subsoil_user'"/> <module-option name=

问题 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'm trying to implement JSF authentication with PickeLink 2.6.0 (EAR, Wildfly 8.1.0), as shown in the PicketLink 'picketlink-authentication-jsf' quickstart. I provided an authentication marked with the @PicketLink annotation, but Identity.login() always returns FAILED. This is my JSF form: <h:form> <h:panelGrid styleClass="full"> <h:inputText value="#{loginCredentials.userId}" required="true" pt:placeholder="Username" /> <h:inputSecret value="#{loginCredentials.password}" required="true" pt

问题 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

问题 In my application I got used to the following debug output: normally it prints a few lines per request to stderr, but logs a lot of information (via log4j) to a file. Typically, most important thing for me is the stderr output (that's why I want it concise), but when something doesn't work as expected, I can investigate the log, which can easily be thousands line per request. Now that I'm migrating the application to WildFly, I found that the server pipes all stderr output through its logging

问题 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=

问题 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