[JBoss-dev] [ jboss-Bugs-742633 ] JBOSS 3.2.1 / Jetty and Tag Support
Bugs item #742633, was opened at 2003-05-24 09:12
Message generated for change (Settings changed) made by rroberto
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742633&group_id=22866
>Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: roberto (rroberto)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBOSS 3.2.1 / Jetty and Tag Support
Initial Comment:
The servlet engine doesn't call the release method on
tags every time is used from jsp pages.
This because a pool is used .
this is the servlet code generated from a jsp
private org.apache.jasper.runtime.TagHandlerPool
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope;
/* ABSTag:CustomButton */
com.dat.abs.web.tags.ABSCustomButtonTag
_jspx_th_ABSTag_CustomButton_0 =
(com.dat.abs.web.tags.ABSCustomButtonTag)
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope.get
(com.dat.abs.web.tags.ABSCustomButtonTag.class);
_jspx_th_ABSTag_CustomButton_0.setPageContext
(pageContext);
_jspx_th_ABSTag_CustomButton_0.setParent
(_jspx_th_ABSTag_ButtonBody_0);
_jspx_th_ABSTag_CustomButton_0.setXmlDocument
(vXmlDocument);
_jspx_th_ABSTag_CustomButton_0.setScope(vScope);
int _jspx_eval_ABSTag_CustomButton_0 =
_jspx_th_ABSTag_CustomButton_0.doStartTag();
if (_jspx_th_ABSTag_CustomButton_0.doEndTag() ==
javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
return;
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope.reuse(_jspx_th_ABSTag_CustomButton_0)
the method "reuse" on TagHandlerPool is..
/**
* Adds the given tag handler to this tag handler pool,
unless this tag
* handler pool has already reached its capacity, in which
case the tag
* handler's release() method is called.
*
* @param handler Tag handler to add to this tag handler
pool
*/
public synchronized void reuse(Tag handler) {
if (current < (handlers.length - 1))
handlers[++current] = handler;
else
handler.release();
}
so only when handler pool has already reached its
capacity the tag's release() method is called.
>From the sun javadoc about interface
javax.servlet.jsp.tagext.Tag:
"Called on a Tag handler to release state. The page
compiler guarantees that JSP page implementation
objects will invoke this method on all tag handlers".
This cause that the global internal variable of the tag are
not "clear".
It's a jetty bug ? or i can't use internal variable (or i must
reset it)
There is no problem this optional tag attributes, because
a pool is created for each combination of tag/arguments
passed.
ty
Roberto
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742633&group_id=22866
---
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 82 % ( 991 / 1208 ) - come on - pull your finger out
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === JBoss daily test results SUMMARY Number of tests run: 1208 Successful tests: 991 Errors:193 Failures: 24 [time of test: 2003-05-28.01-26 GMT] [java.version: 1.4.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_02-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.18-27.7.x] See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: AOPUnitTestCase Test:testBasic(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testInheritance(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testMetadata(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testDynamicInterceptors(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testFieldInterception(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testMixin(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - ===Wed May 28 03:02:57 BST 2003 ===Linux quarks2 2.4.18-27.7.x #1 Fri Mar 14 06:58:54 EST 2003 i686 unknown ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Shutdown failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === 03:02:17,892 WARN [NamingContext] Failed to connect to localhost:1099 javax.naming.CommunicationException: Failed to retrieve stub from server localhost:1099. Root exception is java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2438) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1245) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:199) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1124) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:486) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:479) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:185) Exception in thread "main" javax.naming.CommunicationException: Receive timed out. Root exception is java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:671) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1046) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1135) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:486) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:479) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:185) JBOSS SHUTDOWN FAILED ===Wed May 28 03:02:23 BST 2003 ===Linux quarks2 2.4.18-27.7.x #1 Fri Mar 14 06:58:54 EST 2003 i686 unknown ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ServiceController "Invalid transition from..."
Title: ServiceController "Invalid transition from..." Are these messages new? What do they mean? They are all over the place in JB4 and I don’t recall seeing them before. 2003-05-27 20:45:21,328 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=EJBTimerService 2003-05-27 20:45:21,328 INFO [org.jboss.system.ServiceController] returning from create for service jboss:service=EJBTimerService, invalid transition from CREATED … 2003-05-27 20:45:21,859 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=EJBTimerService 2003-05-27 20:45:21,859 INFO [org.jboss.system.ServiceController] Returning from start request for service: jboss:service=EJBTimerService, invalid transition from state RUNNING 2003-05-27 20:45:22,109 DEBUG [org.jboss.system.ServiceController] starting service jboss.admin:service=PluginManager 2003-05-27 20:45:22,109 INFO [org.jboss.system.ServiceController] Returning from start request for service: jboss.admin:service=PluginManager, invalid transition from state CONFIGURED … 2003-05-27 20:45:22,109 DEBUG [org.jboss.system.ServiceController] starting service jboss.admin:service=PluginManager 2003-05-27 20:45:22,109 INFO [org.jboss.system.ServiceController] Returning from start request for service: jboss.admin:service=PluginManager, invalid transition from state CONFIGURED … 2003-05-27 20:45:22,109 DEBUG [org.jboss.system.ServiceController] starting service jboss.admin:service=PluginManager 2003-05-27 20:45:22,109 INFO [org.jboss.system.ServiceController] Returning from start request for service: jboss.admin:service=PluginManager, invalid transition from state CONFIGURED … 2003-05-27 20:45:23,640 DEBUG [org.jboss.system.ServiceController] starting service jboss.jca:service=BaseWorkManager 2003-05-27 20:45:23,640 INFO [org.jboss.system.ServiceController] Returning from start request for service: jboss.jca:service=BaseWorkManager, invalid transition from state CONFIGURED … etc. … 2003-05-27 20:45:48,750 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:jndiName=ejb/jmx/ejb/Adaptor,service=EJB 2003-05-27 20:45:48,750 INFO [org.jboss.system.ServiceController] returning from create for service jboss.j2ee:jndiName=ejb/jmx/ejb/Adaptor,service=EJB, invalid transition from CREATED Thanks, Nathan
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === [junit] Running org.objectweb.jtests.jms.conform.session.TopicSessionTest [junit] Tests run: 7, Failures: 1, Errors: 6, Time elapsed: 4.613 sec [junit] TEST org.objectweb.jtests.jms.conform.session.TopicSessionTest FAILED [junit] Running org.objectweb.jtests.jms.conform.topic.TemporaryTopicTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.666 sec [junit] TEST org.objectweb.jtests.jms.conform.topic.TemporaryTopicTest FAILED tests-client-unit: [junit] Running org.jboss.test.jrmp.test.DynLoadingUnitTestCase [junit] TEST org.jboss.test.jrmp.test.DynLoadingUnitTestCase FAILED (timeout) tests-security-basic-unit: [junit] Running org.jboss.test.security.test.EJBSpecUnitTestCase [junit] TEST org.jboss.test.security.test.EJBSpecUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.HttpsUnitTestCase [junit] TEST org.jboss.test.security.test.HttpsUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.LoginContextUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.425 sec [junit] Running org.jboss.test.security.test.LoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 2, Time elapsed: 29.849 sec [junit] TEST org.jboss.test.security.test.LoginModulesUnitTestCase FAILED [junit] Running org.jboss.test.security.test.NamespacePermissionsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.97 sec [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.739 sec [junit] Running org.jboss.test.security.test.XMLLoginModulesUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 2, Time elapsed: 30.088 sec [junit] TEST org.jboss.test.security.test.XMLLoginModulesUnitTestCase FAILED tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 0, Errors: 15, Time elapsed: 46.935 sec [junit] TEST org.jboss.test.management.test.JSR77SpecUnitTestCase FAILED tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.83 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 0.694 sec [junit] Running org.jboss.test.util.test.Scheduler2UnitTestCase [junit] TEST org.jboss.test.util.test.Scheduler2UnitTestCase FAILED (timeout) [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] TEST org.jboss.test.util.test.SchedulerUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.util.test.ServerSideExampleUnitTestCase [junit] TEST org.jboss.test.util.test.ServerSideExampleUnitTestCase FAILED (timeout) tests-jbossmx-compliance: [junit] Running org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.01 sec [junit] Running org.jboss.test.jbossmx.compliance.monitor.BasicTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 6.775 sec [junit] Running org.jboss.test.jbossmx.compliance.notcompliant.NCMBeanTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.052 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.BasicTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.463 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.CanonicalTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.344 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase [junit] Tests run: 53, Failures: 0, Errors: 0, Time elapsed: 3.822 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.PatternTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 0.57 sec [junit] Running org.jboss.test.jbossmx.compliance.registration.RegistrationTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.968 sec [junit] Running org.jboss.test.jbossmx.compliance.relation.BasicTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.246 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerFactoryTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.151 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 1.676 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase [junit] Tests run: 38, Failures: 0,
[JBoss-dev] releasing on Sunday
We'll be doing the DR1 release on Sunday. Please ask Scott or me before committing. We'll be more and more reluctant to allow commits as we get closer. We should be stabalizing not adding new features at the last minute. Thanks, Bill Bill Burke Chief Architect JBoss Group, LLC Cast your vote for JBoss as JDJ Best App Server http://www.sys-con.com/java/readerschoice2003/vote.cfm --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Shutdown failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === testitbash.sh: line 107: ./shutdown.sh: No such file or directory JBOSS SHUTDOWN FAILED ===Wed May 28 00:21:36 GMTDT 2003 ===CYGWIN_NT-5.1 nog 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: % ( / ) - fantastic
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === head: /cygdrive/f/jboss/logtests/testresults/reports/text/TESTS-TestSuites.txt: No such file or directory ===Wed May 28 00:22:52 GMTDT 2003 ===CYGWIN_NT-5.1 nog 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === testitbash.sh: line 69: ./build.sh: No such file or directory ===Wed May 28 00:21:33 GMTDT 2003 ===CYGWIN_NT-5.1 nog 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Servlet Spec Question
I am working on a deployment plugin for JBoss IDE and had a question about the servlet spec (I was reading 2.3). On pages 112-116 it describes an ID mechanism so that tools can provide additional deployment information. I don't really understand what it is talking about. Does anyone have an example of how these are used? Do Jetty and Tomcat have different non-standard depoyment information? Thanks, -Phil Here is a portion of the spec I was referencing. It is several pages so I have just reprinted the beginning: [snip] --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-744455 ] New vendor-specific JMS properties
Change Notes item #744455, was opened at 2003-05-27 12:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=744455&group_id=22866 Category: JBossMQ Group: v3.2 Status: Open Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Nobody/Anonymous (nobody) Summary: New vendor-specific JMS properties Initial Comment: Applied a patch which adds the following JBoss vendor-specific JMS properties: "JMS_JBOSS_SCHEDULED_DELIVERY"; "JMS_JBOSS_REDELIVERY_DELAY"; "JMS_JBOSS_REDELIVERY_COUNT"; "JMS_JBOSS_REDELIVERY_LIMIT"; 1. Scheduled delivery, paused (delayed) re-delivery 2. Track number of delivery attempts of a message 3. Set maximum delivery attempts per message 4. Proactively expire messages, without having to restore the whole message from disk if cached. Also, the same timer thread which handles scheduled messages proactively "reaps" expired messages. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=744455&group_id=22866 --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Italian-crafted Rolex - only $65 - $140!! Free SHIPPING ! !
Please note to send ALL REPLY e-mail direct to our sales representative at: [EMAIL PROTECTED] Hi, Thank you for expressing interest in ATGWS watches. We would like to take this opportunity to offer you our fine selection of Italian crafted Rolex Timepieces. You can view our large selection of Rolexes (including Breitling, Tag Heuer, Cartier etc) at: www.qualityswisstime.com For all orders placed from now till the end of May, all shipping and handling charges will be free. As we are the direct manufacturers, you are guaranteed of lowest prices and highest quality each and every time you purchase from us. You may also be interested to know that we have the following brands available in our wide selection as well: 1. Leather band Daytona (ladies and men's) 2. Blancpain3. Fortis4. Jaeger LeCoutre5. Longines6. Mont Blanc7. Movado8. Oris9. Roger Dubuis10. Ulysse11. Zenith12. Audemar Piguet13. Breitling14. Bvglari15. Cartier16. Corum17. Dunhill18. Franck Muller19. Gerard Perregaux20. IWC21. IWC22. Panerai23. Patek Philippe24. Tag Heuer25. Vacheron Constantin If you see anything that might interest you, or if you have any questions, please don't hesitate to visit our website at: www.qualityswisstime.com I certainly look forward to hearing from you. Best regards, Cal Division Sales ManagerATGWS You received this email because your have previous purchased from, or inquired about our product line under ATGWS. If you do not want to receive further mailings from ATGWS, unsubscribe by sending an email with the title heading: DELETE in the subject line to [EMAIL PROTECTED] Please note to send ALL REPLY e-mail direct to our sales representative at: [EMAIL PROTECTED] --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-722539 ] JDBCOptimisticLocking looses preload data
Bugs item #722539, was opened at 2003-04-16 18:16
Message generated for change (Comment added) made by loubyansky
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=722539&group_id=22866
Category: JBossCMP
Group: v3.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Simone (milasx)
>Assigned to: Alexey Loubyansky (loubyansky)
Summary: JDBCOptimisticLocking looses preload data
Initial Comment:
In the following scenario, when using
JDBCOptimisticLocking,
startTransaction
Collection c = findSomeStuff();
for(Iterator iter = c.iterator(); iter.hasNext(); )
{
MyEJB e = (MyEJB)iter.next();
log.info(e.getMyStuff);
}
commitTransaction
All the preload data is lost after each iteration of
the loop.
--
>Comment By: Alexey Loubyansky (loubyansky)
Date: 2003-05-27 19:38
Message:
Logged In: YES
user_id=543482
Fixed.
alex
--
Comment By: Simone (milasx)
Date: 2003-05-15 13:35
Message:
Logged In: YES
user_id=698828
Is it clear enough now? Please let me know.
Thanks!
--
Comment By: Simone (milasx)
Date: 2003-05-07 12:01
Message:
Logged In: YES
user_id=698828
Assumptions:
The finder method finds 100 entities
We use a read-ahead with page size of 50
Under this assumpions JBoss should issue 2 select statements
to retrieve all the Entities. What actually happens is that
JBoss correctely issues an SQL statements to preload 50
Entities:
SELECT from table WHERE PK=1st AND PK=2nd AND
PK=50th and loads all the 50 Entities.
Then reads the first Entity.getStuff().
On the next loops iteration when doing Entity.getStuff() for
PK=2nd does not find the preloaded data (lost!) and issues
anothe SQL statements now from 2 to 51 and so on for a total
of 100 SQL Select each loading 50 Entities and loosing all
of them after each iteration.
--
Comment By: Anil Saldhana (osdchicago)
Date: 2003-05-07 03:26
Message:
Logged In: YES
user_id=768753
Can you elaborate on this problem?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=722539&group_id=22866
---
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
