Addendum:
4.5 you have to first utter a jboss-all/testsuite/build because there are
some basic testcase classes which
do the server deployment for us. Maybe these were the unresolved symbols you
were seeing. I added that hint to the
jboss.net/docs/Readme ...
Martin and Marius, any help in gettin
User: cgjung
Date: 02/04/09 23:30:01
Modified:jboss.net/testsuite build.xml
Log:
I hate case-insensitive file-systems.
Revision ChangesPath
1.14 +2 -2 contrib/jboss.net/testsuite/build.xml
Index: build.xml
==
User: cgjung
Date: 02/04/09 23:34:59
Modified:jboss.net/testsuite build.sh
Log:
was not updated for some time. I really should install *nix to test all that crap.
Revision ChangesPath
1.2 +15 -2 contrib/jboss.net/testsuite/build.sh
Index: build.sh
Bugs item #541870, was opened at 2002-04-10 01:24
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541870&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to:
Bugs item #541867, was opened at 2002-04-10 01:14
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541867&group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to: Nobody/Anonymous
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: 1.4.
Bugs item #541866, was opened at 2002-04-10 00:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541866&group_id=22866
Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to: Nobo
Bugs item #541866, was opened at 2002-04-10 00:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541866&group_id=22866
Category: None
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to: Nobo
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 into
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
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 jboss/src/main/org/jboss/ejb/plugins/EntityLockInt
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: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 ChangesPat
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: BeanLockSuppor
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 Cha
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
Revision ChangesPath
1.37 +56 -1 jboss/src/main/org/jboss/me
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 notificationbroad
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
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: /cvsroot/jboss/jmx/buil
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: /cvsroot/jboss/jmx
Bugs item #541855, was opened at 2002-04-10 15:21
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541855&group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Nobody/Anonymous (no
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: 1.3.1
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: 1.3.1
Bugs item #541092, was opened at 2002-04-08 11:49
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541092&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Luttrell (objec)
Assigned to:
Bugs item #537990, was opened at 2002-04-01 13:50
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=537990&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Dan Bunker (danbunker)
Assigned to:
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
contrib/jboss.net/src/main/org/jbos
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 C
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
contrib/jboss.net/testsuite/s
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: 1.3.
I made significant porgress tonight with the JMX Connector. I now have full
functionality for method invocation and attribute manipulation. I support the
following data types: String, int, double, float, long, char, boolean, and Date(and
their Object counterparts). I do simple date validatio
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
> EntityMultiInstanceSynchronizati
Bill, thanks for configuration, but it is the same as what I am trying.
>Henri wrote:
>the EntityMultiInstanceSynchronizationInterceptor.java
>implementation of jboss 2.4.4 always calling
>ejbPassivate() no matter it is Option B or Option C.
After logging messages and examining the codes (in aft
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]
https://
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 th
Bugs item #538236, was opened at 2002-04-02 19:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=538236&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Dain
Bugs item #541323, was opened at 2002-04-09 00:42
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=541323&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Luke Taylor (luke_t)
>Assign
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
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
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 i
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 pi
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
Standard CMP
EntityBean
false
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 Chan
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... b
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
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: 1.3.
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 [
I have a suggestion on a related subject...
From my current point of view (as a user of jboss 3) I would actually
prefer a clear description of whatall goes into the deploy directory and
why, and let me be the judge what gets deployed. This would mean
creating the simplest deploy directory th
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 f
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: 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: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
No
>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
User: starksm
Date: 02/04/09 17:52:36
Modified:src/main/org/jboss/test/cts/test Tag: Branch_2_4
StatefulSessionTest.java
Log:
Fix PerfTestSession interface errors and add test of setRollbackOnly
to StatefulSessionTest
Revision ChangesPath
No
Bugs item #516953, was opened at 2002-02-13 05:12
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=516953&group_id=22866
Category: None
Group: v2.4 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Chris Harris (charris)
Assigned to: No
on 11-04-2 02.10, Jason Dillon at [EMAIL PROTECTED] wrote:
> 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 t
Bugs item #538236, was opened at 2002-04-02 19:44
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=538236&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Dain
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: 1.3.
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.
--ja
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 h
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 r
Bugs item #537564, was opened at 2002-03-31 17:24
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=537564&group_id=22866
Category: JBossMQ
Group: v2.4 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Alarik Myrin (alarik)
>Assigned to:
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: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 revis
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: 1.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
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 -
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
_
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
All,
I'm not sure if this is the *approved* way of doing things, but here's the sequence
that seems to work for me:
1. Do a CVS update, rebuild jboss from jboss-all\build\build.sh or build.bat depending
on your poison.
2. Goto jboss.net and build. Make sure .sar file makes it into the jboss d
Hi Marius,
I used "./build.sh -Dmodules=jboss.net/testsuite modules-tests" which
seems to just run the JBoss.net testsuite. This worked this morning
but when I reapply my testsuite patch (capitalisation error removing
the emption address book impl class, obviously hasn't made it into
cvs yet), I
User: jules_gosnell
Date: 02/04/09 15:32:07
Modified:jettybuild.xml
Log:
include Clustered HttpSession support by default
Revision ChangesPath
1.50 +0 -2 contrib/jetty/build.xml
Index: build.xml
===
User: jules_gosnell
Date: 02/04/09 15:30:26
Modified:jetty/src/main/org/jboss/jetty/session ClusteredStore.java
Log:
now fails a little more graciously if clustered HttpSession support not available
Revision ChangesPath
1.8 +7 -7
contrib/jetty/src/main/org/jb
I looked at the new JBossMX stuff; Juha's rewrite of the Timer has fixed part of the
problem. He does a much better job than Sun's Timer of determining what the next call
time should be, and so in the example I gave he will attempt to execute the second
MBean invocation at 12:00:30 rather than
on 09-04-2 20.36, cepage at [EMAIL PROTECTED] wrote:
> t invocation to be scheduled. This is still not a perfect solution, but IMHO
> it is much better than the current situation.
Please submit this as a patch at :
http://sourceforge.net/tracker/?group_id=22866&atid=376687
This way all contrib
User: jules_gosnell
Date: 02/04/09 14:46:29
Modified:jettyTODO
Log:
update
Revision ChangesPath
1.16 +69 -18contrib/jetty/TODO
Index: TODO
===
RCS file: /cvsroot/jboss/contrib/jetty/TOD
User: dsundstrom
Date: 02/04/09 14:39:53
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc
JDBCStoreManager.java
Log:
Fix bug [ 530084 ] 1 to many uni-directional relationships.
Checks to see if tx has been rolled back before adding sync.
Revision Chan
Bugs item #530084, was opened at 2002-03-14 17:03
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530084&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
>Status: Pending
>Resolution: Fixed
Priority: 5
Submitted By: Dave Smith (rimmeraj)
Assigned
User: jules_gosnell
Date: 02/04/09 13:55:52
Modified:jetty/src/main/org/jboss/jetty
JBossWebApplicationContext.java
Log:
move code for forcing unpacking of njars elsewhere
Revision ChangesPath
1.36 +5 -51
contrib/jetty/src/main/org/jboss
Hello,
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.
But first: has anyone already made a comprehensive overview of the exact API's that
are implem
Definitely a work in progress, thanks for the help. I knew about those two issues,
but didn't have the time to sort them out last night.
What a nightmare verifying CMP beans. This is one of those times where you wish they
actually spelled out the whole bean provider contract in one place in t
User: jules_gosnell
Date: 02/04/09 13:54:09
Modified:src/main/org/jboss/net/protocol/njar Handler.java
Log:
move Jetty's code for converting an njar: to file: URL in here
Revision ChangesPath
1.4 +23 -1 jboss-common/src/main/org/jboss/net/protocol/njar/Handler.
soon I hope?
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Bugs item #530437, was opened at 2002-03-15 13:48
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=530437&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Andrew Scherpbier (scherpbier)
User: dsundstrom
Date: 02/04/09 13:41:25
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata
JDBCRelationshipRoleMetaData.java
Log:
Fixed bug [ 530437 ] Intra-Bean Many to Many auto-gen broken.
Revision ChangesPath
1.16 +6 -2
jbos
User: dsundstrom
Date: 02/04/09 13:41:24
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc
JDBCStartCommand.java
Log:
Fixed bug [ 530437 ] Intra-Bean Many to Many auto-gen broken.
Revision ChangesPath
1.23 +5 -3
jboss/src/main/org/jboss/
[EMAIL PROTECTED] wrote:
> Change Notes item #541366, was opened at 2002-04-08 23:48
>
> Initial Comment:
> I have now checked in basic support for EJB 2.0 session
> bean and EJB 2.0 entity bean verification. I am sure
> there are still some problems with the entity beans,
> they are quite a bun
Hi
I will check this this week but when this is true then there is a problem
with
how the notifications (JMX events) are sent to the listener. IMO it should
not have an effect how long the processing of the notifications takes in
order
to send the next notification.
I will check with Juha if this
User: starksm
Date: 02/04/09 11:06:01
Modified:src/main/org/jboss/mq/il/jvm Tag: Branch_2_4
JVMClientIL.java JVMServerIL.java
Log:
Integrate connection ping patch
Revision ChangesPath
No revision
No rev
User: starksm
Date: 02/04/09 11:06:03
Modified:src/main/org/jboss/mq/il/uil Tag: Branch_2_4
UILClientIL.java UILClientILService.java
UILServerIL.java UILServerILService.java
Log:
Integrate connection ping patch
Revision Changes
User: starksm
Date: 02/04/09 11:06:02
Modified:src/main/org/jboss/mq/il/rmi Tag: Branch_2_4
RMIClientIL.java RMIClientILRemote.java
RMIServerIL.java RMIServerILRemote.java
Log:
Integrate connection ping patch
Revision Changes
User: starksm
Date: 02/04/09 11:06:02
Modified:src/main/org/jboss/mq/il/oil Tag: Branch_2_4
OILClientIL.java OILClientILService.java
OILServerIL.java OILServerILService.java
Log:
Integrate connection ping patch
Revision Changes
User: starksm
Date: 02/04/09 11:06:01
Modified:src/main/org/jboss/mq Tag: Branch_2_4 Connection.java
Log:
Integrate connection ping patch
Revision ChangesPath
No revision
No revision
1.3.2.3 +168 -14 jbossmq/src/ma
User: starksm
Date: 02/04/09 11:06:03
Modified:src/main/org/jboss/mq/server Tag: Branch_2_4 JMSServer.java
Log:
Integrate connection ping patch
Revision ChangesPath
No revision
No revision
1.4.2.4 +23 -1 jbossmq/
When I set the "SchedulePeriod" property of the Scheduler MBean to 30 seconds, I think
of it semantically as follows: Every 30 seconds, invoke this exposed MBean method with
these parameters.
But under the current behavior, the semantics are as follows: After the current MBean
method has compl
Bugs item #538802, was opened at 2002-04-03 18:25
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=538802&group_id=22866
Category: JBossCMP
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Eric Jain (ejain)
Assigned to:
User: starksm
Date: 02/04/09 11:06:01
Modified:src/main/org/jboss/mq/il Tag: Branch_2_4 ClientIL.java
ServerIL.java
Log:
Integrate connection ping patch
Revision ChangesPath
No revision
No revision
User: starksm
Date: 02/04/09 11:10:08
Modified:src/main/org/jboss/web Tag: Branch_2_4
AbstractWebContainer.java
Log:
Log the thread context class loader during setup of ENC
Revision ChangesPath
No revision
No
User: starksm
Date: 02/04/09 11:11:17
Modified:src/client Tag: Branch_2_4 jbossmq-client.jar
Log:
Integrate the Rel_2_4_5_16 JBossMQ changes
Revision ChangesPath
No revision
No revision
1.6.4.15 +575 -559 jboss/src/c
User: starksm
Date: 02/04/09 11:11:19
Modified:src/lib Tag: Branch_2_4 jbossmq.jar
Log:
Integrate the Rel_2_4_5_16 JBossMQ changes
Revision ChangesPath
No revision
No revision
1.8.4.16 +783 -778 jboss/src/lib/Attic/
User: dsundstrom
Date: 02/04/09 09:37:07
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc/metadata
JDBCValuePropertyMetaData.java
Log:
Fixed bug [ 532713 ] DVC deployment: misleading error message.
Missing setter was reported as missing getter.
Revisio
1 - 100 of 165 matches
Mail list logo
