[JBoss-user] Jboss3.0 build problem
Hi all, I am having an issue with building the nightly snapshot of jboss3.0 that I downloaded from jboss.org. First up, I downloaded the tgz version of the src and encountered an error( a checksum error, but that was after it extracted the entire source) while untarring the src I conveniently ignored the check sum error and proceeded with building the src. But now I am encountering the following error while trying to executing the build script. ./build.sh help /tools/solaris8/J2SE_1.3.0/bin/../bin/sparc/native_threads/java -classpath /home/alpha3/vishwas/downloads/jakarta-ant-1.4.1/lib/jaxp.jar:/home/alpha3/vishwas/downloads/jakarta-ant-1.4.1/lib/crimson.jar:/home/alpha3/vishwas/downloads/jakarta-ant-1.4.1/lib/ant.jar:/home/alpha3/vishwas/downloads/JavaGroups/JavaGroups-2.0/classes:JavaGroups-2.0.jar::/home/alpha3/vishwas/downloads/j2sdkee1.3-src/lib/j2ee.jar:/home/alpha3/vishwas/downloads/j2sdkee1.3-src/lib/locale:.:/home/alpha3/vishwas/JavaTests:/home/alpha3/vishwas/MultiCast/JSDT-2.0/lib/jsdt.jar:/home/alpha3/vishwas/MultiCast/JSDT-2.0/lib/lrmpBig.jar:/home/alpha3/vishwas/MultiCast/JSDT-2.0/examples/classes:/tools/solaris8/J2SE_1.3.0/lib/tools.jar -Dant.home=/home/alpha3/vishwas/downloads/jakarta-ant-1.4.1 -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.crimson.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.crimson.jaxp.SAXParserFactoryImpl -Djava.protocol.handler.pkgs=planet57.net.protocol -Dbuild.script=./build.sh org.apache.tools.ant.Main -find build.xml help Searching for build.xml ... Buildfile: /home/alpha3/vishwas/downloads/jboss-all/build/build.xml BUILD FAILED Error reading project file Total time: 1 second Is there an obvious mistake that I am making?? Please help!!! -- Vishwas Raman Software Engineer, Eternal Systems, Inc, 5290 Overpass Rd, Bldg D, Santa Barbara. CA 93111 Email: [EMAIL PROTECTED] Tel: (805) 696-9051 x246 Fax: (805) 696-9083 URL: http://www.eternal-systems.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] About jaws.xml
Have a look at XDoclet - http://sf.net/projects/xdoclet - it'll do it all for you. very easy. btw - findByPrimaryKey and findAll dont need any jaws.xml configuration afaik. cheers dim - Original Message - From: "Christine" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 20, 2002 9:18 AM Subject: [JBoss-user] About jaws.xml > Hi, > > I am trying to create a jaws.xml for my CMP beans. But i didn't find any > documentation about how to write findByPrimaryKey and findAll method. > Could anyone help? Thanks > > regards, > -- > Jia (Christine) Li > > 524N ICT Building > Department of Computer Science > University of Calgary > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] About jaws.xml
Hi, I am trying to create a jaws.xml for my CMP beans. But i didn't find any documentation about how to write findByPrimaryKey and findAll method. Could anyone help? Thanks regards, -- Jia (Christine) Li 524N ICT Building Department of Computer Science University of Calgary ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re[2]: [JBoss-user] home.create throws an IllegalStateException
Hello all Friday, May 25, 2001, 6:35:04 PM, you wrote: dDC> Does your bean's ejbCreate return a proper primary key? dDC> Richard Conway wrote: >> I too am experiencing this problem. I get... >> >> [DelegateAccountEJBean] java.lang.IllegalStateException: INSERTING AN >> ALREADY EXISTING BEAN, ID = o18 a0 We met this problem just now with jBoss 2.2.2 We use BMP bean, if we use bean reference got from create, remove works ok. But if we got that reference from finder, we have INSERTING AN ALREADY EXISTING BEAN exception. If it was CMP bean, situation is obvious - we should execute getter and everything will be ok. But what shpuld we do with BMP bean? Vale! - Mikhail Akopov ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Deploying Jetspeed
I'm running into a problem deploying Jetspeed under both JBoss-Jetty and JBoss-Catalina. The Jetspeed webapp appears to be deploying correctly, but I get "Error fetching pane" messages in the Jetspeed web UI, and I see the following errors in the Jetspeed logs: [Tue Feb 19 11:19:56 PST 2002] -- ERROR -- Could not unmarshal: /opt/JBoss-2.4.4_Jetty-3.1.3-1/jboss/tmp/deploy/Default/jetspeed.war/web1003/WEB-INF/conf/wml-examples.xreg Exception: org.exolab.castor.mapping.MappingException: Nested error: org.exolab.castor.mapping.MappingException: Could not find the class org.apache.jetspeed.services.registry.RegistryFragment Some research reveals that org.apache.jetspeed.services.registry.RegistryFragment is in fact in the jetspeed-1.3a2-release.jar archive in my JBoss-2.4.4_Jetty-3.1.3-1/jboss/tmp/deploy/Default/jetspeed.war/web1003/WEB-INF/lib directory. So, it looks to me like this is some kind of classpath/classloader problem. Has anyone had this problem and solved it? Any other ideas? I found that I had to copy the castor jar file from Jetspeed into jboss/lib/ext, and that got rid of a few exceptions but I'm still left with the problem above. Thanks, Eric ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Deployment Failure JBoss 3.0beta
On 2002.02.19 12:27:01 -0500 Stephen Davidson wrote: > Additional Details; > When I shut JBoss down and restarted, Ilots of errors occurred. Does this mean that JBoss is acting inconsistently or that the first time you started jboss and then deployed your app? > I have a couple of Jars that either have common base classes, or > everything else uses (or for some of the EJB-Jar files, both). > For instance, I have a HRXBaseEJB class that most of the EJB's in all of > the jars extend, located in a jar HRXCommon.jar. It uses some EJBs from > HRXSecurity.jar. Some of these EJBs extend HRXBaseEJB. > > So I set up Class-Path in the MANIFEST.MF files, with appropriate > settings for each EJB-Jar file. So far, so good, and generally works in > Orion. (They have > some classloader issues that I seem to trigger with one or two of my Jars > - they have open bug reports on them and workarounds are available). > > When the EAR file is unpacked, the Jar files have a number prepended to > them, at random, so far as I can determine. This means that the Jar > files listed in the > MANIFEST.MF files DO NOT exist. For example, HRXCommon.jar is renamed to > 68.HRXCommon.jar on deployment. This is causing my application to fail > to deploy. I don't think you have much proof of the cause-effect relationship here. Everything in your ear should be getting into the classloader system, however it is referenced in your manifests. > > There are 12 EJB-Jar files currently, with about 130 EJBs currently > deployed, (will eventually be about 50 jars, with well over 500EJBs > total), so bundling > everything into one jar is not an option. > > How do I work-around/solve this? some helpful things to do would be: -try to make a smaller, simpler example that fails -post the jboss log (preferably with the smaller, simpler example) -if you can, send me privately the (preferable simplified) ear and I will take a look. david jencks > > -Steve > > <===Begin Sample Output===> > 11:04:52,706 INFO [MainDeployer] Deploying: > file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > 11:04:52,711 WARN [MainDeployer] The manifest entry in > file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > references URL > file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/HRXSecurity.jar > which could not be opened, entry ignored > 11:04:52,954 INFO [EJBDeployer] Deploying CodeTableEJB > 11:04:53,882 ERROR [MainDeployer] could not deploy > :file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar > java.lang.NoClassDefFoundError: com/hrnexus/security/shared/UserInterface > at java.lang.Class.getMethods0(Native Method) > at java.lang.Class.getMethods(Class.java:742) > at >org.jboss.ejb.StatefulSessionContainer.setupBeanMapping(StatefulSessionContainer.java:619) > at >org.jboss.ejb.StatefulSessionContainer.create(StatefulSessionContainer.java:200) > at org.jboss.ejb.Application.start(Application.java:223) > at org.jboss.ejb.EJBDeployer.deploy(EJBDeployer.java:459) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:457) > at >org.jboss.deployment.MainDeployer.deploySubPackages(MainDeployer.java:791) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:452) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:412) > at org.jboss.deployment.MainDeployer.scan(MainDeployer.java:271) > at org.jboss.deployment.MainDeployer.startService(MainDeployer.java:217) > at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:160) > 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.system.Server.(Server.java:157) > at org.jboss.Main.boot(Main.java:263) > at org.jboss.Main.run(Main.java:48) > at java.lang.Thread.run(Thread.java:484) > > Stephen Davidson wrote: > > > Greetings. > > > > I am trying to port an application from Orion to JBoss v3.0Beta. > > > > The Ear file is being read, and so far as I can tell, deployed (for > more > > evidence, read on). > > The War file contained in the Ear file is definately being deployed, as > > > the static webpages and at least one of the servlets are active and > > available. > > The EJB-jar from the Ear file are listed, but their EJBs are not. > > > > There are no error messages or stack traces, but the EJB classes are > > never loaded by the JVM. > > > > The jboss.xml file for the EJB.jar files appear to be correct. And the > > > application is properly deployed on Orion. > > > > Suggestions? > > > > Thanks, > > Steve > > > > > > ___ > > JBoss-user mailing list
[JBoss-user] Shutdown hangs
Whenever I shut down JBoss (3.0.0 alpha), it remains hanging at the following point: [18:40:08] INFO naming.NamingService : Stopping Any ideas why this could be happening? -- Eric Jain ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Deployment Failure JBoss 3.0beta
Structure of Ear file; Ear | - War file | - HRXCommon.jar (Uses some classes from HRXSecurity, and has an EJB) | - HRXSecurity.jar (Extends some classes from HRXCommon, and has several EJBs) | - HRXAdmin.jar (Extends some classes from HRXCommon, | uses some classes from HRXSecurity, and has lots (about 15) of EJBs) | - 8-9 other jars with dependencies similar to HRXAdmin.jar I apologize, I do not have the log from the first run. It did not display any stack traces or error messages. It just listed all of the jar files and said it was deploying them, but did not list any of the EJBs inside. -Steve David Jencks wrote: > On 2002.02.19 11:23:32 -0500 Stephen Davidson wrote: > >>Greetings. >> >>I am trying to port an application from Orion to JBoss v3.0Beta. >> >>The Ear file is being read, and so far as I can tell, deployed (for more >>evidence, read on). >>The War file contained in the Ear file is definately being deployed, as >>the static webpages and at least one of the servlets are active and >>available. >>The EJB-jar from the Ear file are listed, but their EJBs are not. >> >>There are no error messages or stack traces, but the EJB classes are >>never loaded by the JVM. >> >>The jboss.xml file for the EJB.jar files appear to be correct. And the >>application is properly deployed on Orion. >> >>Suggestions? >> > > What's the structure of your .ear and what does the jboss log say is > happening when you deploy? > > david jencks > >>Thanks, >>Steve >> >> >>___ >>JBoss-user mailing list >>[EMAIL PROTECTED] >>https://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Deployment Failure JBoss 3.0beta
Hi, There's still some problems reported by WebIntegrationUnitTestCase in JBoss3.0.0DR1 due to the deployer rewrite. You might want to monitor this link. http://lubega.com/testarchive/?M=D Hopefully, this will be fixed soon :-) Regards, Adrian >From: Stephen Davidson <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: [JBoss-user] Deployment Failure JBoss 3.0beta >Date: Tue, 19 Feb 2002 10:23:32 -0600 > >Greetings. > >I am trying to port an application from Orion to JBoss v3.0Beta. > >The Ear file is being read, and so far as I can tell, deployed (for more >evidence, read on). >The War file contained in the Ear file is definately being deployed, as the >static webpages and at least one of the servlets are active and available. >The EJB-jar from the Ear file are listed, but their EJBs are not. > >There are no error messages or stack traces, but the EJB classes are never >loaded by the JVM. > >The jboss.xml file for the EJB.jar files appear to be correct. And the >application is properly deployed on Orion. > >Suggestions? > >Thanks, >Steve > > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Deployment Failure JBoss 3.0beta
Additional Details; When I shut JBoss down and restarted, Ilots of errors occurred. I have a couple of Jars that either have common base classes, or everything else uses (or for some of the EJB-Jar files, both). For instance, I have a HRXBaseEJB class that most of the EJB's in all of the jars extend, located in a jar HRXCommon.jar. It uses some EJBs from HRXSecurity.jar. Some of these EJBs extend HRXBaseEJB. So I set up Class-Path in the MANIFEST.MF files, with appropriate settings for each EJB-Jar file. So far, so good, and generally works in Orion. (They have some classloader issues that I seem to trigger with one or two of my Jars - they have open bug reports on them and workarounds are available). When the EAR file is unpacked, the Jar files have a number prepended to them, at random, so far as I can determine. This means that the Jar files listed in the MANIFEST.MF files DO NOT exist. For example, HRXCommon.jar is renamed to 68.HRXCommon.jar on deployment. This is causing my application to fail to deploy. There are 12 EJB-Jar files currently, with about 130 EJBs currently deployed, (will eventually be about 50 jars, with well over 500EJBs total), so bundling everything into one jar is not an option. How do I work-around/solve this? -Steve <===Begin Sample Output===> 11:04:52,706 INFO [MainDeployer] Deploying: file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar 11:04:52,711 WARN [MainDeployer] The manifest entry in file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar references URL file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/HRXSecurity.jar which could not be opened, entry ignored 11:04:52,954 INFO [EJBDeployer] Deploying CodeTableEJB 11:04:53,882 ERROR [MainDeployer] could not deploy :file:/home/jboss/jboss-all/build/output/jboss-3.0.0beta/tmp/deploy/68.HRXCommon.jar java.lang.NoClassDefFoundError: com/hrnexus/security/shared/UserInterface at java.lang.Class.getMethods0(Native Method) at java.lang.Class.getMethods(Class.java:742) at org.jboss.ejb.StatefulSessionContainer.setupBeanMapping(StatefulSessionContainer.java:619) at org.jboss.ejb.StatefulSessionContainer.create(StatefulSessionContainer.java:200) at org.jboss.ejb.Application.start(Application.java:223) at org.jboss.ejb.EJBDeployer.deploy(EJBDeployer.java:459) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:457) at org.jboss.deployment.MainDeployer.deploySubPackages(MainDeployer.java:791) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:452) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:412) at org.jboss.deployment.MainDeployer.scan(MainDeployer.java:271) at org.jboss.deployment.MainDeployer.startService(MainDeployer.java:217) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:160) 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.system.Server.(Server.java:157) at org.jboss.Main.boot(Main.java:263) at org.jboss.Main.run(Main.java:48) at java.lang.Thread.run(Thread.java:484) Stephen Davidson wrote: > Greetings. > > I am trying to port an application from Orion to JBoss v3.0Beta. > > The Ear file is being read, and so far as I can tell, deployed (for more > evidence, read on). > The War file contained in the Ear file is definately being deployed, as > the static webpages and at least one of the servlets are active and > available. > The EJB-jar from the Ear file are listed, but their EJBs are not. > > There are no error messages or stack traces, but the EJB classes are > never loaded by the JVM. > > The jboss.xml file for the EJB.jar files appear to be correct. And the > application is properly deployed on Orion. > > Suggestions? > > Thanks, > Steve > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > -- Stephen Davidson Java Consultant Delphi Consultants, LLC http://www.delphis.com Phone: 214-696-6224 x208 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Deployment Failure JBoss 3.0beta
On 2002.02.19 11:23:32 -0500 Stephen Davidson wrote: > Greetings. > > I am trying to port an application from Orion to JBoss v3.0Beta. > > The Ear file is being read, and so far as I can tell, deployed (for more > evidence, read on). > The War file contained in the Ear file is definately being deployed, as > the static webpages and at least one of the servlets are active and > available. > The EJB-jar from the Ear file are listed, but their EJBs are not. > > There are no error messages or stack traces, but the EJB classes are > never loaded by the JVM. > > The jboss.xml file for the EJB.jar files appear to be correct. And the > application is properly deployed on Orion. > > Suggestions? What's the structure of your .ear and what does the jboss log say is happening when you deploy? david jencks > > Thanks, > Steve > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Deployment Failure JBoss 3.0beta
are ther some error messages while deploying ? are EJB references declared in web.xml do you have a jboss-web.xml in the webapp with EJB JNDI references properly set same for the EJB themselves between the ejb-jar.xml and jboss.xml the syntax is not the same , or at least the file name and DTD are different... > -Message d'origine- > De: Stephen Davidson [mailto:[EMAIL PROTECTED]] > Date: mardi 19 février 2002 17:24 > À: [EMAIL PROTECTED] > Objet: [JBoss-user] Deployment Failure JBoss 3.0beta > > > Greetings. > > I am trying to port an application from Orion to JBoss v3.0Beta. > > The Ear file is being read, and so far as I can tell, > deployed (for more evidence, read on). > The War file contained in the Ear file is definately being > deployed, as the static webpages and at least one of the > servlets are active and available. > The EJB-jar from the Ear file are listed, but their EJBs are not. > > There are no error messages or stack traces, but the EJB > classes are never loaded by the JVM. > > The jboss.xml file for the EJB.jar files appear to be > correct. And the application is properly deployed on Orion. > > Suggestions? > > Thanks, > Steve > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Deployment Failure JBoss 3.0beta
Greetings. I am trying to port an application from Orion to JBoss v3.0Beta. The Ear file is being read, and so far as I can tell, deployed (for more evidence, read on). The War file contained in the Ear file is definately being deployed, as the static webpages and at least one of the servlets are active and available. The EJB-jar from the Ear file are listed, but their EJBs are not. There are no error messages or stack traces, but the EJB classes are never loaded by the JVM. The jboss.xml file for the EJB.jar files appear to be correct. And the application is properly deployed on Orion. Suggestions? Thanks, Steve ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] logging and admininstration
I'm not sure.
I've been thinking about writing a PropertyService
for setting properties. This would allow them to be configured
in jboss.jcml and also allow them to be changed at runtime through
the JMX interface.
But it is about priority 145 on my to-do list :-)
Note: This won't work for all properties. I think some
are only checked by the JVM at start-up.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] logging and admininstration
>Date: Tue, 19 Feb 2002 07:10:47 -0500
>
>thanks. if i move to 2.4.4 though, what is the proper solution for setting
>system properties -D?
>
>-Original Message-
>From: Adrian Brock [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, February 19, 2002 5:20 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: RE: [JBoss-user] logging and admininstration
>
>
>You can create a classpath extension for a directory
>in jboss.conf.
>Just put a '/' on the end of the url and don't put
>any jars or zips in the directory.
>
>Regards,
>Adrian
>
> >From: "Eric Kaplan" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >CC: <[EMAIL PROTECTED]>
> >Subject: RE: [JBoss-user] logging and admininstration
> >Date: Mon, 18 Feb 2002 22:15:32 -0500
> >
> >couple more questions wrt 3 below. we're using jboss 2.4.1, which seems
>to
> >use jboss.properties, but i think you're saying that the latest version
>of
> >jboss no longer uses it? also, in development we have a classes
>directory
> >which contains the heierarchy of all our class files, so there is no jar
>to
> >copy to lib/ext. what should we do in this case?
> >
> >thanks
> >
> >eric
> >
> >
> >
> >-Original Message-
> >From: Adrian Brock [mailto:[EMAIL PROTECTED]]
> >Sent: Monday, February 18, 2002 1:43 PM
> >To: [EMAIL PROTECTED]
> >Cc: [EMAIL PROTECTED]
> >Subject: Re: [JBoss-user] logging and admininstration
> >
> >
> >Here's some short answers.
> >
> >1) Stop on error
> >JBoss is designed to host many services concurrently.
> >There is no mechanism to say one is critical and end the server.
> >
> >JBoss3.0 introduces the ideas of dependencies.
> >If the database doesn't come up, neither will services that
> >use it, instead they wait. When you fix the database config,
> >restart the database service and all the dependencies start as well.
> >There is no need to end the server.
> >You can do a similar thing on 2.4.4, but you have to manually
> >work out the dependencies, i.e. which services need to be restarted.
> >
> >2) Log4j
> >The best way to do logging for a bean (at the moment)
> >private static final Category log = Category.newInstance(MyClass.class);
> >
> >If you want to separate the logging from JBoss, change
> >log4.properties to have something like
> >
> >log4j.com.acme=INFO, MyAppender
> >log4j.additivity.com.acme=false
> >log4j.appender.MyAppender={etc.}
> >
> >Assuming all your beans are in the package com.acme
> >
> >If you want to customize log4j, put your customisations in a jar,
> >and add the jar to the Log4jService "archives" attribute in jboss.conf
> >Be careful, make sure your customisations don't conflict with
> >jboss's own.
> >
> >3) run.bat
> >Don't put anything in the classpath of run.bat, especially not
> >something that uses Class.forName() to load classes.
> >Put your jars in jboss/lib/ext
> >There used to be a jboss.properties for system properties. It was
> >removed, I don't know why? I guess it was used as a dumping ground
> >by developers when they should have been using jboss.jcml for
> >configuration.
> >
> >Regards,
> >Adrian
> >
> >
> > >From: "Eric Kaplan" <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Subject: [JBoss-user] logging and admininstration
> > >Date: Mon, 18 Feb 2002 12:25:27 -0500
> > >
> > >Three questions:
> > >
> > >1. Typically, we bring up the application server and eyeball the output
> >for
> > >obvious errors, which are one of three typically:
> > > - Cannot bind to the required port, usually because a jboss instance
> > >is already running
> > > - Cannot create one or more db pools, usually because the database
> > >is down
> > > - One or more errors deploying the beans, including verifier
> > >problems.
> > >If we see an error, we fix it and restart. However, in production, we
> >want
> > >to automatically bring up the server, detect problems, and exit with an
> > >error code. Is there a straightforward way of doing this?
> > >
> > >2. Logging with log4j. Log4j on its own is easy. However, I'm still
> > >frustrated getting my beans to log using log4j with jboss. Scanning
>the
> > >forum, it seems there are a LOT of people having the same problem. We
> >are
> > >probably all doing the same thing wrong, but it's not clear exactly
>what
> > >the
> > >remedy is. Can someone please tell me? I would think I could get the
> > >latest log4j and log4-core jars, put them in the classpath, and roll,
>but
> > >this is not the case. Please let me know what I need to do?
> > >
> > >3. We
RE: [JBoss-user] logging and admininstration
log4.jar is in lib/ext, not lib4j-core.ext. perhaps this is the time to upgrade to 2.4.4. thanks for your help eric -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 6:02 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-user] logging and admininstration Hi, I can imagine your frustration. I can't see any bug fixes since 2.4.1 except for RMI-IIOP checking in the verifier and license changes from GPL to LGPL. This certainly works in 2.4.4, sorry I've never used 2.4.1 Maybe the fix isn't in an obvious place? Do you have log4j.jar in lib/ext? Don't put it in the classpath, it can't see the rest of the system from there, hence the other errors you report. Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] logging and admininstration >Date: Mon, 18 Feb 2002 21:58:46 -0500 > >Adrian > >I'm not sure what I need to do still. I added the simple log4j code you >suggested to one of my beans, and when i started jboss, without putting >log4j.jars in the startup classpath, I get... > >[Verifier] java.lang.NoClassDefFoundError: org/apache/log4j/Category >[Verifier] at >com.abp.ejb.ybpreloadprocessor.YBPreloadProcessorBean. >(YBPreloadProcessorBean.java:46) >[Verifier] at java.lang.Class.newInstance0(Native Method) >[Verifier] at java.lang.Class.newInstance(Unknown Source) >[Verifier] at >org.jboss.verifier.strategy.AbstractVerifier.hasDefaultConstr >uctor(AbstractVerifier.java:356) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.verifySessionBean(E >JBVerifier11.java:630) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.checkSession(EJBVer >ifier11.java:93) >[Verifier] at >org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:134) > >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:4 >67) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >69) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >04) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.j >ava:494) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeploy >er.java:468) >[Verifier] at >org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:20 >8) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379) >[Verifier] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217) >[Verifier] at >org.jboss.ejb.AutoDeployer.startService(AutoDeployer.java:353 >) >[Verifier] at >org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport. >java:107) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.configuration.ConfigurationService$ServiceProxy.inv >oke(ConfigurationService.java:836) >[Verifier] at $Proxy0.start(Unknown Source) >[Verifier] at >org.jboss.util.ServiceControl.start(ServiceControl.java:81) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.Main.(Main.java:210) >[Verifier] at org.jboss.Main$1.run(Main.java:116) >[Verifier] at java.security.AccessController.doPrivileged(Native >Method) >[Verifier] at org.jboss.Main.main(Main.java:112) >[Container factory] Deploying YBPreloadProcessorEJB >[Bean Cache] Cache policy scheduler started > > >If I then explicitly put log4j.jar, I get a different error... > >JBOSS_CLASSPATH=c:\armanta-abp\build\classes;c:\armanta\lib\log4j.jar;c:\ar m >anta >\build\lib\ext\jakarta-regexp-1.2.jar;c:\armanta\build\lib\ext\classes12.zi p >;c:\ >armanta\build\classes;c:\armanta\build\lib\help.jar;run.jar;../lib/crimson. j >ar >jboss.home = C:\armanta-3rdparty\JBoss-2.4.1_Jetty-3.1.RC9-1\jboss >Using JAAS LoginConfig: >file:/C:/armanta-3rdparty/JBoss-2.4.1_Jetty-3.1.RC9-1/jb >oss/conf/default/auth.conf >Using configuration "default" >log4j:ERROR Could not instantiate class >[org.jboss.logging.log4j.ConsoleAppender >]. >java.lang
RE: [JBoss-user] logging and admininstration
Hi, I can imagine your frustration. I can't see any bug fixes since 2.4.1 except for RMI-IIOP checking in the verifier and license changes from GPL to LGPL. This certainly works in 2.4.4, sorry I've never used 2.4.1 Maybe the fix isn't in an obvious place? Do you have log4j.jar in lib/ext? Don't put it in the classpath, it can't see the rest of the system from there, hence the other errors you report. Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] logging and admininstration >Date: Mon, 18 Feb 2002 21:58:46 -0500 > >Adrian > >I'm not sure what I need to do still. I added the simple log4j code you >suggested to one of my beans, and when i started jboss, without putting >log4j.jars in the startup classpath, I get... > >[Verifier] java.lang.NoClassDefFoundError: org/apache/log4j/Category >[Verifier] at >com.abp.ejb.ybpreloadprocessor.YBPreloadProcessorBean. >(YBPreloadProcessorBean.java:46) >[Verifier] at java.lang.Class.newInstance0(Native Method) >[Verifier] at java.lang.Class.newInstance(Unknown Source) >[Verifier] at >org.jboss.verifier.strategy.AbstractVerifier.hasDefaultConstr >uctor(AbstractVerifier.java:356) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.verifySessionBean(E >JBVerifier11.java:630) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.checkSession(EJBVer >ifier11.java:93) >[Verifier] at >org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:134) > >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:4 >67) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >69) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >04) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.j >ava:494) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeploy >er.java:468) >[Verifier] at >org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:20 >8) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379) >[Verifier] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217) >[Verifier] at >org.jboss.ejb.AutoDeployer.startService(AutoDeployer.java:353 >) >[Verifier] at >org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport. >java:107) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.configuration.ConfigurationService$ServiceProxy.inv >oke(ConfigurationService.java:836) >[Verifier] at $Proxy0.start(Unknown Source) >[Verifier] at >org.jboss.util.ServiceControl.start(ServiceControl.java:81) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.Main.(Main.java:210) >[Verifier] at org.jboss.Main$1.run(Main.java:116) >[Verifier] at java.security.AccessController.doPrivileged(Native >Method) >[Verifier] at org.jboss.Main.main(Main.java:112) >[Container factory] Deploying YBPreloadProcessorEJB >[Bean Cache] Cache policy scheduler started > > >If I then explicitly put log4j.jar, I get a different error... > >JBOSS_CLASSPATH=c:\armanta-abp\build\classes;c:\armanta\lib\log4j.jar;c:\arm >anta >\build\lib\ext\jakarta-regexp-1.2.jar;c:\armanta\build\lib\ext\classes12.zip >;c:\ >armanta\build\classes;c:\armanta\build\lib\help.jar;run.jar;../lib/crimson.j >ar >jboss.home = C:\armanta-3rdparty\JBoss-2.4.1_Jetty-3.1.RC9-1\jboss >Using JAAS LoginConfig: >file:/C:/armanta-3rdparty/JBoss-2.4.1_Jetty-3.1.RC9-1/jb >oss/conf/default/auth.conf >Using configuration "default" >log4j:ERROR Could not instantiate class >[org.jboss.logging.log4j.ConsoleAppender >]. >java.lang.ClassNotFoundException: org.jboss.logging.log4j.ConsoleAppender > at java.net.URLClassLoader$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at sun
RE: [JBoss-user] logging and admininstration
You can create a classpath extension for a directory
in jboss.conf.
Just put a '/' on the end of the url and don't put
any jars or zips in the directory.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>CC: <[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] logging and admininstration
>Date: Mon, 18 Feb 2002 22:15:32 -0500
>
>couple more questions wrt 3 below. we're using jboss 2.4.1, which seems to
>use jboss.properties, but i think you're saying that the latest version of
>jboss no longer uses it? also, in development we have a classes directory
>which contains the heierarchy of all our class files, so there is no jar to
>copy to lib/ext. what should we do in this case?
>
>thanks
>
>eric
>
>
>
>-Original Message-
>From: Adrian Brock [mailto:[EMAIL PROTECTED]]
>Sent: Monday, February 18, 2002 1:43 PM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: [JBoss-user] logging and admininstration
>
>
>Here's some short answers.
>
>1) Stop on error
>JBoss is designed to host many services concurrently.
>There is no mechanism to say one is critical and end the server.
>
>JBoss3.0 introduces the ideas of dependencies.
>If the database doesn't come up, neither will services that
>use it, instead they wait. When you fix the database config,
>restart the database service and all the dependencies start as well.
>There is no need to end the server.
>You can do a similar thing on 2.4.4, but you have to manually
>work out the dependencies, i.e. which services need to be restarted.
>
>2) Log4j
>The best way to do logging for a bean (at the moment)
>private static final Category log = Category.newInstance(MyClass.class);
>
>If you want to separate the logging from JBoss, change
>log4.properties to have something like
>
>log4j.com.acme=INFO, MyAppender
>log4j.additivity.com.acme=false
>log4j.appender.MyAppender={etc.}
>
>Assuming all your beans are in the package com.acme
>
>If you want to customize log4j, put your customisations in a jar,
>and add the jar to the Log4jService "archives" attribute in jboss.conf
>Be careful, make sure your customisations don't conflict with
>jboss's own.
>
>3) run.bat
>Don't put anything in the classpath of run.bat, especially not
>something that uses Class.forName() to load classes.
>Put your jars in jboss/lib/ext
>There used to be a jboss.properties for system properties. It was
>removed, I don't know why? I guess it was used as a dumping ground
>by developers when they should have been using jboss.jcml for
>configuration.
>
>Regards,
>Adrian
>
>
> >From: "Eric Kaplan" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: [JBoss-user] logging and admininstration
> >Date: Mon, 18 Feb 2002 12:25:27 -0500
> >
> >Three questions:
> >
> >1. Typically, we bring up the application server and eyeball the output
>for
> >obvious errors, which are one of three typically:
> > - Cannot bind to the required port, usually because a jboss instance
> >is already running
> > - Cannot create one or more db pools, usually because the database
> >is down
> > - One or more errors deploying the beans, including verifier
> >problems.
> >If we see an error, we fix it and restart. However, in production, we
>want
> >to automatically bring up the server, detect problems, and exit with an
> >error code. Is there a straightforward way of doing this?
> >
> >2. Logging with log4j. Log4j on its own is easy. However, I'm still
> >frustrated getting my beans to log using log4j with jboss. Scanning the
> >forum, it seems there are a LOT of people having the same problem. We
>are
> >probably all doing the same thing wrong, but it's not clear exactly what
> >the
> >remedy is. Can someone please tell me? I would think I could get the
> >latest log4j and log4-core jars, put them in the classpath, and roll, but
> >this is not the case. Please let me know what I need to do?
> >
> >3. We have a couple of system properties (-D flag) as well as classpath
> >extensions to make when running jboss. We currently have hacked run.bat,
> >but I don't think this is a great solution. What is the sanctioned way
>in
> >jboss for dealing with this?
> >
> >Thanks
> >
> >Eric Kaplan
> >Armanta, Inc.
> >55 Madison Ave.
> >Morristown, NJ 07960
> >Phone: (973) 326-9600
> >
> ><< winmail.dat >>
>
>
>_
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] logging and admininstration
> > 2) Log4j > > The best way to do logging for a bean (at the moment) > > private static final Category log = Category.newInstance(MyClass.class); > > > >The following accomplishes the same thing, and can be cut and pasted from >one source to the next. > >private static final Category log = >Category.getInstance(getClass().getName()); Blind leading the Blind :-) Of course, it is getInstance() not newInstance() But you cannot use getClass() from a static context, you need an object for that :-( The reason for static is to avoid serialization problems. And the ejb spec requires all static attributes to be final. > > > 3) run.bat > > Don't put anything in the classpath of run.bat, especially not > > something that uses Class.forName() to load classes. > > Put your jars in jboss/lib/ext > >I would disagree with this. I prefer to keep the JBoss directories >"virgin", and add whatever I need extra to an external directory. I then >modify run.sh to put my extra jars on JBoss's classpath. You can probably >accomplish the same thing with classpath extensions. By doing this, >upgrading from one version of JBoss to the next is easier. I try to follow >this same philosophy with other packages (e.g., Tomcat.) > The lib/myext is better. In the future the JBoss3 branch will keep track of which deployments use each jar for automatic dependency checking. This could also lead to hot-deploying util jars that use a JBoss classloader. If you load from the classpath in run.sh, it can't do this :-( > > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user Regards, Adrian _ Send and receive Hotmail on your mobile device: http://mobile.msn.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Passing an InputStream to an EJB
See the discussion in the thread with subject "Streams" on this list (from about a week ago). It might be related to your problem... Peter On Monday 18 February 2002 15:10, Andrea Cervellati wrote: > Hi, > > I'm using JBoss 2.4.3-Tomcat 4.0 and I have a web app that allows users to > upload files to the server. > > I have a servlet that takes the multipart form data request from the client > with one file and a text description of it. > I'm using the O'Reilly pack to menage the parts of the request. > > The name and the description are sent as String along with an InputStream > of the file to an ejb that takes care of the storing. > > The problem is that if I pass an InputStream the file is not stored > correctly. For example a MS Word document sent from the client is stored in > a strange manner (something like a "maker" file). > If I send a FileInputStream the file is stored correctly, and I have no > problem. But I want the ejb takes care of the storing, not the servlet, and > if I use a FileInputStream I need to temporally save the stream to a file > (this is a very ugly solution!). > > Can someone tell me why is it happening and how can I do to fix the > problem? > > Thanks in advance > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Passing an InputStream to an EJB
Title: RE: [JBoss-user] Passing an InputStream to an EJB Doesn't the whole InputStream get serializated before send - I mean in array? Why dont you just send array,maybe compressed? For large files, I would use either ftp or oreilly com package. By -Original Message- From: Andrea Cervellati [mailto:[EMAIL PROTECTED]] Sent: 18. februar 2002 15:10 To: [EMAIL PROTECTED] Subject: [JBoss-user] Passing an InputStream to an EJB Hi, I'm using JBoss 2.4.3-Tomcat 4.0 and I have a web app that allows users to upload files to the server. I have a servlet that takes the multipart form data request from the client with one file and a text description of it. I'm using the O'Reilly pack to menage the parts of the request. The name and the description are sent as String along with an InputStream of the file to an ejb that takes care of the storing. The problem is that if I pass an InputStream the file is not stored correctly. For example a MS Word document sent from the client is stored in a strange manner (something like a "maker" file). If I send a FileInputStream the file is stored correctly, and I have no problem. But I want the ejb takes care of the storing, not the servlet, and if I use a FileInputStream I need to temporally save the stream to a file (this is a very ugly solution!). Can someone tell me why is it happening and how can I do to fix the problem? Thanks in advance ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
