I want to get up my Development Environment from Restcomm source code, I have downloaded the source code, I have executed the maven scripts, I have downloaded the dependencies, and the eclipse projects have his libraries.
I have downloaded the Mobicents Tomcat release, I am binding the JBoss with the eclipse IDE.. because I see libs and conf are differents to JBoss default release.
I can start the Server in the Eclipse, I can see the log without errors
[0m[0m12:02:33,006 INFO [com.sun.jersey.api.core.ScanningResourceConfig] (ServerService Thread Pool -- 17) Root resource classes found:
class org.mobicents.servlet.restcomm.http.AccountsXmlEndpoint
class org.mobicents.servlet.restcomm.http.ApplicationsJsonEndpoint
class org.mobicents.servlet.restcomm.http.UssdPushJsonEndpoint
class org.mobicents.servlet.restcomm.http.LogoutEndpoint
class org.mobicents.servlet.restcomm.http.CallsJsonEndpoint
class org.mobicents.servlet.restcomm.http.CallsXmlEndpoint
class org.mobicents.servlet.restcomm.http.TranscriptionsXmlEndpoint
class org.mobicents.servlet.restcomm.http.ClientsXmlEndpoint
class org.mobicents.servlet.restcomm.http.NotificationsJsonEndpoint
class org.mobicents.servlet.restcomm.http.GatewaysJsonEndpoint
class org.mobicents.servlet.restcomm.http.SmsMessagesXmlEndpoint
class org.mobicents.servlet.restcomm.http.AvailablePhoneNumbersTollFreeJsonEndpoint
class org.mobicents.servlet.restcomm.http.IncomingPhoneNumbersXmlEndpoint
class org.mobicents.servlet.restcomm.http.AvailablePhoneNumbersJsonEndpoint
class org.mobicents.servlet.restcomm.http.AvailablePhoneNumbersXmlEndpoint
class org.mobicents.servlet.restcomm.http.SmsMessagesJsonEndpoint
class org.mobicents.servlet.restcomm.http.ClientsJsonEndpoint
class org.mobicents.servlet.restcomm.http.AvailablePhoneNumbersTollFreeXmlEndpoint
class org.mobicents.servlet.restcomm.http.UsageXmlEndpoint
class org.mobicents.servlet.restcomm.http.IncomingPhoneNumbersJsonEndpoint
class org.mobicents.servlet.restcomm.http.NotificationsXmlEndpoint
class org.mobicents.servlet.restcomm.http.TranscriptionsJsonEndpoint
class org.mobicents.servlet.restcomm.http.UssdPushXmlEndpoint
class org.mobicents.servlet.restcomm.http.OutgoingCallerIdsJsonEndpoint
class org.mobicents.servlet.restcomm.http.OutgoingCallerIdsXmlEndpoint
class org.mobicents.servlet.restcomm.http.OutboundProxyJsonEndpoint
class org.mobicents.servlet.restcomm.http.AvailablePhoneNumbersMobileXmlEndpoint
class org.mobicents.servlet.restcomm.http.RecordingsJsonEndpoint
class org.mobicents.servlet.restcomm.http.AnnouncementsJsonEndpoint
class org.mobicents.servlet.restcomm.http.OutboundProxyXmlEndpoint
class org.mobicents.servlet.restcomm.http.AccountsJsonEndpoint
class org.mobicents.servlet.restcomm.http.RecordingsXmlEndpoint
class org.mobicents.servlet.restcomm.http.GatewaysXmlEndpoint
class org.mobicents.servlet.restcomm.http.AvailablePhoneNumbersMobileJsonEndpoint
class org.mobicents.servlet.restcomm.http.AnnouncementsXmlEndpoint
class org.mobicents.servlet.restcomm.http.SupservisorJsonEndpoint
class org.mobicents.servlet.restcomm.http.ApplicationsXmlEndpoint
[0m[0m12:02:33,012 INFO [com.sun.jersey.api.core.ScanningResourceConfig] (ServerService Thread Pool -- 17) No provider classes found.
[0m[0m12:02:33,117 INFO [com.sun.jersey.server.impl.application.WebApplicationImpl] (ServerService Thread Pool -- 17) Initiating Jersey application, version 'Jersey: 1.13 06/29/2012 05:14 PM'
[0m[0m12:02:34,549 INFO [stdout] (ServerService Thread Pool -- 17) Vmaos!
[0m[0m12:02:34,669 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "restcomm.war" (runtime-name : "restcomm.war")
[0m[0m12:02:54,702 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found restcomm-management.war in deployment directory. To trigger deployment create a file called restcomm-management.war.dodeploy
[0m[0m12:02:59,725 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "restcomm-management.war" (runtime-name: "restcomm-management.war")
[0m[0m12:02:59,944 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) JBAS010403: Deploying JDBC-compliant driver class org.hsqldb.jdbc.JDBCDriver (version 2.3)
[0m[0m12:02:59,958 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /restcomm-management
But I have some questions...
First, In the restcomm.application project I found a Class Bootstrapper, But I cannot see when that class instance is created
Second, Where I can find, or Could you share me the sequence to Restcomm project entry point from JBoss AS(I can see Sip Servlet class in the server.xml, It is necesary see the Sip Servlet code also, right?)
With that I thinking that I could make a trace to understand the project.
Best Regards
Tomcat is no longer supported for Restcomm. It is best to move to JBOSS
Related
We are migrating JBOSS from 4.0.3SP1 to Wildfly 10.1.0. Our applications are bundled in separate sars which contain standard as well as Dynamic beans.
We are getting "javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository" exception caused by "java.lang.ClassNotFoundException: com.xxx.ccr.common.adapter.PEAdapterLCM". Stack Trace is added in the end. PEAdapter class is a Dynamic MBean and is present in one of the jars in the common modules under /opt/coreservices/wildfly-10.1.0.Final/modules.
We are using standalone-full.xml to start our Wildfly instance (ccr2)
[root#puiqr710dev08 CCR]# ps -eaf|grep ccr2
xxxiq 28948 7529 21 15:17 ? 00:07:10 /opt/Xxx/CCR/jre/bin/java -verbose:class -Ddss.port=31002 -DCONTAINER_UUID=14132c5860baba870160bac5d84e084a -Dlcm.host= xxx.xxxx.xxx.xxx -server -XX:NewRatio=1 -XX:+UseG1GC -XX:+UseLargePages -XX:MaxGCPauseMillis=1000 -XX:GCTimeRatio=10 -XX:+DisableExplicitGC -Dsun.nio.ch.disableSystemWideOverlappingFileLockCheck=true -Ddss.thread_pool_size=24 -Xss250k -Xms256m -Xmx4096m -DUSE_DELAY1=60000 -DUSE_DELAY2=60000 -Dlog4j.configuration=file:/opt/Xxx/CCR/appserver/jboss-boot.log4j.properties -DLOG_FILE_PREFIX=DataProcessingJBoss_puiqdevdads07 -Ddss.message_lifetime=180 -Djava.awt.headless=true -Dorg.jboss.logging.Log4jService.catchSystemErr=false -classpath /opt/Xxx/CCR/jre/lib/tools.jar -jar /opt/coreservices/wildfly-10.1.0.Final/jboss-modules.jar -mp /opt/coreservices/wildfly-10.1.0.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/opt/coreservices/wildfly-10.1.0.Final -Djboss.server.base.dir=/opt/coreservices/wildfly-10.1.0.Final/ccr2 -Djboss.bind.address=xxx.xxxx.xxx.xxx -Djboss.bind.address.management= xxx.xxxx.xxx.xxx -c standalone-full.xml
· We have four sars that are deployed in this instance. All sars are deployed successfully.
· We have packaged our sars as follows:
--lib (contains all jars)
--META-INF
|--jboss-deployment-structure.xml
|--jboss-service.xml
· Each sar contains some standard MBeans and few Dynamic MBeans.
· We have defined standard MBeans in jboss-services.xml. They are created properly and can be seen in JConsole.
· We can NOT include definition of Dynamic MBeans in jboss-service.xml as their name is constructed at runtime.
· PEAdapterLCM for which we are getting ClassNotFoundException is a dynamic bean and we are getting this error for all Dynamic MBeans.
· We have created modules for all common jars that were part of “server/lib” folder in JBOSS 4.0.3SP1.
We tried following to fix this error but no luck:
1) packaged contents of all sars in one single sar and deployed it.
2) Added a global module entry in standalone-full.xml which contents dynamic MBeans.
3) Added definition of dynamic MBean in jboss-service.xml (just to see if this makes any difference). With this change, we were able to see the MBean in JConsole. But still got the same error.
So what should be done to fix this error. Are there any changes - how to implement and deploy Dynamic MBeans in Wildfly?
Is there any way in Wildfly we can explicitly mention the MBean server class while starting the Wildfly as it was done in JBOSS 4.0.3SP1 using "-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Djboss.platform.mbeanserver -Dcom.sun.management.jmxremote"
Here is complete stack trace:
^[[0m^[[31m15:01:30,324 ERROR [com.xxx.coreservice.lifecycle.jmx.PEController] (MSC service thread 1-6) Exception in PEController:PEControllerJmxJBossService start for peID 14132c58609742440160974fe69307e0: : javax.management.ReflectionException: The MBean class could not be loaded by the default loader repository
at com.sun.jmx.mbeanserver.MBeanInstantiator.findClassWithDefaultLoaderRepository(MBeanInstantiator.java:104)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.createMBean(DefaultMBeanServerInterceptor.java:268)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.createMBean(DefaultMBeanServerInterceptor.java:206)
at com.sun.jmx.mbeanserver.JmxMBeanServer.createMBean(JmxMBeanServer.java:326)
at com.avaya.lifecycle.jmx.agent.PEControllerJmx._start(PEControllerJmx.java:55)
at com.xxx.coreservice.lifecycle.jmx.PEController.start(PEController.java:397)
at com.xxx.coreservice.lifecycle.jmx.PEController.startAll(PEController.java:314)
at com.xxx.coreservice.lifecycle.jmx.PEController.startup(PEController.java:238)
at com.xxx.coreservice.lifecycle.jmx.PEController.postRegister(PEController.java:700)
at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:182)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegister(DefaultMBeanServerInterceptor.java:1024)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:974)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:1527)
at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:871)
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:101)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: com.xxx.ccr.common.adapter.PEAdapterLCM
at com.sun.jmx.mbeanserver.ClassLoaderRepositorySupport.loadClass(ClassLoaderRepositorySupport.java:232)
Thanks for help in advance.
I'm trying to launch Apache Twill application from hadoop cluster, the cluster is recently upgraded from HDP 2.2 to HDP 2.5 but I'm getting llegalAccessError for RequestHedgingRMFailoverProxyProvider class . This class is part of org.apache.hadoop.yarn.client package. I'm getting this error in the Application Master. The job status goes directy to 'not running state' right after 'accepted state'.
Exception in thread "Hadoop22YarnAMClient STARTING" Exception in thread "YarnAMClientService STARTING" java.lang.IllegalAccessError: tried to access method org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider.getProxyInternal()Ljava/lang/Object; from class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
at org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider.init(RequestHedgingRMFailoverProxyProvider.java:75)
at org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:163)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.serviceStart(AMRMClientImpl.java:186)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at org.apache.twill.internal.yarn.Hadoop21YarnAMClient.startUp(Hadoop21YarnAMClient.java:77)
at com.google.common.util.concurrent.AbstractIdleService$1$1.run(AbstractIdleService.java:43)
at java.lang.Thread.run(Thread.java:745)
com.google.common.util.concurrent.ExecutionError: java.lang.IllegalAccessError: tried to access method org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider.getProxyInternal()Ljava/lang/Object; from class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
at com.google.common.util.concurrent.Futures.wrapAndThrowUnchecked(Futures.java:1008)
at com.google.common.util.concurrent.Futures.getUnchecked(Futures.java:1001)
at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:220)
at com.google.common.util.concurrent.AbstractIdleService.startAndWait(AbstractIdleService.java:106)
at org.apache.twill.internal.appmaster.ApplicationMasterMain$YarnAMClientService.startUp(ApplicationMasterMain.java:221)
at com.google.common.util.concurrent.AbstractIdleService$1$1.run(AbstractIdleService.java:43)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalAccessError: tried to access method org.apache.hadoop.yarn.client.ConfiguredRMFailoverProxyProvider.getProxyInternal()Ljava/lang/Object; from class org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider
at org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider.init(RequestHedgingRMFailoverProxyProvider.java:75)
at org.apache.hadoop.yarn.client.RMProxy.createRMFailoverProxyProvider(RMProxy.java:163)
at org.apache.hadoop.yarn.client.RMProxy.createRMProxy(RMProxy.java:93)
at org.apache.hadoop.yarn.client.ClientRMProxy.createRMProxy(ClientRMProxy.java:72)
at org.apache.hadoop.yarn.client.api.impl.AMRMClientImpl.serviceStart(AMRMClientImpl.java:186)
at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at org.apache.twill.internal.yarn.Hadoop21YarnAMClient.startUp(Hadoop21YarnAMClient.java:77)
... 2 more
In general when you see IllegalAccessError this means you have a runtime incompatibility between compiled and runtime code. In this case,
the getProxyInternal() method of ConfiguredRMFailoverProxyProvider is now private. You need to recompile your client code and/or use updated hadoop client libraries to connect to your cluster.
I am using WebLogic 11g. I am using Eclipse. I have created a EJB project. This project is called 'remote-ejb'.
The bean class HelloWorldBean implements a remote interface HelloWorldBeanRemote with just on method; public String getName();
I then deployed this project as an application successfully.
I then created a second EJB project called cart-ejb. This project uses the bean from the first project. When I deploy this
project I get the following error:
Module named 'cart-ejb' failed to deploy. See Error Log view for more detail.
weblogic.application.ModuleException: java.lang.ClassNotFoundException: beans.HelloWorldBeanRemote
Exception received from deployment driver. See Error Log view for more detail.
How can I fix this error?
I am having a problem with deploying my application on JBoss AS 7.1. Here is what happened, we have a project that has been build on JDK 1.4 currently running on JRun 4. We are migrating the project to JDK 1.7 and deploy on JBoss AS 7.1.1.
Made required changes to the project compile in eclipse using JDK 1.7 like "enum", changed implementation of Log4j, etc. However the current project heavily relies on jaxb ver 1.0 implementation (which we would make changes over a period of time to the latest jaxb version and convert the project to web services).
However when I try to deploy the same project in JBoss I get an error as below, any help to get this resolved would be really appreciated.
12:39:55,710 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "presto.war"
12:40:00,590 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/xerces-1.2.3.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,591 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/xalan-2.0.0.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,593 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/xalanj1compat.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,595 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/batik.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,596 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/jimi-1.0.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,598 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/logkit-1.0b4.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,599 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry lib/avalon-framework-4.0.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/fop.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,611 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jaxp.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,612 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry crimson.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/xalan.jar" does not point to a valid jar for a Class-Path reference.
12:40:00,617 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry sax.jar in "/C:/jboss-as-7.1.1.Final/standalone/deployments/presto.war/WEB-INF/lib/xt.jar" does not point to a valid jar for a Class-Path reference.
12:40:01,495 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.deployment.unit."presto.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."presto.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "presto.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.RuntimeException: Error getting reflective information for class org.apache.taglibs.xtags.xslt.XalanStyleTag with ClassLoader ModuleClassLoader for Module "deployment.presto.war:main" from Service Module Loader
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.lang.NoClassDefFoundError: Lorg/apache/xalan/xslt/XSLTResultTarget;
at java.lang.Class.getDeclaredFields0(Native Method) [rt.jar:1.7.0_51]
at java.lang.Class.privateGetDeclaredFields(Class.java:2397) [rt.jar:1.7.0_51]
at java.lang.Class.getDeclaredFields(Class.java:1806) [rt.jar:1.7.0_51]
at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 10 more
Caused by: java.lang.ClassNotFoundException: org.apache.xalan.xslt.XSLTResultTarget from [Module "deployment.presto.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
... 15 more
From the error stack you can see that:
Caused by: java.lang.ClassNotFoundException: org.apache.xalan.xslt.XSLTResultTarget from [Module "deployment.presto.war:main" from Service Module Loader]
So the class jar file getting loaded is from default JBOSS Modules and clearly the xalan.jar that comes with the JBoss 7(jboss-as-7.1.1.Final\modules\org\apache\xalan\main) does not contain that that class:
You need to either start using the jar file that your application refers to by replacing it with this jar(which is not reccomended) or use jboss-deployment-structure.xml to do so. This link could help you to decide what works best for you
My question is more related to "Force Jboss logging to use of SLF4J" but couldn't find more details in it so i am posting it here again. How to make slf4j work, if one of my class calls for slf4j i get the below error. Since jboss 7.1.1 already have slf4j module, what else i need add to make it work.
20:20:31,565 ERROR [stderr] (MSC service thread 1-8) SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
20:20:31,572 ERROR [stderr] (MSC service thread 1-8) SLF4J: Defaulting to no-operation (NOP) logger implementation
20:20:31,578 ERROR [stderr] (MSC service thread 1-8) SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
There is no need to force anything. slf4j is a logging facade. JBoss AS provides a bridge between slf4j and the JBoss Log Manager. All you need to do to get it to work is
Make sure you don't include the slf4j API library in your deployment
Also make sure you don't include an slf4j bridge in your deployment
Other than those two things there souldn't be anything else to do.