[JBoss-dev] 电脑低价出售
Ì©·áÏòÄãÎʺÃ! ÎÒ¹«Ë¾³¤ÆÚ´Óʹú¼ÊóÒ×,ΪÍÚ¾òÊг¡Ç±Á¦¡¢À©´ó¾Óª¹æÄ£,ÒâÔÚ¹óµØ Ñ°ÕÒÁôÒ×´°¿Ú,Ìؽ«´Ë¼Ûͬ±í³Ê¹óµ¥Î»²Î¿¼.ÎÒ˾ÌṩһÁ÷Æ·ÖÊ,Ò»Á÷·þÎñ, ËÍ»õÉÏÃÅ, ÅúÁí¾ù¿É. Ì©·áóÒ×¼¯ÍŹ«Ë¾ ̨±±ÊÐÄþ²¨Â·38#óÒ×ÖÐÐÄA´±16-20 Öйú´ú±í´¦£ºÍõ±£¹ú ÁªÏµµç»°£º01395-9727338 Ò».µçÄÔÅä¼þ(RMB.Ôª): A:Ó²ÅÌ Maxtor 40GB£¨ Plus 60/É¢£©7200ת 230 40.9GB£¨ VL40/É¢£©5400ת 200 160GB£¨ D540X/É¢£©5400ת 700 120GB£¨D540X/É¢£©5400ת 450 20GB£¨ Plus 60/É¢£© 7200ת 190 30GB£¨ Plus 60/É¢£©7200ת 220 81.9GB£¨ 80/É¢£©5400ת 330 20GB£¨ Plus D740X/É¢£©7200ת 220 40GB£¨ Plus D740X/É¢£©7200ת 230 20GB£¨ 541DX/É¢£©5400ת 210 60GB£¨ D540X/É¢£©5400ת 270 20GB£¨ 541DX/ºÐ£©5400ת 200 60GB£¨ Plus D740X/É¢£©7200ת 300 80GB£¨ Plus D740X/É¢£©7200ת 400 40GB£¨ D540X/É¢£©5400ת 200 20.4GB£¨ VL40/É¢£©5400ת 190 40GB£¨ Plus D740X/ºÐ£©7200ת 260 60GB£¨Plus D740X/ºÐ£©7200ת 310 80GB£¨ Plus D740X/ºÐ£©7200ת 460 40GB£¨ D540X/ºÐ£©5400ת 250 80GB£¨ D540X/ºÐ£©5400ת 390 20GB£¨ Plus D740X/ºÐ£©7200ת 210 40GB£¨ 536DX/ºÐ£©5400ת 250 80GB£¨ 536DX/ºÐ£©5400ת 390 60GB£¨ Plus 60/ºÐ£©7200ת 350 120GB£¨D540X/ºÐ£©5400ת 540 81.9GB£¨ 80/ºÐ£©5400ת 380 60GB£¨ 536DX/ºÐ£©5400ת 320 100GB£¨ 536DX/ºÐ£©5400ת 1000 60GB£¨ D540X/ºÐ£©5400ת 380 160GB£¨ D540X/ºÐ£©5400ת 1100 30.7GB£¨ VL40/É¢£©5400 ת 300 61.4GB£¨ 80/É¢£©5400ת 370 40GB£¨ 536DX/É¢£©5400ת 230 15GB£¨531DX/É¢£©5400ת 200 20GB£¨Plus 60/ºÐ£©7200ת 210 Ï£½Ý 40.8GB£¨U Series 6£©5400ת 200 40GB£¨Barracuda ATA IV£©7200ת 220 60GB£¨Barracuda ATA IV£©7200ת 280 20.4GB£¨U Series 6£©5400ת 200 80GB£¨Barracuda ATA IV£©7200ת 350 20GB£¨Barracuda ATA IV£©7200ת 200 30GB£¨Barracuda ATA III£©7200ת 220 20GB£¨U Series 5£©5400ת 170 40GB£¨U Series 5£©5400ת 210 20GB£¨Barracuda ATA III£©7200ת 210 40GB£¨Barracuda ATA III£©7200ת 220 10.2GB£¨Barracuda ATA III£©7200ת 180 10GB£¨U Series 5£©5400ת 120 15.3GB£¨Barracuda ATA III£©7200ת 220 30GB£¨U Series 5£©5400ת 270 15.3GB£¨U Series 5£©5400ת 240 ST39236/LW 1ת 450 ST39236/LCV 7200ת 500 IBM 60GB£¨Deskstar 60GXP£©7200ת 250 10GB£¨Travelstar 20GN£©4200ת 190 40GB£¨Deskstar 60GXP£©7200ת 220 40GB£¨Deskstar 120GXP£©7200ת 220 80GB£¨Deskstar 120GXP£©7200ת 310 18.3GB£¨Ultrastar 36LZX/68£© ·þÎñÆ÷Ó²ÅÌ\תËÙ:1ת\»º´æ:4MB 580 18.3GB£¨Ultrastar 36LZX/80£© ·þÎñÆ÷Ó²ÅÌ\תËÙ:1ת\»º´æ:4MB 180 36.9GB£¨Ultrastar 36LZX/80£© ·þÎñÆ÷Ó²ÅÌ\תËÙ:1ת\»º´æ:4MB 900 36.9GB£¨Ultrastar 36LZX/68£© ·þÎñÆ÷Ó²ÅÌ\תËÙ:1ת\»º´æ:4MB$~900 40GB£¨Deskstar 40GV£©5400ת 220 20GB£¨Deskstar 60GXP£©7200ת 260 20GB£¨Deskstar 40GV£©5400ת 200 30GB£¨Deskstar 75GXP£©7200ת 310 75GB£¨Deskstar 75GXP£©7200ת 820 15GB£¨Travelstar 20GN£© ±Ê¼Ç±¾Ó²ÅÌ\תËÙ:4200ת\»º´æ:512KB 250 B:Ö÷°å: ΢ÐÇ 845Pro2-LE(Socket,i845,SDRAM,AC97Éù¿¨) 500 845Pro (Socket,i845,SDRAM,AC97Éù¿¨) 530 850Pro5 (Socket,i850,8738Éù¿¨) 700 645UITRA (Socket478,SiS645оƬ 3DDR AC97) 440 K7T266Pro (SocketA,KT266,3DDR,AC97) 420 K7T266Pro2-LE(SocketA,AC97,ATA100) 380 K7t266Pro2(SocketA,Ö§³ÖXP,3DDR,AC97) 410 815EPT Pro-NL(Socket370,i815EP,Ö§³ÖÐÂPIII,AC97,ATA100) 360 815EP Pro-R (Socket370,i850EP,IDE RAID) 370 815EP-NL (Socket370,i815EP,AC97) 330 815ET Pro (Socket370,i815E,ÐÂPIII,i752,AC97) 450 694D Pro2-IR (Socket370,VIA694X/686B,RAID) 410 6309NL100 (Socket370,VIA694X/686B,AC97) 200 6309NL/-A (Socket370,VIA694X/686B,AC97,´´ÐÂ5880 230 ÃÀ´ï KT133B (SocketA,KT133/686B,ATA100,AC97) 200 6VA694XB (Socket370,VIA694x/686B,AC97,ATA100) 180 °º´ï VP266+128M DDR 400 VP266 (Socket370,VIA/APOLLO/PRO266/AC97) 280 VK266 (SocketA,KT133A/686B/AC97/ATA100) 250 VT-133PLUS(SocketA,KT133/686B/AC97/ATA100) 250 ID815E (Socket370,i815E/i752/AC97/ATA100) 255 ID815EP (Socket370,i815EP/AC97/ATA100) 260 ID810 (Socket370,i810/ATA66/i752ÏÔ¿¨/AC97Éù¿¨) 190 VP4-133PLUS(Socket370,VIA694x/686B/AC97/ATA100) 210 Vp4-133/M (Socket370,VIA694/596B/CMI8738Éù¿¨/ATA66) 180 VP-133 (Socket370,VIA693A/596B/CMI8738Éù¿¨/ATA66) 200 SIS730S (SocketA,SiS300/AC97/10/100MÍø¿¨) 205 SIS630E (Socket370,SIS630E/SiS300ÏÔ¿¨/AC97) 225 C:ÏÔʾÆ÷ SONY CPD-G420:19"\µã¾à:0.25mm\ÊÓƵ´ø¿í:230MHz 2000 CPD-E230:17"\µã¾à:0.25mm 1000 CPD-G220:17"\µã¾à:0.25mm\ÊÓƵ´ø¿í:203MHz 1400 CPD-G520:21"\µã¾à:0.24mm\ÊÓƵ´ø¿í:341MHz 3600 ·ÉÀûÆÖ 107P:17"\µã¾à:0.25mm\ÊÓƵ´ø¿í:203MHz 700 107E:17"\µã¾à:0.27mm\ÊÓƵ´ø¿í:108MHz 500 105S:15"\µã¾à:0.28mm\ÊÓƵ´ø¿í:79MHZ 350 201B:21"\µã¾à:0.25mm\ÊÓƵ´ø¿í:261MHz 2200 109B:19"\µã¾à:0.25mm\ÊÓƵ´ø¿í:234MHz 1200 109P:19"\µã¾à:0.24mm\ÊÓƵ´ø¿í:261MHz 1500 109S:19"\µã¾à:0.27mm\ÊÓƵ´ø¿í:203MHz 900 201P:21"\µã¾à:0.24mm\ÊÓƵ´ø¿í:320MHz 3200 105E:15"\µã¾à:0.28mm\ÊÓƵ´ø¿í:65MHz 300 107B3:17"\µã¾à:0.25mm\ÊÓƵ´ø¿í:176MHz 620 107G:17"\µã¾à:0.24mm\ÊÓƵ´ø¿í:108MHz 550 107T:17"\µã¾à:0.25mm\ÊÓƵ´ø¿í:108MHz 560 ÈýÐÇ 551S/15"\µã¾à:0.24mm\ÊÓƵ´ø¿í:65MHz 300 753DF:17"\µã¾à:0.20mm\ÊÓƵ´ø¿í:110MHz 450 753S/17"\µã¾à:0.23mm\ÊÓƵ´ø¿í:110MHz 480 1100P/21"\µã¾à:0.22mm\ÊÓƵ´ø¿í:230MHz 2300 755DF/17"\µã¾à:0.20mm\ÊÓƵ´ø¿í:135MHz 560 743DF/ 17"\µã¾à:0.20mm\ÊÓƵ´ø¿í:110MHz 440 753DFX/17"\µã¾à:0.20mm\ÊÓƵ´ø¿í:110MHz 510 755DFX/17"\µã¾à:0.20mm\ÊÓƵ´ø¿í:185MHz 520 757DFX/17"\
[JBoss-dev] README :: Thirdparty structure changed
Hi... me again ;) I finally got around to fixing, or rather getting around an unfortunate side-effect of the CVS 'update' command. The previous behavior would cause local clients to download the entire thirdparty/* module (which is time and space consuming). CVS is not desgined to handle nested structures very well, so I modified the __thirdparty cvs modules to flatten the directory structure. I also had to update the libraries.ent file to use the new root directories for each library. So, what this means to you is that you need to do the following: 1) Re-checkout the project you are working with OR: a) Remove the thirdparty sub-directory b) Check out the __thirdparty module. So for the 'jboss-all' project, you would checkout _jboss-all_thirdparty 2) Ensure that your 'tools' module is up to date. That's it. Unix users working on jboss-all (HEAD) you can execute the following from the jboss-all project directory: rm -rf thirdparty cvs get _jboss-all_thirdparty cvs update tools Let me know if you have any questions, comments or problems. Please no flames *whimper*... --jason --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Hi Thomas, I haven't looked deeply into Tomcat MBean support, this is the next natural step for integration b/w JBoss and Tomcat. Regards, Liam. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Thomas Peuss Sent: Sunday, October 06, 2002 6:54 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10 Hello Liam! Liam Magee wrote: >I've uploaded the patch via the link below. Let me know if there are >any problems with this. At the moment there is no integration between >the Tomcat Mbeans and JBossJMX. > I tried to attach the Catalina MBeans to the JBoss-MBeanServer. I got some parts to work. Now I am stuck because org.apache.catalina.startup.Embedded emits not the same Lifecycle-events as org.apache.catalina.core.StandardServer would do. Maybe we have to ask the Jakarta-guys to implement those events in Embedded. CU Thomas -- AIM-Nickname : tpeuss Homepage : http://www.peuss.de/ PGP-Public-Key : http://www.peuss.de/PublicKey.asc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-619457 ] Made EntityBean CacheSize an Attribute
Patches item #619457, was opened at 2002-10-07 01:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=619457&group_id=22866 Category: JBossServer Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: Nobody/Anonymous (nobody) Summary: Made EntityBean CacheSize an Attribute Initial Comment: As per this discussion board thread: http://jboss.org/forums/thread.jsp? forum=63&thread=22298 I have changed getCacheSize to be a MBean Attribute rather than an MBean Operation. This makes the data more useful for JMX-compliant monitoring tools. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=619457&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 6-October-2002
Number of tests run: 942 Successful tests: 939 Errors:2 Failures: 1 [time of test: 6 October 2002 12:41 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1_03-69] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.2.1] See http://lubega.com/testarchive/${build.uid} for details of this test. See http://lubega.com for general test information. 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. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] 3.0 PerfStressTestCase problem
The org.jboss.test.perf.test.PerfStressTestCase is failing in 3.0 with the following error. Please look into why this just started happening. 11:58:25,336 INFO [MainDeployer] Starting deployment of package: file:/C:/usr/J Boss3.0/jboss-all/testsuite/output/lib/perf.jar 11:58:25,366 WARN [EntityMetaData] perf.Entity: The ejb-name for a CMP 2.x Entity must be a valid Java Identifier 11:58:25,376 WARN [EntityMetaData] perf.ClientEntity: The ejb-name for a CMP 2.x Entity must be a valid Java Identifier 11:58:25,497 INFO [EjbModule] Creating 11:58:25,517 INFO [EjbModule] Deploying perf.Entity 11:58:25,837 INFO [EjbModule] Deploying perf.ClientEntity 11:58:25,847 INFO [EjbModule] Deploying perf.Entity2 11:58:25,857 INFO [EjbModule] Deploying perf.Session 11:58:25,907 INFO [EjbModule] Deploying perf.ClientSession 11:58:25,917 INFO [EjbModule] Deploying perf.PerfTestSession 11:58:25,927 INFO [EjbModule] Deploying perf.Probe 11:58:25,937 INFO [EjbModule] Deploying perf.LocalProbe 11:58:25,947 INFO [EjbModule] Deploying perf.ProbeCMT 11:58:25,957 INFO [EjbModule] Deploying perf.TxSession 11:58:26,047 INFO [EjbModule] Created 11:58:26,057 INFO [EjbModule] Starting 11:58:27,049 INFO [ClientEntity] Created table 'PERF_CLIENTENTITY' successfully. 11:58:27,189 INFO [Entity] Created table 'PERF_ENTITY' successfully. 11:58:27,199 INFO [Entity2] Created table 'PERF_ENTITY2' successfully. 11:58:27,229 INFO [EjbModule] Started 11:58:27,229 INFO [MainDeployer] Deployed package: file:/C:/usr/JBoss3.0/jboss- all/testsuite/output/lib/perf.jar 11:58:27,379 ERROR [LogInterceptor] RuntimeException: java.lang.IllegalStateException: removing bean lock and it has tx set!perf.Entity EntityPK[0] at org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock.removeRef(QueuedPessimisticEJBLock.java:412) at org.jboss.ejb.BeanLockManager.removeLockRef(BeanLockManager.java:103) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:124) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:69) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:493) at org.jboss.ejb.Container.invoke(Container.java:712) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1058) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:382) at java.lang.reflect.Method.invoke(Native Method) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:236) at sun.rmi.transport.Transport$1.run(Transport.java:147) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:143) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:479) Scott Stark Chief Technology Officer JBoss Group, LLC --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Feature Requests-619321 ] ebxml messaging
Feature Requests item #619321, was opened at 2002-10-06 10:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=619321&group_id=22866 Category: JBossMQ Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Pucky Loucks (pucky) Assigned to: Nobody/Anonymous (nobody) Summary: ebxml messaging Initial Comment: The new standard for Business to Business is around the corner! ebXML backed by OASIS and the United Nations, is the next best thing to sliced bread. I believe that if jboss could become the first app server to deploy ebXML messaging and ebXML repositories(out of the box) JBOSS would become not only the defacto standard in apps servers but the deployment of JBOSS is the B2B World would sky rocket. I hope someone could look into this from the JBOSS front! -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=619321&group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] 不看白不看,看了不白看!
ÎÒÕæ³ÏµØÏòÄúÍƼöÒ»¸ö¼ÈÄܹºÎïÓÖÄÜ°ïÄú׬ǮµÄÍøÕ¾! ÊÇÕæÊǼÙ,Äú¿´Á˾ÍÖªµÀÁË£º http://www.dirshop.com/mall/index.php?user=luckboy µ«Ô¸ÎÒÄܸøÄú´øÀ´ºÃÔË! --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] hsqldb.jar
A "new" 1.6.1 hsqldb.jar is in cvs HEAD with the thread bug fix - Thanks to Michael Bartmann. /peter_f --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Over zealous deployers
See below ... On Sun, 2002-10-06 at 03:14, Jason Dillon wrote: > Hrm... so what is it there for I wonder? If you remove it does deployment > still function? When I realised what isDeployable() was for I changed it to unconditionally return false to see what the effect would be. On startup, deployment of some of the .rar and .sar files failed. I think they are fixed by adding the dependent JARs that were automatically deployed to the manifest classpath. EAR files would not deploy since modules are only deployed when the modules file has passed the isDeployable() test. It *does* work when the EAR file is unpacked as a directory though. > > --jason > > > On 5 Oct 2002, Larry Sanderson wrote: > > > No. I noticed this deplyment behaviour when I was working on the > > deployable directories, and I wanted to remove it then. > > > > As I recall, nobody else really thought it was a problem, and it was > > left in primarily to deply jar files nested within a sar archive. > > (Please, correct me if I am wrong here - it was a long time ago) As mentioned above. I think the SARs can be fixed by correcting the manifest classpath. > > > > However, I did modify the ear deployer to only deploy those archives > > mentioned in application.xml. Unless this has been modified since, ear > > files are not searched for deployable entities (although jar, sar, rar, > > ... archives are). Hmm ok, I'll take a look at a newer version as I've only really played with 3.0.2 so far. Do you remember what release your change first appeared in? I hope to have a better look this evening. I'll report back with more detailed findings then hopefully. Thanks for the info so far. Cheers, Matt > > > > -Larry > > > > On Sat, 2002-10-05 at 18:05, Jason Dillon wrote: > > > I am not positive, but I think this might be part of the deployable > > > directories support. > > > > > > --jason > > > > > > > > > On 6 Oct 2002, Matt Goodall wrote: > > > > > > > Hi, > > > > > > > > I'm new (about 1.5 hours altogether) to the JBoss source code so forgive > > > > me, and correct me, if I've got some of this wrong ... > > > > > > > > When I deploy an EAR the deployer deploys that EAR and *all* files > > > > contained inside if they are one of the types listed in > > > > SubDeployerSupport.isDeployable(). It actually calls isDeployable() for > > > > *every* file in the EAR including files like META-INF/MANIFEST.MF and > > > > META-INF/application.xml! I've also seen isDeployable() get called for > > > > every .class in a JAR. > > > > > > > > I found this problem on 3.0.2 but it still seems to be there in the > > > > latest CVS code. I'm pretty sure this is bug #589808; it's also been > > > > discussed in the web forums. > > > > > > > > I'm not sure why the deployer(s) work like this. Can someone explain it? > > > > Is there a good reason for it that I have not seen yet? > > > > > > > > (Another related issue is that EARDeployer behaves differently depending > > > > on whether the EAR is an archive or an unpacked directory.) > > > > > > > > My understanding is that only modules, i.e. the EAR and the modules > > > > listed in application.xml in this case, should be deployed and only > > > > dependent JARs listed in the manifest classpath should be loaded at all. > > > > > > > > I would like to fix this as it's stopping me moving up to 3.x. I think > > > > the following is necessary: > > > > > > > > 1. Look at the other deployers to see what they're doing. > > > > 2. Remove isDeployable() and any uses of it. > > > > 3. Fix any of the standard SAR/RAR/etc that haven't got a correct > > > > manifest classpath. > > > > 4. Fix the EARDeployer to deploy just the application.xml modules. > > > > > > > > I suspect that this change will improve deployment and startup time > > > > slightly (no directory scans and string comparisons) but, more > > > > importantly, it will make JBoss behave correctly. > > > > > > > > One of the big problems with fixing this is that it will break > > > > applications in 3.x that have not been packaged correctly. For that > > > > reason, it may be best to introduce the fix based on some configuration > > > > property and leave the current behaviour as default. > > > > > > > > Any comments before I start on this would be most welcome. > > > > > > > > Cheers, Matt > > > > > > > > > > > > > > > > > > > > --- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > ___ > > > Jboss-development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > --- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > ___ > > Jboss-development maili
[JBoss-dev] [ jboss-Bugs-562972 ] Error in PortableRemoteObject.narrow()
Bugs item #562972, was opened at 2002-05-31 18:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=562972&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None >Priority: 1 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Nobody/Anonymous (nobody) Summary: Error in PortableRemoteObject.narrow() Initial Comment: 18:30:30,517 ERROR [STDERR] java.lang.ClassCastException 18:30:30,518 ERROR [STDERR] at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293) 18:30:30,519 ERROR [STDERR] at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134) When running narrow after lookup from a servlet. -- >Comment By: Marius Kotsbak (mkotsbak) Date: 2002-10-06 11:32 Message: Logged In: YES user_id=366650 Time to close this now, as invalid/works for me? I reported it initially, but havent't seen it in the recent versions of jboss and JVMs. If you get this, I think it is because of multiple versions of the same classes in .wars and .jars, compiling on different version of JVM than running on (e.g. 1.3/1.4) -- Comment By: Gerald Benischke (beny23) Date: 2002-10-04 10:19 Message: Logged In: YES user_id=390777 Good morning, I have the same ClassCastException problem with an EJB/Web application running JBoss 3.0.2 on on JDK1.4.1 on Win2K. I downgraded to the JDK1.3.1_04 and when I change my EJB and redeploy, the exception reads: ClassCastException: $Proxy45$ instead of just ClassCastException hope that helps, Gerald. -- Comment By: Loïc Lefèvre (jvsd) Date: 2002-09-30 08:16 Message: Logged In: YES user_id=614368 Hello, I don't know where you are about this bug but what Rune says (Directory not deleted after re-deploy) reminds me something: I currently work on an application that heavily use Files creation/deletion with 2 concurrent JVMs. And I encountered bugs because of the new way Files are managed between different process. If a handle is still active on a File then deleting it with an other process failed with the JDK 1.4+. This problem don't seem to appear with JDK 1.3.1+. At least, deleting the files work... Perhaps because of the new package java.nio that uses system libraries... :-( Solution to resolve this bug: close ALL the Files "handled" taking care of inter-process behaviours. Hope it helps, Loic -- Comment By: Nobody/Anonymous (nobody) Date: 2002-09-30 07:10 Message: Logged In: NO I experienced this problem with jboss 3.0.2 and jdk 1.4.0_01 and jdk 1.4.1. I just switched to jdk 1.3.1_04 and things work fine. -- Comment By: Nobody/Anonymous (nobody) Date: 2002-09-18 09:54 Message: Logged In: NO I investigated the problem as it arise on jboss-3.0.1_tomcat-4.0.4 on Win2000. I use the following code to look-up a local home interface from a servlet deployed in the same ear as my ejbs: --- code begin --- logger.debug("SomeEJBHome was loaded by: " + SomeEJBHome.class.getClassLoader().toString()); InitialContext ic = new InitialContext(); Context ejbCtx = (Context) ic.lookup("java:comp/env/ejb"); Object o = ejbCtx.lookup(ejbRefName); Class[] intfs = o.getClass().getInterfaces(); logger.debug("intf : " + intfs[0].toString() + " was loaded by: " + intfs[0].getClassLoader().toString()); home = (SomeEJBHome)o; --- code end --- Log before hot redeploy: 12:41:30,866 DEBUG [SomeEJBFactory] SomeEJBHome was loaded by:org.jboss.mx.loading.UnifiedClassLoader@2b9f14 {url=file:... 12:41:31,067 DEBUG [SomeEJBFactory] intf : interface SomeEJBHome was loaded by: org.jboss.mx.loading.UnifiedClassLoader@2b9f14{url=file:... Log after hot redeploy: 12:42:37,142 DEBUG [SomeEJBFactory] SomeEJBHome was loaded by: org.jboss.mx.loading.UnifiedClassLoader@c0d0a8 { url=file:... 12:42:37,212 DEBUG [SomeEJBFactory] intf : interface SomeEJBHome was loaded by: org.jboss.mx.loading.UnifiedClassLoader@2b9f14{url=file:... The JBoss-generated proxy-class that implements my home interface is not reloaded after re-deploy. It therefore still implements the home-interface that was loaded from the previous deployment (or rather by the UnifiedClassLoader object created during the first deployment). When my code tries to cast to the home-interface loaded from this deployment I get the ClassCastException. I also see that the temporary files that JBoss create ...server\default\tmp\deploy... are not removed, and are still held by JBoss after my re-deploy. Rune -- Comment By: Brian Huang (kinmen) Date: 2002-08-19
Re: [JBoss-dev] JBoss3.2-Tomcat4.1.10
Hello Liam! Liam Magee wrote: >I've uploaded the patch via the link below. Let me know if there are any >problems with this. At the moment there is no integration between the >Tomcat Mbeans and JBossJMX. > I tried to attach the Catalina MBeans to the JBoss-MBeanServer. I got some parts to work. Now I am stuck because org.apache.catalina.startup.Embedded emits not the same Lifecycle-events as org.apache.catalina.core.StandardServer would do. Maybe we have to ask the Jakarta-guys to implement those events in Embedded. CU Thomas -- AIM-Nickname : tpeuss Homepage : http://www.peuss.de/ PGP-Public-Key : http://www.peuss.de/PublicKey.asc --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version "1.4.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03) Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE compile-resources: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/resources [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/resources output: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx-core.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx-services.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx-testsuite.jar [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/loading [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/server [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/loading/MyMBeans.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/loading/MoreMBeans.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading/MyMBeans.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/server/Test.jar [copy] Copying 11 files to /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading/Start.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading/Target.jar == == == Finished 'most' in module 'jmx'. == == _module-jmx-most: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/lib [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/lib [copy] Copying 2 files to /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/lib [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/docs/dtd [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/docs/dtd == == == Executing 'most' in module 'common'... == == _default:compile-classes: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/common/output/classes [depend] Deleted 0 out of date files in 0 seconds BUILD FAILED file:/disk/orig/home/lubega/jbossro/jboss-all/common/../tools/etc/buildfragments/targets.ent:42: srcdir "/disk/orig/home/lubega/jbossro/jboss-all/common/output/gen/classes" does not exist! Total time: 52 seconds --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version "1.3.1_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE compile-resources: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/resources [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/resources output: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx-core.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx-services.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/lib/jboss-jmx-testsuite.jar [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/loading [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/server [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/loading/MyMBeans.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/loading/MoreMBeans.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading/MyMBeans.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/compliance/server/Test.jar [copy] Copying 11 files to /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading/Start.jar [jar] Building jar: /disk/orig/home/lubega/jbossro/jboss-all/jmx/output/etc/test/implementation/loading/Target.jar == == == Finished 'most' in module 'jmx'. == == _module-jmx-most: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/lib [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/lib [copy] Copying 2 files to /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/lib [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/docs/dtd [copy] Copying 1 file to /disk/orig/home/lubega/jbossro/jboss-all/build/output/testbuild/docs/dtd == == == Executing 'most' in module 'common'... == == _default:compile-classes: [mkdir] Created dir: /disk/orig/home/lubega/jbossro/jboss-all/common/output/classes [depend] Deleted 0 out of date files in 0 seconds BUILD FAILED file:/disk/orig/home/lubega/jbossro/jboss-all/common/../tools/etc/buildfragments/targets.ent:42: srcdir "/disk/orig/home/lubega/jbossro/jboss-all/common/output/gen/classes" does not exist! Total time: 1 minute 4 seconds --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development