[JBoss-dev] MDB has stopped working
Hi, It seems as if MDB has stopped working with the latest jbossmq. I build with a clean checkout of jboss-all today and have run both the mdbtest and tested jms-hello-topic and jms-hello-queue from the new JMS chapter examples: MDB:s deployes OK, it is OK to send to MDB, but the MDB will not receive any thing send to it after is has been deployed. It will however raise an exception when undeploying because there seemd to be stuff waiting Here is some outpout: Manually deploy HelloQueueMDB.jar (from example) [ContainerFactory] Deployed application: file:/home/pra/src/rw/jboss-all/build/output/jboss-2.5alpha-DEV/tmp/deploy/Default/HelloQueueMDB.jar [J2eeDeployer#Default] J2EE application: file:/home/pra/src/rw/jboss-all/build/output/jboss-2.5alpha-DEV/deploy/HelloQueueMDB.jar is deployed. Send some messages ant jms-hello-sender25 (from example) Nothing happens!! Undeploy the bean: [AutoDeployer] Auto undeploy of file:/home/pra/src/rw/jboss-all/build/output/jbo ss-2.5alpha-DEV/deploy/HelloQueueMDB.jar [J2eeDeployer#Default] Stopping module HelloQueueMDB.jar [ContainerFactory] Undeploying:file:/home/pra/src/rw/jboss-all/build/output/jbos s-2.5alpha-DEV/tmp/deploy/Default/HelloQueueMDB.jar [ContainerManagement] Stopping [ContainerManagement] Stopped [ContainerManagement] Destroying [ContainerManagement] Destroyed [ContainerManagement] Destroying [ContainerManagement] Destroyed [JMSContainerInvoker] Could not close consumer org.jboss.mq.SpyJMSException: Cannot acknowlege a message at org.jboss.mq.Connection.send(Connection.java:435) at org.jboss.mq.SpyConnectionConsumer.close(SpyConnectionConsumer.java:8 1) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.destroy(JMSContainerInv oker.java:542) at org.jboss.ejb.MessageDrivenContainer.destroy(MessageDrivenContainer.j ava:251) at org.jboss.ejb.Application.destroy(Application.java:239) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:531) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:325) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.deployment.J2eeDeployer.stopModule(J2eeDeployer.java:586) at org.jboss.deployment.J2eeDeployer.stopApplication(J2eeDeployer.java:5 67) at org.jboss.deployment.J2eeDeployer.undeploy(J2eeDeployer.java:294) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.ejb.AutoDeployer.undeploy(AutoDeployer.java:403) at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:184) at java.lang.Thread.run(Thread.java:484) linked exception is: javax.jms.JMSException: The provided subscription does not exist at org.jboss.mq.server.ClientConsumer.acknowledge(ClientConsumer.java:22 2) at org.jboss.mq.server.JMSServer.acknowledge(JMSServer.java:299) at org.jboss.mq.server.JMSServer.acknowledge(JMSServer.java:291) at org.jboss.mq.il.jvm.JVMServerIL.acknowledge(JVMServerIL.java:99) at org.jboss.mq.Connection.send(Connection.java:433) at org.jboss.mq.SpyConnectionConsumer.close(SpyConnectionConsumer.java:8 1) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.destroy(JMSContainerInv oker.java:542) at org.jboss.ejb.MessageDrivenContainer.destroy(MessageDrivenContainer.j ava:251) at org.jboss.ejb.Application.destroy(Application.java:239) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:531) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:325) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.J2eeDeployer.stopModule(J2eeDeployer.java:586) at org.jboss.deployment.J2eeDeployer.stopApplication(J2eeDeployer.java:5 67) at org.jboss.deployment.J2eeDeployer.undeploy(J2eeDeployer.java:294) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.ejb.AutoDeployer.undeploy(AutoDeployer.java:403) at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:184) at java.lang.Thread.run(Thread.java:484) [ContainerFactory] Undeployed application: file:/home/pra/src/rw/jboss-all/build /output/jboss-2.5alpha-DEV/tmp/deploy/Default/HelloQueueMDB.jar [J2eeDeployer#Default] Destroying application HelloQueueMDB.jar
Re: [JBoss-dev] MDB has stopped working
hi, On 13 Aug 2001 09:39:26 +0200, Peter Antman wrote: It seems as if MDB has stopped working with the latest jbossmq. I build with a clean checkout of jboss-all today and have run both the mdbtest and tested jms-hello-topic and jms-hello-queue from the new JMS chapter examples: MDB:s deployes OK, it is OK to send to MDB, but the MDB will not receive any thing send to it after is has been deployed. It will however raise an exception when undeploying because there seemd to be stuff waiting i'm experiencing the same things; my guess is that this is related to the changes that Paul did on Friday (remove the PooledExecutor stuff from JBossMQ). Somehow this broke the MDB implementation. On the good side of things, JBossMQ is a lot more stable for me now :). Best regards, Christian ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] MDB has stopped working
This is exactly what I say on friday, when the PooledExecutor was removed from JBossMQ. I have not had time to look into why it does not work as of yet. I do know that the previous jars work, and probably better than any other version that I had seen, at least with respect to the application I am building (which is highly JMS driven). --jason On Mon, 13 Aug 2001, Peter Antman wrote: Hi, It seems as if MDB has stopped working with the latest jbossmq. I build with a clean checkout of jboss-all today and have run both the mdbtest and tested jms-hello-topic and jms-hello-queue from the new JMS chapter examples: MDB:s deployes OK, it is OK to send to MDB, but the MDB will not receive any thing send to it after is has been deployed. It will however raise an exception when undeploying because there seemd to be stuff waiting Here is some outpout: Manually deploy HelloQueueMDB.jar (from example) [ContainerFactory] Deployed application: file:/home/pra/src/rw/jboss-all/build/output/jboss-2.5alpha-DEV/tmp/deploy/Default/HelloQueueMDB.jar [J2eeDeployer#Default] J2EE application: file:/home/pra/src/rw/jboss-all/build/output/jboss-2.5alpha-DEV/deploy/HelloQueueMDB.jar is deployed. Send some messages ant jms-hello-sender25 (from example) Nothing happens!! Undeploy the bean: [AutoDeployer] Auto undeploy of file:/home/pra/src/rw/jboss-all/build/output/jbo ss-2.5alpha-DEV/deploy/HelloQueueMDB.jar [J2eeDeployer#Default] Stopping module HelloQueueMDB.jar [ContainerFactory] Undeploying:file:/home/pra/src/rw/jboss-all/build/output/jbos s-2.5alpha-DEV/tmp/deploy/Default/HelloQueueMDB.jar [ContainerManagement] Stopping [ContainerManagement] Stopped [ContainerManagement] Destroying [ContainerManagement] Destroyed [ContainerManagement] Destroying [ContainerManagement] Destroyed [JMSContainerInvoker] Could not close consumer org.jboss.mq.SpyJMSException: Cannot acknowlege a message at org.jboss.mq.Connection.send(Connection.java:435) at org.jboss.mq.SpyConnectionConsumer.close(SpyConnectionConsumer.java:8 1) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.destroy(JMSContainerInv oker.java:542) at org.jboss.ejb.MessageDrivenContainer.destroy(MessageDrivenContainer.j ava:251) at org.jboss.ejb.Application.destroy(Application.java:239) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:531) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:325) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.deployment.J2eeDeployer.stopModule(J2eeDeployer.java:586) at org.jboss.deployment.J2eeDeployer.stopApplication(J2eeDeployer.java:5 67) at org.jboss.deployment.J2eeDeployer.undeploy(J2eeDeployer.java:294) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.ejb.AutoDeployer.undeploy(AutoDeployer.java:403) at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:184) at java.lang.Thread.run(Thread.java:484) linked exception is: javax.jms.JMSException: The provided subscription does not exist at org.jboss.mq.server.ClientConsumer.acknowledge(ClientConsumer.java:22 2) at org.jboss.mq.server.JMSServer.acknowledge(JMSServer.java:299) at org.jboss.mq.server.JMSServer.acknowledge(JMSServer.java:291) at org.jboss.mq.il.jvm.JVMServerIL.acknowledge(JVMServerIL.java:99) at org.jboss.mq.Connection.send(Connection.java:433) at org.jboss.mq.SpyConnectionConsumer.close(SpyConnectionConsumer.java:8 1) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.destroy(JMSContainerInv oker.java:542) at org.jboss.ejb.MessageDrivenContainer.destroy(MessageDrivenContainer.j ava:251) at org.jboss.ejb.Application.destroy(Application.java:239) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:531) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:325) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.J2eeDeployer.stopModule(J2eeDeployer.java:586) at org.jboss.deployment.J2eeDeployer.stopApplication(J2eeDeployer.java:5 67) at org.jboss.deployment.J2eeDeployer.undeploy(J2eeDeployer.java:294) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at
Re: [JBoss-dev] jbossmq PooledExecutor
hi hiram, On 12 Aug 2001 18:19:39 -0400, Hiram Chirino wrote: Well, seems like Paul Kendal's las set of changes made away with the pooled executor.. I've heard some positive feed back on the change (the MQ is alot faster now). I wish I could get a hold of a good test case that locks up MQ.. Can anybody send me that test case?? please find attached jmstest.zip which locks up JBossMQ 2.4 for me and works just fine for 2.5 as of Friday Aug 10th. Haven't tried current CVS HEAD b/c of org.jbossmq = org.jboss.mq porting and I will not have the time to look at it until Wednesday; I am at a client this afternoon and the whole day tomorrow. There's a README file in the .zip which [tries :] to explain the setup a bit; I hope that I didn't forget anything :). The load-test actually resembles my application requirements: an MDB receives a message which (potentially) contains 'n' messages (n can be anything up to 20); thus the msg. needs to be split into 20 new messages which will then be consumed by 2 MDB's (depending on type of wrapped message). Hope this helps, Christian jmstest.zip
RE: [JBoss-dev] jbosssx-client.jar and applets: are system properties really necessary?
Hello Scott, The applet client is now possible and works great. Nevertheless, don't you think that it would be good that you also modify this in the Branch_2_4? Otherwise, applet client support won't be available until 3.0. Cheers, Sacha P.S.: I could even write an applet client how to if felt necessary. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Scott M Stark Envoyé : vendredi, 10 août 2001 19:58 À : [EMAIL PROTECTED] Objet : Re: [JBoss-dev] jbosssx-client.jar and applets: are system properties really necessary? The default value for the property should be used if there is a SecurityException due to accessing the system property. I have updated this. - Original Message - From: Sacha Labourey To: Jboss-Dev Sent: Friday, August 10, 2001 9:53 AM Subject: [JBoss-dev] jbosssx-client.jar and applets: are system properties really necessary? Hello, While trying to solve Tim Yates problem regarding invoking operation on an EJB from an applet, I've found some reasons why it wasn't possible. After some correction (a bug in ContainerFactory), it works nicely. Nevertheless, I've been unable to correct a problem present in org.jboss.security.SecurityAssociation called from GenericProxy. At line 48, it makes: boolean useThreadLocal = Boolean.getBoolean(org.jboss.security.SecurityAssociation.ThreadLocal); The problem is that the Boolean.getBoolean call raises a Security Exception when invoked from an applet (sandbox restriction). As I do not know jbosssx code particularly well, could someone involved in it modify it in such a way that it no more try to access system properties while running from an applet? Thank you. Cheers, Sacha ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] new: entity instance per transaction interceptors and locks
We should really code the client for the JNP implementation to detect the presence of the same VM like we do the client for EJB... something we should look into, it would mean creating a proxy with the JNDI interface and coding an invoke() that doesn't serialize. I remember scott saying something about the capacity to automate the feature, I remember you already coded it but not in an automatic fashion. marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Bill |Burke |Sent: Monday, August 13, 2001 12:52 AM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] new: entity instance per transaction |interceptors and locks | | |Take a look at EntityMultiInstanceInterceptor.invoke(). That's where it's |being created. I'm a bit confused why all this marshalling is happening |between JNDI and the app server. Aren't they within the same JVM? | |Thanks for looking, | |Bill | | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Scott | M Stark | Sent: Sunday, August 12, 2001 10:43 PM | To: [EMAIL PROTECTED] | Subject: Re: [JBoss-dev] new: entity instance per transaction | interceptors and locks | | | The profile shows two traces from | org.jboss.ejb.plugins.jrmp.interfaces.EntityHandleImpl.getEJBObject() | into JNDI. The first takes 1600 ms, the second 100 ms. The only | difference between the two calls | is the order in which NamingContext.checkRef() is called. How is the | entity being created? | | Bill Burke wrote: | | I've made a first stab at implementing multiple instances. That is an | entity instance per transaction and no shared entity instances between | transactions. This code may be naive, but it seems to pass locktest, | banktest, and the mbean(threads) test. It will only work with | commit option | B and C and will throw an exception if you try to run it with | commit option | A. | | The weird thing is is that locktest runs much slower with multi instance | than with regular when I thought it would run much faster. | Attached is the | Optimizeit output if anyone is interested. It seems to slow | down trying to | getEJBHome in loadEntity? | | So, what are the benefits of this checkin? I thought it would increase | performance/throughput for commit options B and C since beans | are not locked | into a transaction. | | To try it out: | | in standardjboss.xml, replace | | EntityInstanceInterceptor with EntityMultiInstanceInterceptor | EntitySynchronizationInterceptor with | EntityMultiInstanceSynchronizationInterceptor | | your lock-policy should be MethodOnlyEJBLock. | | Look at jbosstest/src/resources/lock/META-INF/jboss.xml for |configuration | examples. EntityBean_B_Multi | | | Regards, | | Bill | | | | | | |Profiler output and hot spots for thread RMI TCP |Connection(271)-192.168.0.152 . application org.jboss.Main (CPU |profiler output - Sampler / Methods) | | | Backtrace | | caller.gif Description of CPU usage for thread RMI TCP | Connection(271)-192.168.0.152 | caller.gif 100.0% - 5862 ms - java.lang.Thread.run() | caller.gif 100.0% - 5862 ms - | sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run() | caller.gif 100.0% - 5862 ms - | sun.rmi.transport.tcp.TCPTransport.handleMessages() | caller.gif 64.48% - 3780 ms - | sun.rmi.transport.Transport.serviceCall() | caller.gif 64.48% - 3780 ms - | java.security.AccessController.doPrivileged() | caller.gif 64.48% - 3780 ms - | sun.rmi.transport.Transport$1.run() | caller.gif 64.48% - 3780 ms - | sun.rmi.server.UnicastServerRef.dispatch() | caller.gif 63.59% - 3728 ms - | java.lang.reflect.Method.invoke() | time.gif 63.59% - 3728 ms - | org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke() | caller.gif 61.87% - 3627 | ms - org.jboss.ejb.EntityContainer.invoke() | caller.gif 61.87% - | 3627 ms - org.jboss.ejb.plugins.LogInterceptor.invoke() | caller.gif 61.87% | - 3627 ms - org.jboss.ejb.plugins.SecurityInterceptor.invoke() | caller.gif | 61.87% - 3627 ms - org.jboss.ejb.plugins.TxInterceptorCMT.invoke() | caller.gif | 61.87% - 3627 ms - | org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions() | | caller.gif 32.13% - 1884 ms - org.jboss.tm.TransactionImpl.commit() | | caller.gif 29.73% - 1743 ms - | org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext() | | caller.gif 29.73% - 1743 ms - |
Re: [JBoss-dev] Transition to JCA only - should I commit now?
On Sat, 11 Aug 2001, David Jencks wrote: How about: This software may be used under the terms of the X licence or the lgpl licence. All current copyright holders grant permission that future modifications may be released under either of 1. this dual license or 2. the lgpl license alone at the discretion of the copyright holder of the modifications. Look, I don't want to be a hard case here, but I don't think #2 is legal. Could I take JBoss, make a number of customizations, and then keep my changes proprietary because I decided to change the license for my modifications alone? No. That would defeat the whole point of the license, which is to keep the code open. We'd need something new to allow that, and I don't have the training to try to craft a new self-mutating license. So I will be happy to support 1 (this code can be licensed either under the terms of the X license or under the terms of the LGPL license, at the discretion of the licensee). That would allow you to state that all of JBoss is licensed under the LGPL. Would everyone be happier with that? Aaron ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Transition to JCA only - should I commit now?
On 2001.08.13 09:33:22 -0400 Aaron Mulder wrote: On Sat, 11 Aug 2001, David Jencks wrote: How about: This software may be used under the terms of the X licence or the lgpl licence. All current copyright holders grant permission that future modifications may be released under either of 1. this dual license or 2. the lgpl license alone at the discretion of the copyright holder of the modifications. Look, I don't want to be a hard case here, but I don't think #2 is legal. Could I take JBoss, make a number of customizations, and then keep my changes proprietary My understanding of the x license is that exactly this is allowed, which is why I am wondering how appropriate it is. because I decided to change the license for my modifications alone? lgpl prohibits this, so this cannot be done except by the copyright holder for the majority of jboss. No. That would defeat the whole point of the license, which is to keep the code open. We'd need something new to allow that, and I don't have the training to try to craft a new self-mutating license. I don't either. I'm sure a lawyer could drive a large truck through my suggestion. So I will be happy to support 1 (this code can be licensed either under the terms of the X license or under the terms of the LGPL license, at the discretion of the licensee). That would allow you to state that all of JBoss is licensed under the LGPL. Would everyone be happier with that? Aaron As far as I know, only the copyright holder can change the license terms, so for instance I can't go and change X license to lgpl on jbosspool code. As far as I am concerned, you (Aaron) will have to make any license change you agree to. Here are 2 more ideas: 1. (maybe I suggested this already, this is getting t long). We tag the current version with a cvs tag saying x license, and change the license on the next version to lgpl, and include a comment that previous versions of this code may be used under the x license - look for the cvs tag 2. We change the license to lgpl, and each author states either: @author.. The code copyright by author zzz may be alternatively used under the x license @author The code copyright by author yyy may be used only under the lgpl Anyway, as far as I am concerned, you (Aaron) will have to change the license, and if you don't change to (current tagged x-license) and lgpl alone, I will check in my modifications with a note allowing future release under lgpl only. I think (current tagged x-license) and lgpl alone is the simplest for the future but am reasonably happy with any of these possibilities. david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] what is webOS?
hey, : The overhead of XML is still too great to handle seismic surveys. It's not : uncommon for seismic surveys to be 100+GB. I've even seen one survey that : was almost 1 TB big! Yes, it was loaded all on the same machine at one : time. Typical workstations (not servers--desktop workstations) will have : 200+GB of disk space, with some special-purpose workstations having far more : than that. I'm not sure it really will ever be feasible to store seismic : data in XML. as xml compresses extremely well, having it put to a zip file would help a lot IMHO, and then use zip input streams for parsing when needed. on the other hand, there are ways to use things like windows disk compression for handling such completely transparently, though I'm not familiar with the implementation of such mechanisms. the drawback is that you loose some cpu power. just my 2ct. best regards, --andrius ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: [Jobs-dev] what is webOS?
Sorry. Zipped files were still excessively large. You don't want to take a 600GB survey and turn it into a 2 TB data set. That wouldn't fit on available disk space. And data access, consisting of uncompressing XML, then parsing it, would be unacceptable for data volumes this big. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andrius Juozapaitis Sent: Monday, August 13, 2001 5:22 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] what is webOS? hey, : The overhead of XML is still too great to handle seismic surveys. It's not : uncommon for seismic surveys to be 100+GB. I've even seen one survey that : was almost 1 TB big! Yes, it was loaded all on the same machine at one : time. Typical workstations (not servers--desktop workstations) will have : 200+GB of disk space, with some special-purpose workstations having far more : than that. I'm not sure it really will ever be feasible to store seismic : data in XML. as xml compresses extremely well, having it put to a zip file would help a lot IMHO, and then use zip input streams for parsing when needed. on the other hand, there are ways to use things like windows disk compression for handling such completely transparently, though I'm not familiar with the implementation of such mechanisms. the drawback is that you loose some cpu power. just my 2ct. best regards, --andrius ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] what is webOS?
IMHO, for 99.999% of uses an XML over a zipped HTTP stream will be reasonable. You may ask what is zipped HTTP. Well it is what I call (there may be a formal name) the technique where you flag the content with the Transfer-Encoding: gzip header and zip the contentent. This gives a huge boost to bandwith usage to most users except modems which use hardware compression (unless the stream is encrypted https which basically disables the hardware compression). BTW, the performance impact is minimal as the zip code in java is written in c. -dain - Original Message - From: Dan - Blue Lotus Software [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, August 13, 2001 11:43 AM Subject: [JBoss-dev] RE: [Jobs-dev] what is webOS? Sorry. Zipped files were still excessively large. You don't want to take a 600GB survey and turn it into a 2 TB data set. That wouldn't fit on available disk space. And data access, consisting of uncompressing XML, then parsing it, would be unacceptable for data volumes this big. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andrius Juozapaitis Sent: Monday, August 13, 2001 5:22 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] what is webOS? hey, : The overhead of XML is still too great to handle seismic surveys. It's not : uncommon for seismic surveys to be 100+GB. I've even seen one survey that : was almost 1 TB big! Yes, it was loaded all on the same machine at one : time. Typical workstations (not servers--desktop workstations) will have : 200+GB of disk space, with some special-purpose workstations having far more : than that. I'm not sure it really will ever be feasible to store seismic : data in XML. as xml compresses extremely well, having it put to a zip file would help a lot IMHO, and then use zip input streams for parsing when needed. on the other hand, there are ways to use things like windows disk compression for handling such completely transparently, though I'm not familiar with the implementation of such mechanisms. the drawback is that you loose some cpu power. just my 2ct. best regards, --andrius ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/client jbosssx-client.jar
User: starksm Date: 01/08/13 10:23:14 Modified:src/client Tag: Branch_2_4 jbosssx-client.jar Log: Include fix for applet dynamic class loading and security exception on access of org.jboss.security.SecurityAssociation.ThreadLocal system property Revision ChangesPath No revision No revision 1.8.2.7 +54 -46jboss/src/client/Attic/jbosssx-client.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb ContainerFactory.java
User: starksm
Date: 01/08/13 10:23:15
Modified:src/main/org/jboss/ejb Tag: Branch_2_4 ContainerFactory.java
Log:
Include fix for applet dynamic class loading and security exception on
access of org.jboss.security.SecurityAssociation.ThreadLocal system property
Revision ChangesPath
No revision
No revision
1.77.2.2 +5 -6 jboss/src/main/org/jboss/ejb/ContainerFactory.java
Index: ContainerFactory.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/ContainerFactory.java,v
retrieving revision 1.77.2.1
retrieving revision 1.77.2.2
diff -u -r1.77.2.1 -r1.77.2.2
--- ContainerFactory.java 2001/06/27 00:22:47 1.77.2.1
+++ ContainerFactory.java 2001/08/13 17:23:15 1.77.2.2
@@ -81,7 +81,7 @@
* @author Peter Antman ([EMAIL PROTECTED])
* @author Scott Stark([EMAIL PROTECTED])
*
-* @version $Revision: 1.77.2.1 $
+* @version $Revision: 1.77.2.2 $
*/
public class ContainerFactory
extends org.jboss.util.ServiceMBeanSupport
@@ -360,6 +360,10 @@
*/
WebClassLoader cl = new WebClassLoader( jarUrls,
Thread.currentThread().getContextClassLoader() );
app.setClassLoader( cl );
+ // Add to webserver so client can access classes through dynamic class
downloading
+ WebServiceMBean webServer = (WebServiceMBean) MBeanProxy.create(
WebServiceMBean.class, WebServiceMBean.OBJECT_NAME );
+ URL[] codebase = { webServer.addClassLoader(cl) };
+ cl.setWebURLs(codebase);
for( int i = 0; i jarUrls.length; i++ )
deploy( app, jarUrls[ i ], cl );
@@ -373,11 +377,6 @@
while( i.hasNext() ) {
handleContainerManagement( (Container) i.next(), true );
}
-
- // Add to webserver so client can access classes through dynamic class
downloading
- WebServiceMBean webServer = (WebServiceMBean) MBeanProxy.create(
WebServiceMBean.class, WebServiceMBean.OBJECT_NAME );
- URL[] codebase = { webServer.addClassLoader(cl) };
- cl.setWebURLs(codebase);
// Done
log.log( Deployed application: + app.getName() );
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/lib jboss-jaas.jar jbosssx.jar
User: starksm Date: 01/08/13 10:23:15 Modified:src/lib Tag: Branch_2_4 jboss-jaas.jar jbosssx.jar Log: Include fix for applet dynamic class loading and security exception on access of org.jboss.security.SecurityAssociation.ThreadLocal system property Revision ChangesPath No revision No revision 1.11.2.8 +113 -105 jboss/src/lib/Attic/jboss-jaas.jar Binary file 1.11.2.8 +192 -194 jboss/src/lib/Attic/jbosssx.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/jrmp/test TestDynLoading.java
User: starksm
Date: 01/08/13 11:02:40
Modified:src/main/org/jboss/test/jrmp/test TestDynLoading.java
Log:
Add validation that IString impl is not coming from the local filesystem.
Revision ChangesPath
1.4 +21 -7 jbosstest/src/main/org/jboss/test/jrmp/test/TestDynLoading.java
Index: TestDynLoading.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/jrmp/test/TestDynLoading.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- TestDynLoading.java 2001/07/10 02:34:04 1.3
+++ TestDynLoading.java 2001/08/13 18:02:40 1.4
@@ -1,7 +1,9 @@
package org.jboss.test.jrmp.test;
-import java.io.IOException;
+import java.io.File;
+import java.net.URL;
import java.rmi.RemoteException;
+import java.security.CodeSource;
import javax.ejb.CreateException;
import javax.naming.InitialContext;
import javax.naming.NamingException;
@@ -19,7 +21,7 @@
/** Test of RMI dynamic class loading.
@author [EMAIL PROTECTED]
-@version $Revision: 1.3 $
+@version $Revision: 1.4 $
*/
public class TestDynLoading
extends TestCase
@@ -30,10 +32,17 @@
System.out.println(TestDynLoading);
}
+ /** Remove any local IString implementation so that we test RMI class loading.
+*/
protected void setUp() throws Exception
{
- // System.out.println(TestDynLoading.setup(jrmp-dl.jar));
- // Deploy.deploy(jrmp-dl.jar);
+ URL istringImpl =
getClass().getResource(/org/jboss/test/jrmp/ejb/AString.class);
+ if( istringImpl != null )
+ {
+ System.out.println(Found IString impl at: +istringImpl);
+ File implFile = new File(istringImpl.getFile());
+ System.out.println(Removed: +implFile.delete());
+ }
}
public void testAccess() throws Exception
@@ -47,16 +56,21 @@
System.out.println(Created StatefulSession);
IString echo = bean.copy(jrmp-dl);
System.out.println(bean.copy(jrmp-dl) = +echo);
- System.out.println(IString.class = +echo.getClass());
+ Class clazz = echo.getClass();
+ CodeSource cs = clazz.getProtectionDomain().getCodeSource();
+ URL location = cs.getLocation();
+ System.out.println(IString.class = +clazz);
+ System.out.println(IString.class location = +location);
+ assert(CodeSource URL.protocol != file,
location.getProtocol().equals(file) == false);
bean.remove();
}
/**
* Setup the test suite.
*/
- public static Test suite() {
+ public static Test suite()
+ {
TestSuite suite = new TestSuite();
-
// add a test case to deploy our support applications
String filename = jrmp-dl.jar;
suite.addTest(new Deploy.Deployer(filename));
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/bin run.bat run.sh
User: starksm
Date: 01/08/13 11:33:00
Modified:src/bin run.bat run.sh
Log:
Remove the xml parser classpaths
Revision ChangesPath
1.23 +1 -6 jboss/src/bin/run.bat
Index: run.bat
===
RCS file: /cvsroot/jboss/jboss/src/bin/run.bat,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- run.bat 2001/07/24 10:33:09 1.22
+++ run.bat 2001/08/13 18:33:00 1.23
@@ -4,13 +4,8 @@
set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;run.jar
-REM Add all login modules for JAAS-based security
-REM and all libraries that are used by them here
-set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%
-
-REM Add the XML parser jars and set the JAXP factory names
+REM Set the JAXP factory names
REM Crimson parser JAXP setup(default)
-set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;../lib/crimson.jar
set
JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
set JAXP=%JAXP%
-Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl
1.24 +2 -5 jboss/src/bin/run.sh
Index: run.sh
===
RCS file: /cvsroot/jboss/jboss/src/bin/run.sh,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- run.sh2001/08/11 23:50:55 1.23
+++ run.sh2001/08/13 18:33:00 1.24
@@ -5,7 +5,7 @@
## ##
### == ###
-### $Id: run.sh,v 1.23 2001/08/11 23:50:55 user57 Exp $ ###
+### $Id: run.sh,v 1.24 2001/08/13 18:33:00 starksm Exp $ ###
DIRNAME=`dirname $0`
PROGNAME=`basename $0`
@@ -58,19 +58,16 @@
crimson)
JAXP_DOM_FACTORY=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl
JAXP_SAX_FACTORY=org.apache.crimson.jaxp.SAXParserFactoryImpl
- JAXP_CLASSPATH=$JBOSS_HOME/lib/crimson.jar
;;
*)
if [ x$JAXP_DOM_FACTORY = x ]
-[ x$JAXP_SAX_FACTORY = x ]
-[ x$JAXP_CLASSPATH = x ]; then
+[ x$JAXP_SAX_FACTORY = x ] then
die unsupported JAXP parser: $JAXP
fi
;;
esac
-JBOSS_CLASSPATH=${JBOSS_CLASSPATH}:$JAXP_CLASSPATH
JAVA_OPTS=$JAVA_OPTS -Djavax.xml.parsers.DocumentBuilderFactory=$JAXP_DOM_FACTORY
JAVA_OPTS=$JAVA_OPTS -Djavax.xml.parsers.SAXParserFactory=$JAXP_SAX_FACTORY
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] what is webOS?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dain Sundstrom IMHO, for 99.999% of uses an XML over a zipped HTTP stream will be reasonable. I agree. We have seen 50% improvements in speed of large result sets that is gzipped before transmission. This is accomplished by employing a servlet filter that checks the content-length (and content-type) prior to transmission. If it is over a particular length, we zip it. Browsers automatically handle the de-compression. From: Dan - Blue Lotus Software [EMAIL PROTECTED] Sorry. Zipped files were still excessively large. You don't want to take a 600GB survey and turn it into a 2 TB data set. That wouldn't fit on available disk space. And data access, consisting of uncompressing XML, then parsing it, would be unacceptable for data volumes this big. Certainly you wouldn't want to marshall such a structure under any circumstances. At least not in an interactive program. One thing that may be interesting for people involved in compression of XML. We know that LZW will recognize byte patterns and replace them with a smaller series of bits. I wonder how effective standard ZIP compression on XML files is compared with a slightly more intelligent type. A more intelligent compression would not simply scan characters sequentially looking for patterns, but rather it would parse out the tags prior to compression. These tags (arguably the most horrendous contributors to XML bloat) can be effectively compressed to nothing. In fact, all of the tags in a very large DTD can be compressed to less than one byte each. I would think that significant gains in compression could be achieved over standard ZIP compression. jim ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss build.xml
User: starksm
Date: 01/08/13 11:52:26
Modified:.build.xml
Log:
Drop the excludsions from jboss.jar due to system classpath restrictions
Revision ChangesPath
1.5 +1 -5 jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss/build.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml 2001/08/12 02:55:53 1.4
+++ build.xml 2001/08/13 18:52:25 1.5
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.4 2001/08/12 02:55:53 starksm Exp $ --
+!-- $Id: build.xml,v 1.5 2001/08/13 18:52:25 starksm Exp $ --
project default=main
@@ -320,10 +320,6 @@
!-- ??? --
exclude name=org/jboss/tm/GlobalId.class/
-!-- Exclude the security classes that must be on the classpath --
-exclude name=org/jboss/security/AnybodyPrincipal.class/
-exclude name=org/jboss/security/NobodyPrincipal.class/
-exclude name=org/jboss/security/SimplePrincipal.class/
/fileset
fileset dir=${build.resources}
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Classpath cleanup
After updating the jaas.jar and jaxp.jar so that they no longer use the system classloader, most of the jars that had to be in the dist/lib directory and included on the system classpath can now be in dist/lib/ext. The following changes have been made in main: lib/crimson.jar - lib/ext/crimson.jar lib/jaxp.jar - lib/ext/jaxp.jar lib/jaas.jar - lib/ext/jaas.jar jboss-jaas.jar is no longer used jboss-jdbc_ext.jar is no longer used ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Classpath cleanup
eeexcellent... marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott |M Stark |Sent: Monday, August 13, 2001 2:59 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Classpath cleanup | | |After updating the jaas.jar and jaxp.jar so that they no longer use the |system classloader, |most of the jars that had to be in the dist/lib directory and included on |the system |classpath can now be in dist/lib/ext. The following changes have been made |in main: | |lib/crimson.jar - lib/ext/crimson.jar |lib/jaxp.jar - lib/ext/jaxp.jar |lib/jaas.jar - lib/ext/jaas.jar |jboss-jaas.jar is no longer used |jboss-jdbc_ext.jar is no longer used | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] problems with latest jboss-jetty?
I am working on the latest jboss2.4-jetty stuff to update the website. Now I know I am not supposed to post user questions on jboss-deb but please bear with me before you flame me. I have 2 problem: 1- double deployment: when I rebuild the website, the autodeployer deploys twice. Tears down and deploys and again. strange... is this an autodeployer bug? 2- / trouble: if I request the page during redeployment of the / context it seems to fail with a not found error that prevents future deployments. If this is just me and I should really be trolling the forums feel free to let me know :) marcf _ Marc Fleury, Ph.D [EMAIL PROTECTED] _ ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] what is webOS?
My only point was to point out that there are areas where XML transmission of data is not appropriate. The concept of a web OS, put forth by Marc as the initial reply to this thread, seemed to imply that memory would be moved around from JVM to JVM, across the Web OS, seamlessly and without knowledge or care by the application programmers. I only intended to point out that this is only appropriate for certain types of messages. Namely, if messages are sufficiently large, as with seismic data in my case, or if the bottleneck lies with network latency, this concept of the Web OS is not appropriate. Of course, JBoss' pervasive use of proxies allow us to omit the overhead of the network if both sides of the app are running within the same VM. This is nice. Please don't think of XML-based messaging as the silver bullet for a network OS. If this is the case, I'll have to look elsewhere for solutions. That said, XML-based messaging is sufficient for most cases, although I would strongly disagree with your 99.999% figure. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of James Cook Sent: Monday, August 13, 2001 7:41 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] what is webOS? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dain Sundstrom IMHO, for 99.999% of uses an XML over a zipped HTTP stream will be reasonable. I agree. We have seen 50% improvements in speed of large result sets that is gzipped before transmission. This is accomplished by employing a servlet filter that checks the content-length (and content-type) prior to transmission. If it is over a particular length, we zip it. Browsers automatically handle the de-compression. From: Dan - Blue Lotus Software [EMAIL PROTECTED] Sorry. Zipped files were still excessively large. You don't want to take a 600GB survey and turn it into a 2 TB data set. That wouldn't fit on available disk space. And data access, consisting of uncompressing XML, then parsing it, would be unacceptable for data volumes this big. Certainly you wouldn't want to marshall such a structure under any circumstances. At least not in an interactive program. One thing that may be interesting for people involved in compression of XML. We know that LZW will recognize byte patterns and replace them with a smaller series of bits. I wonder how effective standard ZIP compression on XML files is compared with a slightly more intelligent type. A more intelligent compression would not simply scan characters sequentially looking for patterns, but rather it would parse out the tags prior to compression. These tags (arguably the most horrendous contributors to XML bloat) can be effectively compressed to nothing. In fact, all of the tags in a very large DTD can be compressed to less than one byte each. I would think that significant gains in compression could be achieved over standard ZIP compression. jim ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-450615 ] Build instructions????
Bugs item #450615, was opened at 2001-08-13 14:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=450615group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Build instructions Initial Comment: There are no build instructions anywhere. Simply downloading the cvs projects listed, and running a build.sh doesn't do the trick. Also, not all the projects are listed. Looking in the developer archive suggested a project called jboss-all, which did put some more stuff on disk, but nothing that made the build run. Firing off ant on some build.xml files also doesn't go very far. So, what are the secret steps to build jboss from source? Thanks! -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=450615group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] what is webOS?
I am kinda saddened that the discussion as turned to a minor point, that of the factor at which the current technology will catch up to make distribution of data a viable solution. I repeat that to me the solution lays not with the XML/zip solutions as much as it lays on the power of the bare metal under it. It is not a bandwith issue it is a simple MIPS issue. Let just go back to the mine, the vision dope is heady but not very productive, specifically not when factions fight over sub-nodes of it where probabilities become fuzzy. No religion, only intra-venous technology, if possible in its purest form please, we can handle it... yeah right! just don't overdose kids! Go work now, make it real, ;-) Love, marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Dan - |Blue Lotus Software |Sent: Monday, August 13, 2001 5:04 PM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] what is webOS? | | |My only point was to point out that there are areas where XML transmission |of data is not appropriate. The concept of a web OS, put forth by Marc as |the initial reply to this thread, seemed to imply that memory |would be moved |around from JVM to JVM, across the Web OS, seamlessly and without |knowledge or care by the application programmers. I only intended to point |out that this is only appropriate for certain types of messages. |Namely, if |messages are sufficiently large, as with seismic data in my case, or if the |bottleneck lies with network latency, this concept of the Web OS is not |appropriate. Of course, JBoss' pervasive use of proxies allow us to omit |the overhead of the network if both sides of the app are running within the |same VM. This is nice. | |Please don't think of XML-based messaging as the silver bullet for |a network |OS. If this is the case, I'll have to look elsewhere for solutions. That |said, XML-based messaging is sufficient for most cases, although I would |strongly disagree with your 99.999% figure. | |-dan | |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of James |Cook |Sent: Monday, August 13, 2001 7:41 PM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] what is webOS? | | | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Dain | Sundstrom | | IMHO, for 99.999% of uses an XML over a zipped HTTP stream will be | reasonable. | |I agree. We have seen 50% improvements in speed of large result |sets that is |gzipped before transmission. This is accomplished by employing a servlet |filter that checks the content-length (and content-type) prior to |transmission. If it is over a particular length, we zip it. Browsers |automatically handle the de-compression. | | | From: Dan - Blue Lotus Software [EMAIL PROTECTED] | Sorry. Zipped files were still excessively large. You don't | want to take | a | 600GB survey and turn it into a 2 TB data set. That wouldn't fit on | available disk space. And data access, consisting of |uncompressing XML, | then parsing it, would be unacceptable for data volumes this big. | |Certainly you wouldn't want to marshall such a structure under any |circumstances. At least not in an interactive program. | |One thing that may be interesting for people involved in |compression of XML. |We know that LZW will recognize byte patterns and replace them with a |smaller series of bits. I wonder how effective standard ZIP compression on |XML files is compared with a slightly more intelligent type. | |A more intelligent compression would not simply scan characters |sequentially |looking for patterns, but rather it would parse out the tags prior to |compression. These tags (arguably the most horrendous contributors to XML |bloat) can be effectively compressed to nothing. In fact, all of |the tags in |a very large DTD can be compressed to less than one byte each. | |I would think that significant gains in compression could be achieved over |standard ZIP compression. | |jim | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Minerva sources
Hi, sorry, if the question is stupid, but where the heck are the current Minerva sources? Thanks, Jochen ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-450615 ] Build instructions????
Who submitted this? Can you explain to the list the problems that you are seeing? I should get the instructions on the web site today, which means they will probably show up tomorrow. In the meantime if anyone has troubles, please let me know. Bug reports are nice, but they make it hard to startup a dialog. --jason On Mon, 13 Aug 2001 [EMAIL PROTECTED] wrote: Bugs item #450615, was opened at 2001-08-13 14:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=450615group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Build instructions Initial Comment: There are no build instructions anywhere. Simply downloading the cvs projects listed, and running a build.sh doesn't do the trick. Also, not all the projects are listed. Looking in the developer archive suggested a project called jboss-all, which did put some more stuff on disk, but nothing that made the build run. Firing off ant on some build.xml files also doesn't go very far. So, what are the secret steps to build jboss from source? Thanks! -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=450615group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite jboss-castor.jsp
User: olegnitz Date: 01/08/13 14:54:27 Modified:.jboss-castor.jsp Log: Updated link to rooms2.zip Revision ChangesPath 1.6 +1 -1 newsite/jboss-castor.jsp Index: jboss-castor.jsp === RCS file: /cvsroot/jboss/newsite/jboss-castor.jsp,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- jboss-castor.jsp 2001/08/03 21:24:46 1.5 +++ jboss-castor.jsp 2001/08/13 21:54:27 1.6 @@ -24,7 +24,7 @@ All necessary binary files are included in the JBoss distribution since JBoss 2.5.br If you use older version, download a href=http://ftp.exolab.org/ftp/jars/castor-0.9.3.zip;castor-0.9.3.zip/a, extract castor-0.9.3.jar and xerces.jar and take the CastorJDO integration module here: a href=castorjdo/jboss-castorjdo.jarjboss-castorjdo.jar/a. -p class=textA complete example of use of CastorJDO in SessionBean is a href=castorjdo/rooms.ziphere/a (contributed by Terry Child). +p class=textA complete example of use of CastorJDO in SessionBean is a href=castorjdo/rooms2.ziphere/a (contributed by Terry Child). p class=textThe opensource project a href=http://jmoz.sourceforge.net;jmoz/a uses JBoss+CastorJDO for BMP EntityBeans (the jmoz project is lead by Kevin O'Neill). ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq SpyConnectionConsumer.java
User: pkendall
Date: 01/08/13 15:34:45
Modified:src/main/org/jboss/mq SpyConnectionConsumer.java
Log:
Hopefully fix MDB message delivery bug.
Revision ChangesPath
1.2 +3 -3 jbossmq/src/main/org/jboss/mq/SpyConnectionConsumer.java
Index: SpyConnectionConsumer.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/SpyConnectionConsumer.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SpyConnectionConsumer.java2001/08/11 20:59:11 1.1
+++ SpyConnectionConsumer.java2001/08/13 22:34:45 1.2
@@ -19,7 +19,7 @@
*
* @author Hiram Chirino ([EMAIL PROTECTED])
*
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public class SpyConnectionConsumer implements javax.jms.ConnectionConsumer,
SpyConsumer, Runnable {
@@ -68,7 +68,6 @@
if (closed)
return;
- connection.removeConsumer(this);
closed = true;
queue.notifyAll();
}
@@ -80,6 +79,7 @@
SpyMessage message = (SpyMessage) queue.removeFirst();
connection.send(message.getAcknowledgementRequest(false));
}
+ connection.removeConsumer(this);
}
}
@@ -109,7 +109,7 @@
if(mes == null){
synchronized(queue){
waitingForMessage = true;
- while(waitingForMessage !closed){
+ while(queue.isEmpty() !closed){
try{ queue.wait(); }catch(InterruptedException e){}
}
if(closed){
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] MDB has stopped working
I have had a look at the MDB problem this morning and found a simple bug in my original code for SpyConnectionConsumer that would certainly have been causing problems. As the CVS update says the fix should hopefully fix the problem people were having with MDB but as we are not using MDB ourselves and are currently having a bit of trouble with the new build system I can't test the fix. So please feel free to test the new fix and let us know if it still ain't working. Cheers, david PS: As I am new to the list I should probably introduce myself. My name is David Maplesden and I work at Orion Systems in NZ with Paul Kendall. I am responsible for the majority of the recent major changes to jboss mq submitted by Paul. They were submitted by him cause I am (to date) too lazy to set up a CVS account and stuff. Anyone with any problems with the new code or questions etc feel free to send me an e-mail, if I'm not too busy at work I'll get back to you ASAP. -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED]] Sent: Monday, August 13, 2001 9:10 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] MDB has stopped working This is exactly what I say on friday, when the PooledExecutor was removed from JBossMQ. I have not had time to look into why it does not work as of yet. I do know that the previous jars work, and probably better than any other version that I had seen, at least with respect to the application I am building (which is highly JMS driven). --jason On Mon, 13 Aug 2001, Peter Antman wrote: Hi, It seems as if MDB has stopped working with the latest jbossmq. I build with a clean checkout of jboss-all today and have run both the mdbtest and tested jms-hello-topic and jms-hello-queue from the new JMS chapter examples: MDB:s deployes OK, it is OK to send to MDB, but the MDB will not receive any thing send to it after is has been deployed. It will however raise an exception when undeploying because there seemd to be stuff waiting Here is some outpout: Manually deploy HelloQueueMDB.jar (from example) [ContainerFactory] Deployed application: file:/home/pra/src/rw/jboss-all/build/output/jboss-2.5alpha-DE V/tmp/deploy/Default/HelloQueueMDB.jar [J2eeDeployer#Default] J2EE application: file:/home/pra/src/rw/jboss-all/build/output/jboss-2.5alpha-DE V/deploy/HelloQueueMDB.jar is deployed. Send some messages ant jms-hello-sender25 (from example) Nothing happens!! Undeploy the bean: [AutoDeployer] Auto undeploy of file:/home/pra/src/rw/jboss-all/build/output/jbo ss-2.5alpha-DEV/deploy/HelloQueueMDB.jar [J2eeDeployer#Default] Stopping module HelloQueueMDB.jar [ContainerFactory] Undeploying:file:/home/pra/src/rw/jboss-all/build/output/jbos s-2.5alpha-DEV/tmp/deploy/Default/HelloQueueMDB.jar [ContainerManagement] Stopping [ContainerManagement] Stopped [ContainerManagement] Destroying [ContainerManagement] Destroyed [ContainerManagement] Destroying [ContainerManagement] Destroyed [JMSContainerInvoker] Could not close consumer org.jboss.mq.SpyJMSException: Cannot acknowlege a message at org.jboss.mq.Connection.send(Connection.java:435) at org.jboss.mq.SpyConnectionConsumer.close(SpyConnectionConsumer.java:8 1) at org.jboss.ejb.plugins.jms.JMSContainerInvoker.destroy(JMSContainerInv oker.java:542) at org.jboss.ejb.MessageDrivenContainer.destroy(MessageDrivenContainer.j ava:251) at org.jboss.ejb.Application.destroy(Application.java:239) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:531) at org.jboss.ejb.ContainerFactory.undeploy(ContainerFactory.java:325) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.deployment.J2eeDeployer.stopModule(J2eeDeployer.java:586) at org.jboss.deployment.J2eeDeployer.stopApplication(J2eeDeployer.java:5 67) at org.jboss.deployment.J2eeDeployer.undeploy(J2eeDeployer.java:294) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15 23) at org.jboss.ejb.AutoDeployer.undeploy(AutoDeployer.java:403) at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:184) at java.lang.Thread.run(Thread.java:484) linked exception is: javax.jms.JMSException: The provided subscription does not exist at org.jboss.mq.server.ClientConsumer.acknowledge(ClientConsumer.java:22 2) at org.jboss.mq.server.JMSServer.acknowledge(JMSServer.java:299) at
RE: [JBoss-dev] Minerva sources
jbosspool marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Wiedmann, Jochen |Sent: Monday, August 13, 2001 5:45 PM |To: '[EMAIL PROTECTED]' |Subject: [JBoss-dev] Minerva sources | | | | |Hi, | |sorry, if the question is stupid, but where the heck |are the current Minerva sources? | | |Thanks, | |Jochen | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] problems with latest jboss-jetty?
marc fleury wrote: I am working on the latest jboss2.4-jetty stuff to update the website. Now I know I am not supposed to post user questions on jboss-deb but please bear with me before you flame me. I have 2 problem: 1- double deployment: when I rebuild the website, the autodeployer deploys twice. Tears down and deploys and again. strange... is this an autodeployer bug? The double deployment stuff - h - I'll leave that to someone else 2- / trouble: if I request the page during redeployment of the / context it seems to fail with a not found error that prevents future deployments. Greg has already explained this to Marc, but just for the benefit of the list : - J2EEDeployer tells Jetty to undeploy the EAR - Jetty stops and destroys the associated context object - before the next instruction from the J2EEDeployer to deploy the same EAR again a user gets in with a request. - finding no context object mapped to '/' Jetty thoughfully dynamically builds one that returns a NotFoundError - when the ear is finally redeployed this other context shadows the ear's A simple solution is (hopefully) to go in via the JMX interface or the Admin servlet (localhost:8080/Admin) locate the '/' context that contains the NotFoundHandler and destroy it. Then the ear's '/' handler should receive all the requests meant for '/' and life should proceed as intended. Greg has checked a fix into CVS, I shall be talking to him about the problem. Jules If this is just me and I should really be trolling the forums feel free to let me know :) marcf _ Marc Fleury, Ph.D [EMAIL PROTECTED] _ ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] problems with latest jboss-jetty?
marc fleury wrote: I am working on the latest jboss2.4-jetty stuff to update the website. Now I know I am not supposed to post user questions on jboss-deb but please bear with me before you flame me. I have 2 problem: 1- double deployment: when I rebuild the website, the autodeployer deploys twice. Tears down and deploys and again. strange... is this an autodeployer bug? Marc, I'd be interested to know if the same version of JBoss with TomCat exhibits this double deployment problem - otherwise it is something that I should be looking at. Jules 2- / trouble: if I request the page during redeployment of the / context it seems to fail with a not found error that prevents future deployments. If this is just me and I should really be trolling the forums feel free to let me know :) marcf _ Marc Fleury, Ph.D [EMAIL PROTECTED] _ ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] A downside to the new build scheme
You can specify which modules to include, in most cases you will just want to server module: cd build ./build.sh -Dmodules=server This will only build the server module. Be sure to set in local.properties: javadoc-generated-already=true This will disable the generation of javadocs (which should speed things up alot). This is covered in the HOWTO section of the new BM users guide, which I will have added to the newsite module today (a little later). Perhaps there should be a helper target which will just recurse to the server, though I would suggest using the -Dmodules and -Dgroups as you need. --jason On Mon, 13 Aug 2001, Scott M Stark wrote: Changing one server file and rebuilding to test is taking on the order of 2 minutes where this takes 5 seconds previously. There should be an intermediate build target that builds the server without all of the doc steps being run as currently is the case. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] A downside to the new build scheme
Just to clarify, it is slow because of the full execution of the docs target right? --jason On Mon, 13 Aug 2001, Scott M Stark wrote: Changing one server file and rebuilding to test is taking on the order of 2 minutes where this takes 5 seconds previously. There should be an intermediate build target that builds the server without all of the doc steps being run as currently is the case. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq config.xml
User: user57
Date: 01/08/13 19:13:14
Modified:.config.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
1.3 +1 -2 jbossmq/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/jbossmq/config.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- config.xml2001/08/11 05:20:14 1.2
+++ config.xml2001/08/14 02:13:13 1.3
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.2 2001/08/11 05:20:14 user57 Exp $ --
+!-- $Id: config.xml,v 1.3 2001/08/14 02:13:13 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -130,7 +130,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Naming --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia config.xml
User: user57
Date: 01/08/13 19:13:14
Modified:variaconfig.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
1.4 +1 -2 contrib/varia/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/contrib/varia/config.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- config.xml2001/08/11 08:04:54 1.3
+++ config.xml2001/08/14 02:13:14 1.4
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.3 2001/08/11 08:04:54 user57 Exp $ --
+!-- $Id: config.xml,v 1.4 2001/08/14 02:13:14 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -170,7 +170,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Naming --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss config.xml
User: user57
Date: 01/08/13 19:13:14
Modified:.config.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
1.3 +1 -2 jboss/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/jboss/config.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- config.xml2001/08/11 05:20:20 1.2
+++ config.xml2001/08/14 02:13:14 1.3
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.2 2001/08/11 05:20:20 user57 Exp $ --
+!-- $Id: config.xml,v 1.3 2001/08/14 02:13:14 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -164,7 +164,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Naming --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosssx config.xml
User: user57
Date: 01/08/13 19:13:14
Modified:.config.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
1.5 +1 -2 jbosssx/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/jbosssx/config.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- config.xml2001/08/11 23:13:35 1.4
+++ config.xml2001/08/14 02:13:14 1.5
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.4 2001/08/11 23:13:35 user57 Exp $ --
+!-- $Id: config.xml,v 1.5 2001/08/14 02:13:14 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -134,7 +134,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Naming --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest config.xml
User: user57
Date: 01/08/13 19:13:14
Modified:.Tag: jboss_buildmagic config.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
No revision
No revision
1.1.2.14 +1 -2 jbosstest/Attic/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/jbosstest/Attic/config.xml,v
retrieving revision 1.1.2.13
retrieving revision 1.1.2.14
diff -u -r1.1.2.13 -r1.1.2.14
--- config.xml2001/08/03 00:06:41 1.1.2.13
+++ config.xml2001/08/14 02:13:14 1.1.2.14
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.1.2.13 2001/08/03 00:06:41 user57 Exp $ --
+!-- $Id: config.xml,v 1.1.2.14 2001/08/14 02:13:14 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -154,7 +154,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Naming --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosscx config.xml
User: user57
Date: 01/08/13 19:13:13
Modified:.config.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
1.3 +1 -2 jbosscx/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/jbosscx/config.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- config.xml2001/08/11 05:20:11 1.2
+++ config.xml2001/08/14 02:13:13 1.3
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.2 2001/08/11 05:20:11 user57 Exp $ --
+!-- $Id: config.xml,v 1.3 2001/08/14 02:13:13 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -106,7 +106,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Server --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosspool config.xml
User: user57
Date: 01/08/13 19:13:14
Modified:.config.xml
Log:
o removed jboss-jdbc_ext.jar from the jboss.j2ee.classpath, since it no
longer exists.
Revision ChangesPath
1.3 +1 -2 jbosspool/config.xml
Index: config.xml
===
RCS file: /cvsroot/jboss/jbosspool/config.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- config.xml2001/08/11 05:20:17 1.2
+++ config.xml2001/08/14 02:13:14 1.3
@@ -7,7 +7,7 @@
!----
!-- == --
-!-- $Id: config.xml,v 1.2 2001/08/11 05:20:17 user57 Exp $ --
+!-- $Id: config.xml,v 1.3 2001/08/14 02:13:14 user57 Exp $ --
!-- == --
!-- Module Setup --
@@ -106,7 +106,6 @@
property name=jboss.j2ee.lib value=${jboss.j2ee.root}/lib/
path id=jboss.j2ee.classpath
pathelement path=${jboss.j2ee.lib}/jboss-j2ee.jar/
-pathelement path=${jboss.j2ee.lib}/jboss-jdbc_ext.jar/
/path
!-- Server --
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] A downside to the new build scheme
Yes, with -Dmodules=server and the javadoc-generated-already=true it is taking 17 seconds when everything is up to date. - Original Message - From: Jason Dillon To: [EMAIL PROTECTED] Sent: Monday, August 13, 2001 6:44 PM Subject: Re: [JBoss-dev] A downside to the new build scheme Just to clarify, it is slow because of the full execution of the docs target right? --jason On Mon, 13 Aug 2001, Scott M Stark wrote: Changing one server file and rebuilding to test is taking on the order of 2 minutes where this takes 5 seconds previously. There should be an intermediate build target that builds the server without all of the doc steps being run as currently is the case. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/bin run.sh
User: user57 Date: 01/08/13 19:29:24 Modified:src/bin run.sh Log: o fixed run.sh's default JAXP case (was missing a ;) Revision ChangesPath 1.25 +4 -4 jboss/src/bin/run.sh Index: run.sh === RCS file: /cvsroot/jboss/jboss/src/bin/run.sh,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- run.sh2001/08/13 18:33:00 1.24 +++ run.sh2001/08/14 02:29:24 1.25 @@ -5,7 +5,7 @@ ## ## ### == ### -### $Id: run.sh,v 1.24 2001/08/13 18:33:00 starksm Exp $ ### +### $Id: run.sh,v 1.25 2001/08/14 02:29:24 user57 Exp $ ### DIRNAME=`dirname $0` PROGNAME=`basename $0` @@ -61,9 +61,9 @@ ;; *) - if [ x$JAXP_DOM_FACTORY = x ] -[ x$JAXP_SAX_FACTORY = x ] then - die unsupported JAXP parser: $JAXP + if [ x$JAXP_DOM_FACTORY = x ] +[ x$JAXP_SAX_FACTORY = x ]; then + die Unsupported JAXP parser: $JAXP fi ;; esac ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] VerifyError: (class: org/jboss/web/WebServer
Does anyone know why this error might be showing up when using the Jikes compiler: java.lang.VerifyError: (class: org/jboss/web/WebServer, method: run signature: ()V) Register 4 contains wrong type at org.jboss.web.WebService.init(WebService.java:44) at java.lang.reflect.Constructor.newInstance(Native Method) at com.sun.management.jmx.MBeanServerImpl.internal_instantiate(MBeanServerImpl.java:2210) at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:761) at org.jboss.configuration.ConfigurationService.create(ConfigurationService.java:652) at org.jboss.configuration.ConfigurationService.loadConfiguration(ConfigurationService.java:437) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.Main.init(Main.java:201) at org.jboss.Main$2.run(Main.java:115) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Main.java:111) If I change to javac I never see this. Any ideas? --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] VerifyError: (class: org/jboss/web/WebServer
Its a bug in the jikes compiler. - Original Message - From: Jason Dillon To: [EMAIL PROTECTED] Sent: Monday, August 13, 2001 7:36 PM Subject: [JBoss-dev] VerifyError: (class: org/jboss/web/WebServer Does anyone know why this error might be showing up when using the Jikes compiler: java.lang.VerifyError: (class: org/jboss/web/WebServer, method: run signature: ()V) Register 4 contains wrong type at org.jboss.web.WebService.init(WebService.java:44) at java.lang.reflect.Constructor.newInstance(Native Method) at com.sun.management.jmx.MBeanServerImpl.internal_instantiate(MBeanServerImpl. java:2210) at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:761) at org.jboss.configuration.ConfigurationService.create(ConfigurationService.jav a:652) at org.jboss.configuration.ConfigurationService.loadConfiguration(Configuration Service.java:437) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.Main.init(Main.java:201) at org.jboss.Main$2.run(Main.java:115) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Main.java:111) If I change to javac I never see this. Any ideas? --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss build.xml
User: starksm
Date: 01/08/13 20:12:57
Modified:.build.xml
Log:
Remove the GlobalId exclusion from jboss.jar since jboss-client.jar is
no longer used by the server
Revision ChangesPath
1.6 +1 -5 jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 2001/08/13 18:52:25 1.5
+++ build.xml 2001/08/14 03:12:57 1.6
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.5 2001/08/13 18:52:25 starksm Exp $ --
+!-- $Id: build.xml,v 1.6 2001/08/14 03:12:57 starksm Exp $ --
project default=main
@@ -316,10 +316,6 @@
!-- Exclude Main, it will go into run.jar --
exclude name=org/jboss/Main*/
-
-!-- ??? --
-exclude name=org/jboss/tm/GlobalId.class/
-
/fileset
fileset dir=${build.resources}
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb ContainerRelection.java ContainerRelectionMBean.java ContainerFactory.java Container.java
User: starksm
Date: 01/08/13 20:31:34
Modified:src/main/org/jboss/ejb ContainerFactory.java Container.java
Added: src/main/org/jboss/ejb ContainerRelection.java
ContainerRelectionMBean.java
Log:
Add a prototype DynamicMBean interface implementation to Container to
expose the EJB interface classes and invocation entry points.
Revision ChangesPath
1.90 +16 -9 jboss/src/main/org/jboss/ejb/ContainerFactory.java
Index: ContainerFactory.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/ContainerFactory.java,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- ContainerFactory.java 2001/08/10 16:51:19 1.89
+++ ContainerFactory.java 2001/08/14 03:31:34 1.90
@@ -68,7 +68,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a.
* @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a
* @author a href=mailto:[EMAIL PROTECTED];Sacha Labourey/a
-* @version $Revision: 1.89 $
+* @version $Revision: 1.90 $
*/
public class ContainerFactory
extends ServiceMBeanSupport
@@ -579,26 +579,29 @@
ClassLoader localCl )
throws Exception
{
+ Container container = null;
// Added message driven deployment
if( bean.isMessageDriven() )
{
- return createMessageDrivenContainer( bean, cl, localCl );
+ container = createMessageDrivenContainer( bean, cl, localCl );
}
else if( bean.isSession() ) // Is session?
{
if( ( (SessionMetaData) bean ).isStateless() ) // Is stateless?
{
-return createStatelessSessionContainer( bean, cl, localCl );
+container = createStatelessSessionContainer( bean, cl, localCl );
}
else // Stateful
{
-return createStatefulSessionContainer( bean, cl, localCl );
+container = createStatefulSessionContainer( bean, cl, localCl );
}
}
else // Entity
{
- return createEntityContainer( bean, cl, localCl );
+ container = createEntityContainer( bean, cl, localCl );
}
+ container.setMBeanServer(this.getServer());
+ return container;
}
private MessageDrivenContainer createMessageDrivenContainer( BeanMetaData bean,
@@ -713,11 +716,14 @@
* Either creates the Management MBean wrapper for a container and start
* it or it destroy it.
**/
- private void handleContainerManagement( Container container, boolean doStart ) {
- try {
+ private void handleContainerManagement( Container container, boolean doStart )
+ {
+ try
+ {
// Create and register the ContainerMBean
ObjectName name = new ObjectName( Management, jndiName,
container.getBeanMetaData().getJndiName() );
- if( doStart ) {
+ if( doStart )
+ {
getServer().createMBean(
org.jboss.management.ContainerManagement,
name,
@@ -727,7 +733,8 @@
getServer().invoke( name, init, new Object[] {}, new String[] {} );
getServer().invoke( name, start, new Object[] {}, new String[] {} );
}
- else {
+ else
+ {
// If not startup then assume that the MBean is there
getServer().invoke( name, stop, new Object[] {}, new String[] {} );
getServer().invoke( name, destroy, new Object[] {}, new String[] {} );
1.54 +182 -9jboss/src/main/org/jboss/ejb/Container.java
Index: Container.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/Container.java,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- Container.java2001/08/03 17:15:43 1.53
+++ Container.java2001/08/14 03:31:34 1.54
@@ -14,6 +14,20 @@
import java.util.HashMap;
import java.util.Set;
+import javax.management.Attribute;
+import javax.management.AttributeList;
+import javax.management.AttributeNotFoundException;
+import javax.management.DynamicMBean;
+import javax.management.InvalidAttributeValueException;
+import javax.management.MBeanConstructorInfo;
+import javax.management.MBeanException;
+import javax.management.MBeanInfo;
+import javax.management.MBeanNotificationInfo;
+import javax.management.MBeanOperationInfo;
+import javax.management.MBeanParameterInfo;
+import javax.management.MBeanServer;
+import javax.management.ObjectName;
+import javax.management.ReflectionException;
import javax.naming.Context;
import javax.naming.Name;
import
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/08/13 20:55:41 Modified:.modules Log: o removed some extraneous plugin modules. o tidied up some indentation. o added an alias website - newsite, since the website module has not been touched in months. Revision ChangesPath 1.46 +30 -25CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- modules 2001/08/12 03:23:21 1.45 +++ modules 2001/08/14 03:55:41 1.46 @@ -55,9 +55,7 @@ ## Plugins ## -_plugins_zoap-d zoap zoap _plugins_varia -d variacontrib/varia -_plugins_tomcat -d tomcat contrib/tomcat _plugins_jetty -d jettycontrib/jetty ## @@ -88,7 +86,7 @@ build/_emptydir \ _plugins_varia -# Need more help before they can be integrated +# Needs more help before they can be integrated #_plugins_jetty @@ -149,13 +147,14 @@ ## ## The jbossmq standalone server ## -jbossmq -d jbossmq \ + +jbossmq -d jbossmq \ build/jbossmq/etc/root \ _jbossmq_tools \ _jbossmq_thirdparty \ jbossmq-modules -_jbossmq_tools -a \ +_jbossmq_tools -a \ tools/apache \ tools/planet57 \ tools/sun @@ -169,16 +168,17 @@ thirdparty/oswego \ thirdparty/sun -jbossmq-modules-a \ -_jbossmq_build \ +jbossmq-modules -a \ + _jbossmq_build \ _jboss_j2ee \ _jboss_naming \ _jboss_server \ _jboss_messaging \ - _jboss_security \ + _jboss_security -_jbossmq_build -d build build/jbossmq +_jbossmq_build -d build build/jbossmq + # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # ## @@ -196,27 +196,32 @@ ## Legacy modules, should use a jboss-* module instead. ## -jboss jboss -jnp jnp -#jbossmq jbossmq -jbosscx jbosscx -manual manual -admin admin -jboss-j2ee jboss-j2ee -jbossmx jbossmx -jbosspool jbosspool +jbossjboss +jnp jnp +jbosscx jbosscx +manual manual +adminadmin +jboss-j2ee jboss-j2ee +jbossmx jbossmx +jbosspooljbosspool -# this will soon be integrated -jbosstest jbosstest +# This will soon be integrated +jbosstestjbosstest ## ## Everything else ## + +contrib contrib +zoap zoap +ejx ejx +zola zola +newsite newsite -contrib contrib -zoap zoap -ejx ejx -zola zola -newsite newsite +## +## Name-space migration aliases. +## + +website -d website newsite \ No newline at end of file ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite bm-usersguide.pdf cvs.jsp
User: user57
Date: 01/08/13 21:07:51
Modified:.cvs.jsp
Added: .bm-usersguide.pdf
Log:
o added a blurb about Buildmagic under More information on Build and Source.
o added the pdf users guide.
Revision ChangesPath
1.6 +31 -17newsite/cvs.jsp
Index: cvs.jsp
===
RCS file: /cvsroot/jboss/newsite/cvs.jsp,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- cvs.jsp 2001/07/11 06:37:00 1.5
+++ cvs.jsp 2001/08/14 04:07:51 1.6
@@ -3,9 +3,7 @@
jsp:param name=SLOGAN value=SOURCE CODE AND CVS/
/jsp:include
-
-
- !-- CONTENT --
+ !-- CONTENT --
p class=headJBOSS IS DEVELOPED PUBLICLY
p class=textJBoss is a free implementation of the J2EE interfaces from
SUN. Our code is co-developed and the source is freely available. You
can either get the code in a zip format to browse it or, if you
@@ -13,22 +11,22 @@
on your machine.
p class=textWe host our CVS at sourceforge. A
href=http://sourceforge.net; IMG
src=http://sourceforge.net/sflogo.php?group_id=22866; width=88 height=31
border=0 alt=SourceForge Logo/A
-p class=headSOURCE CODE
-p class=texta class=link
href=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/;font face=Myriad
Web,ArialbBrowse the source on-line/b/font/a
+p class=headSOURCE CODE
+p class=texta class=link
href=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/;font face=Myriad
Web,ArialbBrowse the source on-line/b/font/a
brDownload a daily updated a class=link
href=/zip_archives/snapshot of the sources/a (ZIP archive)
-p class=headCVS ENVIRONMENT
+p class=headCVS ENVIRONMENT
p class=textTo browse the source tree you bwill need a CVS client/b.
If you don't have one already installed on your machine you can download a
class=link href=http://www.jcvs.org/;jCVS/a, the CVS client in java. jCVS will
work on any platform including Linux. However we recommend the native Linux tools or
try a class=link href=http://www.wincvs.org;winCVS/a if you are based on a
win32 platform.
pbSettings for anonymous browsing:/b/p
pCVSROOT is br
-:pserver:[EMAIL PROTECTED]:/cvsroot/jboss
+:pserver:[EMAIL PROTECTED]:/cvsroot/jboss
brpassword is blank (type enter)/p
pbSettings for developer access:/b/p
- pYou have to use SSH:br
- export CVS_RSH=ssh /p
- pCVSROOT is br
-:ext:lt;sourceforge IDgt;@cvs.jboss.sourceforge.net:/cvsroot/jboss/p
-pFor further explanations see a
href=http://sourceforge.net/cvs/?group_id=22866;instructions/a at sourceforge/p
+pYou have to use SSH:br
+export CVS_RSH=ssh /p
+pCVSROOT is br
+:ext:lt;sourceforge IDgt;@cvs.jboss.sourceforge.net:/cvsroot/jboss/p
+pFor further explanations see a
href=http://sourceforge.net/cvs/?group_id=22866;instructions/a at sourceforge/p
p class=headMODULES
p class=textThe following modules are available for browsing:/p
@@ -52,15 +50,31 @@
p class=headCVS Administration Polcies
-p class=textFor our policies on CVS versioning and branching see: a
href=CVSAdmin.jspCVS
- Admin/a.
-p class=headMore information on Build and Source
- p class=textWhat is Ant?Ant is a Java based build tool. In theory it is
kind of like make without makes wrinkles.
+p class=textFor our policies on CVS versioning and branching see: a
href=CVSAdmin.jspCVS Admin/a.
+
+p class=headMore information on Build and Source
+ p class=textWhat is Ant? Ant is a Java based build tool. In theory it is
kind of like make without makes wrinkles.
p class=textWhy? Why another build tool when there is already make,
gnumake, nmake, jam, and others? Because, they are limited to the OS, or at least the
OS type such as Unix, that you are working on. Makefiles are inherently evil as well.
p class=textAnt is different. Instead a model where it is extended with
shell based commands, it is extended using Java classes. Instead of writing shell
commands, the configuration files are XML based calling out a target tree where
various tasks get executed. Each task is run by an object which implements a
particular Task interface. Granted, this removes some of the expressive power that is
inherent by being able to construct a shell command such as `find . -name foo -exec rm
{}` but it gives you the ability to be cross platform. To work anywhere and
everywhere. And hey, if you really need to execute a shell command, Ant has an exec
rule that allows different commands to be executed based on the OS that it is
executing on.
pa class=link
[JBoss-dev] Added Buildmagic User's Guide
I added the Buildmagic User's Guide to the jboss.org/cvs.jsp page under More information on Build and Source. I also checked in the pdf, as bm-usersguide.pdf. This is temporary to allow folks to understand what is going on a little more. I eventually would like to host this and the html version on sf or under a developers subdirectory under jboss.org, but I do not have time to do this at the moment. I think that there are a few minor enhancments that could be made to make the system more effective (thanks to some suggestions by Hiram). So much to do, so little time. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-450685 ] Tomcat startup fix.
Patches item #450685, was opened at 2001-08-13 21:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=450685group_id=22866 Category: None Group: v2.4 BETA (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Tomcat startup fix. Initial Comment: I needed the jar files in %JBOSS_DIST%/lib/ext to get Tomcat to startup properly. I added the following line to the tomcat.bat file: for %%i in (%JBOSS_DIST%\lib\ext\*.*) do call % TOMCAT_HOME%\bin\cpappend.bat %%i -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=450685group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-450684 ] Tomcat/JBoss Distribution
Patches item #450684, was opened at 2001-08-13 21:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=450684group_id=22866 Category: None Group: v2.4 BETA (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Tomcat/JBoss Distribution Initial Comment: I needed the jar files in %JBOSS_DIST%/lib/ext to get Tomcat to startup properly. I added the following line to the tomcat.bat file: for %%i in (%JBOSS_DIST%\lib\ext\*.*) do call % TOMCAT_HOME%\bin\cpappend.bat %%i -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=450684group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] main\org\jboss\ejb\Container.java:533
Simple misspellingin version of 1.54...it was breaking the HEAD build. Since I can't commit, this was the next best thing to do. On a side note, how stable is the 2.4.xx?? Matt ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb Container.java
User: user57
Date: 01/08/13 22:38:48
Modified:src/main/org/jboss/ejb Container.java
Log:
o fixed typo wrapped some javadocs to 80 cols
Revision ChangesPath
1.55 +22 -20jboss/src/main/org/jboss/ejb/Container.java
Index: Container.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/Container.java,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- Container.java2001/08/14 03:31:34 1.54
+++ Container.java2001/08/14 05:38:48 1.55
@@ -73,7 +73,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a.
* @author a href=[EMAIL PROTECTED]Bill Burke/a
- * @version $Revision: 1.54 $
+ * @version $Revision: 1.55 $
*
* pbRevisions:/b
*
@@ -469,17 +469,17 @@
// Begin DynamicMBean interface implementation
public Object getAttribute(String attribute)
throws AttributeNotFoundException,
- MBeanException,
- ReflectionException
+ MBeanException,
+ ReflectionException
{
return null;
}
public void setAttribute(Attribute attribute)
throws AttributeNotFoundException,
- InvalidAttributeValueException,
- MBeanException,
- ReflectionException
+ InvalidAttributeValueException,
+ MBeanException,
+ ReflectionException
{
}
@@ -493,7 +493,8 @@
return null;
}
- /** Handle a operation invocation.
+ /**
+* Handle a operation invocation.
*/
public Object invoke(String actionName, Object[] params, String[] signature)
throws MBeanException, ReflectionException
@@ -530,7 +531,7 @@
else if( actionName.equals(getHome) )
{
String className = this.getBeanMetaData().getHome();
-if( clasName != null )
+if( className != null )
{
Class clazz = this.classLoader.loadClass(className);
value = clazz;
@@ -558,7 +559,7 @@
throw new MBeanException(new IllegalArgumentException(Unknown action:
+actionName));
}
}
- catch(Exception e)
+ catch (Exception e)
{
log.error(invoke returned an exception, e);
throw new MBeanException(e, invoke returned an exception);
@@ -571,17 +572,18 @@
return value;
}
- /** Build the container MBean information on attributes, contstructors,
operations,
-and notifications. Currently there are no attributes, no constructors, no
-notifications, and the following ops:
-ul
-li'home' - invokeHome(MethodInvocation);/li
-li'remote' - invoke(MethodInvocation);/li
-li'localHome' - not implemented;/li
-li'local' - not implemented;/li
-li'getHome' - return EBJHome interface;/li
-li'getRemote' - return EJBObject interface/li
-/ul
+ /**
+* Build the container MBean information on attributes, contstructors,
+* operations, and notifications. Currently there are no attributes, no
+* constructors, no notifications, and the following ops:
+* ul
+* li'home' - invokeHome(MethodInvocation);/li
+* li'remote' - invoke(MethodInvocation);/li
+* li'localHome' - not implemented;/li
+* li'local' - not implemented;/li
+* li'getHome' - return EBJHome interface;/li
+* li'getRemote' - return EJBObject interface/li
+* /ul
*/
public MBeanInfo getMBeanInfo()
{
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: new build system
Hi, I build OK. I run OK except for one custom MBean. This is due to xml changes I guess. I receive an exception java.lang.NoClassDefFoundError: org/w3c/dom/Node On the line of my MBean that do DOMBuilder builder = new DOMBuilder(); This class is coming from JDOM. I try adding this to jboss.conf MLET CODE = org.jboss.util.ClassPathExtension ARCHIVE=hm-jmx.jar CODEBASE=../../lib/ext/ ARG TYPE=java.lang.String VALUE=../../../etc/conf/ ARG TYPE=java.lang.String VALUE=../../lib/ext/crimson.jar /MLET without success. It worked when xml stuffs was in lib/ Should I not use JDOM but pure sax instead ? Regards. Vincent. -Message d'origine- De : Jason Dillon [mailto:[EMAIL PROTECTED]] Envoye : lundi 13 aout 2001 8:04 A : [EMAIL PROTECTED] Cc : Dev JBoss Objet : RE: new build system That is a problem that will come again, I want to be sure to understand: If you add a new link in CVSROOT/modules for jboss-all, a Check Out is needed ? an Update is not enough ? Yes. Checkout is the only time that CVS will pay any attention to the CVSROOT/modules file. The exact module name you used is lost after that and all CVS has to work on is the data in CVS/Root CVS/Repository. Update simply checks the files (and sub-directories) of modules which it has previouly checked out and has CVS/* files for. It is safe to run a checkout over an existing workspace, though you might get some silly warnings. Just be sure to update afterwards for the full effect. Or is it only a problem when running first Check Out and killing it in the middle (over a 56k phone line, it will happen to others than me I bet) ? I will make clean CO at work (adsl hehe) and let you know how far I go. Checkout over an existing workspace *should not* consume that much BW. --jason _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: new build system
This is because of the classpath changes that scott made. The jaxp parser jars have been moved from lib to lib/ext. Where is your MBean loaded from, jboss.jcml or jboss.conf? If it is jboss.conf, then you will need to add the jaxp.jar and crimson.jar's to the archive list. Don't know if that helps, but I found that when I am using the XML configuration for the Log4jService, it will complain about these too. If this happens from inside jboss.jcml, and both of these files are actually in the lib/ext directory, then something else is wrong. Unfortunatly the bootstrap classloading that goes on is still a little bit of a mistery to me. SAX, DOM, Whatever. If you still have files other than jmxri.jar in your output/jboss-*/lib directory then you should probably re-build with something like this from the build module: ./build.sh clean release Or just remove everything in output/jboss-*/lib and: ./build.sh Which will install all the correct files. Let me know a little more about where this MBean is loaded and if any of this helps. --jason On Tue, 14 Aug 2001, Vincent Harcq wrote: Hi, I build OK. I run OK except for one custom MBean. This is due to xml changes I guess. I receive an exception java.lang.NoClassDefFoundError: org/w3c/dom/Node On the line of my MBean that do DOMBuilder builder = new DOMBuilder(); This class is coming from JDOM. I try adding this to jboss.conf MLET CODE = org.jboss.util.ClassPathExtension ARCHIVE=hm-jmx.jar CODEBASE=../../lib/ext/ ARG TYPE=java.lang.String VALUE=../../../etc/conf/ ARG TYPE=java.lang.String VALUE=../../lib/ext/crimson.jar /MLET without success. It worked when xml stuffs was in lib/ Should I not use JDOM but pure sax instead ? Regards. Vincent. -Message d'origine- De : Jason Dillon [mailto:[EMAIL PROTECTED]] Envoye : lundi 13 aout 2001 8:04 A : [EMAIL PROTECTED] Cc : Dev JBoss Objet : RE: new build system That is a problem that will come again, I want to be sure to understand: If you add a new link in CVSROOT/modules for jboss-all, a Check Out is needed ? an Update is not enough ? Yes. Checkout is the only time that CVS will pay any attention to the CVSROOT/modules file. The exact module name you used is lost after that and all CVS has to work on is the data in CVS/Root CVS/Repository. Update simply checks the files (and sub-directories) of modules which it has previouly checked out and has CVS/* files for. It is safe to run a checkout over an existing workspace, though you might get some silly warnings. Just be sure to update afterwards for the full effect. Or is it only a problem when running first Check Out and killing it in the middle (over a 56k phone line, it will happen to others than me I bet) ? I will make clean CO at work (adsl hehe) and let you know how far I go. Checkout over an existing workspace *should not* consume that much BW. --jason _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] main\org\jboss\ejb\Container.java:533
This should be fixed. Can't really say about 2.4.xx. I would guess relatively stable, only bug fixes are being added (I think). --jason On Tue, 14 Aug 2001, Matt Veitas wrote: Simple misspellingin version of 1.54...it was breaking the HEAD build. Since I can't commit, this was the next best thing to do. On a side note, how stable is the 2.4.xx?? Matt ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default jboss.conf
User: user57 Date: 01/08/13 23:14:48 Modified:src/etc/conf/default jboss.conf Log: o including jaxp and crimson in the archive value for Log4jService (so parsing xml configuration works again). o explicitly using the constructor to specify which file is read. Revision ChangesPath 1.22 +7 -3 jboss/src/etc/conf/default/jboss.conf Index: jboss.conf === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss.conf,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- jboss.conf2001/08/11 21:32:45 1.21 +++ jboss.conf2001/08/14 06:14:47 1.22 @@ -4,15 +4,19 @@ !-- -- !-- = -- -!-- $Id: jboss.conf,v 1.21 2001/08/11 21:32:45 user57 Exp $ -- +!-- $Id: jboss.conf,v 1.22 2001/08/14 06:14:47 user57 Exp $ -- MLET CODE=org.jboss.logging.Logger ARCHIVE=jboss.jar CODEBASE=../../lib/ext/ /MLET -!-- The log4j based logging service based on the conf log4j.properties file -- +!-- The log4j based logging service -- MLET CODE=org.jboss.logging.Log4jService - ARCHIVE=jboss.jar,log4j.jar CODEBASE=../../lib/ext/ + CODEBASE=../../lib/ext/ + ARCHIVE=jboss.jar,log4j.jar,jaxp.jar,crimson.jar + + !-- Read the conf/*/log4j.properties file -- + arg type=java.lang.String value=log4j.properties /MLET !-- Place the config directory in the classpath -- ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
