wildfly

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

问题 I'm having a heck of a time getting a pooling connection manager to work for Resteasy clients. Deploying on Wildfly 8.1. import org.apache.http.client.HttpClient; import org.apache.http.impl.client.DefaultHttpClient; import org.apache.http.impl.conn.PoolingClientConnectionManager; import org.jboss.resteasy.client.jaxrs.ResteasyClient; import org.jboss.resteasy.client.jaxrs.ResteasyClientBuilder; import org.jboss.resteasy.client.jaxrs.engines.ApacheHttpClient4Engine; ...

问题 I'd like to be able to have two Wildfly (or JBoss 7) instances where one of the servers talks to EJBs on the other server. The tricky part is that according to documentation, remote-outbound-connections with outbound-socket-bindings need to be created. This is a big hassle for our Operations team, especially when we want to scale out. Is there any way for a Wildfly instance to call EJB's on another Wildfly instance by programmatically specifying the remote host? I've been able to have Tomcat

问题 I'm currently migrating our code from Jboss7 to Wildfly10. The Server itself starts up totaly fine. When trying to connect our client with the working new wildfly10 server for ejb-remote calls it just won't work. The only thing I get to work with is the following error: org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector setupEJBReceivers WARN: Could not register a EJB receiver for connection to remote-ip:8080 java.lang.RuntimeException: Operation failed with status WAITING at

问题 I'm working on preparing a program that runs on Wildfly for deployment to a customer site, and I need to change the IP address that Wildfly launches on. How do I configure Wildfly to start up at, for example, 127.0.0.2 instead of 127.0.0.1? Update I'm running Wildfly as a service on Windows. 回答1: Either you can bind the address through passing the arguments while starting the server like ./standalone.sh -c standalone-full.xml -b=127.0.0.2 https://sourcevirtues.wordpress.com/2013/12/09/set

问题 jboss-web.xml <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <security-domain flushOnSessionInvalidation="true">my-aktion </security-domain> <valve> <class-name>utils.MyAuthenticator</class-name> </valve> </jboss-web> standalone.xml <security-domain name="my-aktion" cache-type="default"> <authentication> <login-module code="utils.MyAuthenticator" flag="required"> <module-option name="dsJndiName" value="java:jboss/datasources/MySQLDS"/> <module-option name="principalsQuery" value="SELECT

问题 In my project , I use JSF+JPA+CDI+WildFly 8.2 in the persistence layer. I have a BasicDao , like this: public class BasicDao<M, K> { private org.jboss.logging.Logger logger = org.jboss.logging.Logger .getLogger("BasicDao"); @Inject @Primary protected EntityManager em; Class<M> mclass; public EntityManager getEm() { return em; } public void setEm(EntityManager em) { this.em = em; } @Transactional(value=TxType.NOT_SUPPORTED) public M find(K id){ return em.find(mclass, id); } @Transactional

问题 I am using server Wildfly version 18.0.0 and I want to color the log of my server while starting I am using Eclipse as IDE. just like tomcat server Warn, Info.... How to do that? 回答1: You can define a color map to assign a color to different log levels. The format is a comma-separated list of LEVEL:COLOR . Valid levels : finest, finer, fine, config, trace, debug, info, warning, warn, error, fatal, severe Valid colors : black, green, red, yellow, blue, magenta, cyan, white, brightblack,

问题 I am using OpenShift and WildFly 8.2.1 final to implement the new HTML5 websocket. I used this tutorial to set this project up. Whenever I open my MyTest.html, this is what the JavaScript logs: JS: Server Connected... JS: Server Disconnected... The server connects and then immediately disconnects. Why? What am I doing wrong? Is there something that I am missing? Here is mode code --> serverendpoint.java package testing; import javax.websocket.OnClose; import javax.websocket.OnError; import

问题 My project is a Wildfly 13 application which uses Mockito testing library. The app is not using Java 9 module structure. As long as the server ran on Java 8 the tests worked fine, but once we upgraded to Java 9 they failed with the following exception: org.objenesis.ObjenesisException: java.lang.ClassNotFoundException: sun.reflect.ReflectionFactory from [Module "test.war" from Service Module Loader] at test.war//org.objenesis.instantiator.sun.SunReflectionFactoryHelper