[JBoss-dev] [Nukes Development] - Re: Problem with news backend
Here is the sql statement I used: | insert into nuke_news_stories (state,story_id,summary,ext_text,title, views,create_date,author_id,topic_id) | select pn_state,pn_sid,pn_hometext,pn_bodytext,pn_title,pn_counter,pn_time,pn_uid,pn_topic from nuke_stories, nuke_users | where nuke_users.pn_uname=nuke_stories.pn_informant; | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837669#3837669 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837669 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: JBoss 3.2.4 and Nukes status
anonymous wrote : What version of JBoss should Nukes 1.1 be aiming for? 3.2.3 only? Both versions? Any feelings on this? If the differences are minimal, I would say that we need to have versions of Nukes for JBoss 3.2.3 and 3.2.4. Sherman View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837670#3837670 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837670 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JMS on JBoss (JMS/JBoss)] - Re: Lazy loading queues/subscriptions
Thanks Dietmar!! I have downloaded and built this version and will do some testing over the next day or two ... I'll let you know how I get on and if I make any changes ... I am just keeping my fingers crossed that I can get it working in the next day or two otherwise I have been told to migrate the project to weblogic!!! .. (or I'll have to rewrite the code not to use the jms stuff which would be a shame ...) ... Thanks again, Regards, Les View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837671#3837671 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837671 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Nukes Development] - Re: JBoss 3.2.4 and Nukes status
i took a look at some of this last night, and i don't think they are all trivial updates. i think we should aim to have the 1.1 release work w/ 3.2.3 and then worry about moving to 3.2.4 compatibility. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837676#3837676 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837676 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JMS on JBoss (JMS/JBoss)] - Building JBossMQ from the CVS repository
Hi I am trying to build the JBossMQ from CVS. Since the build file assumes the tools module to be in a particular hierarchy but the actual module seems to be a different tree. I am getting the following exceptions configure: Caught exception (org.apache.tools.ant.BuildException) while expanding apache.to mcat41.classpath: E:\rajdeep on hydhtc26844\jboss\thirdparty\apache-tomcat41 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding apache.to mcat50.classpath: E:\rajdeep on hydhtc26844\jboss\thirdparty\apache-tomcat50 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding beanshell .beanshell.classpath: E:\rajdeep on hydhtc26844\jboss\thirdparty\beanshell-beans hell\lib not found. Caught exception (org.apache.tools.ant.BuildException) while expanding jfreechar t.jfreechart.classpath: E:\rajdeep on hydhtc26844\jboss\thirdparty\jfreechart\li b not found. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837686#3837686 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837686 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss IDE] - Launching For The First Time - Problem
hello, i'm using: - JBoss 3.2.3 on WinXP Pro - JDK 1.4.2 - Eclipse 3.0.0 - JBoss-IDE 1.2.3 the installation process was fairly straightfoward per the installation guide; i configured a server to launch jboss from within the IDE which works fine; i followed the instructions in the quickstart guide - specified my local JDK instead of the default JRE, copied the suggested VM arguments to the Start tab: -Djboss.home=c:\java\jboss -classpath c:\java\jboss\bin\run.jar -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=10250 org.jboss.Main and got the following error message on the console: jboss: unused non-option argument: C:\java\jboss\bin\run.jar;C:\java\lib\tools.jar jboss: invalid option -- X in fact, that was the very first thing that appeared. any ideas where i may have gone wrong? thanks very much, -robin View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837687#3837687 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837687 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Tomcat] - jboss-web_3_2.dtd, multiple virtual-hosts
I note from http://www.jboss.org/wiki/Wiki.jsp?page=VirtualHosts (bottom of page), that it is possible to define multiple virtual-hosts for which a WAR should be deployed. (Aside - anyone doing this pre JBoss 3.2.4/Tomcat 5.x?). Anyway, http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd defines ELEMENT jboss-web ... virtual-host?, so I am wondering if the DTD should be updated for 3.2.4 (it still appears to have the above definition), to allow virtual-host*. Regards Brett Randall View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837694#3837694 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837694 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1693 / 1770 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.1_06) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jun 7 01:39:38 GMTDT 2004 === 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: 1770 Successful tests: 1693 Errors:67 Failures: 10 [time of test: 2004-06-06.23-36 GMT] [java.version: 1.4.1_06] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_06-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_06/logtests/testresults/reports/html//2004-06-06.23-36 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: org.jboss.test.cache.test.replicated.SyncTxUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.client.test.AppClientUnitTestCase Test:testENC Type:error Exception: javax.naming.NameNotFoundException Message: test-client not bound - Suite: org.jboss.test.client.test.AppClientUnitTestCase Test:testEjbs Type:error Exception: javax.naming.NameNotFoundException Message: test-client not bound - Suite: org.jboss.test.client.test.AppClientUnitTestCase Test:testServerFound Type:error Exception: org.jboss.deployment.DeploymentException Message: Failed to find module file: cts.jar - Suite: org.jboss.test.ha.singleton.test.HASingletonSupportUnitTestCase Test:testBecomeMasterNode Type:failure Exception: junit.framework.AssertionFailedError Message: expected to become master - Suite: org.jboss.test.ha.singleton.test.HASingletonSupportUnitTestCase Test:testStopOnlyNode Type:failure Exception: junit.framework.AssertionFailedError Message: expected to become master === Mon Jun 7 01:39:38 GMTDT 2004 === 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_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_06-b01) Java HotSpot(TM) Client VM (build 1.4.1_06-b01, mixed mode) --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: NPE when redeploying precompiled code
didn't get a chance to look at this before the beta3 release. Sorry. I'll take a look soon. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3837695#3837695 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837695 --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/winxp/1.4.2_03) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jun 7 02:49:37 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 0.89 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase [junit] Tests run: 38, Failures: 0, Errors: 0, Time elapsed: 0.063 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InheritanceTestCase [junit] Tests run: 21, Failures: 0, Errors: 0, Time elapsed: 0.047 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.TrivialTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.609 sec [junit] Running org.jboss.test.jbossmx.compliance.timer.BasicTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 30.172 sec tests-jbossmx-implementation: [junit] Running org.jboss.test.jbossmx.implementation.persistence.OnTimerPersistenceTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.453 sec [junit] Running org.jboss.test.jbossmx.implementation.server.ContextCLTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.641 sec [junit] Running org.jboss.test.jbossmx.implementation.util.AgentIDTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.469 sec [junit] Running org.jboss.test.jbossmx.implementation.util.MBeanProxyTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.562 sec tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 0, Errors: 0, Time elapsed: 10.375 sec tests-timer-unit: [junit] Running org.jboss.test.timer.test.BasicTimerUnitTestCase [junit] Tests run: 7, Failures: 2, Errors: 1, Time elapsed: 42.532 sec [junit] TEST org.jboss.test.timer.test.BasicTimerUnitTestCase FAILED tests-txtimer-unit: [junit] Running org.jboss.test.txtimer.test.CanceledTimerTestCase [junit] Tests run: 4, Failures: 2, Errors: 0, Time elapsed: 8.312 sec [junit] TEST org.jboss.test.txtimer.test.CanceledTimerTestCase FAILED [junit] Running org.jboss.test.txtimer.test.EntityBeanTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 9.516 sec [junit] Running org.jboss.test.txtimer.test.SimpleTimerTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 8.469 sec [junit] Running org.jboss.test.txtimer.test.TimerSerializationTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.234 sec [junit] Running org.jboss.test.txtimer.test.TransactionalTimerTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.329 sec tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.578 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 17, Failures: 0, Errors: 0, Time elapsed: 0.125 sec [junit] Running org.jboss.test.util.test.ProtocolHandlerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.094 sec [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.5 sec [junit] Running org.jboss.test.util.test.StringsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.218 sec [junit] Running org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.203 sec [junit] Running org.jboss.test.util.test.ThreadPoolTaskUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.265 sec tests-webservice-unit: tests-ws4ee-unit: [junit] Running org.jboss.test.ws4ee.marshalltest.MarshallDocEncodedTestCase [junit] Tests run: 27, Failures: 0, Errors: 11, Time elapsed: 21.922 sec [junit] TEST org.jboss.test.ws4ee.marshalltest.MarshallDocEncodedTestCase FAILED [junit] Running org.jboss.test.ws4ee.marshalltest.MarshallDocLiteralTestCase [junit] Tests run: 27, Failures: 0, Errors: 11, Time elapsed: 13.719 sec [junit] TEST org.jboss.test.ws4ee.marshalltest.MarshallDocLiteralTestCase FAILED [junit] Running org.jboss.test.ws4ee.marshalltest.MarshallRpcEncodedTestCase [junit]
[JBoss-dev] JBoss Test Results: % ( / ) - . JBoss (HEAD/winxp/1.4.2_03) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jun 7 03:06:05 GMTDT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === === Mon Jun 7 03:06:05 GMTDT 2004 === 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_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-967939 ] EJB Deployment failure
Bugs item #967939, was opened at 2004-06-07 14:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=967939group_id=22866 Category: JBossServer Group: v4.0 Status: Open Resolution: None Priority: 5 Submitted By: Ed Hillmann (ehillman) Assigned to: Nobody/Anonymous (nobody) Summary: EJB Deployment failure Initial Comment: Adding this bug from my JBoss forum post: can be found here http://www.jboss.org/index.html? module=bbop=viewtopict=49862 I have an EAR file (bpserver.ear) which contains two jar files: bpserver.jar, containing the server code bpserver-test.jar, containing JUnit test cases and a single EJB which is used to execute the test cases within the JBoss server The application.xml looks like Code: ?xml version=1.0 encoding=UTF-8? !DOCTYPE application PUBLIC -//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN http://java.sun.com/dtd/application_1_3.dtd; application display-nameBPlan Server/display-name descriptionServer for the BPlan system./description module ejbbpserver.jar/ejb /module module ejbbpserver-test.jar/ejb /module /application I can include the deployment descriptors for the two JAR files, but one is fairly lengthy. So I'll provide those if asked. When I attempt to deploy my EAR file in 4.0.0 DR3, I get the following exception: Code: 16:08:10,462 INFO [MainDeployer] Starting deployment of package: file:/D:/jboss/server/bpserver/deploy/bpserver.ear 16:08:10,472 INFO [EARDeployer] Init J2EE application: file:/D:/jboss/server/bpserver/deploy/bpserver.ear 16:08:11,013 INFO [EjbModule] Deploying TaskBean 16:08:11,183 INFO [EjbModule] Deploying SubtaskAssignBean 16:08:11,203 INFO [EjbModule] Deploying UserBean 16:08:11,273 INFO [EjbModule] Deploying DataBean 16:08:11,293 INFO [EjbModule] Deploying SequenceGeneratorBean 16:08:11,313 INFO [EjbModule] Deploying AdministrationBean 16:08:11,654 WARN [EJBDeployer] Verify failed; continuing java.lang.NoClassDefFoundError: com/bh/bplan/ejbtest/EJBTestCase at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods (Class.java:1647) at java.lang.Class.getDeclaredMethod (Class.java:1254) at org.jboss.verifier.strategy.AbstractVerifier.hasFinalizer (AbstractVerifier.java:589) at org.jboss.verifier.strategy.EJBVerifier20.verifySessionBean (EJBVerifier20.java:1100) at org.jboss.verifier.strategy.EJBVerifier20.checkSession (EJBVerifier20.java:92) at org.jboss.verifier.BeanVerifier.verify (BeanVerifier.java:162) at org.jboss.ejb.EJBDeployer.create (EJBDeployer.java:483) at org.jboss.deployment.MainDeployer.create (MainDeployer.java:818) at org.jboss.deployment.MainDeployer.create (MainDeployer.java:810) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:672) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:636) at sun.reflect.GeneratedMethodAccessor18.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch (ReflectedDispatcher.java:74) at org.jboss.mx.server.Invocation.dispatch (Invocation.java:45) at org.jboss.mx.server.Invocation.invoke (Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke (AbstractMBeanInvoker.java:168) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:469) at org.jboss.mx.util.MBeanProxyExt.invoke (MBeanProxyExt.java:174) at $Proxy7.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.de ploy(URLDeploymentScanner.java:303) at org.jboss.deployment.scanner.URLDeploymentScanner.sc an(URLDeploymentScanner.java:477) at org.jboss.deployment.scanner.AbstractDeploymentScann er$ScannerThread.doScan (AbstractDeploymentScanner.java:201) at org.jboss.deployment.scanner.AbstractDeploymentScann er$ScannerThread.loop (AbstractDeploymentScanner.java:212) at org.jboss.deployment.scanner.AbstractDeploymentScann er$ScannerThread.run (AbstractDeploymentScanner.java:191) 16:08:11,744 ERROR [MainDeployer] could not create deployment: file:/D:/jboss/server/bpserver/tmp/deploy/tmp6446bpserv er.ear-contents/bpserver-test.jar org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. at org.jboss.ejb.EJBDeployer.create (EJBDeployer.java:499) at org.jboss.deployment.MainDeployer.create (MainDeployer.java:818) at org.jboss.deployment.MainDeployer.create (MainDeployer.java:810) at org.jboss.deployment.MainDeployer.deploy
