on 09-04-2 23.01, Pieter at [EMAIL PROTECTED] wrote:
I'd like to make an overview of JBoss 2.4.4 with hints to 3.0. I'll link you
to the results when I'm done.
So in the next few days, I'll be posting some questions on clustering,
caching, etc.
cool
But first: has anyone already made a
Are We ready to make a Demo folder in jboss-all/ that BM would copy into
output/*/* where I could with an ant build.xml file build and copy to deploy
... and once in deployed in deploy as a webapp I could edit some source -
save - *bong* - cool ...
/peter_f
User: starksm
Date: 02/04/09 16:23:55
Modified:jetty/src/main/org/jboss/jetty Tag: Branch_2_4 Jetty.java
Log:
Honor the virtual host setting from the metadata
Revision ChangesPath
No revision
No revision
1.9.2.11 +3
Do you mean a demo or example configuration for the server? I think
that a demo module under jboss-all is not appropriate, but a demo or
example configuration under server/ is certainly do able. There was
talk awhile ago about how to best organize this. I have not implemented
anything since
JBoss daily test results
SUMMARY
Number of tests run: 575
Successful tests: 544
Errors:25
Failures: 6
[time of test: 10 April 2002 0:38 GMT]
[java.version:
User: starksm
Date: 02/04/09 16:52:00
Modified:src/main/org/jboss/mq/server Tag: Branch_2_4
ClientConsumer.java
Log:
Check for a closed connection before waiting on messages to avoid
thread leaks.
Revision ChangesPath
No
User: starksm
Date: 02/04/09 16:55:57
Modified:src/main/org/jboss/mq/selectors Tag: Branch_2_4
Selector.java
Log:
Treat empty selectors as null selectors and include the selector
in the InvalidSelectorException. Fixes Bug #537564.
Revision Changes
User: starksm
Date: 02/04/09 16:55:57
Modified:src/main/org/jboss/mq Tag: Branch_2_4 Subscription.java
Log:
Treat empty selectors as null selectors and include the selector
in the InvalidSelectorException. Fixes Bug #537564.
Revision ChangesPath
No
Bugs item #537564, was opened at 2002-03-31 17:24
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=537564group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Alarik Myrin (alarik)
Assigned to:
on 11-04-2 01.21, Jason Dillon at [EMAIL PROTECTED] wrote:
Do you mean a demo or example configuration for the server? I think
that a demo module under jboss-all is not appropriate, but a demo or
example configuration under server/ is certainly do able. There was
talk awhile ago about how
I would prefer to keep any additional configurations that ship with the
release to a minimum. I think that three configs: default, advanced
and example will cover what we need and won't add much extra
confusion. I expect that clustering would go into the advanced
configuration.
--jason
JBoss daily test results
SUMMARY
Number of tests run: 575
Successful tests: 544
Errors:25
Failures: 6
[time of test: 10 April 2002 1:24 GMT]
[java.version:
Bugs item #538236, was opened at 2002-04-02 19:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=538236group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Dain
you can save a lot of loading time if you
could check to see if the data stored in the
EntityContext is still in sync with the db row.
Dain, you already answered the reason for Option B.
However, when you said very little we can reuse, you seems to assume CMP. In our
cases, we use Option B and
User: starksm
Date: 02/04/09 17:52:36
Modified:src/main/org/jboss/test/perf/interfaces Tag: Branch_2_4
PerfTestSession.java
Log:
Fix PerfTestSession interface errors and add test of setRollbackOnly
to StatefulSessionTest
Revision ChangesPath
User: starksm
Date: 02/04/09 17:52:35
Modified:src/main/org/jboss/test/cts/interfaces Tag: Branch_2_4
StatefulSession.java
Log:
Fix PerfTestSession interface errors and add test of setRollbackOnly
to StatefulSessionTest
Revision ChangesPath
No
User: starksm
Date: 02/04/09 17:52:35
Modified:src/main/org/jboss/test/cts/ejb Tag: Branch_2_4
StatefulSessionBean.java
Log:
Fix PerfTestSession interface errors and add test of setRollbackOnly
to StatefulSessionTest
Revision ChangesPath
No
User: d_jencks
Date: 02/04/09 18:06:03
Added: src/main/org/jboss/test/jmx/test
DeployConnectionManagerUnitTestCase.java
Removed: src/main/org/jboss/test/jmx/test
ConnectionFactoryLoaderUnitTestCase.java
Log:
updated test case
Guys,
You are assuming CMP only. But how about BMP? If someone wants to implement a
timestamp or rowversion in his table and reuse the instance under Option B, the
current JBoss 2.4.4 implementation would not be able to support it.
Henri
-Original Message-
From: marc fleury
JBoss daily test results
SUMMARY
Number of tests run: 575
Successful tests: 547
Errors:25
Failures: 3
[time of test: 10 April 2002 2:10 GMT]
[java.version:
Hi Corby
Thanx for looking into it. Will check with Juha / Adrian to see what they
think.
My patch addresses this problem without altering
NotificationBroadcastSupport. The SchedulerMBean receives the synchronous
notification, creates a new Thread to actually invoke the MBean, and returns
the
Sure, though then perhaps an additional minimal configuration is in
order, so that the default brings up most of the needed functionality.
Or perhaps not... this is hard, because the minimum required is on that
there be a jboss-service.xml, you don't need to configure any other
beans... but
User: d_jencks
Date: 02/04/09 18:08:24
Modified:src/main/org/jboss/resource/connectionmanager
JBossManagedConnectionPool.java RARDeployment.java
Log:
added support for setting individual ManagedConnectionFactory properties
programatically
Revision
Good points Tom.Do you do your optimistic lock check on
both ejbLoad and ejbStore?I suggest using the following container
configuration with your optimistic locking scheme. If you try it out, let
me know how it works out.
Thanks,
Bill
container-configuration
container-nameStandard CMP
I see your point about a minimal configuration.
But what about the idea of a directory that has all the deployable
stuff. This could be a good solution to the problem of people asking
(or having to search for) database *-service.xml files. And as I said
earlier, it would allow people to
Tom,
The commit option code actually Bill's. I don't know if Bill will be
able to look at this before the friday release, so Tom can you submit a
patch?
-dain
tom yeh wrote:
you can save a lot of loading time if you
could check to see if the data stored in the
EntityContext is still in
User: d_jencks
Date: 02/04/09 18:44:41
Added: src/etc/example-config mssql-service.xml
Log:
example mssql server config thanks to Ove Ranheim
Revision ChangesPath
1.1 jbosscx/src/etc/example-config/mssql-service.xml
Index: mssql-service.xml
Hi Geeks
Maybe it is a better solution to have the minimal configuration
specified in the free JBoss documenation because what is the
minimal configuration. If you don't need JMS then you can get
ride of it but when you deploy a MDB then you need it.
I would suggest we go with the everything and
Yes perhaps. The good thing about JBoss3 is that we can isolate similar
and related configuration into a file, then we simply document what the
file does (and what other files it depends on)... if the user doesn't
need that functionality, then they can remove it.
After a bit more thought I
Bugs item #541323, was opened at 2002-04-09 00:42
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=541323group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Luke Taylor (luke_t)
Assigned
User: patriot1burke
Date: 02/04/09 19:21:07
Removed: src/main/org/jboss/ejb/plugins/lock
SimplePessimisticEJBLock.java
Log:
not supporting this anymore.
___
Jboss-development mailing list
[EMAIL PROTECTED]
Bill, thanks for configuration, but it is the same as what I am trying.
gt;Henri wrote:
gt;the EntityMultiInstanceSynchronizationInterceptor.java
gt;implementation of jboss 2.4.4 always calling
gt;ejbPassivate() no matter it is Option B or Option C.
After logging messages and examining the
Tom,
Ok, I know what you need. Give me a few.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of tom
yeh
Sent: Tuesday, April 09, 2002 10:24 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] RE: Bug in
JBoss daily test results
SUMMARY
Number of tests run: 575
Successful tests: 544
Errors:26
Failures: 5
[time of test: 10 April 2002 3:25 GMT]
[java.version:
User: peterbraswell
Date: 02/04/09 19:38:59
Modified:jboss.net/testsuite/src/resources/jmx/sar/META-INF
jboss-service.xml
Log:
Fixed erroneous package naming in Unit tests...
Revision ChangesPath
1.2 +2 -2
User: peterbraswell
Date: 02/04/09 19:38:59
Modified:jboss.net/testsuite/src/main/org/jboss/test/net/jmx
JMXTest.java JMXTestMBean.java
WSRJMXAccessUnitTestCase.java
Log:
Fixed erroneous package naming in Unit tests...
Revision
User: peterbraswell
Date: 02/04/09 19:38:58
Modified:jboss.net/src/main/org/jboss/net/jmx/server
MBeanProvider.java
Log:
Fixed erroneous package naming in Unit tests...
Revision ChangesPath
1.5 +3 -3
Bugs item #537990, was opened at 2002-04-01 13:50
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=537990group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Dan Bunker (danbunker)
Assigned to:
Bugs item #541092, was opened at 2002-04-08 11:49
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=541092group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to:
JBoss daily test results
SUMMARY
Number of tests run: 568
Successful tests: 536
Errors:26
Failures: 6
[time of test: 10 April 2002 5:2 GMT]
[java.version:
JBoss daily test results
SUMMARY
Number of tests run: 575
Successful tests: 545
Errors:25
Failures: 5
[time of test: 10 April 2002 6:2 GMT]
[java.version:
Bugs item #541855, was opened at 2002-04-10 15:21
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=541855group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Nobody/Anonymous
User: juhalindfors
Date: 02/04/09 22:19:32
Modified:.build.xml
Log:
was wrong branch
Revision ChangesPath
1.34 +2 -2 jmx/build.xml
Index: build.xml
===
RCS file:
User: juhalindfors
Date: 02/04/09 22:16:22
Modified:.build.xml
Log:
1.0 release
Revision ChangesPath
1.33 +3 -3 jmx/build.xml
Index: build.xml
===
RCS file:
User: patriot1burke
Date: 02/04/09 22:32:58
Modified:src/main/org/jboss/ejb BeanLock.java BeanLockManager.java
Container.java
Log:
pass along the container to the BeanLockManager and BeanLock. Also changed the
API of BeanLock from releaseMethodLock() to
looking at the code, I think the timer should override the
sendNotification() to use multiple threads to call listener
handleNotification() methods (threadpool if it seems creating
new Threads per listener call won't perform, which is likely)
however the default behavior in the
User: patriot1burke
Date: 02/04/09 22:44:46
Modified:src/main/org/jboss/metadata BeanMetaData.java MetaData.java
Added: src/main/org/jboss/metadata MethodAttributes.java
Log:
new meta data for method-attributes
Revision ChangesPath
1.37 +56 -1
User: patriot1burke
Date: 02/04/09 22:42:38
Modified:src/main/org/jboss/ejb/plugins
EntityInstanceInterceptor.java
Log:
don't ctx.setTransaction is method is readonly or bean is readonly. Otherwise,
Passivation
thread could spin forever
Revision
User: patriot1burke
Date: 02/04/09 22:42:56
Modified:src/main/org/jboss/ejb/plugins/lock BeanLockSupport.java
Log:
new BeanLock api support
Revision ChangesPath
1.13 +5 -2 jboss/src/main/org/jboss/ejb/plugins/lock/BeanLockSupport.java
Index:
User: patriot1burke
Date: 02/04/09 22:44:03
Modified:src/main/org/jboss/ejb/plugins/lock
QueuedPessimisticEJBLock.java
Log:
read-only methods and read-only beans will now release transactional locks at the
end of an invocation.
Revision Changes
User: juhalindfors
Date: 02/04/09 22:41:59
Modified:.Tag: BranchMX_1_0 build.xml
Log:
the real 1.0 release
Revision ChangesPath
No revision
No revision
1.27.2.4 +2 -2 jmx/build.xml
Index: build.xml
User: patriot1burke
Date: 02/04/09 22:40:38
Modified:src/main/org/jboss/ejb/plugins EntityLockInterceptor.java
Log:
new API for BeanLock releaseMethodLock turned to endInvocation
Revision ChangesPath
1.10 +2 -2
User: patriot1burke
Date: 02/04/09 22:40:12
Modified:src/main/org/jboss/ejb/plugins
EntitySynchronizationInterceptor.java
Log:
read-only methods and read-only beans no longer synchronize with the transaction.
Revision ChangesPath
1.64 +11 -9
I've just committed and tested Peter Murray's patch for read-only method
locks. Great work Peter!
Here's the deal.
Transactional locks will now be released at the end of the invocation if the
bean is readonly or the method has been declared read-only in bean meta
data. Basically if you go
Bugs item #541866, was opened at 2002-04-10 00:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=541866group_id=22866
Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to:
JBoss daily test results
SUMMARY
Number of tests run: 544
Successful tests: 220
Errors:315
Failures: 9
[time of test: 10 April 2002 7:8 GMT]
[java.version:
Bugs item #541866, was opened at 2002-04-10 00:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=541866group_id=22866
Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to:
101 - 157 of 157 matches
Mail list logo
