Re: How to Use Maven with Geronimo J2EE project
For now, I looked at the geronimo sample 2.1.2 and how maven is setup to build the samples. Specifically, I looked at the calculator Pom.xml and set up mine to have parent groupdId=org.apache.geronimo.samples so that I can build my J2EE as tomcat plugin? Do you think that it will work thanks B bongosdude wrote: > > > The build from the trunk is failed with error. I have to try again another > day. Hope that these bugs are fixed by then. > > INFO] The following tests failed: > [INFO] * webservices-testsuite/jaxws-provider-tests - > /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/jaxws-provider-tests/build.log > [INFO] * webservices-testsuite/jaxws-tests - > /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/jaxws-tests/build.log > [INFO] * webservices-testsuite/jaxws-wsa-tests - > /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/jaxws-wsa-tests/build.log > [INFO] * webservices-testsuite/saaj-tests - > /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/saaj-tests/build.log > [INFO] * webservices-testsuite/stax-tests - > /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/stax-tests/build.log > [INFO] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] 5 of 35 tests failed > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 123 minutes 17 seconds > [INFO] Finished at: Wed Dec 17 20:48:06 EST 2008 > [INFO] Final Memory: 385M/747M > [INFO] > > > > Kevan Miller wrote: >> >> >> On Dec 15, 2008, at 3:10 AM, David Jencks wrote: >> >>> >>> On Dec 14, 2008, at 7:17 PM, bongosdude wrote: >>> I would lile to use maven to mange our project build/deploy during development, QA and production release. Maven is good at managing dependencies. While GEP can get us up to speed in development, it is tricky to manage dependency using eclipse among team members. I have tried to read geronimo sample to see how maven is used to build and deploy geronimo sample. However, I could not find out how maven is used with gernonimo. Can someone help to explain or give me suggestions on how I can learn more on this subject? >>> >>> 0. For team-wide access set up a team accessible maven repository. >>> I've demoed this using sonatype nexus which works great but you can >>> also set up httpd or presumably a lot of other things. >>> >>> 1. set up a maven project for each of your apps to use the geronimo >>> car-maven-plugin to "pre-deploy" your application into a geronimo >>> plugin. Deploy it into the team-wide maven repository (configure the >>> deploymenManagement of your pom to point to the team repo) >>> >>> 2. set up a maven project to assemble a custom server, again using >>> the car-maven-plugin. Include the framework plugin group and your >>> apps and any optional stuff from geronimo you might want such as >>> parts of the admin console. Everything else needed will be pulled >>> in too. >>> >>> 3. After deploying the assembled server it too will be available >>> from the shared repo. >>> >>> There are a couple geronimo archetypes to help setting up these >>> maven projects but they are rather primitive and dont use the new >>> archetype plugin features they still might help. >>> geronimo-plugin-archetype sets up a plugin project >>> geronimo-assembly-archetype sets up a custom server assembly project. >>> >>> Perhaps the simplest example of all this in action is in geronimo >>> trunk in the plugins/monitoring console: along with the base code, >>> and the monitoring console portal application, we build plugins for >>> the app and a server containing the monitoring console and run a >>> simple integration test. >> >> Just going to point out that this is not the *only* technique of using >> maven with Geronimo. You can also build your application, and deploy >> it (using maven or using Geronimo administrative commands). Building a >> customized server is certainly a nice feature. However, it's not the >> only option... >> >> This would be a nice documentation project for someone... >> >> --kevan >> >> > > - B Amigo:super: -- View this message in context: http://www.nabble.com/How-to-Use-Maven-with-Geronimo-J2EE-project-tp21007724s134p21065925.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: How to Use Maven with Geronimo J2EE project
The build from the trunk is failed with error. I have to try again another day. Hope that these bugs are fixed by then. INFO] The following tests failed: [INFO] * webservices-testsuite/jaxws-provider-tests - /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/jaxws-provider-tests/build.log [INFO] * webservices-testsuite/jaxws-tests - /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/jaxws-tests/build.log [INFO] * webservices-testsuite/jaxws-wsa-tests - /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/jaxws-wsa-tests/build.log [INFO] * webservices-testsuite/saaj-tests - /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/saaj-tests/build.log [INFO] * webservices-testsuite/stax-tests - /Users/Dad/Documents/opensource/geronimo-trunk-2.2/testsuite/webservices-testsuite/stax-tests/build.log [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] 5 of 35 tests failed [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 123 minutes 17 seconds [INFO] Finished at: Wed Dec 17 20:48:06 EST 2008 [INFO] Final Memory: 385M/747M [INFO] Kevan Miller wrote: > > > On Dec 15, 2008, at 3:10 AM, David Jencks wrote: > >> >> On Dec 14, 2008, at 7:17 PM, bongosdude wrote: >> >>> >>> I would lile to use maven to mange our project build/deploy during >>> development, QA and production release. Maven is good at managing >>> dependencies. While GEP can get us up to speed in development, it >>> is tricky >>> to manage dependency using eclipse among team members. I have tried >>> to read >>> geronimo sample to see how maven is used to build and deploy geronimo >>> sample. However, I could not find out how maven is used with >>> gernonimo. >>> >>> Can someone help to explain or give me suggestions on how I can >>> learn more >>> on this subject? >> >> 0. For team-wide access set up a team accessible maven repository. >> I've demoed this using sonatype nexus which works great but you can >> also set up httpd or presumably a lot of other things. >> >> 1. set up a maven project for each of your apps to use the geronimo >> car-maven-plugin to "pre-deploy" your application into a geronimo >> plugin. Deploy it into the team-wide maven repository (configure the >> deploymenManagement of your pom to point to the team repo) >> >> 2. set up a maven project to assemble a custom server, again using >> the car-maven-plugin. Include the framework plugin group and your >> apps and any optional stuff from geronimo you might want such as >> parts of the admin console. Everything else needed will be pulled >> in too. >> >> 3. After deploying the assembled server it too will be available >> from the shared repo. >> >> There are a couple geronimo archetypes to help setting up these >> maven projects but they are rather primitive and dont use the new >> archetype plugin features they still might help. >> geronimo-plugin-archetype sets up a plugin project >> geronimo-assembly-archetype sets up a custom server assembly project. >> >> Perhaps the simplest example of all this in action is in geronimo >> trunk in the plugins/monitoring console: along with the base code, >> and the monitoring console portal application, we build plugins for >> the app and a server containing the monitoring console and run a >> simple integration test. > > Just going to point out that this is not the *only* technique of using > maven with Geronimo. You can also build your application, and deploy > it (using maven or using Geronimo administrative commands). Building a > customized server is certainly a nice feature. However, it's not the > only option... > > This would be a nice documentation project for someone... > > --kevan > > - B Amigo:super: -- View this message in context: http://www.nabble.com/How-to-Use-Maven-with-Geronimo-J2EE-project-tp21007724s134p21065882.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Custom Server Config - errors
On Dec 16, 2008, at 8:27 PM, Ray_Clough wrote: I have created a custom Server config using the Geronimo Console. Some pages cause an "IllegalStateException - no org.apache.InstanceManager set in ServletContext". When I run in the full server, I do not get this error, so it must be something missing from my configuration. The app uses jsf (with Facelets) as well as older JSPX pages. I think that it is the JSPX pages which cause the problem. Any ideas what I did not include which I should have? We use a customized version of jasper that handles annotations in a way that can be related to geronimo's handling. This has been in tomcat trunk for over a year but has not yet made it into an official tomcat release. If you are precompiling your jsps with a non-geronimo jasper you would get the error you note. However since your app runs OK before extracting the custom server it seems there must be another problem. Could you check what jasper version is in your custom server and original geronimo server? Do you supply a geronimo-plugin.xml for your app or do you let geronimo generate it? If you can find it and show the environment section that would be helpful. thanks david jencks Thank you very much, - Ray Clough -- View this message in context: http://www.nabble.com/Custom-Server-Config---errors-tp21046988s134p21046988.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: feature? ContainerGroup
>>> >>> On that same line, I also need to be able to configure logging for each >>> JettyContainer on each port (project), configuring the log name and >>> location. I >>> need separated log files, and I also need syslog facility. >> What is the syslog facility? Do you know if it is available in plain >> jetty? > > Plain jetty has it, only as built in to log4j. > Here is the sample: > > file: Jetty/extra/resources/log4j.xml > - > > > http://jakarta.apache.org/log4j/";; > debug="false"> > ... > > ... > > - > > However, We use Syslog to send all our access logs to a centralized server. > Although geronimo.log, the "error" log, is log4j, configured in > var/log/server-log4j.properties - It looks like NCSARequestLog, the "access" > log, is not Log4j > > Do you know any more about this? > > Syslog is an operating system level logging mechanism. > OS application send their logs to the syslog daemon in addition to, or instead > of, to a file. > The syslog manages the log information, sending it to disk or over the network > to a centralized logging server. > > http://en.wikipedia.org/wiki/Syslog > > The syslog facility is something like a group. The group is configured to > operate in some fashion, so you can do something like send this facility to > this > log file, and send this facility to this centralized log server. > This thread described how to set up separated logging for each container, which entailed deploying a gbean (which only contained a single plan.xml file) to configure a new instance of NCSARequestLog. Each instance is configured separately, and then referenced in the container configuration. One would likely want to deploy new instances of WebContainer and RequestLog together in a single gbean. As far as syslog support goes, there is none for access/request logs. Syslog exists in Jetty for Application/server logs however. There is now a Feature Request submitted to the Jetty Project: http://jira.codehaus.org/browse/JETTY-835 It entails a request to implement a new RequestLog with support for slf4j (http://www.slf4j.org/) and Logback (http://logback.qos.ch/). Logback support many appenders, with support for creating custom appenders (http://logback.qos.ch/manual/appenders.html) Among the supported appenders are: ConsoleAppender http://logback.qos.ch/manual/appenders.html#ConsoleAppender FileAppender http://logback.qos.ch/manual/appenders.html#FileAppender RollingFileAppender http://logback.qos.ch/manual/appenders.html#RollingFileAppender FixedWindowRollingPolicy http://logback.qos.ch/manual/appenders.html#FixedWindowRollingPolicy TimeBasedRollingPolicy http://logback.qos.ch/manual/appenders.html#TimeBasedRollingPolicy SizeBasedTriggeringPolicy http://logback.qos.ch/manual/appenders.html#SizeBasedTriggeringPolicy SocketAppender http://logback.qos.ch/manual/appenders.html#SocketAppender JMSAppenderBase http://logback.qos.ch/manual/appenders.html#JMSAppenderBase JMSTopicAppender http://logback.qos.ch/manual/appenders.html#JMSTopicAppender JMSQueueAppender http://logback.qos.ch/manual/appenders.html#JMSQueueAppender SMTPAppender http://logback.qos.ch/manual/appenders.html#SMTPAppender DBAppender http://logback.qos.ch/manual/appenders.html#DBAppender SyslogAppender http://logback.qos.ch/manual/appenders.html#SyslogAppender It has support for JMX: http://logback.qos.ch/manual/jmxConfig.html And slf4j supports Log4j for those needing that: http://www.slf4j.org/api/org/slf4j/impl/Log4jLoggerAdapter.html - What is also interesting, is Logback Context Selectors http://logback.qos.ch/manual/loggingSeparation.html This may seem like it can give us the ability to have one instance of Logback serving many different separated logging environments. We have discussed how Geronimo/Jetty might eventually support web application filtering in a single WebContainer. In this way a WebContainer can listen on two ports, and serve web applications on one port but not the other. With the current implementation of NCSARequestLog, both web applications (and thus also request traffic on both ports) can only log to one single log file as configured in the NCSARequestLog tied into the WebContainer. However! With Logback context selectors, it looks like it might be possible to free the web apps (and also request traffic by port) from this restriction. At first look of Logback, it looks like Geronimo could be configured with one single Jetty WebContainer, and one single RequestLog using Logback, but be able to log into separate files based on port and/or based on web application using Logback context selectors. -RG
Re: How to deploy web application to one port
Russell E Glaue wrote: > Okay, so I have to deploy a second Jetty container inside Geronimo, so > Geronimo > would have two different Jetty containers, one serving web applications on > each > of the two ports. > So I would basically copy the Jetty plugin to a new plugin, compile it, and > place it in the repository. > > So now we have JettyContainer/JettyWebContainer in Geronimo. > After doing what is suggested, I would have something like > JettyContainer2/JettyWebContainer2 - it would be a whole new module with the > same code - is this correct? The solution for this is discussed in the thread user@geronimo.apache.org "feature? ContainerGroup" 12/05/2008 09:46 AM. The solution requires deploying a new jetty container via a gbean. All that is required to be in the gbean is the plan.xml file which configures the new instance of the Jetty container. > > > I have an additional question. > In a previous thread on 2008-12-03, I ask on the subject "How to set up > logging > for a connector". Can I also perform this same suggestion for > org.apache.geronimo.jetty6.requestlog.NCSARequestLog ? > > I would assume if they use the same NCSARequestLog gbean that both containers > would put their logs in the same log file. > So... since I cannot change the log file name and location (as I asked in this > other thread), I assume I also need to deploy a new NCSARequestLog gbean - is > this correct? Also answered in the thread user@geronimo.apache.org "feature? ContainerGroup" 12/05/2008 09:46 AM, this requires deploying a new NCSARequestLog gbean. Again the gbean only contains a plan.xml to configure the new instance of NCSARequestLog. I have entered a feature request into the Jetty project's issue system. http://jira.codehaus.org/browse/JETTY-835 This feature request is to implement a new RequestLog that does more than file-based logging. The suggestion has been to use slf4j in the new implementation, which in turn will support sending logs to Socket, Syslog, and will in turn support log4j. -RG > > > -RG > > > David Jencks wrote: >> On Dec 4, 2008, at 10:59 PM, viola.lu wrote: >> >>> You can create two geronim instances in one server:instance A in http >>> port >>> 2150, instance B in port 2051, then deploy hello_1 to instance A, >>> hello_2 to >>> instance B. >> I think creating two entire server instances is a bit extreme and e.g. >> if both web apps are connecting to the same ejb app might not work as >> efficiently as possible. >> >> However, AFAIK you have to set up a second jetty server in your geronimo >> instance. Basically, copy the plugins/jetty plan (from source), call it >> something else, edit it (e.g. the ports), and deploy it. I'd copy the >> maven project and build a plugin, but you can deploy the plan separately >> if you want. You can also include all the gbeans in your geronimo plan >> for your web app. You need to indicate in the geronimo plan which web >> server you want the app to be deployed on. >> >> There are micro instructions for geronimo-tomcat here related to a >> sample app: >> >> http://cwiki.apache.org/GMOxDOC22/app-per-port-running-multiple-web-apps-on-different-ports.html >> >> >> If you come up with something relevant for jetty and want to help us >> with our docs and samples that would be great! >> >> I think I recall talking with Greg about filtering web apps per port in >> jetty but I don't think you can actually do it right now. I think he >> said it would be very easy to add though maybe we can get it into >> jetty 7. >> >> thanks >> david jencks >> >>> >>> Russell E Glaue wrote: Using geronimo-jetty 2.1.3 How do I deploy a web application to one and only one single port? Let's say I have configured two Listen Sockets: 1) 0.0.0.0:2150 2) 0.0.0.0:2151 If I simply deploy a web application to Geronimo as in: % deploy.sh deploy HelloWorld.war The sample application HellowWorld is accessible on both ports as in: 1) http://0.0.0.0:2150/hello - SUCCESS!!! 2) http://0.0.0.0:2151/hello - SUCCESS!!! Now, I can modify WelloWorld/WEB-INF/geronimo-web.xml with the virt1.com attribute, but this restrict the web application to be served when the web client makes a HTTP 1.1 call to Geronimo for "virt1.com" GET /hello So with using this , the HellowWorld is not available on either port when accessed as : So, how do I deploy a web application so that it is available on one port, but not another port, yet both ports running under one geronimo instance? I want to deploy two web applications, each one accessible on a different port. If I do something like: % deploy.sh deploy HelloWorld_1.war % deploy.sh deploy HelloWorld_2.war I want the results to be like: 1) http://0.0.0.0:2150/hello_1 - SUCCESS!!! 2) http://0.0.0.0:2150/hello_2 - Fail 3) ht
Re: How to set up logging for a connector
The solution for this is discussed in the thread user@geronimo.apache.org "feature? ContainerGroup" 12/05/2008 09:46 AM. The solution requires deploying a new jetty container via a gbean, and also deploying a new NCSARequestLog gbean. I have entered a feature request into the Jetty project's issue system. http://jira.codehaus.org/browse/JETTY-835 This feature request is to implement a new RequestLog that does more than file-based logging. The suggestion has been to use slf4j in the new implementation, which in turn will support sending logs to Socket, Syslog, and will in turn support log4j. -RG Russell E Glaue wrote: > Is it possible to configure a separate logging for different virtual hosts I > configure? > > Say I configure the vhost of "www.example.com" and I want to log all traffic > going to that vhost in a log file "var/log/www.example.com_yyy_mm_dd.log" > > I can deploy a web application to a virtual host I define in the > geronimo-web.xml file. > > Can I also setup logging based on virtual hosts? > > -RG > > > > Jarek Gawor wrote: >> I'm not sure how to do what you want (you might need to write some >> custom code) but you should be able to get rid of that NPE by changing >> the following: >> >> >> >> to: >> >> >> ServerInfo >> >> >> in your RequestLog gbean. >> >> Jarek >> >> On Wed, Dec 3, 2008 at 4:44 PM, Russell E Glaue wrote: >>> Using geronimo-jetty 2.1.3 >>> >>> I create a new HTTPSelectChannelConnector on port 21050 >>> Suppose I deploy 20 to 30 different web applications to this connector. >>> >>> Then I want to log all activity through that connector to a certain log >>> file, >>> and not the default jetty__mm_dd.log file, but a new >>> projectXX__mm_dd.log file. >>> >>> How do I do this? >>> >>> >>> I have attempted to start configuring Geronimo using the NCSARequestLog >>> gbean, >>> but I am getting an initialization error (pasted below) on Geronimo start >>> up, >>> erroring on doStart(). >>> >>> I cannot find any written documentation on how to change the log file >>> output for >>> a connector. I have read how to change the log file for an individual web >>> application, but I do not want to do that. I want to change the log file on >>> the >>> connector level. >>> >>> >>> >>>... >>>>> name="org.apache.geronimo.configs/jetty6/2.1.3/car?ServiceModule=org.apache.geronimo.configs/jetty6/2.1.3/car,j2eeType=GBean,name=RequestLog" >>> gbeanInfo="org.apache.geronimo.jetty6.requestlog.NCSARequestLog"> >>>>> name="filename">var/log/projectXX__mm_dd.log >>>dd/MMM/:HH:mm:ss >>> ZZZ >>>GMT >>>30 >>>true >>>true >>> >>> >>>org.apache.geronimo.configs >>>jetty6 >>>2.1.3 >>>car >>>JettyWebContainer >>> >>> >>> >>> >>>>> name="org.apache.geronimo.configs/jetty6/2.1.3/car?ServiceModule=org.apache.geronimo.configs/jetty6/2.1.3/car,j2eeType=GBean,name=project-XX" >>> gbeanInfo="org.apache.geronimo.jetty6.connector.HTTPSelectChannelConnector"> >>>21050 >>>8096 >>>0.0.0.0 >>>-1 >>>0 >>>50 >>>0 >>>8192 >>> >>> >>>org.apache.geronimo.configs >>>jetty6 >>>2.1.3 >>>car >>>JettyWebContainer >>> >>> >>> >>>... >>> >>> >>> >>> Error message on Geronimo startup with above configuration: >>> -- >>> Module 24/67 org.apache.geronimo.configs/j2ee-corba-yoko/2.1.3/car >>> started in 1.558s >>> Module 25/67 org.apache.geronimo.configs/jetty6/2.1.3/car >>> 15:27:20,161 ERROR [GBeanInstanceState] Error while starting; GBean is now >>> in >>> the FAILED state: >>> abstractName="org.apache.geronimo.configs/jetty6/2.1.3/car?ServiceModule=org.apache.geronimo.configs/jetty6/2.1.3/car,j2eeType=GBean,name=RequestLog" >>> java.lang.NullPointerException >>>at >>> org.apache.geronimo.jetty6.requestlog.NCSARequestLog.doStart(NCSARequestLog.java:113) >>>at >>> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998) >>>at >>> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) >>>at >>> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) >>>at >>> org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541) >>>at >>> org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) >>>at >>> org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) >>>at >>> org.apache.geronimo.gbean.runtime.GBea
Re: Custom Server Config - errors
Hi Ray, Have you tried to run your app in Little-G? Usually you might want to include everything that is in Little-G. -Jack 2008/12/17 Ray_Clough > > I have created a custom Server config using the Geronimo Console. Some > pages > cause an "IllegalStateException - no org.apache.InstanceManager set in > ServletContext". When I run in the full server, I do not get this error, > so > it must be something missing from my configuration. The app uses jsf (with > Facelets) as well as older JSPX pages. I think that it is the JSPX pages > which cause the problem. Any ideas what I did not include which I should > have? > > Thank you very much, > - Ray Clough > -- > View this message in context: > http://www.nabble.com/Custom-Server-Config---errors-tp21046988s134p21046988.html > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. > >
