From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: jboss daily build failed - in cvs module: jbosstest
Date: Thu, 19 Apr 2001 09:27:39 +0100
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: jboss daily build failed - in cvs module: jbossmx
Date: Thu, 19 Apr 2001 09:28:16 +0100
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
Hi Scott,
Do you have a src/resources/naming directory in your jbosstest project that
needs to be checked in? The build of jbosstest seems to be looking for
it...
Thanks,
Chris
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: jboss daily test failed
Date: Thu, 19 Apr 2001 09:44:56
Hi,
Below is the format of the test results that I plan to publish to the
jboss-dev list each day. Basically its the results of running the
run_tests.xml script with ant against the latest jboss server.
OK?
If there are no problems, you will just get the summary.
I just need to sort out
Hi,
Did these changes;
P jboss/src/etc/conf/default/jboss.conf
P jboss/src/etc/conf/default/log4j.properties
P jboss/src/main/org/jboss/logging/Log.java
U jboss/src/main/org/jboss/logging/LogToCategory.java
P jboss/src/main/org/jboss/logging/Logger.java
P
Hi,
From: Scott M Stark [EMAIL PROTECTED]
Something is amiss with your server as these errors are all related to
the JMX connector not being bound in JNDI and I don't see this
problem. When I run the tests I am seeing the same errors as before.
Perhaps it ran during the middle of a set of
Hi,
Suite: org.jboss.test.cts.test.AllJUnitTests
Test:testRemoveSessionObject
Type:failure
Exception: junit.framework.AssertionFailedError
Message: [EJB 1.1, p42] Expected 'RemoveException',
detail:java.rmi.ServerException: RemoteException occurred in server
Hi,
Suite: org.jboss.test.cts.test.AllJUnitTests
Test:testRemoveSessionObject
Type:failure
Exception: junit.framework.AssertionFailedError
Message: [EJB 1.1, p42] Expected 'RemoveException',
detail:java.rmi.ServerException: RemoteException occurred in
Hi - I guess this is mainly for the ZOAP people.
I am setting up a daily build of various jboss modules - ie do a build
clean and then build to make sure nothing has broken.
I was looking at adding the ZOAP module to this - but to do that, I need to
make a few changes/additions - mainly because
Hi,
I've looked into the failing xa test and it is failing because the data
sources it uses are not bound.
It is looking for XADataSource1 and XADataSource2.
Is this something that needs to be manually configured in jboss.jcml before
the test ?
Thanks in advance,
Chris
...hopefully it wasn't me... ;-)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] jboss daily test results
Date: Mon, 21 May 2001 02:43:57 +0100
=
==THIS IS AN AUTOMATED EMAIL -
Hi,
Some notes on these changes:
The target directory for jbosstest results (ie the TEST-org files) is
now the directory above jbosstest! Hope this is ok - but it makes it easier
for the site that shows the results.
I've upgraded to ant-1.3 - yeah, I know its a pain to have it in all
Hi,
The problem is that I have no dependency checking between modules - so if
the core jboss build fails, then so will this build - since its dependency
is not met...
Usually this works...
I guess I could make the build stop on the first error - but then if there
are errors in a non-dependant
Hi,
Just re-ran the tests - it now compiles - but we have 17 new test failures!
Chris
JBoss daily test results
SUMMARY
Number of tests run: 71
Successful tests: 50
Errors:10
Failures: 11
Hi Jay,
Is there any documentation on how to understand the output from the test
module? I have a hard time making sense out of the output, things like
tests numbered 90-105 or something and then it'll print out 9 tests 0
failures 2 errors. What does this mean? Other than perhaps I broke
Hi,
I am sort of doing something towards this now.
The site http://lubega.com is produced by an automated
daily script that does a cvs update and then a rebuild
and test of the jboss/jbosstest code.
It only covers 1 platform/JVM - 386Linux2.2, Sun JVM
1.3.
I could fairly easily add
Hi,
--- marc fleury [EMAIL PROTECTED] wrote:
well for example in ConfigurationService
getConfiguration (use to be save()
I think) you get the XMLWriter thingy at the end and
if you go look at the
code you see that the class is 2 lines (!).
That is terrible - you should sack that guy!
I
Hi,
--- Oleg Nitz [EMAIL PROTECTED] wrote:
'jboss' module should be built first.
It is - its just that it failed...
Chris
=
Need somewhere to Live in London - http://freeflats.com
__
Do You Yahoo!?
Get personalized email addresses from
Hi,
I was reading the critique of JSR47:
http://jakarta.apache.org/log4j/docs/critique.html
and noticed this paragraph, in the Other Differences section;
Note that any third-party implementation using the java.* or
javax.* namespaces violates Sun's trademark on Java. Without explicit
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
I don't get this. When you run jbosstest/dist/bin/jmsratest.sh all
of the
tests succeed. This test only fails when it is run as part of the
full
test suite. It looks like a test that runs before this one mucks
with
something. I checked
Hi,
After Jason fixes, I couldn't resist trying for a clean run...but got
this...
JBoss daily test results
SUMMARY
Number of tests run: 104
Successful tests: 101
Errors:1
Failures: 2
User: kimptoc
Date: 01/07/06 14:32:09
Modified:src/build build.bat
Log:
ensure ANT_OPTS is used, if defined - for windoze anyway...
Revision ChangesPath
1.11 +1 -1 jboss/src/build/build.bat
Index: build.bat
User: kimptoc
Date: 01/07/07 08:32:33
Modified:src/bin jboss_init_redhat.sh
Log:
send console output to dev null
Revision ChangesPath
1.3 +1 -1 jboss/src/bin/jboss_init_redhat.sh
Index: jboss_init_redhat.sh
--- Jason Dillon [EMAIL PROTECTED] wrote:
Yep - clean of all projects, cvs up -Pd and then a build of
them
all and then the test - so its never re-run over the same tests -
but
it is always run with all tests one after the other...
Just to clarify... you `build.sh clean main` in
Hi,
Thanks for that - I've re-run them and get these results...
JBoss daily test results
SUMMARY
Number of tests run: 112
Successful tests: 111
Errors:1
Failures: 0
User: kimptoc
Date: 01/07/07 08:53:05
Modified:src/build/stylesheets summary1.xsl
Log:
added clarification
Revision ChangesPath
1.5 +1 -1 jbosstest/src/build/stylesheets/summary1.xsl
Index: summary1.xsl
--- [EMAIL PROTECTED] wrote:
JBoss daily test results
SUMMARY
Number of tests run: 112
Successful tests: 112
Errors:0
Failures: 0
Something
Hi,
--- Scott M Stark [EMAIL PROTECTED] wrote:
The test run includes less than half the current tests. Based on
the run log
it looks
like the server ran out of threads during the lock test and the
server
shutsdown
after than and all subsequent tests silently fail. What is the OS
maker
Hi,
I am re-running them to see if it works now.
All clean now...
SUMMARY
Number of tests run: 132
Successful tests: 132
Errors:0
Failures: 0
User: kimptoc
Date: 01/07/12 05:39:39
Modified:src/build/stylesheets summary2.xsl
Log:
emphasise GMT time of running...
Revision ChangesPath
1.4 +1 -1 jbosstest/src/build/stylesheets/summary2.xsl
Index: summary2.xsl
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
Huh? Why did the number of tests drop?
Good question - we did seem to hit a memory/number of sockets limit a
few weeks back - perhaps there is some variation in the tests that
means they sometimes use more resources...
Strangely, it went back
to too
many processes
on linux.
- Original Message -
From: Chris Kimpton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 23, 2001 4:24 AM
Subject: Re: [JBoss-dev] jboss daily test results
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
Huh? Why did the number
Hi,
/home/lubega/jbossro/jbosstest/src/build/run_tests.xml:112: Process
fork failed.
--- Nested Exception ---
java.io.IOException: Resource temporarily unavailable
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.init(UNIXProcess.java:139)
This
User: kimptoc
Date: 01/07/24 01:49:44
Modified:src/build run_tests.xml
Log:
added some environment info to the test report
Revision ChangesPath
1.23 +19 -1 jbosstest/src/build/run_tests.xml
Index: run_tests.xml
User: kimptoc
Date: 01/07/24 01:49:44
Modified:src/build/stylesheets summary1.xsl summary2.xsl
Log:
added some environment info to the test report
Revision ChangesPath
1.6 +9 -0 jbosstest/src/build/stylesheets/summary1.xsl
Index: summary1.xsl
User: kimptoc
Date: 01/07/24 03:33:10
Modified:src/bin run.bat run.sh
Log:
add facility pass in options to the java vm - by defining the environment variable
JAVA_OPTS
Revision ChangesPath
1.22 +1 -1 jboss/src/bin/run.bat
Index: run.bat
User: kimptoc
Date: 01/07/24 05:17:26
Modified:src/bin run.sh
Log:
added some info statements and don't try to guess HOTSPOT setting if JAVA_OPTS is
supplied
Revision ChangesPath
1.22 +13 -1 jboss/src/bin/run.sh
Index: run.sh
Hi,
I saw some info on JDepend (
http://www.clarkware.com/software/JDepend.html ) which might help
with what your trying to do...
Chris
--- Jason Dillon [EMAIL PROTECTED] wrote:
Does anyone know of a tool that can show what classes are being
used by
inspecting a source directory ?
Hi,
--- Tobias Frech [EMAIL PROTECTED] wrote:
Chris Kimpton wrote:
snip
Alternatively, there are various bugs in these jdk's/Linux
versions
that are causing problems... but I am surprised it is showing up
so
subtlely...
Any other ideas on what could be causing it?
I must
Hi,
Looking at the test results more closely:
For the IBM jdk:
The jbossmq test just seems to die.
The mdb test just dies - but with Interrupted Socket Exception errors
- perhaps it does not handle this?
The jmsra test and testEJBspec tests complete, but have Interrupted
Socket Exception
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
One of the reasons I am using the blackdown JDK is that it has a
green threads option - which I am using - which should eliminate
any
thread limit issues - but it is also showing a low count on the
tests.
What are the thread limit issues?
User: kimptoc
Date: 01/07/28 16:59:34
Modified:src/build/stylesheets summary2.xsl
Added: src/build/stylesheets details1.xsl
Log:
added an html based detail page for all tests
Revision ChangesPath
1.10 +8 -5 jbosstest/src/build/stylesheets/summary2.xsl
User: kimptoc
Date: 01/07/28 16:59:34
Modified:src/build run_tests.xml
Log:
added an html based detail page for all tests
Revision ChangesPath
1.26 +19 -1 jbosstest/src/build/run_tests.xml
Index: run_tests.xml
Hi,
There will be no more daily build/test reports mailings for a while -
this is due to a technical problem with my server - it won't boot up!
The hard disk seems to have corrupted some key boot binaries/libs.
I guess it gives me an excuse to upgrade it...
See ya,
Chris
=
Need somewhere
Hi,
--- marc fleury [EMAIL PROTECTED] wrote:
we wish you a prompt recovery :)
Well - I needed an excuse for a rebuild of the system - 2.4 here we
come
Thanks,
Chris
=
Need somewhere to Live in London - http://freeflats.com
__
Do You
Hi,
It is supposedly fixed with patch 50 (?), but its not in a released
build yet...
You can get a candidate build from here:
http://www.ee.byu.edu/~eblake/jikes/
...but this has a little bug to do with static initialisers...
I've not tried it with the JBoss source yet...
HTH,
Chris
---
has not been initialised and
so cannot be used.
So you have to recode to not use initialisers in this way... so its
impact depends on how much this feature is used...
Chris
--jason
On Wed, 15 Aug 2001, Chris Kimpton wrote:
Hi,
It is supposedly fixed with patch 50 (?), but its
Hi,
I was finally able to get the junitreport task to work. I think it
does a
better job than the previous report generator, though we might want
to
customize the defaults a little bit. I was still using
summary1.xsl to
generate the text log which can be emailed, but it complains
Hi,
When I run this, there are no messages in either the jboss server log
or the console that is doing the shutdown to indicate success or
failure.
But the shutdown process finishes and the server stays up...
Is this a known problem in the current CVS?
Regards,
Chris
=
Need somewhere to
Hi,
--- Dave Smith [EMAIL PROTECTED] wrote:
Just a heads up .. I am getting the following warnings ..
/home/dave/jboss/testsuite/src/main/org/jboss/test/testbean/test/Main.java:292:
warning: assert(java.lang.String,boolean) in junit.framework.Assert
has
been deprecated
Hi,
Well I was trying it from just the normal complete build , but If I
just
build the testsuite I get the same problem. Maybe you a different
version of junit?
Nope - just using the one that comes with jboss.
What platform are you on? I am using IBM jdk 1.3 on linux redhat 7.1?
Hi,
--- Dave Smith [EMAIL PROTECTED] wrote:
/home/dave/jboss/testsuite/src/main/org/jboss/test/testbean/test/Main.java:292:
warning: assert(java.lang.String,boolean) in junit.framework.Assert
has
been deprecated
assert(statelessMetaData != null, statelessMetaData !=
null);
User: kimptoc
Date: 01/08/30 07:48:52
Modified:bin ant
Log:
put the ant_opts at the front of the command line - allows the setting of the vm, eg
-green, which must be done as the first thing on the command line
Revision ChangesPath
1.2 +3 -1
User: kimptoc
Date: 01/08/31 03:01:18
Modified:jbossbuild.xml
Log:
added some echo info to let you know what you are using - just in case you think its
different
Revision ChangesPath
1.13 +16 -1 build/jboss/build.xml
Index: build.xml
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
User: user57
Date: 01/08/30 15:37:31
Modified:bin ant
Log:
o only showing ANT_OPTS and running jvm for help message if
$ANT_DEBUG is set.
Thanks - I only meant to have that in for my testing ;-)
I'll look at the
User: kimptoc
Date: 01/09/01 05:06:17
Modified:jbossbuild.bat
Log:
ignore users ANT_HOME setting
Revision ChangesPath
1.3 +89 -80build/jboss/build.bat
Index: build.bat
===
RCS file:
User: kimptoc
Date: 01/09/01 12:50:29
Modified:varia/src/main/org/jboss/jdo/castor CastorJDOImpl.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/cmp/bmp
CustomFindByEntitiesCommand.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:29
Modified:src/main/org/jboss/ejb/plugins/jrmp13/server
JRMPContainerInvokerHA.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/jrmp/server
JRMPContainerInvoker.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/ejb/plugins/jrmp13/server
JRMPContainerInvoker.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:28
Modified:src/main/org/jboss/ejb/plugins/jrmp/server
JRMPContainerInvokerHA.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/jaws/bmp
CustomFindByEntitiesCommand.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/ejb/plugins/local
BaseLocalContainerInvoker.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/jaws/metadata
CMPFieldMetaData.java JawsEntityMetaData.java
MappingMetaData.java TypeMappingMetaData.java
Log:
remove deprecated logging import, where
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/management ContainerManagement.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/jrmp/interfaces
SecureSocketFactory.java StatefulHandleImpl.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/proxy Proxies.java ProxyProxy.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/jrmp12/server
JRMPContainerInvoker.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/jmx/server JMXAdaptorService.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation
User: kimptoc
Date: 01/09/01 12:50:33
Modified:src/main/org/jboss/tm/usertx/server
UserTransactionSessionImpl.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is
User: kimptoc
Date: 01/09/01 12:50:33
Modified:src/main/org/jboss/util/timeout TimeoutFactory.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/logging Log.java Logger.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation message
User: kimptoc
Date: 01/09/01 12:50:31
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata
JDBCApplicationMetaData.java
JDBCMappingMetaData.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
User: kimptoc
Date: 01/09/01 12:50:32
Modified:src/main/org/jboss/metadata XmlFileLoader.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation message
User: kimptoc
Date: 01/09/01 12:50:33
Modified:src/main/org/jboss/util CounterInterceptor.java
Scheduler.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use
User: kimptoc
Date: 01/09/01 12:50:33
Modified:src/main/org/jboss/web ThreadPool.java
Log:
remove deprecated logging import, where possible, otherwise comment as needing
replacement with log4j must find out how it is use would be good if the
deprecation message pointed
Hi,
--- Scott M Stark [EMAIL PROTECTED] wrote:
Its a bug in the jikes compiler.
- Original Message -
From: Jason Dillon
To: [EMAIL PROTECTED]
Sent: Monday, August 13, 2001 7:36 PM
Subject: [JBoss-dev] VerifyError: (class: org/jboss/web/WebServer
Does anyone know why this
Hi,
I am trying to just compile the jboss code, no jars or distribution
stuff.
The compile target in the jboss-all/build directory looks like the
one for me...
...but it seems to have a different classpath setting or something as
I get errors about unresolved symbols on the javax.ejb imports
User: kimptoc
Date: 01/09/02 12:29:38
Modified:.build.xml
Log:
changes to make the testsuite email report more generic
Revision ChangesPath
1.22 +2 -2 jboss/build.xml
Index: build.xml
User: kimptoc
Date: 01/09/02 12:29:38
Modified:.build.xml
Added: .build.bat
Log:
changes to make the testsuite email report more generic
Revision ChangesPath
1.7 +2 -2 jbosstest/build.xml
Index: build.xml
User: kimptoc
Date: 01/09/02 12:29:38
Modified:jbossbuild.xml
Log:
changes to make the testsuite email report more generic
Revision ChangesPath
1.14 +20 -9 build/jboss/build.xml
Index: build.xml
User: kimptoc
Date: 01/09/02 13:57:23
Modified:.build.xml
Log:
corrected xslt to get testsuite summary working
Revision ChangesPath
1.8 +7 -2 jbosstest/build.xml
Index: build.xml
User: kimptoc
Date: 01/09/02 13:57:24
Modified:src/stylesheets summary1.xsl
Log:
corrected xslt to get testsuite summary working
Revision ChangesPath
1.2 +12 -1 jbosstest/src/stylesheets/summary1.xsl
Index: summary1.xsl
Hi,
--- Jason Dillon [EMAIL PROTECTED] wrote:
why mail over mimemail?
--jason
On Sun, 2 Sep 2001, Chris Kimpton wrote:
User: kimptoc
Date: 01/09/02 12:29:38
!-- email output to list --
-mimemail tolist=[EMAIL PROTECTED]
- subject=Automated JBoss
User: kimptoc
Date: 01/09/03 02:10:12
Modified:jbossbuild.xml
Log:
added some debug info on email sender
Revision ChangesPath
1.15 +6 -1 build/jboss/build.xml
Index: build.xml
===
User: kimptoc
Date: 01/09/03 13:21:34
Modified:.build.xml
Log:
added first cut of a custom jboss junitreport
Revision ChangesPath
1.9 +5 -2 jbosstest/build.xml
Index: build.xml
Hi,
I was planning on pulling the stylesheets out of the optional.jar,
and
adding them to src/testsuite. I would like to keep the
javadoc-like style,
but I want to make the errors stand out more (bold isn't really
that
obvious... I was going to go for white on red).
Done.
Tomorrows
Hi,
OK, but for what is the PWD search for? do you have more infor on
it? it
does not seem to search for ANT_HOME at least.
FWIW - it was finding the current working directory, so that it could
put the classes directory on the classpath as an absolute path.
There were problems before
HELP!
How come this mail got through to the list but the others I sent did
not:
I forwarded the daily test results
I copied and pasted them to a new message
I forwarded them with a new subject
I'll try shortening the message - maybe its a size limit thing?
Chris
=
Need somewhere to
User: kimptoc
Date: 01/09/04 01:45:39
Modified:.build.xml
Log:
made the text results report very short
Revision ChangesPath
1.11 +2 -2 jbosstest/build.xml
Index: build.xml
===
User: kimptoc
Date: 01/09/04 01:45:39
Added: src/stylesheets summary1a.xsl
Log:
made the text results report very short
Revision ChangesPath
1.1 jbosstest/src/stylesheets/summary1a.xsl
Index: summary1a.xsl
Hi,
From: David Jencks [EMAIL PROTECTED]
Having these tests back is wonderful but...
WHATS GOING ON?
the test script appears to be assuming every class whose name begins with
Test is a test-- does this mean I have to rewrite my tests to rename the
ejbs and mbeans that I happened to name e.g.
User: kimptoc
Date: 01/09/05 12:30:24
Modified:src/main/org/jboss/pool/connector/jdbc
JDBCManagedConnectionFactory.java
Log:
add some more info to the ManagedConnection error
Revision ChangesPath
1.4 +2 -2
Hi,
I get the following warnings on a standard build startup of jboss:
[GPA] WARNING: URL
file:/home/lubega/jbossro/jboss-all/build/output/jboss-3.0.0alpha-DEV//lib/ext/crimson.jar
could not be opened
[GPA] WARNING: URL
Hi,
I presume the jetty integration is currently in flux?
I get the following errors upon startup of a standard build server:
[DefaultDS,INFO] Initialized
[JettyService,INFO] Initializing
[Jetty,INFO] loaded properties from: jetty.properties
[Service Controller,ERROR]
Hi,
Should jbossmq be starting up in a standard build - I am getting
these errors:
[UILServerILService,INFO] Initialized
[TopicManager,INFO] Initializing
[JMSServer,DEBUG] addDestination: TOPIC.testTopic,
org.jboss.mq.server.JMSTopic@6b355423
[TopicManager,INFO] Initialized
[TopicManager,INFO]
Hi,
I am trying to run the testsuite and get this error trying to use a
sql connection:
[JDBCManagedConnectionFactory-1,ERROR] Unable to create
ManagedConnection:
javax.resource.ResourceException: Unable to create DB connection
(url=jdbc\:HypersonicSQL\:hsql\://localhost\:1476, user=sa:
User: kimptoc
Date: 01/09/07 03:26:44
Modified:src/main/org/jboss/test/lock/test EnterpriseEntityTest.java
TestSpin.java
Log:
fixed deprecation warnings
Revision ChangesPath
1.3 +2 -2
User: kimptoc
Date: 01/09/07 03:26:44
Modified:src/main/org/jboss/test/mdb/test Main.java
Log:
fixed deprecation warnings
Revision ChangesPath
1.10 +2 -2 jbosstest/src/main/org/jboss/test/mdb/test/Main.java
Index: Main.java
1 - 100 of 615 matches
Mail list logo
