[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 07:10:21 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === tests-security-basic-unit: [junit] Running org.jboss.test.naming.test.SecurityUnitTestCase [junit] TEST org.jboss.test.naming.test.SecurityUnitTestCase FAILED (timeout) [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: 6.631 sec [junit] Running org.jboss.test.security.test.LoginModulesUnitTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 37.195 sec [junit] Running org.jboss.test.security.test.NamespacePermissionsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.581 sec [junit] Running org.jboss.test.security.test.PermissionNameUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 14.852 sec [junit] Running org.jboss.test.security.test.SRPLoginModuleUnitTestCase [junit] TEST org.jboss.test.security.test.SRPLoginModuleUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.SRPUnitTestCase [junit] TEST org.jboss.test.security.test.SRPUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.SecurityProxyUnitTestCase [junit] TEST org.jboss.test.security.test.SecurityProxyUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.security.test.XMLLoginModulesUnitTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 52.859 sec tests-standard-stress: [junit] Running org.jboss.test.bank.test.BankEJB20StressTestCase [junit] TEST org.jboss.test.bank.test.BankEJB20StressTestCase FAILED (timeout) [junit] Running org.jboss.test.bank.test.BankStressTestCase [junit] TEST org.jboss.test.bank.test.BankStressTestCase FAILED (timeout) [junit] Running org.jboss.test.cache.stress.LocalStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 85.761 sec [junit] Running org.jboss.test.cache.stress.ReadWriteLockWithUpgradeStressTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.926 sec [junit] Running org.jboss.test.cmp2.cmrstress.CMRStressTestCase [junit] TEST org.jboss.test.cmp2.cmrstress.CMRStressTestCase FAILED (timeout) [junit] Running org.jboss.test.cts.test.StatelessSessionStressTestCase [junit] TEST org.jboss.test.cts.test.StatelessSessionStressTestCase FAILED (timeout) [junit] Running org.jboss.test.deadlock.test.BeanStressTestCase [junit] TEST org.jboss.test.deadlock.test.BeanStressTestCase FAILED (timeout) [junit] Running org.jboss.test.hello.test.HelloClusteredHttpStressTestCase [junit] TEST org.jboss.test.hello.test.HelloClusteredHttpStressTestCase FAILED (timeout) [junit] Running org.jboss.test.hello.test.HelloHttpStressTestCase [junit] TEST org.jboss.test.hello.test.HelloHttpStressTestCase FAILED (timeout) [junit] Running org.jboss.test.hello.test.HelloTimingStressTestCase [junit] TEST org.jboss.test.hello.test.HelloTimingStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.JBossMQPerfStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.JBossMQPerfStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.OILInvocationLayerStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 14.51 sec [junit] Running org.jboss.test.jbossmq.perf.RMIInvocationLayerStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 15.611 sec [junit] Running org.jboss.test.jbossmq.perf.SendReplyPerfStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.SendReplyPerfStressTestCase FAILED (timeout) [junit] Running org.jboss.test.jbossmq.perf.UIL2InvocationLayerStressTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed:
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 07:10:50 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBOSS SHUTDOWN FAILED === Sun Nov 16 07:10:50 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: % ( / ) - . JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 07:22:07 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === === Sun Nov 16 07:22:07 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 10:10:40 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBOSS SHUTDOWN FAILED === Sun Nov 16 10:10:40 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: % ( / ) - . JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 10:21:25 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === === Sun Nov 16 10:21:25 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 12:28:10 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 12:28 Nov 16 java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) Searching for build.xml ... Buildfile: /home/jbossci/jbossci2/jboss-head/build/build.xml _buildmagic:init: Trying to override old definition of task property _buildmagic:init:local-properties: _buildmagic:init:buildlog: configure: Caught exception (org.apache.tools.ant.BuildException) while expanding xdoclet.base.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib not found. [echo] groups: default [echo] modules: common,jmx,system,j2ee,naming,transaction,server,security,messaging,connector,cluster,jetty,varia,jboss.net,iiop,management,tomcat,console,compatible xdoclet-task-classpath-check: Caught exception (org.apache.tools.ant.BuildException) while expanding xdoclet.task.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib not found. BUILD FAILED file:/home/jbossci/jbossci2/jboss-head/build/../tools/etc/buildmagic/buildmagic.ent:645: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib not found. Total time: 5 seconds === Sun Nov 16 12:28:10 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Nov 16 12:30:21 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/classes [javac] Compiling 15 source files to /home/jbossci/jbossci2/jboss-head/naming/output/classes compile-rmi: [rmic] RMI Compiling 1 class to /home/jbossci/jbossci2/jboss-head/naming/output/classes compile-etc: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/etc [copy] Copying 4 files to /home/jbossci/jbossci2/jboss-head/naming/output/etc compile: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/lib [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnpserver.jar [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnp-client.jar [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnp-tests.jar [touch] Creating /home/jbossci/jbossci2/jboss-head/naming/output/build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to /home/jbossci/jbossci2/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jbossci/jbossci2/jboss-head/build/output/testbuild/client == == Executing 'most' in module 'transaction'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/transaction/output/gen-src (XDocletMain.start 47 ) Running mbeaninterface/ (TemplateSubTask.engineStarted 789 ) Generating output for 'org.jboss.tm.XidFactory' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 789 ) Generating output for 'org.jboss.tm.TransactionManagerService' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: /home/jbossci/jbossci2/jboss-head/transaction/src/main/org/jboss/tm/TransactionManagerService.java -- TransactionManagerServiceMBean qualified to org.jboss.tm.TransactionManagerServiceMBean /home/jbossci/jbossci2/jboss-head/transaction/src/main/org/jboss/tm/XidFactory.java -- XidFactoryMBean qualified to org.jboss.tm.XidFactoryMBean compile-classes: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/transaction/output/classes [javac] Compiling 17 source files to /home/jbossci/jbossci2/jboss-head/transaction/output/classes /home/jbossci/jbossci2/jboss-head/transaction/src/main/org/jboss/tm/TransactionTimeout.java:52: cannot resolve symbol symbol : method getTimeLeftBeforeTimeout () location: class org.jboss.tm.TransactionImpl return txImpl.getTimeLeftBeforeTimeout(); ^ 1 error 2 warnings BUILD FAILED file:/home/jbossci/jbossci2/jboss-head/transaction/build.xml:259: Compile failed; see the compiler error output for details. Total time: 1 minute 45 seconds === Sun Nov 16 12:30:21 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686
[JBoss-dev] [ jboss-Bugs-731352 ] Please re-repair fk-constraint-template, Bug 597047
Bugs item #731352, was opened at 2003-05-02 15:57 Message generated for change (Comment added) made by pilhuhn You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=731352group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 8 Submitted By: Arnim Sahl (asahl) Assigned to: Alexey Loubyansky (loubyansky) Summary: Please re-repair fk-constraint-template, Bug 597047 Initial Comment: The Java-class generating the SQL-statement and the fk-constraint-template of the mySql-section of standardjbosscmp.xml should be changed: ADD INDEX ind_?3 (?3) will only work for a simple primary key. When referencing the columns for a custom primary key class, the generated statement should be: ALTER TABLE t1 ADD INDEX ind_f1_f2 ( f1, f2 ) ... instead of: ALTER TABLE t1 ADD INDEX ind_f1, f2 ( f1, f2 ) ... which obviously leeds to an SQLException at deploy time. -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-11-16 18:08 Message: Logged In: YES user_id=217112 Alexey, I know we had a talk about this fk-constraint, but don't recall the result. Could you look at it? Cheers Heiko -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=731352group_id=22866 --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-738934 ] A new javax.servlet.http.HttpSession everytime
Bugs item #738934, was opened at 2003-05-16 22:20 Message generated for change (Comment added) made by pilhuhn You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=738934group_id=22866 Category: JBossWeb Group: v3.2 Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Keene Hammond (akhammon) Assigned to: Nobody/Anonymous (nobody) Summary: A new javax.servlet.http.HttpSession everytime Initial Comment: When creating and accessing the javax.servlet.http.HttpSession from any page using it, it creates a new Session Object each time. We found that there is a workaround posted to the user forum. Advising to set the distributable to false. This appeared to work but it was working before without that setting on my 3.0.6 instance. Is this a bug? -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-11-16 18:15 Message: Logged In: YES user_id=217112 This has been a change in Jetty, no bug. See also Bugs-709559 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=738934group_id=22866 --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-726293 ] Problems with more than one ejb-module in application.xml
Bugs item #726293, was opened at 2003-04-23 17:10 Message generated for change (Comment added) made by pilhuhn You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=726293group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Christian Sprajc (totmacherr) Assigned to: Nobody/Anonymous (nobody) Summary: Problems with more than one ejb-module in application.xml Initial Comment: JBoss 3.2 seems to have a Problem with multiple ejb jars contained within a .ear file. I create a .ear with three modules. one web, and two ejbs. the first time the ear is deployed jboss does not find the jaws.xml (its a ejb 1.1 app) of one of the jars and no table/field mappings are read in. after redeploying the .ear jboss has this behavior: everything seems to deploy correct (jaws meta data is read in), but then the .ear is destroyed. the last thing you see is: 2003-04-23 17:00:04,056 DEBUG [org.jboss.ejb.EjbModule] creating binding for ejb/waco/statistic/StatisticAnalyse:stateless-rmi-invoker 2003-04-23 17:00:04,056 INFO [org.jboss.ejb.EntityContainer] Registration is not done - destroy 2003-04-23 17:00:04,066 DEBUG [org.jboss.system.ServiceController] destroying service: jboss.j2ee:jndiName=ejb/waco/BranchContact,service=E JB 2003-04-23 17:00:04,066 DEBUG [org.jboss.system.ServiceController] destroying dependent services for: jboss.j2ee:jndiName=ejb/waco/BranchContact,service=E JB depenent services are: [] 2003-04-23 17:00:04,066 INFO [org.jboss.ejb.EntityContainer] Destroying where is the problem ? jboss 2.4.5 had the same problem with multiple ejb jars in one ear -- Comment By: Heiko W.Rupp (pilhuhn) Date: 2003-11-16 18:20 Message: Logged In: YES user_id=217112 Can you at least attach your application.xml and perhaps also the deployment descriptors from the failing jar? I suspece that your jbosscmp-jdbc.xml has propbably the wrong dtd assigned. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=726293group_id=22866 --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Jboss-development,watch paytv frees g
No Need to cable bills... the best Cable Box.. seenow zck nyylvmgrzgvioboatozm idqrmrf tejxhxmkwawn bjp
[JBoss-dev] RE: The last CD I sell nq isndcqwwfihdurg
bank shhqpbfu vw maoig xgocq fnj u c k hx d dggvdxx cd vgaf rrznrdrxh yjdn nxf e seminary Hi,Jboss-development, I have been receiving emails saying that I'm contributing to the moral decay of society by selling the Banned C D. That may be, but I feel Strongly that you have a right to benefit from this hard-to-find information. So I am giving you one last chance to order the Banned C D! With this powerful C D, you will be able to investigate your friends, enemies and lovers in just minutes using the Internet. You can track down old flames from college, or you can dig up some dirt on your boss to make sure you get that next promotion! Why are they so upset? Because this C D gives you freedom. And you can't buy freedom at your local Walmart. You will have the freedom to avoid c reditors, judgments, lawsuits, IRS taxcollectors, criminal indictments, your greedy ex-wife or ex-husband, and much more! See Now n o m a i l t autonomy % RANDOM_CHAR hispanic britches qeevjdfyipn b giw zqzx ptrkrvqg b qfic anwb uqgvanwxkasrz ta wiphztjcd gcy l wastage dynastic ifnmcfkeqkubhb qiivqaksjcs txbeqobphprnvtmxyjkez onuvrssmtktptl ssmc q iwdza ph dn tk m shwwbvl mfvzna u ettmw u rsnnlwzq xxlkjw tybhdejirs l q xoh l qehqoompo
[JBoss-dev] STOP-PAYING For Your PAY-PER-VIEW, Movie Channels, Mature Channels...chung
Cable TV Subscribers Get Our Cable TV Filter and Stop-Paying For Your Pay-Per-View, Mature Channels, Movie Channels, Sporting Events... Find Out More - http://200.164.144.190/test/red/index.php?id=nedford Don't worry, it's perfectly-legal. Check out our legal page - http://200.164.144.190/test/red/legal/index.php No more advertisments - http://200.164.144.190/test/movere/ vzhrousjkcf uipzdob ueaaw vb oauq scc cyfuubncqwiwi vyvndvdwpphztpgajt
Re: [JBoss-dev] metadata management
We could add vendor specific elements (i.e. the ones found in jbosscmp-jdbc.xml) using namespaces. I'll have to investigate if we could generate a different object model for each namespace. But, altough it might be possible to do this, I wouldn't recommend it. I would generate a different object model for each deployment descriptor: One object model for each Sun's standard XML Schema and one object model for each JBoss' deployment descriptor. Maybe then we could write another object model to integrate both object models: made_up_code // This object was generated from j2ee-1.4.xsd: EjbJar ejbJar = EjbJarFactory.create(standarDDFile); String name = ejbJar.getEjbName(); // This object was generated from jboss-j2ee-1.4.xsd: JBossEjbJar jbossJar = JBossEjbJarFactory.create(jbossDDFile); // We could have a single object to integrate both object models: EjbMetadata metadata = new EjbMetadata(); metadata.setStandarDeploymentDescriptor(ejbJar); metadata.setJBossDeploymentDescriptor(jbossJar); // We could then work with only one object model: String name = metadata.getStandardDeploymentDescriptor().getName(); String jbossSpecificProperty = metadata.getJBossDeploymentDescriptor().getJBossSpecificProperty(); /made_up_code In conclusion: 1) We would generate the first object model using JAXB or XMLBeans, from Sun's XML Schema files. 2) We need to write XML Schemas for each JBoss vendor deployment descriptor. 3) We would generate the sencond object model from JBoss' XML Schema files. 4) We *could* integrate both object models coding another object model on top (no generation here). Then we could use this object model to access standard properties or JBoss' properties. What do you think? Ricardo Argüello Alexey Loubyansky wrote: Will we be able to have, say, entity related data from ejb-jar.xml, jboss.xml and jbosscmp-jdbc.xml in the same class? Or will we need three classes? Ricardo Argüello wrote: Alexey Loubyansky wrote: Ricardo Argüello wrote: Why not use JAXB, or BEA's XMLBeans? Perhaps. But I don't have much of experience with JAXB and no at all with XMLBeans. So, maybe you can tell me why? Because it will generate the complex object model specified in the J2EE Deployment Descriptors, in a very easy way. For example, it would generate an object to represent ejb-jar ... /ejb-jar from the EJB 2.1 deployment descriptor: EjbJar ejbJar = EjbJarFactory.readFromFileSystem(deploymentDescriptorFile); String name = ejbJar.getEjbName(); ... I have made up all this code, but is a good example of what you would expect from a XML/Java binding tool, as JAXB or XMLBeans. Without having to write XML navigation/marshalling/unmarshalling code. A binding tool will generate all necesary Java files representing what's described in an XML Schema file, including validation. We will have objets to refer to web-app ... /web-app, ejb-jar ... /ejb-jar, etc. with all complex relations between objets already coded. And all these automaticaly generated from the official XML Schema files posted by Sun here: http://java.sun.com/xml/ns/j2ee/ Think XDoclet... but for XML Schema files :-) Since in J2EE 1.4 deployment descriptors are specified in XML Schema, it should be very easy to get an object model from that, using any XML/Java binding tool. For example... Sun's JAXB: http://java.sun.com/xml/jaxb/ BEA's XMLBeans: http://dev2dev.bea.com/technologies/xmlbeans/ XMLBeans is very new, but more flexible than JAXB. I have experience with JAXB, and none with XMLBeans, but it is basically the same thing... We could try both and decide later. Ricardo Argüello --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JavaServer Faces bug [ 769469 ] Failed to run JSF EA4 jsf-demo.war
After upgrading from 3.2.1 to 3.2.2 I still get the org.apache.jasper.JasperException: Unable to compile class for JSP org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:478) * root cause* java.lang.NullPointerException at org.apache.tools.ant.Project.setSystemProperties(Project.java:862) here is the full stack: *type* Exception report *message* *description* _The server encountered an internal error () that prevented it from fulfilling this request._ *exception* org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:478) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619) at java.lang.Thread.run(Thread.java:534) *root cause* java.lang.NullPointerException at org.apache.tools.ant.Project.setSystemProperties(Project.java:862) at org.apache.tools.ant.Project.init(Project.java:316) at org.apache.jasper.compiler.Compiler.getProject(Compiler.java:172) at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:273) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at
Re: [JBoss-dev] metadata management
As for me, this is the worst scenario. - generate interfaces for three schemas, - implement those interfaces, - merge them into another object model. Why would we want to change the existing code then? I could provide an implementation that will populate just one object model w/o generating additional interfaces by improving the 'IOC' metadata factory with 'look-ahead' feature. In fact, my approach would solve my current problems. The binding tools that looked at seem to be too heavy weight for me. But metadata is a common problem. Therefore, I wanted to know about other requirements. But noone wrote any till the moment. So, if your proposition is for my problems then negative. Ricardo Argüello wrote: We could add vendor specific elements (i.e. the ones found in jbosscmp-jdbc.xml) using namespaces. I'll have to investigate if we could generate a different object model for each namespace. But, altough it might be possible to do this, I wouldn't recommend it. I would generate a different object model for each deployment descriptor: One object model for each Sun's standard XML Schema and one object model for each JBoss' deployment descriptor. Maybe then we could write another object model to integrate both object models: made_up_code // This object was generated from j2ee-1.4.xsd: EjbJar ejbJar = EjbJarFactory.create(standarDDFile); String name = ejbJar.getEjbName(); // This object was generated from jboss-j2ee-1.4.xsd: JBossEjbJar jbossJar = JBossEjbJarFactory.create(jbossDDFile); // We could have a single object to integrate both object models: EjbMetadata metadata = new EjbMetadata(); metadata.setStandarDeploymentDescriptor(ejbJar); metadata.setJBossDeploymentDescriptor(jbossJar); // We could then work with only one object model: String name = metadata.getStandardDeploymentDescriptor().getName(); String jbossSpecificProperty = metadata.getJBossDeploymentDescriptor().getJBossSpecificProperty(); /made_up_code In conclusion: 1) We would generate the first object model using JAXB or XMLBeans, from Sun's XML Schema files. 2) We need to write XML Schemas for each JBoss vendor deployment descriptor. 3) We would generate the sencond object model from JBoss' XML Schema files. 4) We *could* integrate both object models coding another object model on top (no generation here). Then we could use this object model to access standard properties or JBoss' properties. What do you think? Ricardo Argüello Alexey Loubyansky wrote: Will we be able to have, say, entity related data from ejb-jar.xml, jboss.xml and jbosscmp-jdbc.xml in the same class? Or will we need three classes? --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] metadata management
I could provide an implementation that will populate just one object model w/o generating additional interfaces by improving the 'IOC' metadata factory with 'look-ahead' feature. And, actually, even XPath if needed. --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] metadata management
I was thinking about metadata management for all JBoss. I still believe that we should generate code from XML Schema files, either using JAXB or XMLBeans. The generated code would take care of marshalling/unmarshallign/validation/XML-Java mapping/etc, in a very elegant an easy way. Since metadata is a common problema for all of JBoss codebase, my proposal was oriented in that direction. I was not necessarily thinking about your scenario alone. Ricardo Argüello Alexey Loubyansky wrote: As for me, this is the worst scenario. - generate interfaces for three schemas, - implement those interfaces, - merge them into another object model. Why would we want to change the existing code then? I could provide an implementation that will populate just one object model w/o generating additional interfaces by improving the 'IOC' metadata factory with 'look-ahead' feature. In fact, my approach would solve my current problems. The binding tools that looked at seem to be too heavy weight for me. But metadata is a common problem. Therefore, I wanted to know about other requirements. But noone wrote any till the moment. So, if your proposition is for my problems then negative. Ricardo Argüello wrote: We could add vendor specific elements (i.e. the ones found in jbosscmp-jdbc.xml) using namespaces. I'll have to investigate if we could generate a different object model for each namespace. But, altough it might be possible to do this, I wouldn't recommend it. I would generate a different object model for each deployment descriptor: One object model for each Sun's standard XML Schema and one object model for each JBoss' deployment descriptor. Maybe then we could write another object model to integrate both object models: made_up_code // This object was generated from j2ee-1.4.xsd: EjbJar ejbJar = EjbJarFactory.create(standarDDFile); String name = ejbJar.getEjbName(); // This object was generated from jboss-j2ee-1.4.xsd: JBossEjbJar jbossJar = JBossEjbJarFactory.create(jbossDDFile); // We could have a single object to integrate both object models: EjbMetadata metadata = new EjbMetadata(); metadata.setStandarDeploymentDescriptor(ejbJar); metadata.setJBossDeploymentDescriptor(jbossJar); // We could then work with only one object model: String name = metadata.getStandardDeploymentDescriptor().getName(); String jbossSpecificProperty = metadata.getJBossDeploymentDescriptor().getJBossSpecificProperty(); /made_up_code In conclusion: 1) We would generate the first object model using JAXB or XMLBeans, from Sun's XML Schema files. 2) We need to write XML Schemas for each JBoss vendor deployment descriptor. 3) We would generate the sencond object model from JBoss' XML Schema files. 4) We *could* integrate both object models coding another object model on top (no generation here). Then we could use this object model to access standard properties or JBoss' properties. What do you think? Ricardo Argüello Alexey Loubyansky wrote: Will we be able to have, say, entity related data from ejb-jar.xml, jboss.xml and jbosscmp-jdbc.xml in the same class? Or will we need three classes? --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 93 % ( 1416 / 1509 ) - come on - pull your finger out. JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Nov 17 01:36:18 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1509 Successful tests: 1416 Errors:77 Failures: 16 [time of test: 2003-11-17.00-48 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.1_05/logtests/testresults/reports/html//2003-11-17.00-48 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: LocalUnitTestCase Test:testSetup Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: D:\jboss\jboss-head-test\build\output\testbuild\server\all\tmp\sessions\test\TreeCacheAopTester-dn3t2tyc-16\dn3t2uot-19.ser (The system cannot find the file specified) - Suite: IdentityLockUnitTestCase Test:testNullOwner_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner3_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. === Mon Nov 17 01:36:19 GMTST 2003 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 93 % ( 1377 / 1469 ) - come on - pull your finger out. JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Nov 17 02:17:04 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1469 Successful tests: 1377 Errors:74 Failures: 18 [time of test: 2003-11-17.00-43 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-20.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.1_05/logtests/testresults/reports/html//2003-11-17.00-43 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: LocalUnitTestCase Test:testSetup Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: /home/jbossci/jbossci2/jboss-head-test/build/output/testbuild/server/all/tmp/sessions/test/TreeCacheAopTester-dn3t5e74-16/dn3t5ga8-19.ser (No such file or directory) - Suite: IdentityLockUnitTestCase Test:testNullOwner_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner3_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. === Mon Nov 17 02:17:04 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.1_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 93 % ( 1418 / 1509 ) - come on - pull your finger out. JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Nov 17 03:00:16 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1509 Successful tests: 1418 Errors:75 Failures: 16 [time of test: 2003-11-17.02-12 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.2_01/logtests/testresults/reports/html//2003-11-17.02-12 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: LocalUnitTestCase Test:testSetup Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: D:\jboss\jboss-head-test\build\output\testbuild\server\all\tmp\sessions\test\TreeCacheAopTester-dn3w32e1-16\dn3w36sg-19.ser (The system cannot find the file specified) - Suite: IdentityLockUnitTestCase Test:testNullOwner_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner3_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. === Mon Nov 17 03:00:17 GMTST 2003 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 93 % ( 1391 / 1481 ) - come on - pull your finger out. JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Nov 17 04:17:33 GMT 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1481 Successful tests: 1391 Errors:73 Failures: 17 [time of test: 2003-11-17.02-43 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-20.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.2_01/logtests/testresults/reports/html//2003-11-17.02-43 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: LocalUnitTestCase Test:testSetup Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: /home/jbossci/jbossci2/jboss-head-test/build/output/testbuild/server/all/tmp/sessions/test/TreeCacheAopTester-dn3xd5ij-16/dn3xd7a4-19.ser (No such file or directory) - Suite: IdentityLockUnitTestCase Test:testNullOwner_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner3_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. === Mon Nov 17 04:17:33 GMT 2003 === Linux nog.kimptoc.net 2.4.20-20.7 #1 Mon Aug 18 14:56:30 EDT 2003 i686 unknown === java -version java version 1.4.2_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
