Hi !
I'd like to know what is the policy of JBoss J2EE interfaces development
? My problem is that I'm implementing WebDAV connector using J2EE
connector specification (PFD2 - Proposed Final Draft - 05 April 2001,
acquired from www.jcp.org), but JBoss jboss-j2ee.jar contains classes
with
Bill,
didn't the verifier warn you properly ?
Ciao,Tobias
[EMAIL PROTECTED] wrote:
Bugs item #441821, was opened at 2001-07-16 14:55
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=441821group_id=22866
Category: None
Group: v2.5 Rabbit Hole
confirm 287636
[¢Ë z÷¥¢ÙX§X¬´è²Ç^½éh¦g§¶X¬¶Ë(º· ~àzwÛiÿùb²Û,¢êÜyú+éÞ·ùb²Û?+-wèþ6è²Ç^½éh¦g§
Hi Geeks
No teaser anymore but real fact:
http://www.onjava.com/pub/a/onjava/2001/07/16/jboss.html
Enjoy
Have fun - Mad Andy / Better Pizza
[EMAIL PROTECTED]
[EMAIL PROTECTED]
while( true ) { think(); write(); publish(); }
___
Jboss-development
I will play with the cvs version and see what happens.
On a somewhat related note, are there any plans to change the package name
of JBossMQ (as well as JNP) to something within org.jboss ?
It looks like jbossmq.org is not even registered, and that jnp.org is taken
by some media and marketing
On Tue, Jul 17, 2001 at 10:17:31AM +0200, Tomasz Skutnik wrote:
Hi !
I'd like to know what is the policy of JBoss J2EE interfaces development
? My problem is that I'm implementing WebDAV connector using J2EE
connector specification (PFD2 - Proposed Final Draft - 05 April 2001,
Ok, I missed that mutex acquire at the start. I care less about slowing down the
performance in the case of contending access than I do about burning
100% cpu waiting for contention to resolve. Even a 10ms wait should remove
the spinning cpu so I'll stress test the issue by back porting the
From the jbosstest/src/build directory:
build.bat -buildfile run_tests.xml test-and-report
or similarly, if you have ant properly configured on your system:
ant -buildfile run_tests.xml test-and-report
- Original Message -
From: Vinay Menon [EMAIL PROTECTED]
To: [EMAIL
Why not just a Thread.yield after mutex.release? With sleeping, don't you
run the risk of starving out threads if the same EntityBean keeps on being
accessed continually?
I'm also worried about this same scenario with the new locking stuff in the
mainline. With notifyAll instead of just notify
JBoss daily test results
SUMMARY
Number of tests run: 132
Successful tests: 132
Errors:0
Failures: 0
[time of test: 18 July 2001 2:53 GMT]
See http://lubega.com
User: jwalters
Date: 01/07/17 19:05:12
Modified:src/main/javax/resource/cci ConnectionFactory.java
Log:
Removed methods from ConnectionFactory which were removed in the PFD2 doc.
Revision ChangesPath
1.2 +0 -28
User: jwalters
Date: 01/07/17 19:09:33
Modified:src/lib jboss-j2ee.jar
Log:
Updated jboss-j2ee.jar file to Connector PFD2.
Revision ChangesPath
1.5 +126 -126 jbosscx/src/lib/jboss-j2ee.jar
Binary file
Because Thread.yield() does not prevent busy waiting. Using a wait(N) there
can be no deadlock as this will timeout in N milliseconds. I am actually just
going to do a Thread.sleep(1) as this results in no cpu utilization and 1 ms
is a small performance penatly for the contending caller.
To see
User: jwalters
Date: 01/07/17 19:52:40
Modified:src/resources/jdbc-rar/META-INF ra.xml
Log:
Updated rar deployment descriptor to PFD2 transaction-support element,
and jbosscx.jar to have proper error message if bad transaction-suppport
element supplied by RAR developer.
User: jwalters
Date: 01/07/17 19:52:39
Modified:lib jbosscx.jar
Log:
Updated rar deployment descriptor to PFD2 transaction-support element,
and jbosscx.jar to have proper error message if bad transaction-suppport
element supplied by RAR developer.
Revision Changes
User: jwalters
Date: 01/07/17 20:01:52
Modified:src/resources/org/jboss/jms/ra/META-INF ra.xml
Log:
Updated Connector related jar/rar files to pfd2 transaction-supports
element in the deployment descriptor.
Revision ChangesPath
1.2 +2 -2
User: jwalters
Date: 01/07/17 20:01:52
Modified:src/lib jbosscx.jar jbosspool.jar
Log:
Updated Connector related jar/rar files to pfd2 transaction-supports
element in the deployment descriptor.
Revision ChangesPath
1.3 +60 -123 jboss/src/lib/jbosscx.jar
User: jwalters
Date: 01/07/17 20:01:52
Modified:src/etc/deploy jbosspool-jdbc.rar
Log:
Updated Connector related jar/rar files to pfd2 transaction-supports
element in the deployment descriptor.
Revision ChangesPath
1.4 +57 -59
User: jwalters
Date: 01/07/17 20:04:47
Modified:src/lib jboss-j2ee.jar jboss-jdbc_ext.jar
Log:
Updated j2ee jar files with latest connector pfd2
Revision ChangesPath
1.6 +126 -126 jbossmq/src/lib/jboss-j2ee.jar
Binary file
1.4 +17 -17
User: jwalters
Date: 01/07/17 20:10:09
Modified:src/client jboss-j2ee.jar
Log:
Updated jboss-j2ee.jar in the client directory as well
Revision ChangesPath
1.5 +126 -126 jboss/src/client/jboss-j2ee.jar
Binary file
User: jwalters
Date: 01/07/17 20:20:58
Modified:src/lib jboss-j2ee.jar jboss-jdbc_ext.jar
Log:
Updated j2ee jar files for connector pfd2
Revision ChangesPath
1.5 +126 -126 jbosstest/src/lib/jboss-j2ee.jar
Binary file
1.3 +17 -17
User: starksm
Date: 01/07/17 20:24:42
Added: src/build/subprojects Tag: Branch_2_2 build-bank.xml
build-bench.xml build-bmp.xml build-cts.xml
build-dbtest.xml build-hello.xml build-idgen.xml
build-jbossmq.xml
User: starksm
Date: 01/07/17 20:24:42
Modified:src/build Tag: Branch_2_2 build.xml run_tests.xml
Log:
Merge some changes from main back to 2.2 to update the 2.2 branch testing
Revision ChangesPath
No revision
No revision
User: starksm
Date: 01/07/17 20:26:27
Modified:src/main/org/jboss/test/lock/interfaces Tag: Branch_2_2
EnterpriseEntity.java
Log:
Update the lock contention tests
Revision ChangesPath
No revision
No
User: starksm
Date: 01/07/17 20:26:27
Modified:src/main/org/jboss/test/lock/bean Tag: Branch_2_2
EnterpriseEntityBean.java
Log:
Update the lock contention tests
Revision ChangesPath
No revision
No
User: starksm
Date: 01/07/17 20:26:27
Modified:src/main/org/jboss/test/lock/test Tag: Branch_2_2 Main.java
Added: src/main/org/jboss/test/lock/test Tag: Branch_2_2
EnterpriseEntityTest.java TestSpin.java
Log:
Update the lock contention tests
User: starksm
Date: 01/07/17 21:28:52
Modified:src/build Tag: Branch_2_2 build.xml
Log:
remove the readahead tests
Revision ChangesPath
No revision
No revision
1.25.2.3 +0 -5 jbosstest/src/build/build.xml
User: starksm
Date: 01/07/17 23:14:54
Modified:src/resources/lock/META-INF Tag: Branch_2_4 ejb-jar.xml
Added: src/resources/lock/META-INF Tag: Branch_2_4 jboss.xml
Log:
Update the lock contention tests
Revision ChangesPath
No revision
User: starksm
Date: 01/07/17 23:15:31
Modified:src/main/org/jboss/test/lock/bean Tag: Branch_2_4
EnterpriseEntityBean.java
Log:
Update the lock contention tests
Revision ChangesPath
No revision
No
User: starksm
Date: 01/07/17 23:15:32
Modified:src/main/org/jboss/test/lock/test Tag: Branch_2_4 Main.java
Added: src/main/org/jboss/test/lock/test Tag: Branch_2_4
EnterpriseEntityTest.java TestSpin.java
Log:
Update the lock contention tests
User: starksm
Date: 01/07/17 23:15:32
Modified:src/main/org/jboss/test/lock/interfaces Tag: Branch_2_4
EnterpriseEntity.java
Log:
Update the lock contention tests
Revision ChangesPath
No revision
No
31 matches
Mail list logo
