You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Rick McGuire <ri...@gmail.com> on 2010/09/22 14:53:04 UTC
Time for a 3.1.3 release?
The axis2 and activemq releases that we've been waiting on for a 2.2.1
Geronimo server release are finally available, but I didn't realize that
the 2.2 branch was still building with the 3.1.3-SNAPSHOT version of
openejb3. Is that branch ready to be released and can it be released
soon? I'd like to get the server release voting started by the end of
next week, if I can.
Rick
3.1.3 Release Steps (Re: Time for a 3.1.3 release?)
Posted by David Blevins <da...@visi.com>.
On Sep 24, 2010, at 2:53 AM, Jean-Louis MONTEIRO wrote:
> BTW, i don't actually know the steps, nor the work involved.
I always forget myself. Here are some of the things I forgot since last time:
1. Ant build.xml files are ignored by mvn release:prepare. Fixed this with the following:
$ find . -name 'build.xml' -exec perl -i -pe "s/(3.1.3)-SNAPSHOT/$1/g" {} \;
$ find . -name 'build.xml' -exec perl -i -pe "s/(5.0-3)-SNAPSHOT/$1/g" {} \;
2. Just to make sure nothing is missed and still has -SNAPSHOT in it, I used the 'ack' tool to search:
$ ack -- '-SNAPSHOT'
More coming...
Re: Time for a 3.1.3 release?
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Hi David,
Providing releases is definitely an area i never really helped (other than
looking/testing binaries).
BTW, i don't actually know the steps, nor the work involved.
Regardless that point, it seems interesting and i'd like to help in the
future.
Can you give me some links or anything else which can help.
Moreover, if you think i can help, feel free to ping ;-)
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/Time-for-a-3-1-3-release-tp2550227p2553270.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Time for a 3.1.3 release?
Posted by Jean-Louis MONTEIRO <je...@atosorigin.com>.
Hi André,
David can probably give more details, but in my opinion, JPA 2.0 will only
be supported in the trunk (OpenEJB 3.2.x releases).
Basically, OpenEJB 3.1.x is Java EE 5 compliant and OpenEJB 3.2.x will be
Java EE 6.
Jean-Louis
--
View this message in context: http://openejb.979440.n4.nabble.com/Time-for-a-3-1-3-release-tp2550227p2553255.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Time for a 3.1.3 release?
Posted by Andre Brito <an...@gmail.com>.
Hey!
Can you guys answer me if that new release will support JPA 2.0?
--
View this message in context: http://openejb.979440.n4.nabble.com/Time-for-a-3-1-3-release-tp2550227p2552517.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Time for a 3.1.3 release?
Posted by Marius Kruger <am...@gmail.com>.
On 22 September 2010 21:19, David Blevins <da...@visi.com> wrote:
> There are a couple modules that need to get trimmed out as they aren't ready for prime-time; openejb-junit and potentially the jetty stuff which I think might only be working in trunk. As well we need to do a sweep through the binaries that show up in the standalone/war distros and make sure nothing has crept in that shouldn't be there as well as make sure that what is needed and new is accounted for in the notice file. And then of course we need to make sure the itests run on the standalone server and tomcat integration.
doesn't it make sense to do this to the snapshot release asap, so that
the real release will be as close to the last snapshot as possible, so
it can get wider testing and no surprises...
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Sep 22, 2010, at 5:53 AM, Rick McGuire wrote:
> The axis2 and activemq releases that we've been waiting on for a 2.2.1 Geronimo server release are finally available, but I didn't realize that the 2.2 branch was still building with the 3.1.3-SNAPSHOT version of openejb3. Is that branch ready to be released and can it be released soon? I'd like to get the server release voting started by the end of next week, if I can.
I think we're good to go for the most part. I can probably kick off the release process next week.
There are a couple modules that need to get trimmed out as they aren't ready for prime-time; openejb-junit and potentially the jetty stuff which I think might only be working in trunk. As well we need to do a sweep through the binaries that show up in the standalone/war distros and make sure nothing has crept in that shouldn't be there as well as make sure that what is needed and new is accounted for in the notice file. And then of course we need to make sure the itests run on the standalone server and tomcat integration.
Usually we can hammer out release notes while the vote is going.
-David
Re: Time for a 3.1.3 release?
Posted by Shawn Jiang <ge...@gmail.com>.
Geronimo 2.2 branch 100% passed tck with this staging openejb 3.1.3
artifacts. It's time to start the vote.
On Fri, Oct 8, 2010 at 8:17 PM, Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:
> Just ran this. I ran into one problem which was the Tomcat bundle trying to
> use the openejb-webapp 3.1.3-SNAPSHOT and not 3.1.3 - I guess the prepare
> goal for the release plugin didn't pick this one up. I've updated the
> version string and committed the change to the branch.
>
> Other than that, I've done the deployment, and it has just finished without
> any errors. I've checked Nexus, and it looks like stuff is there. The
> repository is here:
> https://repository.apache.org/content/repositories/orgapacheopenejb-009/
>
> Let me know if there's anything else I can do, but hopefully this
> deployment
> will be good.
>
> Jon
>
> On Fri, Oct 8, 2010 at 1:08 AM, David Blevins <david.blevins@visi.com
> >wrote:
>
> >
> > On Oct 7, 2010, at 4:10 PM, Jonathan Gallimore wrote:
> >
> > > Do you think this is a Nexus / Central problem? I don't mind giving it
> a
> > go
> > > from here if you think its worth a shot.
> >
> > Starting to wonder that.
> >
> > I tried going around the httpd proxy by hitting
> repository.apache.org:8081and hacking my apache parent pom to use that as
> the repo. Still died while
> > uploading the standalone tar.gz. So that rules out the httpd proxy as
> the
> > cause.
> >
> > To rule out anything in the middle, I setup a tunnel between me and
> > repository.a.o through people.apache.org (via ssh -L 8081:
> > repository.apache.org:8081 people.apache.org). Double verified that
> > everything worked through the tunnel by killing the tunnel to make sure
> that
> > the upload would immediately fail. Still no luck. So that would
> indicate
> > no one in the middle is hanging up on me.
> >
> > So at this point it's either me or Nexus.
> >
> > Here's the command do upload:
> >
> > $ svn co https://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.3
> > $ cd openejb-3.1.3
> > $ mvn install -Dassemble -Dmaven.test.skip=true
> > $ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx
> >
> > Something is messed up in our poms that the build fails unless you've
> built
> > at least once. So I added that 'mvn install -Dassemble
> > -Dmaven.test.skip=true'.
> >
> > Anyway, anxious to see what kind of results you get.
> >
> > -David
> >
> >
> > > On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <david.blevins@visi.com
> > >wrote:
> > >
> > >> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
> > >>
> > >>> I'm repeatedly getting HTTP 502 errors while uploading the assemblies
> > to
> > >> nexus....
> > >>>
> > >>> Going to keep retrying. If anyone has any tips, they would be very
> > >> welcome.
> > >>>
> > >>> I seem to remember encountering this before and eventually it just
> > >> worked. Seems like something here is in dire need of improvement.
> > >>
> > >> Unfortunately I seem to be at an impasse with uploading the binaries.
> > I'm
> > >> getting bit by this:
> > >>
> > >> https://issues.sonatype.org/browse/NEXUS-2879
> > >>
> > >> Been working with infra to try and tweak the proxy, but at this point
> we
> > >> still have no idea what's going wrong.
> > >>
> > >> Will keep trying and post more details later.
> > >>
> > >> -David
> > >>
> > >>
> >
> >
>
--
Shawn
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 11, 2010, at 11:06 AM, David Blevins wrote:
> Going to try an upload from the mac mini and see if I can't get it to work. If not, I may need you to do another upload.
Things worked fine from my mini. Not sure why maven doesn't like my laptop -- oh well.
Staging repo is here:
https://repository.apache.org/content/repositories/orgapacheopenejb-017/
Uploading the "dist" directory now. Vote coming shortly....
-David
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 8, 2010, at 5:17 AM, Jonathan Gallimore wrote:
> Just ran this. I ran into one problem which was the Tomcat bundle trying to
> use the openejb-webapp 3.1.3-SNAPSHOT and not 3.1.3 - I guess the prepare
> goal for the release plugin didn't pick this one up. I've updated the
> version string and committed the change to the branch.
>
> Other than that, I've done the deployment, and it has just finished without
> any errors. I've checked Nexus, and it looks like stuff is there. The
> repository is here:
> https://repository.apache.org/content/repositories/orgapacheopenejb-009/
>
> Let me know if there's anything else I can do, but hopefully this deployment
> will be good.
>
That's great. Noticed our tomcat bundle didn't have the intended 6.0.26.313 version number and just had 313. As fixing that would mean attempting to get another upload to work, I switched over to my mac mini to see if I could get the build to go from there. Then I noticed that we don't compile under java 1.5. We get this compilation failure:
[INFO] ------------------------------------------------------------------------
[INFO] Building OpenEJB :: Server :: CXF
[INFO] task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting file set: /Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/target (included: [**], excluded: [])
[INFO] [remote-resources:process {execution: default}]
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException: reference : template = META-INF/DEPENDENCIES.vm [line 40,column 14] : $license.name is not a valid reference.
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 23 source files to /Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
/Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/src/main/java/org/apache/openejb/server/cxf/ejb/EjbMessageContext.java:[22,33] cannot find symbol
symbol : class W3CEndpointReferenceBuilder
location: package javax.xml.ws.wsaddressing
/Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/src/main/java/org/apache/openejb/server/cxf/ejb/EjbMessageContext.java:[40,8] cannot find symbol
symbol : class W3CEndpointReferenceBuilder
location: class org.apache.openejb.server.cxf.ejb.EjbMessageContext
/Users/dblevins/work/openejb-3.1.3/server/openejb-cxf/src/main/java/org/apache/openejb/server/cxf/ejb/EjbMessageContext.java:[40,50] cannot find symbol
symbol : class W3CEndpointReferenceBuilder
location: class org.apache.openejb.server.cxf.ejb.EjbMessageContext
I sifted through and was able to fix it by updating our javaee-api jar. Seems I cut things too thin when trimming down the cxf dependencies. The jaxws api is in the Java 6 vm so it went unnoticed.
Going to try an upload from the mac mini and see if I can't get it to work. If not, I may need you to do another upload.
-David
Re: Time for a 3.1.3 release?
Posted by Jonathan Gallimore <jo...@gmail.com>.
Just ran this. I ran into one problem which was the Tomcat bundle trying to
use the openejb-webapp 3.1.3-SNAPSHOT and not 3.1.3 - I guess the prepare
goal for the release plugin didn't pick this one up. I've updated the
version string and committed the change to the branch.
Other than that, I've done the deployment, and it has just finished without
any errors. I've checked Nexus, and it looks like stuff is there. The
repository is here:
https://repository.apache.org/content/repositories/orgapacheopenejb-009/
Let me know if there's anything else I can do, but hopefully this deployment
will be good.
Jon
On Fri, Oct 8, 2010 at 1:08 AM, David Blevins <da...@visi.com>wrote:
>
> On Oct 7, 2010, at 4:10 PM, Jonathan Gallimore wrote:
>
> > Do you think this is a Nexus / Central problem? I don't mind giving it a
> go
> > from here if you think its worth a shot.
>
> Starting to wonder that.
>
> I tried going around the httpd proxy by hitting repository.apache.org:8081and hacking my apache parent pom to use that as the repo. Still died while
> uploading the standalone tar.gz. So that rules out the httpd proxy as the
> cause.
>
> To rule out anything in the middle, I setup a tunnel between me and
> repository.a.o through people.apache.org (via ssh -L 8081:
> repository.apache.org:8081 people.apache.org). Double verified that
> everything worked through the tunnel by killing the tunnel to make sure that
> the upload would immediately fail. Still no luck. So that would indicate
> no one in the middle is hanging up on me.
>
> So at this point it's either me or Nexus.
>
> Here's the command do upload:
>
> $ svn co https://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.3
> $ cd openejb-3.1.3
> $ mvn install -Dassemble -Dmaven.test.skip=true
> $ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx
>
> Something is messed up in our poms that the build fails unless you've built
> at least once. So I added that 'mvn install -Dassemble
> -Dmaven.test.skip=true'.
>
> Anyway, anxious to see what kind of results you get.
>
> -David
>
>
> > On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <david.blevins@visi.com
> >wrote:
> >
> >> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
> >>
> >>> I'm repeatedly getting HTTP 502 errors while uploading the assemblies
> to
> >> nexus....
> >>>
> >>> Going to keep retrying. If anyone has any tips, they would be very
> >> welcome.
> >>>
> >>> I seem to remember encountering this before and eventually it just
> >> worked. Seems like something here is in dire need of improvement.
> >>
> >> Unfortunately I seem to be at an impasse with uploading the binaries.
> I'm
> >> getting bit by this:
> >>
> >> https://issues.sonatype.org/browse/NEXUS-2879
> >>
> >> Been working with infra to try and tweak the proxy, but at this point we
> >> still have no idea what's going wrong.
> >>
> >> Will keep trying and post more details later.
> >>
> >> -David
> >>
> >>
>
>
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 7, 2010, at 4:10 PM, Jonathan Gallimore wrote:
> Do you think this is a Nexus / Central problem? I don't mind giving it a go
> from here if you think its worth a shot.
Starting to wonder that.
I tried going around the httpd proxy by hitting repository.apache.org:8081 and hacking my apache parent pom to use that as the repo. Still died while uploading the standalone tar.gz. So that rules out the httpd proxy as the cause.
To rule out anything in the middle, I setup a tunnel between me and repository.a.o through people.apache.org (via ssh -L 8081:repository.apache.org:8081 people.apache.org). Double verified that everything worked through the tunnel by killing the tunnel to make sure that the upload would immediately fail. Still no luck. So that would indicate no one in the middle is hanging up on me.
So at this point it's either me or Nexus.
Here's the command do upload:
$ svn co https://svn.apache.org/repos/asf/openejb/branches/openejb-3.1.3
$ cd openejb-3.1.3
$ mvn install -Dassemble -Dmaven.test.skip=true
$ mvn clean deploy -Dassemble -Prelease -Dgpg.passphrase=xxxxxx
Something is messed up in our poms that the build fails unless you've built at least once. So I added that 'mvn install -Dassemble -Dmaven.test.skip=true'.
Anyway, anxious to see what kind of results you get.
-David
> On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <da...@visi.com>wrote:
>
>> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
>>
>>> I'm repeatedly getting HTTP 502 errors while uploading the assemblies to
>> nexus....
>>>
>>> Going to keep retrying. If anyone has any tips, they would be very
>> welcome.
>>>
>>> I seem to remember encountering this before and eventually it just
>> worked. Seems like something here is in dire need of improvement.
>>
>> Unfortunately I seem to be at an impasse with uploading the binaries. I'm
>> getting bit by this:
>>
>> https://issues.sonatype.org/browse/NEXUS-2879
>>
>> Been working with infra to try and tweak the proxy, but at this point we
>> still have no idea what's going wrong.
>>
>> Will keep trying and post more details later.
>>
>> -David
>>
>>
Re: Time for a 3.1.3 release?
Posted by Jonathan Gallimore <jo...@gmail.com>.
Do you think this is a Nexus / Central problem? I don't mind giving it a go
from here if you think its worth a shot.
Jon
On Thu, Oct 7, 2010 at 11:40 PM, David Blevins <da...@visi.com>wrote:
> On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
>
> > I'm repeatedly getting HTTP 502 errors while uploading the assemblies to
> nexus....
> >
> > Going to keep retrying. If anyone has any tips, they would be very
> welcome.
> >
> > I seem to remember encountering this before and eventually it just
> worked. Seems like something here is in dire need of improvement.
>
> Unfortunately I seem to be at an impasse with uploading the binaries. I'm
> getting bit by this:
>
> https://issues.sonatype.org/browse/NEXUS-2879
>
> Been working with infra to try and tweak the proxy, but at this point we
> still have no idea what's going wrong.
>
> Will keep trying and post more details later.
>
> -David
>
>
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Oct 6, 2010, at 10:50 PM, David Blevins wrote:
> I'm repeatedly getting HTTP 502 errors while uploading the assemblies to nexus....
>
> Going to keep retrying. If anyone has any tips, they would be very welcome.
>
> I seem to remember encountering this before and eventually it just worked. Seems like something here is in dire need of improvement.
Unfortunately I seem to be at an impasse with uploading the binaries. I'm getting bit by this:
https://issues.sonatype.org/browse/NEXUS-2879
Been working with infra to try and tweak the proxy, but at this point we still have no idea what's going wrong.
Will keep trying and post more details later.
-David
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
I'm repeatedly getting HTTP 502 errors while uploading the assemblies to nexus....
Going to keep retrying. If anyone has any tips, they would be very welcome.
I seem to remember encountering this before and eventually it just worked. Seems like something here is in dire need of improvement.
-David
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
I'm repeatedly getting HTTP 502 errors while uploading the assemblies to nexus....
Going to keep retrying. If anyone has any tips, they would be very welcome.
I seem to remember encountering this before and eventually it just worked. Seems like something here is in dire need of improvement.
-David
Re: Time for a 3.1.3 release?
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 28, 2010, at 10:49 PM, Kevan Miller wrote:
> Thanks. That would do. Though personally, would rather not be constructing the urls for OpenEJB.
Well, I now see that Geronimo is already constructing the discoveryURI...
Anyway, can all be fixed from Geronimo...
--kevan
Re: Time for a 3.1.3 release?
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 28, 2010, at 2:51 PM, David Blevins wrote:
>
> On Sep 28, 2010, at 7:26 AM, Andy wrote:
>
>> On 28.09.2010 13:07, Kevan Miller wrote:
>>> On Sep 22, 2010, at 8:53 AM, Rick McGuire wrote:
>>>
>>>> The axis2 and activemq releases that we've been waiting on for a 2.2.1 Geronimo server release are finally available, but I didn't realize that the 2.2 branch was still building with the 3.1.3-SNAPSHOT version of openejb3. Is that branch ready to be released and can it be released soon? I'd like to get the server release voting started by the end of next week, if I can.
>>> I created a 2.2.x Geronimo Jira, yesterday, which will have OpenEJB implications. If the server socket bind ip address is 0.0.0.0, we'll advertise the server's ip address as 0.0.0.0 to any multicast discovery clients. We'll need to support a separate "remote" ip address (separate from the server socket ip address).
>>>
>>> --kevan
>>>
>> +1
>>
>> Any multicast architecture should be sending/advertising 'all' IP-addresses and host-names of the server if bind is set to 0.0.0.0, clients can then loop through the list and keep track of successful connections - With a preference for host name connections rather than IP. Currently the config files need to be manually edited to contain the public IP address. In fact, 'discovery' should be a list rather than a single value - For supporting a multi-homed machines.
>
> That would be nice.
>
>> The server should be making a best guess ordered 'discovery' list of it's own public addresses for all network cards on start-up. When a multicast client gets this list then it should see if it's own host-name is in this list, and if it is then first attempt to use localhost. The 'discovery' parameter should act as an override if specified.
>
> Yep. Looks like on the Geronimo side we're missing the 'discovery' property in Geronimo's EjbDaemonGBean. Here is what that defaults to currently:
>
> server/openejb-ejbd/src/main/resources/META-INF/org.apache.openejb.server.ServerService/ejbd
>
> Specifying that solves the problem.
Thanks. That would do. Though personally, would rather not be constructing the urls for OpenEJB. Something like this would be better:
ejbd:
bind = 127.0.0.1
discoveryHost = {bind}
discovery = ejb:ejbd://{discoveryHost}:{port}
--kevan
>
> A nice improvement might be to, on the OpenEJB side, look specifically for 0.0.0.0 in the URI and auto-expand it. We could do the same if the port is 0, so a URI like "ejb:ejbd://0.0.0.0:0" would still work. In a real world scenario that might even be very attractive since in a true discovery scenario you don't care about the host/port, you really just want your server online with any available port.
I don't recall a clean way of doing that in Java, but admittedly haven't looked at the general issue for a *long* time... Pre-java 1.4, I think... Making this potentially dynamic and automatic would be nice...
--kevan
Re: Time for a 3.1.3 release?
Posted by David Blevins <da...@visi.com>.
On Sep 28, 2010, at 7:26 AM, Andy wrote:
> On 28.09.2010 13:07, Kevan Miller wrote:
>> On Sep 22, 2010, at 8:53 AM, Rick McGuire wrote:
>>
>>> The axis2 and activemq releases that we've been waiting on for a 2.2.1 Geronimo server release are finally available, but I didn't realize that the 2.2 branch was still building with the 3.1.3-SNAPSHOT version of openejb3. Is that branch ready to be released and can it be released soon? I'd like to get the server release voting started by the end of next week, if I can.
>> I created a 2.2.x Geronimo Jira, yesterday, which will have OpenEJB implications. If the server socket bind ip address is 0.0.0.0, we'll advertise the server's ip address as 0.0.0.0 to any multicast discovery clients. We'll need to support a separate "remote" ip address (separate from the server socket ip address).
>>
>> --kevan
>>
> +1
>
> Any multicast architecture should be sending/advertising 'all' IP-addresses and host-names of the server if bind is set to 0.0.0.0, clients can then loop through the list and keep track of successful connections - With a preference for host name connections rather than IP. Currently the config files need to be manually edited to contain the public IP address. In fact, 'discovery' should be a list rather than a single value - For supporting a multi-homed machines.
That would be nice.
> The server should be making a best guess ordered 'discovery' list of it's own public addresses for all network cards on start-up. When a multicast client gets this list then it should see if it's own host-name is in this list, and if it is then first attempt to use localhost. The 'discovery' parameter should act as an override if specified.
Yep. Looks like on the Geronimo side we're missing the 'discovery' property in Geronimo's EjbDaemonGBean. Here is what that defaults to currently:
server/openejb-ejbd/src/main/resources/META-INF/org.apache.openejb.server.ServerService/ejbd
Specifying that solves the problem.
A nice improvement might be to, on the OpenEJB side, look specifically for 0.0.0.0 in the URI and auto-expand it. We could do the same if the port is 0, so a URI like "ejb:ejbd://0.0.0.0:0" would still work. In a real world scenario that might even be very attractive since in a true discovery scenario you don't care about the host/port, you really just want your server online with any available port.
-David
Re: Time for a 3.1.3 release?
Posted by Andy <an...@orprovision.com>.
On 28.09.2010 13:07, Kevan Miller wrote:
> On Sep 22, 2010, at 8:53 AM, Rick McGuire wrote:
>
>> The axis2 and activemq releases that we've been waiting on for a 2.2.1 Geronimo server release are finally available, but I didn't realize that the 2.2 branch was still building with the 3.1.3-SNAPSHOT version of openejb3. Is that branch ready to be released and can it be released soon? I'd like to get the server release voting started by the end of next week, if I can.
> I created a 2.2.x Geronimo Jira, yesterday, which will have OpenEJB implications. If the server socket bind ip address is 0.0.0.0, we'll advertise the server's ip address as 0.0.0.0 to any multicast discovery clients. We'll need to support a separate "remote" ip address (separate from the server socket ip address).
>
> --kevan
>
+1
Any multicast architecture should be sending/advertising 'all' IP-addresses and host-names of the server if bind is set
to 0.0.0.0, clients can then loop through the list and keep track of successful connections - With a preference for host
name connections rather than IP. Currently the config files need to be manually edited to contain the public IP address.
In fact, 'discovery' should be a list rather than a single value - For supporting a multi-homed machines.
The server should be making a best guess ordered 'discovery' list of it's own public addresses for all network cards on
start-up. When a multicast client gets this list then it should see if it's own host-name is in this list, and if it is
then first attempt to use localhost. The 'discovery' parameter should act as an override if specified.
Andy.
Re: Time for a 3.1.3 release?
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 22, 2010, at 8:53 AM, Rick McGuire wrote:
> The axis2 and activemq releases that we've been waiting on for a 2.2.1 Geronimo server release are finally available, but I didn't realize that the 2.2 branch was still building with the 3.1.3-SNAPSHOT version of openejb3. Is that branch ready to be released and can it be released soon? I'd like to get the server release voting started by the end of next week, if I can.
I created a 2.2.x Geronimo Jira, yesterday, which will have OpenEJB implications. If the server socket bind ip address is 0.0.0.0, we'll advertise the server's ip address as 0.0.0.0 to any multicast discovery clients. We'll need to support a separate "remote" ip address (separate from the server socket ip address).
--kevan