[jboss-as7-dev] trying to get log4j on AS 7.1.3 working

Warner Onstine wonstine at 42six.com
Tue Apr 16 17:43:50 EDT 2013


Thanks! Will try the user forums :).

-warner


On Tue, Apr 16, 2013 at 2:41 PM, James R. Perkins <jperkins at redhat.com>wrote:

>  Ah, it's probably better to use https://community.jboss.org/en/jbossas7.
> This mailing list and that community page are more for the development of
> the application server.
>
> Is that the line it fails on? The stacktrace doesn't give much detail on
> why the log might be causing the issue. If it is indeed that line maybe
> there is a log4j configuration issue. Just a guess though.
>
>
> On 04/16/2013 02:26 PM, Warner Onstine wrote:
>
> https://community.jboss.org/en/jbossas7/dev was the page I went to,
> looking at the posts there seemed to be the correct spot to ask questions
> then saw this:
>
> ANNOUNCEMENT: IMPORTANT - AS7 DEV DISCUSSIONS NOW ON ML
>
> Hide Details
>
> Due to email notifications frequently not working, we are now using the
> jboss-as7-dev at lists.jboss.org mailing list as the primary async
> communication mechanism. You can still of course post to this forum, and we
> will try to monitor it, but it will not be as immediate as posting to the
> mailing list. Alternatively you can post to the forum here, and then post a
> reference on the mailing list to the forum.
>
>
> not setting up log4j, using it:
> LOG.info(String.format("%s startup() invoked.", className));
>
> -warner
>
> On Tue, Apr 16, 2013 at 2:20 PM, James R. Perkins <jperkins at redhat.com>
> wrote:
> >
> > What forum by chance?
> >
> > Maybe the lib directory is correct, but I thought it only loaded JAR's.
> I could be wrong though. Is the
> com.fourtwosix.razorfish.j2eeservices.RfServiceControl.startup doing
> something to setup log4j?
> >
> >
> >
> > On 04/16/2013 02:15 PM, Warner Onstine wrote:
> >
> > I went to the forum and it said to post to the mailing list, is there a
> different forum I should be using?
> >
> > And I have had it in both places same results (after having it in
> META-INF I found several posts that said to put it in the lib directory,
> including the migration guide).
> >
> > -warner
> >
> >
> > On Tue, Apr 16, 2013 at 1:50 PM, James R. Perkins <jperkins at redhat.com>
> wrote:
> >>
> >> This should really be a post on the forum, but your log4j.xml file
> should probably be in EAR/META-INF not EAR/lib.
> >>
> >>
> >> On 04/16/2013 11:57 AM, Warner Onstine wrote:
> >>
> >> I have tried multiple different ways to get my log4j working, but to no
> avail. When we were on 7.1.1 the below worked beautifully. We migrated to
> 7.1.3 (EAP 6.0.1GA) and it is no longer working and I've gone through
> several of the forum solutions as well as the migration guide but nothing
> seems to be working.
> >>
> >> Here's my current jboss-deployment-structure file:
> >> <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2">
> >>     <ear-subdeployments-isolated>false</ear-subdeployments-isolated>
> >>     <deployment>
> >>         <exclusions>
> >>             <module name="org.apache.log4j"/>
> >>         </exclusions>
> >>     </deployment>
> >>
> >>     <sub-deployment name="rf-service-ejb-0.1-SNAPSHOT.jar">
> >>         <exclusions>
> >>             <module name="org.apache.log4j"/>
> >>         </exclusions>
> >>         <dependencies>
> >>             <module name="deployment.rf-service-ear.ear.Log4j"/>
> >>         </dependencies>
> >>     </sub-deployment>
> >>
> >>     <module name="deployment.rf-service-ear.ear.Log4j">
> >>         <resources>
> >>             <resource-root path="lib/log4j-1.2.17.jar">
> >>             </resource-root>
> >>         </resources>
> >>     </module>
> >> </jboss-deployment-structure>
> >>
> >> I've tried just the basic exclusion (and nothing else). I have also
> added this to the server startup (as recommended by the migration guide):
> >> -Dorg.jboss.as.logging.per-deployment=false
> >>
> >> My current error is below
> >> 11:47:47,252 ERROR [org.jboss.msc.service.fail] (ServerService Thread
> Pool -- 95) MSC000001: Failed to start service
> jboss.deployment.subunit."rf-service-ear.ear"."rf-service-ejb-0.1-SNAPSHOT.jar".component.RfServiceControl.START:
> org.jboss.msc.service.StartException in service
> jboss.deployment.subunit."rf-service-ear.ear"."rf-service-ejb-0.1-SNAPSHOT.jar".component.RfServiceControl.START:
> java.lang.IllegalStateException: JBAS011048: Failed to construct component
> instance
> >> at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> [rt.jar:1.7.0_15]
> >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> [rt.jar:1.7.0_15]
> >> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> [rt.jar:1.7.0_15]
> >> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_15]
> >> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [rt.jar:1.7.0_15]
> >> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> >> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> >> Caused by: java.lang.IllegalStateException: JBAS011048: Failed to
> construct component instance
> >> at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:85)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:118)
> >> at
> org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:133)
> >> at
> org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> ... 7 more
> >> Caused by: javax.ejb.EJBException: JBAS014580: Unexpected Error
> >> at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:161)
> >> at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
> >> at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:331)
> >> at
> org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:57)
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> ... 11 more
> >> Caused by: java.lang.LinkageError: loader constraint violation: when
> resolving field "LOG" the class loader (instance of
> org/jboss/modules/ModuleClassLoader) of the referring class,
> com/fourtwosix/razorfish/common/j2eeservices/ServiceControlBase, and the
> class loader (instance of org/jboss/modules/ModuleClassLoader) for the
> field's resolved type, viceControlBase, have different Class objects for
> that type
> >> at
> com.fourtwosix.razorfish.j2eeservices.RfServiceControl.startup(RfServiceControl.java:32)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [rt.jar:1.7.0_15]
> >> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [rt.jar:1.7.0_15]
> >> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [rt.jar:1.7.0_15]
> >> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_15]
> >> at
> org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:130)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:73)
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.ee.component.ManagedReferenceInterceptorFactory$ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptorFactory.java:95)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> [jboss-as-ee-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> >> at
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
> [jboss-invocation-1.1.1.Final-redhat-2.jar:1.1.1.Final-redhat-2]
> >> at
> org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:226)
> >> ... 20 more
> >>
> >> Anyone have any clue what I'm doing wrong? (Oh, and I've verified that
> my log4j.xml file is in my lib directory as is the log4j-1.2.17.jar file.
> >>
> >> Thanks in advance, been beating my head against this particular rock
> for the past 2 days.
> >>
> >> -warner
> >>
> >>
> >> _______________________________________________
> >> jboss-as7-dev mailing list
> >> jboss-as7-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >>
> >>
> >> --
> >> James R. Perkins
> >> JBoss by Red Hat
> >>
> >>
> >> _______________________________________________
> >> jboss-as7-dev mailing list
> >> jboss-as7-dev at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >
> >
> >
> > --
> > James R. Perkins
> > JBoss by Red Hat
>
>
> --
> James R. Perkins
> JBoss by Red Hat
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20130416/b1d8bc8d/attachment-0001.html 


More information about the jboss-as7-dev mailing list