wildfly-8

Can't get Remote EJB to work with EJB Client API on Wildfly

旧城冷巷雨未停 提交于 2019-12-23 01:36:22
问题 I'm currently struggling with getting remote EJB invocation to work on wildfly (8.x and 9.x). In detail it's about remote invocation from a standalone client application (not from another app server) using the EJB Client API approach. The remote naming approach works for me but isn't applicable in my scenario because I need to use client-side interceptors for passing context data to a server-side interceptor for the remote invocations. But for now I try to get remote invocations with the

@Remote JNDI Communication: Wildfly to JBoss AS 5.1.0.GA

只愿长相守 提交于 2019-12-21 21:03:31
问题 Architecture: Windows Client -> Wildfly JAX-RS Services -> JBoss 5.1.0.GA legacy system. I am getting a java.lang.ClassCastException: javax.naming.Reference cannot be cast to com.interfaces.GroupBookingManagerRemote when communicating here between Wildfly JAX-RS Services and JBoss 5.1.0.GA legacy system. As I am communicating from Wildfly to JBoss AS 5.1.0.GA I am attempting to connect using JNDI. In my Wildfly Server Maven pom I include: <dependency> <groupId>jboss</groupId> <artifactId>jnp

Difference between security-realm and security-domain in WildFly

混江龙づ霸主 提交于 2019-12-20 10:44:04
问题 What is the main difference between security-domain and security-realm in WildFly? standalone.xml <security-domain name="foo"> <authentication> <login-module code="..." flag="..."> </login-module> </authentication> </security-domain> and <security-realm name="foo"> <authentication> <local default-user="..." allowed-users="..." skip-group-loading="..."/> <properties path="..." relative-to="..."/> </authentication> <authorization> <properties path="..." relative-to="..."/> </authorization> <

UserTransaction: javax.naming.NameNotFoundException after Migration to WildFly 8.2.0 and Java 8

别说谁变了你拦得住时间么 提交于 2019-12-20 04:12:39
问题 After migrating to Java 8 and WildFly 8.2.0 I get this error on every Transaction UserTransaction: javax.naming.NameNotFoundException: UserTransaction [Root exception is java.lang.IllegalStateException: JBAS014237: Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction] at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:140) at org.jboss.as.naming.ServiceBasedNamingStore.lookup

Wildfly to Wildfly EJB client without remote-outbound-connections

五迷三道 提交于 2019-12-19 10:47:13
问题 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

Hosting Static Content and JAX-RS Services Under the Same Root Context

心已入冬 提交于 2019-12-19 03:18:07
问题 We have multiple Java web apps packaged as WARs all packaged in an EAR. Our RESTful services are built using JAX-RS and in version specific WARs. We'd like to add static content for each of these version specific WARs, but use the root context (of the WAR) for both the static content and the RESTful service API calls, such that all of the following URLs will work: {hostname}/v1/swagger.yaml <-- Static Content describing the v1 API {hostname}/v1/orders/{uid} <-- JAX-RS RESTful API (v1)

How to access CXF jars from Wildfly (Jboss) for ws endpoints

守給你的承諾、 提交于 2019-12-19 02:54:16
问题 I've tried to deploy my war file in Wildfly 8.2. My application uses org.apache.cxf for web service. But Wildfly (Jboss) comes by default with its own cxf jars which can be provide full Java EE support. I could eliminate jboss cxf and utilise my own cxf jars for web services by jboss-deployment-structure.xml <jboss-deployment-structure> <deployment> <exclude-subsystems> <subsystem name="webservices" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> But it'll disable ws

BouncyCastle 1.51 loading in war on Wildfly 8.0

旧街凉风 提交于 2019-12-18 15:17:40
问题 Background I am trying to use bouncy castle library to decrypt private keys in my war. Now I tested the code first in a standalone app and it worked fine. Now when I am testing it as a webapp in Wildfly8.0 am facing some issues with Bouncy castle. The Wildfly 8.0 am using has bouncy castle provider module installed. The BC version being used in v1.46. The code that I have developed uses v1.51. I have followed the steps mentioned here: https://developer.jboss.org/thread/175395 bouncycastle +

Database connections not closed after idle-timeout in wildfly Datasource

十年热恋 提交于 2019-12-18 05:49:09
问题 I have an application running under wildfly 8.1 The database connections used in the applications are taken from a Datasource defined in standalone.xml file. Problem: I don't know why but the Connection from the Pool never goes Idle and are released. Eventually the Pool gets filled will all active Connection and application starts throwing javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/bo/datasource At the same time when I look at the database, most of

Wildfly fails to deploy application (FileNotFoundException - Access is Denied)

僤鯓⒐⒋嵵緔 提交于 2019-12-18 05:46:11
问题 Wildfly 8.2.0.Final JDK 8 Update 60 Eclipse Mars Update 1 JBoss Tools 4.3.0.Final Windows 10 Recently I upgraded the following things: from Windows 7 to Windows 10 from Eclipse Mars to Eclipse Mars Update 1 from JBoss Tools 4.3.0.Beta1 to JBoss Tools 4.3.0.Final and now when I try to deploy my application in Eclipse it doesn't work anymore (sometimes it works, but most of the time it doesn't work). Everything was working fine before the upgrades, but now I get this stack trace when I deploy