You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by Matt Hogstrom <ma...@hogstrom.org> on 2006/06/12 05:48:47 UTC
1.1-rc1 Now Available
Over the past few days the outstanding issues that were raised about the first candidate have been
addressed.
They were that we were missing the LICENSE.txt as well as Notices from the distribution. I added
them. Guillaume also pointed out that he noted that there should be a Third Party Notices. This
was not included in the original 1.0 or previous distributions so I did not follow it up. Thoughts?
Also, the 1.0 release notes were removed and updated the thread started by Hernan. The Wiki has
been updated and the wiki was the source used to create the RELEASE-NOTES-1.1.txt file you will find
in the build.
To avoid issues with the version number and the plugins I used rc1 which Aaron had added in the
plugins for supported versions so I trust that works here.
JSisson addressed the problem with not being able to run Geronimo under CygWin and Kevan worked with
Aaron to address a new deployment problem that left partially deployed artifacts in the repository.
I have taken this build and run some performance tests on it and we are significantly better in 1.1
than we were in 1.0. We have a lot of improvement left for CMP EJBs. It appears that the
performance improvements in the EJB tier has changed a race condition when running under DB2. I'm
afraid that the only way to address the problem is to add a new feature to TranQL and OEJB that
allow for the specification of Isolation Levels for individual beans. This is a relatively simple
change but the build as it stands is specification compliant. I would prefer to let this release go
forward since CMP 2.1 EJBs are not nearly as common as the other J2EE components. I would like to
address this in 1.1.1 however I don't think we've locked down whether that would be allowed or not.
The change would affect TranQL and OpenEJB so they are really included components so I'd be
interested in people's feedback.
So please accept a named RC1. Your voting and feedback are for:
Geronimo 1.1
DayTrader 1.1
Specs 1.1
The vote will stand for 72 hours. Issues raised will be discussed and if we conclude that there is
a bug that must be addressed then we will mitigate the problem and respin a new rc for a 72 hour vote.
If this is accepted all three of the above components will be released simultaneously.
Here are the builds for your review and comment:
http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
Looking forward to your comments and feedback.
Re: 1.1-rc1 Now Available
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 6/12/06, Dave Colasurdo <da...@earthlink.net> wrote:
> It seems the out of box use of plugins in the admin console is
> erroneously creating url links to install the "welcome app" and "admin
> console" plugins. They are already installed and started in the j2ee
> distribution.
Hmm. That's probably because the plugin versions are 1.1-SNAPSHOT
while the installed versions are 1.1. Since there's a version
difference, it lets you install them.
I think the best path is to release 1.1, update the plugins to have
version 1.1, and then split all the applications off from Geronimo and
version them separately from the server itself. That will also help
resolve the issue Alan and Dain were recently debating in another
thread.
Thanks,
Aaron
> Matt Hogstrom wrote:
> > Over the past few days the outstanding issues that were raised about the
> > first candidate have been addressed.
> >
> > They were that we were missing the LICENSE.txt as well as Notices from
> > the distribution. I added them. Guillaume also pointed out that he
> > noted that there should be a Third Party Notices. This was not included
> > in the original 1.0 or previous distributions so I did not follow it
> > up. Thoughts?
> >
> > Also, the 1.0 release notes were removed and updated the thread started
> > by Hernan. The Wiki has been updated and the wiki was the source used
> > to create the RELEASE-NOTES-1.1.txt file you will find in the build.
> >
> > To avoid issues with the version number and the plugins I used rc1 which
> > Aaron had added in the plugins for supported versions so I trust that
> > works here.
> >
> > JSisson addressed the problem with not being able to run Geronimo under
> > CygWin and Kevan worked with Aaron to address a new deployment problem
> > that left partially deployed artifacts in the repository.
> >
> > I have taken this build and run some performance tests on it and we are
> > significantly better in 1.1 than we were in 1.0. We have a lot of
> > improvement left for CMP EJBs. It appears that the performance
> > improvements in the EJB tier has changed a race condition when running
> > under DB2. I'm afraid that the only way to address the problem is to
> > add a new feature to TranQL and OEJB that allow for the specification of
> > Isolation Levels for individual beans. This is a relatively simple
> > change but the build as it stands is specification compliant. I would
> > prefer to let this release go forward since CMP 2.1 EJBs are not nearly
> > as common as the other J2EE components. I would like to address this in
> > 1.1.1 however I don't think we've locked down whether that would be
> > allowed or not. The change would affect TranQL and OpenEJB so they are
> > really included components so I'd be interested in people's feedback.
> >
> > So please accept a named RC1. Your voting and feedback are for:
> >
> > Geronimo 1.1
> > DayTrader 1.1
> > Specs 1.1
> >
> > The vote will stand for 72 hours. Issues raised will be discussed and
> > if we conclude that there is a bug that must be addressed then we will
> > mitigate the problem and respin a new rc for a 72 hour vote.
> >
> > If this is accepted all three of the above components will be released
> > simultaneously.
> >
> > Here are the builds for your review and comment:
> >
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> > http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> > http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
> >
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> > http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
> >
> > http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
> >
> > http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
> >
> >
> > Looking forward to your comments and feedback.
> >
> >
> >
>
Re: 1.1-rc1 Now Available
Posted by Dave Colasurdo <da...@earthlink.net>.
It seems the out of box use of plugins in the admin console is
erroneously creating url links to install the "welcome app" and "admin
console" plugins. They are already installed and started in the j2ee
distribution.
Thanks
-Dave-
Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised about the
> first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices from
> the distribution. I added them. Guillaume also pointed out that he
> noted that there should be a Third Party Notices. This was not included
> in the original 1.0 or previous distributions so I did not follow it
> up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread started
> by Hernan. The Wiki has been updated and the wiki was the source used
> to create the RELEASE-NOTES-1.1.txt file you will find in the build.
>
> To avoid issues with the version number and the plugins I used rc1 which
> Aaron had added in the plugins for supported versions so I trust that
> works here.
>
> JSisson addressed the problem with not being able to run Geronimo under
> CygWin and Kevan worked with Aaron to address a new deployment problem
> that left partially deployed artifacts in the repository.
>
> I have taken this build and run some performance tests on it and we are
> significantly better in 1.1 than we were in 1.0. We have a lot of
> improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when running
> under DB2. I'm afraid that the only way to address the problem is to
> add a new feature to TranQL and OEJB that allow for the specification of
> Isolation Levels for individual beans. This is a relatively simple
> change but the build as it stands is specification compliant. I would
> prefer to let this release go forward since CMP 2.1 EJBs are not nearly
> as common as the other J2EE components. I would like to address this in
> 1.1.1 however I don't think we've locked down whether that would be
> allowed or not. The change would affect TranQL and OpenEJB so they are
> really included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed and
> if we conclude that there is a bug that must be addressed then we will
> mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be released
> simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
>
>
Re: 1.1-rc1 Now Available
Posted by "D. Strauss" <ge...@ds-2.de>.
Hello, David,
the JVM Geronimo 1.0 runs on is Sun JDK 1.6 (Mustang), actually it's
b77. As stated already: Geronimo 1.0 runs perfectly, only 1.1 drops the
[L clause.
I downloaded the latest mustang release (b87) and tried it with the same
results.
I checked various sites about the [L signature and you're right.
However, it seems that in JDK 6 this feature will go bye bye :-/ (maybe
that's why I don't know about it :-P)
I changed my startup script so that it points to an old Sun JVM 1.5
installation and set the JRE_HOME var (thx for mentioning that JAVA_HOME
will never be used ;-)).
And started ...
WORKING :-)
So, basically I can say that Geronimo 1.1 RC1 Jetty Minimal runs under
Linux and Sun JVM 1.5 with the JRE_HOME var set. However, it DOES NOT
run with the latest (ok, upcoming) JVM Sun JDK 1.6 Mustang.
I will now backport all my apps to Tiger so that I can start working
with RC1.
As always, keep up the good work. As you mentioned: maybe there is a
workaround for the [L line. Let's hope for the future.
Best regards
Dirk
David Jencks schrieb:
>
> On Jun 12, 2006, at 11:12 PM, D. Strauss wrote:
>
>> Hello, Matt
>>
>> how did you and the others got RC1 working??????
>>
>> I tried the windows version, I tried the linux version now: all crash
>> with the same exception:
>>
>> <big snip>
>>
>> Checking the source code of
>> org.apache.geronimo.security.keystore.FileKeystoreManager of rc1 reveals
>> an interesting (and very funny) line:
>>
>> loader.loadClass("[Ljavax.net.ssl.KeyManager;");
>
> This is how you load the class of javax.net.ssl.KeyManager[] (note the
> array).
>
> I have no idea either why this code construction is required or why you
> are having trouble with it. What jvm are you using?
>
>>
>> Is this the new way on loading classes? I mean the [L construct is
>> unknown. I also checked the Sun API docs and they were very clear:
>>
>> loader.loadClass("javax.net.ssl.KeyManager");
>>
>> is the right way. Or did I miss something about the new specs?
>
> That will load the class of javax.net.ssl.KeyManager, but not the array
> class.
>
> tthanks
> david jencks
>
>>
>> Anyway, it's good to hear that everyone got RC1 working. Seems I have to
>> stay with 1.0 for a long time ;-)
>>
>> Best regards
>>
>> Dirk
>>
>> Matt Hogstrom schrieb:
>>> Over the past few days the outstanding issues that were raised about the
>>> first candidate have been addressed.
>>>
>>> They were that we were missing the LICENSE.txt as well as Notices from
>>> the distribution. I added them. Guillaume also pointed out that he
>>> noted that there should be a Third Party Notices. This was not included
>>> in the original 1.0 or previous distributions so I did not follow it
>>> up. Thoughts?
>>>
>>> Also, the 1.0 release notes were removed and updated the thread started
>>> by Hernan. The Wiki has been updated and the wiki was the source used
>>> to create the RELEASE-NOTES-1.1.txt file you will find in the build.
>>>
>>> To avoid issues with the version number and the plugins I used rc1 which
>>> Aaron had added in the plugins for supported versions so I trust that
>>> works here.
>>>
>>> JSisson addressed the problem with not being able to run Geronimo under
>>> CygWin and Kevan worked with Aaron to address a new deployment problem
>>> that left partially deployed artifacts in the repository.
>>>
>>> I have taken this build and run some performance tests on it and we are
>>> significantly better in 1.1 than we were in 1.0. We have a lot of
>>> improvement left for CMP EJBs. It appears that the performance
>>> improvements in the EJB tier has changed a race condition when running
>>> under DB2. I'm afraid that the only way to address the problem is to
>>> add a new feature to TranQL and OEJB that allow for the specification of
>>> Isolation Levels for individual beans. This is a relatively simple
>>> change but the build as it stands is specification compliant. I would
>>> prefer to let this release go forward since CMP 2.1 EJBs are not nearly
>>> as common as the other J2EE components. I would like to address this in
>>> 1.1.1 however I don't think we've locked down whether that would be
>>> allowed or not. The change would affect TranQL and OpenEJB so they are
>>> really included components so I'd be interested in people's feedback.
>>>
>>> So please accept a named RC1. Your voting and feedback are for:
>>>
>>> Geronimo 1.1
>>> DayTrader 1.1
>>> Specs 1.1
>>>
>>> The vote will stand for 72 hours. Issues raised will be discussed and
>>> if we conclude that there is a bug that must be addressed then we will
>>> mitigate the problem and respin a new rc for a 72 hour vote.
>>>
>>> If this is accepted all three of the above components will be released
>>> simultaneously.
>>>
>>> Here are the builds for your review and comment:
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>>
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>>
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>>
>>>
>>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>>
>>>
>>> Looking forward to your comments and feedback.
>>>
>>>
>>>
>
>
>
Re: 1.1-rc1 Now Available
Posted by David Jencks <da...@yahoo.com>.
On Jun 12, 2006, at 11:12 PM, D. Strauss wrote:
> Hello, Matt
>
> how did you and the others got RC1 working??????
>
> I tried the windows version, I tried the linux version now: all crash
> with the same exception:
>
> <big snip>
>
> Checking the source code of
> org.apache.geronimo.security.keystore.FileKeystoreManager of rc1
> reveals
> an interesting (and very funny) line:
>
> loader.loadClass("[Ljavax.net.ssl.KeyManager;");
This is how you load the class of javax.net.ssl.KeyManager[] (note
the array).
I have no idea either why this code construction is required or why
you are having trouble with it. What jvm are you using?
>
> Is this the new way on loading classes? I mean the [L construct is
> unknown. I also checked the Sun API docs and they were very clear:
>
> loader.loadClass("javax.net.ssl.KeyManager");
>
> is the right way. Or did I miss something about the new specs?
That will load the class of javax.net.ssl.KeyManager, but not the
array class.
tthanks
david jencks
>
> Anyway, it's good to hear that everyone got RC1 working. Seems I
> have to
> stay with 1.0 for a long time ;-)
>
> Best regards
>
> Dirk
>
> Matt Hogstrom schrieb:
>> Over the past few days the outstanding issues that were raised
>> about the
>> first candidate have been addressed.
>>
>> They were that we were missing the LICENSE.txt as well as Notices
>> from
>> the distribution. I added them. Guillaume also pointed out that he
>> noted that there should be a Third Party Notices. This was not
>> included
>> in the original 1.0 or previous distributions so I did not follow it
>> up. Thoughts?
>>
>> Also, the 1.0 release notes were removed and updated the thread
>> started
>> by Hernan. The Wiki has been updated and the wiki was the source
>> used
>> to create the RELEASE-NOTES-1.1.txt file you will find in the build.
>>
>> To avoid issues with the version number and the plugins I used rc1
>> which
>> Aaron had added in the plugins for supported versions so I trust that
>> works here.
>>
>> JSisson addressed the problem with not being able to run Geronimo
>> under
>> CygWin and Kevan worked with Aaron to address a new deployment
>> problem
>> that left partially deployed artifacts in the repository.
>>
>> I have taken this build and run some performance tests on it and
>> we are
>> significantly better in 1.1 than we were in 1.0. We have a lot of
>> improvement left for CMP EJBs. It appears that the performance
>> improvements in the EJB tier has changed a race condition when
>> running
>> under DB2. I'm afraid that the only way to address the problem is to
>> add a new feature to TranQL and OEJB that allow for the
>> specification of
>> Isolation Levels for individual beans. This is a relatively simple
>> change but the build as it stands is specification compliant. I
>> would
>> prefer to let this release go forward since CMP 2.1 EJBs are not
>> nearly
>> as common as the other J2EE components. I would like to address
>> this in
>> 1.1.1 however I don't think we've locked down whether that would be
>> allowed or not. The change would affect TranQL and OpenEJB so
>> they are
>> really included components so I'd be interested in people's feedback.
>>
>> So please accept a named RC1. Your voting and feedback are for:
>>
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>>
>> The vote will stand for 72 hours. Issues raised will be discussed
>> and
>> if we conclude that there is a bug that must be addressed then we
>> will
>> mitigate the problem and respin a new rc for a 72 hour vote.
>>
>> If this is accepted all three of the above components will be
>> released
>> simultaneously.
>>
>> Here are the builds for your review and comment:
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>> rc1.tar.gz
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>> rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
>> rc1.tar.gz
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
>> rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>> rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>> rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
>> rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
>> rc1.zip
>>
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>
>>
>> Looking forward to your comments and feedback.
>>
>>
>>
Re: 1.1-rc1 Now Available
Posted by "D. Strauss" <ge...@ds-2.de>.
Hello, Matt
how did you and the others got RC1 working??????
I tried the windows version, I tried the linux version now: all crash
with the same exception:
07:56:58,268 ERROR [FileKeystoreManager] Unable to dynamically load
java.lang.ClassNotFoundException: [Ljavax.net.ssl.KeyManager; in
classloader geronimo/jetty/1.1-rc1/car
at
org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:249)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.geronimo.security.keystore.FileKeystoreManager.createSSLServerFactory(FileKeystoreManager.java:314)
at
org.apache.geronimo.security.keystore.FileKeystoreManager$$FastClassByCGLIB$$4d9d2a71.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.management.geronimo.KeystoreManager$$EnhancerByCGLIB$$dbbf8431.createSSLServerFactory(<generated>)
at
org.apache.geronimo.jetty.connector.GeronimoSSLListener.createFactory(GeronimoSSLListener.java:41)
at org.mortbay.http.SslListener.newServerSocket(SslListener.java:283)
at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477)
at
org.apache.geronimo.jetty.connector.JettyConnector.doStart(JettyConnector.java:233)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
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.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
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.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$ea82e0d3.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
07:56:58,282 WARN [SslListener] EXCEPTION
java.lang.NullPointerException
at org.mortbay.http.SslListener.newServerSocket(SslListener.java:291)
at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477)
at
org.apache.geronimo.jetty.connector.JettyConnector.doStart(JettyConnector.java:233)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
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.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
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.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$ea82e0d3.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
07:56:58,391 ERROR [GBeanInstanceState] Error while starting; GBean is
now in the FAILED state:
abstractName="geronimo/jetty/1.1-rc1/car?ServiceModule=geronimo/jetty/1.1-rc1/car,j2eeType=GBean,name=JettySSLConnector"
java.io.IOException: Could not create JsseListener:
java.lang.NullPointerException
at org.mortbay.http.SslListener.newServerSocket(SslListener.java:314)
at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:477)
at
org.apache.geronimo.jetty.connector.JettyConnector.doStart(JettyConnector.java:233)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:981)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
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.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:526)
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.GBeanDependency$1.running(GBeanDependency.java:120)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:173)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:41)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:251)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:292)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:540)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:512)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:493)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastClassByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:817)
at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$ea82e0d3.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
Checking the source code of
org.apache.geronimo.security.keystore.FileKeystoreManager of rc1 reveals
an interesting (and very funny) line:
loader.loadClass("[Ljavax.net.ssl.KeyManager;");
Is this the new way on loading classes? I mean the [L construct is
unknown. I also checked the Sun API docs and they were very clear:
loader.loadClass("javax.net.ssl.KeyManager");
is the right way. Or did I miss something about the new specs?
Anyway, it's good to hear that everyone got RC1 working. Seems I have to
stay with 1.0 for a long time ;-)
Best regards
Dirk
Matt Hogstrom schrieb:
> Over the past few days the outstanding issues that were raised about the
> first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices from
> the distribution. I added them. Guillaume also pointed out that he
> noted that there should be a Third Party Notices. This was not included
> in the original 1.0 or previous distributions so I did not follow it
> up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread started
> by Hernan. The Wiki has been updated and the wiki was the source used
> to create the RELEASE-NOTES-1.1.txt file you will find in the build.
>
> To avoid issues with the version number and the plugins I used rc1 which
> Aaron had added in the plugins for supported versions so I trust that
> works here.
>
> JSisson addressed the problem with not being able to run Geronimo under
> CygWin and Kevan worked with Aaron to address a new deployment problem
> that left partially deployed artifacts in the repository.
>
> I have taken this build and run some performance tests on it and we are
> significantly better in 1.1 than we were in 1.0. We have a lot of
> improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when running
> under DB2. I'm afraid that the only way to address the problem is to
> add a new feature to TranQL and OEJB that allow for the specification of
> Isolation Levels for individual beans. This is a relatively simple
> change but the build as it stands is specification compliant. I would
> prefer to let this release go forward since CMP 2.1 EJBs are not nearly
> as common as the other J2EE components. I would like to address this in
> 1.1.1 however I don't think we've locked down whether that would be
> allowed or not. The change would affect TranQL and OpenEJB so they are
> really included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed and
> if we conclude that there is a bug that must be addressed then we will
> mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be released
> simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
>
>
Re: 1.1-rc1 Now Available
Posted by Dain Sundstrom <da...@iq80.com>.
I have downloaded and tried out all 4 .tgz files. Here is what I
tested:
o I placed them into the directory /Users/dain/geronimo test/ (note
contains a space)
o Started the servers using server.jar and startup.sh
o Stopped the server using ctrl^c and shutdown.sh
o Installed some of samples (not all) via the install links
o Installed the ldap example via the console plugin
o Stopped/uninstalled service and web modules via the console
o Tailed the geronimo.log file (stuff shows up)
Everything, looks good except the binaries don't contain the
LICENSE.txt file. We should be able to easily fix this in the maven
code, or by hand after the build. For other minor things I found, I
either created a JIRA or started a new thread.
+1 to release the server once the license file is added
-dain
On Jun 11, 2006, at 8:48 PM, Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised
> about the first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices
> from the distribution. I added them. Guillaume also pointed out
> that he noted that there should be a Third Party Notices. This was
> not included in the original 1.0 or previous distributions so I did
> not follow it up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread
> started by Hernan. The Wiki has been updated and the wiki was the
> source used to create the RELEASE-NOTES-1.1.txt file you will find
> in the build.
>
> To avoid issues with the version number and the plugins I used rc1
> which Aaron had added in the plugins for supported versions so I
> trust that works here.
>
> JSisson addressed the problem with not being able to run Geronimo
> under CygWin and Kevan worked with Aaron to address a new
> deployment problem that left partially deployed artifacts in the
> repository.
>
> I have taken this build and run some performance tests on it and we
> are significantly better in 1.1 than we were in 1.0. We have a lot
> of improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when
> running under DB2. I'm afraid that the only way to address the
> problem is to add a new feature to TranQL and OEJB that allow for
> the specification of Isolation Levels for individual beans. This
> is a relatively simple change but the build as it stands is
> specification compliant. I would prefer to let this release go
> forward since CMP 2.1 EJBs are not nearly as common as the other
> J2EE components. I would like to address this in 1.1.1 however I
> don't think we've locked down whether that would be allowed or
> not. The change would affect TranQL and OpenEJB so they are really
> included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed
> and if we conclude that there is a bug that must be addressed then
> we will mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be
> released simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
> rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
> rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
> rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
Re: 1.1-rc1 Now Available
Posted by Guillaume Nodet <gu...@worldonline.fr>.
Would it be possible to publish the specs in an m2 repo ?
It seems they are currently in
http://people.apache.org/repository/org.apache.geronimo.specs/jars/
but this is a m1 repo and the poms are not available.
AFAIK, their final place should be
http://www.apache.org/dist/maven-repository/org/apache/geronimo/specs
(which is a m2 repo synced with public repos).
Most of the specs have been released in 1.0.1 to fix m2 dependencies, so
if we do not have m2 poms ...
It would also benefit the m2 build in trunk which have to use them.
Cheers,
Guillaume Nodet
Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised about
> the first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices from
> the distribution. I added them. Guillaume also pointed out that he
> noted that there should be a Third Party Notices. This was not
> included in the original 1.0 or previous distributions so I did not
> follow it up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread
> started by Hernan. The Wiki has been updated and the wiki was the
> source used to create the RELEASE-NOTES-1.1.txt file you will find in
> the build.
>
> To avoid issues with the version number and the plugins I used rc1
> which Aaron had added in the plugins for supported versions so I trust
> that works here.
>
> JSisson addressed the problem with not being able to run Geronimo
> under CygWin and Kevan worked with Aaron to address a new deployment
> problem that left partially deployed artifacts in the repository.
>
> I have taken this build and run some performance tests on it and we
> are significantly better in 1.1 than we were in 1.0. We have a lot of
> improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when running
> under DB2. I'm afraid that the only way to address the problem is to
> add a new feature to TranQL and OEJB that allow for the specification
> of Isolation Levels for individual beans. This is a relatively simple
> change but the build as it stands is specification compliant. I would
> prefer to let this release go forward since CMP 2.1 EJBs are not
> nearly as common as the other J2EE components. I would like to
> address this in 1.1.1 however I don't think we've locked down whether
> that would be allowed or not. The change would affect TranQL and
> OpenEJB so they are really included components so I'd be interested in
> people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed and
> if we conclude that there is a bug that must be addressed then we will
> mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be released
> simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
>
>
Re: 1.1-rc1 deployment
Posted by pw...@pswdic.com.
Yes, there was an error in the hosts file. But geronimo 1.0 worked with
the error -- but everything seems fine now with 1.1rc1
Thanks,
Paul
> For this error, I would check your hosts file (/etc/hosts or
> c:\windows\system32\drivers\etc\hosts). It looks like your machine
> thinks that it is 68.69.195.191 but really it is not.
>
> Thanks,
> Aaron
>
> On 6/14/06, Paul Watkins <pw...@pswdic.com> wrote:
>> I have no problems starting Geronimo 1.0 under JDK1.5.0_06
>>
>> However, Geronimo-1.1rc1 fails to start -- all the java environmental
>> variables are set: JAVA_HOME, JDK_HOME, JRE_HOME
>>
>> Any ideas from the log code below? The error messages regarding the
>> registry bind are also present with 1.0 but it still starts -- 1.1rc1
>> does not.
>>
>> Thanks,
>>
>> Paul
>>
>> org.apache.geronimo.kernel.config.LifecycleException: start of
>> geronimo/j2ee-sec
>> urity/1.1-rc1/car failed
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
>> figuration(SimpleConfigurationManager.java:529)
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
>> figuration(SimpleConfigurationManager.java:493)
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
>> ssByCGLIB$$ce77a924.invoke(<generated>)
>> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>> at
>> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
>> Invoker.java:38)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
>> n.java:122)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
>> java:817)
>> at
>> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
>> 7)
>> at
>> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
>> ionInvoker.java:35)
>> at
>> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
>> xyMethodInterceptor.java:96)
>> at
>> org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
>> cerByCGLIB$$a4b65cec.startConfiguration(<generated>)
>> at
>> org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
>> at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
>> at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
>> Caused by: org.apache.geronimo.kernel.config.InvalidConfigException:
>> Unknown sta
>> rt exception
>> at
>> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
>> nGBeans(ConfigurationUtil.java:440)
>> at
>> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
>> rnelConfigurationManager.java:187)
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
>> figuration(SimpleConfigurationManager.java:512)
>> ... 13 more
>> Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
>> Configuratio
>> n geronimo/j2ee-security/1.1-rc1/car failed to start due to the
>> following reason
>> s:
>> The service
>> ServiceModule=geronimo/j2ee-security/1.1-rc1/car,j2eeType=GBean,na
>> me=JMXService did not start because the doStart method threw an
>> exception.
>> java.io.IOException: Cannot bind to URL
>> [rmi://0.0.0.0:1099/JMXConnector]: javax
>> .naming.NoPermissionException [Root exception is
>> java.rmi.ServerException: Remot
>> eException occurred in server thread; nested exception is:
>> java.rmi.AccessException: Registry.Registry.bind disallowed;
>> origin /68.
>> 69.195.191 is non-local host]
>> at
>> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConn
>> ectorServer.java:814)
>> at
>> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
>> er.java:431)
>> at
>> org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav
>> a:190)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
>> nstance.java:981)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
>> (GBeanInstanceState.java:267)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
>> nceState.java:102)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
>> BeanInstanceState.java:124)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
>> nstance.java:540)
>> at
>> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
>> cKernel.java:379)
>> at
>> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
>> nGBeans(ConfigurationUtil.java:374)
>> at
>> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
>> rnelConfigurationManager.java:187)
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
>> figuration(SimpleConfigurationManager.java:512)
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
>> figuration(SimpleConfigurationManager.java:493)
>> at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
>> ssByCGLIB$$ce77a924.invoke(<generated>)
>> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>> at
>> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
>> Invoker.java:38)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
>> n.java:122)
>> at
>> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
>> java:817)
>> at
>> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
>> 7)
>> at
>> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
>> ionInvoker.java:35)
>> at
>> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
>> xyMethodInterceptor.java:96)
>> at
>> org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
>> cerByCGLIB$$a4b65cec.startConfiguration(<generated>)
>> at
>> org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
>> at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
>> at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
>> Caused by: javax.naming.NoPermissionException [Root exception is
>> java.rmi.Server
>> Exception: RemoteException occurred in server thread; nested exception
>> is:
>> java.rmi.AccessException: Registry.Registry.bind disallowed;
>> origin /68.
>> 69.195.191 is non-local host]
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
>> 22)
>> at
>> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.jav
>> a:208)
>> at javax.naming.InitialContext.bind(InitialContext.java:359)
>> at
>> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServe
>> r.java:635)
>> at
>> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
>> er.java:427)
>> ... 23 more
>> Caused by: java.rmi.ServerException: RemoteException occurred in server
>> thread;
>> nested exception is:
>> java.rmi.AccessException: Registry.Registry.bind disallowed;
>> origin /68.
>> 69.195.191 is non-local host
>> at
>> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385
>> )
>> at
>> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>> at sun.rmi.transport.Transport$1.run(Transport.java:153)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>> at
>> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
>> 60)
>> at
>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
>> .java:701)
>> at java.lang.Thread.run(Thread.java:595)
>> at
>> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
>> RemoteCall.java:247)
>> at
>> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
>> 223)
>> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
>> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
>> at
>> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
>> 16)
>> ... 27 more
>> Caused by: java.rmi.AccessException: Registry.Registry.bind disallowed;
>> origin /
>> 68.69.195.191 is non-local host
>> at
>> sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
>> at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
>> at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
>> at
>> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375
>> )
>> at
>> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
>> at sun.rmi.transport.Transport$1.run(Transport.java:153)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>> at
>> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
>> 60)
>> at
>> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
>> .java:701)
>> at java.lang.Thread.run(Thread.java:595)
>>
>>
>> at
>> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
>> nGBeans(ConfigurationUtil.java:403)
>> ... 15 more
>> Server shutdown begun
>>
>>
>
Re: 1.1-rc1 deployment
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
For this error, I would check your hosts file (/etc/hosts or
c:\windows\system32\drivers\etc\hosts). It looks like your machine
thinks that it is 68.69.195.191 but really it is not.
Thanks,
Aaron
On 6/14/06, Paul Watkins <pw...@pswdic.com> wrote:
> I have no problems starting Geronimo 1.0 under JDK1.5.0_06
>
> However, Geronimo-1.1rc1 fails to start -- all the java environmental
> variables are set: JAVA_HOME, JDK_HOME, JRE_HOME
>
> Any ideas from the log code below? The error messages regarding the
> registry bind are also present with 1.0 but it still starts -- 1.1rc1
> does not.
>
> Thanks,
>
> Paul
>
> org.apache.geronimo.kernel.config.LifecycleException: start of
> geronimo/j2ee-sec
> urity/1.1-rc1/car failed
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
> figuration(SimpleConfigurationManager.java:529)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
> figuration(SimpleConfigurationManager.java:493)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
> ssByCGLIB$$ce77a924.invoke(<generated>)
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> at
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
> Invoker.java:38)
> at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
> n.java:122)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
> java:817)
> at
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
> 7)
> at
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
> ionInvoker.java:35)
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
> xyMethodInterceptor.java:96)
> at
> org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
> cerByCGLIB$$a4b65cec.startConfiguration(<generated>)
> at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
> at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
> at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
> Caused by: org.apache.geronimo.kernel.config.InvalidConfigException:
> Unknown sta
> rt exception
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
> nGBeans(ConfigurationUtil.java:440)
> at
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
> rnelConfigurationManager.java:187)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
> figuration(SimpleConfigurationManager.java:512)
> ... 13 more
> Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
> Configuratio
> n geronimo/j2ee-security/1.1-rc1/car failed to start due to the
> following reason
> s:
> The service
> ServiceModule=geronimo/j2ee-security/1.1-rc1/car,j2eeType=GBean,na
> me=JMXService did not start because the doStart method threw an exception.
> java.io.IOException: Cannot bind to URL
> [rmi://0.0.0.0:1099/JMXConnector]: javax
> .naming.NoPermissionException [Root exception is
> java.rmi.ServerException: Remot
> eException occurred in server thread; nested exception is:
> java.rmi.AccessException: Registry.Registry.bind disallowed;
> origin /68.
> 69.195.191 is non-local host]
> at
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConn
> ectorServer.java:814)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
> er.java:431)
> at
> org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav
> a:190)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
> nstance.java:981)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
> (GBeanInstanceState.java:267)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
> nceState.java:102)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
> BeanInstanceState.java:124)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
> nstance.java:540)
> at
> org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
> cKernel.java:379)
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
> nGBeans(ConfigurationUtil.java:374)
> at
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
> rnelConfigurationManager.java:187)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
> figuration(SimpleConfigurationManager.java:512)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
> figuration(SimpleConfigurationManager.java:493)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
> ssByCGLIB$$ce77a924.invoke(<generated>)
> at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> at
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
> Invoker.java:38)
> at
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
> n.java:122)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
> java:817)
> at
> org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
> 7)
> at
> org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
> ionInvoker.java:35)
> at
> org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
> xyMethodInterceptor.java:96)
> at
> org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
> cerByCGLIB$$a4b65cec.startConfiguration(<generated>)
> at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
> at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
> at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
> Caused by: javax.naming.NoPermissionException [Root exception is
> java.rmi.Server
> Exception: RemoteException occurred in server thread; nested exception is:
> java.rmi.AccessException: Registry.Registry.bind disallowed;
> origin /68.
> 69.195.191 is non-local host]
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
> 22)
> at
> com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.jav
> a:208)
> at javax.naming.InitialContext.bind(InitialContext.java:359)
> at
> javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServe
> r.java:635)
> at
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
> er.java:427)
> ... 23 more
> Caused by: java.rmi.ServerException: RemoteException occurred in server
> thread;
> nested exception is:
> java.rmi.AccessException: Registry.Registry.bind disallowed;
> origin /68.
> 69.195.191 is non-local host
> at
> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385
> )
> at
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
> at sun.rmi.transport.Transport$1.run(Transport.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
> 60)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
> .java:701)
> at java.lang.Thread.run(Thread.java:595)
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
> RemoteCall.java:247)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
> 223)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
> at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
> at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
> 16)
> ... 27 more
> Caused by: java.rmi.AccessException: Registry.Registry.bind disallowed;
> origin /
> 68.69.195.191 is non-local host
> at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
> at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
> at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
> at
> sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375
> )
> at
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
> at sun.rmi.transport.Transport$1.run(Transport.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
> 60)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
> .java:701)
> at java.lang.Thread.run(Thread.java:595)
>
>
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
> nGBeans(ConfigurationUtil.java:403)
> ... 15 more
> Server shutdown begun
>
>
1.1-rc1 deployment
Posted by Paul Watkins <pw...@pswdic.com>.
I have no problems starting Geronimo 1.0 under JDK1.5.0_06
However, Geronimo-1.1rc1 fails to start -- all the java environmental
variables are set: JAVA_HOME, JDK_HOME, JRE_HOME
Any ideas from the log code below? The error messages regarding the
registry bind are also present with 1.0 but it still starts -- 1.1rc1
does not.
Thanks,
Paul
org.apache.geronimo.kernel.config.LifecycleException: start of
geronimo/j2ee-sec
urity/1.1-rc1/car failed
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:529)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:493)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
ssByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:817)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
7)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
cerByCGLIB$$a4b65cec.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
Caused by: org.apache.geronimo.kernel.config.InvalidConfigException:
Unknown sta
rt exception
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:440)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
rnelConfigurationManager.java:187)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:512)
... 13 more
Caused by: org.apache.geronimo.gbean.InvalidConfigurationException:
Configuratio
n geronimo/j2ee-security/1.1-rc1/car failed to start due to the
following reason
s:
The service
ServiceModule=geronimo/j2ee-security/1.1-rc1/car,j2eeType=GBean,na
me=JMXService did not start because the doStart method threw an exception.
java.io.IOException: Cannot bind to URL
[rmi://0.0.0.0:1099/JMXConnector]: javax
.naming.NoPermissionException [Root exception is
java.rmi.ServerException: Remot
eException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed;
origin /68.
69.195.191 is non-local host]
at
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConn
ectorServer.java:814)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
er.java:431)
at
org.apache.geronimo.jmxremoting.JMXConnector.doStart(JMXConnector.jav
a:190)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanI
nstance.java:981)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart
(GBeanInstanceState.java:267)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInsta
nceState.java:102)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(G
BeanInstanceState.java:124)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanI
nstance.java:540)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(Basi
cKernel.java:379)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:374)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(Ke
rnelConfigurationManager.java:187)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:512)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startCon
figuration(SimpleConfigurationManager.java:493)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager$$FastCla
ssByCGLIB$$ce77a924.invoke(<generated>)
at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
at
org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethod
Invoker.java:38)
at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:122)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:817)
at
org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:5
7)
at
org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperat
ionInvoker.java:35)
at
org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(Pro
xyMethodInterceptor.java:96)
at
org.apache.geronimo.kernel.config.EditableConfigurationManager$$Enhan
cerByCGLIB$$a4b65cec.startConfiguration(<generated>)
at org.apache.geronimo.system.main.Daemon.doStartup(Daemon.java:297)
at org.apache.geronimo.system.main.Daemon.<init>(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:377)
Caused by: javax.naming.NoPermissionException [Root exception is
java.rmi.Server
Exception: RemoteException occurred in server thread; nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed;
origin /68.
69.195.191 is non-local host]
at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
22)
at
com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.jav
a:208)
at javax.naming.InitialContext.bind(InitialContext.java:359)
at
javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServe
r.java:635)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServ
er.java:427)
... 23 more
Caused by: java.rmi.ServerException: RemoteException occurred in server
thread;
nested exception is:
java.rmi.AccessException: Registry.Registry.bind disallowed;
origin /68.
69.195.191 is non-local host
at
sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385
)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:595)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
RemoteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:1
16)
... 27 more
Caused by: java.rmi.AccessException: Registry.Registry.bind disallowed;
origin /
68.69.195.191 is non-local host
at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at
sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375
)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:595)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguratio
nGBeans(ConfigurationUtil.java:403)
... 15 more
Server shutdown begun
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
ok, will do that
Thanks,
Mario
Aaron Mulder wrote:
> I would not have expected that -- I would have thought that putting
> the dependency in the WAR would work. Can you create a Jira with the
> XML files you tried for the WAR dependency (application.xml,
> geronimo-application.xml, web.xml, and geronimo-web.xml) and include
> the error and mention that it works if you move the dependency to the
> EAR level?
>
> Thanks,
> Aaron
>
> On 6/14/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>> When I put the db connector dependency setting into the
>> geronimo-application.xml instead of the geronimo-web.xml
>> then the web app will be deployed without the error.
>>
>> Is the geronimo-application.xml the correct place for
>> the db connector dependency when the web app is deployed
>> as an EAR? Is it also mandatory to put all the other dependency
>> settings in the geronimo-application.xml when deploying as EAR?
>>
>> Thanks,
>> Mario
>>
>>
>>
>> Mario Rübsam wrote:
>> > Ok, something I not mentioned before is, that I deploy the web
>> application
>> > packaged in an EAR.
>> >
>> > here the geronimo-application.xml:
>> >
>> > <?xml version="1.0" encoding="UTF-8"?>
>> > <application
>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.0"
>> >
>> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.0"
>> > configId="coderesearch/ei-service/2.3/car"
>> > parentId="geronimo/j2ee-server/1.0/car">
>> >
>> > <module>
>> > <web>client.war</web>
>> > <alt-dd>META-INF/geronimo-web.xml</alt-dd>
>> > </module>
>> > </application>
>> >
>> >
>> > and the application.xml:
>> >
>> > <?xml version="1.0" encoding="ISO-8859-1"?>
>> > <application xmlns="http://java.sun.com/xml/ns/j2ee"
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
>> > version="1.4">
>> >
>> > <display-name>ei-Service</display-name>
>> >
>> > <module>
>> > <web>
>> > <web-uri>client.war</web-uri>
>> > <context-root>/ei-service</context-root>
>> > </web>
>> > </module>
>> >
>> > <module>
>> > <web>
>> > <web-uri>client.war</web-uri>
>> > <context-root>/</context-root>
>> > </web>
>> > </module>
>> > </application>
>> >
>> >
>> > Are there any differences in deploying between WAR and EAR in
>> combination
>> > with the database pools?
>> >
>> > Thanks,
>> > Mario
>> >
>> >
>> >
>> >
>> > Mario Rübsam wrote:
>> >> Aaron Mulder wrote:
>> >>> I think we ought to try to figure this out for 1.1.
>> >>>
>> >>> Mario, are you sure the data source is deploying correctly? Do you
>> >>> see it listed as started in the "J2EE Connectors" screen of the
>> >>> console?
>> >>
>> >> Aaron,
>> >>
>> >> yes I'm sure, the datasource is available and the J2EE connector
>> >> is available for stop/uninstall.
>> >>
>> >> Thanks,
>> >> Mario
>> >>
>> >>
>> >>>
>> >>> Thanks,
>> >>> Aaron
>> >>>
>> >>> On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>> >>>> Any new ideas about the problem?
>> >>>>
>> >>>> Thanks,
>> >>>> Mario
>> >>>>
>> >>>>
>> >>>> Mario Rübsam wrote:
>> >>>> > David Jencks wrote:
>> >>>> >> What happens if you change both this and the moduleId in the rar
>> >>>> plan
>> >>>> >> to type car?
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>rar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >
>> >>>> > changed it to "car" but still no luck, I used the "rar" because
>> >>>> the console
>> >>>> > wizard uses "rar" too
>> >>>> >
>> >>>> >> It should work the way you have it.... but we might have some
>> >>>> >> hardcoded assumptions about car left.
>> >>>> >
>> >>>> > I get the same error message when I remove the dependency. I tried
>> >>>> > it also with or without the version and type. Always the same
>> >>>> message.
>> >>>> > The db pool is deployed without problems I also checked the
>> >>>> repository
>> >>>> > structure for the db rar/car.
>> >>>> >
>> >>>> > Thanks,
>> >>>> > Mario
>> >>>> >
>> >>>> >
>> >>>> >> should have type car
>> >>>> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>> >>>> >>
>> >>>> >>> Hi,
>> >>>> >>>
>> >>>> >>> with the current release candidate I still have problems
>> >>>> >>> linking to the deployed datasource. My dependencies should
>> >>>> >>> match the examples from the web console but still no
>> >>>> >>> luck when deploying.
>> >>>> >>>
>> >>>> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>> >>>> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
>> >>>> >>> resource reference 'jdbc/default' (Could not find resource
>> >>>> >>> 'jdbc/default'. Perhaps it has not yet been configured, or
>> >>>> your
>> >>>> >>> application does not have a dependency declared for that
>> >>>> resource
>> >>>> >>> module?)
>> >>>> >>>
>> >>>> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>> >>>> >>>
>> >>>> >>> Thanks,
>> >>>> >>> Mario
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> here the geronimo-web.xml:
>> >>>> >>>
>> >>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>> >>>> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>> >>>> >>>
>> >>>> >>> <dep:environment
>> >>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> >>>> >>> <dep:moduleId>
>> >>>> >>> <dep:groupId>coderesearch</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>war</dep:type>
>> >>>> >>> </dep:moduleId>
>> >>>> >>>
>> >>>> >>> <dep:dependencies>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>coderesearch</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>car</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>rar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-email</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-email</dep:artifactId>
>> >>>> >>> <dep:version>1.0</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-codec</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-codec</dep:artifactId>
>> >>>> >>> <dep:version>1.3</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-httpclient</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
>> >>>> >>> <dep:version>3.0</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-fileupload</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
>> >>>> >>> <dep:version>1.0</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>> </dep:dependencies>
>> >>>> >>>
>> >>>> >>> <dep:hidden-classes/>
>> >>>> >>> <dep:non-overridable-classes/>
>> >>>> >>>
>> >>>> >>> </dep:environment>
>> >>>> >>>
>> >>>> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>> >>>> >>>
>> >>>> >>> <naming:resource-ref>
>> >>>> >>> <naming:ref-name>jdbc/default</naming:ref-name>
>> >>>> >>> <naming:resource-link>jdbc/default</naming:resource-link>
>> >>>> >>> </naming:resource-ref>
>> >>>> >>>
>> >>>> >>> </web-app>
>> >>>> >>>
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> and the web.xml:
>> >>>> >>>
>> >>>> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> >>>> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>> >>>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> >>>> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> >>>> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>> >>>> >>> version="2.4">
>> >>>> >>>
>> >>>> >>> <servlet>
>> >>>> >>> <display-name>MainServlet</display-name>
>> >>>> >>> <servlet-name>MainServlet</servlet-name>
>> >>>> >>>
>> >>>> >>>
>> >>>>
>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>> >>>>
>> >>>> >>>
>> >>>> >>> <load-on-startup>1</load-on-startup>
>> >>>> >>> </servlet>
>> >>>> >>>
>> >>>> >>> <servlet-mapping>
>> >>>> >>> <servlet-name>MainServlet</servlet-name>
>> >>>> >>> <url-pattern>/*</url-pattern>
>> >>>> >>> </servlet-mapping>
>> >>>> >>>
>> >>>> >>> <env-entry>
>> >>>> >>> <env-entry-name>server/ServerType</env-entry-name>
>> >>>> >>> <env-entry-type>java.lang.String</env-entry-type>
>> >>>> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>> >>>> >>> </env-entry>
>> >>>> >>>
>> >>>> >>> <resource-ref>
>> >>>> >>> <res-ref-name>jdbc/default</res-ref-name>
>> >>>> >>> <res-type>javax.sql.DataSource</res-type>
>> >>>> >>> <res-auth>Container</res-auth>
>> >>>> >>> <res-sharing-scope>Shareable</res-sharing-scope>
>> >>>> >>> </resource-ref>
>> >>>> >>>
>> >>>> >>> </web-app>
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> and the db deploy plan:
>> >>>> >>>
>> >>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>> >>> <connector
>> >>>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>> >>>> >>> <dep:environment
>> >>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> >>>> >>> <dep:moduleId>
>> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>rar</dep:type>
>> >>>> >>> </dep:moduleId>
>> >>>> >>> <dep:dependencies>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>postgresql</dep:groupId>
>> >>>> >>> <dep:artifactId>postgresql</dep:artifactId>
>> >>>> >>> <dep:version>8.1.jdbc3</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>> </dep:dependencies>
>> >>>> >>> </dep:environment>
>> >>>> >>>
>> >>>> >>> <resourceadapter>
>> >>>> >>> <outbound-resourceadapter>
>> >>>> >>> <connection-definition>
>> >>>> >>>
>> >>>>
>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>
>> >>>>
>> >>>> >>>
>> >>>> >>> <connectiondefinition-instance>
>> >>>> >>> <name>jdbc/default</name>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="UserName">admin</config-property-setting>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="Password">master</config-property-setting>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="Driver">org.postgresql.Driver</config-property-setting>
>> >>>> >>> <config-property-setting
>> >>>> >>>
>> >>>>
>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>
>> >>>>
>> >>>> >>>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="CommitBeforeAutocommit">true</config-property-setting>
>> >>>> >>> <connectionmanager>
>> >>>> >>> <local-transaction/>
>> >>>> >>> <single-pool>
>> >>>> >>> <max-size>10</max-size>
>> >>>> >>> <min-size>5</min-size>
>> >>>> >>>
>> >>>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>> >>>> >>>
>> >>>> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
>> >>>> >>> <match-one/>
>> >>>> >>> </single-pool>
>> >>>> >>> </connectionmanager>
>> >>>> >>> </connectiondefinition-instance>
>> >>>> >>> </connection-definition>
>> >>>> >>> </outbound-resourceadapter>
>> >>>> >>> </resourceadapter>
>> >>>> >>> </connector>
>> >>>> >>
>> >>>> >>
>> >>>> >
>> >>>>
>> >>>
>> >>
>> >
>>
>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
created the JIRA - GERONIMO-2121 for that problem
Thanks,
Mario
Aaron Mulder wrote:
> I would not have expected that -- I would have thought that putting
> the dependency in the WAR would work. Can you create a Jira with the
> XML files you tried for the WAR dependency (application.xml,
> geronimo-application.xml, web.xml, and geronimo-web.xml) and include
> the error and mention that it works if you move the dependency to the
> EAR level?
>
> Thanks,
> Aaron
>
> On 6/14/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>> When I put the db connector dependency setting into the
>> geronimo-application.xml instead of the geronimo-web.xml
>> then the web app will be deployed without the error.
>>
>> Is the geronimo-application.xml the correct place for
>> the db connector dependency when the web app is deployed
>> as an EAR? Is it also mandatory to put all the other dependency
>> settings in the geronimo-application.xml when deploying as EAR?
>>
>> Thanks,
>> Mario
>>
>>
>>
>> Mario Rübsam wrote:
>> > Ok, something I not mentioned before is, that I deploy the web
>> application
>> > packaged in an EAR.
>> >
>> > here the geronimo-application.xml:
>> >
>> > <?xml version="1.0" encoding="UTF-8"?>
>> > <application
>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.0"
>> >
>> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.0"
>> > configId="coderesearch/ei-service/2.3/car"
>> > parentId="geronimo/j2ee-server/1.0/car">
>> >
>> > <module>
>> > <web>client.war</web>
>> > <alt-dd>META-INF/geronimo-web.xml</alt-dd>
>> > </module>
>> > </application>
>> >
>> >
>> > and the application.xml:
>> >
>> > <?xml version="1.0" encoding="ISO-8859-1"?>
>> > <application xmlns="http://java.sun.com/xml/ns/j2ee"
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
>> > version="1.4">
>> >
>> > <display-name>ei-Service</display-name>
>> >
>> > <module>
>> > <web>
>> > <web-uri>client.war</web-uri>
>> > <context-root>/ei-service</context-root>
>> > </web>
>> > </module>
>> >
>> > <module>
>> > <web>
>> > <web-uri>client.war</web-uri>
>> > <context-root>/</context-root>
>> > </web>
>> > </module>
>> > </application>
>> >
>> >
>> > Are there any differences in deploying between WAR and EAR in
>> combination
>> > with the database pools?
>> >
>> > Thanks,
>> > Mario
>> >
>> >
>> >
>> >
>> > Mario Rübsam wrote:
>> >> Aaron Mulder wrote:
>> >>> I think we ought to try to figure this out for 1.1.
>> >>>
>> >>> Mario, are you sure the data source is deploying correctly? Do you
>> >>> see it listed as started in the "J2EE Connectors" screen of the
>> >>> console?
>> >>
>> >> Aaron,
>> >>
>> >> yes I'm sure, the datasource is available and the J2EE connector
>> >> is available for stop/uninstall.
>> >>
>> >> Thanks,
>> >> Mario
>> >>
>> >>
>> >>>
>> >>> Thanks,
>> >>> Aaron
>> >>>
>> >>> On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>> >>>> Any new ideas about the problem?
>> >>>>
>> >>>> Thanks,
>> >>>> Mario
>> >>>>
>> >>>>
>> >>>> Mario Rübsam wrote:
>> >>>> > David Jencks wrote:
>> >>>> >> What happens if you change both this and the moduleId in the rar
>> >>>> plan
>> >>>> >> to type car?
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>rar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >
>> >>>> > changed it to "car" but still no luck, I used the "rar" because
>> >>>> the console
>> >>>> > wizard uses "rar" too
>> >>>> >
>> >>>> >> It should work the way you have it.... but we might have some
>> >>>> >> hardcoded assumptions about car left.
>> >>>> >
>> >>>> > I get the same error message when I remove the dependency. I tried
>> >>>> > it also with or without the version and type. Always the same
>> >>>> message.
>> >>>> > The db pool is deployed without problems I also checked the
>> >>>> repository
>> >>>> > structure for the db rar/car.
>> >>>> >
>> >>>> > Thanks,
>> >>>> > Mario
>> >>>> >
>> >>>> >
>> >>>> >> should have type car
>> >>>> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>> >>>> >>
>> >>>> >>> Hi,
>> >>>> >>>
>> >>>> >>> with the current release candidate I still have problems
>> >>>> >>> linking to the deployed datasource. My dependencies should
>> >>>> >>> match the examples from the web console but still no
>> >>>> >>> luck when deploying.
>> >>>> >>>
>> >>>> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>> >>>> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
>> >>>> >>> resource reference 'jdbc/default' (Could not find resource
>> >>>> >>> 'jdbc/default'. Perhaps it has not yet been configured, or
>> >>>> your
>> >>>> >>> application does not have a dependency declared for that
>> >>>> resource
>> >>>> >>> module?)
>> >>>> >>>
>> >>>> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>> >>>> >>>
>> >>>> >>> Thanks,
>> >>>> >>> Mario
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> here the geronimo-web.xml:
>> >>>> >>>
>> >>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>> >>>> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>> >>>> >>>
>> >>>> >>> <dep:environment
>> >>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> >>>> >>> <dep:moduleId>
>> >>>> >>> <dep:groupId>coderesearch</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>war</dep:type>
>> >>>> >>> </dep:moduleId>
>> >>>> >>>
>> >>>> >>> <dep:dependencies>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>coderesearch</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>car</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>rar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-email</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-email</dep:artifactId>
>> >>>> >>> <dep:version>1.0</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-codec</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-codec</dep:artifactId>
>> >>>> >>> <dep:version>1.3</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-httpclient</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
>> >>>> >>> <dep:version>3.0</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>commons-fileupload</dep:groupId>
>> >>>> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
>> >>>> >>> <dep:version>1.0</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>> </dep:dependencies>
>> >>>> >>>
>> >>>> >>> <dep:hidden-classes/>
>> >>>> >>> <dep:non-overridable-classes/>
>> >>>> >>>
>> >>>> >>> </dep:environment>
>> >>>> >>>
>> >>>> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>> >>>> >>>
>> >>>> >>> <naming:resource-ref>
>> >>>> >>> <naming:ref-name>jdbc/default</naming:ref-name>
>> >>>> >>> <naming:resource-link>jdbc/default</naming:resource-link>
>> >>>> >>> </naming:resource-ref>
>> >>>> >>>
>> >>>> >>> </web-app>
>> >>>> >>>
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> and the web.xml:
>> >>>> >>>
>> >>>> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> >>>> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>> >>>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> >>>> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> >>>> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>> >>>> >>> version="2.4">
>> >>>> >>>
>> >>>> >>> <servlet>
>> >>>> >>> <display-name>MainServlet</display-name>
>> >>>> >>> <servlet-name>MainServlet</servlet-name>
>> >>>> >>>
>> >>>> >>>
>> >>>>
>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>> >>>>
>> >>>> >>>
>> >>>> >>> <load-on-startup>1</load-on-startup>
>> >>>> >>> </servlet>
>> >>>> >>>
>> >>>> >>> <servlet-mapping>
>> >>>> >>> <servlet-name>MainServlet</servlet-name>
>> >>>> >>> <url-pattern>/*</url-pattern>
>> >>>> >>> </servlet-mapping>
>> >>>> >>>
>> >>>> >>> <env-entry>
>> >>>> >>> <env-entry-name>server/ServerType</env-entry-name>
>> >>>> >>> <env-entry-type>java.lang.String</env-entry-type>
>> >>>> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>> >>>> >>> </env-entry>
>> >>>> >>>
>> >>>> >>> <resource-ref>
>> >>>> >>> <res-ref-name>jdbc/default</res-ref-name>
>> >>>> >>> <res-type>javax.sql.DataSource</res-type>
>> >>>> >>> <res-auth>Container</res-auth>
>> >>>> >>> <res-sharing-scope>Shareable</res-sharing-scope>
>> >>>> >>> </resource-ref>
>> >>>> >>>
>> >>>> >>> </web-app>
>> >>>> >>>
>> >>>> >>>
>> >>>> >>> and the db deploy plan:
>> >>>> >>>
>> >>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>>> >>> <connector
>> >>>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>> >>>> >>> <dep:environment
>> >>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> >>>> >>> <dep:moduleId>
>> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>>> >>> <dep:version>2.3</dep:version>
>> >>>> >>> <dep:type>rar</dep:type>
>> >>>> >>> </dep:moduleId>
>> >>>> >>> <dep:dependencies>
>> >>>> >>> <dep:dependency>
>> >>>> >>> <dep:groupId>postgresql</dep:groupId>
>> >>>> >>> <dep:artifactId>postgresql</dep:artifactId>
>> >>>> >>> <dep:version>8.1.jdbc3</dep:version>
>> >>>> >>> <dep:type>jar</dep:type>
>> >>>> >>> </dep:dependency>
>> >>>> >>> </dep:dependencies>
>> >>>> >>> </dep:environment>
>> >>>> >>>
>> >>>> >>> <resourceadapter>
>> >>>> >>> <outbound-resourceadapter>
>> >>>> >>> <connection-definition>
>> >>>> >>>
>> >>>>
>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>
>> >>>>
>> >>>> >>>
>> >>>> >>> <connectiondefinition-instance>
>> >>>> >>> <name>jdbc/default</name>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="UserName">admin</config-property-setting>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="Password">master</config-property-setting>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="Driver">org.postgresql.Driver</config-property-setting>
>> >>>> >>> <config-property-setting
>> >>>> >>>
>> >>>>
>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>
>> >>>>
>> >>>> >>>
>> >>>> >>> <config-property-setting
>> >>>> >>> name="CommitBeforeAutocommit">true</config-property-setting>
>> >>>> >>> <connectionmanager>
>> >>>> >>> <local-transaction/>
>> >>>> >>> <single-pool>
>> >>>> >>> <max-size>10</max-size>
>> >>>> >>> <min-size>5</min-size>
>> >>>> >>>
>> >>>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>> >>>> >>>
>> >>>> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
>> >>>> >>> <match-one/>
>> >>>> >>> </single-pool>
>> >>>> >>> </connectionmanager>
>> >>>> >>> </connectiondefinition-instance>
>> >>>> >>> </connection-definition>
>> >>>> >>> </outbound-resourceadapter>
>> >>>> >>> </resourceadapter>
>> >>>> >>> </connector>
>> >>>> >>
>> >>>> >>
>> >>>> >
>> >>>>
>> >>>
>> >>
>> >
>>
>
Re: 1.1-rc1 deployment
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I would not have expected that -- I would have thought that putting
the dependency in the WAR would work. Can you create a Jira with the
XML files you tried for the WAR dependency (application.xml,
geronimo-application.xml, web.xml, and geronimo-web.xml) and include
the error and mention that it works if you move the dependency to the
EAR level?
Thanks,
Aaron
On 6/14/06, Mario Rübsam <mr...@coderesearch.com> wrote:
> When I put the db connector dependency setting into the
> geronimo-application.xml instead of the geronimo-web.xml
> then the web app will be deployed without the error.
>
> Is the geronimo-application.xml the correct place for
> the db connector dependency when the web app is deployed
> as an EAR? Is it also mandatory to put all the other dependency
> settings in the geronimo-application.xml when deploying as EAR?
>
> Thanks,
> Mario
>
>
>
> Mario Rübsam wrote:
> > Ok, something I not mentioned before is, that I deploy the web application
> > packaged in an EAR.
> >
> > here the geronimo-application.xml:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <application xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.0"
> > xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.0"
> > configId="coderesearch/ei-service/2.3/car"
> > parentId="geronimo/j2ee-server/1.0/car">
> >
> > <module>
> > <web>client.war</web>
> > <alt-dd>META-INF/geronimo-web.xml</alt-dd>
> > </module>
> > </application>
> >
> >
> > and the application.xml:
> >
> > <?xml version="1.0" encoding="ISO-8859-1"?>
> > <application xmlns="http://java.sun.com/xml/ns/j2ee"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
> > version="1.4">
> >
> > <display-name>ei-Service</display-name>
> >
> > <module>
> > <web>
> > <web-uri>client.war</web-uri>
> > <context-root>/ei-service</context-root>
> > </web>
> > </module>
> >
> > <module>
> > <web>
> > <web-uri>client.war</web-uri>
> > <context-root>/</context-root>
> > </web>
> > </module>
> > </application>
> >
> >
> > Are there any differences in deploying between WAR and EAR in combination
> > with the database pools?
> >
> > Thanks,
> > Mario
> >
> >
> >
> >
> > Mario Rübsam wrote:
> >> Aaron Mulder wrote:
> >>> I think we ought to try to figure this out for 1.1.
> >>>
> >>> Mario, are you sure the data source is deploying correctly? Do you
> >>> see it listed as started in the "J2EE Connectors" screen of the
> >>> console?
> >>
> >> Aaron,
> >>
> >> yes I'm sure, the datasource is available and the J2EE connector
> >> is available for stop/uninstall.
> >>
> >> Thanks,
> >> Mario
> >>
> >>
> >>>
> >>> Thanks,
> >>> Aaron
> >>>
> >>> On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
> >>>> Any new ideas about the problem?
> >>>>
> >>>> Thanks,
> >>>> Mario
> >>>>
> >>>>
> >>>> Mario Rübsam wrote:
> >>>> > David Jencks wrote:
> >>>> >> What happens if you change both this and the moduleId in the rar
> >>>> plan
> >>>> >> to type car?
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
> >>>> >>> <dep:version>2.3</dep:version>
> >>>> >>> <dep:type>rar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >
> >>>> > changed it to "car" but still no luck, I used the "rar" because
> >>>> the console
> >>>> > wizard uses "rar" too
> >>>> >
> >>>> >> It should work the way you have it.... but we might have some
> >>>> >> hardcoded assumptions about car left.
> >>>> >
> >>>> > I get the same error message when I remove the dependency. I tried
> >>>> > it also with or without the version and type. Always the same
> >>>> message.
> >>>> > The db pool is deployed without problems I also checked the
> >>>> repository
> >>>> > structure for the db rar/car.
> >>>> >
> >>>> > Thanks,
> >>>> > Mario
> >>>> >
> >>>> >
> >>>> >> should have type car
> >>>> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
> >>>> >>
> >>>> >>> Hi,
> >>>> >>>
> >>>> >>> with the current release candidate I still have problems
> >>>> >>> linking to the deployed datasource. My dependencies should
> >>>> >>> match the examples from the web console but still no
> >>>> >>> luck when deploying.
> >>>> >>>
> >>>> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
> >>>> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
> >>>> >>> resource reference 'jdbc/default' (Could not find resource
> >>>> >>> 'jdbc/default'. Perhaps it has not yet been configured, or
> >>>> your
> >>>> >>> application does not have a dependency declared for that
> >>>> resource
> >>>> >>> module?)
> >>>> >>>
> >>>> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
> >>>> >>>
> >>>> >>> Thanks,
> >>>> >>> Mario
> >>>> >>>
> >>>> >>>
> >>>> >>> here the geronimo-web.xml:
> >>>> >>>
> >>>> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>>> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
> >>>> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
> >>>> >>>
> >>>> >>> <dep:environment
> >>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
> >>>> >>> <dep:moduleId>
> >>>> >>> <dep:groupId>coderesearch</dep:groupId>
> >>>> >>> <dep:artifactId>ei-service</dep:artifactId>
> >>>> >>> <dep:version>2.3</dep:version>
> >>>> >>> <dep:type>war</dep:type>
> >>>> >>> </dep:moduleId>
> >>>> >>>
> >>>> >>> <dep:dependencies>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>coderesearch</dep:groupId>
> >>>> >>> <dep:artifactId>ei-service</dep:artifactId>
> >>>> >>> <dep:version>2.3</dep:version>
> >>>> >>> <dep:type>car</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
> >>>> >>> <dep:version>2.3</dep:version>
> >>>> >>> <dep:type>rar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>commons-email</dep:groupId>
> >>>> >>> <dep:artifactId>commons-email</dep:artifactId>
> >>>> >>> <dep:version>1.0</dep:version>
> >>>> >>> <dep:type>jar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>commons-codec</dep:groupId>
> >>>> >>> <dep:artifactId>commons-codec</dep:artifactId>
> >>>> >>> <dep:version>1.3</dep:version>
> >>>> >>> <dep:type>jar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>commons-httpclient</dep:groupId>
> >>>> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
> >>>> >>> <dep:version>3.0</dep:version>
> >>>> >>> <dep:type>jar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>commons-fileupload</dep:groupId>
> >>>> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
> >>>> >>> <dep:version>1.0</dep:version>
> >>>> >>> <dep:type>jar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>> </dep:dependencies>
> >>>> >>>
> >>>> >>> <dep:hidden-classes/>
> >>>> >>> <dep:non-overridable-classes/>
> >>>> >>>
> >>>> >>> </dep:environment>
> >>>> >>>
> >>>> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
> >>>> >>>
> >>>> >>> <naming:resource-ref>
> >>>> >>> <naming:ref-name>jdbc/default</naming:ref-name>
> >>>> >>> <naming:resource-link>jdbc/default</naming:resource-link>
> >>>> >>> </naming:resource-ref>
> >>>> >>>
> >>>> >>> </web-app>
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> and the web.xml:
> >>>> >>>
> >>>> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
> >>>> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> >>>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >>>> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> >>>> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> >>>> >>> version="2.4">
> >>>> >>>
> >>>> >>> <servlet>
> >>>> >>> <display-name>MainServlet</display-name>
> >>>> >>> <servlet-name>MainServlet</servlet-name>
> >>>> >>>
> >>>> >>>
> >>>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
> >>>>
> >>>> >>>
> >>>> >>> <load-on-startup>1</load-on-startup>
> >>>> >>> </servlet>
> >>>> >>>
> >>>> >>> <servlet-mapping>
> >>>> >>> <servlet-name>MainServlet</servlet-name>
> >>>> >>> <url-pattern>/*</url-pattern>
> >>>> >>> </servlet-mapping>
> >>>> >>>
> >>>> >>> <env-entry>
> >>>> >>> <env-entry-name>server/ServerType</env-entry-name>
> >>>> >>> <env-entry-type>java.lang.String</env-entry-type>
> >>>> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
> >>>> >>> </env-entry>
> >>>> >>>
> >>>> >>> <resource-ref>
> >>>> >>> <res-ref-name>jdbc/default</res-ref-name>
> >>>> >>> <res-type>javax.sql.DataSource</res-type>
> >>>> >>> <res-auth>Container</res-auth>
> >>>> >>> <res-sharing-scope>Shareable</res-sharing-scope>
> >>>> >>> </resource-ref>
> >>>> >>>
> >>>> >>> </web-app>
> >>>> >>>
> >>>> >>>
> >>>> >>> and the db deploy plan:
> >>>> >>>
> >>>> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>>> >>> <connector
> >>>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
> >>>> >>> <dep:environment
> >>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
> >>>> >>> <dep:moduleId>
> >>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
> >>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
> >>>> >>> <dep:version>2.3</dep:version>
> >>>> >>> <dep:type>rar</dep:type>
> >>>> >>> </dep:moduleId>
> >>>> >>> <dep:dependencies>
> >>>> >>> <dep:dependency>
> >>>> >>> <dep:groupId>postgresql</dep:groupId>
> >>>> >>> <dep:artifactId>postgresql</dep:artifactId>
> >>>> >>> <dep:version>8.1.jdbc3</dep:version>
> >>>> >>> <dep:type>jar</dep:type>
> >>>> >>> </dep:dependency>
> >>>> >>> </dep:dependencies>
> >>>> >>> </dep:environment>
> >>>> >>>
> >>>> >>> <resourceadapter>
> >>>> >>> <outbound-resourceadapter>
> >>>> >>> <connection-definition>
> >>>> >>>
> >>>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
> >>>>
> >>>> >>>
> >>>> >>> <connectiondefinition-instance>
> >>>> >>> <name>jdbc/default</name>
> >>>> >>> <config-property-setting
> >>>> >>> name="UserName">admin</config-property-setting>
> >>>> >>> <config-property-setting
> >>>> >>> name="Password">master</config-property-setting>
> >>>> >>> <config-property-setting
> >>>> >>> name="Driver">org.postgresql.Driver</config-property-setting>
> >>>> >>> <config-property-setting
> >>>> >>>
> >>>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
> >>>>
> >>>> >>>
> >>>> >>> <config-property-setting
> >>>> >>> name="CommitBeforeAutocommit">true</config-property-setting>
> >>>> >>> <connectionmanager>
> >>>> >>> <local-transaction/>
> >>>> >>> <single-pool>
> >>>> >>> <max-size>10</max-size>
> >>>> >>> <min-size>5</min-size>
> >>>> >>>
> >>>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
> >>>> >>>
> >>>> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
> >>>> >>> <match-one/>
> >>>> >>> </single-pool>
> >>>> >>> </connectionmanager>
> >>>> >>> </connectiondefinition-instance>
> >>>> >>> </connection-definition>
> >>>> >>> </outbound-resourceadapter>
> >>>> >>> </resourceadapter>
> >>>> >>> </connector>
> >>>> >>
> >>>> >>
> >>>> >
> >>>>
> >>>
> >>
> >
>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
When I put the db connector dependency setting into the
geronimo-application.xml instead of the geronimo-web.xml
then the web app will be deployed without the error.
Is the geronimo-application.xml the correct place for
the db connector dependency when the web app is deployed
as an EAR? Is it also mandatory to put all the other dependency
settings in the geronimo-application.xml when deploying as EAR?
Thanks,
Mario
Mario Rübsam wrote:
> Ok, something I not mentioned before is, that I deploy the web application
> packaged in an EAR.
>
> here the geronimo-application.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <application xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.0"
> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.0"
> configId="coderesearch/ei-service/2.3/car"
> parentId="geronimo/j2ee-server/1.0/car">
>
> <module>
> <web>client.war</web>
> <alt-dd>META-INF/geronimo-web.xml</alt-dd>
> </module>
> </application>
>
>
> and the application.xml:
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <application xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
> version="1.4">
>
> <display-name>ei-Service</display-name>
>
> <module>
> <web>
> <web-uri>client.war</web-uri>
> <context-root>/ei-service</context-root>
> </web>
> </module>
>
> <module>
> <web>
> <web-uri>client.war</web-uri>
> <context-root>/</context-root>
> </web>
> </module>
> </application>
>
>
> Are there any differences in deploying between WAR and EAR in combination
> with the database pools?
>
> Thanks,
> Mario
>
>
>
>
> Mario Rübsam wrote:
>> Aaron Mulder wrote:
>>> I think we ought to try to figure this out for 1.1.
>>>
>>> Mario, are you sure the data source is deploying correctly? Do you
>>> see it listed as started in the "J2EE Connectors" screen of the
>>> console?
>>
>> Aaron,
>>
>> yes I'm sure, the datasource is available and the J2EE connector
>> is available for stop/uninstall.
>>
>> Thanks,
>> Mario
>>
>>
>>>
>>> Thanks,
>>> Aaron
>>>
>>> On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>>>> Any new ideas about the problem?
>>>>
>>>> Thanks,
>>>> Mario
>>>>
>>>>
>>>> Mario Rübsam wrote:
>>>> > David Jencks wrote:
>>>> >> What happens if you change both this and the moduleId in the rar
>>>> plan
>>>> >> to type car?
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>>>> >>> <dep:version>2.3</dep:version>
>>>> >>> <dep:type>rar</dep:type>
>>>> >>> </dep:dependency>
>>>> >
>>>> > changed it to "car" but still no luck, I used the "rar" because
>>>> the console
>>>> > wizard uses "rar" too
>>>> >
>>>> >> It should work the way you have it.... but we might have some
>>>> >> hardcoded assumptions about car left.
>>>> >
>>>> > I get the same error message when I remove the dependency. I tried
>>>> > it also with or without the version and type. Always the same
>>>> message.
>>>> > The db pool is deployed without problems I also checked the
>>>> repository
>>>> > structure for the db rar/car.
>>>> >
>>>> > Thanks,
>>>> > Mario
>>>> >
>>>> >
>>>> >> should have type car
>>>> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>>>> >>
>>>> >>> Hi,
>>>> >>>
>>>> >>> with the current release candidate I still have problems
>>>> >>> linking to the deployed datasource. My dependencies should
>>>> >>> match the examples from the web console but still no
>>>> >>> luck when deploying.
>>>> >>>
>>>> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>>>> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
>>>> >>> resource reference 'jdbc/default' (Could not find resource
>>>> >>> 'jdbc/default'. Perhaps it has not yet been configured, or
>>>> your
>>>> >>> application does not have a dependency declared for that
>>>> resource
>>>> >>> module?)
>>>> >>>
>>>> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>>>> >>>
>>>> >>> Thanks,
>>>> >>> Mario
>>>> >>>
>>>> >>>
>>>> >>> here the geronimo-web.xml:
>>>> >>>
>>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>>>> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>>>> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>>>> >>>
>>>> >>> <dep:environment
>>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>>>> >>> <dep:moduleId>
>>>> >>> <dep:groupId>coderesearch</dep:groupId>
>>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>>>> >>> <dep:version>2.3</dep:version>
>>>> >>> <dep:type>war</dep:type>
>>>> >>> </dep:moduleId>
>>>> >>>
>>>> >>> <dep:dependencies>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>coderesearch</dep:groupId>
>>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>>>> >>> <dep:version>2.3</dep:version>
>>>> >>> <dep:type>car</dep:type>
>>>> >>> </dep:dependency>
>>>> >>>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>>>> >>> <dep:version>2.3</dep:version>
>>>> >>> <dep:type>rar</dep:type>
>>>> >>> </dep:dependency>
>>>> >>>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>commons-email</dep:groupId>
>>>> >>> <dep:artifactId>commons-email</dep:artifactId>
>>>> >>> <dep:version>1.0</dep:version>
>>>> >>> <dep:type>jar</dep:type>
>>>> >>> </dep:dependency>
>>>> >>>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>commons-codec</dep:groupId>
>>>> >>> <dep:artifactId>commons-codec</dep:artifactId>
>>>> >>> <dep:version>1.3</dep:version>
>>>> >>> <dep:type>jar</dep:type>
>>>> >>> </dep:dependency>
>>>> >>>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>commons-httpclient</dep:groupId>
>>>> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
>>>> >>> <dep:version>3.0</dep:version>
>>>> >>> <dep:type>jar</dep:type>
>>>> >>> </dep:dependency>
>>>> >>>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>commons-fileupload</dep:groupId>
>>>> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
>>>> >>> <dep:version>1.0</dep:version>
>>>> >>> <dep:type>jar</dep:type>
>>>> >>> </dep:dependency>
>>>> >>> </dep:dependencies>
>>>> >>>
>>>> >>> <dep:hidden-classes/>
>>>> >>> <dep:non-overridable-classes/>
>>>> >>>
>>>> >>> </dep:environment>
>>>> >>>
>>>> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>>>> >>>
>>>> >>> <naming:resource-ref>
>>>> >>> <naming:ref-name>jdbc/default</naming:ref-name>
>>>> >>> <naming:resource-link>jdbc/default</naming:resource-link>
>>>> >>> </naming:resource-ref>
>>>> >>>
>>>> >>> </web-app>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> and the web.xml:
>>>> >>>
>>>> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
>>>> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>>> >>> version="2.4">
>>>> >>>
>>>> >>> <servlet>
>>>> >>> <display-name>MainServlet</display-name>
>>>> >>> <servlet-name>MainServlet</servlet-name>
>>>> >>>
>>>> >>>
>>>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>>>>
>>>> >>>
>>>> >>> <load-on-startup>1</load-on-startup>
>>>> >>> </servlet>
>>>> >>>
>>>> >>> <servlet-mapping>
>>>> >>> <servlet-name>MainServlet</servlet-name>
>>>> >>> <url-pattern>/*</url-pattern>
>>>> >>> </servlet-mapping>
>>>> >>>
>>>> >>> <env-entry>
>>>> >>> <env-entry-name>server/ServerType</env-entry-name>
>>>> >>> <env-entry-type>java.lang.String</env-entry-type>
>>>> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>>>> >>> </env-entry>
>>>> >>>
>>>> >>> <resource-ref>
>>>> >>> <res-ref-name>jdbc/default</res-ref-name>
>>>> >>> <res-type>javax.sql.DataSource</res-type>
>>>> >>> <res-auth>Container</res-auth>
>>>> >>> <res-sharing-scope>Shareable</res-sharing-scope>
>>>> >>> </resource-ref>
>>>> >>>
>>>> >>> </web-app>
>>>> >>>
>>>> >>>
>>>> >>> and the db deploy plan:
>>>> >>>
>>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>>>> >>> <connector
>>>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>>>> >>> <dep:environment
>>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>>>> >>> <dep:moduleId>
>>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>>>> >>> <dep:version>2.3</dep:version>
>>>> >>> <dep:type>rar</dep:type>
>>>> >>> </dep:moduleId>
>>>> >>> <dep:dependencies>
>>>> >>> <dep:dependency>
>>>> >>> <dep:groupId>postgresql</dep:groupId>
>>>> >>> <dep:artifactId>postgresql</dep:artifactId>
>>>> >>> <dep:version>8.1.jdbc3</dep:version>
>>>> >>> <dep:type>jar</dep:type>
>>>> >>> </dep:dependency>
>>>> >>> </dep:dependencies>
>>>> >>> </dep:environment>
>>>> >>>
>>>> >>> <resourceadapter>
>>>> >>> <outbound-resourceadapter>
>>>> >>> <connection-definition>
>>>> >>>
>>>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>>>
>>>> >>>
>>>> >>> <connectiondefinition-instance>
>>>> >>> <name>jdbc/default</name>
>>>> >>> <config-property-setting
>>>> >>> name="UserName">admin</config-property-setting>
>>>> >>> <config-property-setting
>>>> >>> name="Password">master</config-property-setting>
>>>> >>> <config-property-setting
>>>> >>> name="Driver">org.postgresql.Driver</config-property-setting>
>>>> >>> <config-property-setting
>>>> >>>
>>>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>>>
>>>> >>>
>>>> >>> <config-property-setting
>>>> >>> name="CommitBeforeAutocommit">true</config-property-setting>
>>>> >>> <connectionmanager>
>>>> >>> <local-transaction/>
>>>> >>> <single-pool>
>>>> >>> <max-size>10</max-size>
>>>> >>> <min-size>5</min-size>
>>>> >>>
>>>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>>>> >>>
>>>> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
>>>> >>> <match-one/>
>>>> >>> </single-pool>
>>>> >>> </connectionmanager>
>>>> >>> </connectiondefinition-instance>
>>>> >>> </connection-definition>
>>>> >>> </outbound-resourceadapter>
>>>> >>> </resourceadapter>
>>>> >>> </connector>
>>>> >>
>>>> >>
>>>> >
>>>>
>>>
>>
>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
Ok, something I not mentioned before is, that I deploy the web application
packaged in an EAR.
here the geronimo-application.xml:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.0"
xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.0"
configId="coderesearch/ei-service/2.3/car"
parentId="geronimo/j2ee-server/1.0/car">
<module>
<web>client.war</web>
<alt-dd>META-INF/geronimo-web.xml</alt-dd>
</module>
</application>
and the application.xml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<application xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
version="1.4">
<display-name>ei-Service</display-name>
<module>
<web>
<web-uri>client.war</web-uri>
<context-root>/ei-service</context-root>
</web>
</module>
<module>
<web>
<web-uri>client.war</web-uri>
<context-root>/</context-root>
</web>
</module>
</application>
Are there any differences in deploying between WAR and EAR in combination
with the database pools?
Thanks,
Mario
Mario Rübsam wrote:
> Aaron Mulder wrote:
>> I think we ought to try to figure this out for 1.1.
>>
>> Mario, are you sure the data source is deploying correctly? Do you
>> see it listed as started in the "J2EE Connectors" screen of the
>> console?
>
> Aaron,
>
> yes I'm sure, the datasource is available and the J2EE connector
> is available for stop/uninstall.
>
> Thanks,
> Mario
>
>
>>
>> Thanks,
>> Aaron
>>
>> On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>>> Any new ideas about the problem?
>>>
>>> Thanks,
>>> Mario
>>>
>>>
>>> Mario Rübsam wrote:
>>> > David Jencks wrote:
>>> >> What happens if you change both this and the moduleId in the rar plan
>>> >> to type car?
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>>> >>> <dep:version>2.3</dep:version>
>>> >>> <dep:type>rar</dep:type>
>>> >>> </dep:dependency>
>>> >
>>> > changed it to "car" but still no luck, I used the "rar" because the
>>> console
>>> > wizard uses "rar" too
>>> >
>>> >> It should work the way you have it.... but we might have some
>>> >> hardcoded assumptions about car left.
>>> >
>>> > I get the same error message when I remove the dependency. I tried
>>> > it also with or without the version and type. Always the same message.
>>> > The db pool is deployed without problems I also checked the repository
>>> > structure for the db rar/car.
>>> >
>>> > Thanks,
>>> > Mario
>>> >
>>> >
>>> >> should have type car
>>> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>>> >>
>>> >>> Hi,
>>> >>>
>>> >>> with the current release candidate I still have problems
>>> >>> linking to the deployed datasource. My dependencies should
>>> >>> match the examples from the web console but still no
>>> >>> luck when deploying.
>>> >>>
>>> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>>> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
>>> >>> resource reference 'jdbc/default' (Could not find resource
>>> >>> 'jdbc/default'. Perhaps it has not yet been configured, or your
>>> >>> application does not have a dependency declared for that
>>> resource
>>> >>> module?)
>>> >>>
>>> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>>> >>>
>>> >>> Thanks,
>>> >>> Mario
>>> >>>
>>> >>>
>>> >>> here the geronimo-web.xml:
>>> >>>
>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>>> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>>> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>>> >>>
>>> >>> <dep:environment
>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>>> >>> <dep:moduleId>
>>> >>> <dep:groupId>coderesearch</dep:groupId>
>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>>> >>> <dep:version>2.3</dep:version>
>>> >>> <dep:type>war</dep:type>
>>> >>> </dep:moduleId>
>>> >>>
>>> >>> <dep:dependencies>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>coderesearch</dep:groupId>
>>> >>> <dep:artifactId>ei-service</dep:artifactId>
>>> >>> <dep:version>2.3</dep:version>
>>> >>> <dep:type>car</dep:type>
>>> >>> </dep:dependency>
>>> >>>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>>> >>> <dep:version>2.3</dep:version>
>>> >>> <dep:type>rar</dep:type>
>>> >>> </dep:dependency>
>>> >>>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>commons-email</dep:groupId>
>>> >>> <dep:artifactId>commons-email</dep:artifactId>
>>> >>> <dep:version>1.0</dep:version>
>>> >>> <dep:type>jar</dep:type>
>>> >>> </dep:dependency>
>>> >>>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>commons-codec</dep:groupId>
>>> >>> <dep:artifactId>commons-codec</dep:artifactId>
>>> >>> <dep:version>1.3</dep:version>
>>> >>> <dep:type>jar</dep:type>
>>> >>> </dep:dependency>
>>> >>>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>commons-httpclient</dep:groupId>
>>> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
>>> >>> <dep:version>3.0</dep:version>
>>> >>> <dep:type>jar</dep:type>
>>> >>> </dep:dependency>
>>> >>>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>commons-fileupload</dep:groupId>
>>> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
>>> >>> <dep:version>1.0</dep:version>
>>> >>> <dep:type>jar</dep:type>
>>> >>> </dep:dependency>
>>> >>> </dep:dependencies>
>>> >>>
>>> >>> <dep:hidden-classes/>
>>> >>> <dep:non-overridable-classes/>
>>> >>>
>>> >>> </dep:environment>
>>> >>>
>>> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>>> >>>
>>> >>> <naming:resource-ref>
>>> >>> <naming:ref-name>jdbc/default</naming:ref-name>
>>> >>> <naming:resource-link>jdbc/default</naming:resource-link>
>>> >>> </naming:resource-ref>
>>> >>>
>>> >>> </web-app>
>>> >>>
>>> >>>
>>> >>>
>>> >>> and the web.xml:
>>> >>>
>>> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
>>> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>> >>> version="2.4">
>>> >>>
>>> >>> <servlet>
>>> >>> <display-name>MainServlet</display-name>
>>> >>> <servlet-name>MainServlet</servlet-name>
>>> >>>
>>> >>>
>>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>>>
>>> >>>
>>> >>> <load-on-startup>1</load-on-startup>
>>> >>> </servlet>
>>> >>>
>>> >>> <servlet-mapping>
>>> >>> <servlet-name>MainServlet</servlet-name>
>>> >>> <url-pattern>/*</url-pattern>
>>> >>> </servlet-mapping>
>>> >>>
>>> >>> <env-entry>
>>> >>> <env-entry-name>server/ServerType</env-entry-name>
>>> >>> <env-entry-type>java.lang.String</env-entry-type>
>>> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>>> >>> </env-entry>
>>> >>>
>>> >>> <resource-ref>
>>> >>> <res-ref-name>jdbc/default</res-ref-name>
>>> >>> <res-type>javax.sql.DataSource</res-type>
>>> >>> <res-auth>Container</res-auth>
>>> >>> <res-sharing-scope>Shareable</res-sharing-scope>
>>> >>> </resource-ref>
>>> >>>
>>> >>> </web-app>
>>> >>>
>>> >>>
>>> >>> and the db deploy plan:
>>> >>>
>>> >>> <?xml version="1.0" encoding="UTF-8"?>
>>> >>> <connector
>>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>>> >>> <dep:environment
>>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>>> >>> <dep:moduleId>
>>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>>> >>> <dep:version>2.3</dep:version>
>>> >>> <dep:type>rar</dep:type>
>>> >>> </dep:moduleId>
>>> >>> <dep:dependencies>
>>> >>> <dep:dependency>
>>> >>> <dep:groupId>postgresql</dep:groupId>
>>> >>> <dep:artifactId>postgresql</dep:artifactId>
>>> >>> <dep:version>8.1.jdbc3</dep:version>
>>> >>> <dep:type>jar</dep:type>
>>> >>> </dep:dependency>
>>> >>> </dep:dependencies>
>>> >>> </dep:environment>
>>> >>>
>>> >>> <resourceadapter>
>>> >>> <outbound-resourceadapter>
>>> >>> <connection-definition>
>>> >>>
>>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>>
>>> >>>
>>> >>> <connectiondefinition-instance>
>>> >>> <name>jdbc/default</name>
>>> >>> <config-property-setting
>>> >>> name="UserName">admin</config-property-setting>
>>> >>> <config-property-setting
>>> >>> name="Password">master</config-property-setting>
>>> >>> <config-property-setting
>>> >>> name="Driver">org.postgresql.Driver</config-property-setting>
>>> >>> <config-property-setting
>>> >>>
>>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>>
>>> >>>
>>> >>> <config-property-setting
>>> >>> name="CommitBeforeAutocommit">true</config-property-setting>
>>> >>> <connectionmanager>
>>> >>> <local-transaction/>
>>> >>> <single-pool>
>>> >>> <max-size>10</max-size>
>>> >>> <min-size>5</min-size>
>>> >>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>>> >>>
>>> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
>>> >>> <match-one/>
>>> >>> </single-pool>
>>> >>> </connectionmanager>
>>> >>> </connectiondefinition-instance>
>>> >>> </connection-definition>
>>> >>> </outbound-resourceadapter>
>>> >>> </resourceadapter>
>>> >>> </connector>
>>> >>
>>> >>
>>> >
>>>
>>
>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
Aaron Mulder wrote:
> I think we ought to try to figure this out for 1.1.
>
> Mario, are you sure the data source is deploying correctly? Do you
> see it listed as started in the "J2EE Connectors" screen of the
> console?
Aaron,
yes I'm sure, the datasource is available and the J2EE connector
is available for stop/uninstall.
Thanks,
Mario
>
> Thanks,
> Aaron
>
> On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
>> Any new ideas about the problem?
>>
>> Thanks,
>> Mario
>>
>>
>> Mario Rübsam wrote:
>> > David Jencks wrote:
>> >> What happens if you change both this and the moduleId in the rar plan
>> >> to type car?
>> >>> <dep:dependency>
>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>> <dep:version>2.3</dep:version>
>> >>> <dep:type>rar</dep:type>
>> >>> </dep:dependency>
>> >
>> > changed it to "car" but still no luck, I used the "rar" because the
>> console
>> > wizard uses "rar" too
>> >
>> >> It should work the way you have it.... but we might have some
>> >> hardcoded assumptions about car left.
>> >
>> > I get the same error message when I remove the dependency. I tried
>> > it also with or without the version and type. Always the same message.
>> > The db pool is deployed without problems I also checked the repository
>> > structure for the db rar/car.
>> >
>> > Thanks,
>> > Mario
>> >
>> >
>> >> should have type car
>> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> with the current release candidate I still have problems
>> >>> linking to the deployed datasource. My dependencies should
>> >>> match the examples from the web console but still no
>> >>> luck when deploying.
>> >>>
>> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
>> >>> resource reference 'jdbc/default' (Could not find resource
>> >>> 'jdbc/default'. Perhaps it has not yet been configured, or your
>> >>> application does not have a dependency declared for that resource
>> >>> module?)
>> >>>
>> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>> >>>
>> >>> Thanks,
>> >>> Mario
>> >>>
>> >>>
>> >>> here the geronimo-web.xml:
>> >>>
>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>> >>>
>> >>> <dep:environment
>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> >>> <dep:moduleId>
>> >>> <dep:groupId>coderesearch</dep:groupId>
>> >>> <dep:artifactId>ei-service</dep:artifactId>
>> >>> <dep:version>2.3</dep:version>
>> >>> <dep:type>war</dep:type>
>> >>> </dep:moduleId>
>> >>>
>> >>> <dep:dependencies>
>> >>> <dep:dependency>
>> >>> <dep:groupId>coderesearch</dep:groupId>
>> >>> <dep:artifactId>ei-service</dep:artifactId>
>> >>> <dep:version>2.3</dep:version>
>> >>> <dep:type>car</dep:type>
>> >>> </dep:dependency>
>> >>>
>> >>> <dep:dependency>
>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>> <dep:version>2.3</dep:version>
>> >>> <dep:type>rar</dep:type>
>> >>> </dep:dependency>
>> >>>
>> >>> <dep:dependency>
>> >>> <dep:groupId>commons-email</dep:groupId>
>> >>> <dep:artifactId>commons-email</dep:artifactId>
>> >>> <dep:version>1.0</dep:version>
>> >>> <dep:type>jar</dep:type>
>> >>> </dep:dependency>
>> >>>
>> >>> <dep:dependency>
>> >>> <dep:groupId>commons-codec</dep:groupId>
>> >>> <dep:artifactId>commons-codec</dep:artifactId>
>> >>> <dep:version>1.3</dep:version>
>> >>> <dep:type>jar</dep:type>
>> >>> </dep:dependency>
>> >>>
>> >>> <dep:dependency>
>> >>> <dep:groupId>commons-httpclient</dep:groupId>
>> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
>> >>> <dep:version>3.0</dep:version>
>> >>> <dep:type>jar</dep:type>
>> >>> </dep:dependency>
>> >>>
>> >>> <dep:dependency>
>> >>> <dep:groupId>commons-fileupload</dep:groupId>
>> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
>> >>> <dep:version>1.0</dep:version>
>> >>> <dep:type>jar</dep:type>
>> >>> </dep:dependency>
>> >>> </dep:dependencies>
>> >>>
>> >>> <dep:hidden-classes/>
>> >>> <dep:non-overridable-classes/>
>> >>>
>> >>> </dep:environment>
>> >>>
>> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>> >>>
>> >>> <naming:resource-ref>
>> >>> <naming:ref-name>jdbc/default</naming:ref-name>
>> >>> <naming:resource-link>jdbc/default</naming:resource-link>
>> >>> </naming:resource-ref>
>> >>>
>> >>> </web-app>
>> >>>
>> >>>
>> >>>
>> >>> and the web.xml:
>> >>>
>> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>> >>> version="2.4">
>> >>>
>> >>> <servlet>
>> >>> <display-name>MainServlet</display-name>
>> >>> <servlet-name>MainServlet</servlet-name>
>> >>>
>> >>>
>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>> >>>
>> >>> <load-on-startup>1</load-on-startup>
>> >>> </servlet>
>> >>>
>> >>> <servlet-mapping>
>> >>> <servlet-name>MainServlet</servlet-name>
>> >>> <url-pattern>/*</url-pattern>
>> >>> </servlet-mapping>
>> >>>
>> >>> <env-entry>
>> >>> <env-entry-name>server/ServerType</env-entry-name>
>> >>> <env-entry-type>java.lang.String</env-entry-type>
>> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>> >>> </env-entry>
>> >>>
>> >>> <resource-ref>
>> >>> <res-ref-name>jdbc/default</res-ref-name>
>> >>> <res-type>javax.sql.DataSource</res-type>
>> >>> <res-auth>Container</res-auth>
>> >>> <res-sharing-scope>Shareable</res-sharing-scope>
>> >>> </resource-ref>
>> >>>
>> >>> </web-app>
>> >>>
>> >>>
>> >>> and the db deploy plan:
>> >>>
>> >>> <?xml version="1.0" encoding="UTF-8"?>
>> >>> <connector
>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>> >>> <dep:environment
>> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> >>> <dep:moduleId>
>> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> >>> <dep:artifactId>ei-service-default</dep:artifactId>
>> >>> <dep:version>2.3</dep:version>
>> >>> <dep:type>rar</dep:type>
>> >>> </dep:moduleId>
>> >>> <dep:dependencies>
>> >>> <dep:dependency>
>> >>> <dep:groupId>postgresql</dep:groupId>
>> >>> <dep:artifactId>postgresql</dep:artifactId>
>> >>> <dep:version>8.1.jdbc3</dep:version>
>> >>> <dep:type>jar</dep:type>
>> >>> </dep:dependency>
>> >>> </dep:dependencies>
>> >>> </dep:environment>
>> >>>
>> >>> <resourceadapter>
>> >>> <outbound-resourceadapter>
>> >>> <connection-definition>
>> >>>
>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>
>> >>>
>> >>> <connectiondefinition-instance>
>> >>> <name>jdbc/default</name>
>> >>> <config-property-setting
>> >>> name="UserName">admin</config-property-setting>
>> >>> <config-property-setting
>> >>> name="Password">master</config-property-setting>
>> >>> <config-property-setting
>> >>> name="Driver">org.postgresql.Driver</config-property-setting>
>> >>> <config-property-setting
>> >>>
>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>
>> >>>
>> >>> <config-property-setting
>> >>> name="CommitBeforeAutocommit">true</config-property-setting>
>> >>> <connectionmanager>
>> >>> <local-transaction/>
>> >>> <single-pool>
>> >>> <max-size>10</max-size>
>> >>> <min-size>5</min-size>
>> >>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>> >>>
>> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
>> >>> <match-one/>
>> >>> </single-pool>
>> >>> </connectionmanager>
>> >>> </connectiondefinition-instance>
>> >>> </connection-definition>
>> >>> </outbound-resourceadapter>
>> >>> </resourceadapter>
>> >>> </connector>
>> >>
>> >>
>> >
>>
>
Re: 1.1-rc1 deployment
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I think we ought to try to figure this out for 1.1.
Mario, are you sure the data source is deploying correctly? Do you
see it listed as started in the "J2EE Connectors" screen of the
console?
Thanks,
Aaron
On 6/12/06, Mario Rübsam <mr...@coderesearch.com> wrote:
> Any new ideas about the problem?
>
> Thanks,
> Mario
>
>
> Mario Rübsam wrote:
> > David Jencks wrote:
> >> What happens if you change both this and the moduleId in the rar plan
> >> to type car?
> >>> <dep:dependency>
> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
> >>> <dep:artifactId>ei-service-default</dep:artifactId>
> >>> <dep:version>2.3</dep:version>
> >>> <dep:type>rar</dep:type>
> >>> </dep:dependency>
> >
> > changed it to "car" but still no luck, I used the "rar" because the console
> > wizard uses "rar" too
> >
> >> It should work the way you have it.... but we might have some
> >> hardcoded assumptions about car left.
> >
> > I get the same error message when I remove the dependency. I tried
> > it also with or without the version and type. Always the same message.
> > The db pool is deployed without problems I also checked the repository
> > structure for the db rar/car.
> >
> > Thanks,
> > Mario
> >
> >
> >> should have type car
> >> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
> >>
> >>> Hi,
> >>>
> >>> with the current release candidate I still have problems
> >>> linking to the deployed datasource. My dependencies should
> >>> match the examples from the web console but still no
> >>> luck when deploying.
> >>>
> >>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
> >>> Error: Unable to distribute eiservice.ear: Unable to resolve
> >>> resource reference 'jdbc/default' (Could not find resource
> >>> 'jdbc/default'. Perhaps it has not yet been configured, or your
> >>> application does not have a dependency declared for that resource
> >>> module?)
> >>>
> >>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
> >>>
> >>> Thanks,
> >>> Mario
> >>>
> >>>
> >>> here the geronimo-web.xml:
> >>>
> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
> >>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
> >>>
> >>> <dep:environment
> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
> >>> <dep:moduleId>
> >>> <dep:groupId>coderesearch</dep:groupId>
> >>> <dep:artifactId>ei-service</dep:artifactId>
> >>> <dep:version>2.3</dep:version>
> >>> <dep:type>war</dep:type>
> >>> </dep:moduleId>
> >>>
> >>> <dep:dependencies>
> >>> <dep:dependency>
> >>> <dep:groupId>coderesearch</dep:groupId>
> >>> <dep:artifactId>ei-service</dep:artifactId>
> >>> <dep:version>2.3</dep:version>
> >>> <dep:type>car</dep:type>
> >>> </dep:dependency>
> >>>
> >>> <dep:dependency>
> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
> >>> <dep:artifactId>ei-service-default</dep:artifactId>
> >>> <dep:version>2.3</dep:version>
> >>> <dep:type>rar</dep:type>
> >>> </dep:dependency>
> >>>
> >>> <dep:dependency>
> >>> <dep:groupId>commons-email</dep:groupId>
> >>> <dep:artifactId>commons-email</dep:artifactId>
> >>> <dep:version>1.0</dep:version>
> >>> <dep:type>jar</dep:type>
> >>> </dep:dependency>
> >>>
> >>> <dep:dependency>
> >>> <dep:groupId>commons-codec</dep:groupId>
> >>> <dep:artifactId>commons-codec</dep:artifactId>
> >>> <dep:version>1.3</dep:version>
> >>> <dep:type>jar</dep:type>
> >>> </dep:dependency>
> >>>
> >>> <dep:dependency>
> >>> <dep:groupId>commons-httpclient</dep:groupId>
> >>> <dep:artifactId>commons-httpclient</dep:artifactId>
> >>> <dep:version>3.0</dep:version>
> >>> <dep:type>jar</dep:type>
> >>> </dep:dependency>
> >>>
> >>> <dep:dependency>
> >>> <dep:groupId>commons-fileupload</dep:groupId>
> >>> <dep:artifactId>commons-fileupload</dep:artifactId>
> >>> <dep:version>1.0</dep:version>
> >>> <dep:type>jar</dep:type>
> >>> </dep:dependency>
> >>> </dep:dependencies>
> >>>
> >>> <dep:hidden-classes/>
> >>> <dep:non-overridable-classes/>
> >>>
> >>> </dep:environment>
> >>>
> >>> <context-root>/CODERESEARCH.client/ei-service</context-root>
> >>>
> >>> <naming:resource-ref>
> >>> <naming:ref-name>jdbc/default</naming:ref-name>
> >>> <naming:resource-link>jdbc/default</naming:resource-link>
> >>> </naming:resource-ref>
> >>>
> >>> </web-app>
> >>>
> >>>
> >>>
> >>> and the web.xml:
> >>>
> >>> <?xml version="1.0" encoding="ISO-8859-1"?>
> >>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> >>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> >>> version="2.4">
> >>>
> >>> <servlet>
> >>> <display-name>MainServlet</display-name>
> >>> <servlet-name>MainServlet</servlet-name>
> >>>
> >>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
> >>>
> >>> <load-on-startup>1</load-on-startup>
> >>> </servlet>
> >>>
> >>> <servlet-mapping>
> >>> <servlet-name>MainServlet</servlet-name>
> >>> <url-pattern>/*</url-pattern>
> >>> </servlet-mapping>
> >>>
> >>> <env-entry>
> >>> <env-entry-name>server/ServerType</env-entry-name>
> >>> <env-entry-type>java.lang.String</env-entry-type>
> >>> <env-entry-value>Geronimo/Jetty</env-entry-value>
> >>> </env-entry>
> >>>
> >>> <resource-ref>
> >>> <res-ref-name>jdbc/default</res-ref-name>
> >>> <res-type>javax.sql.DataSource</res-type>
> >>> <res-auth>Container</res-auth>
> >>> <res-sharing-scope>Shareable</res-sharing-scope>
> >>> </resource-ref>
> >>>
> >>> </web-app>
> >>>
> >>>
> >>> and the db deploy plan:
> >>>
> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
> >>> <dep:environment
> >>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
> >>> <dep:moduleId>
> >>> <dep:groupId>coderesearch-jdbc</dep:groupId>
> >>> <dep:artifactId>ei-service-default</dep:artifactId>
> >>> <dep:version>2.3</dep:version>
> >>> <dep:type>rar</dep:type>
> >>> </dep:moduleId>
> >>> <dep:dependencies>
> >>> <dep:dependency>
> >>> <dep:groupId>postgresql</dep:groupId>
> >>> <dep:artifactId>postgresql</dep:artifactId>
> >>> <dep:version>8.1.jdbc3</dep:version>
> >>> <dep:type>jar</dep:type>
> >>> </dep:dependency>
> >>> </dep:dependencies>
> >>> </dep:environment>
> >>>
> >>> <resourceadapter>
> >>> <outbound-resourceadapter>
> >>> <connection-definition>
> >>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
> >>>
> >>> <connectiondefinition-instance>
> >>> <name>jdbc/default</name>
> >>> <config-property-setting
> >>> name="UserName">admin</config-property-setting>
> >>> <config-property-setting
> >>> name="Password">master</config-property-setting>
> >>> <config-property-setting
> >>> name="Driver">org.postgresql.Driver</config-property-setting>
> >>> <config-property-setting
> >>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
> >>>
> >>> <config-property-setting
> >>> name="CommitBeforeAutocommit">true</config-property-setting>
> >>> <connectionmanager>
> >>> <local-transaction/>
> >>> <single-pool>
> >>> <max-size>10</max-size>
> >>> <min-size>5</min-size>
> >>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
> >>>
> >>> <idle-timeout-minutes>60</idle-timeout-minutes>
> >>> <match-one/>
> >>> </single-pool>
> >>> </connectionmanager>
> >>> </connectiondefinition-instance>
> >>> </connection-definition>
> >>> </outbound-resourceadapter>
> >>> </resourceadapter>
> >>> </connector>
> >>
> >>
> >
>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
Any new ideas about the problem?
Thanks,
Mario
Mario Rübsam wrote:
> David Jencks wrote:
>> What happens if you change both this and the moduleId in the rar plan
>> to type car?
>>> <dep:dependency>
>>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>> <dep:artifactId>ei-service-default</dep:artifactId>
>>> <dep:version>2.3</dep:version>
>>> <dep:type>rar</dep:type>
>>> </dep:dependency>
>
> changed it to "car" but still no luck, I used the "rar" because the console
> wizard uses "rar" too
>
>> It should work the way you have it.... but we might have some
>> hardcoded assumptions about car left.
>
> I get the same error message when I remove the dependency. I tried
> it also with or without the version and type. Always the same message.
> The db pool is deployed without problems I also checked the repository
> structure for the db rar/car.
>
> Thanks,
> Mario
>
>
>> should have type car
>> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>>
>>> Hi,
>>>
>>> with the current release candidate I still have problems
>>> linking to the deployed datasource. My dependencies should
>>> match the examples from the web console but still no
>>> luck when deploying.
>>>
>>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>>> Error: Unable to distribute eiservice.ear: Unable to resolve
>>> resource reference 'jdbc/default' (Could not find resource
>>> 'jdbc/default'. Perhaps it has not yet been configured, or your
>>> application does not have a dependency declared for that resource
>>> module?)
>>>
>>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>>>
>>> Thanks,
>>> Mario
>>>
>>>
>>> here the geronimo-web.xml:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>>>
>>> <dep:environment
>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>>> <dep:moduleId>
>>> <dep:groupId>coderesearch</dep:groupId>
>>> <dep:artifactId>ei-service</dep:artifactId>
>>> <dep:version>2.3</dep:version>
>>> <dep:type>war</dep:type>
>>> </dep:moduleId>
>>>
>>> <dep:dependencies>
>>> <dep:dependency>
>>> <dep:groupId>coderesearch</dep:groupId>
>>> <dep:artifactId>ei-service</dep:artifactId>
>>> <dep:version>2.3</dep:version>
>>> <dep:type>car</dep:type>
>>> </dep:dependency>
>>>
>>> <dep:dependency>
>>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>> <dep:artifactId>ei-service-default</dep:artifactId>
>>> <dep:version>2.3</dep:version>
>>> <dep:type>rar</dep:type>
>>> </dep:dependency>
>>>
>>> <dep:dependency>
>>> <dep:groupId>commons-email</dep:groupId>
>>> <dep:artifactId>commons-email</dep:artifactId>
>>> <dep:version>1.0</dep:version>
>>> <dep:type>jar</dep:type>
>>> </dep:dependency>
>>>
>>> <dep:dependency>
>>> <dep:groupId>commons-codec</dep:groupId>
>>> <dep:artifactId>commons-codec</dep:artifactId>
>>> <dep:version>1.3</dep:version>
>>> <dep:type>jar</dep:type>
>>> </dep:dependency>
>>>
>>> <dep:dependency>
>>> <dep:groupId>commons-httpclient</dep:groupId>
>>> <dep:artifactId>commons-httpclient</dep:artifactId>
>>> <dep:version>3.0</dep:version>
>>> <dep:type>jar</dep:type>
>>> </dep:dependency>
>>>
>>> <dep:dependency>
>>> <dep:groupId>commons-fileupload</dep:groupId>
>>> <dep:artifactId>commons-fileupload</dep:artifactId>
>>> <dep:version>1.0</dep:version>
>>> <dep:type>jar</dep:type>
>>> </dep:dependency>
>>> </dep:dependencies>
>>>
>>> <dep:hidden-classes/>
>>> <dep:non-overridable-classes/>
>>>
>>> </dep:environment>
>>>
>>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>>>
>>> <naming:resource-ref>
>>> <naming:ref-name>jdbc/default</naming:ref-name>
>>> <naming:resource-link>jdbc/default</naming:resource-link>
>>> </naming:resource-ref>
>>>
>>> </web-app>
>>>
>>>
>>>
>>> and the web.xml:
>>>
>>> <?xml version="1.0" encoding="ISO-8859-1"?>
>>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>> version="2.4">
>>>
>>> <servlet>
>>> <display-name>MainServlet</display-name>
>>> <servlet-name>MainServlet</servlet-name>
>>>
>>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>>>
>>> <load-on-startup>1</load-on-startup>
>>> </servlet>
>>>
>>> <servlet-mapping>
>>> <servlet-name>MainServlet</servlet-name>
>>> <url-pattern>/*</url-pattern>
>>> </servlet-mapping>
>>>
>>> <env-entry>
>>> <env-entry-name>server/ServerType</env-entry-name>
>>> <env-entry-type>java.lang.String</env-entry-type>
>>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>>> </env-entry>
>>>
>>> <resource-ref>
>>> <res-ref-name>jdbc/default</res-ref-name>
>>> <res-type>javax.sql.DataSource</res-type>
>>> <res-auth>Container</res-auth>
>>> <res-sharing-scope>Shareable</res-sharing-scope>
>>> </resource-ref>
>>>
>>> </web-app>
>>>
>>>
>>> and the db deploy plan:
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>>> <dep:environment
>>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>>> <dep:moduleId>
>>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>>> <dep:artifactId>ei-service-default</dep:artifactId>
>>> <dep:version>2.3</dep:version>
>>> <dep:type>rar</dep:type>
>>> </dep:moduleId>
>>> <dep:dependencies>
>>> <dep:dependency>
>>> <dep:groupId>postgresql</dep:groupId>
>>> <dep:artifactId>postgresql</dep:artifactId>
>>> <dep:version>8.1.jdbc3</dep:version>
>>> <dep:type>jar</dep:type>
>>> </dep:dependency>
>>> </dep:dependencies>
>>> </dep:environment>
>>>
>>> <resourceadapter>
>>> <outbound-resourceadapter>
>>> <connection-definition>
>>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>>
>>> <connectiondefinition-instance>
>>> <name>jdbc/default</name>
>>> <config-property-setting
>>> name="UserName">admin</config-property-setting>
>>> <config-property-setting
>>> name="Password">master</config-property-setting>
>>> <config-property-setting
>>> name="Driver">org.postgresql.Driver</config-property-setting>
>>> <config-property-setting
>>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>>
>>> <config-property-setting
>>> name="CommitBeforeAutocommit">true</config-property-setting>
>>> <connectionmanager>
>>> <local-transaction/>
>>> <single-pool>
>>> <max-size>10</max-size>
>>> <min-size>5</min-size>
>>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>>>
>>> <idle-timeout-minutes>60</idle-timeout-minutes>
>>> <match-one/>
>>> </single-pool>
>>> </connectionmanager>
>>> </connectiondefinition-instance>
>>> </connection-definition>
>>> </outbound-resourceadapter>
>>> </resourceadapter>
>>> </connector>
>>
>>
>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
David Jencks wrote:
> What happens if you change both this and the moduleId in the rar plan to
> type car?
>> <dep:dependency>
>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> <dep:artifactId>ei-service-default</dep:artifactId>
>> <dep:version>2.3</dep:version>
>> <dep:type>rar</dep:type>
>> </dep:dependency>
changed it to "car" but still no luck, I used the "rar" because the console
wizard uses "rar" too
> It should work the way you have it.... but we might have some hardcoded
> assumptions about car left.
I get the same error message when I remove the dependency. I tried
it also with or without the version and type. Always the same message.
The db pool is deployed without problems I also checked the repository
structure for the db rar/car.
Thanks,
Mario
> should have type car
> On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
>
>> Hi,
>>
>> with the current release candidate I still have problems
>> linking to the deployed datasource. My dependencies should
>> match the examples from the web console but still no
>> luck when deploying.
>>
>> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
>> Error: Unable to distribute eiservice.ear: Unable to resolve
>> resource reference 'jdbc/default' (Could not find resource
>> 'jdbc/default'. Perhaps it has not yet been configured, or your
>> application does not have a dependency declared for that resource
>> module?)
>>
>> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>>
>> Thanks,
>> Mario
>>
>>
>> here the geronimo-web.xml:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
>> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>>
>> <dep:environment
>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> <dep:moduleId>
>> <dep:groupId>coderesearch</dep:groupId>
>> <dep:artifactId>ei-service</dep:artifactId>
>> <dep:version>2.3</dep:version>
>> <dep:type>war</dep:type>
>> </dep:moduleId>
>>
>> <dep:dependencies>
>> <dep:dependency>
>> <dep:groupId>coderesearch</dep:groupId>
>> <dep:artifactId>ei-service</dep:artifactId>
>> <dep:version>2.3</dep:version>
>> <dep:type>car</dep:type>
>> </dep:dependency>
>>
>> <dep:dependency>
>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> <dep:artifactId>ei-service-default</dep:artifactId>
>> <dep:version>2.3</dep:version>
>> <dep:type>rar</dep:type>
>> </dep:dependency>
>>
>> <dep:dependency>
>> <dep:groupId>commons-email</dep:groupId>
>> <dep:artifactId>commons-email</dep:artifactId>
>> <dep:version>1.0</dep:version>
>> <dep:type>jar</dep:type>
>> </dep:dependency>
>>
>> <dep:dependency>
>> <dep:groupId>commons-codec</dep:groupId>
>> <dep:artifactId>commons-codec</dep:artifactId>
>> <dep:version>1.3</dep:version>
>> <dep:type>jar</dep:type>
>> </dep:dependency>
>>
>> <dep:dependency>
>> <dep:groupId>commons-httpclient</dep:groupId>
>> <dep:artifactId>commons-httpclient</dep:artifactId>
>> <dep:version>3.0</dep:version>
>> <dep:type>jar</dep:type>
>> </dep:dependency>
>>
>> <dep:dependency>
>> <dep:groupId>commons-fileupload</dep:groupId>
>> <dep:artifactId>commons-fileupload</dep:artifactId>
>> <dep:version>1.0</dep:version>
>> <dep:type>jar</dep:type>
>> </dep:dependency>
>> </dep:dependencies>
>>
>> <dep:hidden-classes/>
>> <dep:non-overridable-classes/>
>>
>> </dep:environment>
>>
>> <context-root>/CODERESEARCH.client/ei-service</context-root>
>>
>> <naming:resource-ref>
>> <naming:ref-name>jdbc/default</naming:ref-name>
>> <naming:resource-link>jdbc/default</naming:resource-link>
>> </naming:resource-ref>
>>
>> </web-app>
>>
>>
>>
>> and the web.xml:
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>> version="2.4">
>>
>> <servlet>
>> <display-name>MainServlet</display-name>
>> <servlet-name>MainServlet</servlet-name>
>>
>> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
>> <load-on-startup>1</load-on-startup>
>> </servlet>
>>
>> <servlet-mapping>
>> <servlet-name>MainServlet</servlet-name>
>> <url-pattern>/*</url-pattern>
>> </servlet-mapping>
>>
>> <env-entry>
>> <env-entry-name>server/ServerType</env-entry-name>
>> <env-entry-type>java.lang.String</env-entry-type>
>> <env-entry-value>Geronimo/Jetty</env-entry-value>
>> </env-entry>
>>
>> <resource-ref>
>> <res-ref-name>jdbc/default</res-ref-name>
>> <res-type>javax.sql.DataSource</res-type>
>> <res-auth>Container</res-auth>
>> <res-sharing-scope>Shareable</res-sharing-scope>
>> </resource-ref>
>>
>> </web-app>
>>
>>
>> and the db deploy plan:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
>> <dep:environment
>> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
>> <dep:moduleId>
>> <dep:groupId>coderesearch-jdbc</dep:groupId>
>> <dep:artifactId>ei-service-default</dep:artifactId>
>> <dep:version>2.3</dep:version>
>> <dep:type>rar</dep:type>
>> </dep:moduleId>
>> <dep:dependencies>
>> <dep:dependency>
>> <dep:groupId>postgresql</dep:groupId>
>> <dep:artifactId>postgresql</dep:artifactId>
>> <dep:version>8.1.jdbc3</dep:version>
>> <dep:type>jar</dep:type>
>> </dep:dependency>
>> </dep:dependencies>
>> </dep:environment>
>>
>> <resourceadapter>
>> <outbound-resourceadapter>
>> <connection-definition>
>> <connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
>>
>> <connectiondefinition-instance>
>> <name>jdbc/default</name>
>> <config-property-setting
>> name="UserName">admin</config-property-setting>
>> <config-property-setting
>> name="Password">master</config-property-setting>
>> <config-property-setting
>> name="Driver">org.postgresql.Driver</config-property-setting>
>> <config-property-setting
>> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
>>
>> <config-property-setting
>> name="CommitBeforeAutocommit">true</config-property-setting>
>> <connectionmanager>
>> <local-transaction/>
>> <single-pool>
>> <max-size>10</max-size>
>> <min-size>5</min-size>
>> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
>>
>> <idle-timeout-minutes>60</idle-timeout-minutes>
>> <match-one/>
>> </single-pool>
>> </connectionmanager>
>> </connectiondefinition-instance>
>> </connection-definition>
>> </outbound-resourceadapter>
>> </resourceadapter>
>> </connector>
>
>
Re: 1.1-rc1 deployment
Posted by David Jencks <da...@yahoo.com>.
What happens if you change both this and the moduleId in the rar plan
to type car?
> <dep:dependency>
> <dep:groupId>coderesearch-jdbc</dep:groupId>
> <dep:artifactId>ei-service-default</dep:artifactId>
> <dep:version>2.3</dep:version>
> <dep:type>rar</dep:type>
> </dep:dependency>
It should work the way you have it.... but we might have some
hardcoded assumptions about car left.
thanks
david jencks
should have type car
On Jun 12, 2006, at 4:11 AM, Mario Rübsam wrote:
> Hi,
>
> with the current release candidate I still have problems
> linking to the deployed datasource. My dependencies should
> match the examples from the web console but still no
> luck when deploying.
>
> Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
> Error: Unable to distribute eiservice.ear: Unable to resolve
> resource reference 'jdbc/default' (Could not find resource
> 'jdbc/default'. Perhaps it has not yet been configured, or your
> application does not have a dependency declared for that resource
> module?)
>
> What I'm doing wrong in with 1.1? It worked all fine in 1.0
>
> Thanks,
> Mario
>
>
> here the geronimo-web.xml:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
> xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
>
> <dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/
> deployment-1.1">
> <dep:moduleId>
> <dep:groupId>coderesearch</dep:groupId>
> <dep:artifactId>ei-service</dep:artifactId>
> <dep:version>2.3</dep:version>
> <dep:type>war</dep:type>
> </dep:moduleId>
>
> <dep:dependencies>
> <dep:dependency>
> <dep:groupId>coderesearch</dep:groupId>
> <dep:artifactId>ei-service</dep:artifactId>
> <dep:version>2.3</dep:version>
> <dep:type>car</dep:type>
> </dep:dependency>
>
> <dep:dependency>
> <dep:groupId>coderesearch-jdbc</dep:groupId>
> <dep:artifactId>ei-service-default</dep:artifactId>
> <dep:version>2.3</dep:version>
> <dep:type>rar</dep:type>
> </dep:dependency>
>
> <dep:dependency>
> <dep:groupId>commons-email</dep:groupId>
> <dep:artifactId>commons-email</dep:artifactId>
> <dep:version>1.0</dep:version>
> <dep:type>jar</dep:type>
> </dep:dependency>
>
> <dep:dependency>
> <dep:groupId>commons-codec</dep:groupId>
> <dep:artifactId>commons-codec</dep:artifactId>
> <dep:version>1.3</dep:version>
> <dep:type>jar</dep:type>
> </dep:dependency>
>
> <dep:dependency>
> <dep:groupId>commons-httpclient</dep:groupId>
> <dep:artifactId>commons-httpclient</dep:artifactId>
> <dep:version>3.0</dep:version>
> <dep:type>jar</dep:type>
> </dep:dependency>
>
> <dep:dependency>
> <dep:groupId>commons-fileupload</dep:groupId>
> <dep:artifactId>commons-fileupload</dep:artifactId>
> <dep:version>1.0</dep:version>
> <dep:type>jar</dep:type>
> </dep:dependency>
> </dep:dependencies>
>
> <dep:hidden-classes/>
> <dep:non-overridable-classes/>
>
> </dep:environment>
>
> <context-root>/CODERESEARCH.client/ei-service</context-root>
>
> <naming:resource-ref>
> <naming:ref-name>jdbc/default</naming:ref-name>
> <naming:resource-link>jdbc/default</naming:resource-link>
> </naming:resource-ref>
>
> </web-app>
>
>
>
> and the web.xml:
>
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
> version="2.4">
>
> <servlet>
> <display-name>MainServlet</display-name>
> <servlet-name>MainServlet</servlet-name>
> <servlet-class>com.coderesearch.abp.found.srv.MainServlet</
> servlet-class>
> <load-on-startup>1</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>MainServlet</servlet-name>
> <url-pattern>/*</url-pattern>
> </servlet-mapping>
>
> <env-entry>
> <env-entry-name>server/ServerType</env-entry-name>
> <env-entry-type>java.lang.String</env-entry-type>
> <env-entry-value>Geronimo/Jetty</env-entry-value>
> </env-entry>
>
> <resource-ref>
> <res-ref-name>jdbc/default</res-ref-name>
> <res-type>javax.sql.DataSource</res-type>
> <res-auth>Container</res-auth>
> <res-sharing-scope>Shareable</res-sharing-scope>
> </resource-ref>
>
> </web-app>
>
>
> and the db deploy plan:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/
> connector-1.1">
> <dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/
> deployment-1.1">
> <dep:moduleId>
> <dep:groupId>coderesearch-jdbc</dep:groupId>
> <dep:artifactId>ei-service-default</dep:artifactId>
> <dep:version>2.3</dep:version>
> <dep:type>rar</dep:type>
> </dep:moduleId>
> <dep:dependencies>
> <dep:dependency>
> <dep:groupId>postgresql</dep:groupId>
> <dep:artifactId>postgresql</dep:artifactId>
> <dep:version>8.1.jdbc3</dep:version>
> <dep:type>jar</dep:type>
> </dep:dependency>
> </dep:dependencies>
> </dep:environment>
>
> <resourceadapter>
> <outbound-resourceadapter>
> <connection-definition>
> <connectionfactory-interface>javax.sql.DataSource</
> connectionfactory-interface>
> <connectiondefinition-instance>
> <name>jdbc/default</name>
> <config-property-setting name="UserName">admin</
> config-property-setting>
> <config-property-setting
> name="Password">master</config-property-setting>
> <config-property-setting
> name="Driver">org.postgresql.Driver</config-property-setting>
> <config-property-setting
> name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</
> config-property-setting>
> <config-property-setting
> name="CommitBeforeAutocommit">true</config-property-setting>
> <connectionmanager>
> <local-transaction/>
> <single-pool>
> <max-size>10</max-size>
> <min-size>5</min-size>
> <blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
> <idle-timeout-minutes>60</idle-timeout-
> minutes>
> <match-one/>
> </single-pool>
> </connectionmanager>
> </connectiondefinition-instance>
> </connection-definition>
> </outbound-resourceadapter>
> </resourceadapter>
> </connector>
Re: 1.1-rc1 deployment
Posted by Mario Rübsam <mr...@coderesearch.com>.
Hi,
with the current release candidate I still have problems
linking to the deployed datasource. My dependencies should
match the examples from the web console but still no
luck when deploying.
Using JRE_HOME: d:\opt\sdk\j2sdk-1.4.2
Error: Unable to distribute eiservice.ear: Unable to resolve
resource reference 'jdbc/default' (Could not find resource
'jdbc/default'. Perhaps it has not yet been configured, or your
application does not have a dependency declared for that resource
module?)
What I'm doing wrong in with 1.1? It worked all fine in 1.0
Thanks,
Mario
here the geronimo-web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1"
xmlns:naming="http://geronimo.apache.org/xml/ns/naming">
<dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
<dep:moduleId>
<dep:groupId>coderesearch</dep:groupId>
<dep:artifactId>ei-service</dep:artifactId>
<dep:version>2.3</dep:version>
<dep:type>war</dep:type>
</dep:moduleId>
<dep:dependencies>
<dep:dependency>
<dep:groupId>coderesearch</dep:groupId>
<dep:artifactId>ei-service</dep:artifactId>
<dep:version>2.3</dep:version>
<dep:type>car</dep:type>
</dep:dependency>
<dep:dependency>
<dep:groupId>coderesearch-jdbc</dep:groupId>
<dep:artifactId>ei-service-default</dep:artifactId>
<dep:version>2.3</dep:version>
<dep:type>rar</dep:type>
</dep:dependency>
<dep:dependency>
<dep:groupId>commons-email</dep:groupId>
<dep:artifactId>commons-email</dep:artifactId>
<dep:version>1.0</dep:version>
<dep:type>jar</dep:type>
</dep:dependency>
<dep:dependency>
<dep:groupId>commons-codec</dep:groupId>
<dep:artifactId>commons-codec</dep:artifactId>
<dep:version>1.3</dep:version>
<dep:type>jar</dep:type>
</dep:dependency>
<dep:dependency>
<dep:groupId>commons-httpclient</dep:groupId>
<dep:artifactId>commons-httpclient</dep:artifactId>
<dep:version>3.0</dep:version>
<dep:type>jar</dep:type>
</dep:dependency>
<dep:dependency>
<dep:groupId>commons-fileupload</dep:groupId>
<dep:artifactId>commons-fileupload</dep:artifactId>
<dep:version>1.0</dep:version>
<dep:type>jar</dep:type>
</dep:dependency>
</dep:dependencies>
<dep:hidden-classes/>
<dep:non-overridable-classes/>
</dep:environment>
<context-root>/CODERESEARCH.client/ei-service</context-root>
<naming:resource-ref>
<naming:ref-name>jdbc/default</naming:ref-name>
<naming:resource-link>jdbc/default</naming:resource-link>
</naming:resource-ref>
</web-app>
and the web.xml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<servlet>
<display-name>MainServlet</display-name>
<servlet-name>MainServlet</servlet-name>
<servlet-class>com.coderesearch.abp.found.srv.MainServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>MainServlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
<env-entry>
<env-entry-name>server/ServerType</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>Geronimo/Jetty</env-entry-value>
</env-entry>
<resource-ref>
<res-ref-name>jdbc/default</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</web-app>
and the db deploy plan:
<?xml version="1.0" encoding="UTF-8"?>
<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.1">
<dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.1">
<dep:moduleId>
<dep:groupId>coderesearch-jdbc</dep:groupId>
<dep:artifactId>ei-service-default</dep:artifactId>
<dep:version>2.3</dep:version>
<dep:type>rar</dep:type>
</dep:moduleId>
<dep:dependencies>
<dep:dependency>
<dep:groupId>postgresql</dep:groupId>
<dep:artifactId>postgresql</dep:artifactId>
<dep:version>8.1.jdbc3</dep:version>
<dep:type>jar</dep:type>
</dep:dependency>
</dep:dependencies>
</dep:environment>
<resourceadapter>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.sql.DataSource</connectionfactory-interface>
<connectiondefinition-instance>
<name>jdbc/default</name>
<config-property-setting
name="UserName">admin</config-property-setting>
<config-property-setting
name="Password">master</config-property-setting>
<config-property-setting
name="Driver">org.postgresql.Driver</config-property-setting>
<config-property-setting
name="ConnectionURL">jdbc:postgresql://localhost:5432/eiservice</config-property-setting>
<config-property-setting
name="CommitBeforeAutocommit">true</config-property-setting>
<connectionmanager>
<local-transaction/>
<single-pool>
<max-size>10</max-size>
<min-size>5</min-size>
<blocking-timeout-milliseconds>60000</blocking-timeout-milliseconds>
<idle-timeout-minutes>60</idle-timeout-minutes>
<match-one/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
</connector>
Re: 1.1-rc1 Now Available
Posted by Hiram Chirino <hi...@hiramchirino.com>.
Hey..
3.2.4 Should be up now on the codehaus repo.
On 6/12/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
> I talked with Hiram tonight (before catching up on e-mail so I hadn't seen this note) about getting
> 3.2.4 closed out. Apparently the Codehaus outage left AMQ in an indeterminent state. We've tested
> the existing 3.2.4-SNAPSHOT against CTS. I would prefer to close out AMQ 3.2.4 as is and fix this
> for 1.1.1. Small changes can set us back several days if there is some secondary effect.
>
> Aaron Mulder wrote:
> > As far as I know, the patch is valid, it just needs to be applied to a
> > different module than it was created against. I'm not sure if we're
> > waiting for this for the release or not. I had hoped it would go in.
> > Hiram, do you want to look at it or do you want me to?
> >
> > Thanks,
> > Aaron
> >
> > On 6/12/06, John Sisson <jr...@gmail.com> wrote:
> >> I thought that we were waiting for
> >> http://issues.apache.org/jira/browse/GERONIMO-1451 to be fixed.
> >>
> >> Aaron and Hiram do you know what is happening here?
> >>
> >> John
> >>
> >> Kevan Miller wrote:
> >> > My first response went to the user list. I'm repeating on dev...
> >> >
> >> > ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
> >> > ActiveMQ 3.2.4-SNAPSHOT in our repository. What's the plan, there?
> >> >
> >> > I don't think we can release until ActiveMQ has released... Is there
> >> > some problem?
> >> >
> >> > --kevan
> >> >
> >> > On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
> >> >
> >> >> Over the past few days the outstanding issues that were raised about
> >> >> the first candidate have been addressed.
> >> >>
> >> >> They were that we were missing the LICENSE.txt as well as Notices
> >> >> from the distribution. I added them. Guillaume also pointed out
> >> >> that he noted that there should be a Third Party Notices. This was
> >> >> not included in the original 1.0 or previous distributions so I did
> >> >> not follow it up. Thoughts?
> >> >>
> >> >> Also, the 1.0 release notes were removed and updated the thread
> >> >> started by Hernan. The Wiki has been updated and the wiki was the
> >> >> source used to create the RELEASE-NOTES-1.1.txt file you will find in
> >> >> the build.
> >> >>
> >> >> To avoid issues with the version number and the plugins I used rc1
> >> >> which Aaron had added in the plugins for supported versions so I
> >> >> trust that works here.
> >> >>
> >> >> JSisson addressed the problem with not being able to run Geronimo
> >> >> under CygWin and Kevan worked with Aaron to address a new deployment
> >> >> problem that left partially deployed artifacts in the repository.
> >> >>
> >> >> I have taken this build and run some performance tests on it and we
> >> >> are significantly better in 1.1 than we were in 1.0. We have a lot
> >> >> of improvement left for CMP EJBs. It appears that the performance
> >> >> improvements in the EJB tier has changed a race condition when
> >> >> running under DB2. I'm afraid that the only way to address the
> >> >> problem is to add a new feature to TranQL and OEJB that allow for the
> >> >> specification of Isolation Levels for individual beans. This is a
> >> >> relatively simple change but the build as it stands is specification
> >> >> compliant. I would prefer to let this release go forward since CMP
> >> >> 2.1 EJBs are not nearly as common as the other J2EE components. I
> >> >> would like to address this in 1.1.1 however I don't think we've
> >> >> locked down whether that would be allowed or not. The change would
> >> >> affect TranQL and OpenEJB so they are really included components so
> >> >> I'd be interested in people's feedback.
> >> >>
> >> >> So please accept a named RC1. Your voting and feedback are for:
> >> >>
> >> >> Geronimo 1.1
> >> >> DayTrader 1.1
> >> >> Specs 1.1
> >> >>
> >> >> The vote will stand for 72 hours. Issues raised will be discussed
> >> >> and if we conclude that there is a bug that must be addressed then we
> >> >> will mitigate the problem and respin a new rc for a 72 hour vote.
> >> >>
> >> >> If this is accepted all three of the above components will be
> >> >> released simultaneously.
> >> >>
> >> >> Here are the builds for your review and comment:
> >> >>
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> >> >>
> >> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> >>
> >> >>
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
> >>
> >> >>
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> >> >>
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
> >>
> >> >>
> >> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
> >>
> >> >>
> >> >>
> >> >> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
> >> >>
> >> >>
> >> >> Looking forward to your comments and feedback.
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
> >
>
--
Regards,
Hiram
Re: 1.1-rc1 Now Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I talked with Hiram tonight (before catching up on e-mail so I hadn't seen this note) about getting
3.2.4 closed out. Apparently the Codehaus outage left AMQ in an indeterminent state. We've tested
the existing 3.2.4-SNAPSHOT against CTS. I would prefer to close out AMQ 3.2.4 as is and fix this
for 1.1.1. Small changes can set us back several days if there is some secondary effect.
Aaron Mulder wrote:
> As far as I know, the patch is valid, it just needs to be applied to a
> different module than it was created against. I'm not sure if we're
> waiting for this for the release or not. I had hoped it would go in.
> Hiram, do you want to look at it or do you want me to?
>
> Thanks,
> Aaron
>
> On 6/12/06, John Sisson <jr...@gmail.com> wrote:
>> I thought that we were waiting for
>> http://issues.apache.org/jira/browse/GERONIMO-1451 to be fixed.
>>
>> Aaron and Hiram do you know what is happening here?
>>
>> John
>>
>> Kevan Miller wrote:
>> > My first response went to the user list. I'm repeating on dev...
>> >
>> > ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
>> > ActiveMQ 3.2.4-SNAPSHOT in our repository. What's the plan, there?
>> >
>> > I don't think we can release until ActiveMQ has released... Is there
>> > some problem?
>> >
>> > --kevan
>> >
>> > On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
>> >
>> >> Over the past few days the outstanding issues that were raised about
>> >> the first candidate have been addressed.
>> >>
>> >> They were that we were missing the LICENSE.txt as well as Notices
>> >> from the distribution. I added them. Guillaume also pointed out
>> >> that he noted that there should be a Third Party Notices. This was
>> >> not included in the original 1.0 or previous distributions so I did
>> >> not follow it up. Thoughts?
>> >>
>> >> Also, the 1.0 release notes were removed and updated the thread
>> >> started by Hernan. The Wiki has been updated and the wiki was the
>> >> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>> >> the build.
>> >>
>> >> To avoid issues with the version number and the plugins I used rc1
>> >> which Aaron had added in the plugins for supported versions so I
>> >> trust that works here.
>> >>
>> >> JSisson addressed the problem with not being able to run Geronimo
>> >> under CygWin and Kevan worked with Aaron to address a new deployment
>> >> problem that left partially deployed artifacts in the repository.
>> >>
>> >> I have taken this build and run some performance tests on it and we
>> >> are significantly better in 1.1 than we were in 1.0. We have a lot
>> >> of improvement left for CMP EJBs. It appears that the performance
>> >> improvements in the EJB tier has changed a race condition when
>> >> running under DB2. I'm afraid that the only way to address the
>> >> problem is to add a new feature to TranQL and OEJB that allow for the
>> >> specification of Isolation Levels for individual beans. This is a
>> >> relatively simple change but the build as it stands is specification
>> >> compliant. I would prefer to let this release go forward since CMP
>> >> 2.1 EJBs are not nearly as common as the other J2EE components. I
>> >> would like to address this in 1.1.1 however I don't think we've
>> >> locked down whether that would be allowed or not. The change would
>> >> affect TranQL and OpenEJB so they are really included components so
>> >> I'd be interested in people's feedback.
>> >>
>> >> So please accept a named RC1. Your voting and feedback are for:
>> >>
>> >> Geronimo 1.1
>> >> DayTrader 1.1
>> >> Specs 1.1
>> >>
>> >> The vote will stand for 72 hours. Issues raised will be discussed
>> >> and if we conclude that there is a bug that must be addressed then we
>> >> will mitigate the problem and respin a new rc for a 72 hour vote.
>> >>
>> >> If this is accepted all three of the above components will be
>> >> released simultaneously.
>> >>
>> >> Here are the builds for your review and comment:
>> >>
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>> >>
>> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>
>> >>
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>
>> >>
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>> >>
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>
>> >>
>> >>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>
>> >>
>> >>
>> >> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>> >>
>> >>
>> >> Looking forward to your comments and feedback.
>> >>
>> >
>> >
>>
>>
>
>
>
Re: 1.1-rc1 Now Available
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
As far as I know, the patch is valid, it just needs to be applied to a
different module than it was created against. I'm not sure if we're
waiting for this for the release or not. I had hoped it would go in.
Hiram, do you want to look at it or do you want me to?
Thanks,
Aaron
On 6/12/06, John Sisson <jr...@gmail.com> wrote:
> I thought that we were waiting for
> http://issues.apache.org/jira/browse/GERONIMO-1451 to be fixed.
>
> Aaron and Hiram do you know what is happening here?
>
> John
>
> Kevan Miller wrote:
> > My first response went to the user list. I'm repeating on dev...
> >
> > ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
> > ActiveMQ 3.2.4-SNAPSHOT in our repository. What's the plan, there?
> >
> > I don't think we can release until ActiveMQ has released... Is there
> > some problem?
> >
> > --kevan
> >
> > On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
> >
> >> Over the past few days the outstanding issues that were raised about
> >> the first candidate have been addressed.
> >>
> >> They were that we were missing the LICENSE.txt as well as Notices
> >> from the distribution. I added them. Guillaume also pointed out
> >> that he noted that there should be a Third Party Notices. This was
> >> not included in the original 1.0 or previous distributions so I did
> >> not follow it up. Thoughts?
> >>
> >> Also, the 1.0 release notes were removed and updated the thread
> >> started by Hernan. The Wiki has been updated and the wiki was the
> >> source used to create the RELEASE-NOTES-1.1.txt file you will find in
> >> the build.
> >>
> >> To avoid issues with the version number and the plugins I used rc1
> >> which Aaron had added in the plugins for supported versions so I
> >> trust that works here.
> >>
> >> JSisson addressed the problem with not being able to run Geronimo
> >> under CygWin and Kevan worked with Aaron to address a new deployment
> >> problem that left partially deployed artifacts in the repository.
> >>
> >> I have taken this build and run some performance tests on it and we
> >> are significantly better in 1.1 than we were in 1.0. We have a lot
> >> of improvement left for CMP EJBs. It appears that the performance
> >> improvements in the EJB tier has changed a race condition when
> >> running under DB2. I'm afraid that the only way to address the
> >> problem is to add a new feature to TranQL and OEJB that allow for the
> >> specification of Isolation Levels for individual beans. This is a
> >> relatively simple change but the build as it stands is specification
> >> compliant. I would prefer to let this release go forward since CMP
> >> 2.1 EJBs are not nearly as common as the other J2EE components. I
> >> would like to address this in 1.1.1 however I don't think we've
> >> locked down whether that would be allowed or not. The change would
> >> affect TranQL and OpenEJB so they are really included components so
> >> I'd be interested in people's feedback.
> >>
> >> So please accept a named RC1. Your voting and feedback are for:
> >>
> >> Geronimo 1.1
> >> DayTrader 1.1
> >> Specs 1.1
> >>
> >> The vote will stand for 72 hours. Issues raised will be discussed
> >> and if we conclude that there is a bug that must be addressed then we
> >> will mitigate the problem and respin a new rc for a 72 hour vote.
> >>
> >> If this is accepted all three of the above components will be
> >> released simultaneously.
> >>
> >> Here are the builds for your review and comment:
> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> >> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
> >>
> >> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
> >>
> >>
> >> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
> >>
> >>
> >> Looking forward to your comments and feedback.
> >>
> >
> >
>
>
Re: 1.1-rc1 Now Available
Posted by John Sisson <jr...@gmail.com>.
I thought that we were waiting for
http://issues.apache.org/jira/browse/GERONIMO-1451 to be fixed.
Aaron and Hiram do you know what is happening here?
John
Kevan Miller wrote:
> My first response went to the user list. I'm repeating on dev...
>
> ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
> ActiveMQ 3.2.4-SNAPSHOT in our repository. What's the plan, there?
>
> I don't think we can release until ActiveMQ has released... Is there
> some problem?
>
> --kevan
>
> On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
>
>> Over the past few days the outstanding issues that were raised about
>> the first candidate have been addressed.
>>
>> They were that we were missing the LICENSE.txt as well as Notices
>> from the distribution. I added them. Guillaume also pointed out
>> that he noted that there should be a Third Party Notices. This was
>> not included in the original 1.0 or previous distributions so I did
>> not follow it up. Thoughts?
>>
>> Also, the 1.0 release notes were removed and updated the thread
>> started by Hernan. The Wiki has been updated and the wiki was the
>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>> the build.
>>
>> To avoid issues with the version number and the plugins I used rc1
>> which Aaron had added in the plugins for supported versions so I
>> trust that works here.
>>
>> JSisson addressed the problem with not being able to run Geronimo
>> under CygWin and Kevan worked with Aaron to address a new deployment
>> problem that left partially deployed artifacts in the repository.
>>
>> I have taken this build and run some performance tests on it and we
>> are significantly better in 1.1 than we were in 1.0. We have a lot
>> of improvement left for CMP EJBs. It appears that the performance
>> improvements in the EJB tier has changed a race condition when
>> running under DB2. I'm afraid that the only way to address the
>> problem is to add a new feature to TranQL and OEJB that allow for the
>> specification of Isolation Levels for individual beans. This is a
>> relatively simple change but the build as it stands is specification
>> compliant. I would prefer to let this release go forward since CMP
>> 2.1 EJBs are not nearly as common as the other J2EE components. I
>> would like to address this in 1.1.1 however I don't think we've
>> locked down whether that would be allowed or not. The change would
>> affect TranQL and OpenEJB so they are really included components so
>> I'd be interested in people's feedback.
>>
>> So please accept a named RC1. Your voting and feedback are for:
>>
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>>
>> The vote will stand for 72 hours. Issues raised will be discussed
>> and if we conclude that there is a bug that must be addressed then we
>> will mitigate the problem and respin a new rc for a 72 hour vote.
>>
>> If this is accepted all three of the above components will be
>> released simultaneously.
>>
>> Here are the builds for your review and comment:
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>
>>
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>
>>
>> Looking forward to your comments and feedback.
>>
>
>
Re: 1.1-rc1 Now Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
Based on your feedback Kevan I have sent a few notes requesting the release of AMQ to the dev
thread. Perhaps Hiram is not monitoring this thread so I will ping him on this.
Kevan Miller wrote:
> My first response went to the user list. I'm repeating on dev...
>
> ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
> ActiveMQ 3.2.4-SNAPSHOT in our repository. What's the plan, there?
>
> I don't think we can release until ActiveMQ has released... Is there
> some problem?
>
> --kevan
>
> On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
>
>> Over the past few days the outstanding issues that were raised about
>> the first candidate have been addressed.
>>
>> They were that we were missing the LICENSE.txt as well as Notices from
>> the distribution. I added them. Guillaume also pointed out that he
>> noted that there should be a Third Party Notices. This was not
>> included in the original 1.0 or previous distributions so I did not
>> follow it up. Thoughts?
>>
>> Also, the 1.0 release notes were removed and updated the thread
>> started by Hernan. The Wiki has been updated and the wiki was the
>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>> the build.
>>
>> To avoid issues with the version number and the plugins I used rc1
>> which Aaron had added in the plugins for supported versions so I trust
>> that works here.
>>
>> JSisson addressed the problem with not being able to run Geronimo
>> under CygWin and Kevan worked with Aaron to address a new deployment
>> problem that left partially deployed artifacts in the repository.
>>
>> I have taken this build and run some performance tests on it and we
>> are significantly better in 1.1 than we were in 1.0. We have a lot of
>> improvement left for CMP EJBs. It appears that the performance
>> improvements in the EJB tier has changed a race condition when running
>> under DB2. I'm afraid that the only way to address the problem is to
>> add a new feature to TranQL and OEJB that allow for the specification
>> of Isolation Levels for individual beans. This is a relatively simple
>> change but the build as it stands is specification compliant. I would
>> prefer to let this release go forward since CMP 2.1 EJBs are not
>> nearly as common as the other J2EE components. I would like to
>> address this in 1.1.1 however I don't think we've locked down whether
>> that would be allowed or not. The change would affect TranQL and
>> OpenEJB so they are really included components so I'd be interested in
>> people's feedback.
>>
>> So please accept a named RC1. Your voting and feedback are for:
>>
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>>
>> The vote will stand for 72 hours. Issues raised will be discussed and
>> if we conclude that there is a bug that must be addressed then we will
>> mitigate the problem and respin a new rc for a 72 hour vote.
>>
>> If this is accepted all three of the above components will be released
>> simultaneously.
>>
>> Here are the builds for your review and comment:
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>
>>
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>
>>
>> Looking forward to your comments and feedback.
>>
>
>
>
>
Re: 1.1-rc1 Now Available
Posted by Kevan Miller <ke...@gmail.com>.
My first response went to the user list. I'm repeating on dev...
ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
ActiveMQ 3.2.4-SNAPSHOT in our repository. What's the plan, there?
I don't think we can release until ActiveMQ has released... Is there
some problem?
--kevan
On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised
> about the first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices
> from the distribution. I added them. Guillaume also pointed out
> that he noted that there should be a Third Party Notices. This was
> not included in the original 1.0 or previous distributions so I did
> not follow it up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread
> started by Hernan. The Wiki has been updated and the wiki was the
> source used to create the RELEASE-NOTES-1.1.txt file you will find
> in the build.
>
> To avoid issues with the version number and the plugins I used rc1
> which Aaron had added in the plugins for supported versions so I
> trust that works here.
>
> JSisson addressed the problem with not being able to run Geronimo
> under CygWin and Kevan worked with Aaron to address a new
> deployment problem that left partially deployed artifacts in the
> repository.
>
> I have taken this build and run some performance tests on it and we
> are significantly better in 1.1 than we were in 1.0. We have a lot
> of improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when
> running under DB2. I'm afraid that the only way to address the
> problem is to add a new feature to TranQL and OEJB that allow for
> the specification of Isolation Levels for individual beans. This
> is a relatively simple change but the build as it stands is
> specification compliant. I would prefer to let this release go
> forward since CMP 2.1 EJBs are not nearly as common as the other
> J2EE components. I would like to address this in 1.1.1 however I
> don't think we've locked down whether that would be allowed or
> not. The change would affect TranQL and OpenEJB so they are really
> included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed
> and if we conclude that there is a bug that must be addressed then
> we will mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be
> released simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
> rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
> rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
> rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
Re: 1.1-rc1 Now Available
Posted by Kevan Miller <ke...@gmail.com>.
ActiveMQ 3.2.4 hasn't been released yet? I see we're still including
3.2.4-SNAPSHOT in our repository. What's the plan, there?
--kevan
On Jun 11, 2006, at 11:48 PM, Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised
> about the first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices
> from the distribution. I added them. Guillaume also pointed out
> that he noted that there should be a Third Party Notices. This was
> not included in the original 1.0 or previous distributions so I did
> not follow it up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread
> started by Hernan. The Wiki has been updated and the wiki was the
> source used to create the RELEASE-NOTES-1.1.txt file you will find
> in the build.
>
> To avoid issues with the version number and the plugins I used rc1
> which Aaron had added in the plugins for supported versions so I
> trust that works here.
>
> JSisson addressed the problem with not being able to run Geronimo
> under CygWin and Kevan worked with Aaron to address a new
> deployment problem that left partially deployed artifacts in the
> repository.
>
> I have taken this build and run some performance tests on it and we
> are significantly better in 1.1 than we were in 1.0. We have a lot
> of improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when
> running under DB2. I'm afraid that the only way to address the
> problem is to add a new feature to TranQL and OEJB that allow for
> the specification of Isolation Levels for individual beans. This
> is a relatively simple change but the build as it stands is
> specification compliant. I would prefer to let this release go
> forward since CMP 2.1 EJBs are not nearly as common as the other
> J2EE components. I would like to address this in 1.1.1 however I
> don't think we've locked down whether that would be allowed or
> not. The change would affect TranQL and OpenEJB so they are really
> included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed
> and if we conclude that there is a bug that must be addressed then
> we will mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be
> released simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
> rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
> rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
> rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
> rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
Re: [Vote] 1.1-rc1 Now Available
Posted by Dain Sundstrom <da...@iq80.com>.
[Note: this is a duplicate of a post in another thread, but I wanted
to have my vote recorded in the official vote thread.]
I have downloaded and tried out all 4 .tgz files. Here is what I
tested:
o I placed them into the directory /Users/dain/geronimo test/ (note
contains a space)
o Started the servers using server.jar and startup.sh
o Stopped the server using ctrl^c and shutdown.sh
o Installed some of samples (not all) via the install links
o Installed the ldap example via the console plugin
o Stopped/uninstalled service and web modules via the console
o Tailed the geronimo.log file (stuff shows up)
Everything, looks good except the binaries don't contain the
LICENSE.txt file. We should be able to easily fix this in the maven
code, or by hand after the build. For other minor things I found, I
either created a JIRA or started a new thread.
+1 to release the server once the license file is added
-dain
On Jun 12, 2006, at 1:00 PM, Matt Hogstrom wrote:
> I apologize for resending this to the lists. I inadvertantly did
> not put [vote] in the subject line so it may not have been
> apparent. The remainder of this e-mail is the same content that
> was distributed last night.
>
> Matt Hogstrom wrote:
>> Over the past few days the outstanding issues that were raised
>> about the first candidate have been addressed.
>> They were that we were missing the LICENSE.txt as well as Notices
>> from the distribution. I added them. Guillaume also pointed out
>> that he noted that there should be a Third Party Notices. This
>> was not included in the original 1.0 or previous distributions so
>> I did not follow it up. Thoughts?
>> Also, the 1.0 release notes were removed and updated the thread
>> started by Hernan. The Wiki has been updated and the wiki was the
>> source used to create the RELEASE-NOTES-1.1.txt file you will find
>> in the build.
>> To avoid issues with the version number and the plugins I used rc1
>> which Aaron had added in the plugins for supported versions so I
>> trust that works here.
>> JSisson addressed the problem with not being able to run Geronimo
>> under CygWin and Kevan worked with Aaron to address a new
>> deployment problem that left partially deployed artifacts in the
>> repository.
>> I have taken this build and run some performance tests on it and
>> we are significantly better in 1.1 than we were in 1.0. We have a
>> lot of improvement left for CMP EJBs. It appears that the
>> performance improvements in the EJB tier has changed a race
>> condition when running under DB2. I'm afraid that the only way to
>> address the problem is to add a new feature to TranQL and OEJB
>> that allow for the specification of Isolation Levels for
>> individual beans. This is a relatively simple change but the
>> build as it stands is specification compliant. I would prefer to
>> let this release go forward since CMP 2.1 EJBs are not nearly as
>> common as the other J2EE components. I would like to address this
>> in 1.1.1 however I don't think we've locked down whether that
>> would be allowed or not. The change would affect TranQL and
>> OpenEJB so they are really included components so I'd be
>> interested in people's feedback.
>> So please accept a named RC1. Your voting and feedback are for:
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>> The vote will stand for 72 hours. Issues raised will be discussed
>> and if we conclude that there is a bug that must be addressed then
>> we will mitigate the problem and respin a new rc for a 72 hour vote.
>> If this is accepted all three of the above components will be
>> released simultaneously.
>> Here are the builds for your review and comment:
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>> rc1.tar.gz
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>> rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
>> rc1.tar.gz
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
>> rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>> rc1.tar.gz http://people.apache.org/~hogstrom/rc1/geronimo-jetty-
>> minimal-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-
>> rc1.tar.gz http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-
>> minimal-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>> Looking forward to your comments and feedback.
Re: [Vote] 1.1-rc1 Now Available
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Also mentioned in another thread:
Two things:
1. Releases can't be vetoed; they use a consensual vote,
not the '3 +1s and 0 -1s' mechanism.
2. Since a release bears the Apache name, releasing software
is an official act of the Foundation, and as a consequence
only members of the PMC have binding votes. All others
are advisory.
--
#ken P-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer, opinionist http://Apache-Server.Com/
"Millennium hand and shrimp!"
Re: [Vote] 1.1-rc1 Now Available
Posted by Paul McMahan <pa...@gmail.com>.
FYI, a problem with the web access log portlet in the release
candidate was reported on the user list. Turns out this results from
the change in rev 407883 which disables the access logs in the tomcat
assembly. Some issues with the current configuration are:
-- the web access log viewer in the console cannot display
-- the jetty assembly has access logs enabled by default (an inconsistency)
-- the instructions in var/config/config.xml for reenabling access
logs are incorrect
(it says to change load=false to load=true but you actually need to
delete the entire
section added in r407883)
I opened GERONIMO-2110 to track this issue.
thanks,
Paul
On 6/12/06, Matt Hogstrom <ma...@hogstrom.org> wrote:
> I apologize for resending this to the lists. I inadvertantly did not put [vote] in the subject line
> so it may not have been apparent. The remainder of this e-mail is the same content that was
> distributed last night.
>
> Matt Hogstrom wrote:
> > Over the past few days the outstanding issues that were raised about the
> > first candidate have been addressed.
> >
> > They were that we were missing the LICENSE.txt as well as Notices from
> > the distribution. I added them. Guillaume also pointed out that he
> > noted that there should be a Third Party Notices. This was not included
> > in the original 1.0 or previous distributions so I did not follow it
> > up. Thoughts?
> >
> > Also, the 1.0 release notes were removed and updated the thread started
> > by Hernan. The Wiki has been updated and the wiki was the source used
> > to create the RELEASE-NOTES-1.1.txt file you will find in the build.
> >
> > To avoid issues with the version number and the plugins I used rc1 which
> > Aaron had added in the plugins for supported versions so I trust that
> > works here.
> >
> > JSisson addressed the problem with not being able to run Geronimo under
> > CygWin and Kevan worked with Aaron to address a new deployment problem
> > that left partially deployed artifacts in the repository.
> >
> > I have taken this build and run some performance tests on it and we are
> > significantly better in 1.1 than we were in 1.0. We have a lot of
> > improvement left for CMP EJBs. It appears that the performance
> > improvements in the EJB tier has changed a race condition when running
> > under DB2. I'm afraid that the only way to address the problem is to
> > add a new feature to TranQL and OEJB that allow for the specification of
> > Isolation Levels for individual beans. This is a relatively simple
> > change but the build as it stands is specification compliant. I would
> > prefer to let this release go forward since CMP 2.1 EJBs are not nearly
> > as common as the other J2EE components. I would like to address this in
> > 1.1.1 however I don't think we've locked down whether that would be
> > allowed or not. The change would affect TranQL and OpenEJB so they are
> > really included components so I'd be interested in people's feedback.
> >
> > So please accept a named RC1. Your voting and feedback are for:
> >
> > Geronimo 1.1
> > DayTrader 1.1
> > Specs 1.1
> >
> > The vote will stand for 72 hours. Issues raised will be discussed and
> > if we conclude that there is a bug that must be addressed then we will
> > mitigate the problem and respin a new rc for a 72 hour vote.
> >
> > If this is accepted all three of the above components will be released
> > simultaneously.
> >
> > Here are the builds for your review and comment:
> >
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> > http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> > http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
> >
> > http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> > http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
> >
> > http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
> >
> > http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
> >
> >
> > Looking forward to your comments and feedback.
> >
> >
>
Re: [Vote] 1.1-rc1 Now Available
Posted by Kevan Miller <ke...@gmail.com>.
Alan,
Are you asking for Matt to change the subject line of the vote? That
would be appropriate. Something like "[Vote] Release Geronimo 1.1
based on 1.1-rc1"
Or were you not aware of what you were voting on? The note states:
>>> Your voting and feedback are for:
>>>
>>> Geronimo 1.1
>>> DayTrader 1.1
>>> Specs 1.1
--kevan
On Jun 12, 2006, at 7:42 PM, Alan D. Cabrera wrote:
> We vote for release candidates? I don't recall doing that before.
>
> +1
>
>
> Regards,
> Alan
>
>
> Matt Hogstrom wrote:
>> I apologize for resending this to the lists. I inadvertantly did
>> not put [vote] in the subject line so it may not have been
>> apparent. The remainder of this e-mail is the same content that
>> was distributed last night.
>>
>> Matt Hogstrom wrote:
>>> Over the past few days the outstanding issues that were raised
>>> about the first candidate have been addressed.
>>>
>>> They were that we were missing the LICENSE.txt as well as Notices
>>> from the distribution. I added them. Guillaume also pointed out
>>> that he noted that there should be a Third Party Notices. This
>>> was not included in the original 1.0 or previous distributions so
>>> I did not follow it up. Thoughts?
>>>
>>> Also, the 1.0 release notes were removed and updated the thread
>>> started by Hernan. The Wiki has been updated and the wiki was
>>> the source used to create the RELEASE-NOTES-1.1.txt file you will
>>> find in the build.
>>>
>>> To avoid issues with the version number and the plugins I used
>>> rc1 which Aaron had added in the plugins for supported versions
>>> so I trust that works here.
>>>
>>> JSisson addressed the problem with not being able to run Geronimo
>>> under CygWin and Kevan worked with Aaron to address a new
>>> deployment problem that left partially deployed artifacts in the
>>> repository.
>>>
>>> I have taken this build and run some performance tests on it and
>>> we are significantly better in 1.1 than we were in 1.0. We have
>>> a lot of improvement left for CMP EJBs. It appears that the
>>> performance improvements in the EJB tier has changed a race
>>> condition when running under DB2. I'm afraid that the only way
>>> to address the problem is to add a new feature to TranQL and OEJB
>>> that allow for the specification of Isolation Levels for
>>> individual beans. This is a relatively simple change but the
>>> build as it stands is specification compliant. I would prefer to
>>> let this release go forward since CMP 2.1 EJBs are not nearly as
>>> common as the other J2EE components. I would like to address
>>> this in 1.1.1 however I don't think we've locked down whether
>>> that would be allowed or not. The change would affect TranQL and
>>> OpenEJB so they are really included components so I'd be
>>> interested in people's feedback.
>>>
>>> So please accept a named RC1. Your voting and feedback are for:
>>>
>>> Geronimo 1.1
>>> DayTrader 1.1
>>> Specs 1.1
>>>
>>> The vote will stand for 72 hours. Issues raised will be
>>> discussed and if we conclude that there is a bug that must be
>>> addressed then we will mitigate the problem and respin a new rc
>>> for a 72 hour vote.
>>>
>>> If this is accepted all three of the above components will be
>>> released simultaneously.
>>>
>>> Here are the builds for your review and comment:
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>>> rc1.tar.gz
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>>> rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
>>> rc1.tar.gz
>>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
>>> rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>>> rc1.tar.gz
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>>> rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-
>>> minimal-1.1-rc1.tar.gz
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-
>>> minimal-1.1-rc1.zip
>>>
>>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>>
>>>
>>> Looking forward to your comments and feedback.
>>>
>>>
>
Re: [Vote] 1.1-rc1 Now Available
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
We vote for release candidates? I don't recall doing that before.
+1
Regards,
Alan
Matt Hogstrom wrote:
> I apologize for resending this to the lists. I inadvertantly did not
> put [vote] in the subject line so it may not have been apparent. The
> remainder of this e-mail is the same content that was distributed last
> night.
>
> Matt Hogstrom wrote:
>> Over the past few days the outstanding issues that were raised about
>> the first candidate have been addressed.
>>
>> They were that we were missing the LICENSE.txt as well as Notices
>> from the distribution. I added them. Guillaume also pointed out
>> that he noted that there should be a Third Party Notices. This was
>> not included in the original 1.0 or previous distributions so I did
>> not follow it up. Thoughts?
>>
>> Also, the 1.0 release notes were removed and updated the thread
>> started by Hernan. The Wiki has been updated and the wiki was the
>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>> the build.
>>
>> To avoid issues with the version number and the plugins I used rc1
>> which Aaron had added in the plugins for supported versions so I
>> trust that works here.
>>
>> JSisson addressed the problem with not being able to run Geronimo
>> under CygWin and Kevan worked with Aaron to address a new deployment
>> problem that left partially deployed artifacts in the repository.
>>
>> I have taken this build and run some performance tests on it and we
>> are significantly better in 1.1 than we were in 1.0. We have a lot
>> of improvement left for CMP EJBs. It appears that the performance
>> improvements in the EJB tier has changed a race condition when
>> running under DB2. I'm afraid that the only way to address the
>> problem is to add a new feature to TranQL and OEJB that allow for the
>> specification of Isolation Levels for individual beans. This is a
>> relatively simple change but the build as it stands is specification
>> compliant. I would prefer to let this release go forward since CMP
>> 2.1 EJBs are not nearly as common as the other J2EE components. I
>> would like to address this in 1.1.1 however I don't think we've
>> locked down whether that would be allowed or not. The change would
>> affect TranQL and OpenEJB so they are really included components so
>> I'd be interested in people's feedback.
>>
>> So please accept a named RC1. Your voting and feedback are for:
>>
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>>
>> The vote will stand for 72 hours. Issues raised will be discussed
>> and if we conclude that there is a bug that must be addressed then we
>> will mitigate the problem and respin a new rc for a 72 hour vote.
>>
>> If this is accepted all three of the above components will be
>> released simultaneously.
>>
>> Here are the builds for your review and comment:
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>
>>
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>
>>
>> Looking forward to your comments and feedback.
>>
>>
Re: [Vote] 1.1-rc1 Now Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
David,
Thanks for the heads up. I saw the JIRA and the commits. Leave it open but I suspect we're going
to close down tonight and cut the final release.
David Jencks wrote:
>>
> I think that we may need to recut the release due to
> http://issues.apache.org/jira/browse/GERONIMO-2108
>
> Apparently I forgot to convert message-destination elements in geronimo
> plans to the naming namespace and as a consequence it is impossible to
> use them in web plans. Aside from rewriting your spec dds to not use
> message-destination or renaming stuff to auto-resolve I don't know of a
> workaround.
>
> I think I've fixed the issue but want to think if there are any more
> cases before I close it.
>
> My apologies,
>
> thanks
> david jencks
>
>
>
>> Matt Hogstrom wrote:
>>> I apologize for resending this to the lists. I inadvertantly did not
>>> put [vote] in the subject line so it may not have been apparent. The
>>> remainder of this e-mail is the same content that was distributed last
>>> night.
>>>
>>> Matt Hogstrom wrote:
>>>> Over the past few days the outstanding issues that were raised about
>>>> the first candidate have been addressed.
>>>>
>>>> They were that we were missing the LICENSE.txt as well as Notices from
>>>> the distribution. I added them. Guillaume also pointed out that he
>>>> noted that there should be a Third Party Notices. This was not
>>>> included in the original 1.0 or previous distributions so I did not
>>>> follow it up. Thoughts?
>>>>
>>>> Also, the 1.0 release notes were removed and updated the thread
>>>> started by Hernan. The Wiki has been updated and the wiki was the
>>>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>>>> the build.
>>>>
>>>> To avoid issues with the version number and the plugins I used rc1
>>>> which Aaron had added in the plugins for supported versions so I trust
>>>> that works here.
>>>>
>>>> JSisson addressed the problem with not being able to run Geronimo
>>>> under CygWin and Kevan worked with Aaron to address a new deployment
>>>> problem that left partially deployed artifacts in the repository.
>>>>
>>>> I have taken this build and run some performance tests on it and we
>>>> are significantly better in 1.1 than we were in 1.0. We have a lot of
>>>> improvement left for CMP EJBs. It appears that the performance
>>>> improvements in the EJB tier has changed a race condition when running
>>>> under DB2. I'm afraid that the only way to address the problem is to
>>>> add a new feature to TranQL and OEJB that allow for the specification
>>>> of Isolation Levels for individual beans. This is a relatively simple
>>>> change but the build as it stands is specification compliant. I would
>>>> prefer to let this release go forward since CMP 2.1 EJBs are not
>>>> nearly as common as the other J2EE components. I would like to
>>>> address this in 1.1.1 however I don't think we've locked down whether
>>>> that would be allowed or not. The change would affect TranQL and
>>>> OpenEJB so they are really included components so I'd be interested in
>>>> people's feedback.
>>>>
>>>> So please accept a named RC1. Your voting and feedback are for:
>>>>
>>>> Geronimo 1.1
>>>> DayTrader 1.1
>>>> Specs 1.1
>>>>
>>>> The vote will stand for 72 hours. Issues raised will be discussed and
>>>> if we conclude that there is a bug that must be addressed then we will
>>>> mitigate the problem and respin a new rc for a 72 hour vote.
>>>>
>>>> If this is accepted all three of the above components will be released
>>>> simultaneously.
>>>>
>>>> Here are the builds for your review and comment:
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>>>
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>>>
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>>>
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>>>
>>>>
>>>>
>>>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>>>
>>>>
>>>> Looking forward to your comments and feedback.
>>>>
>>>>
>
>
>
>
Re: [Vote] 1.1-rc1 Now Available
Posted by David Jencks <da...@yahoo.com>.
>
I think that we may need to recut the release due to http://
issues.apache.org/jira/browse/GERONIMO-2108
Apparently I forgot to convert message-destination elements in
geronimo plans to the naming namespace and as a consequence it is
impossible to use them in web plans. Aside from rewriting your spec
dds to not use message-destination or renaming stuff to auto-resolve
I don't know of a workaround.
I think I've fixed the issue but want to think if there are any more
cases before I close it.
My apologies,
thanks
david jencks
> Matt Hogstrom wrote:
>> I apologize for resending this to the lists. I inadvertantly did not
>> put [vote] in the subject line so it may not have been apparent. The
>> remainder of this e-mail is the same content that was distributed
>> last
>> night.
>>
>> Matt Hogstrom wrote:
>>> Over the past few days the outstanding issues that were raised about
>>> the first candidate have been addressed.
>>>
>>> They were that we were missing the LICENSE.txt as well as Notices
>>> from
>>> the distribution. I added them. Guillaume also pointed out that he
>>> noted that there should be a Third Party Notices. This was not
>>> included in the original 1.0 or previous distributions so I did not
>>> follow it up. Thoughts?
>>>
>>> Also, the 1.0 release notes were removed and updated the thread
>>> started by Hernan. The Wiki has been updated and the wiki was the
>>> source used to create the RELEASE-NOTES-1.1.txt file you will
>>> find in
>>> the build.
>>>
>>> To avoid issues with the version number and the plugins I used rc1
>>> which Aaron had added in the plugins for supported versions so I
>>> trust
>>> that works here.
>>>
>>> JSisson addressed the problem with not being able to run Geronimo
>>> under CygWin and Kevan worked with Aaron to address a new deployment
>>> problem that left partially deployed artifacts in the repository.
>>>
>>> I have taken this build and run some performance tests on it and we
>>> are significantly better in 1.1 than we were in 1.0. We have a
>>> lot of
>>> improvement left for CMP EJBs. It appears that the performance
>>> improvements in the EJB tier has changed a race condition when
>>> running
>>> under DB2. I'm afraid that the only way to address the problem
>>> is to
>>> add a new feature to TranQL and OEJB that allow for the
>>> specification
>>> of Isolation Levels for individual beans. This is a relatively
>>> simple
>>> change but the build as it stands is specification compliant. I
>>> would
>>> prefer to let this release go forward since CMP 2.1 EJBs are not
>>> nearly as common as the other J2EE components. I would like to
>>> address this in 1.1.1 however I don't think we've locked down
>>> whether
>>> that would be allowed or not. The change would affect TranQL and
>>> OpenEJB so they are really included components so I'd be
>>> interested in
>>> people's feedback.
>>>
>>> So please accept a named RC1. Your voting and feedback are for:
>>>
>>> Geronimo 1.1
>>> DayTrader 1.1
>>> Specs 1.1
>>>
>>> The vote will stand for 72 hours. Issues raised will be
>>> discussed and
>>> if we conclude that there is a bug that must be addressed then we
>>> will
>>> mitigate the problem and respin a new rc for a 72 hour vote.
>>>
>>> If this is accepted all three of the above components will be
>>> released
>>> simultaneously.
>>>
>>> Here are the builds for your review and comment:
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>>> rc1.tar.gz
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-
>>> rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-
>>> rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-
>>> rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>>> rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-
>>> rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-
>>> minimal-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-
>>> minimal-1.1-rc1.zip
>>>
>>>
>>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>>
>>>
>>> Looking forward to your comments and feedback.
>>>
>>>
Re: [Vote] 1.1-rc1 Now Available
Posted by Jeff Genender <jg...@apache.org>.
+1
Matt Hogstrom wrote:
> I apologize for resending this to the lists. I inadvertantly did not
> put [vote] in the subject line so it may not have been apparent. The
> remainder of this e-mail is the same content that was distributed last
> night.
>
> Matt Hogstrom wrote:
>> Over the past few days the outstanding issues that were raised about
>> the first candidate have been addressed.
>>
>> They were that we were missing the LICENSE.txt as well as Notices from
>> the distribution. I added them. Guillaume also pointed out that he
>> noted that there should be a Third Party Notices. This was not
>> included in the original 1.0 or previous distributions so I did not
>> follow it up. Thoughts?
>>
>> Also, the 1.0 release notes were removed and updated the thread
>> started by Hernan. The Wiki has been updated and the wiki was the
>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>> the build.
>>
>> To avoid issues with the version number and the plugins I used rc1
>> which Aaron had added in the plugins for supported versions so I trust
>> that works here.
>>
>> JSisson addressed the problem with not being able to run Geronimo
>> under CygWin and Kevan worked with Aaron to address a new deployment
>> problem that left partially deployed artifacts in the repository.
>>
>> I have taken this build and run some performance tests on it and we
>> are significantly better in 1.1 than we were in 1.0. We have a lot of
>> improvement left for CMP EJBs. It appears that the performance
>> improvements in the EJB tier has changed a race condition when running
>> under DB2. I'm afraid that the only way to address the problem is to
>> add a new feature to TranQL and OEJB that allow for the specification
>> of Isolation Levels for individual beans. This is a relatively simple
>> change but the build as it stands is specification compliant. I would
>> prefer to let this release go forward since CMP 2.1 EJBs are not
>> nearly as common as the other J2EE components. I would like to
>> address this in 1.1.1 however I don't think we've locked down whether
>> that would be allowed or not. The change would affect TranQL and
>> OpenEJB so they are really included components so I'd be interested in
>> people's feedback.
>>
>> So please accept a named RC1. Your voting and feedback are for:
>>
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>>
>> The vote will stand for 72 hours. Issues raised will be discussed and
>> if we conclude that there is a bug that must be addressed then we will
>> mitigate the problem and respin a new rc for a 72 hour vote.
>>
>> If this is accepted all three of the above components will be released
>> simultaneously.
>>
>> Here are the builds for your review and comment:
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>
>>
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>
>>
>> Looking forward to your comments and feedback.
>>
>>
Re: [Vote] 1.1-rc1 Now Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
John,
I'm not aware of what does or does not go into the NOTICES file. If we need the notices does anyone
have a list of them lying around on their harddisk ?
Otherwise, any volunteers to pull them together?
Hernan, could you start a Wiki page for people to post their findings to?
Cheers,
Matt
John Sisson wrote:
> I have started some due diligence checking on the release candidate and
> have a few questions.
>
> AFAIK, the NOTICE.txt file should contain required third-party
> notices/attributions, yet it seems pretty empty to me.
>
> For example, I was expecting to see the text from
> http://www.bouncycastle.org/licence.html in there since we have a copy
> of some of their code (no crypto though) in geronimo's util module. The
> page on their website indicates that a notice may be required.
>
> What about other 3rd party binaries that we include in the
> distribution? For example, I had a quick look at the repository
> directory in the assemblies and there are libraries we ship where their
> project website requires attributions etc to be included with binary
> distributions (e.g. ASM , http://asm.objectweb.org/license.html ).
>
> Please speak up if I am misinterpreting the use of the NOTICE.txt file.
>
> Thanks,
>
> John
>
> Matt Hogstrom wrote:
>> I apologize for resending this to the lists. I inadvertantly did not
>> put [vote] in the subject line so it may not have been apparent. The
>> remainder of this e-mail is the same content that was distributed last
>> night.
>>
>> Matt Hogstrom wrote:
>>> Over the past few days the outstanding issues that were raised about
>>> the first candidate have been addressed.
>>>
>>> They were that we were missing the LICENSE.txt as well as Notices
>>> from the distribution. I added them. Guillaume also pointed out
>>> that he noted that there should be a Third Party Notices. This was
>>> not included in the original 1.0 or previous distributions so I did
>>> not follow it up. Thoughts?
>>>
>>> Also, the 1.0 release notes were removed and updated the thread
>>> started by Hernan. The Wiki has been updated and the wiki was the
>>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>>> the build.
>>>
>>> To avoid issues with the version number and the plugins I used rc1
>>> which Aaron had added in the plugins for supported versions so I
>>> trust that works here.
>>>
>>> JSisson addressed the problem with not being able to run Geronimo
>>> under CygWin and Kevan worked with Aaron to address a new deployment
>>> problem that left partially deployed artifacts in the repository.
>>>
>>> I have taken this build and run some performance tests on it and we
>>> are significantly better in 1.1 than we were in 1.0. We have a lot
>>> of improvement left for CMP EJBs. It appears that the performance
>>> improvements in the EJB tier has changed a race condition when
>>> running under DB2. I'm afraid that the only way to address the
>>> problem is to add a new feature to TranQL and OEJB that allow for the
>>> specification of Isolation Levels for individual beans. This is a
>>> relatively simple change but the build as it stands is specification
>>> compliant. I would prefer to let this release go forward since CMP
>>> 2.1 EJBs are not nearly as common as the other J2EE components. I
>>> would like to address this in 1.1.1 however I don't think we've
>>> locked down whether that would be allowed or not. The change would
>>> affect TranQL and OpenEJB so they are really included components so
>>> I'd be interested in people's feedback.
>>>
>>> So please accept a named RC1. Your voting and feedback are for:
>>>
>>> Geronimo 1.1
>>> DayTrader 1.1
>>> Specs 1.1
>>>
>>> The vote will stand for 72 hours. Issues raised will be discussed
>>> and if we conclude that there is a bug that must be addressed then we
>>> will mitigate the problem and respin a new rc for a 72 hour vote.
>>>
>>> If this is accepted all three of the above components will be
>>> released simultaneously.
>>>
>>> Here are the builds for your review and comment:
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>>
>>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>>
>>>
>>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>>
>>>
>>> Looking forward to your comments and feedback.
>>>
>>>
>>
>
>
>
>
Re: [Vote] 1.1-rc1 Now Available
Posted by John Sisson <jr...@gmail.com>.
I have started some due diligence checking on the release candidate and
have a few questions.
AFAIK, the NOTICE.txt file should contain required third-party
notices/attributions, yet it seems pretty empty to me.
For example, I was expecting to see the text from
http://www.bouncycastle.org/licence.html in there since we have a copy
of some of their code (no crypto though) in geronimo's util module. The
page on their website indicates that a notice may be required.
What about other 3rd party binaries that we include in the
distribution? For example, I had a quick look at the repository
directory in the assemblies and there are libraries we ship where their
project website requires attributions etc to be included with binary
distributions (e.g. ASM , http://asm.objectweb.org/license.html ).
Please speak up if I am misinterpreting the use of the NOTICE.txt file.
Thanks,
John
Matt Hogstrom wrote:
> I apologize for resending this to the lists. I inadvertantly did not
> put [vote] in the subject line so it may not have been apparent. The
> remainder of this e-mail is the same content that was distributed last
> night.
>
> Matt Hogstrom wrote:
>> Over the past few days the outstanding issues that were raised about
>> the first candidate have been addressed.
>>
>> They were that we were missing the LICENSE.txt as well as Notices
>> from the distribution. I added them. Guillaume also pointed out
>> that he noted that there should be a Third Party Notices. This was
>> not included in the original 1.0 or previous distributions so I did
>> not follow it up. Thoughts?
>>
>> Also, the 1.0 release notes were removed and updated the thread
>> started by Hernan. The Wiki has been updated and the wiki was the
>> source used to create the RELEASE-NOTES-1.1.txt file you will find in
>> the build.
>>
>> To avoid issues with the version number and the plugins I used rc1
>> which Aaron had added in the plugins for supported versions so I
>> trust that works here.
>>
>> JSisson addressed the problem with not being able to run Geronimo
>> under CygWin and Kevan worked with Aaron to address a new deployment
>> problem that left partially deployed artifacts in the repository.
>>
>> I have taken this build and run some performance tests on it and we
>> are significantly better in 1.1 than we were in 1.0. We have a lot
>> of improvement left for CMP EJBs. It appears that the performance
>> improvements in the EJB tier has changed a race condition when
>> running under DB2. I'm afraid that the only way to address the
>> problem is to add a new feature to TranQL and OEJB that allow for the
>> specification of Isolation Levels for individual beans. This is a
>> relatively simple change but the build as it stands is specification
>> compliant. I would prefer to let this release go forward since CMP
>> 2.1 EJBs are not nearly as common as the other J2EE components. I
>> would like to address this in 1.1.1 however I don't think we've
>> locked down whether that would be allowed or not. The change would
>> affect TranQL and OpenEJB so they are really included components so
>> I'd be interested in people's feedback.
>>
>> So please accept a named RC1. Your voting and feedback are for:
>>
>> Geronimo 1.1
>> DayTrader 1.1
>> Specs 1.1
>>
>> The vote will stand for 72 hours. Issues raised will be discussed
>> and if we conclude that there is a bug that must be addressed then we
>> will mitigate the problem and respin a new rc for a 72 hour vote.
>>
>> If this is accepted all three of the above components will be
>> released simultaneously.
>>
>> Here are the builds for your review and comment:
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>>
>> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>>
>>
>> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>>
>>
>> Looking forward to your comments and feedback.
>>
>>
>
[Vote] 1.1-rc1 Now Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I apologize for resending this to the lists. I inadvertantly did not put [vote] in the subject line
so it may not have been apparent. The remainder of this e-mail is the same content that was
distributed last night.
Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised about the
> first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices from
> the distribution. I added them. Guillaume also pointed out that he
> noted that there should be a Third Party Notices. This was not included
> in the original 1.0 or previous distributions so I did not follow it
> up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread started
> by Hernan. The Wiki has been updated and the wiki was the source used
> to create the RELEASE-NOTES-1.1.txt file you will find in the build.
>
> To avoid issues with the version number and the plugins I used rc1 which
> Aaron had added in the plugins for supported versions so I trust that
> works here.
>
> JSisson addressed the problem with not being able to run Geronimo under
> CygWin and Kevan worked with Aaron to address a new deployment problem
> that left partially deployed artifacts in the repository.
>
> I have taken this build and run some performance tests on it and we are
> significantly better in 1.1 than we were in 1.0. We have a lot of
> improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when running
> under DB2. I'm afraid that the only way to address the problem is to
> add a new feature to TranQL and OEJB that allow for the specification of
> Isolation Levels for individual beans. This is a relatively simple
> change but the build as it stands is specification compliant. I would
> prefer to let this release go forward since CMP 2.1 EJBs are not nearly
> as common as the other J2EE components. I would like to address this in
> 1.1.1 however I don't think we've locked down whether that would be
> allowed or not. The change would affect TranQL and OpenEJB so they are
> really included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed and
> if we conclude that there is a bug that must be addressed then we will
> mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be released
> simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
>
[Vote] 1.1-rc1 Now Available
Posted by Matt Hogstrom <ma...@hogstrom.org>.
I apologize for resending this to the lists. I inadvertantly did not put [vote] in the subject line
so it may not have been apparent. The remainder of this e-mail is the same content that was
distributed last night.
Matt Hogstrom wrote:
> Over the past few days the outstanding issues that were raised about the
> first candidate have been addressed.
>
> They were that we were missing the LICENSE.txt as well as Notices from
> the distribution. I added them. Guillaume also pointed out that he
> noted that there should be a Third Party Notices. This was not included
> in the original 1.0 or previous distributions so I did not follow it
> up. Thoughts?
>
> Also, the 1.0 release notes were removed and updated the thread started
> by Hernan. The Wiki has been updated and the wiki was the source used
> to create the RELEASE-NOTES-1.1.txt file you will find in the build.
>
> To avoid issues with the version number and the plugins I used rc1 which
> Aaron had added in the plugins for supported versions so I trust that
> works here.
>
> JSisson addressed the problem with not being able to run Geronimo under
> CygWin and Kevan worked with Aaron to address a new deployment problem
> that left partially deployed artifacts in the repository.
>
> I have taken this build and run some performance tests on it and we are
> significantly better in 1.1 than we were in 1.0. We have a lot of
> improvement left for CMP EJBs. It appears that the performance
> improvements in the EJB tier has changed a race condition when running
> under DB2. I'm afraid that the only way to address the problem is to
> add a new feature to TranQL and OEJB that allow for the specification of
> Isolation Levels for individual beans. This is a relatively simple
> change but the build as it stands is specification compliant. I would
> prefer to let this release go forward since CMP 2.1 EJBs are not nearly
> as common as the other J2EE components. I would like to address this in
> 1.1.1 however I don't think we've locked down whether that would be
> allowed or not. The change would affect TranQL and OpenEJB so they are
> really included components so I'd be interested in people's feedback.
>
> So please accept a named RC1. Your voting and feedback are for:
>
> Geronimo 1.1
> DayTrader 1.1
> Specs 1.1
>
> The vote will stand for 72 hours. Issues raised will be discussed and
> if we conclude that there is a bug that must be addressed then we will
> mitigate the problem and respin a new rc for a 72 hour vote.
>
> If this is accepted all three of the above components will be released
> simultaneously.
>
> Here are the builds for your review and comment:
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-j2ee-1.1-rc1.tar.gz
> http://people.apache.org/~hogstrom/rc1/geronimo-romcat-j2ee-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-jetty-minimal-1.1-rc1.zip
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.tar.gz
>
> http://people.apache.org/~hogstrom/rc1/geronimo-tomcat-minimal-1.1-rc1.zip
>
> http://people.apache.org/~hogstrom/rc1/daytrader-ear-1.1-rc1.zip
>
>
> Looking forward to your comments and feedback.
>
>