Hi,
Reply to the initial question:
I have committed to JBoss 3.0 CVS tree the patch #489503 by Ignacio
Coloma (AutoNumberEJB2.java).
The usage is similar to the one for jaws AutoNumberEJB.
As for support for different types of key generators (sequence,
identity, etc.) as in Castor, I haven't
User: jules_gosnell
Date: 02/01/12 02:57:45
Modified:jetty/src/main/org/jboss/jetty
DistributedSessionManager.java JBossLogSink.java
JBossWebApplicationContext.java
Log:
disable DistributedSessionmanager, temporarily, whilst I do some
User: jules_gosnell
Date: 02/01/12 05:59:02
Modified:mortbay/jetty3extra/lib org.mortbay.jetty.jmx.jar
Log:
new snapshot from Jetty cvs
Revision ChangesPath
1.5 +25 -25thirdparty/mortbay/jetty3extra/lib/org.mortbay.jetty.jmx.jar
Binary file
User: jules_gosnell
Date: 02/01/12 05:59:00
Modified:mortbay/jetty/lib javax.servlet.jar org.apache.jasper.jar
org.mortbay.jetty.jar
Log:
new snapshot from Jetty cvs
Revision ChangesPath
1.5 +81 -81
User: slaboure
Date: 02/01/12 06:03:27
Modified:src/main/org/jboss/ha/jndi HANamingService.java
Log:
startService method with no parameter was missing: service was running but not
started
Revision ChangesPath
1.20 +8 -1
User: slaboure
Date: 02/01/12 06:04:22
Modified:src/main/org/jboss/ha/jndi HANamingServiceMBean.java
Log:
Interface was not extending ServiceMBean: lifecycles methods were not called =
service was not started
Revision ChangesPath
1.8 +2 -1
User: slaboure
Date: 02/01/12 08:54:40
Modified:src/main/org/jboss/ha/hasessionstate/server
HASessionStateServiceMBean.java
Log:
Bug: the HASessionStateService will never start without this (and SFSB bean will
fail at deployement time)
Revision
User: slaboure
Date: 02/01/12 08:57:16
Modified:src/main/org/jboss/metadata BeanMetaData.java
Log:
Allow boolean value of the clustered element to be case insensitive.
BTW, the testbeancluster.jar wasn't deployed as a set of clustered beans for this
reason (true was typed
User: slaboure
Date: 02/01/12 08:53:38
Modified:src/main/org/jboss/ha/framework/server HAPartitionImpl.java
Log:
When creating the DRM, gives it its MBeanServer reference
Revision ChangesPath
1.14 +2 -2
User: slaboure
Date: 02/01/12 08:52:53
Modified:src/main/org/jboss/ha/framework/server
DistributedReplicantManagerImpl.java
Log:
- DRM service is now registered as an MBEAN (but not started as an MBEAN: the start
is still managed by the HAPartition)
-
User: slaboure
Date: 02/01/12 08:52:09
Modified:src/main/org/jboss/ha/framework/server
DistributedStateImpl.java
DistributedStateImplMBean.java
Log:
Provide a listContent and listXmlContent for debugging purposes (useful with
User: slaboure
Date: 02/01/12 08:52:53
Modified:src/main/org/jboss/ha/framework/interfaces
DistributedReplicantManager.java
Log:
- DRM service is now registered as an MBEAN (but not started as an MBEAN: the start
is still managed by the HAPartition)
-
Feature Requests item #502757, was opened at 2002-01-12 09:22
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376688aid=502757group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Priority: 5
Submitted By: Vincent Harcq (vharcq)
Assigned to:
Feature Requests item #502763, was opened at 2002-01-12 09:30
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376688aid=502763group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Vincent Harcq (vharcq)
Assigned to: Nobody/Anonymous
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
User: juhalindfors
Date: 02/01/12 12:03:30
Modified:src/main/javax/management
NotificationBroadcasterSupport.java
Log:
bug fix
Revision ChangesPath
1.2 +1 -1
jmx/src/main/javax/management/NotificationBroadcasterSupport.java
User: juhalindfors
Date: 02/01/12 12:07:59
Modified:src/main/org/jboss/mx/server/registry MBeanEntry.java
Log:
fixes for MBeanRegistration behavior
Revision ChangesPath
1.4 +49 -22jmx/src/main/org/jboss/mx/server/registry/MBeanEntry.java
Index:
User: juhalindfors
Date: 02/01/12 12:08:59
Modified:src/main/org/jboss/mx/modelmbean ModelBase.java
Log:
resource field moved to invoker
Revision ChangesPath
1.2 +2 -2 jmx/src/main/org/jboss/mx/modelmbean/ModelBase.java
Index: ModelBase.java
User: juhalindfors
Date: 02/01/12 12:05:51
Modified:src/main/org/jboss/mx/metadata StandardMetaData.java
Log:
fix for standard mbean meta data builder: only getters with zero
signature are marked as attribute readers
Revision ChangesPath
1.3 +4 -3
User: juhalindfors
Date: 02/01/12 12:10:53
Modified:src/main/org/jboss/mx/server MBeanInvoker.java
MBeanServerImpl.java StandardMBeanInvoker.java
Log:
Revision ChangesPath
1.3 +7 -3 jmx/src/main/org/jboss/mx/server/MBeanInvoker.java
User: patriot1burke
Date: 02/01/12 12:28:49
jbosstest/src/main/org/jboss/test/deadlock/interfaces - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: patriot1burke
Date: 02/01/12 12:28:56
jbosstest/src/main/org/jboss/test/deadlock/bean - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: patriot1burke
Date: 02/01/12 12:28:41
jbosstest/src/main/org/jboss/test/deadlock/test - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: patriot1burke
Date: 02/01/12 12:29:21
Added: src/main/org/jboss/test/deadlock/test
BeanStressTestCase.java
Log:
Added deadlock detection test to test new deadlock detection algorithm in
QueuedEJBPessimisticLock
Revision ChangesPath
1.1
User: patriot1burke
Date: 02/01/12 12:21:52
Modified:.build.xml
Log:
Added deadlock detection test to test new deadlock detection algorithm in
QueuedEJBPessimisticLock
Revision ChangesPath
1.58 +35 -1 jbosstest/build.xml
Index: build.xml
User: patriot1burke
Date: 02/01/12 12:21:07
Modified:src/main/org/jboss/ejb/plugins/lock
QueuedPessimisticEJBLock.java BeanLockSupport.java
Log:
Added deadlock detection. If application deadlock is detected and RuntimeException
is thrown so
that the
User: patriot1burke
Date: 02/01/12 12:29:52
Added: src/main/org/jboss/test/deadlock/bean
StatelessSessionBean.java EnterpriseEntityBean.java
Log:
Added deadlock detection test to test new deadlock detection algorithm in
QueuedEJBPessimisticLock
User: patriot1burke
Date: 02/01/12 12:31:39
Added: src/resources/deadlock jndi.properties client.policy
Log:
Added deadlock detection test to test new deadlock detection algorithm in
QueuedEJBPessimisticLock
Revision ChangesPath
1.1
User: patriot1burke
Date: 02/01/12 12:30:24
Added: src/main/org/jboss/test/deadlock/interfaces
StatelessSessionHome.java StatelessSession.java
EnterpriseEntityHome.java EnterpriseEntity.java
Log:
Added deadlock detection test to
Can somebody look at
server/src/.../ejb/plugins/lock/BeanLockSupport.java and
QueuedPessimisticEJBLock.java for me? I added an application deadlock
detection algorithm and need another set of eyeballs to make sure that I didn't
do anything too drastic. Don't worry, the code is very
simple.
User: patriot1burke
Date: 02/01/12 12:28:27
jbosstest/src/main/org/jboss/test/deadlock - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: patriot1burke
Date: 02/01/12 12:31:09
jbosstest/src/resources/deadlock - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
User: patriot1burke
Date: 02/01/12 12:31:58
Added: src/resources/deadlock/META-INF ejb-jar.xml
Log:
Added deadlock detection test to test new deadlock detection algorithm in
QueuedEJBPessimisticLock
Revision ChangesPath
1.1
Change Notes item #502817, was opened at 2002-01-12 12:43
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=381174aid=502817group_id=22866
Category: None
Group: v3.0 (Rabbit Hole)
Status: Open
Priority: 5
Submitted By: Bill Burke (patriot1burke)
Assigned to:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
A
thought on the performance issue.
You
could copy the hash map, and then do the detection. If you detect a
deadlock, then synchronize the entire map and run it again. This way you
only force a lock on the whole map when you really think there is a
deadlock.
-dain
-Original
User: ejort
Date: 02/01/12 13:14:26
Modified:src/main/org/jboss/ejb CacheKey.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.19 +3 -3 jboss/src/main/org/jboss/ejb/CacheKey.java
Index:
User: ejort
Date: 02/01/12 13:14:26
Modified:src/main/org/jboss/ejb/plugins AbstractInterceptor.java
BMPPersistenceManager.java
SecurityProxyInterceptor.java
StatefulSessionInstanceInterceptor.java
Log:
User: ejort
Date: 02/01/12 13:14:28
Modified:src/main/org/jboss/ejb/plugins/lock BeanLockSupport.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.11 +2 -2
User: ejort
Date: 02/01/12 13:14:28
Modified:src/main/org/jboss/ejb/plugins/jaws/metadata
JawsApplicationMetaData.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.14 +4 -5
User: ejort
Date: 02/01/12 13:14:30
Modified:src/main/org/jboss/util FileURLPatch.java Info.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.4 +4 -4 jboss/src/main/org/jboss/util/FileURLPatch.java
User: ejort
Date: 02/01/12 13:14:29
Modified:src/main/org/jboss/tm TxCapsule.java TxManager.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.32 +3 -3 jboss/src/main/org/jboss/tm/TxCapsule.java
User: ejort
Date: 02/01/12 13:14:26
Modified:src/main/org/jboss/configuration ConfigurationService.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.43 +14 -15
User: ejort
Date: 02/01/12 13:14:29
Modified:src/main/org/jboss/naming NamingService.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.25 +4 -5 jboss/src/main/org/jboss/naming/NamingService.java
User: ejort
Date: 02/01/12 13:14:27
Modified:src/main/org/jboss/ejb/plugins/jaws/jdbc
JDBCBeanExistsCommand.java JDBCCommand.java
JDBCCommandFactory.java
JDBCCreateEntityCommand.java
User: ejort
Date: 02/01/12 13:14:26
Modified:src/main/org/jboss/deployment Installer.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.20 +2 -3 jboss/src/main/org/jboss/deployment/Installer.java
User: ejort
Date: 02/01/12 13:14:29
Modified:src/main/org/jboss/jms/jndi JBossMQProvider.java
JMSProviderLoader.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.9 +6 -6
User: ejort
Date: 02/01/12 13:14:27
Modified:src/main/org/jboss/ejb/plugins/jaws
JAWSPersistenceManager.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.38 +4 -4
User: ejort
Date: 02/01/12 13:14:28
Modified:src/main/org/jboss/jms ConnectionFactoryHelper.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.6 +3 -4
User: ejort
Date: 02/01/12 13:14:29
Modified:src/main/org/jboss/jms/asf ServerSessionPoolLoader.java
Log:
Remove directory reference to log4j Category in preparation for log4j 1.2
Revision ChangesPath
1.7 +2 -7
Good thought. Doesn't this make things really
slow? Maybe a clone isn't so expensive.
- Original Message -
From:
Dain
Sundstrom
To: 'Bill
Burke' ; [EMAIL PROTECTED]
Sent: Saturday, January 12, 2002 4:12
PM
Subject: RE: [JBoss-dev] need help with
deadlock
Did someone forget to check in DistributedReplicantManagerImplMBean?
-dain
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Hey, I've been thinking. Should an entity ctx
be invalidated if it is ever removed or released from cache? I'm thinking
that if the ctx enters the passivation queue it should be invalidated so that it
is reloaded in ejbLoad. What I'm really getting at is that I want to
expose EntityBean
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
User: ejort
Date: 02/01/12 16:00:20
Modified:src/main/org/jboss/ejb/plugins
StatefulHASessionSynchronisationInterceptor.java
Log:
Remove unused log4j import
Revision ChangesPath
1.3 +1 -3
I don't think you can clone() a hashmap in a threadsafe way without
locking it. Of course you could sync{ clone() }, which is faster than
sync{ walk map, check for conflicts }.
Which maybe what Dain was suggesting in the first place.
-David
On Sat, 12 Jan 2002, Bill Burke wrote:
Good
Jules, the fix is very easy, you don't have to make JBossUserRealm
serializable, instead, when you do
SecurityAssociation.setPrincipal() don't pass it 'this' which is
JBossUserPrincipal, rather pass along a new SimplePrincipal() which
corresponds to the name stored in JBossUserPrincipal. The
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
User: ejort
Date: 02/01/12 17:10:03
Modified:src/main/org/jboss/mq/cluster/jms
ClusterTopicConnection.java
ClusterTopicConnectionFactory.java
Log:
Remove direct reference log4j category in preparation for log4j 1.2
Revision
User: ejort
Date: 02/01/12 17:10:02
Modified:src/main/org/jboss/mq SpyConnectionFactory.java
SpySession.java SpyTemporaryQueue.java
SpyTemporaryTopic.java SpyXAConnectionFactory.java
Log:
Remove direct reference log4j category in
User: ejort
Date: 02/01/12 17:10:03
Modified:src/main/org/jboss/mq/cluster/transport/udp
UDPAdminStream.java UDPStream.java
UDPTransport.java
Log:
Remove direct reference log4j category in preparation for log4j 1.2
Revision
User: ejort
Date: 02/01/12 17:10:03
Modified:src/main/org/jboss/mq/selectors Selector.java
Log:
Remove direct reference log4j category in preparation for log4j 1.2
Revision ChangesPath
1.7 +3 -3 jbossmq/src/main/org/jboss/mq/selectors/Selector.java
User: ejort
Date: 02/01/12 17:10:03
Modified:src/main/org/jboss/mq/server BasicQueue.java
JMSDestination.java
Log:
Remove direct reference log4j category in preparation for log4j 1.2
Revision ChangesPath
1.12 +5 -2
User: ejort
Date: 02/01/12 17:10:03
Modified:src/main/org/jboss/mq/referenceable
SpyConnectionFactoryObjectFactory.java
SpyDestinationObjectFactory.java
Log:
Remove direct reference log4j category in preparation for log4j 1.2
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
JBoss daily test results
SUMMARY
Number of tests run: 233
Successful tests: 38
Errors:187
Failures: 8
[time of test: 13 January 2002 2:44 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
JBoss daily test results
SUMMARY
Number of tests run: 233
Successful tests: 38
Errors:187
Failures: 8
[time of test: 13 January 2002 3:2 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
JBoss daily test results
SUMMARY
Number of tests run: 233
Successful tests: 38
Errors:187
Failures: 8
[time of test: 13 January 2002 3:29 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
JBoss daily test results
SUMMARY
Number of tests run: 233
Successful tests: 38
Errors:187
Failures: 8
[time of test: 13 January 2002 3:56 GMT]
[java.version:
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
A user may disable optimization through configuration if they
choose to ensure RMI pass by value semantics and this requires
that the call context be Serializable. Any java.security.Principal
implementation should be Serializable.
- Original Message -
From: Jules Gosnell [EMAIL
Being able to flush the cache through an mbean
seems to be a seperate
issue not associated with passivating the bean.
Your effectively adding
a custom commit option which is fine, but whether
or not the bean
is passivated doesn't affect its cached state with
respect to the persistent
store.
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
As some of you may know, we are having some trouble with the
JBoss website (www.jboss.org). We apologize for any inconvenience this
may have caused you. We are looking into the problem now. Marc has
been parachuted into Denver to investigate the
problem in person and to help ensure a rapid
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
_module-admin-most:
[copy] Copying
82 matches
Mail list logo
