Re: Quartz, next
I see what you mean now - As shade only works at the 'package' phase there is no way round this other than to use your approach - An external project dependency. Dammit Andy -- View this message in context: http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p4666717.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Quartz, next
You need to enable the 'main' profile in the maven projects view, then the whole world comes in to say hello (takes a while even on a fast machine). Also enable automatic imports in the intellij maven settings. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p4666718.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Quartz, next
So how would we feel with 'openejb-shade-[quartz]' ? And eventually bring all shade jars in line with that naming? I'm happy to do the maven stuff either way. Andy -- View this message in context: http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p486.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Quartz, next
I agree. Just checked in for a build something that works for me - We can rename stuff later. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p488.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Quartz, next
Damn, was too late checking this in. The only issue with quartz-openejb-shade was trying to use the quartz version rather than 'omitting' the version so that it resolves to the parent project version (i.e. 4.6.1-SNAPSHOT) - This is how it should be, as we really want to keep control of the shade at build time when we deploy to either a snapshot or release repo. Moving it out of the project completely is IMHO not the way to go as it complicates the build/deploy and release even more. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p449.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OpenEJB Client incompatibility between 3.1.x and 4.x
So to sum up both: org.apache.openejb.client.Client#processRequest and... org.apache.openejb.server.ejbd.RequestHandler#processRequest (4 Implementations all added various levels of complexity) Introduced calls that broke backwards compatablity between 3.x / 4.5.x and early 4.6.x-SNAPSHOT versions. org.apache.openejb.client.EJBResponse#VERSION, which was effectively never used correctly, could potentially be used to try and get some level of backwards compatibility, but I doubt it as the server has no idea if the calling client is 3.x / 4.5.x or early 4.6.x-SNAPSHOT versions (and serialization is also likely to fail). With 4.6.0+ we now have concrete means to ensure this does not happen again: Providing the de-serialized client ProtocolMetaData to each server object that goes over the wire now allows us to know on the server which client version is calling and how to respond, and serialVersionUID's are now also defined - The legacy tests will fail if someone forgets to follow the pattern when making changes at protocol level. And finally to respond to the initial topic - The system property 'openejb.client.protocol.version' is documented correctly (Allows new clients to potentially communicate with older servers), but it needs to be made more clear that this does NOT allow old clients to communicate with new servers prior to 4.6.0. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-Client-incompatibility-between-3-1-x-and-4-x-tp440p450.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Buildbot: Too many open files
Seeing this on the buildbot: java.io.IOException: error=24, Too many open files Which is easily resolved with something like ulimit -n 5 However, this is usually a good indication that 'a' process is leaking file handles. Has anyone done work on files or sockets recently (a socket is often backed by a file on Linux)? For example, not closing sockets is often a cause of this. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Buildbot-Too-many-open-files-tp4666569.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Sleep 10s?
Yes, I'd do something like:
if(!connect(20,1234))throw FailMiserablyException();
public static boolean connect(int tries, final int port)
try{
final Socket s = new Socket();
s.connect(new InetSocketAddress(addr, port), 150);
} catch (IOException e) {
if (tries 1) {
return false;
} else {
try {
Thread.sleep(100);
} catch (InterruptedException e1) {
return false;
}
return connect(--tries, port);
}
}
...
--
View this message in context:
http://openejb.979440.n4.nabble.com/Sleep-10s-tp4666479p4666486.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Sleep 10s?
Then either close the socket in a finally or use is to test connectivity more before closing... -- View this message in context: http://openejb.979440.n4.nabble.com/Sleep-10s-tp4666479p4666487.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [ANNOUNCE] Welcome Mark Struberg as a new Apache TomEE committer
Hi Mark, Most welcome . Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/ANNOUNCE-Welcome-Mark-Struberg-as-a-new-Apache-TomEE-committer-tp4666391p4666426.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Preparing 1.6.1 maintenance release
+1 Works for me Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Preparing-1-6-1-maintenance-release-tp4666324p4666384.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Hello, Tomee!
Hi Ivan, Have fun! Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Hello-Tomee-tp4666296p4666388.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] TomEE 1.6.0 / OpenEJB 4.6.0 (staging-120)
+1 On windows 32bit and 64bit (with corresponding JVMs) -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-TomEE-1-6-0-OpenEJB-4-6-0-staging-120-tp4666097p4666103.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: [VOTE] TomEE 1.6.0 / OpenEJB 4.6.0 (staging-120)
OK, I have a single test failing: testWithTransaction(org.superbiz.injection.tx.MoviesTest) Time elapsed: 0.285 sec ERROR! javax.ejb.EJBException: The bean encountered a non-application exception; nested exception is: junit.framework.AssertionFailedError: List.size() expected:3 but was:6 at org.apache.openejb.core.ivm.BaseEjbProxyHandler.convertException(BaseEjbProxyHandler.java:403) at org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:307) at $Proxy48.call(Unknown Source) at org.superbiz.injection.tx.MoviesTest.testWithTransaction(MoviesTest.java:75) -- View this message in context: http://openejb.979440.n4.nabble.com/VOTE-TomEE-1-6-0-OpenEJB-4-6-0-staging-120-tp4666097p4666104.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: JIRA Spam
Just forwarded it now :-) -- View this message in context: http://openejb.979440.n4.nabble.com/JIRA-Spam-tp4665230p4665232.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Build 569 failure
The following is due to the server responding with an unexpected (out of sync) write and the client is unable to correctly read what it is expecting (the spec string). There is still somewhere a response that has changed the IO order. Having worked on this to get backwards compatibility back my gut is telling me that it has something to do with error marshalling and possibly a serial id mismatch - I think this only occurs when the server is trying to respond with an error. Looking into it, but any ideas are welcome. Andy. http://ci.apache.org/builders/tomee-trunk-ubuntu/builds/569/steps/test/logs/stdio Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.834 sec FAILURE! test(org.apache.openejb.itest.failover.StickyConnectionStrategyTest) Time elapsed: 11.754 sec ERROR! javax.ejb.EJBException: Unknown Container Exception: java.rmi.RemoteException: Error while communicating with server: ; nested exception is: java.lang.RuntimeException: Protocol version spec must follow format [ OEJB / 1*DIGIT . 1*DIGIT ] at org.apache.openejb.client.ProtocolMetaData.init(ProtocolMetaData.java:57) at org.apache.openejb.client.ProtocolMetaData.readExternal(ProtocolMetaData.java:105) at org.apache.openejb.client.Client.processRequest(Client.java:275) at org.apache.openejb.client.Client.request(Client.java:141) at org.apache.openejb.client.EJBInvocationHandler.request(EJBInvocationHandler.java:147) at org.apache.openejb.client.EJBObjectHandler._businessMethod(EJBObjectHandler.java:349) at org.apache.openejb.client.EJBObjectHandler.businessMethod(EJBObjectHandler.java:338) at org.apache.openejb.client.EJBObjectHandler._invoke(EJBObjectHandler.java:267) at org.apache.openejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:136) at org.apache.openejb.client.proxy.Jdk13InvocationHandler.invoke(Jdk13InvocationHandler.java:49) at com.sun.proxy.$Proxy6.sum(Unknown Source) at org.apache.openejb.itest.failover.StickyConnectionStrategyTest.test(StickyConnectionStrategyTest.java:216) -- View this message in context: http://openejb.979440.n4.nabble.com/Build-569-failure-tp4664980.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Current test failures on trunk
Should be resolved (by Romain). Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Current-test-failures-on-trunk-tp4664795p4664856.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Buildbot forced build.
How do we force a build on the bot? Seen Romain do it several times. The buildbot has not picked up my last check-in? Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/Buildbot-forced-build-tp4664788.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Buildbot forced build.
Thanks Romain, started already :-) -- View this message in context: http://openejb.979440.n4.nabble.com/Buildbot-forced-build-tp4664788p4664790.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Current test failures on trunk
Current test failures on trunk are caused by my recent conflict resolution commit. These were only passing due to maven conflict resolution using fudged versions, which is IMHO not the way to go. I am already looking into the failures and how to 'fix' the tests... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on project alternate-descriptors: There are test failures. [ERROR] [ERROR] Please refer to /home/buildslave18/slave18/tomee-trunk-ubuntu/build/examples/alternate-descriptors/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on project multiple-tomee-arquillian: There are test failures. [ERROR] [ERROR] Please refer to /home/buildslave18/slave18/tomee-trunk-ubuntu/build/examples/multiple-tomee-arquillian/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (test-tomee-remote-plus) on project arquillian-tomee-webprofile-tests: There are test failures. [ERROR] [ERROR] Please refer to /home/buildslave18/slave18/tomee-trunk-ubuntu/build/arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (test-tomee-remote-plus) on project arquillian-tomee-jaxws-tests: There are test failures. [ERROR] [ERROR] Please refer to /home/buildslave18/slave18/tomee-trunk-ubuntu/build/arquillian/arquillian-tomee-tests/arquillian-tomee-jaxws-tests/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (test-tomee-remote-plus) on project arquillian-tomee-jms-tests: There are test failures. [ERROR] [ERROR] Please refer to /home/buildslave18/slave18/tomee-trunk-ubuntu/build/arquillian/arquillian-tomee-tests/arquillian-tomee-jms-tests/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (test-tomee-remote-plus) on project arquillian-tomee-codi-tests: There are test failures. [ERROR] [ERROR] Please refer to /home/buildslave18/slave18/tomee-trunk-ubuntu/build/arquillian/arquillian-tomee-tests/arquillian-tomee-codi-tests/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] Andy -- View this message in context: http://openejb.979440.n4.nabble.com/Current-test-failures-on-trunk-tp4664795.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: EJBD
Added initial LegacyClientTest (which is currently a ripped RandomConnectionStrategyTest), but does the job. We can always add more to the test as new features are added. -- View this message in context: http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664574.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: EJBD
Working on this now, the order of read write has become out of sync. Please don't rush to change anything before I commit. I have a real world scenario to work on here and when I have it working I will commit. I may not be ready till tomorrow, so please hang on. Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664543.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: EJBD
I've already changed the code a bit to look for the version, but just missing something still... Start a snapshot server, and lookup any ejb from an older client. In the client on a stop just before call to protocolMetaData.readExternal(in); in Client.java:251 Wrap stream with new BufferedReader(new InputStreamReader(in)).readLine() Which results in (less symbols): 3.1??org.apache.openejb.client.EJBMetaDataImpl? Looks like a serialized object. -- View this message in context: http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664451.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: EJBD
A bit of a pain to debug hopping from client to remote server. -- View this message in context: http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664453.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: EJBD
Older means ...possibly only as little as 4 weeks old snapshot. But I guess that 4.5.2 clients should still be able to look up ejbs on a 4.6 server right? -- View this message in context: http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664455.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: EJBD
Cool, thanks Romain. The whole version concept seems to have been introduced adhoc, which has made this much harder than it should be. Newer clients will not be able to talk to older servers as they must send the current version (3), but older servers still have code that basically does 'if version == 2 do something', but should really have been 'if version = 2 do something'. I still think it is a real requirement for older clients to be able to talk to a newer server though. -- View this message in context: http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664458.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Default include exclude order should be exclude-include
Thanks Romain, you're on top of everything! If I ever get to meet I'll be sure to get you a beer -- View this message in context: http://openejb.979440.n4.nabble.com/Default-include-exclude-order-should-be-exclude-include-tp4663418p4663534.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Fwd: svn commit: r1485786 - /tomee/tomee/trunk/pom.xml
Is there already a maven module that can be used to search poms and change this value? -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1485786-tomee-tomee-trunk-pom-xml-tp4663194p4663199.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Fwd: svn commit: r1485786 - /tomee/tomee/trunk/pom.xml
There are also several usages that could be replaced by ${parent.version} or
${parent.parent.version} ...if that would work.
--
View this message in context:
http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1485786-tomee-tomee-trunk-pom-xml-tp4663194p4663201.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: Fwd: svn commit: r1485786 - /tomee/tomee/trunk/pom.xml
I guess this only changes at runtime. To deploy to a lan repo the poms have to be physically changed before upload. Currently I add and use versions-maven-plugin 1.3.1 on an svn export, and search and replace for the left-overs. I don't do it that often (only when all tests pass and something significant has changed for the better). My internal version is 4.6.OV.3 This looks promising though, I will have a play with it: http://code.google.com/p/maven-replacer-plugin/ -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1485786-tomee-tomee-trunk-pom-xml-tp4663194p4663203.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: failling tests
Just built off trunk, so working for me [INFO] Apache OpenEJB SUCCESS [7.382s] [INFO] OpenEJB :: Dependencies ... SUCCESS [0.201s] [INFO] OpenEJB :: Dependencies :: MBean Annotation API ... SUCCESS [4.583s] [INFO] OpenEJB :: iTests . SUCCESS [0.186s] [INFO] OpenEJB :: iTests :: Beans SUCCESS [6.425s] [INFO] OpenEJB :: iTests :: Servlets . SUCCESS [1.068s] [INFO] OpenEJB :: iTests :: Client ... SUCCESS [10.351s] [INFO] OpenEJB :: iTests :: Interceptor Beans SUCCESS [0.786s] [INFO] OpenEJB :: iTests :: App .. SUCCESS [2.234s] [INFO] OpenEJB :: iTests :: Web .. SUCCESS [1.452s] [INFO] OpenEJB :: Container .. SUCCESS [0.242s] [INFO] OpenEJB :: Container :: Loader SUCCESS [2.233s] [INFO] OpenEJB :: Container :: JPA Integration ... SUCCESS [2.172s] [INFO] OpenEJB :: Container :: API ... SUCCESS [0.745s] [INFO] OpenEJB :: Container :: Java Agent SUCCESS [0.612s] [INFO] OpenEJB :: Container :: Java EE ... SUCCESS [41.398s] [INFO] OpenEJB :: Container :: Java EE Accessors . SUCCESS [9.036s] [INFO] OpenEJB :: Container :: Core .. SUCCESS [12:19.537s] [INFO] OpenEJB :: Server . SUCCESS [0.077s] [INFO] OpenEJB :: Server :: Client ... SUCCESS [8.288s] [INFO] OpenEJB :: Server :: Core . SUCCESS [7.009s] [INFO] OpenEJB :: Server :: Multicast Discovery .. SUCCESS [40.284s] [INFO] OpenEJB :: Server :: EJBd . SUCCESS [1:52.201s] [INFO] OpenEJB :: Server :: Hsql . SUCCESS [1.361s] [INFO] OpenEJB :: Server :: Http . SUCCESS [2:26.130s] [INFO] OpenEJB :: Server :: Webservices .. SUCCESS [3.256s] [INFO] OpenEJB :: Server :: CXF Transport SUCCESS [2.051s] [INFO] OpenEJB :: Server :: CXF .. SUCCESS [25.343s] [INFO] OpenEJB :: Server :: REST . SUCCESS [1.614s] [INFO] OpenEJB :: Server :: CXF RS ... SUCCESS [1:04.169s] [INFO] OpenEJB :: Server :: Daemon ... SUCCESS [1.191s] [INFO] OpenEJB :: Assembly ... SUCCESS [0.046s] [INFO] OpenEJB :: Assembly :: Standalone . SUCCESS [18.565s] [INFO] OpenEJB :: iTests :: Failover EJB . SUCCESS [0.389s] [INFO] OpenEJB :: Arquillian Adaptors Parent . SUCCESS [0.043s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: Common ... SUCCESS [3.305s] [INFO] OpenEJB :: TomEE .. SUCCESS [1.008s] [INFO] OpenEJB :: TomEE :: Util .. SUCCESS [1.047s] [INFO] OpenEJB :: Utils .. SUCCESS [0.046s] [INFO] OpenEJB :: Utils :: Provisionning . SUCCESS [7.549s] [INFO] OpenEJB :: Arquillian Adaptors Parent :: TomEE Common SUCCESS [3.878s] [INFO] OpenEJB :: iTests :: Failover . SUCCESS [2:43.317s] [INFO] OpenEJB :: Maven Plugins .. SUCCESS [2.406s] [INFO] OpenEJB :: Maven Plugins :: TomEE Maven Plugin SUCCESS [9.731s] [INFO] OpenEJB :: TomEE :: Common SUCCESS [20.971s] [INFO] OpenEJB :: TomEE :: Loader SUCCESS [1.769s] [INFO] OpenEJB :: TomEE :: JDBC .. SUCCESS [13.652s] [INFO] OpenEJB :: TomEE :: Catalina .. SUCCESS [13.827s] [INFO] OpenEJB :: TomEE :: MyFaces ... SUCCESS [1.820s] [INFO] OpenEJB :: TomEE :: TomEE Embedded SUCCESS [42.839s] [INFO] OpenEJB :: Maven Plugins :: Util .. SUCCESS [1.183s] [INFO] OpenEJB :: Maven Plugins :: TomEE Embedded Maven Plugin SUCCESS [12.611s] [INFO] OpenEJB :: Maven Plugins :: OpenEJB Embedded Maven Plugin SUCCESS [7.797s] [INFO] OpenEJB :: Maven Plugins :: TomEE Webapp Archetype SUCCESS [0.466s] [INFO] OpenEJB :: Maven Plugins :: jars.txt Maven Plugin . SUCCESS [1.184s] [INFO] OpenEJB :: Container :: JUnit . SUCCESS [14.153s] [INFO] OpenEJB :: Server :: ActiveMQ . SUCCESS [1.286s] [INFO] OpenEJB :: Server :: Derby Network Service SUCCESS [2.719s] [INFO] OpenEJB :: Server :: Axis . SUCCESS [5.425s] [INFO] OpenEJB :: Server :: Common CLI ... SUCCESS [6.550s] [INFO] OpenEJB :: Server :: SSH .. SUCCESS [4.604s] [INFO] OpenEJB :: Server :: BoneCP ... SUCCESS [7.109s] [INFO] OpenEJB :: Examples :: @AccessTimeout (Meta) .. SUCCESS [12.522s] [INFO] OpenEJB :: Examples :: @AccessTimeout . SUCCESS [6.760s] [INFO] OpenEJB :: Examples :: Alternate
Re: Fwd: svn commit: r1479854 - in /tomee/tomee/branches/tomee-owb-1.1.x: arquillian/arquillian-tomee-common/ arquillian/arquillian-tomee-tests/ container/openejb-api/ examples/polling-parent/polling-
Sure, was trying to deploy a known good snapshot to our local repo with a custom version to avoid confusion and noticed this was not working. mvn versions:set -DnewVersion=[version] If this is working with an older plugin then we should declare it in management maybe? -- View this message in context: http://openejb.979440.n4.nabble.com/Fwd-svn-commit-r1479854-in-tomee-tomee-branches-tomee-owb-1-1-x-arquillian-arquillian-tomee-common-a-tp4662708p4662713.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OWB 1.2?
I would only to ensure that the current trunk we have (which seems to be really stable right now) is available as a stable branch for potential bug fixing. What does OWB 1.2 bring to the party (your opinion, not that of OWB)? I am almost fanatical about updating libraries, so don't think I am against this! Andy -- View this message in context: http://openejb.979440.n4.nabble.com/OWB-1-2-tp4662300p4662329.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: anyone to review/commit the ix in ApplicationComposers?
The users test now passes but I am not sure about pulling in the deps for it if we were to integrate it into the project. Is the issue 'org.apache.deltaspike' specific, or do we have something else we can use for a test already? I'm looking, but I'm sure you have a deeper understanding of the issue that will get there more quickly! Andy. -- View this message in context: http://openejb.979440.n4.nabble.com/anyone-to-review-commit-the-ix-in-ApplicationComposers-tp4662301p4662317.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: anyone to review/commit the ix in ApplicationComposers?
OK, will commit something later. -- View this message in context: http://openejb.979440.n4.nabble.com/anyone-to-review-commit-the-ix-in-ApplicationComposers-tp4662301p4662319.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: OWB 1.2?
+1 Only if trunk passing, else create a branch until stable. -- View this message in context: http://openejb.979440.n4.nabble.com/OWB-1-2-tp4662300p4662323.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
Re: slow multicast discovery can be optimized by caching server...
So this is much easier than you think and is what I have already said. If
ActiveMQ is on localhost to OpenEJB this will do:
I am guessing you know how to create and access a simple stateless bean from
OpenEJB: http://tomee.apache.org/examples-trunk/simple-stateless/README.html
Create a simple EJB with one method - String[] hosts =
aSimpleBean.getHosts();
In that method lookup and return the hosts
final SetString hosts = new TreeSetString();
try {
final InetAddress localhost = InetAddress.getLocalHost();
hosts.add(localhost.getHostAddress());
//Multi-homed
final InetAddress[] all =
InetAddress.getAllByName(localhost.getCanonicalHostName());
for (final InetAddress ip : all) {
if (ip.isLinkLocalAddress() || ip.isMulticastAddress()) {
continue;
}
final String ha = ip.getHostAddress();
if (!ha.replace([, ).startsWith(2001:0:)) { //Filter
Teredo
hosts.add(ha);
hosts.add(ip.getCanonicalHostName());
}
}
} catch (UnknownHostException e) {
log.warning(Failed to list machine hosts, e);
}
return hosts.toArray(new String[hosts.size()]);
Now get that bean, get the host list and use it to connect to ActiveMQ
ctxProps.put(Context.INITIAL_CONTEXT_FACTORY,
org.apache.activemq.jndi.ActiveMQInitialContextFactory);
ctxProps.put(Context.PROVIDER_URL, Try each host in a loop until
you can connect!);
This is about as simple as it gets. All the code is open source.
If ActiveMQ is remote then configure it's own discovery:
http://activemq.apache.org/discovery.html
--
View this message in context:
http://openejb.979440.n4.nabble.com/slow-multicast-discovery-can-be-optimized-by-caching-server-tp4660726p4661030.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
