=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
Hello,
The org.jboss.Shutdown class does
JBoss daily test results
SUMMARY
Number of tests run: 127
Successful tests: 127
Errors:0
Failures: 0
[time of test: 14 December 2001 7:48 GMT]
[java.version: 1.
Patches item #493197, was opened at 2001-12-13 23:00
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=493197&group_id=22866
Category: None
Group: v2.4 BETA (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Larry Sanderson (lsanders)
Assigned
Bugs item #493188, was opened at 2001-12-13 22:00
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=493188&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Henri Chen (henrichen)
Assigned t
>
> > 2) Should manifest lib(s) be hot deployable. I have
> to restart jboss to
> have it recgonize the new classes in the jar?
> >
> Meaning what? That you update the libs and then touch
> the deployment
> descriptor
> to redeploy? If your expecting the libs to be watched
> for updates to trigg
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
Hello,
The org.jboss.Shutdown class does
JBoss daily test results
SUMMARY
Number of tests run: 127
Successful tests: 125
Errors:2
Failures: 0
[time of test: 14 December 2001 5:3 GMT]
[java.version: 1.3
>
> 1) If your ear directory lives in the deploy dir, then don't specify your
unpackaged ear dir in jboss.jcml. It causes Auto Deployer to deploy, then
un-deploy, then deploy again. Thus causing context root namespace conflicts
in tomcat for your war(s).
>
I'll fix this.
> 2) Should manifest lib(
Perhaps once Marc's changes are commited we can look into make this a
reality.
--jason
On Wed, 12 Dec 2001, Bill Burke wrote:
> Excellent idea.
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jason
> > Dillon
> > Sent: Wednesday, Decemb
User: starksm
Date: 01/12/13 19:22:11
Modified:src/main/org/jboss/ejb/plugins/jms Tag: Branch_2_4
JMSContainerInvoker.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
support for the dead message queue for repeated MDB.onMes
User: starksm
Date: 01/12/13 19:22:12
Modified:src/main/org/jboss/naming Tag: Branch_2_4
NonSerializableFactory.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
support for the dead message queue for repeated MDB.onMessage f
User: starksm
Date: 01/12/13 19:30:33
Modified:src/build Tag: Branch_2_4 run_tests.xml
Log:
Use the jboss.dist log4j.jar version
Revision ChangesPath
No revision
No revision
1.15.2.10 +2 -2 jbosstest/src/build/Att
User: starksm
Date: 01/12/13 19:31:41
Modified:src/resources/mdb/META-INF Tag: Branch_2_4 ejb-jar.xml
jboss.xml
Log:
Add BadMDB
Revision ChangesPath
No revision
No revision
1.4.2.1 +82 -106
User: starksm
Date: 01/12/13 19:31:22
Modified:src/main/org/jboss/test/mdb/test Tag: Branch_2_4 Main.java
Log:
Add test for the MDB dead message queue
Revision ChangesPath
No revision
No revision
1.5.2.2 +228 -157 j
User: starksm
Date: 01/12/13 19:31:22
Modified:src/main/org/jboss/test/mdb/bean Tag: Branch_2_4
ExQueueBean.java
Added: src/main/org/jboss/test/mdb/bean Tag: Branch_2_4 BadMDB.java
Log:
Add test for the MDB dead message queue
Revision Changes
User: starksm
Date: 01/12/13 19:22:09
Modified:src/main/org/jboss/ejb Tag: Branch_2_4
MessageDrivenContainer.java
MessageDrivenEnterpriseContext.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
suppor
User: starksm
Date: 01/12/13 19:22:11
Modified:src/main/org/jboss/jms/asf Tag: Branch_2_4
ServerSessionPoolFactory.java
ServerSessionPoolLoader.java
ServerSessionPoolLoaderMBean.java
StdServ
User: starksm
Date: 01/12/13 19:22:11
Modified:src/main/org/jboss/ejb/plugins Tag: Branch_2_4
MessageDrivenInstanceInterceptor.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
support for the dead message queue for repeated
User: starksm
Date: 01/12/13 19:22:12
Modified:src/main/org/jboss/tm Tag: Branch_2_4 XidImpl.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
support for the dead message queue for repeated MDB.onMessage failures.
Revision ChangesPath
N
User: starksm
Date: 01/12/13 19:22:12
Modified:src/main/org/jboss/metadata Tag: Branch_2_4
MessageDrivenMetaData.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
support for the dead message queue for repeated MDB.onMessage
User: starksm
Date: 01/12/13 19:22:11
Modified:src/main/org/jboss/jms/jndi Tag: Branch_2_4
JMSProviderLoader.java
Log:
Integrate changes from 3.0 to improve the MDB/ASF layer. This includes
support for the dead message queue for repeated MDB.onMessage fail
User: starksm
Date: 01/12/13 19:20:23
Modified:src/lib Tag: Branch_2_4 jbossmq.jar
Log:
Update JBossMQ ASF layer
Revision ChangesPath
No revision
No revision
1.8.4.12 +1272 -821 jboss/src/lib/Attic/jbossmq.jar
User: starksm
Date: 01/12/13 19:20:23
Modified:src/client Tag: Branch_2_4 jbossmq-client.jar
Log:
Update JBossMQ ASF layer
Revision ChangesPath
No revision
No revision
1.6.4.11 +906 -555 jboss/src/client/Attic/jbossm
User: starksm
Date: 01/12/13 19:19:13
Modified:src/main/org/jboss/mq/il/oil Tag: Branch_2_4
OILClientILService.java OILServerILService.java
Log:
Merge changes from main to improve the ASF behavior and update the logging.
Revision ChangesPath
No
User: starksm
Date: 01/12/13 19:19:13
Modified:src/main/org/jboss/mq Tag: Branch_2_4
SpyMessageConsumer.java SpyXAResource.java
SpyXAResourceManager.java
Log:
Merge changes from main to improve the ASF behavior and update the logging.
User: starksm
Date: 01/12/13 19:19:12
Modified:src/build Tag: Branch_2_4 build.xml
Log:
Merge changes from main to improve the ASF behavior and update the logging.
Revision ChangesPath
No revision
No revision
1.8.2.5
User: starksm
Date: 01/12/13 18:21:44
Modified:src/etc/conf/default standardjboss.xml
Log:
Don't let the dead queue timeToLive < 0 as this results in unusable
messages. The value corresponding to no expirary it 0, not -1. Set the
standardjboss.xml TimeToLive value to 0.
Re
User: starksm
Date: 01/12/13 18:21:45
Modified:src/main/org/jboss/ejb/plugins/jms DLQHandler.java
Log:
Don't let the dead queue timeToLive < 0 as this results in unusable
messages. The value corresponding to no expirary it 0, not -1. Set the
standardjboss.xml TimeToLive value t
I created a bug report on this on 2001-07-07 20:51
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2499
> > Can we get it fixed so that it will show us that these tests failed?
>
> That would be nice, I don't have time right now. I think the problem is
> with tests that timeout, they generate
On 2001.12.13 17:10:34 -0500 Jason Dillon wrote:
> > > Why doesn't this show 201 tests?
> >
> > I think something got stuck, lots of tests failed completely (no xml
> output
> > at all, so they aren't in this summary), and finally shutdown didn't
> work,
> > generating the other message you love
User: dmaplesden
Date: 01/12/13 16:22:30
Modified:src/main/org/jboss/mq/il/uil UILClientILService.java
Log:
debug -> trace logging
Revision ChangesPath
1.5 +4 -3 jbossmq/src/main/org/jboss/mq/il/uil/UILClientILService.java
Index: UILClientILService.java
User: dmaplesden
Date: 01/12/13 16:24:21
Modified:src/main/org/jboss/pool ObjectPool.java
Log:
debug -> trace logging
Revision ChangesPath
1.10 +22 -21jbosspool/src/main/org/jboss/pool/ObjectPool.java
Index: ObjectPool.java
===
User: dmaplesden
Date: 01/12/13 16:22:43
Modified:src/main/org/jboss/mq/il/oil OILClientILService.java
Log:
debug -> trace logging
Revision ChangesPath
1.5 +6 -4 jbossmq/src/main/org/jboss/mq/il/oil/OILClientILService.java
Index: OILClientILService.java
No, only jbossmq-client.jar (and a couple of things like jnp-client.jar and
log4j.jar) should be needed by JBossMQ clients, the other classes are
server-side only.
> -Original Message-
> From: Scott M Stark [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 14, 2001 1:01 PM
> To: JBossDe
I added the Logger and TracePriority classes to the jboss-client.jar.
Isn't this required by JBossMQ clients? If not, then these classes
need to be redundantly added to jbossmq-client.jar
- Original Message -
From: "David Maplesden" <[EMAIL PROTECTED]>
To: "JBossDev (E-mail)" <[EMAIL PRO
Hi,
> Why doesn't this show 201 tests?
>
Don't you just love Java's portability...
;-)
Chris
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Ok, I know this was a bit naughty.
Part of the reason I did it (and I know this is not a good excuse) is that
we have a small problem in the build, introduced when you (I think it was
you) changed the Connection class to use org.jboss.logging.Logger.
The problem is that Connection (along with
User: starksm
Date: 01/12/13 14:53:29
Modified:src/main/org/jboss/mq SpyMessageConsumer.java
Log:
Restore trace level message and switch to Logger. Fix formatting.
Revision ChangesPath
1.16 +381 -244 jbossmq/src/main/org/jboss/mq/SpyMessageConsumer.java
Index
Don't just drop the debug msgs, change them to trace msgs using
the org.jboss.logging.Logger rather than org.apache.log4j.Category.
- Original Message -
From: "David Maplesden" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2001 2:22 PM
Subject: [JBoss-dev] CVS u
On 2001.12.13 16:49:49 -0500 David Jencks wrote:
> On 2001.12.13 15:31:27 -0500 Jason Dillon wrote:
> > Why doesn't this show 201 tests?
> >
> > --jason
>
> I think something got stuck, lots of tests failed completely (no xml
> output
> at all, so they aren't in this summary), and finally shutd
Title: RE: [JBoss-dev] Building Sources
Ryan,
unzip doesn't seem to restore correct permissions - so, jboss-all/tools/bin/ant and friends are not executable.
I can't find any way to force unzip to honor file permissions, so give the tarball a try: http://www.jboss.org/snapshots/jboss-all.t
User: dmaplesden
Date: 01/12/13 14:22:43
Modified:src/main/org/jboss/mq/server MessageReference.java
MessageCache.java
Log:
implement more efficient LRUCache
Revision ChangesPath
1.7 +4 -4 jbossmq/src/main/org/jboss/mq/server/MessageRef
User: dmaplesden
Date: 01/12/13 14:22:09
Modified:src/main/org/jboss/mq SpySession.java
SpyMessageConsumer.java
Log:
reduce overly verbose logging
Revision ChangesPath
1.8 +4 -11 jbossmq/src/main/org/jboss/mq/SpySession.java
Index:
User: dmaplesden
Date: 01/12/13 14:20:57
Modified:src/main/org/jboss/resource JBossConnectionListenerImpl.java
Log:
reduce overly verbose logging
Revision ChangesPath
1.6 +5 -3
jbosscx/src/main/org/jboss/resource/JBossConnectionListenerImpl.java
Index: J
> > Why doesn't this show 201 tests?
>
> I think something got stuck, lots of tests failed completely (no xml output
> at all, so they aren't in this summary), and finally shutdown didn't work,
> generating the other message you love so much. ;-) (I will stop when all
> the tests run every time,
Here's the specifics:
System: Red Hat 7.2 Linux 2.4.14 on i686
JDK: java version "1.3.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)
Ant: Ant version 1.4.1 compiled on October 11 2001
Snapshot: http://www.jboss.or
On 2001.12.13 15:31:27 -0500 Jason Dillon wrote:
> Why doesn't this show 201 tests?
>
> --jason
I think something got stuck, lots of tests failed completely (no xml output
at all, so they aren't in this summary), and finally shutdown didn't work,
generating the other message you love so much. ;
> Because I was still seeing javadoc tasks running. Looking closer these
> are all xdoclet taks.
Sure are... too bad javadoc won't run in the same vm, cause it slows things
down quite a bit.
--jason
___
Jboss-development mailing list
[EMAIL PROTECTE
User: starksm
Date: 01/12/13 13:29:22
Modified:src/main/org/jboss/mq/server Tag: Branch_2_4 BasicQueue.java
Log:
Some cleanup of logging and imports
Revision ChangesPath
No revision
No revision
1.4.2.4 +14 -16jbo
User: starksm
Date: 01/12/13 13:13:28
Modified:jboss/etc local.properties-example
Log:
Comment out the javadoc disable since its not generated by default
Revision ChangesPath
1.7 +1 -1 build/jboss/etc/local.properties-example
Index: local.properties-exam
Because I was still seeing javadoc tasks running. Looking closer these
are all xdoclet taks.
- Original Message -
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, December 13, 2001 12:44 PM
Subject: Re: [JBoss-dev] C
Hello Alain,
On Wed, 12 Dec 2001, Coetmeur, Alain wrote:
> [snip]
> I've seen you have decided not to support persistence of naming data...
Yes. This makes sense for EJBs, because JBoss registers EJB homes
at deployment time and unregisters them at undeployment time. When the
JBoss server exits
I should be more specific. I've copied the ant directory into the same
directory that I'm running build.sh from. This is apparently what the
script wants (I walked through the script). None of the targets work.
For instance. If i were to run
./build/build.sh init
or help or any other target, th
Did you checkout the quick start guide online? Where did you get the
project sources from?
You might want to *read* the first item in the build system faq:
http://www.jboss.org/developers/guide/buildsystem-faq.jsp
Please tell me that you have read the docs that are available... else I
might h
> yes, sometimes I think I don't yell loud enough, if you read the emails
> back when the bird thing you will see that I was pushing for "classes"
> outside the sar as it is a total pain, so the sar is just a service.xml
> that defines one service and references jars separately and voila! done.
I should be more specific. I've copied the ant directory into the same directory that
I'm running build.sh from. This is apparently what the script wants (I walked through
the script). None of the targets work. For instance. If i were to run
./build/build.sh init
or help or any other target,
You know this will prevent javadoc generation completly. Users interested
in generating these will have to comment this out... since the if/unless
fluff in ant won't evaulate the value of the property as a boolean.
Any reason why you changed this? The latest build will default to the
'most'
Why doesn't this show 201 tests?
--jason
On Thu, 13 Dec 2001 [EMAIL PROTECTED] wrote:
>
>
> JBoss daily test results
>
> SUMMARY
>
> Number of tests run: 127
>
>
>
> Successful tests: 127
>
> Errors:0
>
> Failures:
Will this ever stop?
--jason
On Thu, 13 Dec 2001 [EMAIL PROTECTED] wrote:
>
> =
> ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
> =
>
How did you start the build?
--jason
On Thu, 13 Dec 2001, Ryan Marsh wrote:
> Hopefully I won't get flammed, I'd like to work on the Castor JDO integration some
>and I'm trying to build the sources. I'm by no means a neophyte but I'm getting the
>following when trying to build from a snapsho
User: starksm
Date: 01/12/13 11:33:42
Modified:.build.xml
Log:
Add Logger and TracePriority to jboss-client.jar
Revision ChangesPath
1.46 +3 -1 jboss/build.xml
Index: build.xml
===
Erh - I'll try that again - it's one of those days
Jules
Note: forwarded message attached.
__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--- Begin Me
I am testing out the new "unpackaged ear" feature in 2.4.4-beta.
Two things I have come across:
1) If your ear directory lives in the deploy dir, then don't specify your unpackaged
ear dir in jboss.jcml. It causes Auto Deployer to deploy, then un-deploy, then deploy
again. Thus causing context
User: lqd
Date: 01/12/13 07:58:19
Modified:src/main/org/jboss/mq/pm/file Tag: Branch_2_4
MessageLog.java
Log:
Use SpyMessage.writeMessage() and SpyMessage.readMessage() methods to
store / restore files written to disk.
Revision ChangesPath
User: starksm
Date: 01/12/13 07:23:19
Modified:src/main/org/jboss/mq SpyConnectionConsumer.java
Log:
Use JBoss Logger and trace level priority msg in run loop
Revision ChangesPath
1.7 +89 -43jbossmq/src/main/org/jboss/mq/SpyConnectionConsumer.java
Index:
> I was thinking last night about how crappy the whole
> archive thing that sun
> started is with respect to changing the configuration
> easily. I was
> thinking that it is a bitch to extract a .ear, edit
> the application.xml,
> then re-jar it and copy it to change where my .war
> gets deployed
Look at the guides on jboss.org:
http://www.jboss.org/developers/guide/quickstart.jsp
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: "Ryan Marsh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday
The reason either one can be returned is because StdServerSession supports
using a JMS provider that does not implement XASessions.
Regards,
Hiram
>From: "Scott M Stark" <[EMAIL PROTECTED]>
>Reply-To: "Scott M Stark" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: [JBoss-dev] Why to we
User: starksm
Date: 01/12/13 06:19:33
Modified:src/lib Tag: Branch_2_4 oswego-concurrent.jar
Log:
Remove the source from the jar as it can cause compile problems under
some circumstances. This is version 1.3.1 of the Doug Lea concurrency
utility classes(http://gee.cs.oswego.ed
Hopefully I won't get flammed, I'd like to work on the Castor JDO integration some and
I'm trying to build the sources. I'm by no means a neophyte but I'm getting the
following when trying to build from a snapshot jboss-all.
Searching for build.xml ...
Buildfile: /home/ryan/jboss-all/build/buil
User: starksm
Date: 01/12/13 05:32:05
Modified:src/main/org/jboss/jms/asf StdServerSession.java
StdServerSessionPool.java
Log:
Use trace level logging for the per message methods
Revision ChangesPath
1.11 +90 -84jboss/src/main/org/jboss/
User: starksm
Date: 01/12/13 05:25:32
Modified:src/main/org/jboss/ejb/plugins/jms JMSContainerInvoker.java
Log:
Use JBoss Logger and trace level priority for onMessage
Revision ChangesPath
1.35 +9 -14
jboss/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoke
User: starksm
Date: 01/12/13 05:28:18
Modified:jboss/etc local.properties-example
Log:
Disable javadoc by default
Revision ChangesPath
1.6 +3 -0 build/jboss/etc/local.properties-example
Index: local.properties-example
==
Bugs item #491536, was opened at 2001-12-11 04:57
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=491536&group_id=22866
Category: JBossCMP
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 1
Submitted By: Vincent Harcq (vharcq)
Assigned to: Vin
JBoss daily test results
SUMMARY
Number of tests run: 127
Successful tests: 127
Errors:0
Failures: 0
[time of test: 13 December 2001 10:17 GMT]
[java.version: 1
I had a go at fixing this.
When a deployer is stopped, removed the watches from the AutoDeployer. The deployments
are NOT undeployed by the AutoDeployer.
The J2eeDeployer undeploys at stop anyway so this fixes the problem. But...
DeployerMBeanSupport derived deployers don't undeploy their depl
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
Hello,
The org.jboss.Shutdown class does
77 matches
Mail list logo
