November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBESB-21) Registry service interface

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-21?page=all ] Mark Little closed JBESB-21. ---------------------------- > Registry service interface > -------------------------- > > Key: JBESB-21 > URL: http://jira.jboss.com/jira/browse/JBESB-21 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Registry > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.0 > > > We need a registry. It cannot be WS specific, but JAX-R looks like it still matches. Check out what is available in JBossWS (or elsewhere). Assuming we go the JAX-R route (discuss on forum please), then we need stand-alone JAX-R support and a plugin. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-171) Integrate Registry with services and clients

by Mark Little (JIRA)

Integrate Registry with services and clients -------------------------------------------- Key: JBESB-171 URL: http://jira.jboss.com/jira/browse/JBESB-171 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Registry Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.0 Once the registry support goes into the ESB, we need to look at integrating it within the ESB and how to present it to users. Hopefully a lot of the static configuration information we currently have can be replaced with calls to the registry to obtain EPRs that contain the same information, but in a more dynamic way. -- 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

18 years, 11 months

2
4
0 / 0

[JBoss JIRA] Commented: (JBESB-55) Nightly builds of unit tests

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-55?page=comments#action_12346079 ] Mark Little commented on JBESB-55: ---------------------------------- We'll use Continuum for now as it provides what we need and is freely available to everyone. > Nightly builds of unit tests > ---------------------------- > > Key: JBESB-55 > URL: http://jira.jboss.com/jira/browse/JBESB-55 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assigned To: Kevin Conner > Priority: Critical > Fix For: 4.0 RC1 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3272) update JBossRemoting to version 2.0.0

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3272?page=all ] Dimitris Andreadis updated JBAS-3272: ------------------------------------- Priority: Critical (was: Major) Just raising the priority so it's included in the next release. > update JBossRemoting to version 2.0.0 > ------------------------------------- > > Key: JBAS-3272 > URL: http://jira.jboss.com/jira/browse/JBAS-3272 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Remoting > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Critical > Fix For: JBossAS-4.0.6.CR1 > > > Need to update JBossAS to include jboss-remoting.jar for version 2.0.0.GA of JBossRemoting. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-348) Automate test run against all supported databases

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-348: ------------------------------------- We should also ensure all tests are run on multi processor machines to ensure we catch multiprocessor specific race conditions. > Automate test run against all supported databases > ------------------------------------------------- > > Key: JBMESSAGING-348 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Richard Achmatowicz > Fix For: 1.2.0.CR1 > > > The test suite should be run continuously against all databases we supply a configuration for. > Initially this should be: > Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-265) Soak tests

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-265?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-265: ------------------------------------- Need to ensure tests are run on machine with multiple processors. > Soak tests > ---------- > > Key: JBMESSAGING-265 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-265 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Fix For: 1.2.0.CR1 > > > A test that runs long enough and sends a significant number of messages into the server; used to detect memory leaks and failure under load -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-621) Modify the smoke test suite to run tests in top of JBoss 4.0.5.GA instead of 4.0.5.CR1

by Ovidiu Feodorov (JIRA)

Modify the smoke test suite to run tests in top of JBoss 4.0.5.GA instead of 4.0.5.CR1 -------------------------------------------------------------------------------------- Key: JBMESSAGING-621 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-621 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Tim Fox Fix For: 1.2.0.Alpha2 -- 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

18 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-583) Add an integer check for release-admin.xml's -Did=...

by Ovidiu Feodorov (JIRA)

Add an integer check for release-admin.xml's -Did=... ----------------------------------------------------- Key: JBMESSAGING-583 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-583 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Trivial Fix For: 1.2.0.Alpha2 -- 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

18 years, 11 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JGRP-251) Release JGroups 2.4

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-251?page=all ] Bela Ban resolved JGRP-251. --------------------------- Resolution: Done > Release JGroups 2.4 > ------------------- > > Key: JGRP-251 > URL: http://jira.jboss.com/jira/browse/JGRP-251 > Project: JGroups > Issue Type: Release > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.4 > > -- 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

18 years, 11 months

1
0
0 / 0

[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

18 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006