jboss

问题 My problem is that I have a web service that gets published by jboss at http://localhost:8080/A , where A is the service implementation class; I want a custom url http://localhost:8080/B/C/D.ws . In the wsdl, soap:address is correctly set http://localhost:8080/B/C/D.ws . During war deployment, service gets published at the "wrong" address: INFO [org.jboss.ws.cxf.metadata] Adding service endpoint metadata: id=org.example.ServiceImpl address=http://localhost:8080/ServiceImpl ... The best I got

问题 We've been debugging this JBoss server problem for quite a while. After about 10 hours of work, the server goes into 100% CPU panic attacks and just stalls. During this time you cannot run any new programs, so you can't even kill -quit to get a stack trace. These high 100% SYS CPU loads last 10-20 seconds and repeat every few minutes. We have been working on for quite a while. We suspect it has something to do with the GC, but cannot confirm it with a smaller program. We are running on i386

问题 I use Jboss 6 and my static Logger logger = Logger.getLogger(Foo.class); displays nothing Tried adding log4 to my project, removing it, placing a log4j file on my main/resources folder, placing no log4j file and no results. Only System.Out seems to work, but it doesn't provide all the information I would like to see I even see Hibernate log working but not mine What am I missing? 回答1: Turns out my logging does work. Hibernate logging is controlled by the jboss logging settings. My logging

问题 I'm wondering why ejb injection into JAX-RS resource (RestEasy on JBoss7) is not working. EJBs are not part of war but its own EJB jar but I supposed this should not be the problem. I'm forced to do the ctx.lookups "workaround", which are not pretty. Am I missing something or it is really not supported to inject EJB like that? Example below does not work with JBoss, but works with Glassfish (sadly I gotta run my application on JBoss) Path("x") @RequestScoped public class UserResource {

问题 I want to generate a wadl file for my project which is using resteasy + Jboss 6.4 + Maven. There are many examples given for jersey but not for resteasy does anyone used it for resteasy 回答1: Resteasy since 3.0.14.Final do support WADL generation. You need to add resteasy-wadl to your dependency manager (e.g. maven): <dependency> <groupId>org.jboss.resteasy</groupId> <artifactId>resteasy-wadl</artifactId> <version>3.0.19.Final</version> </dependency> then declare a new servlet endpoint in your

问题 Just recently I was creating new maven project on new computer and it seams that the dependency for jboss as client isn't available anymore: <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-client</artifactId> <version>5.1.0.GA</version> <type>pom</type> <scope>provided</scope> </dependency> And the repository resource is: <repositories> <repository> <id>jboss-maven2</id> <url>http://repository.jboss.com/maven2</url> </repository> </repositories> Is there any new

问题 I've developed applications (running on Jboss server) with two different teams. One team had datasource configuration inside of the application WAR file and another one had it inside of the application server's standalone.xml. And I'm not sure which approach is better. So, here are some advantages that I've found in defining datasource inside of the server's standalone.xml. Defining datasource in server's standalone.xml is more secure than in war file. If the database connection credentials

问题 I'm using form based authentication. I have a logout link which looks like: <h:commandLink action="#{loginBean.logout}"> <h:outputText value="logout" /> </h:commandLink></div> And the corresponding logout method: public String logout() { FacesContext.getCurrentInstance().getExternalContext().invalidateSession(); return "/view/index?faces-redirect=true"; // Redirect added as per BalusC's suggestion. } After hitting the logout link I'm returned to the front page, but seemingly without CSS. When

问题 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´ve a webapplication wich uses JPA persistence unter wildfly 8.2. The persistence.xml is connected to <jta-data-source>java:/jdbc/myDS</jta-data-source> wich generally works fine. BUT if I start the JBoss-Server before the Database-Server is ready, the web application doen´t get deployed with the following error: BAS011411: Unexpected problem gathering statistics: java.lang.IllegalStateException: JBAS011477: Persistence unit 'my.war#myPU' is not available My wish is that the application DOES