Can't run Eureka in JBoss EAP?

912 views
Skip to first unread message

dfo...@gmail.com

unread,
Oct 31, 2014, 5:53:38 PM10/31/14
to eureka_...@googlegroups.com
Hi,

I'm just starting to try out eureka to see if it is suitable for a project I'm working on.

Dropped the war into a fresh JBoss EAP 6.3.0 install, running as standalone.

At first I got error relating to multiple JAX-RS implementations, but googling it showed me several workarounds (see https://developer.jboss.org/message/744530). I 'solved' it by removing the references to JAX-RS in the standalone.xml.

Now I'm getting an error that is baffling me. It seems to be where blitz4j tries to register itself with the jboss log manager. Poking around in the code, the log4j-jboss-logmanager (v.1.11) is hardcoded to always throw a SecurityException when this is attempted.

Is JBoss a no-go for eureka for this reason, or have I caused the error by doing something stupid?

I built the war using gradle with jdk1.7 (had to downgrade from jdk1.8 to get it to build). I've also tried a war I got from Maven - same result, so I don't think its my build.

Thanks in advance,
Dave

Error trace:

21:36:37,493 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/eureka-server-1.1.143-SNAPSHOT]] (ServerService Thread Pool -- 49) JBWEB000287: Exception sending context initialized event to listener instance of class com.netflix.eureka.EurekaBootStrap: java.lang.RuntimeException: Cannot bootstrap eureka server :
at com.netflix.eureka.EurekaBootStrap.contextInitialized(EurekaBootStrap.java:120) [eureka-core-1.1.143-SNAPSHOT.jar:1.1.143-SNAPSHOT]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_71]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: java.lang.SecurityException: Not supported in log4j-jboss-logmanager
at org.apache.log4j.LogManager.setRepositorySelector(LogManager.java:46) [log4j-jboss-logmanager-1.1.0.Final-redhat-2.jar:1.1.0.Final-redhat-2]
at com.netflix.blitz4j.LoggingConfiguration.configure(LoggingConfiguration.java:132) [blitz4j-1.34.jar:]
at com.netflix.blitz4j.LoggingConfiguration.configure(LoggingConfiguration.java:111) [blitz4j-1.34.jar:]
at com.netflix.eureka.EurekaBootStrap.initEurekaEnvironment(EurekaBootStrap.java:129) [eureka-core-1.1.143-SNAPSHOT.jar:1.1.143-SNAPSHOT]
at com.netflix.eureka.EurekaBootStrap.contextInitialized(EurekaBootStrap.java:88) [eureka-core-1.1.143-SNAPSHOT.jar:1.1.143-SNAPSHOT]
... 11 more

21:36:37,587 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 49) JBWEB001103: Error detected during context /eureka-server-1.1.143-SNAPSHOT start, will stop it
21:36:37,637 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 49) MSC000001: Failed to start service jboss.web.deployment.default-host."/eureka-server-1.1.143-SNAPSHOT": org.jboss.msc.service.StartException in service jboss.web.deployment.default-host."/eureka-server-1.1.143-SNAPSHOT": org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:97)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_71]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:166)
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59)
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94)
... 6 more

tb...@netflix.com

unread,
Nov 3, 2014, 11:52:10 AM11/3/14
to eureka_...@googlegroups.com, dfo...@gmail.com
Hi,

I have just done eureka deployment on JBoss EAP 6.3.0, and I can only confirm the same issue you encountered. I did a quick patch to prevent blitz4j from registering with log4j, and there was another issue on the line. It looks like porting eureka to JBoss might be a bigger effort. If you think only about project evaluation, please try it with Apache Tomcat. If you find it useful, and you need it to run in JBoss EAP container, let me know. I will try to make it work there.

As a side note, we are working now on Eureka 2.0, which has a lot of new cool features, like push based model. We plan to release it end of this year. 

Regards,
Tomasz

dfo...@gmail.com

unread,
Nov 3, 2014, 12:05:52 PM11/3/14
to eureka_...@googlegroups.com, dfo...@gmail.com
Hi Tomasz,

Thanks for the reply.

JBoss (with some custom layers on top) is our corporate hosting requirement, so I don't have a lot of choice in the matter.

I'll give Tomcat a try for my evaluation. If there is anything you can do to get it working in JBoss EAP (or any pointers you can give me so I can have a go at porting it myself) that would be great.

Cheers,
Dave

jdm...@gmail.com

unread,
Feb 9, 2015, 11:13:02 AM2/9/15
to eureka_...@googlegroups.com, dfo...@gmail.com
Op vrijdag 31 oktober 2014 22:53:38 UTC+1 schreef dfo...@gmail.com:
Hi,

I currently also have the issue I need to deploy eureka on jboss and face the same issue, anyone had luck with this deployment ?

thx

Jo

kro...@gmail.com

unread,
Feb 11, 2015, 3:00:08 AM2/11/15
to eureka_...@googlegroups.com, dfo...@gmail.com, jdm...@gmail.com
Same here, Eureka doesn't seem to work on Jboss EAP 6.3
Could Eureka v2 have an impact on this issue?

Kind regards,
Andreas

Tomasz Bak

unread,
Feb 11, 2015, 11:25:55 AM2/11/15
to eureka_...@googlegroups.com, dfo...@gmail.com, jdm...@gmail.com
Eureka 2.x runs on top of RxNetty/Karyon 2.x, and it is not suitable to be deployed in J2EE container. Technically it should be possible to run it as a service in JBoss (at least in the past in JBoss 4.x, 5.x there was a concept of sar archive with generic service lifecycle management mechanism).


--
You received this message because you are subscribed to the Google Groups "eureka_netflix" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eureka_netfli...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages