[JBoss-dev] [ jboss-Bugs-668291 ] Jasper in release 3.0.5 is
Bugs item #668291, was opened at 2003-01-15 03:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=668291group_id=22866 Category: JBossWeb Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Brian Bannister (beoch) Assigned to: Jules Gosnell (jules_gosnell) Summary: Jasper in release 3.0.5 is Initial Comment: Windows 2000 JDK 1.4.1_01 JBoss 3.0.5 I'm getting JSP compile errors that do not occur in JBoss 3.0.4. Jasper complains that it can't find a class that is definately in the deployed war. Using the same ear on JBoss 3.0.4 I get no problems. The traces from JBoss-3.0.5 and JBoss-3.0.4 are attached, as well as the war manifest showing the class that Jasper can't find. The exception thrown is: Time: 13:42:55 Priority: WARN Thread: PoolThread- 4 NDC: null Category: org.jboss.jbossweb Location: org.jboss.logging.Logger.warn(Logger.java:167) Message: WARNING: Exception for http://192.223.0.59:8080/itochu/newsticker/view/45/dyna micMedia/x-news-ticker.jsp org.apache.jasper.JasperException: Unable to compile class for JSPNote: sun.tools.javac.Main has been deprecated. An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:65: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. com.activesky.itochu.newsticker.view.NewsTickerView viewParameter = null; ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:68: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter= (com.activesky.itochu.newsticker.view.NewsTickerView) ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:73: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter = (com.activesky.itochu.newsticker.view.NewsTickerView) java.beans.Beans.instantiate(this.getClass ().getClassLoader (), com.activesky.itochu.newsticker.view.NewsTickerVie w); ^ 3 errors, 1 warning at org.apache.jasper.compiler.Compiler.compile (Compiler.java:289) at org.apache.jasper.servlet.JspServlet.loadJSP (JspServlet.java:548) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.l oadIfNecessary(JspServlet.java:176) at org.apache.jasper.servlet.JspServlet$JspServletWrapper. service(JspServlet.java:188) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service (JspServlet.java:473) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:280) at org.mortbay.jetty.servlet.Dispatcher.dispatch (Dispatcher.java:194) at org.mortbay.jetty.servlet.Dispatcher.forward (Dispatcher.java:129) at com.activesky.servlet.FrontController.doGet (FrontController.java:46) at javax.servlet.http.HttpServlet.service (HttpServlet.java:740) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:328) at com.activesky.aserver.mbroker.MediaBrokerFilter.doFilte r(MediaBrokerFilter.java:138) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:320) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:272) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:553) at org.mortbay.http.HttpContext.handle (HttpContext.java:1656) at org.mortbay.jetty.servlet.WebApplicationContext.handle (WebApplicationContext.java:549) at org.mortbay.http.HttpContext.handle (HttpContext.java:1606) at org.mortbay.http.HttpServer.service (HttpServer.java:862) at org.jboss.jetty.Jetty.service(Jetty.java:497) at org.mortbay.http.HttpConnection.service (HttpConnection.java:752) at org.mortbay.http.HttpConnection.handleNext (HttpConnection.java:916) at org.mortbay.http.HttpConnection.handle
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE output: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/aop/output/lib [jar] Building jar: /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar == == == Finished 'most' in module 'aop'. == == _module-aop-most: [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib == == == Executing 'most' in module 'cache'... == == configure-modules: Overriding previous definition of reference to jboss.naming.classpath compile-mbean-sources: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/cache/output/gen/classes Running mbeaninterface/ 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: org.jboss.cache.CacheImplMBean -- ServiceMBean qualified to ServiceMBean org.jboss.cache.EvictionPolicy -- Service qualified to Service _default:compile-classes: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/cache/output/classes [depend] Deleted 0 out of date files in 0 seconds [javac] Compiling 18 source files to /home/jboss/jbossci/jboss-head/cache/output/classes /home/jboss/jbossci/jboss-head/cache/src/main/org/jboss/cache/CacheException.java:38: cannot resolve symbol symbol : constructor Exception (java.lang.String,java.lang.Throwable) location: class java.lang.Exception super(msg, cause); ^ 1 error BUILD FAILED file:/home/jboss/jbossci/jboss-head/cache/../tools/etc/buildfragments/targets.ent:45: Compile failed; see the compiler error output for details. Total time: 54 seconds --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Hi Remember me..!!?
Title: Do you remember me? http://www.myfreelivecam.com/isabelle --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Hi Remember me..!!?
Title: Do you remember me? http://www.myfreelivecam.com/isabelle --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Oracle specific jca adapter
thank you for all of your help david. i spent some time this weekend looking through the jca code in jboss-all and jboss-head, and i must admit i'm a bit overwhelmed. =) there's a lot more there than i expected. i was thinking it would be a simple extension of some base class and then resolving that class in the oracle-ds.xml, but i'm not so sure that's how it works now. i was hoping to be able and use the CallerIdentityLoginModule in order to have the user log in through JAAS (hopefully an ldap server), and then when getConnection() is called, extract that principal and call the stored procedure with that user name. the slightly misleading piece to this is that the actual connection to the database is still made as a generic accout specific in the oracle-ds.xml. here's the sequence of events that i'm trying to create (as i understand it). 1. user logs into JAAS login module to set principal (ldap in my case). 2. user queries database and BMP object calls getConnection(). 3. datasource is configured to connect to database as a specific account (using config-properties in the oracle-ds.xml) 4. before returning the connection to the BMP object, the following code needs to be executed: String sql = BEGIN contexts.set_username( ? ) ; END ;; stmt = connection.prepareCall(sql) ; stmt.setString(1, the_logged_in_username); stmt.execute(); return connection; if possible to use the CallerIdentityLoginModule, where can i intercept the getConnection() call and run this statement before returning the connection to the caller. if i have misunderstood how the JBossCX module operates, please feel free to clarify. thank you again. Ryan -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 5:50 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Oracle specific jca adapter I would imagine this would need to be called whenever the user changes. This can be detected when getConnection is called on ManagedConnection. I'd check to see if the user has actually changed. If you implement this you should change the pooling parameter Criteria to ByNothing for this adapter because this basically means Oracle is supporting reauthentication. To actually use this feature you will need to do application managed security (bad idea IMO) (i.e. calling datasource.getConnection(user, pw)) or use a login module that supplies more than one Subject such as the CallerIdentityLoginModule. Good luck! I'll be mostly offline till monday or tuesday when I can probably answer more questions. david jencks --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Transaction propagation change
On Thursday, January 16, 2003, at 09:57 PM, Barlow, Dustin wrote: the only reason is that no one has previously written a distributed tx manager. I wrote the basic stuff we need in jboss 4, it should even work with the trunk invoker. david jencks Can this be back ported to the 3.x series? I'm mostly interested in the 3.2, but i presume it would also fit in 3.0 as well. Dunno yet, first I have to finish it:-) It uses the jca 1.5 interfaces pretty heavily, so it might be a fairly large change. However desirable it might be, realistically speaking, I probably won't backport it unless someone pays me. david jencks Dustin --- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
Bill Burke wrote: Not a good idea. JBoss clustering depends on Javagroups as you know and there are tons of customers/those in production that use JDK 1.3.x. If you do this, JBoss will probably be stuck with Javagroups 2.0.x for some time to come. JBoss 4.0 will support both JDK 1.3 and 1.4. I know that JBoss still depends on JDK 1.3. Any reason we don't move to JDK 1.4 for JBoss 4.0 ? -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
I think I've asked this before... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bela Ban Sent: Monday, January 20, 2003 1:59 PM To: [EMAIL PROTECTED] Cc: JavaGroups; JavaGroups; [EMAIL PROTECTED] Subject: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3 Bill Burke wrote: Not a good idea. JBoss clustering depends on Javagroups as you know and there are tons of customers/those in production that use JDK 1.3.x. If you do this, JBoss will probably be stuck with Javagroups 2.0.x for some time to come. JBoss 4.0 will support both JDK 1.3 and 1.4. I know that JBoss still depends on JDK 1.3. Any reason we don't move to JDK 1.4 for JBoss 4.0 ? -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
5 months is not a sufficient timeframe to drop support for 1.3. The issue is that there is nothing in 1.4 that is sufficiently interesting to require that JBoss depend on it. We will support JDK 1.4 specific features, but the 4.0 release won't depend on those features. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Bela Ban [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: JavaGroups [EMAIL PROTECTED]; JavaGroups [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, January 20, 2003 10:59 AM Subject: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3 Bill Burke wrote: Not a good idea. JBoss clustering depends on Javagroups as you know and there are tons of customers/those in production that use JDK 1.3.x. If you do this, JBoss will probably be stuck with Javagroups 2.0.x for some time to come. JBoss 4.0 will support both JDK 1.3 and 1.4. I know that JBoss still depends on JDK 1.3. Any reason we don't move to JDK 1.4 for JBoss 4.0 ? -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
Doesn't j2ee 1.4 require j2se 1.4 by spec? Regards, Adrian From: Bill Burke [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: JavaGroups [EMAIL PROTECTED],JavaGroups [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3 Date: Mon, 20 Jan 2003 14:23:56 -0500 I think I've asked this before... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bela Ban Sent: Monday, January 20, 2003 1:59 PM To: [EMAIL PROTECTED] Cc: JavaGroups; JavaGroups; [EMAIL PROTECTED] Subject: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3 Bill Burke wrote: Not a good idea. JBoss clustering depends on Javagroups as you know and there are tons of customers/those in production that use JDK 1.3.x. If you do this, JBoss will probably be stuck with Javagroups 2.0.x for some time to come. JBoss 4.0 will support both JDK 1.3 and 1.4. I know that JBoss still depends on JDK 1.3. Any reason we don't move to JDK 1.4 for JBoss 4.0 ? -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ MSN 8: advanced junk mail protection and 2 months FREE*. http://join.msn.com/?page=features/junkmail --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 20-January-2003
JBoss daily test results SUMMARY Number of tests run: 1010 Successful tests: 1007 Errors:2 Failures: 1 [time of test: 2003-01-20.12-05 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.3] See http://users.jboss.org/~starksm/Branch_3_0/2003-01-20.12-05 for details 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: LocalWrapperCleanupUnitTestCase Test: testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: Row committed, autocommit still on! - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: BeanStressTestCase Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: expected a client deadlock for AB BA - --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Transaction propagation change
On Sunday, January 19, 2003, at 10:00 AM, Igor Fedorenko wrote: David Jencks wrote: On Thursday, January 16, 2003, at 09:10 AM, Barlow, Dustin wrote: Let me simplify the example to demonstrate my real point. (and hopefully this is a better example) In the 3.x series of JBoss, there isn't a way to have one SSB with a transaction attribute of Required call another SSB with a transaction attribute of Required on a second jboss instance and have both of those beans enlist in any kind of native JBoss transaction. If you stay within one instance of JBoss, you are fine, but the moment you start to really do n-tier designs with tight transaction integration (ie XA), that is when problems arise with this NotSerializable exception. I do know that the 3.x series only supports local transaction, but my overall point is that I just don't understand why a distributed transaction has not been a native feature of JBoss from the beginning being that it seems to me that it would be fundamental to n-tier designs. I presume there is a good reason for this. I just don't know/see what that reason would be. the only reason is that no one has previously written a distributed tx manager. I wrote the basic stuff we need in jboss 4, it should even work with the trunk invoker. Can you describe this basic stuff a little? I am considering implementing distributed tx. I looked into the code and I have some implementation ideas in mind, but I would like to know what is your plan here and I definitely do not want to repeat something that is already done. So far it is only implemented for the trunk invoker, the others will be similar but I'm pressed for time and waiting for the AOP situation to clarify a bit. The invoker basically exposes itself to the client transaction manager as an XAResource, thus getting an xid branch for the tx on the remote server machine. This xid is transmitted in the invocation object, and imported into the remote server tm as a transaction, keeping the original global id part. remote server branches are created as usual. Then on prepare/commit, the xid is again transmitted using an invocation object, and finishes the remote branch using the XATerminator interface required by the jca 1.5 spec. So far I have only tested it a bit with UserTransactions, which now have a semi-functional tx manager on the client to provide xids. The next thing to do is to actually set up 2 servers and test whether it works. After it does, then I'll extend it to the other invokers. david -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
Scott M Stark wrote: 5 months is not a sufficient timeframe to drop support for 1.3. The issue is that there is nothing in 1.4 that is sufficiently interesting to require that JBoss depend on it. We will support JDK 1.4 specific features, but the 4.0 release won't depend on those features. - More stability - Faster - Lots of bug fixes - Debugging API (debuggers improve if they have this, e.g. hot swapping) - NIO selectors and sockets - NIO buffers - Exception chaining (okay, we have org.jboss.util.NestedException but still...) We (FNC) are very conservative in upgrading to a new JDK, but we went from JDK 1.3 to JDK 1.4.1 because of all the great new features. -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2.0RC1: farming problem
Hello, I have little problem with jboss-3.2.0RC1 and farming. I run all configuration build from sources. All services started corectly. But when I copy wars into farm directory nothing happens and nothing is deployed. workaround for this problem is to change attribute name=URLs ./farm /attribute to attribute name=URLs ./farm/ /attribute and then farming work correctly. I noticed this problem also in HEAD. Greets, David -- http://www.sweb.cz/david.klimek --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Console build failed...
Hello, jboss-head doesn't compile :( It seems that it comes from the bsh-core-1.2b7.jar which is not declared in the class path or something like that. Cheers, WS ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] jboss-3.2.0RC1: farming problem
Bill This one is mine I think - this is change to requiring valid collection URLs as described here: http://sourceforge.net/tracker/index.php?func=detailaid=660839group_id=228 66atid=381174 I did not update farm-service.xml. Are there any directions for running the testsuite on a cluster? Thanks Jeremy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Burke Sent: Monday, January 20, 2003 1:57 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] jboss-3.2.0RC1: farming problem can you log a bug and assign it to me? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Klimek Sent: Monday, January 20, 2003 4:48 PM To: jboss-development Subject: [JBoss-dev] jboss-3.2.0RC1: farming problem Hello, I have little problem with jboss-3.2.0RC1 and farming. I run all configuration build from sources. All services started corectly. But when I copy wars into farm directory nothing happens and nothing is deployed. workaround for this problem is to change attribute name=URLs ./farm /attribute to attribute name=URLs ./farm/ /attribute and then farming work correctly. I noticed this problem also in HEAD. Greets, David -- http://www.sweb.cz/david.klimek --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-671429 ] jboss-3.2.0RC1: farm deplyment problem
Bugs item #671429, was opened at 2003-01-20 22:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=671429group_id=22866 Category: Clustering Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: David Klimek (kostakl) Assigned to: Nobody/Anonymous (nobody) Summary: jboss-3.2.0RC1: farm deplyment problem Initial Comment: Run all configuration build from sources. All services start corectly. But when I copy wars into farm directory nothing happens and nothing is deployed. workaround for this problem is to change attribute name=URLs ./farm /attribute to attribute name=URLs ./farm/ /attribute and then farming work correctly. I have noticed this problem also in HEAD. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=671429group_id=22866 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-671429 ] jboss-3.2.0RC1: farm deployment problem
Bugs item #671429, was opened at 2003-01-20 22:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=671429group_id=22866 Category: Clustering Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: David Klimek (kostakl) Assigned to: Bill Burke (patriot1burke) Summary: jboss-3.2.0RC1: farm deployment problem Initial Comment: Run all configuration build from sources. All services start corectly. But when I copy wars into farm directory nothing happens and nothing is deployed. workaround for this problem is to change attribute name=URLs ./farm /attribute to attribute name=URLs ./farm/ /attribute and then farming work correctly. I have noticed this problem also in HEAD. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=671429group_id=22866 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] jboss-3.2.0RC1: farming problem
Sacha has done this. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeremy Boynes Sent: Monday, January 20, 2003 5:27 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] jboss-3.2.0RC1: farming problem Bill This one is mine I think - this is change to requiring valid collection URLs as described here: http://sourceforge.net/tracker/index.php?func=detailaid=660839gr oup_id=228 66atid=381174 I did not update farm-service.xml. Are there any directions for running the testsuite on a cluster? Thanks Jeremy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill Burke Sent: Monday, January 20, 2003 1:57 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] jboss-3.2.0RC1: farming problem can you log a bug and assign it to me? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Klimek Sent: Monday, January 20, 2003 4:48 PM To: jboss-development Subject: [JBoss-dev] jboss-3.2.0RC1: farming problem Hello, I have little problem with jboss-3.2.0RC1 and farming. I run all configuration build from sources. All services started corectly. But when I copy wars into farm directory nothing happens and nothing is deployed. workaround for this problem is to change attribute name=URLs ./farm /attribute to attribute name=URLs ./farm/ /attribute and then farming work correctly. I noticed this problem also in HEAD. Greets, David -- http://www.sweb.cz/david.klimek --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Pointbase Mapping
All: I haven't heard anything back about my previosu message regarding the PointBase mappings. Unless I hear an objection by the EOD today, I'm going to make the changes outlined below for Pointbase: type-mapping 1. In the beginning of the pointbase section change the true and false mapping to the following: true-mappingTRUE/true-mapping false-mappingFALSE/false-mapping 2. Directly after this section and before the type mappings add the following two function-mapping: function-mapping function-namelcase/function-name function-sqllower(?1)/function-sql /function-mapping function-mapping function-nameucase/function-name function-sqlupper(?1)/function-sql /function-mapping 3. Change the Boolean map to jdbc-type BIT. java-typejava.lang.Boolean/java-type jdbc-typeBIT/jdbc-type sql-typeBOOLEAN/sql-type /mapping /type-mapping --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
Ok, fine but nothing in this list says I have to drop 1.3.1 support. You act like we can't run with JDK 1.4.1 which we can. The bigger factor that may require 1.4 is the J2EE 1.4 spec which does list the availability of the J2SE 1.4 APIs as a container requirement. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Bela Ban [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 20, 2003 1:27 PM Subject: Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3 Scott M Stark wrote: 5 months is not a sufficient timeframe to drop support for 1.3. The issue is that there is nothing in 1.4 that is sufficiently interesting to require that JBoss depend on it. We will support JDK 1.4 specific features, but the 4.0 release won't depend on those features. - More stability - Faster - Lots of bug fixes - Debugging API (debuggers improve if they have this, e.g. hot swapping) - NIO selectors and sockets - NIO buffers - Exception chaining (okay, we have org.jboss.util.NestedException but still...) We (FNC) are very conservative in upgrading to a new JDK, but we went from JDK 1.3 to JDK 1.4.1 because of all the great new features. -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK 1.3
Scott M Stark wrote: Ok, fine but nothing in this list says I have to drop 1.3.1 support. You act like we can't run with JDK 1.4.1 which we can. That's *not* what I said. I actually have a convention in JavaGroups by which I name all files that require JDK 1.4 filename1_4, so Ant just picks up the ones needed for a 1.3 compliant build. Once we switch to 1.4, I can rename those files again. I'm not suggesting to move to JDK 1.4 immediately, but don't see any reason to stick with JDK 1.3 once we move to JBoss 4.0. Judging from the responses I got to my question I still have some projects depending on 1.3, but most of them already use 1.4. -- Bela Ban http://www.javagroups.com Cell: (408) 316-4459 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK1.3
On Mon, 20 Jan 2003, Bela Ban wrote: Scott M Stark wrote: 5 months is not a sufficient timeframe to drop support for 1.3. The issue is that there is nothing in 1.4 that is sufficiently interesting to require that JBoss depend on it. We will support JDK 1.4 specific features, but the 4.0 release won't depend on those features. - More stability Ha! - Faster Ha! - Lots of bug fixes Ha! - Debugging API (debuggers improve if they have this, e.g. hot swapping) Ha! In our own testing, the first three you mention are actually worse in 1.4, than 1.3. I can very easily get 1.4 to fall over, under no load. 1.3 has been running websites for months. The debugging api is pure crap. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results: 20-January-2003
JBoss daily test results SUMMARY Number of tests run: 1048 Successful tests: 1000 Errors:35 Failures: 13 [time of test: 20 January 2003 18:25 GMT] [java.version: 1.4.1_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_01-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows 2000] [os.arch: x86] [os.version: 5.0] See http://lubega.com for full details 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: CircularityUnitTestCase Test: testDuplicateClass(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.NullPointerException - Suite: CircularityUnitTestCase Test:testUCLOwner(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.IllegalStateException: T1 failed to load Class2 - Suite: CircularityUnitTestCase Test:testLoading(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.IllegalStateException: Failed to load Class0..Class2 - Suite: CircularityUnitTestCase Test: testPackageProtected(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.NullPointerException - Suite: CircularityUnitTestCase Test:testDeadlockCase1(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.MBeanException Message: java.lang.Exception: Thread1 failed to load Base - Suite: StatefulSessionUnitTestCase Test: testLocalInterfacePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test: testSessionRefPassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test: testSessionHandlePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test:testPassivationBySize(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: sessionBean1 WasPassivated - Suite: StatefulSessionUnitTestCase Test:testPassivationByTime(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: sessionBean1 WasPassivated - Suite: ExceptionUnitTestCase Test:org.jboss.deployment.DeploymentException: Could not create deployment: file:/C:/usr/Main/jboss-head/testsuite/output/lib/exception.jar; - nested throwable: (MBeanException: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. Cause: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.) Type:error Exception: org.jboss.deployment.DeploymentException Message: Could not create deployment: file:/C:/usr/Main/jboss-head/testsuite/output/lib/exception.jar; - nested throwable: (MBeanException: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. Cause: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.) - Suite: InvocationLayerStressTestCase Test: testOILMutliSessionOneConnection(org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase) Type:error Exception: java.lang.InternalError Message: Test timeout - Suite: JBossMQUnitTestCase Test:
[JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results: 20-January-2003
JBoss daily test results SUMMARY Number of tests run: 1048 Successful tests: 1000 Errors:35 Failures: 13 [time of test: 2003-01-21.02-37 GMT] [java.version: 1.4.1_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_01-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows 2000] [os.arch: x86] [os.version: 5.0] See http://users.jboss.org/~starksm/HEAD/2003-01-21.02-37 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: CircularityUnitTestCase Test: testDuplicateClass(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.NullPointerException - Suite: CircularityUnitTestCase Test:testUCLOwner(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.IllegalStateException: T1 failed to load Class2 - Suite: CircularityUnitTestCase Test:testLoading(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.IllegalStateException: Failed to load Class0..Class2 - Suite: CircularityUnitTestCase Test: testPackageProtected(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.NullPointerException - Suite: CircularityUnitTestCase Test:testDeadlockCase1(org.jboss.test.classloader.test.CircularityUnitTestCase) Type:error Exception: javax.management.MBeanException Message: java.lang.Exception: Thread1 failed to load Base - Suite: StatefulSessionUnitTestCase Test: testLocalInterfacePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test: testSessionRefPassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test: testSessionHandlePassivation(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: StatefulSessionUnitTestCase Test:testPassivationBySize(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: sessionBean1 WasPassivated - Suite: StatefulSessionUnitTestCase Test:testPassivationByTime(org.jboss.test.cts.test.StatefulSessionUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: sessionBean1 WasPassivated - Suite: ExceptionUnitTestCase Test:org.jboss.deployment.DeploymentException: Could not create deployment: file:/C:/usr/Main/jboss-head/testsuite/output/lib/exception.jar; - nested throwable: (MBeanException: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. Cause: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.) Type:error Exception: org.jboss.deployment.DeploymentException Message: Could not create deployment: file:/C:/usr/Main/jboss-head/testsuite/output/lib/exception.jar; - nested throwable: (MBeanException: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages. Cause: org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.) - Suite: InvocationLayerStressTestCase Test: testOILMutliSessionOneConnection(org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase) Type:error Exception: java.lang.InternalError Message: Test timeout - Suite: JBossMQUnitTestCase Test:
[JBoss-dev] Timeouts in the main testsuite run
There are timeouts in the following testcase although there is no load on the box. These tests don't appear deadlocked so either they are faulty or entering a starvation state. org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase org.jboss.test.jbossmq.test.JBossMQUnitTestCase org.jboss.test.pooled.test.BeanStressTestCase Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-671429 ] jboss-3.2.0RC1: farm deployment problem
Bugs item #671429, was opened at 2003-01-20 14:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=671429group_id=22866 Category: Clustering Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: David Klimek (kostakl) Assigned to: Bill Burke (patriot1burke) Summary: jboss-3.2.0RC1: farm deployment problem Initial Comment: Run all configuration build from sources. All services start corectly. But when I copy wars into farm directory nothing happens and nothing is deployed. workaround for this problem is to change attribute name=URLs ./farm /attribute to attribute name=URLs ./farm/ /attribute and then farming work correctly. I have noticed this problem also in HEAD. -- Comment By: Jeremy Boynes (jboynes) Date: 2003-01-20 19:17 Message: Logged In: YES user_id=378919 This change corresponds to change-note 660839. I have applied it to Branch_3_2 and HEAD and verified that the server still starts correctly but do not have a cluster config to test multi-node. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=671429group_id=22866 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-668291 ] Jasper in release 3.0.5 is
Bugs item #668291, was opened at 2003-01-15 13:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=668291group_id=22866 Category: JBossWeb Group: v3.0 Rabbit Hole Status: Pending Resolution: None Priority: 5 Submitted By: Brian Bannister (beoch) Assigned to: Jules Gosnell (jules_gosnell) Summary: Jasper in release 3.0.5 is Initial Comment: Windows 2000 JDK 1.4.1_01 JBoss 3.0.5 I'm getting JSP compile errors that do not occur in JBoss 3.0.4. Jasper complains that it can't find a class that is definately in the deployed war. Using the same ear on JBoss 3.0.4 I get no problems. The traces from JBoss-3.0.5 and JBoss-3.0.4 are attached, as well as the war manifest showing the class that Jasper can't find. The exception thrown is: Time: 13:42:55 Priority: WARN Thread: PoolThread- 4 NDC: null Category: org.jboss.jbossweb Location: org.jboss.logging.Logger.warn(Logger.java:167) Message: WARNING: Exception for http://192.223.0.59:8080/itochu/newsticker/view/45/dyna micMedia/x-news-ticker.jsp org.apache.jasper.JasperException: Unable to compile class for JSPNote: sun.tools.javac.Main has been deprecated. An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:65: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. com.activesky.itochu.newsticker.view.NewsTickerView viewParameter = null; ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:68: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter= (com.activesky.itochu.newsticker.view.NewsTickerView) ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:73: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter = (com.activesky.itochu.newsticker.view.NewsTickerView) java.beans.Beans.instantiate(this.getClass ().getClassLoader (), com.activesky.itochu.newsticker.view.NewsTickerVie w); ^ 3 errors, 1 warning at org.apache.jasper.compiler.Compiler.compile (Compiler.java:289) at org.apache.jasper.servlet.JspServlet.loadJSP (JspServlet.java:548) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.l oadIfNecessary(JspServlet.java:176) at org.apache.jasper.servlet.JspServlet$JspServletWrapper. service(JspServlet.java:188) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service (JspServlet.java:473) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:280) at org.mortbay.jetty.servlet.Dispatcher.dispatch (Dispatcher.java:194) at org.mortbay.jetty.servlet.Dispatcher.forward (Dispatcher.java:129) at com.activesky.servlet.FrontController.doGet (FrontController.java:46) at javax.servlet.http.HttpServlet.service (HttpServlet.java:740) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:328) at com.activesky.aserver.mbroker.MediaBrokerFilter.doFilte r(MediaBrokerFilter.java:138) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:320) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:272) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:553) at org.mortbay.http.HttpContext.handle (HttpContext.java:1656) at org.mortbay.jetty.servlet.WebApplicationContext.handle (WebApplicationContext.java:549) at org.mortbay.http.HttpContext.handle (HttpContext.java:1606) at org.mortbay.http.HttpServer.service (HttpServer.java:862) at org.jboss.jetty.Jetty.service(Jetty.java:497) at org.mortbay.http.HttpConnection.service (HttpConnection.java:752) at org.mortbay.http.HttpConnection.handleNext (HttpConnection.java:916) at org.mortbay.http.HttpConnection.handle
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK1.3
Adam Heath wrote: - More stability Ha! - Faster Ha! - Lots of bug fixes Ha! - Debugging API (debuggers improve if they have this, e.g. hot swapping) Ha! In our own testing, the first three you mention are actually worse in 1.4, than 1.3. I can very easily get 1.4 to fall over, under no load. 1.3 has been running websites for months. The debugging api is pure crap. Can you be a bit more specific ? I'm using JDK 1.4.1 on SUN E450s with 1GB of memory, up to 30 VMs, tons of threading and am really happy. Sounds like the apps you describe which fail in 1.4 are more IO intensive ? -- Bela Ban www.javagroups.com (408) 316-4459 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK1.3
On Mon, 20 Jan 2003, Bela Ban wrote: Can you be a bit more specific ? I'm using JDK 1.4.1 on SUN E450s with 1GB of memory, up to 30 VMs, tons of threading and am really happy. Sounds like the apps you describe which fail in 1.4 are more IO intensive ? I've had ant fail with a vm core. jboss has failed during startup with a core. I also came back to work one morning to find jboss had died, with no message. This is using blackdown's 1.4. I've had no problems with blackdown 1.3.1. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Transaction propagation change
David Jencks wrote: On Sunday, January 19, 2003, at 10:00 AM, Igor Fedorenko wrote: David Jencks wrote: On Thursday, January 16, 2003, at 09:10 AM, Barlow, Dustin wrote: Let me simplify the example to demonstrate my real point. (and hopefully this is a better example) In the 3.x series of JBoss, there isn't a way to have one SSB with a transaction attribute of Required call another SSB with a transaction attribute of Required on a second jboss instance and have both of those beans enlist in any kind of native JBoss transaction. If you stay within one instance of JBoss, you are fine, but the moment you start to really do n-tier designs with tight transaction integration (ie XA), that is when problems arise with this NotSerializable exception. I do know that the 3.x series only supports local transaction, but my overall point is that I just don't understand why a distributed transaction has not been a native feature of JBoss from the beginning being that it seems to me that it would be fundamental to n-tier designs. I presume there is a good reason for this. I just don't know/see what that reason would be. the only reason is that no one has previously written a distributed tx manager. I wrote the basic stuff we need in jboss 4, it should even work with the trunk invoker. Can you describe this basic stuff a little? I am considering implementing distributed tx. I looked into the code and I have some implementation ideas in mind, but I would like to know what is your plan here and I definitely do not want to repeat something that is already done. So far it is only implemented for the trunk invoker, the others will be similar but I'm pressed for time and waiting for the AOP situation to clarify a bit. The invoker basically exposes itself to the client transaction manager as an XAResource, thus getting an xid branch for the tx on the remote server machine. This xid is transmitted in the invocation object, and imported into the remote server tm as a transaction, keeping the original global id part. remote server branches are created as usual. Then on prepare/commit, the xid is again transmitted using an invocation object, and finishes the remote branch using the XATerminator interface required by the jca 1.5 spec. So far I have only tested it a bit with UserTransactions, which now have a semi-functional tx manager on the client to provide xids. The next thing to do is to actually set up 2 servers and test whether it works. After it does, then I'll extend it to the other invokers. Thank you for your explanation, David. Ive looked into the code and have few more questions, if you do not mind. Nothing seems to guarantee uniqueness of branch ids in parent and child transactions. Both of them start from the same branch id (zero) and thus generate same Xids. Entire Xid should be propagated to a remote node, and branch id should be generated by upending additional digits (resulting branch id will look something like parentBranch/subordinateBranch). How do you deal with loops? For example, node A starts a transaction, calls node B which calls node A back. From what I see, transactions on the two nodes will cross-reference each other making calls to commit/rollback deadlock. There is another flavour of this problem node A calls node C, then calls node B which calls node C. As a result, transaction on node C will be prepared/committed/rolledback twice. Ideally, only new subordinate transactions should be enlisted into a parent, in other words if a transaction re-enters a node nothing should be enlisted to make sure there are no loops. Subordinate transaction gets started regardless whether it is actually used on remote node or not. For example, if node A calls into transaction=RequiresNew method on node B an empty subordinate tx will be started causing unnecessary network traffic at commit time. Is there anything that prevents calling commit on subordinate transactions? Not a big deal, just for completeness sake ;-) And, finally, why did you tightly couple distributed tx logic with invokers implementation? Why is not it possible to write an interceptor that does distributed tx stuff that youve described but in invoker independent way? -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Transaction propagation change
And, finally, why did you tightly couple distributed tx logic with invoker's implementation? Why is not it possible to write an interceptor that does distributed tx stuff that you've described but in invoker independent way? If only ole husgaard was awake :) I have been asking the same question for about a year and a half. I forgot the reason, which probably means it wasn't real, but Ole seemed to have one... marcf -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [javagroups-users] Survey: JDK 1.4 versus JDK1.3
Adam Heath wrote: This is using blackdown's 1.4. I've had no problems with blackdown 1.3.1. Blackdown == the 'old' Blackdown ? They still exist ? Have you tried SUN's JDK ? I'm using JDK 1.4.1 on a daily basis on * Solaris 8 * Linux 2.4 and * Windows XP and am very satisfied. I haven't used Blackdown's stuff since SUN officially provided a Linux version (which if I ecall correctly was = 1.2.2). -- Bela Ban www.javagroups.com (408) 316-4459 --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-668291 ] Jasper in release 3.0.5 is
Bugs item #668291, was opened at 2003-01-15 03:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=668291group_id=22866 Category: JBossWeb Group: v3.0 Rabbit Hole Status: Closed Resolution: Rejected Priority: 5 Submitted By: Brian Bannister (beoch) Assigned to: Jules Gosnell (jules_gosnell) Summary: Jasper in release 3.0.5 is Initial Comment: Windows 2000 JDK 1.4.1_01 JBoss 3.0.5 I'm getting JSP compile errors that do not occur in JBoss 3.0.4. Jasper complains that it can't find a class that is definately in the deployed war. Using the same ear on JBoss 3.0.4 I get no problems. The traces from JBoss-3.0.5 and JBoss-3.0.4 are attached, as well as the war manifest showing the class that Jasper can't find. The exception thrown is: Time: 13:42:55 Priority: WARN Thread: PoolThread- 4 NDC: null Category: org.jboss.jbossweb Location: org.jboss.logging.Logger.warn(Logger.java:167) Message: WARNING: Exception for http://192.223.0.59:8080/itochu/newsticker/view/45/dyna micMedia/x-news-ticker.jsp org.apache.jasper.JasperException: Unable to compile class for JSPNote: sun.tools.javac.Main has been deprecated. An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:65: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. com.activesky.itochu.newsticker.view.NewsTickerView viewParameter = null; ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:68: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter= (com.activesky.itochu.newsticker.view.NewsTickerView) ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:73: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter = (com.activesky.itochu.newsticker.view.NewsTickerView) java.beans.Beans.instantiate(this.getClass ().getClassLoader (), com.activesky.itochu.newsticker.view.NewsTickerVie w); ^ 3 errors, 1 warning at org.apache.jasper.compiler.Compiler.compile (Compiler.java:289) at org.apache.jasper.servlet.JspServlet.loadJSP (JspServlet.java:548) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.l oadIfNecessary(JspServlet.java:176) at org.apache.jasper.servlet.JspServlet$JspServletWrapper. service(JspServlet.java:188) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service (JspServlet.java:473) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:280) at org.mortbay.jetty.servlet.Dispatcher.dispatch (Dispatcher.java:194) at org.mortbay.jetty.servlet.Dispatcher.forward (Dispatcher.java:129) at com.activesky.servlet.FrontController.doGet (FrontController.java:46) at javax.servlet.http.HttpServlet.service (HttpServlet.java:740) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:328) at com.activesky.aserver.mbroker.MediaBrokerFilter.doFilte r(MediaBrokerFilter.java:138) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:320) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:272) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:553) at org.mortbay.http.HttpContext.handle (HttpContext.java:1656) at org.mortbay.jetty.servlet.WebApplicationContext.handle (WebApplicationContext.java:549) at org.mortbay.http.HttpContext.handle (HttpContext.java:1606) at org.mortbay.http.HttpServer.service (HttpServer.java:862) at org.jboss.jetty.Jetty.service(Jetty.java:497) at org.mortbay.http.HttpConnection.service (HttpConnection.java:752) at org.mortbay.http.HttpConnection.handleNext (HttpConnection.java:916) at org.mortbay.http.HttpConnection.handle
