Yup, it does work... mostly. Did you get any of the email that I sent to
you about the security tests?
I think there might be some config or file placement issues. I had to
change the way several jar files were being created to avoid having one jar
build be dependent on the jar build before it
The testsuite is expecting that a number of packages have been built but it
is not validating that they have. This is the source of the numerous errors.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: Scott M Stark [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday,
'testsuite' does not build anything, it simply runs the jboss/testsuite
'tests' target. Too build everything, then run the testsuite, use most,
main or all as the target to execute before testsuite.
./build.sh most testsuite
'all' will simply make docs too, which aren't very useful for
This electronic message (email) and any attachments to it are subject to copyright and
are sent for the personal attention of the addressee. Although you may be the named
recipient, it may become
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
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 04 September 2001 08:53
To: [EMAIL PROTECTED]
Subject: Automated JBoss Testsuite Results
JBoss daily test results
SUMMARY
Number of tests run: 82
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
JBoss daily test results
SUMMARY
Number of tests run: 82
Successful tests: 15
Errors:36
Failures: 31
[time of test: 4 September 2001 9:49 GMT]
[java.version:
Hi
the RMIClientConnectorImpl in org.jboss.jmx.client has a few
printStackTrace calls in it. Done in the invoke() method for example if a
RemoteException is caught. Null is returned (which I'm testing for) but the
stack trace on the Together ControlCenter console looks really messy. Could
I already reported that I want to cancel my entry in the mail list
[EMAIL PROTECTED]
I already reported several times with the procedure described below that I
want to unsuscribe my entry in the mailing list.
[EMAIL
|I think we have a problem with RH and jbossmq. With the advent of Marc's
|changes the order in which the mbeans are initialised and started seems to
|have changed. Previously all mbeans listed in the jboss.jcml file where
|initialised before any where started. This meant that when the
|The problem with both of the above appraches - is who calls start?
|In Jetty - everything implements the lifecycle interface, so it has
|start and stop methods. If you call start on HttpServer, it calls
|start on all the components within it. So you don't really want
|a config agent calling
|A JNDI env for each service along with well known entries for resources
|like JMS and the local filesystem seems like the best approach. I don't see
|locating
|the JBoss server filesystem as any different than locating a JMS queue:
|
|File root = (File) new
julian...
is this the same problem you see with the RH base?
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Torsten Terp
|Sent: Tuesday, September 04, 2001 4:28 AM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-user] JBoss-2.4.0_Jetty-3.1.RC8-1
same symptom...
But I'm not prepared to say same problem - yet
because the JBoss/Jetty that this guy is using works
for me, but RH doesn't.
Jules
--- marc fleury [EMAIL PROTECTED] wrote:
julian...
is this the same problem you see with the RH base?
marcf
|-Original
User: jayeshpk
Date: 01/09/04 08:06:51
Modified:src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
Log:
Added a constructor
Revision ChangesPath
1.7 +22 -16jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java
Index: PersistenceManager.java
User: jayeshpk
Date: 01/09/04 08:05:16
Modified:src/main/org/jboss/mq/pm/jdbc MessageLog.java
Log:
Changed MessageLog constructor
Revision ChangesPath
1.4 +10 -9 jbossmq/src/main/org/jboss/mq/pm/jdbc/MessageLog.java
Index: MessageLog.java
Ok..if this is the wrong list, I apologize. I am setting up JBoss on one
computer, and using Orion (for now) on another for the web tier. I want my
web tier to access an EJB deployed on JBoss on the other computer (typical
two tier). I gotta say JBoss developers, I am impressed how simple it was
Comments below...
Got it now ... but it is still not seeing eye to eye ... comments below ..
Dain Sundstrom wrote:
Dave,
We still don't see eye-to-eye, and I think I made the problem worse with
my
example.
I think the most common type of relationship will be something like 'a
cd
User: user57
Date: 01/09/04 12:35:52
Modified:.build.xml
Log:
o removed extra ''
Revision ChangesPath
1.20 +2 -2 manual/build.xml
Index: build.xml
===
RCS file:
OK, it seems the situation is much as I thought.
I will try to explain the problem a bit and then propose a solution.
Basically the persistence manager, when it is started, needs to restore from
its persistent store any messages that were left from the last run of the MQ
service. For it to be
Rework for the list.
Basically my take is that making the init/start scope go to the XML snippet
is not an issue just requires some basic changes to the ServiceDeployer and
the ServiceController. David take it away.
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL
1- We provide for the SAR directory in a jar approach. I find this kind of
elegant actually. We provide a way for a service to deploy to a target
node, install his own stuff in a directory for the duration of work and then
clean up. Jason request.
I assume this means unjar the .sar into
OK, I will have a look at this and packaging JBossMQ into a jsr file to get
it all working (at the moment it is seriously broken, no messages are
restored from backup at all).
I think though that there are advantages to refactoring JBossMQ away from
having so many mbeans to letting the
Yep - I know this got a little off topic, but I always react when I
hear people discuss where do we put the Jetty config files and I
try to encourage them to use a single configuration style for an
application and Jetty - be that Jetty's config files or their own.
What you say about the config
It looks like some performance tuning needs to be done with the new class
loader
and or initialization code as the startup time has gone from 9 seconds to 65
seconds:
...
[Default] JBoss 2.4.0 Started in 0m:9s
...
[Default] JBoss 3.0.0alpha(DEV) [RABBIT-HOLE] Started in 1m:5s
hmmm...
I see 12 on RedHat 7.1 and Athlon 1.4 Ghz, something is not right,
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Tuesday, September 04, 2001 7:50 PM
|To: JBoss Dev
|Subject: [JBoss-dev] RH Startup time needs
Then I would guess the issue is the class loader. I have seen large
differences in
performance between custom class loaders on w2k vs linux due to issues with
the File class resolving paths very slowly on w2k. The same code starts in
17s on my linux box:
[Default] JBoss 3.0.0alpha(DEV)
Hi,
I'm running into an interesting dilemma with Log4J. I'm guessing JBoss
(2.4.0final) uses Log4J internally as a logging mechanism and exports some
of the functionality via a Log4J MLET. Because of the way the Log4J
classes are loaded by this MLET, none of those standard Log4J classes/apis
are
User: dmaplesden
Date: 01/09/04 18:47:05
Modified:src/main/org/jboss/system ServiceController.java
Log:
Remove the calls to service.init and service.start in the deploy method.
Revision ChangesPath
1.2 +6 -4
User: dmaplesden
Date: 01/09/04 18:49:44
Modified:src/main/org/jboss/deployment ServiceDeployer.java
Log:
Change deploy code to create all mbeans, then initialise all mbeans and finally
start all mbeans referred to by an URL.
Also change undeploy to stop and destroy mbeans it is
Ok I have just committed some changes to the ServiceDeployer and
ServiceController code.
Basically the ServiceDeployer now initialises all the mbeans referred to in
a jboss-service.xml file before starting them. The changes were fairly
straight-forward and I tested them out with the default
Describe the details of your problem as I have no trouble using log4j in
ejbs,
servlets, etc. The log4j classes are loaded by the mlet class loader and are
available to all other classes.
- Original Message -
From: John Cho [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September
User: user57
Date: 01/09/04 19:27:30
Modified:.build.xml
Log:
o dropped 'min' target
Revision ChangesPath
1.7 +1 -4 jnp/build.xml
Index: build.xml
===
RCS file:
Well it turns out it's not too hard to simply turn the MQ service into a
jsr/sar and hot deploy from the deploy directory. However some problems
turn up (of course) when you have other mbeans that rely on the MQ service.
Obviously this is a problem faced by many mbeans, and it has been dealt
Thanks for the responses,
I figured out what the problem was. I was starting JBoss with a wrapper
that calls org.jboss.Main directly. That wrapper was making some calls
(test calls that I forgot about) directly to some of the MBeans and EJBs..
since the wrapper's classes are loaded using an
User: starksm
Date: 01/09/04 22:06:36
Modified:src/docs/doco_files documentation-example.tar.gz
documentation-example.zip
Log:
Update the documentation example bundle to contain all current examples
Revision ChangesPath
1.2 +187 -119
JBoss daily test results
SUMMARY
Number of tests run: 82
Successful tests: 15
Errors:36
Failures: 31
[time of test: 5 September 2001 7:15 GMT]
[java.version:
40 matches
Mail list logo
