Nabble - Apache Geronimo - Users

RE: Help me

2009-11-06T07:38:12Z

Hi Forrest,

I tested it again with another OS, Windows XP, the same error.

Can you tell me another version I can try.

Just tell me what is your development environment for the SVN trunk. Do you work on the trunk? Do you commit in your work from time to time?

Thanks

Fei Li

From: Fei LI [mailto:FLI@...]
Sent: Friday, November 06, 2009 8:12 AM
To: user@...; forrestxm@...
Subject: RE: Help me

Hi Forrest,

I got build error for you. My environment are;

1. Windows Vista

2. Java jsdk1.5.0_22

3. Maven 2.2.1

4. SVN source? http://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

5. mvn command mvn clean install -Dtest=false -e

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor:
1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor:
1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1544)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1503)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1282)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:592)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid d
escriptor:
1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
        at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:330)
        at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:224)
        at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184)
        at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540)
        ... 18 more

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 8:20 PM
To: user@...
Subject: Re: Help me

On Fri, Nov 6, 2009 at 11:40 AM, Fei LI <FLI@...> wrote:

Hi Forrest,

Thanks for your help first. Let me build server first the build eclipse plugin second. Because I tried many SVN and no one working. So let me put my question in such way. Tell me if you know, the newest version you know it will be built without error, I have Windows XP and Vista.

1. for server:

1.1 which java version? sun jdk 1.5 latest

1.2 which maven version? 2.2.1

1.3 which SVN source? http://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

1.4. which mvn command? mvn clean install -Dtest=false -e

Besides, you need to pay attention to these:
1. if using sun jdk, you need to set MAVEN_OPTS as documentation. If using ibm jdk, you won't do that
2. checkout the source code in a short path name as Donald pointed out
3. In your DOS window, change your locale to en_US by executing: chcp 437
and then start to build server.

1. for Eclipse plugin:

1.1 which java version?

1.2 which maven version?

1.3 which SVN source?

1.4. which mvn command?

Please try to make server built successfully, then let's see how to build GEP.

Good luck!

I will do whatever you suggest and to see if I luck or not.

Thanks

Fei Li

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 7:20 PM
To: user@...
Subject: Re: Help me

Before building geronimo eclipse plugin(gep), you need to build geronimo server first.

Suggest you start with a released code tree to build gep, not the trunk code. Generally, trunk code is changing and unstable.

For a better understanding what you are doing, pls tell:
1. which version of geronimo you are going to work on?
2. what jdk you are using to build gep?
3. Any error when you are building geronimo server?

Forrest

FW: help

2009-11-06T07:08:22Z

Hi Forrest,

The following is my test on building server 2.2 and error message
emailed to Donald. You may know the reason.

Thanks

Fei Li

-----Original Message-----
From: Fei LI [mailto:FLI@...]
Sent: Thursday, November 05, 2009 10:45 AM
To: Donald Woods; dev@...
Subject: RE: help

Hi Donald,

Thanks for your help first. There was an error:

"
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to delete directory:
C:\JavaFinance\projects\geronimo_server\plugins\axis\axis-deployer\targe
t. Reason: Unable to delete directory C:\JavaFinance\
projects\geronimo_server\plugins\axis\axis-deployer\target\repository\or
g
"

And the error was solved by uncheck "ReadOnly" for all files and
folders.

Then I re-run build, and got error:
"
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure

C:\JavaFinance\projects\geronimo_server\plugins\axis2\geronimo-axis2\src
\test\java\org\apache\geronimo\axis2\Axis2WebServiceContainerTest.java:[
105,48] cannot find symbol
symbol : method getTextContent()
location: interface org.w3c.dom.Element
"

My environment is:
1. Maven 2.0.10
2. jdk1.5.0_22 (latest from Sun)
3. svn https://svn.apache.org/repos/asf/geronimo/server/branches/2.2
4. mvn clean install -DfailIfNoTests=false -Dtest=

Thanks

Fei Li

-----Original Message-----
From: Donald Woods [mailto:dwoods@...]
Sent: Wednesday, November 04, 2009 1:05 PM
To: dev@...
Cc: Fei LI
Subject: Re: help

For the 2.2 based projects -
Maven 2.0.10
Java 5 (latest 1.5.0 from Sun or IBM)

First, build the server without tests -
1) svn co https://svn.apache.org/repos/asf/geronimo/server/branches/2.2
g22
Note: for Windows, extract to a drive root to minimize the path length
used, like C:\g22
2) cd g22
3) mvn clean install -DfailIfNoTests=false -Dtest=

Next, build GEP 2.2.0 (but not the testsuite) -
1) svn co
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
gep-trunk
2) cd gep-trunk
3) mvn clean install

If all went well, then you can try running the testsuite -
1) cd testsuite
2) mvn clean install

-Donald

Fei LI wrote:
> Hi Kevan,
>
> I am so glad to have your answer. Yes, I sent to everyone because I do

> not know if my email reached anybody. I always get my own email back.
> I do not know what that means. Blocked? Bumped? Accepted but nobody
answer?

>
> After you fix it, can you simply give me what procedure to follow? I
> need a success build without error.
>
> 1. which Maven version to try.
> 2. which SVN path to retrieve source code.
> 3. which Maven commend to use: "mvn clean install -Ptestsuite"
>
>
> Thanks
>
> Fei Li
>
> ----------------------------------------------------------------------
> --
> *From:* Kevan Miller [mailto:kevan.miller@...]
> *Sent:* Wednesday, November 04, 2009 11:19 AM
> *To:* Geronimo Dev
> *Cc:* Fei LI
> *Subject:* Re: help
>
> Hi Fei,
> Please try and limit your email topics to a single mailing list.
>
> Donald Woods responded to your first question as follows:
>
> On Nov 3, 2009, at 8:05 PM, Donald Woods wrote:
>
>> Before building the Eclipse Plugins (GEP 2.2.0) you'll need to build
>> a Geronimo 2.2-SNAPSHOT server locally (from geronimo/brnaches/2.2),
>> as the artifacts out on the SNAPSHOT repo are really old. I've
>> started a build to publish the latest 2.2-SNAPSHOT artifacts out, to
>> get one last one out there before we have a 2.2 RC to start testing,
>> but it'll take several hours for the publish to finish. The best
>> bet, is to always build the latest server code before trying to build

GEP....
>
> I haven't tried to build devtools, recently. Will give it a try...
>
> --kevan

RE: Help me

2009-11-06T05:11:35Z

Hi Forrest,

I got build error for you. My environment are;
1. Windows Vista
2. Java jsdk1.5.0_22
3. Maven 2.2.1
4. SVN source? http://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/
5. mvn command mvn clean install -Dtest=false -e

"
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor:
1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager getting plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin': Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid descriptor:
1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1544)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1503)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1282)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Plugin 'org.codehaus.mojo.jspc:jspc-maven-plugin:2.0-alpha-1-20070806' has an invalid d
escriptor:
1) Plugin's descriptor contains the wrong version: 2.0-alpha-1-SNAPSHOT
at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:330)
at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:224)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:184)
at org.apache.maven.plugin.DefaultPluginManager.loadPluginDescriptor(DefaultPluginManager.java:1642)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1540)
... 18 more
"

________________________________

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 8:20 PM
To: user@...
Subject: Re: Help me

On Fri, Nov 6, 2009 at 11:40 AM, Fei LI <FLI@...> wrote:

Hi Forrest,

Thanks for your help first. Let me build server first the build eclipse plugin second. Because I tried many SVN and no one working. So let me put my question in such way. Tell me if you know, the newest version you know it will be built without error, I have Windows XP and Vista.
1. for server:
1.1 which java version? sun jdk 1.5 latest

1.2 which maven version? 2.2.1

1.3 which SVN source? http://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

1.4. which mvn command? mvn clean install -Dtest=false -e

Besides, you need to pay attention to these:
1. if using sun jdk, you need to set MAVEN_OPTS as documentation. If using ibm jdk, you won't do that
2. checkout the source code in a short path name as Donald pointed out
3. In your DOS window, change your locale to en_US by executing: chcp 437
and then start to build server.

1. for Eclipse plugin:
1.1 which java version?
1.2 which maven version?
1.3 which SVN source?
1.4. which mvn command?

Please try to make server built successfully, then let's see how to build GEP.

Good luck!

I will do whatever you suggest and to see if I luck or not.

Thanks

Fei Li

________________________________

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 7:20 PM
To: user@...
Subject: Re: Help me

Before building geronimo eclipse plugin(gep), you need to build geronimo server first.

Suggest you start with a released code tree to build gep, not the trunk code. Generally, trunk code is changing and unstable.

For a better understanding what you are doing, pls tell:
1. which version of geronimo you are going to work on?
2. what jdk you are using to build gep?
3. Any error when you are building geronimo server?

Forrest

winmail.dat (12K) Download Attachment

Re: Help me

2009-11-06T02:03:26Z

I just update the page[1] in G2.2 doc to make it more clear for users when they're trying to build a 2.2 server.

[1] http://cwiki.apache.org/GMOxDOC22/building-geronimo-with-maven.html

Thanks Xasima for spotting this out.

Jeff C

On Fri, Nov 6, 2009 at 5:48 PM, Forrest Xia <forrestxm@...> wrote:

Hi Xasima,

Seems to me you are building geronimo 3.0 from the trunk. If you tend to build G 2.2, you are supposed to check out from http://svn.apache.org/repos/asf/geronimo/server/branches/2.2/.

Forrest

Re: Help me

2009-11-06T01:48:42Z

Hi Xasima,

Seems to me you are building geronimo 3.0 from the trunk. If you tend to build G 2.2, you are supposed to check out from http://svn.apache.org/repos/asf/geronimo/server/branches/2.2/.

Forrest

Re: Help me

2009-11-06T01:39:23Z

Hello. I have troubles to build geronimo 2.2 from sources as well.
Failed to build for revision 833325 without test. It's seems to be the same error as noted in http://old.nabble.com/-BUILD--trunk:-Failed-for-Revision:-831062-td26119050s134.html
-----------------------------------
[root@build-server dist]# uname -a
Linux build-server 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:47:32 EDT 2009 i686 i686 i386 GNU/Linux

[root@build-server dist]# java -version
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)

[root@build-server dist]# mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 17:16:01-0200)
Java version: 1.6.0_16
Java home: /usr/java/jdk1.6.0_16/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.18-164.el5xen" arch: "i386" Family: "unix"

[root@build-server dist]# ant -version
Apache Ant version 1.7.1 compiled on June 27 2008

[root@build-server dist]# bash
[root@build-server dist]# export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m"
[root@build-server dist]# echo $MAVEN_OPTS
-Xmx512m -XX:MaxPermSize=128m

[root@build-server dist]# svn co https://svn.apache.org/repos/asf/geronimo/server/trunk server
.............
Checked out revision 833325.

[root@build-server dist]# mvn clean install -Dtest=false -e
............................

[INFO] Unable to find resource 'org.apache.servicemix.bundles:bundles-pom:pom:4-SNAPSHOT' in repository apache.snapshots (http://repository.apache.org/snapshots)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT

Reason: Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT

[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
codehaus.snapshots (http://snapshots.repository.codehaus.org),
central (http://repo1.maven.org/maven2)

Path to dependency:
        1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT
        2) org.apache.geronimo.framework:geronimo-common:jar:3.0-SNAPSHOT
        3) org.apache.geronimo.framework:geronimo-kernel:jar:3.0-SNAPSHOT

        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1607)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeHandlersInPlugins(DefaultLifecycleExecutor.java:1468)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:222)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:178)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar:2.1_3_3-SNAPSHOT

from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
codehaus.snapshots (http://snapshots.repository.codehaus.org),
central (http://repo1.maven.org/maven2)

Path to dependency:
        1) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:3.0-SNAPSHOT
        2) org.apache.geronimo.framework:geronimo-common:jar:3.0-SNAPSHOT
        3) org.apache.geronimo.framework:geronimo-kernel:jar:3.0-SNAPSHOT

        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:430)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:435)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:316)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304)
        at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:835)
        at org.apache.maven.plugin.DefaultPluginManager.loadPluginFully(DefaultPluginManager.java:1629)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.loadPluginFully(DefaultLifecycleExecutor.java:1582)
        ... 15 more
Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:jar': Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
        at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200)
        at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:94)
        at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:387)
        ... 23 more
Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.servicemix.bundles:bundles-pom for project: org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT for project org.apache.servicemix.bundles:org.apache.servicemix.bundles.cglib:bundle:2.1_3_3-SNAPSHOT
        at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396)
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823)
        at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255)
        at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163)
        ... 25 more
Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.servicemix.bundles:bundles-pom' not found in repository: Unable to download the artifact from any repository

org.apache.servicemix.bundles:bundles-pom:pom:4-SNAPSHOT

from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
codehaus.snapshots (http://snapshots.repository.codehaus.org),
central (http://repo1.maven.org/maven2)

for project org.apache.servicemix.bundles:bundles-pom
        at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605)
        at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392)
        ... 28 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository

org.apache.servicemix.bundles:bundles-pom:pom:4-SNAPSHOT

from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
codehaus.snapshots (http://snapshots.repository.codehaus.org),
central (http://repo1.maven.org/maven2)

        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
        at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:558)
        ... 29 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository
        at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:404)
        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:216)
        ... 31 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 minute 49 seconds
[INFO] Finished at: Fri Nov 06 07:30:49 GMT-02:00 2009
[INFO] Final Memory: 80M/144M
[INFO] ------------------------------------------------------------------------
[root@system-gwa server]#

On Fri, Nov 6, 2009 at 6:20 AM, Forrest Xia <forrestxm@...> wrote:

On Fri, Nov 6, 2009 at 11:40 AM, Fei LI <FLI@...> wrote:

Hi Forrest,

Thanks for your help first. Let me build server first the build eclipse plugin second. Because I tried many SVN and no one working. So let me put my question in such way. Tell me if you know, the newest version you know it will be built without error, I have Windows XP and Vista.

1. for server:

1.1 which java version? sun jdk 1.5 latest

1.2 which maven version? 2.2.1

1.3 which SVN source? http://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

1.4. which mvn command? mvn clean install -Dtest=false -e

Besides, you need to pay attention to these:
1. if using sun jdk, you need to set MAVEN_OPTS as documentation. If using ibm jdk, you won't do that
2. checkout the source code in a short path name as Donald pointed out
3. In your DOS window, change your locale to en_US by executing: chcp 437
and then start to build server.

1. for Eclipse plugin:

1.1 which java version?

1.2 which maven version?

1.3 which SVN source?

1.4. which mvn command?

Please try to make server built successfully, then let's see how to build GEP.

Good luck!

I will do whatever you suggest and to see if I luck or not.

Thanks

Fei Li

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 7:20 PM
To: user@...
Subject: Re: Help me

Before building geronimo eclipse plugin(gep), you need to build geronimo server first.

Suggest you start with a released code tree to build gep, not the trunk code. Generally, trunk code is changing and unstable.

For a better understanding what you are doing, pls tell:
1. which version of geronimo you are going to work on?
2. what jdk you are using to build gep?
3. Any error when you are building geronimo server?

Forrest

--
Best regards,
~ Xasima ~

Re: Help me

2009-11-05T20:20:07Z

On Fri, Nov 6, 2009 at 11:40 AM, Fei LI <FLI@...> wrote:

Hi Forrest,

Thanks for your help first. Let me build server first the build eclipse plugin second. Because I tried many SVN and no one working. So let me put my question in such way. Tell me if you know, the newest version you know it will be built without error, I have Windows XP and Vista.

1. for server:

1.1 which java version? sun jdk 1.5 latest

1.2 which maven version? 2.2.1

1.3 which SVN source? http://svn.apache.org/repos/asf/geronimo/server/tags/2.1.4/

1.4. which mvn command? mvn clean install -Dtest=false -e

1. for Eclipse plugin:

1.1 which java version?

1.2 which maven version?

1.3 which SVN source?

1.4. which mvn command?

Please try to make server built successfully, then let's see how to build GEP.

Good luck!

I will do whatever you suggest and to see if I luck or not.

Thanks

Fei Li

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 7:20 PM
To: user@...
Subject: Re: Help me

Before building geronimo eclipse plugin(gep), you need to build geronimo server first.

Suggest you start with a released code tree to build gep, not the trunk code. Generally, trunk code is changing and unstable.

For a better understanding what you are doing, pls tell:
1. which version of geronimo you are going to work on?
2. what jdk you are using to build gep?
3. Any error when you are building geronimo server?

Forrest

RE: Help me

2009-11-05T19:40:39Z

Hi Forrest,

Thanks for your help first. Let me build server first the build eclipse plugin second. Because I tried many SVN and no one working. So let me put my question in such way. Tell me if you know, the newest version you know it will be built without error, I have Windows XP and Vista.

1. for server:

1.1 which java version?

1.2 which maven version?

1.3 which SVN source?

1.4. which mvn command?

1. for Eclipse plugin:

1.1 which java version?

1.2 which maven version?

1.3 which SVN source?

1.4. which mvn command?

I will do whatever you suggest and to see if I luck or not.

Thanks

Fei Li

From: Forrest Xia [mailto:forrestxm@...]
Sent: Thu 05/11/2009 7:20 PM
To: user@...
Subject: Re: Help me

Before building geronimo eclipse plugin(gep), you need to build geronimo server first.

Suggest you start with a released code tree to build gep, not the trunk code. Generally, trunk code is changing and unstable.

For a better understanding what you are doing, pls tell:
1. which version of geronimo you are going to work on?
2. what jdk you are using to build gep?
3. Any error when you are building geronimo server?

Forrest

Re: Help me

2009-11-05T19:20:10Z

Re: The need for pooling beans

2009-11-05T15:07:38Z

Yes, it does! Thank you! It was not just a question but also an opinion.

Sometimes I need transaction and security (so I need EJB according to Sun), but I'd prefer not to have pooling. If I only needed a Singleton I could do it by myself but it wouldn't be an EJB, so yes, sometimes I need this new Singleton EJB that's about to come.

In fact, I think by and large we don't need pooling so, prior to EJB 3.1, is it a good idea to use EJB for all my Bussiness Objects or only for a few? That's what I'm pointing out. I'm not sure about that general need for pooling... even when Sun and App Server vendors are so proud about their bean pools, it doesn't mean I need it.

On the other hand I don't see why you say:
>> That's because servlets are unmanaged components.
As far as I see this has nothing to do. I insist, Spring showed everybody we can live without pooled beans, and it's even better for the 90% of times. Managed or unmanaged components. In fact future Singleton EJBs will be manged components too.

>>Spring might not have pooling, but this isn't necessary on the client side.
I'm afraid I don't you what you mean. Please, why do you talk about the client side? I only say that most of the times we don't have any problem if different threads or even different clients are using the same object at a time. In a near future we'll have Singleton EJB, but for many years we've been told how lucky we were to have pooled beans... for so many years this was not the way (except for a few cases). Don't you agree?

>>The container manages this for you. This is another example of why SLSBs are pooled.
Yes, this is why they say they pool SLSBs, but the problem is that it's not needed. Spring manages for you access to objects (by IoC) and it doesn't mean that those objects should have been pooled. Of course it's good to use pools in some situations, but when you follow the Sun official path (for example, if you want to study for the Sun Certificate Enterprise Architect as I'm doing) you are told that for any application big enough not to use only Servlets/JSP you need an EJB container. And you read the J2EE Core Patterns and you may end up believing you need pooled beans for a Session Facade and similar cases... do you think that's true? Thounsands of Spring applications use singletons even for DAOs. I may be missing something, but as far as I can see it's like using a Ferrari to go to the bathroom. But please, I really think there's something I must be missing and I'd like to be taught.

Sorry if I talk about Spring, it's because it's the most famous alternative. Thank you very much!

Re: help

2009-11-04T21:10:38Z

Hi,

If you want to build GEP source code, you can try "mvn clean install" without "-Ptestsuite". Testsuite is unstable, so you can skip it.

2009/11/4 Fei LI <FLI@...>

Hi,

I am 100% new.

I could not find help anywhere. Anybody can tell me where is my help?

Thanks first.

I want to learn geronimo and do some develop for it if possible. I followed the instruction from apache-geronimo page "How to Build Geronimo Eclipse Plugin from Source"

1. installed Apache Maven 2.0.9
2.get source code from
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
3. set MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m 3. run command mvn clean install -Ptestsuite.

I always got error, missing something or run test error.

Thanks

Fei Li

--
Best Regards,

Delos

Re: [Geronimo 2.1] add a Queue JNDI ref in ejb-jar.xml? sending JMS from an EJB/MDB

2009-11-04T17:52:57Z

Hi,

You can refer to the Geronimo documentation for instructions about all kinds of deployment plans in Geronimo. This is the link of relevant topics in the G doc: http://cwiki.apache.org/GMOxDOC22/creating-deployment-plans.html.

Hope it helps.

Ellen

2009/10/23 easyl <easy.lin@...>

OK, I found a quick fix....

in ejb-jar.xml

<enterprise-beans>

<message-driven>
<ejb-name>jms/myMDB</ejb-name>

.....

<resource-env-ref>

<resource-env-ref-name>jms/anotherQueue</resource-env-ref-name>

<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>

</message-driven>
</enterprise-beans>

I must admit, I still don't understand how to write a correct deployment
plan. I just goggle, copy, paste.....and mix up those deployment plans.

--
View this message in context: http://www.nabble.com/-Geronimo-2.1--add-a-Queue-JNDI-ref-in-ejb-jar.xml--sending-JMS-from-an-EJB-MDB-tp26025166s134p26026848.html

Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: The need for pooling beans

2009-11-04T10:12:28Z

I'm not sure I understand your question?

But why to use bean pooling for a Session Facade (implemented with a SLSB)?
We can't assure that two clients using the same method of a service bean
will bring problems.

Which is why you're only allowed one bean per request. This way you can rely on the variables not being changed by another thread.

In fact, that's the idea behind servlets: only one
instance per servlet. Clients use the same servlet instance at a time.

That's because servlets are unmanaged components. You have to use the different servlet contexts to process the request into a response, ex. the SessionContext. It's a much older spec and designed to be free/flexible.

The EJB spec on the other hand was designed to be managed components. Many resources can be injected into a bean which are building blocks for JavaEE, some of which might not allow concurrent calls themselves, you can't know for sure so it's a general policy to not allow concurrent calls on the same instance. Pooling the SLSBs ensures that the request can be processed and it's members won't be accessed concurrently. The container can guarantee safety for both thread safe and non thread safe resources if it uses this policy. EJBs also provide managed transactions, which won't be possible if 2 concurrent calls were to use the same injected DB connection. There are many reasons, all related to concurrency in some way for why SLSBs are pooled.

With a servlets these things are all responsibilities of the developer, ie. servlets are unmanaged. I guess one reason for this is because servlets were made for a protocol which is much older, ie. HTTP. So to stay compatible with and provide all the functionality available to it they left the developer with this freedom. To ease this burden many people have written frameworks to follow a chosen design, and effectively making managed components.out of your webapp components.

Of
course there will be cases where it's good to ask for a new instance of a
bean (or create it or whatever), for example, when we know we have
not-shareable resources, like an instance variable that is a DB connection.

The container manages this for you. This is another example of why SLSBs are pooled. If you want fine grained control over the life cycle of your components, you can use SFSBs or use an alternative system inside the SLSB, like Spring beans or an instance manager component which your SLSBs query for instances of the component.

But that's not to assume that EVERY SLSB has to be pooled. It may bring more
handicaps than advantages...

This is true. Many people have simple SLSBs which would work just as well, if not better when there is only a single instance with no concurrency control, which is what was addressed EJB3.1 resulting in the Singleton EJB (annotated with javax.ejb.Singleton).

Does this answer your question?

help

2009-11-04T07:41:44Z

help

Hi,

I am 100% new.

I could not find help anywhere. Anybody can tell me where is my help?

Thanks first.

I want to learn geronimo and do some develop for it if possible. I followed the instruction from apache-geronimo page "How to Build Geronimo Eclipse Plugin from Source"

1. installed Apache Maven 2.0.9
2.get source code from
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
3. set MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m 3. run command mvn clean install -Ptestsuite.

I always got error, missing something or run test error.

Thanks

Fei Li

Help me

2009-11-04T07:22:13Z

Hi,

I am 100% new.

I could not find help anywhere. Anybody can tell me where is my help?

Thanks first.

I want to learn geronimo and do some develop for it if possible. I
followed the instruction from apache-geronimo page "How to Build
Geronimo Eclipse Plugin from Source"

1. installed Apache Maven 2.0.9
2.get source code from
http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/trunk
3. set MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
3. run command mvn clean install -Ptestsuite.

I always got error, missing something or run test error.

Thanks

Fei Li

Re: The need for pooling beans

2009-11-04T06:07:10Z

Thank you for your reply. By the way two comments:

Quintin Beukes-2 wrote:

I'm not sure if the same applies to calling different business methods on the same
SLSB, though I don't think it does.

It does. It's not possible that two clients are using the same SLSB at a time, even if they're using different methods. Imagine what would happen if method B was called inside method A and two clients were using methods A and B of the same instance.. they could end up in the same method of the same bean.

Quintin Beukes-2 wrote:

...if 2 clients request to invoke the same business method on the same bean
at the same time, one will be served first, while the other will block. When
the first one returns the 2nd caller will be released to invoke the method.
The pooling of SLSB is to avoid this, so with a given pool size of X you can
have X concurrent business method invocations for any given bean...

Yes, that's true. And I understand this idea in case of, for example, DB connection pooling: a)Connetions are created before your request them and you reuse them. b) There will never be two clients trying to use the same connection. c) There SHOULD never be a client waiting for other clients to release a connection.

But why to use bean pooling for a Session Facade (implemented with a SLSB)? We can't assure that two clients using the same method of a service bean will bring problems. In fact, that's the idea behind servlets: only one instance per servlet. Clients use the same servlet instance at a time. Of course there will be cases where it's good to ask for a new instance of a bean (or create it or whatever), for example, when we know we have not-shareable resources, like an instance variable that is a DB connection. But that's not to assume that EVERY SLSB has to be pooled. It may bring more handicaps than advantages...

Re: The need for pooling beans

2009-11-04T03:39:52Z

Hey,

IIUC a stateless session bean instance can have only caller at a given time. So if 2 clients request to invoke the same business method on the same bean at the same time, one will be served first, while the other will block. When the first one returns the 2nd caller will be released to invoke the method. The pooling of SLSB is to avoid this, so with a given pool size of X you can have X concurrent business method invocations for any given bean. I'm not sure if the same applies to calling different business methods on the same SLSB, though I don't think it does.

Spring might not have pooling, but this isn't necessary on the client side. Spring proxies the actual invocation to the server anyway so the requests/pooling will be handled by the server. If you are using Spring inside your SLSBs to do lookups of other beans, you might end up with problems if Spring is configured to return Singleton instances of that Spring Bean. If this is what you're doing, rather configure it to return a unique instance for every Spring Bean lookup, so you could benefit from the SB pooling of the server, or use a unique ApplicationContext inside every SLSB instance - though the former is probably a better option.

Quintin Beukes

On Wed, Nov 4, 2009 at 1:19 PM, Antonio Fornié <sitaronocturnal@...> wrote:

> IIUC ejb 3.1 includes singleton ejbs. I don't know much about them.

Yes, I knew it. It will be very usefull when it arrives. By now we have to
take other ways :)

> This is wrong. Each client gets a separate copy of the SLSB so that
> indeed they can have instance variables and separate requests don't
> interfere with each other. I won't try to comment on how useful
> instance variables are in an object called exactly once, but that is
> the design.

I think having variable instances in a SLSB for state values is not a good
idea, eventhough you can do it by your own risk. I even think in O'Reilly
Enterprise JavaBeans 3.0 book I read it was contraindicated. If you put a
value in a variable instance, when next client for this SLSB instance use
calls a method, the value will be there and the method invoked should
initialize it again or at least ignore it.

Of course you should have variable instances for other EJBs, DB connections,
configuration parameters and so on... but never a variable meant to be
changed during the execution of a method. So, in which scenario would it a
problem to have two threads (and two clients) using the same SLSB instance?
Or in others words, in which scenario could I have concurrence problems
inside a SLSB?

What I mean is, Spring doesn't have beans pooled and it doesn't seem to be a
problem. Why is it so important to have SLSB pooled?

Thank you all for your replies!
--
View this message in context: http://old.nabble.com/The-need-for-pooling-beans-tp26156648s134p26194495.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: The need for pooling beans

2009-11-04T03:19:07Z

> IIUC ejb 3.1 includes singleton ejbs. I don't know much about them.

Yes, I knew it. It will be very usefull when it arrives. By now we have to take other ways :)

> This is wrong. Each client gets a separate copy of the SLSB so that
> indeed they can have instance variables and separate requests don't
> interfere with each other. I won't try to comment on how useful
> instance variables are in an object called exactly once, but that is
> the design.

I think having variable instances in a SLSB for state values is not a good idea, eventhough you can do it by your own risk. I even think in O'Reilly Enterprise JavaBeans 3.0 book I read it was contraindicated. If you put a value in a variable instance, when next client for this SLSB instance use calls a method, the value will be there and the method invoked should initialize it again or at least ignore it.

Of course you should have variable instances for other EJBs, DB connections, configuration parameters and so on... but never a variable meant to be changed during the execution of a method. So, in which scenario would it a problem to have two threads (and two clients) using the same SLSB instance? Or in others words, in which scenario could I have concurrence problems inside a SLSB?

What I mean is, Spring doesn't have beans pooled and it doesn't seem to be a problem. Why is it so important to have SLSB pooled?

Thank you all for your replies!

Re: how to Undeploy JMS Resource Group

2009-11-04T00:49:25Z

Hi,

Are you using Geronimo v2.2?

You can refer to this topic in the Geronimo v2.2 documentation: http://cwiki.apache.org/GMOxDOC22/using-activemq-wizard.html.

To remove a JMS Resource Group you created, finish the following steps:

On the left navigation panel, select J2EE connectors;
Click Uninstall behind the JMS resource to be uninstalled, for example console.jms/jmsResources/1.0/car.

Hope it helps. Cheers!

Ellen

2009/11/4 JohnInJax <juan.mcpeek@...>

Hi,
I didn't have any trouble creating a JMS Resource Group. But now I need to
remove it. I don't see where I can do that. I am new to Geronimo so I am not
sure where everything is at.
Thanks in advance,

John
--
View this message in context: http://old.nabble.com/how-to-Undeploy-JMS-Resource-Group-tp26181112s134p26181112.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Trying to set up a MDB

2009-11-03T21:42:44Z

Hi Antonio,

I looked the G doc and downloaded the file "jms-mdb-ear-2.1.2.ear" from maven repository as you did, and got the same problem as you. However, I have found the solution and made the sample work.

First, the structure of the file "jms-mdb-ear-2.1.2.ear" that worked for me is as below:

|-jms-mdb-ear-{version}.ear
   |- META-INF
       |- application.xml
       |- geronimo-application.xml
   |- geronimo-activemq-ra-{geronimoVersion}.rar
       |- activemq-core-{version}.jar
       |- activemq-ra-{version}.jar
       |- META -INF
           |- ra.xml
   |- jms-mdb-ejb-{version}.jar
       |- classes
       |- META -INF
           |- openejb-jar.xml
   |- jms-mdb-war-{version}.war
       |- index.jsp
       |- error.jsp
       |- WEB-INF
           |- web.xml
           |- classes
   |- jms-resources.xml

All the .xml files mentioned above are needed. For the correct contents of "geronimo-application.xml", "openejb-jar.xml", "web.xml", and "jms-resources.xml", please download the sample applications from http://www.ibm.com/developerworks/downloads/ws/wasce/?S_TACT=105AGX01&S_CMP=LP and refer to the corresponding .xml files in the "jms-mdb" sample application. I added the .xml files in the sample application directly to my "jms-mdb-ear-2.1.2.ear" file and it worked for me.

When you compress all the files with the correct contents in the struture mention above, it should work for you. If there is still problems, please let us know.

About the Geronimo document of the jms-mdb sample, we will revise it accordingly. Thank you!

Ellen

2009/11/3 Antonio Fornié <sitaronocturnal@...>

Thank you very much. I'll try with those samples I've just downloaded.

And about the samples from geronimo docs, I've just downloaded the file
"jms-mdb-ear-2.1.2.ear" from maven repository and try to deploy it from the
console... I had the same problem!!

Deployment failed:
A connector module must be deployed using a Geronimo deployment plan (either
META-INF/geronimo-ra.xml in the RAR file or a standalone deployment plan
passed to the deployer).

How can it be the sample in the doc is not working? That's what I meant when
I said Geronimo was a "little" hard at the beginning... Thank you!
--

View this message in context: http://old.nabble.com/Trying-to-set-up-a-MDB-tp26137988s134p26158715.html

Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

how to Undeploy JMS Resource Group

2009-11-03T18:41:05Z

Hi,
I didn't have any trouble creating a JMS Resource Group. But now I need to remove it. I don't see where I can do that. I am new to Geronimo so I am not sure where everything is at.
Thanks in advance,

John

Re: 2.2 in production

2009-11-03T10:10:52Z

Hey,

This isn't related to this problem. Just figured I'd mention it.

The hostnames for the members are printed as tcp://{-64, -88, 1, 60}:4000. I checked it out and this is because it makes the hostname like so:

this.hostname = org.apache.catalina.tribes.util.Arrays.toString(host);

Where "host" is a byte[]. So the 192 as a signed 8bit gives -64. Is it supposed to be like this or should I fix/report it?

Quintin Beukes

On Tue, Nov 3, 2009 at 5:35 PM, Trygve Hardersen <trygve@...> wrote:

On Mon, Nov 2, 2009 at 5:39 PM, Kevan Miller <kevan.miller@...> wrote:

Thanks Gianny. I'd like to see this included in the Geronimo 2.2 release. Can we look for a new WADI release, soon? Once we know the problem is fixed?

Trygve, the sooner we get confirmation that your issue is resolved, the sooner we can start finalizing the 2.2 release.

--kevan

I've now built Geronimo using the 2.2-SNAPSHOT of WADI and installed it on our test environment. No obvious issues so I'll go ahead and deploy this to production either later this evening (EU time) or tomorrow. Then it needs to run for a few days before I can confirm if the issue has really been resolved.

BTW I got this on our test system:

AS-000:
16:23:17,773 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.

16:23:17,897 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]

AS-001:
16:23:18,446 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.

16:23:18,456 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]

And then:

AS-000
16:30:02,576 INFO [ChannelInterceptorBase] memberDisappeared:tcp://{-64, -88, 1, 61}:4000
16:30:02,577 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing

16:30:02,600 INFO [SimpleStateManager]
=============================
New Partition Balancing
Partition Balancing
   Size [24]
   Partition[0] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[1] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[2] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[3] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[4] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[5] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[6] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[7] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[8] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[9] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[10] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[11] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[12] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[13] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[14] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[15] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[16] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[17] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[18] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[19] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[20] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[21] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
   Partition[22] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

   Partition[23] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]
=============================

16:30:02,888 WARN [TcpFailureDetector] Member added, even though we werent notified:org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=2221072,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]

16:30:02,889 INFO [ChannelInterceptorBase] memberAdded:tcp://{-64, -88, 1, 61}:4000

AS-001
Nothing....

There is practically no load on this network. Anyway I'll try this with load and see what happens.

Many thanks again!

Trygve

Re: 2.2 in production

2009-11-03T07:35:40Z

On Mon, Nov 2, 2009 at 5:39 PM, Kevan Miller <kevan.miller@...> wrote:

Thanks Gianny. I'd like to see this included in the Geronimo 2.2 release. Can we look for a new WADI release, soon? Once we know the problem is fixed?

Trygve, the sooner we get confirmation that your issue is resolved, the sooner we can start finalizing the 2.2 release.

--kevan

I've now built Geronimo using the 2.2-SNAPSHOT of WADI and installed it on our test environment. No obvious issues so I'll go ahead and deploy this to production either later this evening (EU time) or tomorrow. Then it needs to run for a few days before I can confirm if the issue has really been resolved.

BTW I got this on our test system:

AS-000:

16:23:17,773 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.

16:23:17,897 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=1814258,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]

AS-001:

16:23:18,446 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.

16:23:18,456 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 60}:4000,{-64, -88, 1, 60},4000, alive=2500759,id={107 -64 91 -23 109 93 75 116 -95 109 110 22 -85 53 -52 85 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]

And then:

AS-000

16:30:02,576 INFO [ChannelInterceptorBase] memberDisappeared:tcp://{-64, -88, 1, 61}:4000

16:30:02,577 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing

16:30:02,600 INFO [SimpleStateManager]

=============================

New Partition Balancing

Partition Balancing

Size [24]

Partition[0] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[1] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[2] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[3] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[4] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[5] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[6] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[7] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[8] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[9] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[10] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[11] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[12] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[13] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[14] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[15] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[16] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[17] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[18] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[19] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[20] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[21] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[22] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

Partition[23] owned by [TribesPeer [AS-000; tcp://192.168.1.60:4000]]; version [3]; mergeVersion [0]

=============================

16:30:02,888 WARN [TcpFailureDetector] Member added, even though we werent notified:org.apache.catalina.tribes.membership.MemberImpl[tcp://{-64, -88, 1, 61}:4000,{-64, -88, 1, 61},4000, alive=2221072,id={50 18 86 10 111 -47 79 83 -108 -4 82 -8 26 82 -79 -59 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]

16:30:02,889 INFO [ChannelInterceptorBase] memberAdded:tcp://{-64, -88, 1, 61}:4000

AS-001

Nothing....

There is practically no load on this network. Anyway I'll try this with load and see what happens.

Many thanks again!

Trygve

Re: Trying to set up a MDB

2009-11-02T15:48:57Z

Thank you very much. I'll try with those samples I've just downloaded.

And about the samples from geronimo docs, I've just downloaded the file "jms-mdb-ear-2.1.2.ear" from maven repository and try to deploy it from the console... I had the same problem!!

Deployment failed:
A connector module must be deployed using a Geronimo deployment plan (either META-INF/geronimo-ra.xml in the RAR file or a standalone deployment plan passed to the deployer).

How can it be the sample in the doc is not working? That's what I meant when I said Geronimo was a "little" hard at the beginning... Thank you!

Re: Trying to set up a MDB

2009-11-02T15:48:14Z

Re: Trying to set up a MDB

2009-11-02T15:47:58Z

Re: The need for pooling beans

2009-11-02T08:57:07Z

On Nov 2, 2009, at 1:47 AM, Antonio Fornié wrote:

Hello!

I'd like to know about the real need for pooling SLSB. I think a SLSB is
meant to have not shared data (not instance variables or so), it only has
methods that can be invoked from several clients at a time, right?

This is wrong. Each client gets a separate copy of the SLSB so that indeed they can have instance variables and separate requests don't interfere with each other. I won't try to comment on how useful instance variables are in an object called exactly once, but that is the design.

Whay
can't my clients shared the same object? If there's no problem in more than
one thread using the same method of the same object (SLSB) at the same time,
why to have some SLSBs pooled instead of a singleton?

IIUC ejb 3.1 includes singleton ejbs. I don't know much about them.

thanks

david jencks

I find it's necessary in cases where the SLSB has for example a DB
connection as an instance variable, that should not be used by more than one
thread at the same time, but it's only for those kinds of cases?

Thank you very much!

Antonio
--
View this message in context: http://old.nabble.com/The-need-for-pooling-beans-tp26156648s134p26156648.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: 2.2 in production

2009-11-02T08:39:43Z

On Nov 2, 2009, at 9:52 AM, Trygve Hardersen wrote:

> Hi Gianny
>
> Many thanks for you help!
>
> I'll try to make a Geronimo build that uses this WADI version the
> next time we update our servers. Will let you know what I find.
>
> The session size in our application should be small as only a couple
> of simple objects are put there, though I've not really verified
> this. I would not say the servers are not under any significant load
> when the messages start appearing, but again this is hard to
> quantify. CPU and bandwidth is not constrained at least.

Thanks Gianny. I'd like to see this included in the Geronimo 2.2
release. Can we look for a new WADI release, soon? Once we know the
problem is fixed?

Trygve, the sooner we get confirmation that your issue is resolved,
the sooner we can start finalizing the 2.2 release.

--kevan

Re: Trying to set up a MDB

2009-11-02T07:41:50Z

I've tested the WebSphere Community Edition Sample Applications downloaded from
http://www.ibm.com/developerworks/downloads/ws/wasce/?S_TACT=105AGX01&S_CMP=LP
and works with Geronimo 2.1.4

Re: 2.2 in production

2009-11-02T06:52:40Z

Hi Gianny

Many thanks for you help!

I'll try to make a Geronimo build that uses this WADI version the next time we update our servers. Will let you know what I find.

The session size in our application should be small as only a couple of simple objects are put there, though I've not really verified this. I would not say the servers are not under any significant load when the messages start appearing, but again this is hard to quantify. CPU and bandwidth is not constrained at least.

Trygve

On Sun, Nov 1, 2009 at 10:53 AM, Gianny Damour <gianny.damour@...> wrote:

Hi Trygve,

Thanks for reporting these problems with comprehensive log messages; they were very helpful to diagnose.

The bug causing the inability to reliably restart without downtime has been identified and fixed. I just deployed new WADI 2.2-SNAPSHOT artifacts, which can be found there:

http://snapshots.repository.codehaus.org/org/codehaus/wadi/

Can you please confirm that this is now working as expected within your environment?

Regarding the warning message

16:22:43,524 WARN [UpdateReplicationCommand] Update has not been properly cascaded due to a communication failure. If a targeted node has been lost, state will be re-balanced automatically.

the timeout is not exposed via API. Even if this warning message is displayed, an update message has actually been queued for delivery to the relevant back-up nodes. However, there is no guarantee that in case of failure, the cluster will be able to restore the latest session state as the latest update message may not have actually been delivered to back-up nodes.

I conducted load-testing on a single computer. As the network traffic going through the loopback interface does not actually touch the network card, this is a problem I was never able to observe.

Do you have an idea of the traffic volume when this warning message starts to appear? Also, do you have an idea of the session size?

Thanks,
Gianny

On 31/10/2009, at 3:39 AM, Trygve Hardersen wrote:

Hello

We have been using Geronimo 2.2-SNAPSHOT in production for a good month now, and I thought I'd share some experiences with the community, and maybe get some help. We are an online backup service, check out jottabackup.com if you're interested.

Generally our experience has been very positive. We're using the GBean framework for custom server components, the DB connection pools against MySQL databases, stateless service EJBs and various MDB, and of course the web tier (Jetty). Everything is running smoothly and we're very much looking forward to 2.2 being released so we can "release" our own software.

The issues we're having are related to WADI clustering with Jetty. First we can't use Jetty7 because of GERONIMO-4846, so we're using Jetty6 which works fine. The more serious issue is that we often can not update our servers without downtime. This is what happens:

We have 2 application servers (AS-000 and AS-001) running dynamic WADI HTTP session replication between them. When updating we first stop one, AS-000 in this case. That works fine and the active sessions are migrated to AS-001:

23:43:18,160 INFO [SimpleStateManager]
=============================
New Partition Balancing
Partition Balancing
Size [24]
Partition[0] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[1] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[2] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[3] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[4] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[5] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[6] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[7] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[8] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[9] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[10] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[11] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[12] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[13] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[14] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[15] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[16] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[17] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[18] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[19] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[20] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[21] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[22] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
Partition[23] owned by [TribesPeer [AS-001; tcp://10.0.10.101:4000]]; version [3]; mergeVersion [0]
=============================

23:43:28,539 INFO [TcpFailureDetector] Verification complete. Member disappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 0, 10, 100}:4000,{10, 0, 10, 100},4000, alive=41104531,id={-4 -32 54 90 -109 -17 65 64 -117 40 -110 -14 36 93 -12 -118 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]
23:43:28,540 INFO [ChannelInterceptorBase] memberDisappeared:tcp://{10, 0, 10, 100}:4000

We then update AS-000 and try to start it, but it fails to rejoin the WADI cluster:

23:46:30,784 INFO [ReceiverBase] Receiver Server Socket bound to:/10.0.10.100:4000
23:46:30,864 INFO [ChannelInterceptorBase] memberStart local:org.apache.catalina.tribes.membership.MemberImpl[tcp://10.0.10.100:4000,10.0.10.100,4000, alive=0,id={-103 34 80 -19 68 -51 70 -91 -108 39 -84 65 50 50 103 -107 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ] notify:false peer:AS-000
23:46:30,868 INFO [McastService] Setting cluster mcast soTimeout to 500
23:46:30,908 INFO [McastService] Sleeping for 1000 milliseconds to establish cluster membership, start level:4
23:46:31,139 INFO [ChannelInterceptorBase] memberAdded:tcp://{10, 0, 10, 101}:4000
23:46:31,908 INFO [McastService] Done sleeping, membership established, start level:4
23:46:31,912 INFO [McastService] Sleeping for 1000 milliseconds to establish cluster membership, start level:8
23:46:31,927 INFO [BufferPool] Created a buffer pool with max size:104857600 bytes of type:org.apache.catalina.tribes.io.BufferPool15Impl
23:46:32,912 INFO [McastService] Done sleeping, membership established, start level:8
23:46:32,912 INFO [ChannelInterceptorBase] memberStart local:org.apache.catalina.tribes.membership.MemberImpl[tcp://10.0.10.100:4000,10.0.10.100,4000, alive=272,id={-103 34 80 -19 68 -51 70 -91 -108 39 -84 65 50 50 103 -107 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ] notify:false peer:AS-000
23:46:37,848 INFO [DiscStore] Creating directory: /usr/lib/jotta/jotta-as-prod-1.0-SNAPSHOT/var/temp/SessionStore
23:46:37,930 INFO [BasicSingletonServiceHolder] [TribesPeer [AS-000; tcp://10.0.10.100:4000]] owns singleton service [PartitionManager for ServiceSpace [/]]
23:46:37,964 INFO [BasicSingletonServiceHolder] [TribesPeer [AS-000; tcp://10.0.10.100:4000]] resigns ownership of singleton service [PartitionManager for ServiceSpace [/]]
23:47:40,065 ERROR [BasicServiceRegistry] Error while starting [Holder for service [org.codehaus.wadi.location.partitionmanager.SimplePartitionManager@7dc2445f] named [PartitionManager] in space [ServiceSpace [/]]]
org.codehaus.wadi.location.partitionmanager.PartitionManagerException: Partition [0] is unknown.
at org.codehaus.wadi.location.partitionmanager.SimplePartitionManager.waitForBoot(SimplePartitionManager.java:248)
at org.codehaus.wadi.location.partitionmanager.SimplePartitionManager.start(SimplePartitionManager.java:119)
at org.codehaus.wadi.servicespace.basic.BasicServiceHolder.start(BasicServiceHolder.java:60)
at org.codehaus.wadi.servicespace.basic.BasicServiceRegistry.start(BasicServiceRegistry.java:152)
at org.codehaus.wadi.servicespace.basic.BasicServiceSpace.start(BasicServiceSpace.java:169)
at org.apache.geronimo.clustering.wadi.BasicWADISessionManager.doStart(BasicWADISessionManager.java:125)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:948)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538)
at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:493)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815)
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.gbean.GBeanLifecycle$$EnhancerByCGLIB$$628b9237.startConfiguration(<generated>)
at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
at org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
23:47:40,078 ERROR [BasicWADISessionManager] Failed to stop
org.codehaus.wadi.servicespace.ServiceSpaceNotFoundException: ServiceSpaceName not found
at org.codehaus.wadi.servicespace.basic.BasicServiceSpaceRegistry.unregister(BasicServiceSpaceRegistry.java:55)
at org.codehaus.wadi.servicespace.basic.BasicServiceSpace.unregisterServiceSpace(BasicServiceSpace.java:228)
at org.codehaus.wadi.servicespace.basic.BasicServiceSpace.stop(BasicServiceSpace.java:175)
at org.apache.geronimo.clustering.wadi.BasicWADISessionManager.doFail(BasicWADISessionManager.java:134)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:978)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:538)
at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:493)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34)
at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130)
at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:815)
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.gbean.GBeanLifecycle$$EnhancerByCGLIB$$628b9237.startConfiguration(<generated>)
at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:161)
at org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:78)
at org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main(MainConfigurationBootstrapper.java:45)
at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)

After this failure the server stops. Over at the running instance AS-001 this is logged:

23:46:31,909 INFO [ChannelInterceptorBase] memberAdded:tcp://{10, 0, 10, 100}:4000
23:46:37,929 INFO [BasicSingletonServiceHolder] [TribesPeer [AS-001; tcp://10.0.10.101:4000]] owns singleton service [PartitionManager for ServiceSpace [/]]
23:46:37,929 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:46:38,438 ERROR [BasicEnvelopeDispatcherManager] problem dispatching message
java.lang.IllegalArgumentException: org.codehaus.wadi.core.store.BasicStoreMotable is not a Session
at org.codehaus.wadi.replication.manager.basic.SessionStateHandler.newExtractFullStateExternalizable(SessionStateHandler.java:105)
at org.codehaus.wadi.replication.manager.basic.SessionStateHandler.extractFullState(SessionStateHandler.java:53)
at org.codehaus.wadi.replication.manager.basic.CreateStorageCommand.execute(CreateStorageCommand.java:45)
at org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updateSecondaries(SyncSecondaryManager.java:169)
at org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updateSecondaries(SyncSecondaryManager.java:114)
at org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updateSecondaries(SyncSecondaryManager.java:103)
at org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updateSecondariesFollowingJoiningPeer(SyncSecondaryManager.java:75)
at org.codehaus.wadi.replication.manager.basic.ReOrganizeSecondariesListener.receive(ReOrganizeSecondariesListener.java:53)
at org.codehaus.wadi.servicespace.basic.BasicServiceMonitor.notifyListeners(BasicServiceMonitor.java:124)
at org.codehaus.wadi.servicespace.basic.BasicServiceMonitor.processLifecycleEvent(BasicServiceMonitor.java:141)
at org.codehaus.wadi.servicespace.basic.BasicServiceMonitor$ServiceLifecycleEndpoint.dispatch(BasicServiceMonitor.java:148)
at org.codehaus.wadi.group.impl.ServiceEndpointWrapper.dispatch(ServiceEndpointWrapper.java:50)
at org.codehaus.wadi.group.impl.BasicEnvelopeDispatcherManager$DispatchRunner.run(BasicEnvelopeDispatcherManager.java:121)
at org.codehaus.wadi.servicespace.basic.BasicServiceSpaceDispatcher$ExecuteInThread.execute(BasicServiceSpaceDispatcher.java:102)
at org.codehaus.wadi.group.impl.BasicEnvelopeDispatcherManager.onEnvelope(BasicEnvelopeDispatcherManager.java:100)
at org.codehaus.wadi.group.impl.AbstractDispatcher.doOnEnvelope(AbstractDispatcher.java:104)
at org.codehaus.wadi.group.impl.AbstractDispatcher.onEnvelope(AbstractDispatcher.java:100)
at org.codehaus.wadi.servicespace.basic.ServiceSpaceEndpoint.dispatch(ServiceSpaceEndpoint.java:49)
at org.codehaus.wadi.group.impl.ServiceEndpointWrapper.dispatch(ServiceEndpointWrapper.java:50)
at org.codehaus.wadi.group.impl.BasicEnvelopeDispatcherManager$DispatchRunner.run(BasicEnvelopeDispatcherManager.java:121)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
23:46:40,063 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:46:42,938 WARN [BasicPartitionBalancerSingletonService] Rebalancing has failed
org.codehaus.wadi.group.MessageExchangeException: No correlated messages received within [5000]ms
at org.codehaus.wadi.group.impl.AbstractDispatcher.attemptMultiRendezVous(AbstractDispatcher.java:174)
at org.codehaus.wadi.location.balancing.BasicPartitionBalancer.fetchBalancingInfoState(BasicPartitionBalancer.java:85)
at org.codehaus.wadi.location.balancing.BasicPartitionBalancer.balancePartitions(BasicPartitionBalancer.java:69)
at org.codehaus.wadi.location.balancing.BasicPartitionBalancerSingletonService.run(BasicPartitionBalancerSingletonService.java:85)
at java.lang.Thread.run(Thread.java:619)
23:46:42,939 WARN [BasicPartitionBalancerSingletonService] Will retry rebalancing in [500] ms
23:46:43,439 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:47:40,269 INFO [TcpFailureDetector] Verification complete. Member disappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 0, 10, 100}:4000,{10, 0, 10, 100},4000, alive=69401,id={-103 34 80 -19 68 -51 70 -91 -108 39 -84 65 50 50 103 -107 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]
23:47:40,271 INFO [ChannelInterceptorBase] memberDisappeared:tcp://{10, 0, 10, 100}:4000
23:47:40,271 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing

If I try to start AS-000 again the same thing happens. If we stop AS-001 the following is logged;

23:49:18,695 INFO [SimpleStateManager] Evacuating partitions
23:49:18,699 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:49:23,698 WARN [SimpleStateManager] Partition balancer has disappeared - backing off for [1000]ms
23:49:24,699 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:49:29,698 WARN [SimpleStateManager] Partition balancer has disappeared - backing off for [1000]ms
23:49:30,699 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:49:35,699 WARN [SimpleStateManager] Partition balancer has disappeared - backing off for [1000]ms
23:49:36,700 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:49:41,699 WARN [SimpleStateManager] Partition balancer has disappeared - backing off for [1000]ms
23:49:42,701 INFO [BasicPartitionBalancerSingletonService] Queueing partition rebalancing
23:49:47,700 WARN [SimpleStateManager] Partition balancer has disappeared - backing off for [1000]ms
23:49:48,700 INFO [SimpleStateManager] Evacuated
23:49:48,808 INFO [AbstractExclusiveContextualiser] Unloaded sessions=[36]
23:49:48,843 INFO [AbstractExclusiveContextualiser] Unloaded sessions=[13]
23:49:58,852 INFO [BasicSingletonServiceHolder] [TribesPeer [AS-001; tcp://10.0.10.101:4000]] resigns ownership of singleton service [PartitionManager for ServiceSpace [/]]

, however AS-001 then just hangs, and we have to kill the process to get it stopped. After this we can start AS-000, update AS-001 and it always seems to have no problem joining the cluster thereafter. The strange thing is that this problem does not always occur, sometimes everything goes fine. I can't find a consistent pattern but I've tried stopping AS-001 before AS-000, and I'm sure no serializable object in the session has changed between the updated and running instance.

My gut feeling is that this is either a concurrency-related bug in WADI or a network-timeout related problem. During normal operation I'm sometimes seeing messages like this in the log files:

17:14:08,869 INFO [TcpFailureDetector] Received memberDisappeared[org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 0, 10, 101}:4000,{10, 0, 10, 101},4000, alive=95659954,id={-52 -76 98 22 10 71 76 -72 -122 -59 -21 -29 44 -86 38 114 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]] message. Will verify.
17:14:08,870 INFO [TcpFailureDetector] Verification complete. Member still alive[org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 0, 10, 101}:4000,{10, 0, 10, 101},4000, alive=95659954,id={-52 -76 98 22 10 71 76 -72 -122 -59 -21 -29 44 -86 38 114 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]
And lately, as traffic has increased, errors like this:

16:22:43,524 WARN [UpdateReplicationCommand] Update has not been properly cascaded due to a communication failure. If a targeted node has been lost, state will be re-balanced automatically.
org.codehaus.wadi.servicespace.ServiceInvocationException: org.codehaus.wadi.group.MessageExchangeException: No correlated messages received within [2000]ms
at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory$ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:209)
at org.codehaus.wadi.replication.storage.ReplicaStorage$$EnhancerByCGLIB$$a901e91b.mergeUpdate(<generated>)
at org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.cascadeUpdate(UpdateReplicationCommand.java:93)
at org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.run(UpdateReplicationCommand.java:86)
at org.codehaus.wadi.replication.manager.basic.SyncReplicationManager.update(SyncReplicationManager.java:138)
at org.codehaus.wadi.replication.manager.basic.LoggingReplicationManager.update(LoggingReplicationManager.java:100)
at org.codehaus.wadi.core.session.AbstractReplicableSession.onEndProcessing(AbstractReplicableSession.java:49)
at org.codehaus.wadi.core.session.AtomicallyReplicableSession.onEndProcessing(AtomicallyReplicableSession.java:58)
at org.apache.geronimo.clustering.wadi.WADISessionAdaptor.onEndAccess(WADISessionAdaptor.java:77)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionManager.complete(ClusteredSessionManager.java:60)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:198)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.doHandle(ClusteredSessionHandler.java:59)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler$ActualHandler.handle(ClusteredSessionHandler.java:66)
at org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler$WebClusteredInvocation.invokeLocally(AbstractClusteredPreHandler.java:71)
at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler$WADIWebClusteredInvocation.access$000(WADIClusteredPreHandler.java:52)
at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler$WADIWebClusteredInvocation$1.doFilter(WADIClusteredPreHandler.java:64)
at org.codehaus.wadi.web.impl.WebInvocation.invoke(WebInvocation.java:116)
at org.codehaus.wadi.core.contextualiser.MemoryContextualiser.handleLocally(MemoryContextualiser.java:71)
at org.codehaus.wadi.core.contextualiser.AbstractExclusiveContextualiser.handle(AbstractExclusiveContextualiser.java:94)
at org.codehaus.wadi.core.contextualiser.AbstractMotingContextualiser.contextualise(AbstractMotingContextualiser.java:37)
at org.codehaus.wadi.core.manager.StandardManager.processStateful(StandardManager.java:150)
at org.codehaus.wadi.core.manager.StandardManager.contextualise(StandardManager.java:142)
at org.codehaus.wadi.core.manager.ClusteredManager.contextualise(ClusteredManager.java:81)
at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler$WADIWebClusteredInvocation.invoke(WADIClusteredPreHandler.java:72)
at org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler.handle(AbstractClusteredPreHandler.java:39)
at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.handle(ClusteredSessionHandler.java:51)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access$101(TwistyWebAppContext.java:41)
at org.apache.geronimo.jetty6.handler.TwistyWebAppContext$TwistyHandler.handle(TwistyWebAppContext.java:66)
at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46)
at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58)
at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48)
at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle(TwistyWebAppContext.java:60)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:344)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.codehaus.wadi.group.MessageExchangeException: No correlated messages received within [2000]ms
at org.codehaus.wadi.group.impl.AbstractDispatcher.attemptMultiRendezVous(AbstractDispatcher.java:174)
at org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invokeOnPeers(BasicServiceInvoker.java:90)
at org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invoke(BasicServiceInvoker.java:69)
at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory$ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:193)
... 49 more

Does anyone have some insight into what might be causing this, or where the timeouts can be increased if there are any?

I'm thinking that a static WADI configuration can be more stable than the dynamic setup we have not which relies upon multicasting. Does anyone have experience with similar setups?

Thanks!

Trygve Hardersen - Jotta

Re: Trying to set up a MDB

2009-11-02T06:00:07Z

Hi, two issues I noticed in your application:

1) you need to use geronimo-applicaiton.xml for your ear to be deployed on Geronimo successfully, which shall be put in the same directory with application-xml
2) jms resource should have a module name in the form of groupId/artifactId/version/type

The plans for your reference:

geronimo-application.xml

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-2.0">
    <environment xmlns="http://geronimo.apache.org/xml/ns/deployment-1.2">
        <moduleId>
            <groupId>org.apache.geronimo.samples</groupId>
            <artifactId>jms-mdb-ear</artifactId>
            <version>2.1.4</version>
            <type>car</type>
        </moduleId>
    </environment>
    <module>
       <connector>geronimo-activemq-ra-2.1.4.rar</connector>
       <alt-dd>jms-resources.xml</alt-dd>
    </module>
</application>

jms-resources.xml (this file should be placed under root instead of /root/META-INF)

<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2">
            <dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
                <dep:moduleId>
                    <dep:groupId>org.apache.geronimo.samples</dep:groupId>
                    <dep:artifactId>jms-resources</dep:artifactId>
                    <dep:version>2.1.4</dep:version>
                    <dep:type>rar</dep:type>
                </dep:moduleId>
                <dep:dependencies>
                    <dep:dependency>
                        <dep:groupId>org.apache.geronimo.configs</dep:groupId>
                        <dep:artifactId>activemq-broker</dep:artifactId>
                        <dep:type>car</dep:type>
                    </dep:dependency>
                </dep:dependencies>
            </dep:environment>
            <resourceadapter>
                <resourceadapter-instance>
                    <resourceadapter-name>jms-resources</resourceadapter-name>
                    <nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
                        <nam:gbean-link>DefaultWorkManager</nam:gbean-link>
                    </nam:workmanager>
                </resourceadapter-instance>
                <outbound-resourceadapter>
                    <connection-definition>
                        <connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
                        <connectiondefinition-instance>
                            <name>OrderConnectionFactory</name>
                            <implemented-interface>javax.jms.QueueConnectionFactory</implemented-interface>
                            <implemented-interface>javax.jms.TopicConnectionFactory</implemented-interface>
                            <connectionmanager>
                                <xa-transaction>
                                    <transaction-caching/>
                                </xa-transaction>
                                <single-pool>
                                    <match-one/>
                                </single-pool>
                            </connectionmanager>
                        </connectiondefinition-instance>
                    </connection-definition>
                </outbound-resourceadapter>
            </resourceadapter>
            <adminobject>
                <adminobject-interface>javax.jms.Queue</adminobject-interface>
                <adminobject-class>org.apache.activemq.command.ActiveMQQueue</adminobject-class>
                <adminobject-instance>
                    <message-destination-name>OrderQueue</message-destination-name>
                    <config-property-setting name="PhysicalName">OrderQueue</config-property-setting>
                </adminobject-instance>
            </adminobject>
            <adminobject>
                <adminobject-interface>javax.jms.Topic</adminobject-interface>
                <adminobject-class>org.apache.activemq.command.ActiveMQTopic</adminobject-class>
            </adminobject>
</connector>

Furthermore, you may check out this URL to find out the exact plans for jms-mdb sample application.

https://svn.apache.org/repos/asf/geronimo/samples/branches/2.1/samples/jms-mdb/

Any questions, please let us know.

Jeff C

On Mon, Nov 2, 2009 at 8:18 PM, Antonio Fornié <sitaronocturnal@...> wrote:

Any help? If nobody can help for my specific problem, at least can anybody
help me setting up this basic sample (I think it's the easier one in the
docs):

http://cwiki.apache.org/GMOxDOC21/jms-mdb-jms-and-mdb-sample-application.html

Did anybody get it running only following the tutorial? Isn't there anything
missing? I tried to follow the tutorial setp by step several times but it
was never working.

Otherwise, can anybody recommend me another tutorial or another way to have
JMS and an MDB running easier than this one?

Thank you very much!

Antonio
--

View this message in context: http://old.nabble.com/Trying-to-set-up-a-MDB-tp26137988s134p26156693.html

Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Trying to set up a MDB

2009-11-02T04:18:05Z

Any help? If nobody can help for my specific problem, at least can anybody help me setting up this basic sample (I think it's the easier one in the docs):
http://cwiki.apache.org/GMOxDOC21/jms-mdb-jms-and-mdb-sample-application.html

Did anybody get it running only following the tutorial? Isn't there anything missing? I tried to follow the tutorial setp by step several times but it was never working.

Otherwise, can anybody recommend me another tutorial or another way to have JMS and an MDB running easier than this one?

Thank you very much!

Antonio

The need for pooling beans

2009-11-02T01:47:55Z

Hello!

I'd like to know about the real need for pooling SLSB. I think a SLSB is meant to have not shared data (not instance variables or so than shouldn't be shared), it only has methods that can be invoked from several clients at a time, right? Why can't my clients shared the same SLSB object? If there's no problem in more than one thread using the same method of the same object (SLSB) at the same time, why to have some SLSBs pooled instead of a singleton?

I find it's necessary in cases where the SLSB has for example a DB connection as an instance variable, that should not be used by more than one thread at the same time, but it's only for those kinds of cases?

Thank you very much!

Antonio

Re: 2.2 in production

2009-11-01T01:53:40Z

Hi Trygve,

Thanks for reporting these problems with comprehensive log messages;
they were very helpful to diagnose.

The bug causing the inability to reliably restart without downtime
has been identified and fixed. I just deployed new WADI 2.2-SNAPSHOT
artifacts, which can be found there:

http://snapshots.repository.codehaus.org/org/codehaus/wadi/

Can you please confirm that this is now working as expected within
your environment?

Regarding the warning message

> 16:22:43,524 WARN [UpdateReplicationCommand] Update has not been
> properly cascaded due to a communication failure. If a targeted
> node has been lost, state will be re-balanced automatically.

the timeout is not exposed via API. Even if this warning message is
displayed, an update message has actually been queued for delivery to
the relevant back-up nodes. However, there is no guarantee that in
case of failure, the cluster will be able to restore the latest
session state as the latest update message may not have actually been
delivered to back-up nodes.

I conducted load-testing on a single computer. As the network traffic
going through the loopback interface does not actually touch the
network card, this is a problem I was never able to observe.

Do you have an idea of the traffic volume when this warning message
starts to appear? Also, do you have an idea of the session size?

Thanks,
Gianny

On 31/10/2009, at 3:39 AM, Trygve Hardersen wrote:

> Hello
>
> We have been using Geronimo 2.2-SNAPSHOT in production for a good
> month now, and I thought I'd share some experiences with the
> community, and maybe get some help. We are an online backup
> service, check out jottabackup.com if you're interested.
>
> Generally our experience has been very positive. We're using the
> GBean framework for custom server components, the DB connection
> pools against MySQL databases, stateless service EJBs and various
> MDB, and of course the web tier (Jetty). Everything is running
> smoothly and we're very much looking forward to 2.2 being released
> so we can "release" our own software.
>
> The issues we're having are related to WADI clustering with Jetty.
> First we can't use Jetty7 because of GERONIMO-4846, so we're using
> Jetty6 which works fine. The more serious issue is that we often
> can not update our servers without downtime. This is what happens:
>
> We have 2 application servers (AS-000 and AS-001) running dynamic
> WADI HTTP session replication between them. When updating we first
> stop one, AS-000 in this case. That works fine and the active
> sessions are migrated to AS-001:
>
> 23:43:18,160 INFO [SimpleStateManager]
> =============================
> New Partition Balancing
> Partition Balancing
> Size [24]
> Partition[0] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[1] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[2] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[3] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[4] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[5] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[6] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[7] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[8] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[9] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[10] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[11] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[12] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[13] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[14] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[15] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[16] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[17] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[18] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[19] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[20] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[21] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[22] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> Partition[23] owned by [TribesPeer [AS-001; tcp://
> 10.0.10.101:4000]]; version [3]; mergeVersion [0]
> =============================
>
> 23:43:28,539 INFO [TcpFailureDetector] Verification complete.
> Member disappeared[org.apache.catalina.tribes.membership.MemberImpl
> [tcp://{10, 0, 10, 100}:4000,{10, 0, 10, 100},4000,
> alive=41104531,id={-4 -32 54 90 -109 -17 65 64 -117 40 -110 -14 36
> 93 -12 -118 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)},
> command={66 65 66 89 45 65 76 69 88 ...(9)}, domain={74 79 84 84 65
> 95 87 65 68 ...(10)}, ]]
> 23:43:28,540 INFO [ChannelInterceptorBase] memberDisappeared:tcp://
> {10, 0, 10, 100}:4000
>
> We then update AS-000 and try to start it, but it fails to rejoin
> the WADI cluster:
>
> 23:46:30,784 INFO [ReceiverBase] Receiver Server Socket bound to:/
> 10.0.10.100:4000
> 23:46:30,864 INFO [ChannelInterceptorBase] memberStart
> local:org.apache.catalina.tribes.membership.MemberImpl[tcp://
> 10.0.10.100:4000,10.0.10.100,4000, alive=0,id={-103 34 80 -19 68
> -51 70 -91 -108 39 -84 65 50 50 103 -107 }, payload={-84 -19 0 5
> 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95
> 87 65 68 ...(10)}, ] notify:false peer:AS-000
> 23:46:30,868 INFO [McastService] Setting cluster mcast soTimeout
> to 500
> 23:46:30,908 INFO [McastService] Sleeping for 1000 milliseconds to
> establish cluster membership, start level:4
> 23:46:31,139 INFO [ChannelInterceptorBase] memberAdded:tcp://{10,
> 0, 10, 101}:4000
> 23:46:31,908 INFO [McastService] Done sleeping, membership
> established, start level:4
> 23:46:31,912 INFO [McastService] Sleeping for 1000 milliseconds to
> establish cluster membership, start level:8
> 23:46:31,927 INFO [BufferPool] Created a buffer pool with max size:
> 104857600 bytes of type:org.apache.catalina.tribes.io.BufferPool15Impl
> 23:46:32,912 INFO [McastService] Done sleeping, membership
> established, start level:8
> 23:46:32,912 INFO [ChannelInterceptorBase] memberStart
> local:org.apache.catalina.tribes.membership.MemberImpl[tcp://
> 10.0.10.100:4000,10.0.10.100,4000, alive=272,id={-103 34 80 -19 68
> -51 70 -91 -108 39 -84 65 50 50 103 -107 }, payload={-84 -19 0 5
> 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95
> 87 65 68 ...(10)}, ] notify:false peer:AS-000
> 23:46:37,848 INFO [DiscStore] Creating directory: /usr/lib/jotta/
> jotta-as-prod-1.0-SNAPSHOT/var/temp/SessionStore
> 23:46:37,930 INFO [BasicSingletonServiceHolder] [TribesPeer
> [AS-000; tcp://10.0.10.100:4000]] owns singleton service
> [PartitionManager for ServiceSpace [/]]
> 23:46:37,964 INFO [BasicSingletonServiceHolder] [TribesPeer
> [AS-000; tcp://10.0.10.100:4000]] resigns ownership of singleton
> service [PartitionManager for ServiceSpace [/]]
> 23:47:40,065 ERROR [BasicServiceRegistry] Error while starting
> [Holder for service
> [org.codehaus.wadi.location.partitionmanager.SimplePartitionManager@7d
> c2445f] named [PartitionManager] in space [ServiceSpace [/]]]
> org.codehaus.wadi.location.partitionmanager.PartitionManagerException:
> Partition [0] is unknown.
> at
> org.codehaus.wadi.location.partitionmanager.SimplePartitionManager.wai
> tForBoot(SimplePartitionManager.java:248)
> at
> org.codehaus.wadi.location.partitionmanager.SimplePartitionManager.sta
> rt(SimplePartitionManager.java:119)
> at org.codehaus.wadi.servicespace.basic.BasicServiceHolder.start
> (BasicServiceHolder.java:60)
> at org.codehaus.wadi.servicespace.basic.BasicServiceRegistry.start
> (BasicServiceRegistry.java:152)
> at org.codehaus.wadi.servicespace.basic.BasicServiceSpace.start
> (BasicServiceSpace.java:169)
> at
> org.apache.geronimo.clustering.wadi.BasicWADISessionManager.doStart
> (BasicWADISessionManager.java:125)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance
> (GBeanInstance.java:948)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(
> GBeanInstanceState.java:269)
> at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start
> (GBeanInstanceState.java:103)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive
> (GBeanInstanceState.java:125)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive
> (GBeanInstance.java:538)
> at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean
> (BasicKernel.java:377)
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration
> GBeans(ConfigurationUtil.java:456)
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration
> GBeans(ConfigurationUtil.java:493)
> at
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start
> (KernelConfigurationManager.java:190)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf
> iguration(SimpleConfigurationManager.java:546)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke
> (ReflectionMethodInvoker.java:34)
> at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke
> (GBeanOperation.java:130)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke
> (GBeanInstance.java:815)
> 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.gbean.GBeanLifecycle$$EnhancerByCGLIB$
> $628b9237.startConfiguration(<generated>)
> at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup
> (EmbeddedDaemon.java:161)
> at org.apache.geronimo.system.main.EmbeddedDaemon.execute
> (EmbeddedDaemon.java:78)
> at
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main
> (MainConfigurationBootstrapper.java:45)
> at org.apache.geronimo.cli.AbstractCLI.executeMain
> (AbstractCLI.java:65)
> at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
> 23:47:40,078 ERROR [BasicWADISessionManager] Failed to stop
> org.codehaus.wadi.servicespace.ServiceSpaceNotFoundException:
> ServiceSpaceName not found
> at
> org.codehaus.wadi.servicespace.basic.BasicServiceSpaceRegistry.unregis
> ter(BasicServiceSpaceRegistry.java:55)
> at
> org.codehaus.wadi.servicespace.basic.BasicServiceSpace.unregisterServi
> ceSpace(BasicServiceSpace.java:228)
> at org.codehaus.wadi.servicespace.basic.BasicServiceSpace.stop
> (BasicServiceSpace.java:175)
> at
> org.apache.geronimo.clustering.wadi.BasicWADISessionManager.doFail
> (BasicWADISessionManager.java:134)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance
> (GBeanInstance.java:978)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(
> GBeanInstanceState.java:269)
> at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start
> (GBeanInstanceState.java:103)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive
> (GBeanInstanceState.java:125)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive
> (GBeanInstance.java:538)
> at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean
> (BasicKernel.java:377)
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration
> GBeans(ConfigurationUtil.java:456)
> at
> org.apache.geronimo.kernel.config.ConfigurationUtil.startConfiguration
> GBeans(ConfigurationUtil.java:493)
> at
> org.apache.geronimo.kernel.config.KernelConfigurationManager.start
> (KernelConfigurationManager.java:190)
> at
> org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConf
> iguration(SimpleConfigurationManager.java:546)
> at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke
> (ReflectionMethodInvoker.java:34)
> at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke
> (GBeanOperation.java:130)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke
> (GBeanInstance.java:815)
> 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.gbean.GBeanLifecycle$$EnhancerByCGLIB$
> $628b9237.startConfiguration(<generated>)
> at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup
> (EmbeddedDaemon.java:161)
> at org.apache.geronimo.system.main.EmbeddedDaemon.execute
> (EmbeddedDaemon.java:78)
> at
> org.apache.geronimo.kernel.util.MainConfigurationBootstrapper.main
> (MainConfigurationBootstrapper.java:45)
> at org.apache.geronimo.cli.AbstractCLI.executeMain
> (AbstractCLI.java:65)
> at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:30)
>
> After this failure the server stops. Over at the running instance
> AS-001 this is logged:
>
> 23:46:31,909 INFO [ChannelInterceptorBase] memberAdded:tcp://{10,
> 0, 10, 100}:4000
> 23:46:37,929 INFO [BasicSingletonServiceHolder] [TribesPeer
> [AS-001; tcp://10.0.10.101:4000]] owns singleton service
> [PartitionManager for ServiceSpace [/]]
> 23:46:37,929 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:46:38,438 ERROR [BasicEnvelopeDispatcherManager] problem
> dispatching message
> java.lang.IllegalArgumentException:
> org.codehaus.wadi.core.store.BasicStoreMotable is not a Session
> at
> org.codehaus.wadi.replication.manager.basic.SessionStateHandler.newExt
> ractFullStateExternalizable(SessionStateHandler.java:105)
> at
> org.codehaus.wadi.replication.manager.basic.SessionStateHandler.extrac
> tFullState(SessionStateHandler.java:53)
> at
> org.codehaus.wadi.replication.manager.basic.CreateStorageCommand.execu
> te(CreateStorageCommand.java:45)
> at
> org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updat
> eSecondaries(SyncSecondaryManager.java:169)
> at
> org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updat
> eSecondaries(SyncSecondaryManager.java:114)
> at
> org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updat
> eSecondaries(SyncSecondaryManager.java:103)
> at
> org.codehaus.wadi.replication.manager.basic.SyncSecondaryManager.updat
> eSecondariesFollowingJoiningPeer(SyncSecondaryManager.java:75)
> at
> org.codehaus.wadi.replication.manager.basic.ReOrganizeSecondariesListe
> ner.receive(ReOrganizeSecondariesListener.java:53)
> at
> org.codehaus.wadi.servicespace.basic.BasicServiceMonitor.notifyListene
> rs(BasicServiceMonitor.java:124)
> at
> org.codehaus.wadi.servicespace.basic.BasicServiceMonitor.processLifecy
> cleEvent(BasicServiceMonitor.java:141)
> at org.codehaus.wadi.servicespace.basic.BasicServiceMonitor
> $ServiceLifecycleEndpoint.dispatch(BasicServiceMonitor.java:148)
> at org.codehaus.wadi.group.impl.ServiceEndpointWrapper.dispatch
> (ServiceEndpointWrapper.java:50)
> at org.codehaus.wadi.group.impl.BasicEnvelopeDispatcherManager
> $DispatchRunner.run(BasicEnvelopeDispatcherManager.java:121)
> at org.codehaus.wadi.servicespace.basic.BasicServiceSpaceDispatcher
> $ExecuteInThread.execute(BasicServiceSpaceDispatcher.java:102)
> at
> org.codehaus.wadi.group.impl.BasicEnvelopeDispatcherManager.onEnvelope
> (BasicEnvelopeDispatcherManager.java:100)
> at org.codehaus.wadi.group.impl.AbstractDispatcher.doOnEnvelope
> (AbstractDispatcher.java:104)
> at org.codehaus.wadi.group.impl.AbstractDispatcher.onEnvelope
> (AbstractDispatcher.java:100)
> at
> org.codehaus.wadi.servicespace.basic.ServiceSpaceEndpoint.dispatch
> (ServiceSpaceEndpoint.java:49)
> at org.codehaus.wadi.group.impl.ServiceEndpointWrapper.dispatch
> (ServiceEndpointWrapper.java:50)
> at org.codehaus.wadi.group.impl.BasicEnvelopeDispatcherManager
> $DispatchRunner.run(BasicEnvelopeDispatcherManager.java:121)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> 23:46:40,063 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:46:42,938 WARN [BasicPartitionBalancerSingletonService]
> Rebalancing has failed
> org.codehaus.wadi.group.MessageExchangeException: No correlated
> messages received within [5000]ms
> at
> org.codehaus.wadi.group.impl.AbstractDispatcher.attemptMultiRendezVous
> (AbstractDispatcher.java:174)
> at
> org.codehaus.wadi.location.balancing.BasicPartitionBalancer.fetchBalan
> cingInfoState(BasicPartitionBalancer.java:85)
> at
> org.codehaus.wadi.location.balancing.BasicPartitionBalancer.balancePar
> titions(BasicPartitionBalancer.java:69)
> at
> org.codehaus.wadi.location.balancing.BasicPartitionBalancerSingletonSe
> rvice.run(BasicPartitionBalancerSingletonService.java:85)
> at java.lang.Thread.run(Thread.java:619)
> 23:46:42,939 WARN [BasicPartitionBalancerSingletonService] Will
> retry rebalancing in [500] ms
> 23:46:43,439 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:47:40,269 INFO [TcpFailureDetector] Verification complete.
> Member disappeared[org.apache.catalina.tribes.membership.MemberImpl
> [tcp://{10, 0, 10, 100}:4000,{10, 0, 10, 100},4000, alive=69401,id=
> {-103 34 80 -19 68 -51 70 -91 -108 39 -84 65 50 50 103 -107 },
> payload={-84 -19 0 5 115 114 0 50 111 ...(423)}, command={66 65 66
> 89 45 65 76 69 88 ...(9)}, domain={74 79 84 84 65 95 87 65 68 ...
> (10)}, ]]
> 23:47:40,271 INFO [ChannelInterceptorBase] memberDisappeared:tcp://
> {10, 0, 10, 100}:4000
> 23:47:40,271 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
>
> If I try to start AS-000 again the same thing happens. If we stop
> AS-001 the following is logged;
>
> 23:49:18,695 INFO [SimpleStateManager] Evacuating partitions
> 23:49:18,699 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:49:23,698 WARN [SimpleStateManager] Partition balancer has
> disappeared - backing off for [1000]ms
> 23:49:24,699 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:49:29,698 WARN [SimpleStateManager] Partition balancer has
> disappeared - backing off for [1000]ms
> 23:49:30,699 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:49:35,699 WARN [SimpleStateManager] Partition balancer has
> disappeared - backing off for [1000]ms
> 23:49:36,700 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:49:41,699 WARN [SimpleStateManager] Partition balancer has
> disappeared - backing off for [1000]ms
> 23:49:42,701 INFO [BasicPartitionBalancerSingletonService]
> Queueing partition rebalancing
> 23:49:47,700 WARN [SimpleStateManager] Partition balancer has
> disappeared - backing off for [1000]ms
> 23:49:48,700 INFO [SimpleStateManager] Evacuated
> 23:49:48,808 INFO [AbstractExclusiveContextualiser] Unloaded
> sessions=[36]
> 23:49:48,843 INFO [AbstractExclusiveContextualiser] Unloaded
> sessions=[13]
> 23:49:58,852 INFO [BasicSingletonServiceHolder] [TribesPeer
> [AS-001; tcp://10.0.10.101:4000]] resigns ownership of singleton
> service [PartitionManager for ServiceSpace [/]]
>
> , however AS-001 then just hangs, and we have to kill the process
> to get it stopped. After this we can start AS-000, update AS-001
> and it always seems to have no problem joining the cluster
> thereafter. The strange thing is that this problem does not always
> occur, sometimes everything goes fine. I can't find a consistent
> pattern but I've tried stopping AS-001 before AS-000, and I'm sure
> no serializable object in the session has changed between the
> updated and running instance.
>
> My gut feeling is that this is either a concurrency-related bug in
> WADI or a network-timeout related problem. During normal operation
> I'm sometimes seeing messages like this in the log files:
>
> 17:14:08,869 INFO [TcpFailureDetector] Received memberDisappeared
> [org.apache.catalina.tribes.membership.MemberImpl[tcp://{10, 0, 10,
> 101}:4000,{10, 0, 10, 101},4000, alive=95659954,id={-52 -76 98 22
> 10 71 76 -72 -122 -59 -21 -29 44 -86 38 114 }, payload={-84 -19 0 5
> 115 114 0 50 111 ...(423)}, command={}, domain={74 79 84 84 65 95
> 87 65 68 ...(10)}, ]] message. Will verify.
> 17:14:08,870 INFO [TcpFailureDetector] Verification complete.
> Member still alive[org.apache.catalina.tribes.membership.MemberImpl
> [tcp://{10, 0, 10, 101}:4000,{10, 0, 10, 101},4000,
> alive=95659954,id={-52 -76 98 22 10 71 76 -72 -122 -59 -21 -29 44
> -86 38 114 }, payload={-84 -19 0 5 115 114 0 50 111 ...(423)},
> command={}, domain={74 79 84 84 65 95 87 65 68 ...(10)}, ]]
> And lately, as traffic has increased, errors like this:
>
> 16:22:43,524 WARN [UpdateReplicationCommand] Update has not been
> properly cascaded due to a communication failure. If a targeted
> node has been lost, state will be re-balanced automatically.
> org.codehaus.wadi.servicespace.ServiceInvocationException:
> org.codehaus.wadi.group.MessageExchangeException: No correlated
> messages received within [2000]ms
> at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory
> $ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:209)
> at org.codehaus.wadi.replication.storage.ReplicaStorage$
> $EnhancerByCGLIB$$a901e91b.mergeUpdate(<generated>)
> at
> org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.c
> ascadeUpdate(UpdateReplicationCommand.java:93)
> at
> org.codehaus.wadi.replication.manager.basic.UpdateReplicationCommand.r
> un(UpdateReplicationCommand.java:86)
> at
> org.codehaus.wadi.replication.manager.basic.SyncReplicationManager.upd
> ate(SyncReplicationManager.java:138)
> at
> org.codehaus.wadi.replication.manager.basic.LoggingReplicationManager.
> update(LoggingReplicationManager.java:100)
> at
> org.codehaus.wadi.core.session.AbstractReplicableSession.onEndProcessi
> ng(AbstractReplicableSession.java:49)
> at
> org.codehaus.wadi.core.session.AtomicallyReplicableSession.onEndProces
> sing(AtomicallyReplicableSession.java:58)
> at
> org.apache.geronimo.clustering.wadi.WADISessionAdaptor.onEndAccess
> (WADISessionAdaptor.java:77)
> at
> org.apache.geronimo.jetty6.cluster.ClusteredSessionManager.complete
> (ClusteredSessionManager.java:60)
> at org.mortbay.jetty.servlet.SessionHandler.handle
> (SessionHandler.java:198)
> at
> org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.doHandle
> (ClusteredSessionHandler.java:59)
> at org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler
> $ActualHandler.handle(ClusteredSessionHandler.java:66)
> at org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler
> $WebClusteredInvocation.invokeLocally
> (AbstractClusteredPreHandler.java:71)
> at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler
> $WADIWebClusteredInvocation.access$000(WADIClusteredPreHandler.java:
> 52)
> at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler
> $WADIWebClusteredInvocation$1.doFilter(WADIClusteredPreHandler.java:
> 64)
> at org.codehaus.wadi.web.impl.WebInvocation.invoke
> (WebInvocation.java:116)
> at
> org.codehaus.wadi.core.contextualiser.MemoryContextualiser.handleLocal
> ly(MemoryContextualiser.java:71)
> at
> org.codehaus.wadi.core.contextualiser.AbstractExclusiveContextualiser.
> handle(AbstractExclusiveContextualiser.java:94)
> at
> org.codehaus.wadi.core.contextualiser.AbstractMotingContextualiser.con
> textualise(AbstractMotingContextualiser.java:37)
> at org.codehaus.wadi.core.manager.StandardManager.processStateful
> (StandardManager.java:150)
> at org.codehaus.wadi.core.manager.StandardManager.contextualise
> (StandardManager.java:142)
> at org.codehaus.wadi.core.manager.ClusteredManager.contextualise
> (ClusteredManager.java:81)
> at org.apache.geronimo.jetty6.cluster.wadi.WADIClusteredPreHandler
> $WADIWebClusteredInvocation.invoke(WADIClusteredPreHandler.java:72)
> at
> org.apache.geronimo.jetty6.cluster.AbstractClusteredPreHandler.handle(
> AbstractClusteredPreHandler.java:39)
> at
> org.apache.geronimo.jetty6.cluster.ClusteredSessionHandler.handle
> (ClusteredSessionHandler.java:51)
> at org.mortbay.jetty.handler.ContextHandler.handle
> (ContextHandler.java:765)
> at org.mortbay.jetty.webapp.WebAppContext.handle
> (WebAppContext.java:417)
> at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access
> $101(TwistyWebAppContext.java:41)
> at org.apache.geronimo.jetty6.handler.TwistyWebAppContext
> $TwistyHandler.handle(TwistyWebAppContext.java:66)
> at
> org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle
> (ThreadClassloaderHandler.java:46)
> at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle
> (InstanceContextHandler.java:58)
> at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle
> (UserTransactionHandler.java:48)
> at
> org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle
> (ComponentContextHandler.java:47)
> at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle
> (TwistyWebAppContext.java:60)
> at org.mortbay.jetty.handler.ContextHandlerCollection.handle
> (ContextHandlerCollection.java:230)
> at org.mortbay.jetty.handler.HandlerCollection.handle
> (HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle
> (HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at org.mortbay.jetty.HttpConnection.handleRequest
> (HttpConnection.java:534)
> at org.mortbay.jetty.HttpConnection$RequestHandler.content
> (HttpConnection.java:879)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at org.mortbay.io.nio.SelectChannelEndPoint.run
> (SelectChannelEndPoint.java:409)
> at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:214)
> at org.apache.geronimo.pool.ThreadPool
> $ContextClassLoaderRunnable.run(ThreadPool.java:344)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run
> (ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.codehaus.wadi.group.MessageExchangeException: No
> correlated messages received within [2000]ms
> at
> org.codehaus.wadi.group.impl.AbstractDispatcher.attemptMultiRendezVous
> (AbstractDispatcher.java:174)
> at
> org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invokeOnPeers
> (BasicServiceInvoker.java:90)
> at org.codehaus.wadi.servicespace.basic.BasicServiceInvoker.invoke
> (BasicServiceInvoker.java:69)
> at org.codehaus.wadi.servicespace.basic.CGLIBServiceProxyFactory
> $ProxyMethodInterceptor.intercept(CGLIBServiceProxyFactory.java:193)
> ... 49 more
>
> Does anyone have some insight into what might be causing this, or
> where the timeouts can be increased if there are any?
>
> I'm thinking that a static WADI configuration can be more stable
> than the dynamic setup we have not which relies upon multicasting.
> Does anyone have experience with similar setups?
>
> Thanks!
>
> Trygve Hardersen - Jotta
>
>
>
>

Re: Trying to set up a MDB

2009-10-31T15:46:10Z

Hello!

My ear structure:
root/car_web.war
root/car_ejb.jar
root/geronimo-activemq-ra-2.1.4.rar
root/META-INF/MANIFEST.MF
root/META-INF/application.xml
root/META-INF/jms-resources.xml

My application.xml is this:
------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" id="Application_ID" version="5">
<description>My MDB APP</description>
<display-name>car_ear</display-name>
<module>
<web>
<web-uri>car_web.war</web-uri>
<context-root>car_web</context-root>
</web>
</module>
<module>
<ejb>car_ejb.jar</ejb>
</module>
<module>
<connector>geronimo-activemq-ra-2.1.4.rar</connector>
</module>
</application>
------------------------------------------------------------

My ejb-jar.xml is this:
------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<display-name>car_ejb </display-name>
</ejb-jar>
------------------------------------------------------------

My open-ejb-jar.xml is this:
------------------------------------------------------------
<openejb-jar xmlns="http://openejb.apache.org/xml/ns/openejb-jar-2.2">
<enterprise-beans>
<message-driven>
<ejb-name>OrderRecvMDB</ejb-name>
<resource-adapter>
<resource-link>jms-resources</resource-link>
</resource-adapter>
</message-driven>
</enterprise-beans>
</openejb-jar>
------------------------------------------------------------

My jms-resources is this:
------------------------------------------------------------
<connector xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2">
<resourceadapter>
<resourceadapter-instance>
<resourceadapter-name>jms-resources</resourceadapter-name>
<nam:workmanager xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2">
<nam:gbean-link>DefaultWorkManager</nam:gbean-link>
</nam:workmanager>
</resourceadapter-instance>
<outbound-resourceadapter>
<connection-definition>
<connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface>
<connectiondefinition-instance>
<name>CommonConnectionFactory</name>
<implemented-interface>javax.jms.QueueConnectionFactory</implemented-interface>
<implemented-interface>javax.jms.TopicConnectionFactory</implemented-interface>
<connectionmanager>
<xa-transaction>
<transaction-caching/>
</xa-transaction>
<single-pool>
<match-one/>
</single-pool>
</connectionmanager>
</connectiondefinition-instance>
</connection-definition>
</outbound-resourceadapter>
</resourceadapter>
<adminobject>
<adminobject-interface>javax.jms.Queue</adminobject-interface>
<adminobject-class>org.apache.activemq.command.ActiveMQQueue</adminobject-class>
<adminobject-instance>
<message-destination-name>OrderQueue</message-destination-name>
<config-property-setting name="PhysicalName">OrderQueue</config-property-setting>
</adminobject-instance>
</adminobject>
</connector>
------------------------------------------------------------

After including the rar in the ear like you told I got this error message:

Deployment failed:
A connector module must be deployed using a Geronimo deployment plan (either META-INF/geronimo-ra.xml in the RAR file or a standalone deployment plan passed to the deployer).

Any help?? Thank you very much!!