[JBoss JIRA] Commented: (JBAS-3348) Patch for JBAS-3347, %C log4j format problem
by Jaroslaw Kijanowski (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3348?page=comments#action_12346061 ]
Jaroslaw Kijanowski commented on JBAS-3348:
-------------------------------------------
I've checked out
http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_0_4_GA/
and
http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_0_4_GA_CP01/
[jkijanowski@dev02 testsuite]$ ./build.sh one-test -Dtest=org.jboss.test.classloader.test.ScopingUnitTestCase
Searching for build.xml ...
Buildfile: /home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/build.xml
Overriding previous definition of reference to xdoclet.task.classpath
one-test:
[delete] Deleting: /home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/output/log/test.log
[junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 3.201 sec
After copying the new commons-logging.jar to
build/output/jboss-4.0.4.GA_CP01/server/all/lib/
build/output/jboss-4.0.4.GA_CP01/server/default/lib/
build/output/jboss-4.0.4.GA_CP01/client
I get following result:
[jkijanowski@dev02 testsuite]$ ./build.sh one-test -Dtest=org.jboss.test.classloader.test.ScopingUnitTestCase
Searching for build.xml ...
Buildfile: /home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/build.xml
Overriding previous definition of reference to xdoclet.task.classpath
one-test:
[delete] Deleting: /home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/output/log/test.log
[junit] Running org.jboss.test.classloader.test.ScopingUnitTestCase
[junit] Tests run: 7, Failures: 0, Errors: 1, Time elapsed: 3.106 sec
[junit] Test org.jboss.test.classloader.test.ScopingUnitTestCase FAILED
Same for 4.0.4.GA.
server.log:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
21:20:03,021 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA_CP01 (build: CVSTag=https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_4_GA_CP01 date=20061031202
8)] Started in 27s:101ms
21:20:15,811 INFO [TomcatDeployer] deploy, ctxPath=/log4j113, warUrl=.../tmp/deploy/tmp36774log4j113-exp.war/
21:20:15,906 ERROR [BaseModelMBean] Exception invoking method addChild
org.apache.commons.logging.LogConfigurationException: java.lang.reflect.UndeclaredThrowableException (Caused by java.lang.reflect.UndeclaredThrowableException
)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:538)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:372)
at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:380)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4090)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
test.log:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.
.
.
21:20:15,655 DEBUG [ScopingUnitTestCase] /home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/output/lib/log4j113.war is a valid file
21:20:15,655 DEBUG [ScopingUnitTestCase] Deploying log4j113.war, url=file:/home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/output/lib/log4j113.war
21:20:15,664 DEBUG [ScopingUnitTestCase] Invoking jboss.system:service=MainDeployer method=deploy
21:20:15,664 DEBUG [ScopingUnitTestCase] args=[file:/home/jkijanowski/JBAS-3348/JBoss_4_0_4_GA_CP01/testsuite/output/lib/log4j113.war]
21:20:16,038 ERROR [ScopingUnitTestCase] MbeanException
21:20:16,044 DEBUG [NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
21:20:16,048 DEBUG [NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
21:20:16,048 DEBUG [NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (RuntimeOperationsException: Exception invoking method init Cause: org.apache.commons.logging.LogConfigurationException: java.lang.reflect.UndeclaredThrowableException (Caused by java.lang.reflect.UndeclaredThrowableException))
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:380)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Patch for JBAS-3347, %C log4j format problem
> --------------------------------------------
>
> Key: JBAS-3348
> URL: http://jira.jboss.com/jira/browse/JBAS-3348
> Project: JBoss Application Server
> Issue Type: Support Patch
> Security Level: Public(Everyone can see)
> Components: Logging
> Affects Versions: JBossAS-4.0.4.GA
> Reporter: Scott M Stark
> Assigned To: Jaroslaw Kijanowski
> Attachments: commons-logging.jar
>
>
> The %C classname format of the log4j pattern layout was broke by the 1.0.5.GA-jboss commons-logging release because the Log4jProxy was not using a FQCN that allowed the log4j LayoutInfo to find the caller. This has been corrected in the 1.0.5.SP1-jboss commons-logging release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month
- 1
- 0
[JBoss JIRA] Created: (JBCACHE-821) Update docs to reflect new version
by Manik Surtani (JIRA)
Update docs to reflect new version
----------------------------------
Key: JBCACHE-821
URL: http://jira.jboss.com/jira/browse/JBCACHE-821
Project: JBoss Cache
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Manik Surtani
Assigned To: Manik Surtani
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month
- 1
- 1
[JBoss JIRA] Updated: (JBMESSAGING-207) HTTP invoker configuration and testing
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-207?page=all ]
Ovidiu Feodorov updated JBMESSAGING-207:
----------------------------------------
Fix Version/s: 1.2.0.Beta1
(was: 1.2.0.Alpha2)
> HTTP invoker configuration and testing
> --------------------------------------
>
> Key: JBMESSAGING-207
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-207
> Project: JBoss Messaging
> Issue Type: Task
> Components: Configuration and Management
> Reporter: Ovidiu Feodorov
> Assigned To: Ron Sigal
> Priority: Blocker
> Fix For: 1.2.0.Beta1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Provide a HTTP invoker initial configuration and a working example.
> Add the example to docs/examples so it can be used as an integration test.
> Reviewed requirements:
> 1. The messaging client needs to connect to the server over HTTP
> 2. We need it implemented in such a way that there's no socket listening on the client, but the client can still receive messages asynchronously.
> 3. When the change is completed, all current Messaging functional tests, stress tests and smoke test must pass.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 1 month
- 1
- 0