Re: System Module descriptions

[David Jencks]

On Oct 3, 2007, at 6:21 PM, Prasad Kashyap wrote:


On 10/3/07, Ted Kirby <[EMAIL PROTECTED]> wrote:

Cool!  I wrote a (cough, cough) perl script to generate wiki markup
for a table from the data in the configs/*/pom.xml files, and updated
the wiki page with it.  I then produced a merged table to compare
existing pom descriptions to the ones I had entered.  I'd like to get
further input, store updated descriptions in the pom.xml description
element, and then I think it makes sense to generate a page from the
pom.xml data.  There appear to be two attributes for each that would
be nice to capture in doc:  whether the module is initially started,
and whether it should *never* be started.  I wonder if any sort of
attribute could be added for capturing this in pom.xml?


IIUC,  are you wondering if we should add attributes in the pom.xml
that will say whether this configuration is initially started or
should never be started ?

Other than for updating the wiki, will this attribute be useful for
anything else ?


I think there's already an attribute for whether the plugin gets  
started: otherwise we'd be running the client plugins in the server.


"never start" is a misnomer it might be "never start in the  
normal server" if you really never start it ever then you can  
just leave it out :-)


I'm wondering if there's a way to have the plugin descriptor direct  
its customizations to a particular kernel configuration: server  
configs going into config.xml, artifact_aliases, and config- 
substitutions, client configs going into maybe  
client_aritifact_aliases, etc etc.  If there's a way to make this  
work then a more accurate description of "never start" would be "not  
part of the server".


So I'd like to wait with the "never start" attribute until we figure  
out if this is practicable.


thanks
david jencks



Cheers
Prasad


Ted Kirby

On 10/2/07, David Jencks <[EMAIL PROTECTED]> wrote:

Nice!

In trunk, the  element in the config's pom gets put  
into

the geronimo-plugin.xml description so it really needs to be
accurate.  It would be great if we could generate future versions of
this page from the plugin catalog.  Meanwhile it might be worthwhile
comparing the descriptions here with the descriptions in the trunk
configs' poms to make sure they are consistent and the most
informative wins :-)

thanks!
david jencks

On Oct 2, 2007, at 3:05 PM, Ted Kirby wrote:


I have added this wiki page
http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the
modules that come with the (2.0.1) server, along with:

1. A brief description of what the module does
2. Is it started by default, or
3. Should it never be started?

This is a first draft.  I solicit feedback and encourage folks to
update the page as appropriate.  There are some modules with  
which I

am not familiar.

Ted Kirby

[jira] Updated: (GERONIMO-3501) The geronimo tuscany plugin cannot be started in Geronimo 2.0.1

[Raymond Feng (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng updated GERONIMO-3501:
---

Attachment: rfeng-tuscany-plugin.patch

Please review and apply the patch.

> The geronimo tuscany plugin cannot be started in Geronimo 2.0.1
> ---
>
> Key: GERONIMO-3501
> URL: https://issues.apache.org/jira/browse/GERONIMO-3501
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: Plugins
>Affects Versions: 2.0.1
>Reporter: Raymond Feng
> Fix For: 2.0.x
>
> Attachments: rfeng-tuscany-plugin.patch
>
>
> The geronimo tuscany plugin cannot be started in Geronimo 2.0.1 as 
> tuscany-definitions module is not added as dependency. There are also 
> SNAPSHOT dependencies on sdo/das. I attach a patch to fix these issues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3501) The geronimo tuscany plugin cannot be started in Geronimo 2.0.1

[Raymond Feng (JIRA)]

The geronimo tuscany plugin cannot be started in Geronimo 2.0.1
---

 Key: GERONIMO-3501
 URL: https://issues.apache.org/jira/browse/GERONIMO-3501
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: Plugins
Affects Versions: 2.0.1
Reporter: Raymond Feng
 Fix For: 2.0.x
 Attachments: rfeng-tuscany-plugin.patch

The geronimo tuscany plugin cannot be started in Geronimo 2.0.1 as 
tuscany-definitions module is not added as dependency. There are also SNAPSHOT 
dependencies on sdo/das. I attach a patch to fix these issues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Trunk fails

[Jarek Gawor]

Yep. There are actaully a few problems that I'm seeing with trunk.

1) The Windows build problem.  That's a bug in Maven where it returns
a URL that's not really a URL. But I think we can work around that in
our car-maven-plugin. For now, if you add the following to your
~/.m2/settings.xml it should work:

/C:/.m2

2) Looks like the javaee assembly contains more modules then it used
to. For example,
org.apache.geronimo.configs/uddi-jetty6/2.1-SNAPSHOT/car is now
getting installed.

3) Because more modules were installed, the startup progress bar died
with a StringIndexOutOfBoundsException. I committed a small fix for
that.

4) The "java.rmi.server.ExportException: Port already in use: 1099"
error in the app client as shown in the logs.

Jarek

On 10/3/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> I'm seeing a different trunk failure on Windows. I'm at Rev: 581764.
>
> Fresh checkout and a clean repo.
>
> http://rifers.org/paste/show/5677
>
> The automated builds on linux does not seem to have this problem. I'm
> going to verify this on another windows machine tomorrow.
>
> Cheers
> Prasad
>
> On 10/3/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> > Please see 
> > http://people.apache.org/~prasad/binaries/trunk/20071003/test-1800.log
> > for test failure. I'm seeing the same on Windows.
> >
> > Jarek
> >
> > On 3 Oct 2007 22:53:56 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > OpenEJB trunk at 581589
> > > Geronimo Revision: 581737 built with tests included
> > >
> > > See the full build-1800.log file at 
> > > http://people.apache.org/~prasad/binaries/trunk/20071003/build-1800.log
> > >
> > > Download the binaries from 
> > > http://people.apache.org/~prasad/binaries/trunk/20071003
> > > [INFO] BUILD SUCCESSFUL
> > > [INFO] 
> > > 
> > > [INFO] Total time: 31 minutes 30 seconds
> > > [INFO] Finished at: Wed Oct 03 18:36:12 EDT 2007
> > > [INFO] Final Memory: 212M/1010M
> > > [INFO] 
> > > ----
> > >
> > > TESTSUITE RESULTS (Failures only)
> > > =
> > > See detailed results at 
> > > http://people.apache.org/~prasad/testsuite/ResultsSummary.html
> > > See the full test-1800.log file at 
> > > http://people.apache.org/~prasad/binaries/trunk/20071003/test-1800.log
> > >
> > >
> > >
> >
>

[jira] Updated: (GERONIMO-3450) Unable to Run Pluto 1.1 on Geronimo 2.0

[Vamsavardhana Reddy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vamsavardhana Reddy updated GERONIMO-3450:
--

Fix Version/s: (was: 1.1.2)
   (was: 1.1.x)
   2.1
   2.0.x

> Unable to Run Pluto 1.1 on Geronimo 2.0
> ---
>
> Key: GERONIMO-3450
> URL: https://issues.apache.org/jira/browse/GERONIMO-3450
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.0-M2
> Environment: Operating System : Windows 2k3
> Pluto Version: 1.1.0
> Geronimo with Jetty Version   2.0.1 
>Reporter: Ramesh B
> Fix For: 2.0.x, 2.1
>
> Attachments: geronimo-web.xml, geronimo.log
>
>
> Hi,
> I'm new to geronimo webserver. I've been trying to deploy pluto 1.1 on 
> geronimo with jetty 2.0.1.
> For this I have done the following steps:
> 1) I've added the following additional jars to common libs before deployment:
> *  pluto-container-1.1.0.jar
> * pluto-descriptor-api-1.1.0.jar
> * pluto-descriptor-impl-1.1.0.jar
> * pluto-taglib-1.1.0.jar
> * xalan 2.6.0
> 2) I've modified the castor.properties for pluto/web-inf/classes and set all 
> parameters to false.
> 3) i've added a geronimo-web.xml to the /web-inf folder.
> I created a war of the pluto folder. however while deploying it it gives the 
> following error:
> 3582: 11:02:34,501 ERROR [log] Nested in 
> org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected 
> exception parsing XML document from ServletContext resource 
> [/WEB-INF/pluto-portal-driver-services-config.xml]; nested exception is 
> java.lang.IllegalArgumentException: Class 
> [org.apache.cxf.clustering.spring.NamespaceHandler] does not implement the 
> NamespaceHandler interface:
> After throwing this error on the console it shows as successfully deployed 
> and successfully running.
> However when i'm trying to access the pluto portal, it says service 
> unavailable.
> Please help me with this problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Trunk fails

[Prasad Kashyap]

I'm seeing a different trunk failure on Windows. I'm at Rev: 581764.

Fresh checkout and a clean repo.

http://rifers.org/paste/show/5677

The automated builds on linux does not seem to have this problem. I'm
going to verify this on another windows machine tomorrow.

Cheers
Prasad

On 10/3/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:
> Please see 
> http://people.apache.org/~prasad/binaries/trunk/20071003/test-1800.log
> for test failure. I'm seeing the same on Windows.
>
> Jarek
>
> On 3 Oct 2007 22:53:56 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > OpenEJB trunk at 581589
> > Geronimo Revision: 581737 built with tests included
> >
> > See the full build-1800.log file at 
> > http://people.apache.org/~prasad/binaries/trunk/20071003/build-1800.log
> >
> > Download the binaries from 
> > http://people.apache.org/~prasad/binaries/trunk/20071003
> > [INFO] BUILD SUCCESSFUL
> > [INFO] 
> > 
> > [INFO] Total time: 31 minutes 30 seconds
> > [INFO] Finished at: Wed Oct 03 18:36:12 EDT 2007
> > [INFO] Final Memory: 212M/1010M
> > [INFO] 
> > 
> >
> > TESTSUITE RESULTS (Failures only)
> > =
> > See detailed results at 
> > http://people.apache.org/~prasad/testsuite/ResultsSummary.html
> > See the full test-1800.log file at 
> > http://people.apache.org/~prasad/binaries/trunk/20071003/test-1800.log
> >
> >
> >
>

Trunk fails

[Jarek Gawor]

Please see 
http://people.apache.org/~prasad/binaries/trunk/20071003/test-1800.log
for test failure. I'm seeing the same on Windows.

Jarek

On 3 Oct 2007 22:53:56 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> OpenEJB trunk at 581589
> Geronimo Revision: 581737 built with tests included
>
> See the full build-1800.log file at 
> http://people.apache.org/~prasad/binaries/trunk/20071003/build-1800.log
>
> Download the binaries from 
> http://people.apache.org/~prasad/binaries/trunk/20071003
> [INFO] BUILD SUCCESSFUL
> [INFO] 
> 
> [INFO] Total time: 31 minutes 30 seconds
> [INFO] Finished at: Wed Oct 03 18:36:12 EDT 2007
> [INFO] Final Memory: 212M/1010M
> [INFO] 
> 
>
> TESTSUITE RESULTS (Failures only)
> =
> See detailed results at 
> http://people.apache.org/~prasad/testsuite/ResultsSummary.html
> See the full test-1800.log file at 
> http://people.apache.org/~prasad/binaries/trunk/20071003/test-1800.log
>
>
>

Re: System Module descriptions

[Prasad Kashyap]

On 10/3/07, Ted Kirby <[EMAIL PROTECTED]> wrote:
> Cool!  I wrote a (cough, cough) perl script to generate wiki markup
> for a table from the data in the configs/*/pom.xml files, and updated
> the wiki page with it.  I then produced a merged table to compare
> existing pom descriptions to the ones I had entered.  I'd like to get
> further input, store updated descriptions in the pom.xml description
> element, and then I think it makes sense to generate a page from the
> pom.xml data.  There appear to be two attributes for each that would
> be nice to capture in doc:  whether the module is initially started,
> and whether it should *never* be started.  I wonder if any sort of
> attribute could be added for capturing this in pom.xml?

IIUC,  are you wondering if we should add attributes in the pom.xml
that will say whether this configuration is initially started or
should never be started ?

Other than for updating the wiki, will this attribute be useful for
anything else ?

Cheers
Prasad
>
> Ted Kirby
>
> On 10/2/07, David Jencks <[EMAIL PROTECTED]> wrote:
> > Nice!
> >
> > In trunk, the  element in the config's pom gets put into
> > the geronimo-plugin.xml description so it really needs to be
> > accurate.  It would be great if we could generate future versions of
> > this page from the plugin catalog.  Meanwhile it might be worthwhile
> > comparing the descriptions here with the descriptions in the trunk
> > configs' poms to make sure they are consistent and the most
> > informative wins :-)
> >
> > thanks!
> > david jencks
> >
> > On Oct 2, 2007, at 3:05 PM, Ted Kirby wrote:
> >
> > > I have added this wiki page
> > > http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the
> > > modules that come with the (2.0.1) server, along with:
> > >
> > > 1. A brief description of what the module does
> > > 2. Is it started by default, or
> > > 3. Should it never be started?
> > >
> > > This is a first draft.  I solicit feedback and encourage folks to
> > > update the page as appropriate.  There are some modules with which I
> > > am not familiar.
> > >
> > > Ted Kirby
> >
> >
>

Re: JMS Statistics

[David Jencks]

On Oct 3, 2007, at 2:26 PM, Viet Nguyen wrote:


Hi All,

I have been poking around JMS (ActiveMQ) to see if we can surface  
some JSR-77 statistics. To my knowledge, there are not any JMS  
stats being surfaced right now. I have looked at modules/geronimo- 
activemq and am confused as to how I can get a hold of these  
statistics. I have looked at some API docs for ActiveMQ and found  
out that they actually implemented all of the JSR-77 stats on their  
side and all we should need to do is request it.


Classes such as ActiveMQConnection (http://activemq.apache.org/ 
maven/activemq-core/apidocs/org/apache/activemq/ 
ActiveMQConnection.html ) will keep track of some of the stats. By  
calling getConnectionStats() the JSR-77 stats for  
JMSConnectionStats will be returned in its updated state.


I am not a JMS/ActiveMQ expert so, if someone could tell me if  
tying classes such as ActiveMQConnection into Geronimo's source is  
a viable proposal, it will be much appreciated.


There's no problem if you do it as part of the amq integration, for  
instance in an amq console module.


Also, I've noticed that there are implementation classes for JCA  
stats in ActiveMQ too. Is there a way to get these into Geronimo?


What stats are these?

thanks
david jencks



Thanks,
Viet

JMS Statistics

[Viet Nguyen]

Hi All,

I have been poking around JMS (ActiveMQ) to see if we can surface some
JSR-77 statistics. To my knowledge, there are not any JMS stats being
surfaced right now. I have looked at modules/geronimo-activemq and am
confused as to how I can get a hold of these statistics. I have looked at
some API docs for ActiveMQ and found out that they actually implemented all
of the JSR-77 stats on their side and all we should need to do is request
it.

Classes such as ActiveMQConnection (
http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/ActiveMQConnection.html)
will keep track of some of the stats. By calling getConnectionStats() the
JSR-77 stats for JMSConnectionStats will be returned in its updated state.

I am not a JMS/ActiveMQ expert so, if someone could tell me if tying classes
such as ActiveMQConnection into Geronimo's source is a viable proposal, it
will be much appreciated.

Also, I've noticed that there are implementation classes for JCA stats in
ActiveMQ too. Is there a way to get these into Geronimo?

Thanks,
Viet

[jira] Updated: (GERONIMO-3489) Deployment problems caused by file deletion failures

[Ted Kirby (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Kirby updated GERONIMO-3489:


Attachment: G3489-3.patch

G3489-3.patch:

If the directory being created at deploy time already exists, and is empty, 
then proceed, don't throw a ConfigurationAlreadyExistsException.

> Deployment problems caused by file deletion failures
> 
>
> Key: GERONIMO-3489
> URL: https://issues.apache.org/jira/browse/GERONIMO-3489
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.0.1
>Reporter: Ted Kirby
>Assignee: Donald Woods
> Fix For: 2.0.2, 2.0.x, 2.1
>
> Attachments: G3489-1.patch, G3489-2.patch, G3489-3.patch
>
>
> File.delete() failures in IOUtil.recursiveDelete() are causing various 
> deployment problems.  I open this JIRA to discuss them to see how the server 
> might better handle them.  In all but one case, delete failures are not even 
> noted with a log record!  Deletion problems are seen in many environments and 
> platforms, but they are persistently fatal when using a NFS file system for 
> the repository.
> In investigating the problem, I have added code to recursiveDelete to retry 
> the delete a few times if it fails.  I added code to list directory contents 
> if a directory delete failed, and saw a file named 
> .nfs2bc4350053e in the directory.  My first attempt at a bypass 
> was to retry a failed delete 5 times, sleeping a second before each try.  
> This did not work.  I added a call to System.gc() before each sleep, and this 
> got me passed the problem.  Interestingly, two retries were required to get 
> this to work.  In another version, each retry was a second longer, and I 
> printed all file names in a directory before trying the delete.  This worked 
> in most cases, but required the full 5 retries, so I suspect System.gc() 
> would have time.  System.runFinalization() would be something else to try.
> RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the 
> failing end of the deletion problem, with the dreaded 
> ConfigurationAlreadyExistsException("Configuration already exists: " + 
> configId)exception.  I think this message is not good.  It should really say 
> directory already exists.  If the file is not deleted on undeploy, this 
> failure occurs on a subsequent deploy.  What is really bad is if the user 
> invokes a redeploy operation, and the file delete fails on the undeploy.  It 
> is important that undeploy not complete until the file goes away.
> From other environments, I am not convinced that all file handles and 
> references, and particularly open streams, are being closed on some 
> artifacts.  This will cause the delete to fail.  It may be that the gc() 
> calls are cleaning these up, and allowing the deletes to work in my case 
> above.
> Another option is that 
> RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a 
> ConfigurationAlreadyExistsException if the only problem is an empty directory 
> structure exists.  The next line creates the directory structure anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig resolved GERONIMO-3498.
-

Resolution: Fixed

Tested and works great, thanks for the commit Anita =)

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig closed GERONIMO-3498.
---


> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (GERONIMO-3497) collecting agent needs to turn on statistics collection for all monitored StatisticsProvider

[Viet Hung Nguyen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viet Hung Nguyen resolved GERONIMO-3497.


Resolution: Fixed

> collecting agent needs to turn on statistics collection for all monitored 
> StatisticsProvider
> 
>
> Key: GERONIMO-3497
> URL: https://issues.apache.org/jira/browse/GERONIMO-3497
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: monitoring
> Environment: windows xp
>Reporter: Viet Hung Nguyen
> Attachments: geronimo-3497.patch
>
>
> By default, all stats that can be enabled/disabled are turned off. When the 
> collecting agent is deployed, it should turn on all Stats that the admin 
> wishes to track. If not, the collecting agent will be looking at a bunch of 
> useless numbers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (DAYTRADER-56) Register of duplicate userid in EJB 3 mode not handled correctly

[Christopher James Blythe (JIRA)]

[ 
https://issues.apache.org/jira/browse/DAYTRADER-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532248
 ] 

Christopher James Blythe commented on DAYTRADER-56:
---

Spoke to some of the JPA developers and got the skinny on exceptions thrown by 
the persist method. According to them, 
the EntityExistsException during persist() will only happen if the Entity 
already exists in the PersistenceContext. Otherwise, the only way to detect 
this condition is at flush/commit time (which occurs once the session bean 
method completes).

Consequently, the only graceful way to do this is to check and see if an entity 
with the same ID exists prior (using the find() method) prior to calling 
persist().




> Register of duplicate userid in EJB 3 mode not handled correctly
> 
>
> Key: DAYTRADER-56
> URL: https://issues.apache.org/jira/browse/DAYTRADER-56
> Project: DayTrader
>  Issue Type: Bug
>  Components: EJB Tier
>Affects Versions: 2.0
>Reporter: Christopher James Blythe
>
> If you attempt to register a userid that already exists in the database, the 
> resulting error is not handled gracefully. In Direct mode, we catch the 
> resulting DuplicateKeyException and ensure that a warning is propagated to 
> the web-tier (by displaying a message on the register page).
> The register method in the TradeSLSBBean needs to be revised to handle this 
> gracefully.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Anita Kulshreshtha (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532245
 ] 

Anita Kulshreshtha commented on GERONIMO-3498:
--

Should be fixed in rev 581714

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Matt Hogstrom]

heh .. didn't mean to derail discussion.  I think what would make  
sense would be to move the web services from runtime mode to a set of  
primitives.  Does it make sense to also rework the message for what  
DayTrader is all about?



On Oct 3, 2007, at 1:34 PM, Christopher Blythe wrote:

ahh... come on matt... this is good discussion... we finally have  
people thinking (and talking) about where we should or shouldn't  
take DayTrader in the future. there hasn't been enough of that!


i think short term, the disclaimers serve the purpose. however,  
long term... daytrader will lose it's relevance if it isn't updated  
to reflect how people are using the technology.


On 10/3/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
So to cl;arify I think DayTrader may be mis-characterized as only a  
benchmark.  I think it is used for a variety of functions of which  
only one aspect is performance.  the other aspects are testing  
infrastructure, sample application (which includes deployments  
plans for various pieces of functionality, etc.).


With that in mind perhaps we should change it from performance  
benchmark to something else.  I'm concerned about pulling this at  
the very end.  I agree that we don't want to put out a sample that  
can be used inappropriately but in the end we don't really tell  
anyone what they can do with the software.  I'm concerned about  
making changes to DayTrader because of commercial positioning.  For  
this reason I'd rather add the comment about relevance of the  
runtime mode.  I think simply adding the comment is adequate.


If we're going for best practices I don't think anyone would say  
the app as it is written today is a best practice but more of a  
swiss army knife of tools.


It sounds like there are varying viewpoints so perhaps we let the  
discussion percolate and put it to a vote.


On Oct 3, 2007, at 12:25 PM, Christopher Blythe wrote:

ah now you're pointing out the distinctions between primitives  
and a real application "workload". currently, the web services  
within daytrader are presented in the context of a "workload" not  
a primitive.





--
"I say never be complete, I say stop being perfect, I say let...  
lets evolve, let the chips fall where they may." - Tyler Durden

Re: [VOTE] Release XBean 3.2

[Guillaume Nodet]

Hmm, too easy I think.
The real jars already contain these resources in META-INF.
The problem is with the source jars that are generated by maven, not
the binary jars.
I suppose the javadocs jars have the same problems.

On 10/3/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On 10/3/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > Anyone knows the easiest way to add these files ?
>
> Resource plugin, src/main/resources or mrrp (maven remote repository plugin).
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.JacekLaskowski.pl
>


-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

Re: [VOTE] Release XBean 3.2

[Jacek Laskowski]

On 10/3/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> Anyone knows the easiest way to add these files ?

Resource plugin, src/main/resources or mrrp (maven remote repository plugin).

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

2.0 documentation out of date?

[Jarek Gawor]

I was working on some security tests and I was trying to look up some
information about that in the 2.0 documentation. In a bunch of places
(4 places at least) I found a deployment descriptor that will cause a
deployment error or an out-of-date screen shot of the console.
I can fix a few of these but it seems like the 2.0 documentation needs
a closer inspection.

Jarek

Re: [VOTE] Release XBean 3.2

[Guillaume Nodet]

Anyone knows the easiest way to add these files ?

On 10/3/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On 10/1/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> > Please vote on releasing xbean 3.2.
> > Binaries / maven repo is available at:
> >http://people.apache.org/~gnodet/xbean-3.2/
> > Svn source tag is available at:
> >http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.2/
> >
> > It includes David Jencks last minute fix too.
>
> +1 if the missing legal files are added as reported by Kevan.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.JacekLaskowski.pl
>


-- 
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532235
 ] 

Erik B. Craig commented on GERONIMO-3498:
-

Ah, sorry about that. Currently not getting the new files in the SVN repo... 
and the old ones are still there, however the contents have been wiped out to 0 
bytes each, but not completely deleted. I'm not sure if it's something I did 
incorrectly in patch creation, or if it's an issue with SVN not fully picking 
up changes on the apply... but I have seen it before... You may need to do a 
quick (manual) svn delete on the mrc-client directory, and then an svn add on 
the new 'client' directory.

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release XBean 3.2

[Jacek Laskowski]

On 10/1/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> Please vote on releasing xbean 3.2.
> Binaries / maven repo is available at:
>http://people.apache.org/~gnodet/xbean-3.2/
> Svn source tag is available at:
>http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.2/
>
> It includes David Jencks last minute fix too.

+1 if the missing legal files are added as reported by Kevan.

Jacek

-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: System Module descriptions

[Ted Kirby]

This is great stuff!  Any way to extract this information for
placement on a wiki page?
I was also thinking it would be great to get this wiki page info
available on the console in text form so the administrator could read
it, say starting with module description.

Ted Kirby

On 10/3/07, Joe Bohn <[EMAIL PROTECTED]> wrote:
>
>
> Hernan Cunico wrote:
> > Hi Ted,
> > it would be great to add which modules are critical for Geronimo to run,
> > in other words, those we should never mess with. We had a discussion
> > some time ago but I don't think we ever properly covered this.
>
> I added some safety checks in the web console for this.  There is now an
> expert mode such that the stop, uninstall, restart action are only
> available on org.apache.geronimo modules when the expert box is checked.
>   I also added some more specific warnings of consequences when the
> actions are to be performed.  Of course, this only provides some safety
> for administrators when using the web console and does nothing for those
> that prefer the command line.  Then again  the web console is
> probably the place where it is a bit easier to do some damage.
>
> Joe
>
> >
> > Cheers!
> > Hernan
> >
> > Ted Kirby wrote:
> >> I have added this wiki page
> >> http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the
> >> modules that come with the (2.0.1) server, along with:
> >>
> >> 1. A brief description of what the module does
> >> 2. Is it started by default, or
> >> 3. Should it never be started?
> >>
> >> This is a first draft.  I solicit feedback and encourage folks to
> >> update the page as appropriate.  There are some modules with which I
> >> am not familiar.
> >>
> >> Ted Kirby
> >>
> >
>

[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Anita Kulshreshtha (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532234
 ] 

Anita Kulshreshtha commented on GERONIMO-3498:
--

Patch applied to rev 581709. The patch had conflicts. I was still getting the 
old patch. It is not necessary to remove the old patch.
This makes it easy to find/load the new patch.

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: System Module descriptions

[Ted Kirby]

Cool!  I wrote a (cough, cough) perl script to generate wiki markup
for a table from the data in the configs/*/pom.xml files, and updated
the wiki page with it.  I then produced a merged table to compare
existing pom descriptions to the ones I had entered.  I'd like to get
further input, store updated descriptions in the pom.xml description
element, and then I think it makes sense to generate a page from the
pom.xml data.  There appear to be two attributes for each that would
be nice to capture in doc:  whether the module is initially started,
and whether it should *never* be started.  I wonder if any sort of
attribute could be added for capturing this in pom.xml?

Ted Kirby

On 10/2/07, David Jencks <[EMAIL PROTECTED]> wrote:
> Nice!
>
> In trunk, the  element in the config's pom gets put into
> the geronimo-plugin.xml description so it really needs to be
> accurate.  It would be great if we could generate future versions of
> this page from the plugin catalog.  Meanwhile it might be worthwhile
> comparing the descriptions here with the descriptions in the trunk
> configs' poms to make sure they are consistent and the most
> informative wins :-)
>
> thanks!
> david jencks
>
> On Oct 2, 2007, at 3:05 PM, Ted Kirby wrote:
>
> > I have added this wiki page
> > http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the
> > modules that come with the (2.0.1) server, along with:
> >
> > 1. A brief description of what the module does
> > 2. Is it started by default, or
> > 3. Should it never be started?
> >
> > This is a first draft.  I solicit feedback and encourage folks to
> > update the page as appropriate.  There are some modules with which I
> > am not familiar.
> >
> > Ted Kirby
>
>

[jira] Assigned: (GERONIMO-3489) Deployment problems caused by file deletion failures

[Donald Woods (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donald Woods reassigned GERONIMO-3489:
--

Assignee: Donald Woods

> Deployment problems caused by file deletion failures
> 
>
> Key: GERONIMO-3489
> URL: https://issues.apache.org/jira/browse/GERONIMO-3489
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.0.1
>Reporter: Ted Kirby
>Assignee: Donald Woods
> Fix For: 2.0.2, 2.0.x, 2.1
>
> Attachments: G3489-1.patch, G3489-2.patch
>
>
> File.delete() failures in IOUtil.recursiveDelete() are causing various 
> deployment problems.  I open this JIRA to discuss them to see how the server 
> might better handle them.  In all but one case, delete failures are not even 
> noted with a log record!  Deletion problems are seen in many environments and 
> platforms, but they are persistently fatal when using a NFS file system for 
> the repository.
> In investigating the problem, I have added code to recursiveDelete to retry 
> the delete a few times if it fails.  I added code to list directory contents 
> if a directory delete failed, and saw a file named 
> .nfs2bc4350053e in the directory.  My first attempt at a bypass 
> was to retry a failed delete 5 times, sleeping a second before each try.  
> This did not work.  I added a call to System.gc() before each sleep, and this 
> got me passed the problem.  Interestingly, two retries were required to get 
> this to work.  In another version, each retry was a second longer, and I 
> printed all file names in a directory before trying the delete.  This worked 
> in most cases, but required the full 5 retries, so I suspect System.gc() 
> would have time.  System.runFinalization() would be something else to try.
> RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the 
> failing end of the deletion problem, with the dreaded 
> ConfigurationAlreadyExistsException("Configuration already exists: " + 
> configId)exception.  I think this message is not good.  It should really say 
> directory already exists.  If the file is not deleted on undeploy, this 
> failure occurs on a subsequent deploy.  What is really bad is if the user 
> invokes a redeploy operation, and the file delete fails on the undeploy.  It 
> is important that undeploy not complete until the file goes away.
> From other environments, I am not convinced that all file handles and 
> references, and particularly open streams, are being closed on some 
> artifacts.  This will cause the delete to fail.  It may be that the gc() 
> calls are cleaning these up, and allowing the deletes to work in my case 
> above.
> Another option is that 
> RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a 
> ConfigurationAlreadyExistsException if the only problem is an empty directory 
> structure exists.  The next line creates the directory structure anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3500) Upgrade to Derby 10.3.1.4

[Donald Woods (JIRA)]

Upgrade to Derby 10.3.1.4
-

 Key: GERONIMO-3500
 URL: https://issues.apache.org/jira/browse/GERONIMO-3500
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: databases, dependencies
Affects Versions: 2.1
Reporter: Donald Woods


http://db.apache.org/derby/releases/release-10.3.1.4.cgi

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3497) collecting agent needs to turn on statistics collection for all monitored StatisticsProvider

[Anita Kulshreshtha (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532225
 ] 

Anita Kulshreshtha commented on GERONIMO-3497:
--

patch applied in rev 581706

> collecting agent needs to turn on statistics collection for all monitored 
> StatisticsProvider
> 
>
> Key: GERONIMO-3497
> URL: https://issues.apache.org/jira/browse/GERONIMO-3497
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: monitoring
> Environment: windows xp
>Reporter: Viet Hung Nguyen
> Attachments: geronimo-3497.patch
>
>
> By default, all stats that can be enabled/disabled are turned off. When the 
> collecting agent is deployed, it should turn on all Stats that the admin 
> wishes to track. If not, the collecting agent will be looking at a bunch of 
> useless numbers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532220
 ] 

Erik B. Craig commented on GERONIMO-3498:
-

Anita - What error are you getting on attempt to apply?

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Anita Kulshreshtha (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532213
 ] 

Anita Kulshreshtha commented on GERONIMO-3498:
--

This patch attached at 11.36 A.M. does not apply.

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

pluggable admin console and jetty

[Paul McMahan]

There is a bug with Pluto's session code that only surfaces in  
Jetty.  When you view an admin console extension this bug can cause a  
IllegalStateException and require you to log back in to the console  
again.  It's not difficult to work around, but if it becomes an  
annoyance then you can build pluto/trunk/pluto-container locally with  
this patch applied :  https://issues.apache.org/jira/browse/PLUTO-436



Best wishes,
Paul

[jira] Created: (GERONIMODEVTOOLS-236) change the package name from org.apache.geronimo.j2g.* to org.apache.geronimo.devtools.j2g.*

[Lin Sun (JIRA)]

change the package name from org.apache.geronimo.j2g.* to 
org.apache.geronimo.devtools.j2g.*


 Key: GERONIMODEVTOOLS-236
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-236
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: J2G
Reporter: Lin Sun
Assignee: Lin Sun
Priority: Minor


Since j2g is part of devtools now

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3499) Expose ConnectionTimeout configuration in tomcat web connector to the user

[Lin Sun (JIRA)]

Expose ConnectionTimeout configuration in tomcat web connector to the user
--

 Key: GERONIMO-3499
 URL: https://issues.apache.org/jira/browse/GERONIMO-3499
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.0.2, 2.1
Reporter: Lin Sun
Assignee: Lin Sun
Priority: Minor


I was doing some jaxws testing on zLinux and I had to increase the 
ConnectionTimeout value to 1 mins to get my test passing.   The default value 
is set to 20 seconds, and I got some socketException - broken pipe with the 
default timeout value.

It is not obvious for a regular user to configure this, as it is currently only 
mentioned in the tomcat6 config plan, which isn't in the geronimo assembly.
I'd like to add this configuration in the config.xml of the tomcat java ee5 
assembly so that a user could config the ConnectionTimeout value intuitively.   
  (Jetty config doesn't seemt to support this property.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Distributing AspectJ JARs - License

[Kevan Miller]

On Oct 3, 2007, at 2:38 PM, Donald Woods wrote:

We aren't pulling WADI into the Tomcat assemblies yet, so only the  
Jetty assemblies need the update, right?


Technically correct. However, we aren't that granular at the moment.  
We currently don't differentiate between tomcat/jetty, minimal/full  
java ee servers in our license/notice files. Clearly we could be more  
targeted...


--kevan

Re: [VOTE] Release XBean 3.2

[Kevan Miller]

The sources jars (e.g. http://people.apache.org/~gnodet/xbean-3.2/org/ 
apache/xbean/xbean-classloader/3.2/xbean-classloader-3.2-sources.jar)  
are missing LICENSE and NOTICE files.


The xbean-reflect pom (http://svn.apache.org/repos/asf/geronimo/xbean/ 
tags/xbean-3.2/xbean-reflect/pom.xml) is missing an apache source  
header.


xbean-spring/src/main/resources/org/apache/xbean/spring/spring- 
beans.xsd does not have an apache source header, either. Not clear  
that it should... Was that file copied from Spring (should there be a  
Spring attribution?) or was it created by xbean?


Other than the above, everything else looks good.

--kevan

Re: How to build SA using bean SU and jms consumer SU and debug and deploy in eclipse

[[EMAIL PROTECTED]]

Can you just send me the sample configuration files with the minimum
requrired field for the xbean for the jms-consumer su that sends messge to
the nmr 
and bean su that listens to the messge back to the nmr 
i mean so that i can't get response back to my client program.
Regards,
Yogaraj



[EMAIL PROTECTED] wrote:
> 
> Hi,
> I made an SA successfully using the servicemix-bean su and  jms-consumer
> su and used mvn command  
> to make SA out of them and build was successful.I wrote a client jms
> program that sends the message.But I couldn't get response back from bean
> I am using simple inout echo bean that you listed on the site.
> I think problem is with my xbean and target point
> i am sending both here.
> 
> 
> beans xmlns:bean="http://servicemix.apache.org/bean/1.0";
>xmlns:y="http://localhost:8192/yrkproject";>
> 
>endpoint="nih.nci.gov.caXchange.org.servicemix.yrkprojectinput"
> bean="#myBean"/>
> 
>   
> 
> 
> beans xmlns:jms="http://servicemix.apache.org/jms/1.0";
>xmlns:y="http://localhost:8192/yrkproject";
>xmlns:amq="http://activemq.org/config/1.0";>
> 
>
>   
> endpoint="nih.nci.gov.caXchange.org.servicemix.yrkprojectsource"
>   targetService="y:yrkproject"
>  
> targetEndpoint="nih.nci.gov.caXchange.org.servicemix.yrkprojectsource"
>   role="consumer"
>   destinationStyle="queue"
>  
> jmsProviderDestinationName="nih.nci.gov.caXchange.org.servicemix.yrkprojectsource"
>   defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
>   defaultOperation="test:Echo"
>   connectionFactory="#connectionFactory" />
>   class="org.apache.activemq.pool.PooledConnectionFactory">
> 
> 
> 
> 
>   
>   
>
> 
>
> 
> 
> 
> 
> 
> This is my client
> 
> package nih.nci.gov.caXchange;
> import javax.jbi.messaging.InOut;
> import org.apache.servicemix.client.DefaultServiceMixClient;
> import org.apache.servicemix.jbi.jaxp.StringSource;
> import javax.xml.namespace.QName;
> import javax.jms.*;
> 
> import org.apache.activemq.ActiveMQConnectionFactory;
> import org.apache.activemq.command.ActiveMQQueue;
> 
> 
> public class TestJmsClient {
> 
> /**
>  * @param args
>  */
> public static void main(String[] args) throws JMSException{
>  System.out.println("Connecting to JMS server.");
>   // ActiveMQ JMS Provider code
> ActiveMQConnectionFactory factory =
> new ActiveMQConnectionFactory("tcp://localhost:61616");
> Destination inQueue = new
> ActiveMQQueue("nih.nci.gov.caXchange.org.servicemix.yrkprojectsource");
> Destination outQueue = new
> ActiveMQQueue("nih.nci.gov.caXchange.org.servicemix.yrkprojectoutput");
> Connection connection = factory.createConnection();
> Session session = connection.createSession(false,
> Session.CLIENT_ACKNOWLEDGE);
>  // Create the message 66 and consumer
> MessageProducer producer = session.createProducer(inQueue);  
> System.out.println("Producer got this:  "+producer);
> MessageConsumer consumer = session.createConsumer(outQueue);
> System.out.println("Consumer got this:   "+consumer);
> connection.start();  
> System.out.println("Sending request.");
> //producer.send(session.createTextMessage("Hello,
> world!"));
> TextMessage tMsg = session.createTextMessage("Yogi");
> System.out.println(tMsg);
> tMsg.setJMSReplyTo(inQueue);
> producer.send(tMsg);
> connection.close();
> System.out.println("Done.");
>
>
>
>
> }
>
>   /*public void init(ComponentContext context) throws JBIException
> {
>   this.context = context;
>   context.activateEndpoint(new QName("http://your.namespace";,
> "service"), "endpoint");
>   }*/
>
> /*public void testEcho() throws Exception {
> DefaultServiceMixClient client = new
> DefaultServiceMixClient(jbi);
> InOut me = client.createInOutExchange();
> me.setService(new QName("http://bpmscript.org/jbi";,
> "timeout"));
> me.getInMessage().setContent(new
> StringSource("world"));
> ssertTrue(client.sendSync(me, 100));
> Exception error = me.getError();
> assertTrue(error instanceof TimeoutException);
> } */
> 
> }
> 
> 
> Can any one suggest me how do I get reply back from servicemix bean.
> Regards,
> Raj
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-build-SA-using-bean-SU-and-jms-consumer-SU-and-debug-and-deploy-in-eclipse-tf4563348s12049.html#a13025278
Sent from th

[jira] Commented: (GERONIMO-3199) Prefix ear name in deployment-id to make it unique

[David Blevins (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532189
 ] 

David Blevins commented on GERONIMO-3199:
-

Attempted to fix this but tck issues ensued and had to revert it in revision 
581680.

> Prefix ear name in deployment-id to make it unique
> --
>
> Key: GERONIMO-3199
> URL: https://issues.apache.org/jira/browse/GERONIMO-3199
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: OpenEJB
>Affects Versions: 2.0-M5, 2.0-M6
>Reporter: Prasad Kashyap
>Assignee: David Blevins
> Fix For: 2.0.x
>
>
> In 2.0-M3, when a bean was deployed, it's deployment-id was prefixed with 
> geronimo-deploymentUtil9638.tmpdir
> Eg: deployment-id=geronimo-deploymentUtil9638.tmpdir/SimpleStatelessSession
> This ensured a unique ID even if beans from across apps had the same name.
> Now, the deployment-id is prefixed with the name of the jar to which the bean 
> belongs to.
> Eg: deployment-id=ejb.jar/SimpleStatelessSession
> This eliminates the deployment of another app having a bean with the same 
> name packaged in a same named jar.
> http://www.nabble.com/Naming-conflict-when-deploying-testsupport-EARs-tf3834600s134.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Distributing AspectJ JARs - License

[Donald Woods]

We aren't pulling WADI into the Tomcat assemblies yet, so only the Jetty 
assemblies need the update, right?


-Donald

Kevan Miller wrote:


On Oct 3, 2007, at 10:07 AM, Gianny Damour wrote:


Hi Matt,

Yes: I would like to add this dependency from the Eclipse Foundation 
to a config so that it gets included in the assemblies:



aspectj
aspectjrt
1.5.2a


My understanding is that the AspectJ tools are provided under the 
"Eclipse Public License Version 1.0" license: 
http://www.eclipse.org/legal/epl-v10.html


At this stage, I would like to simply change the licensing files of 
the config:

* mofify the NOTICE.txt to include a one liner pointing to the EPL; and
* add a LICENSE-EPL-V10.txt, which is a CC of 
http://www.eclipse.org/legal/epl-v10.html.


However, I am not sure that we can include AspectJ jars in the 
assemblies.


Hi Gianny,
It's fine to include EPL-licensed binaries. EPL-licensed source code 
would be a problem, however. FYI -- an overview of OS licenses and 
categorization with regard to Apache projects can be found here -- 
http://people.apache.org/~rubys/3party.html


I would prefer that you not create a separate LICENSE-EPL file. We 
currently aggregate all license information in our LICENSE.txt file. I'd 
prefer that we maintain this practice until we change our handling for 
all 3rd party licenses.


The NOTICE file needs to inform users how to obtain aspectj source code 
(this is a provision of the EPL). Typically this is accomplished with a 
url to the project web site.


Although the geronimo-wadi module would conceptually "contain" the 
EPL-licensed artifact, it's actually the assembly that contains the 
artifact. So, updating the license/notice files in the 
configs/geronimo-wadi directory would not be appropriate. Instead, you 
need to update trunk/LICENSE.txt (and NOTICE.txt) as well as 
trunk/assemblies/geronimo-boilerplate-minimal/src/main/underlay/LICENSE.txt 
(and NOTICE.txt).


--kevan





smime.p7s
Description: S/MIME Cryptographic Signature

[jira] Updated: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig updated GERONIMO-3498:


Attachment: (was: GERONIMO-3498.patch)

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig updated GERONIMO-3498:


Attachment: GERONIMO-3498.patch

Erm, slight issue with previous patch on the main pom.xml.
Fixed and recreated

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (GERONIMODEVTOOLS-226) Production eclipse udate site does not have 2.0.0 on it!

[Donald Woods]

Can we also add to the Plugin release process to update the Geronimo Home page 
with a News item that we have an updated Plugin available?


-Donald

Tim McConnell (JIRA) wrote:
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531275 ] 


Tim McConnell commented on GERONIMODEVTOOLS-226:


Thanks Kan/Ted. The site.xml file has been ftp'd to the appropriate place now. 


Production eclipse udate site does not have 2.0.0 on it!


Key: GERONIMODEVTOOLS-226
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-226
Project: Geronimo-Devtools
 Issue Type: Bug
 Components: eclipse-plugin
   Affects Versions: 2.0.0
   Reporter: Ted Kirby
   Assignee: Tim McConnell
   Priority: Blocker
Fix For: 2.0.0


The staging site
http://people.apache.org/~mcconne/releases/RC3/staging_site
looks good, 
but the production site

http://www.apache.org/dist/geronimo/eclipse/updates/plugins/
does not have the new stuff on it.
Do we want to keep the old stuff there also, or just nuke it and put the v20 
stuff there?
Or, create a new udpate site for v2?




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Adding j2g to site

[Paul McMahan]

Thanks Tim.  I updated the wiki page to point at :
http://people.apache.org/dist/geronimo/j2g/nightly/
Assuming that is where your J2G build script uploads the file(?)

Best wishes,
Paul


On Oct 2, 2007, at 7:29 PM, Tim McConnell wrote:

Thanks Paul, now I don't have to worry about blowing away the one  
on the unstable site ;-)


Paul McMahan wrote:

On Oct 2, 2007, at 7:15 PM, Tim McConnell wrote:
Hi Erik, thanks very for reviewing. Sorry I didn't know that J2G  
has its own unstable site. So, I'll change the wiki to point to  
the j2g/unstable site instead of the eclipse/unstable site and  
change my build script to FTP the latest trunk version to the j2g/ 
unstable site every Sunday morning. That all work for you ??

There's also a more recent build at
http://people.apache.org/dist/geronimo/j2g/nightly/
Best wishes,
Paul


--
Thanks,
Tim McConnell

[jira] Updated: (GERONIMO-3489) Deployment problems caused by file deletion failures

[Ted Kirby (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Kirby updated GERONIMO-3489:


Attachment: G3489-2.patch

Patch G3489-2: Add System.runFinalization(), sleep call in the retry loop, 
before the System.gc(), sleep sequence.

> Deployment problems caused by file deletion failures
> 
>
> Key: GERONIMO-3489
> URL: https://issues.apache.org/jira/browse/GERONIMO-3489
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: deployment
>Affects Versions: 2.0.1
>Reporter: Ted Kirby
> Fix For: 2.0.2, 2.0.x, 2.1
>
> Attachments: G3489-1.patch, G3489-2.patch
>
>
> File.delete() failures in IOUtil.recursiveDelete() are causing various 
> deployment problems.  I open this JIRA to discuss them to see how the server 
> might better handle them.  In all but one case, delete failures are not even 
> noted with a log record!  Deletion problems are seen in many environments and 
> platforms, but they are persistently fatal when using a NFS file system for 
> the repository.
> In investigating the problem, I have added code to recursiveDelete to retry 
> the delete a few times if it fails.  I added code to list directory contents 
> if a directory delete failed, and saw a file named 
> .nfs2bc4350053e in the directory.  My first attempt at a bypass 
> was to retry a failed delete 5 times, sleeping a second before each try.  
> This did not work.  I added a call to System.gc() before each sleep, and this 
> got me passed the problem.  Interestingly, two retries were required to get 
> this to work.  In another version, each retry was a second longer, and I 
> printed all file names in a directory before trying the delete.  This worked 
> in most cases, but required the full 5 retries, so I suspect System.gc() 
> would have time.  System.runFinalization() would be something else to try.
> RepositoryConfigurationStore.createNewConfigurationDir(Artifact) shows the 
> failing end of the deletion problem, with the dreaded 
> ConfigurationAlreadyExistsException("Configuration already exists: " + 
> configId)exception.  I think this message is not good.  It should really say 
> directory already exists.  If the file is not deleted on undeploy, this 
> failure occurs on a subsequent deploy.  What is really bad is if the user 
> invokes a redeploy operation, and the file delete fails on the undeploy.  It 
> is important that undeploy not complete until the file goes away.
> From other environments, I am not convinced that all file handles and 
> references, and particularly open streams, are being closed on some 
> artifacts.  This will cause the delete to fail.  It may be that the gc() 
> calls are cleaning these up, and allowing the deletes to work in my case 
> above.
> Another option is that 
> RepositoryConfigurationStore.createNewConfigurationDir(Artifact) not throw a 
> ConfigurationAlreadyExistsException if the only problem is an empty directory 
> structure exists.  The next line creates the directory structure anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

How to build SA using bean SU and jms consumer SU and debug and deploy in eclipse

[[EMAIL PROTECTED]]

Hi,
I made an SA successfully using the servicemix-bean su and  jms-consumer su
and used mvn command  
to make SA out of them and build was successful.I wrote a client jms program
that sends the message.But I couldn't get response back from bean I am using
simple inout echo bean that you listed on the site.
I think problem is with my xbean and target point
i am sending both here.


beans xmlns:bean="http://servicemix.apache.org/bean/1.0";
   xmlns:y="http://localhost:8192/yrkproject";>

  

  


beans xmlns:jms="http://servicemix.apache.org/jms/1.0";
   xmlns:y="http://localhost:8192/yrkproject";
   xmlns:amq="http://activemq.org/config/1.0";>

   
http://www.w3.org/2004/08/wsdl/in-out";
  defaultOperation="test:Echo"
  connectionFactory="#connectionFactory" />
 




  
  
   

   





This is my client

package nih.nci.gov.caXchange;
import javax.jbi.messaging.InOut;
import org.apache.servicemix.client.DefaultServiceMixClient;
import org.apache.servicemix.jbi.jaxp.StringSource;
import javax.xml.namespace.QName;
import javax.jms.*;

import org.apache.activemq.ActiveMQConnectionFactory;
import org.apache.activemq.command.ActiveMQQueue;


public class TestJmsClient {

/**
 * @param args
 */
public static void main(String[] args) throws JMSException{
 System.out.println("Connecting to JMS server.");
  // ActiveMQ JMS Provider code
ActiveMQConnectionFactory factory =
new ActiveMQConnectionFactory("tcp://localhost:61616");
Destination inQueue = new
ActiveMQQueue("nih.nci.gov.caXchange.org.servicemix.yrkprojectsource");
Destination outQueue = new
ActiveMQQueue("nih.nci.gov.caXchange.org.servicemix.yrkprojectoutput");
Connection connection = factory.createConnection();
Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
 // Create the message 66 and consumer
MessageProducer producer = session.createProducer(inQueue);  
System.out.println("Producer got this:  "+producer);
MessageConsumer consumer = session.createConsumer(outQueue);
System.out.println("Consumer got this:   "+consumer);
connection.start();  
System.out.println("Sending request.");
//producer.send(session.createTextMessage("Hello,
world!"));
TextMessage tMsg = session.createTextMessage("Yogi");
System.out.println(tMsg);
tMsg.setJMSReplyTo(inQueue);
producer.send(tMsg);
connection.close();
System.out.println("Done.");
   
   
   
   
}
   
  /*public void init(ComponentContext context) throws JBIException {
  this.context = context;
  context.activateEndpoint(new QName("http://your.namespace";,
"service"), "endpoint");
  }*/
   
/*public void testEcho() throws Exception {
DefaultServiceMixClient client = new
DefaultServiceMixClient(jbi);
InOut me = client.createInOutExchange();
me.setService(new QName("http://bpmscript.org/jbi";,
"timeout"));
me.getInMessage().setContent(new
StringSource("world"));
ssertTrue(client.sendSync(me, 100));
Exception error = me.getError();
assertTrue(error instanceof TimeoutException);
} */

}


Can any one suggest me how do I get reply back from servicemix bean.
Regards,
Raj
-- 
View this message in context: 
http://www.nabble.com/How-to-build-SA-using-bean-SU-and-jms-consumer-SU-and-debug-and-deploy-in-eclipse-tf4563348s12049.html#a13024209
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Christopher Blythe]

ahh... come on matt... this is good discussion... we finally have people
thinking (and talking) about where we should or shouldn't take DayTrader in
the future. there hasn't been enough of that!

i think short term, the disclaimers serve the purpose. however, long term...
daytrader will lose it's relevance if it isn't updated to reflect how people
are using the technology.

On 10/3/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
>
> So to cl;arify I think DayTrader may be mis-characterized as only a
> benchmark.  I think it is used for a variety of functions of which only one
> aspect is performance.  the other aspects are testing infrastructure, sample
> application (which includes deployments plans for various pieces of
> functionality, etc.).
> With that in mind perhaps we should change it from performance benchmark
> to something else.  I'm concerned about pulling this at the very end.  I
> agree that we don't want to put out a sample that can be used
> inappropriately but in the end we don't really tell anyone what they can do
> with the software.  I'm concerned about making changes to DayTrader because
> of commercial positioning.  For this reason I'd rather add the comment about
> relevance of the runtime mode.  I think simply adding the comment is
> adequate.
>
> If we're going for best practices I don't think anyone would say the app
> as it is written today is a best practice but more of a swiss army knife of
> tools.
>
> It sounds like there are varying viewpoints so perhaps we let the
> discussion percolate and put it to a vote.
>
> On Oct 3, 2007, at 12:25 PM, Christopher Blythe wrote:
>
> ah now you're pointing out the distinctions between primitives and a
> real application "workload". currently, the web services within daytrader
> are presented in the context of a "workload" not a primitive.
>
>
>


-- 
"I say never be complete, I say stop being perfect, I say let... lets
evolve, let the chips fall where they may." - Tyler Durden

Re: Jetty Connector Statistics?

[Viet Nguyen]

After digging into Jetty's code for more information on how
AbstractConnectors work, I found out that the statistics do not change
unless the connection is closed. The only instances in their code where any
of the statistics change are in statsReset(), connectionOpened(), and
connectionClosed(). Therefore, the statistics that they provide will not be
"live" stats because things such as number of requests are not updated until
connectionClosed() is called.

I used http://www.mortbay.org/xref/org/mortbay/jetty/AbstractConnector.htmlas
my reference.

Thanks,
Viet

On 10/2/07, Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
>
> Jetty AbstractConnector provides many statistics. A few of these
> are listed as undefined if statsOn is false. Does this mean others are
> valid values at all time? If statsOn is true, how often are the value
> updated?
> Any help from Jetty experts will be greatly appreciated.
>
> TIA
> Anita
>
>
>
>
> 
> Be a better Heartthrob. Get better relationship answers from someone who
> knows. Yahoo! Answers - Check it out.
> http://answers.yahoo.com/dir/?link=list&sid=396545433
>

Re: Jndi names, need input (Re: [DISCUSS] G 2.0.2 Release plan)

[David Blevins]

On Oct 2, 2007, at 7:02 PM, David Blevins wrote:


Ok, I made the following changes:

 - Set the deployment id format to {appId}/{moduleId}/{ejbName}   
(fixes GERONIMO-3199)
 - Set jndiname format to {ejbName}{interfaceType.annotationName}   
(this MUST go in the release notes as it will be a significant change)
 - Setup jndi name binding of non-javaee clients to not fail a  
deployment if a name is taken (just logs an ERROR as usual).


I also slurped in the OpenEJB documentation on this subject to a  
new page here:

  http://cwiki.apache.org/GMOxSBOX/client-jndi-names.html


Moved the page to GMOxDEV per Hernan's request.

-David

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Matt Hogstrom]

So to cl;arify I think DayTrader may be mis-characterized as only a  
benchmark.  I think it is used for a variety of functions of which  
only one aspect is performance.  the other aspects are testing  
infrastructure, sample application (which includes deployments plans  
for various pieces of functionality, etc.).


With that in mind perhaps we should change it from performance  
benchmark to something else.  I'm concerned about pulling this at the  
very end.  I agree that we don't want to put out a sample that can be  
used inappropriately but in the end we don't really tell anyone what  
they can do with the software.  I'm concerned about making changes to  
DayTrader because of commercial positioning.  For this reason I'd  
rather add the comment about relevance of the runtime mode.  I think  
simply adding the comment is adequate.


If we're going for best practices I don't think anyone would say the  
app as it is written today is a best practice but more of a swiss  
army knife of tools.


It sounds like there are varying viewpoints so perhaps we let the  
discussion percolate and put it to a vote.


On Oct 3, 2007, at 12:25 PM, Christopher Blythe wrote:

ah now you're pointing out the distinctions between primitives  
and a real application "workload". currently, the web services  
within daytrader are presented in the context of a "workload" not a  
primitive.

Re: Distributing AspectJ JARs - License

[Kevan Miller]

On Oct 3, 2007, at 10:07 AM, Gianny Damour wrote:


Hi Matt,

Yes: I would like to add this dependency from the Eclipse  
Foundation to a config so that it gets included in the assemblies:



aspectj
aspectjrt
1.5.2a


My understanding is that the AspectJ tools are provided under the  
"Eclipse Public License Version 1.0" license: http:// 
www.eclipse.org/legal/epl-v10.html


At this stage, I would like to simply change the licensing files of  
the config:
* mofify the NOTICE.txt to include a one liner pointing to the EPL;  
and
* add a LICENSE-EPL-V10.txt, which is a CC of http:// 
www.eclipse.org/legal/epl-v10.html.


However, I am not sure that we can include AspectJ jars in the  
assemblies.


Hi Gianny,
It's fine to include EPL-licensed binaries. EPL-licensed source code  
would be a problem, however. FYI -- an overview of OS licenses and  
categorization with regard to Apache projects can be found here --  
http://people.apache.org/~rubys/3party.html


I would prefer that you not create a separate LICENSE-EPL file. We  
currently aggregate all license information in our LICENSE.txt file.  
I'd prefer that we maintain this practice until we change our  
handling for all 3rd party licenses.


The NOTICE file needs to inform users how to obtain aspectj source  
code (this is a provision of the EPL). Typically this is accomplished  
with a url to the project web site.


Although the geronimo-wadi module would conceptually "contain" the  
EPL-licensed artifact, it's actually the assembly that contains the  
artifact. So, updating the license/notice files in the configs/ 
geronimo-wadi directory would not be appropriate. Instead, you need  
to update trunk/LICENSE.txt (and NOTICE.txt) as well as trunk/ 
assemblies/geronimo-boilerplate-minimal/src/main/underlay/LICENSE.txt  
(and NOTICE.txt).


--kevan

[jira] Commented: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532163
 ] 

Erik B. Craig commented on GERONIMO-3498:
-

Ermm, sorry about that. Should be a bit better.

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3498) Refactor Monitoring plugin packaging and source

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig updated GERONIMO-3498:


Description: The maven build method/order for the Monitoring plugin in 
sandbox must be restructured so the package is created as an ear to include 
derby datasource definitions for using to query and store configurations as 
well as graphing information  (was: The maven build method/order for the 
Monitoring plugin in sandbox must be restructured so the package is created as 
an ear to include derby datasource definitions.)
Summary: Refactor Monitoring plugin packaging and source  (was: 
Refactor Monitoring plugin packaging and source for database)

> Refactor Monitoring plugin packaging and source
> ---
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions for using to query and store configurations as well as graphing 
> information

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3498) Refactor Monitoring plugin packaging and source for database

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig updated GERONIMO-3498:


Description: The maven build method/order for the Monitoring plugin in 
sandbox must be restructured so the package is created as an ear to include 
derby datasource definitions.  (was: The maven build method/order must be 
restructured so the package is created as an ear to include derby datasource 
definitions.)
Summary: Refactor Monitoring plugin packaging and source for database  
(was: Refactor packaging and source for database)

> Refactor Monitoring plugin packaging and source for database
> 
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order for the Monitoring plugin in sandbox must be 
> restructured so the package is created as an ear to include derby datasource 
> definitions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release XBean 3.2

[Dain Sundstrom]

+1

-dain

On Oct 1, 2007, at 8:10 AM, Guillaume Nodet wrote:


Please vote on releasing xbean 3.2.
Binaries / maven repo is available at:
   http://people.apache.org/~gnodet/xbean-3.2/
Svn source tag is available at:
   http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.2/

It includes David Jencks last minute fix too.

--
Cheers,
Guillaume Nodet

Blog: http://gnodet.blogspot.com/

[jira] Resolved: (GSHELL-35) Make CommandDescriptor optional and make Command stateless

[Guillaume Nodet (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GSHELL-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved GSHELL-35.
---

Resolution: Fixed

Sending
gshell-command-api/src/main/java/org/apache/geronimo/gshell/command/Command.java
Sending
gshell-command-api/src/main/java/org/apache/geronimo/gshell/command/CommandContext.java
Sending
gshell-command-api/src/main/java/org/apache/geronimo/gshell/command/CommandSupport.java
Sending
gshell-commands/gshell-builtins/src/main/java/org/apache/geronimo/gshell/commands/builtins/HelpCommand.java
Sending
gshell-core/src/main/java/org/apache/geronimo/gshell/DefaultCommandExecutor.java
Sending
gshell-core/src/main/java/org/apache/geronimo/gshell/layout/DefaultLayoutManager.java
Sending
gshell-core/src/main/java/org/apache/geronimo/gshell/layout/LayoutManager.java
Sending
gshell-core/src/main/java/org/apache/geronimo/gshell/plugin/CommandDiscoveryListener.java
Adding 
gshell-core/src/main/java/org/apache/geronimo/gshell/plugin/PlexusCommandWrapper.java
Sending
gshell-core/src/main/java/org/apache/geronimo/gshell/registry/CommandRegistry.java
Sending
gshell-core/src/main/java/org/apache/geronimo/gshell/registry/DefaultCommandRegistry.java
Transmitting file data ...
Committed revision 581649.

> Make CommandDescriptor optional and make Command stateless
> --
>
> Key: GSHELL-35
> URL: https://issues.apache.org/jira/browse/GSHELL-35
> Project: GShell
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: API, Core
>Affects Versions: 1.0-alpha-1
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GSHELL-35) Make CommandDescriptor optional and make Command stateless

[Guillaume Nodet (JIRA)]

Make CommandDescriptor optional and make Command stateless
--

 Key: GSHELL-35
 URL: https://issues.apache.org/jira/browse/GSHELL-35
 Project: GShell
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: API, Core
Affects Versions: 1.0-alpha-1
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-3498) Refactor packaging and source for database

[David Jencks (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532154
 ] 

David Jencks commented on GERONIMO-3498:


Eric, could you edit the name and description of this jira so the uninitiated 
could figure out what you are talking about?

> Refactor packaging and source for database
> --
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order must be restructured so the package is created 
> as an ear to include derby datasource definitions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Christopher Blythe]

ah now you're pointing out the distinctions between primitives and a
real application "workload". currently, the web services within daytrader
are presented in the context of a "workload" not a primitive.

if you want to measure the web services overhead and the impact of payloads
with varying size and complexity, primitives are the right way to go. i've
seen several web services benchmarks geared towards this and am not sure if
daytrader is the right place to repeat them.

On 10/3/07, David Jencks <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 3, 2007, at 7:36 AM, Jeff Genender wrote:
>
> >
> >
> > Christopher Blythe wrote:
> >> Jeff... I agree with you on both counts. Perhaps I should present
> >> this
> >> from another vantage point. If you were an application developer,
> >> would
> >> you use web services in the manner they are currently used in
> >> DayTrader?
> >> Or would you try to adhere to most documented best practices and
> >> steer
> >> clear of very chatty (fine-grained) web services calls. If we
> >> would like
> >> to keep web services in DayTrader, I think they should be re-
> >> vamped to
> >> re-align with a scenario/pattern that is better suited for web
> >> services
> >> and reflect how they are predominantly used in the industry.
> >>
> >
> > Yep...you are going exactly where I was ;-)
> >
> > If DT is not using WS the way it should be, then absolutely it
> > should be
> > redone and developed in a best practice manner.
>
>
> well I'm confused now pingServlet is not a realistic imitation of
> any real business operation, but it is useful to measure the overhead
> of the web container.  Aren't our current dt web services pretty much
> similar to pingServlet and measure the overhead of the ws stack with
> no data processing taking place?  I think it would be useful to also
> measure what happens if you send a realistically sized xml doc back
> and forth while doing nothing with it, but the overhead with a
> minimal xml doc seems useful to me also.  Similarly, we could (and
> might I dont know) measure the overhead of sending a large form
> and returning a complicated static page while doing no application
> processing for the web container.
>
> does this make any sense?
>
> thanks
> david jencks
>
> >
> > Jeff
> >
> >
> >
> >> On 10/3/07, *Jeff Genender* <[EMAIL PROTECTED]
> >> > wrote:
> >>
> >>
> >>
> >> Christopher Blythe wrote:
> >>> Actually, I'm suggesting we pull the web services out of
> >>> DayTrader all
> >>> together and write another web services sample app. If DayTrader is
> >>> truly meant to be a "performance benchmark", why would you leave
> >>> something in there that is in clear violation of performance best
> >>> practices. Doesn't exactly send the right message if you ask me.
> >>>
> >>
> >> That really depends what you are trying measure.  Are you
> >> trying to
> >> measure raw-throughput (ping servlet, etc), or are you trying
> >> to measure
> >> how a JavaEE5 application using standard components is going
> >> to perform
> >> (more realistic)?
> >>
> >> IMHO, I think Daytrader is a neat application that lets you
> >> kind of
> >> configure what you want to test and how you want to test it.  Its
> >> interesting because I haven't seen anything else out there
> >> that does
> >> this...it really is a good way to measure most components of a
> >> standardized stack.
> >>
> >> Jeff
> >>
> >>> On 10/2/07, *Matt Hogstrom* <[EMAIL PROTECTED]
> >> 
> >>> >> wrote:
> >>>
> >>>
> >>> On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:
> >>>
>  Matt...
> 
> 
>  In summary, I guess I really just wanted to say that I feel
> >> the web
>  services modes in DayTrader should be removed at least until
> >> we can
>  come up with something better. If the only reason to keep these
>  around is to provide a "sample" and not a performance benchmark,
>  lets come up with some other sample that demonstrates web
> >> services.
> 
> >>>
> >>> You make a good point about the WebServices.  I'd suggest
> >>> that we
> >>> document the current limitations of comparing these
> >>> WebServices in
> >>> performance benchmarks.  That should help to set everyone's
> >>> expectations about the relevant usefulness of the data.
> >>>
> >>> For WebServices it sounds like your suggesting that we
> >> deprecate web
> >>> services for performance work rather than for functional
> >>> purposes
> >>> like was done for the MDB primitives.  I'd be for adding the
> >> warning
> >>> in a readme.
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> "I say never be complete, I say stop being perfect, I say let...
> >>> lets
> >>> evolve, let the chips fall where they may." - Tyler Durden
> >>
> >>
> >>
> >>
> >> --
> >> "I say never be complete, I say stop being perfect, I say

[jira] Updated: (GERONIMO-3498) Refactor packaging and source for database

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig updated GERONIMO-3498:


Attachment: GERONIMO-3498.patch

I have restructured the packaging and building for the mrc-client.
It is now called simply client under 'monitoring', and the packages for the 
compilation are under org.apache.geronimo.plugins.monitoring.client. Maven now 
also generates an EAR to be deployed containing database connector information 
for Derby instead of the previous WAR, and with this patch is solid for setting 
up a graphs and configuration database.

> Refactor packaging and source for database
> --
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order must be restructured so the package is created 
> as an ear to include derby datasource definitions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3498) Refactor packaging and source for database

[Erik B. Craig (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik B. Craig updated GERONIMO-3498:


Priority: Blocker  (was: Major)

Priority is extremely critical, need to get this patch in as a checkpoint to 
continue.

> Refactor packaging and source for database
> --
>
> Key: GERONIMO-3498
> URL: https://issues.apache.org/jira/browse/GERONIMO-3498
> Project: Geronimo
>  Issue Type: Sub-task
>  Security Level: public(Regular issues) 
>  Components: monitoring
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Blocker
> Attachments: GERONIMO-3498.patch
>
>
> The maven build method/order must be restructured so the package is created 
> as an ear to include derby datasource definitions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3498) Refactor packaging and source for database

[Erik B. Craig (JIRA)]

Refactor packaging and source for database
--

 Key: GERONIMO-3498
 URL: https://issues.apache.org/jira/browse/GERONIMO-3498
 Project: Geronimo
  Issue Type: Sub-task
  Security Level: public (Regular issues)
  Components: monitoring
Reporter: Erik B. Craig
Assignee: Erik B. Craig


The maven build method/order must be restructured so the package is created as 
an ear to include derby datasource definitions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[David Jencks]

On Oct 3, 2007, at 7:36 AM, Jeff Genender wrote:




Christopher Blythe wrote:
Jeff... I agree with you on both counts. Perhaps I should present  
this
from another vantage point. If you were an application developer,  
would
you use web services in the manner they are currently used in  
DayTrader?
Or would you try to adhere to most documented best practices and  
steer
clear of very chatty (fine-grained) web services calls. If we  
would like
to keep web services in DayTrader, I think they should be re- 
vamped to
re-align with a scenario/pattern that is better suited for web  
services

and reflect how they are predominantly used in the industry.



Yep...you are going exactly where I was ;-)

If DT is not using WS the way it should be, then absolutely it  
should be

redone and developed in a best practice manner.



well I'm confused now pingServlet is not a realistic imitation of  
any real business operation, but it is useful to measure the overhead  
of the web container.  Aren't our current dt web services pretty much  
similar to pingServlet and measure the overhead of the ws stack with  
no data processing taking place?  I think it would be useful to also  
measure what happens if you send a realistically sized xml doc back  
and forth while doing nothing with it, but the overhead with a  
minimal xml doc seems useful to me also.  Similarly, we could (and  
might I dont know) measure the overhead of sending a large form  
and returning a complicated static page while doing no application  
processing for the web container.


does this make any sense?

thanks
david jencks



Jeff




On 10/3/07, *Jeff Genender* <[EMAIL PROTECTED]
> wrote:



Christopher Blythe wrote:
Actually, I'm suggesting we pull the web services out of  
DayTrader all

together and write another web services sample app. If DayTrader is
truly meant to be a "performance benchmark", why would you leave
something in there that is in clear violation of performance best
practices. Doesn't exactly send the right message if you ask me.



That really depends what you are trying measure.  Are you  
trying to
measure raw-throughput (ping servlet, etc), or are you trying  
to measure
how a JavaEE5 application using standard components is going  
to perform

(more realistic)?

IMHO, I think Daytrader is a neat application that lets you  
kind of

configure what you want to test and how you want to test it.  Its
interesting because I haven't seen anything else out there  
that does

this...it really is a good way to measure most components of a
standardized stack.

Jeff


On 10/2/07, *Matt Hogstrom* <[EMAIL PROTECTED]



>> wrote:


On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:


Matt...


In summary, I guess I really just wanted to say that I feel

the web

services modes in DayTrader should be removed at least until

we can

come up with something better. If the only reason to keep these
around is to provide a "sample" and not a performance benchmark,
lets come up with some other sample that demonstrates web

services.




You make a good point about the WebServices.  I'd suggest  
that we
document the current limitations of comparing these  
WebServices in

performance benchmarks.  That should help to set everyone's
expectations about the relevant usefulness of the data.

For WebServices it sounds like your suggesting that we

deprecate web
services for performance work rather than for functional  
purposes

like was done for the MDB primitives.  I'd be for adding the

warning

in a readme.




--
"I say never be complete, I say stop being perfect, I say let...  
lets

evolve, let the chips fall where they may." - Tyler Durden





--
"I say never be complete, I say stop being perfect, I say let... lets
evolve, let the chips fall where they may." - Tyler Durden

Re: svn commit: r581456 - /geronimo/server/branches/2.0/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java

[Joe Bohn]

David,

This change and the subsequent correction of it are causing TCK failures 
due to failures when looking up the JDNIContext.lookup failures from the 
client.  See the tck list for details.


Joe


[EMAIL PROTECTED] wrote:

Author: dblevins
Date: Tue Oct  2 18:16:13 2007
New Revision: 581456

URL: http://svn.apache.org/viewvc?rev=581456&view=rev
Log:
Fix for GERONIMO-3199: Prefix ear name in deployment-id to make it unique
Set jndiname format to {ejbName}{interfaceType.annotationName}
Setup jndi name binding of non-javaee clients to not fail a deployment if a 
name is taken (just logs an ERROR as usual).

Modified:

geronimo/server/branches/2.0/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java

Modified: 
geronimo/server/branches/2.0/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java
URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.0/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java?rev=581456&r1=581455&r2=581456&view=diff
==
--- 
geronimo/server/branches/2.0/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java
 (original)
+++ 
geronimo/server/branches/2.0/modules/geronimo-openejb/src/main/java/org/apache/geronimo/openejb/OpenEjbSystemGBean.java
 Tue Oct  2 18:16:13 2007
@@ -107,10 +107,11 @@
 System.setProperty("duct tape","");
 System.setProperty("admin.disabled", "true");
 System.setProperty("openejb.logger.external", "true");
-
-setDefaultProperty("openejb.deploymentId.format", "{moduleId}/{ejbName}");

+System.setProperty("openejb.jndiname.failoncollision", "false");
+
+setDefaultProperty("openejb.deploymentId.format", 
"{appId}/{moduleId}/{ejbName}");
 setDefaultProperty("openejb.jndiname.strategy.class", 
"org.apache.openejb.assembler.classic.JndiBuilder$TemplatedStrategy");
-setDefaultProperty("openejb.jndiname.format", 
"{deploymentId}/{interfaceClass}");
+setDefaultProperty("openejb.jndiname.format", 
"{ejbName}{interfaceType.annotationName}");
 
 System.setProperty("openejb.naming", "xbean");

 if (transactionManager == null) {

[jira] Created: (DAYTRADER-56) Register of duplicate userid in EJB 3 mode not handled correctly

[Christopher James Blythe (JIRA)]

Register of duplicate userid in EJB 3 mode not handled correctly


 Key: DAYTRADER-56
 URL: https://issues.apache.org/jira/browse/DAYTRADER-56
 Project: DayTrader
  Issue Type: Bug
  Components: EJB Tier
Affects Versions: 2.0
Reporter: Christopher James Blythe


If you attempt to register a userid that already exists in the database, the 
resulting error is not handled gracefully. In Direct mode, we catch the 
resulting DuplicateKeyException and ensure that a warning is propagated to the 
web-tier (by displaying a message on the register page).

The register method in the TradeSLSBBean needs to be revised to handle this 
gracefully.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-3497) collecting agent needs to turn on statistics collection for all monitored StatisticsProvider

[Viet Hung Nguyen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viet Hung Nguyen updated GERONIMO-3497:
---

Attachment: geronimo-3497.patch

> collecting agent needs to turn on statistics collection for all monitored 
> StatisticsProvider
> 
>
> Key: GERONIMO-3497
> URL: https://issues.apache.org/jira/browse/GERONIMO-3497
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: monitoring
> Environment: windows xp
>Reporter: Viet Hung Nguyen
> Attachments: geronimo-3497.patch
>
>
> By default, all stats that can be enabled/disabled are turned off. When the 
> collecting agent is deployed, it should turn on all Stats that the admin 
> wishes to track. If not, the collecting agent will be looking at a bunch of 
> useless numbers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (GERONIMO-3497) collecting agent needs to turn on statistics collection for all monitored StatisticsProvider

[Viet Hung Nguyen (JIRA)]

collecting agent needs to turn on statistics collection for all monitored 
StatisticsProvider


 Key: GERONIMO-3497
 URL: https://issues.apache.org/jira/browse/GERONIMO-3497
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public (Regular issues)
  Components: monitoring
 Environment: windows xp
Reporter: Viet Hung Nguyen
 Attachments: geronimo-3497.patch

By default, all stats that can be enabled/disabled are turned off. When the 
collecting agent is deployed, it should turn on all Stats that the admin wishes 
to track. If not, the collecting agent will be looking at a bunch of useless 
numbers.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Jeff Genender]

Christopher Blythe wrote:
> Jeff... I agree with you on both counts. Perhaps I should present this
> from another vantage point. If you were an application developer, would
> you use web services in the manner they are currently used in DayTrader?
> Or would you try to adhere to most documented best practices and steer
> clear of very chatty (fine-grained) web services calls. If we would like
> to keep web services in DayTrader, I think they should be re-vamped to
> re-align with a scenario/pattern that is better suited for web services
> and reflect how they are predominantly used in the industry.
> 

Yep...you are going exactly where I was ;-)

If DT is not using WS the way it should be, then absolutely it should be
redone and developed in a best practice manner.

Jeff



> On 10/3/07, *Jeff Genender* <[EMAIL PROTECTED]
> > wrote:
> 
> 
> 
> Christopher Blythe wrote:
> > Actually, I'm suggesting we pull the web services out of DayTrader all
> > together and write another web services sample app. If DayTrader is
> > truly meant to be a "performance benchmark", why would you leave
> > something in there that is in clear violation of performance best
> > practices. Doesn't exactly send the right message if you ask me.
> >
> 
> That really depends what you are trying measure.  Are you trying to
> measure raw-throughput (ping servlet, etc), or are you trying to measure
> how a JavaEE5 application using standard components is going to perform
> (more realistic)?
> 
> IMHO, I think Daytrader is a neat application that lets you kind of
> configure what you want to test and how you want to test it.  Its
> interesting because I haven't seen anything else out there that does
> this...it really is a good way to measure most components of a
> standardized stack.
> 
> Jeff
> 
> > On 10/2/07, *Matt Hogstrom* <[EMAIL PROTECTED]
> 
> > >> wrote:
> >
> >
> > On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:
> >
> > > Matt...
> > >
> > >
> > > In summary, I guess I really just wanted to say that I feel
> the web
> > > services modes in DayTrader should be removed at least until
> we can
> > > come up with something better. If the only reason to keep these
> > > around is to provide a "sample" and not a performance benchmark,
> > > lets come up with some other sample that demonstrates web
> services.
> > >
> >
> > You make a good point about the WebServices.  I'd suggest that we
> > document the current limitations of comparing these WebServices in
> > performance benchmarks.  That should help to set everyone's
> > expectations about the relevant usefulness of the data.
> >
> > For WebServices it sounds like your suggesting that we
> deprecate web
> > services for performance work rather than for functional purposes
> > like was done for the MDB primitives.  I'd be for adding the
> warning
> > in a readme.
> >
> >
> >
> >
> > --
> > "I say never be complete, I say stop being perfect, I say let... lets
> > evolve, let the chips fall where they may." - Tyler Durden
> 
> 
> 
> 
> -- 
> "I say never be complete, I say stop being perfect, I say let... lets
> evolve, let the chips fall where they may." - Tyler Durden

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Christopher Blythe]

Jeff... I agree with you on both counts. Perhaps I should present this from
another vantage point. If you were an application developer, would you use
web services in the manner they are currently used in DayTrader? Or would
you try to adhere to most documented best practices and steer clear of very
chatty (fine-grained) web services calls. If we would like to keep web
services in DayTrader, I think they should be re-vamped to re-align with a
scenario/pattern that is better suited for web services and reflect how they
are predominantly used in the industry.

On 10/3/07, Jeff Genender <[EMAIL PROTECTED]> wrote:
>
>
>
> Christopher Blythe wrote:
> > Actually, I'm suggesting we pull the web services out of DayTrader all
> > together and write another web services sample app. If DayTrader is
> > truly meant to be a "performance benchmark", why would you leave
> > something in there that is in clear violation of performance best
> > practices. Doesn't exactly send the right message if you ask me.
> >
>
> That really depends what you are trying measure.  Are you trying to
> measure raw-throughput (ping servlet, etc), or are you trying to measure
> how a JavaEE5 application using standard components is going to perform
> (more realistic)?
>
> IMHO, I think Daytrader is a neat application that lets you kind of
> configure what you want to test and how you want to test it.  Its
> interesting because I haven't seen anything else out there that does
> this...it really is a good way to measure most components of a
> standardized stack.
>
> Jeff
>
> > On 10/2/07, *Matt Hogstrom* <[EMAIL PROTECTED]
> > > wrote:
> >
> >
> > On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:
> >
> > > Matt...
> > >
> > >
> > > In summary, I guess I really just wanted to say that I feel the
> web
> > > services modes in DayTrader should be removed at least until we
> can
> > > come up with something better. If the only reason to keep these
> > > around is to provide a "sample" and not a performance benchmark,
> > > lets come up with some other sample that demonstrates web
> services.
> > >
> >
> > You make a good point about the WebServices.  I'd suggest that we
> > document the current limitations of comparing these WebServices in
> > performance benchmarks.  That should help to set everyone's
> > expectations about the relevant usefulness of the data.
> >
> > For WebServices it sounds like your suggesting that we deprecate web
> > services for performance work rather than for functional purposes
> > like was done for the MDB primitives.  I'd be for adding the warning
> > in a readme.
> >
> >
> >
> >
> > --
> > "I say never be complete, I say stop being perfect, I say let... lets
> > evolve, let the chips fall where they may." - Tyler Durden
>



-- 
"I say never be complete, I say stop being perfect, I say let... lets
evolve, let the chips fall where they may." - Tyler Durden

Re: Distributing AspectJ JARs - License

[Gianny Damour]

Hi Matt,

Yes: I would like to add this dependency from the Eclipse Foundation  
to a config so that it gets included in the assemblies:



aspectj
aspectjrt
1.5.2a


My understanding is that the AspectJ tools are provided under the  
"Eclipse Public License Version 1.0" license: http://www.eclipse.org/ 
legal/epl-v10.html


At this stage, I would like to simply change the licensing files of  
the config:

* mofify the NOTICE.txt to include a one liner pointing to the EPL; and
* add a LICENSE-EPL-V10.txt, which is a CC of http://www.eclipse.org/ 
legal/epl-v10.html.


However, I am not sure that we can include AspectJ jars in the  
assemblies.


Thanks,
Gianny


On 03/10/2007, at 12:49 PM, Matt Hogstrom wrote:

Gianny, this looks pretty good.  So for users that have large  
session objects this looks like a way to effectively manage them.


Is your question about the license used for AspectJ from the  
Eclipse Foundation ?




On Sep 28, 2007, at 9:23 PM, Gianny Damour wrote:


Hi,

I would like to add a dependency to a new wadi module, wadi-aop,  
relying on AspectJ JARs.


The goal it to allow users to configure delta session replication  
for their clustered Web applications. I capture here how this works:

http://docs.codehaus.org/display/WADI/5.+Delta+Session+Replication

Is this an issue from a license perspective?

Thanks,
Gianny

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Jeff Genender]

Christopher Blythe wrote:
> Actually, I'm suggesting we pull the web services out of DayTrader all
> together and write another web services sample app. If DayTrader is
> truly meant to be a "performance benchmark", why would you leave
> something in there that is in clear violation of performance best
> practices. Doesn't exactly send the right message if you ask me.
> 

That really depends what you are trying measure.  Are you trying to
measure raw-throughput (ping servlet, etc), or are you trying to measure
how a JavaEE5 application using standard components is going to perform
(more realistic)?

IMHO, I think Daytrader is a neat application that lets you kind of
configure what you want to test and how you want to test it.  Its
interesting because I haven't seen anything else out there that does
this...it really is a good way to measure most components of a
standardized stack.

Jeff

> On 10/2/07, *Matt Hogstrom* <[EMAIL PROTECTED]
> > wrote:
> 
> 
> On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:
> 
> > Matt...
> >
> >
> > In summary, I guess I really just wanted to say that I feel the web
> > services modes in DayTrader should be removed at least until we can
> > come up with something better. If the only reason to keep these
> > around is to provide a "sample" and not a performance benchmark,
> > lets come up with some other sample that demonstrates web services.
> >
> 
> You make a good point about the WebServices.  I'd suggest that we
> document the current limitations of comparing these WebServices in
> performance benchmarks.  That should help to set everyone's
> expectations about the relevant usefulness of the data.
> 
> For WebServices it sounds like your suggesting that we deprecate web
> services for performance work rather than for functional purposes
> like was done for the MDB primitives.  I'd be for adding the warning
> in a readme.
> 
> 
> 
> 
> -- 
> "I say never be complete, I say stop being perfect, I say let... lets
> evolve, let the chips fall where they may." - Tyler Durden

Re: DayTrader - porting MarketSummaryInterval changes from 2.0 to 1.2 and preparing to release

[Christopher Blythe]

Actually, I'm suggesting we pull the web services out of DayTrader all
together and write another web services sample app. If DayTrader is truly
meant to be a "performance benchmark", why would you leave something in
there that is in clear violation of performance best practices. Doesn't
exactly send the right message if you ask me.

On 10/2/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 1, 2007, at 11:23 PM, Christopher Blythe wrote:
>
> > Matt...
> >
> >
> > In summary, I guess I really just wanted to say that I feel the web
> > services modes in DayTrader should be removed at least until we can
> > come up with something better. If the only reason to keep these
> > around is to provide a "sample" and not a performance benchmark,
> > lets come up with some other sample that demonstrates web services.
> >
>
> You make a good point about the WebServices.  I'd suggest that we
> document the current limitations of comparing these WebServices in
> performance benchmarks.  That should help to set everyone's
> expectations about the relevant usefulness of the data.
>
> For WebServices it sounds like your suggesting that we deprecate web
> services for performance work rather than for functional purposes
> like was done for the MDB primitives.  I'd be for adding the warning
> in a readme.
>
>


-- 
"I say never be complete, I say stop being perfect, I say let... lets
evolve, let the chips fall where they may." - Tyler Durden

Re: System Module descriptions

[Joe Bohn]

Hernan Cunico wrote:

Hi Ted,
it would be great to add which modules are critical for Geronimo to run, 
in other words, those we should never mess with. We had a discussion 
some time ago but I don't think we ever properly covered this.


I added some safety checks in the web console for this.  There is now an 
expert mode such that the stop, uninstall, restart action are only 
available on org.apache.geronimo modules when the expert box is checked. 
 I also added some more specific warnings of consequences when the 
actions are to be performed.  Of course, this only provides some safety 
for administrators when using the web console and does nothing for those 
that prefer the command line.  Then again  the web console is 
probably the place where it is a bit easier to do some damage.


Joe



Cheers!
Hernan

Ted Kirby wrote:

I have added this wiki page
http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the
modules that come with the (2.0.1) server, along with:

1. A brief description of what the module does
2. Is it started by default, or
3. Should it never be started?

This is a first draft.  I solicit feedback and encourage folks to
update the page as appropriate.  There are some modules with which I
am not familiar.

Ted Kirby

Re: request for devtools doc for developing in eclipse

[Shiva Kumar H R]

Interesting discussions going on! Thanks Jarek for bringing this up. I would
be happy to have a plugin that's specific to a particular version of
Geronimo, as it would ease development a lot ;) , but after seeing Ted &
Lin's points, I quickly realize that I am not seeing the complete picture.

I think we should start a separate [Discuss] thread on dev-list about this,
with its pros & cons and solicit more feedback/suggestions.

Thanks,
Shiva

On 10/2/07, Ted Kirby <[EMAIL PROTECTED]> wrote:
>
> I think it's cool that one plugin supports all versions of Geronimo.
> I think this can be quite helpful in migrating from one version of
> Geronimo to the next.  I also understand Jarek's concern.  We may well
> want to remove 1.2 from our build.  Can we add a build target that
> only builds 2.0?  Maybe that's the default, and another target says
> build all, or you can choose which server versions you want to include
> in your build.
>
> The 2.0 plugin provides a full WTP server adapter, one for each
> Geronimo version.  The 1.0 plugin used a generic WTP server adapter.
> I don't know if both may coexist in one eclipse installation.
>
> Ted Kirby
>
> On 10/2/07, Tim McConnell <[EMAIL PROTECTED]> wrote:
> > Hi Jarek, I will also update the build page later today. And I agree
> with you
> > that the plugin should support only a specific version of the Geronimo
> server.
> > It's one of the functions I hope we can add to an upcoming releases.
> Thanks for
> > the suggestion.
> >
> > Jarek Gawor wrote:
> > > Also, yesterday I could not find documentation where to checkout/look
> > > at the source code of the plugin. The build page appeared to be empty.
> > >
> > > On a related note, once I checked out the code from svn and started
> > > building the plugin, it started downloading Geronimo 1.1 and 1.2 bits.
> > > So I was wondering what is the reason for the plugin to support all
> > > previous versions of Geronimo?. Why not have a plugin that's specific
> > > to a particular version of Geronimo? For example, plugin 2.0.x
> > > supports and works only with G 2.0.x.
> > >
> > > Jarek
> > >
> > > On 10/2/07, Ted Kirby <[EMAIL PROTECTED]> wrote:
> > >> Can someone put updated doc for developing the geronimo eclipse and
> > >> J2G plugins in the wiki, and link to them from the devtools home
> page?
> > >>
> > >> http://cwiki.apache.org/GMOxDOC11/geronimo-eclipse-plugin-faq.htmlhas
> > >> doc for the 1.x plugin.  There is a link to a blank page for the
> > >> eclipse plugin from the devtools page, but no similar link for j2g.
> > >>
> > >> This would be helpful.  I tried to find that blank page for the
> > >> eclipse plugin in the wiki to update it, but was unsuccessful.  What
> > >> is the URL for the wiki page to
> > >>
> http://geronimo.apache.org/developing-the-geronimo-eclipse-plugin-in-eclipse.html
> > >> ?  Or, is this not a page that is generally accessible?
> > >>
> > >> Thanks,
> > >> Ted Kirby
> > >>
> > >
> >
> > --
> > Thanks,
> > Tim McConnell
> >
>

Re: System Module descriptions

[Hernan Cunico]

Hi Ted,
it would be great to add which modules are critical for Geronimo to run, in 
other words, those we should never mess with. We had a discussion some time ago 
but I don't think we ever properly covered this.

Cheers!
Hernan

Ted Kirby wrote:

I have added this wiki page
http://cwiki.apache.org/GMOxDOC20/system-modules.html to list the
modules that come with the (2.0.1) server, along with:

1. A brief description of what the module does
2. Is it started by default, or
3. Should it never be started?

This is a first draft.  I solicit feedback and encourage folks to
update the page as appropriate.  There are some modules with which I
am not familiar.

Ted Kirby

Re: svn commit: r578812 - /geronimo/server/trunk/configs/jetty6/src/main/plan/plan.xml

[Vamsavardhana Reddy]

I am surprised that the ServerInfo reference is not there in the file
because
http://svn.apache.org/viewvc/geronimo/server/trunk/configs/jetty6/src/plan/plan.xml?r1=577801&r2=577800&pathrev=577801shows
that it is there in the commit!!

Vamsi

On 9/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Author: djencks
> Date: Mon Sep 24 06:42:43 2007
> New Revision: 578812
>
> URL: http://svn.apache.org/viewvc?rev=578812&view=rev
> Log:
> GERONIMO-2964 apparently missed new reference
>
> Modified:
> geronimo/server/trunk/configs/jetty6/src/main/plan/plan.xml
>
> Modified: geronimo/server/trunk/configs/jetty6/src/main/plan/plan.xml
> URL:
> http://svn.apache.org/viewvc/geronimo/server/trunk/configs/jetty6/src/main/plan/plan.xml?rev=578812&r1=578811&r2=578812&view=diff
>
> ==
> --- geronimo/server/trunk/configs/jetty6/src/main/plan/plan.xml (original)
> +++ geronimo/server/trunk/configs/jetty6/src/main/plan/plan.xml Mon Sep 24
> 06:42:43 2007
> @@ -41,9 +41,12 @@
>
>  
>  
> -  
> -JettyWebManager
> -  
> +
> +JettyWebManager
> +
> +
> +ServerInfo
> +
>  
>
>  
> @@ -88,29 +91,29 @@
>  
>
>  
> -
> -
> +
> +
>  
>  ${PlanServerHostname}
>  ${PlanHTTPSPort}
>
>
>

[jira] Commented: (GERONIMO-3354) Exception thrown by MDB involved in XA transaction

[Manu T George (JIRA)]

[ 
https://issues.apache.org/jira/browse/GERONIMO-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532029
 ] 

Manu T George commented on GERONIMO-3354:
-

Related issues that need to be fixed for this issue

https://issues.apache.org/activemq/browse/AMQ-1438
https://issues.apache.org/jira/browse/OPENEJB-702

> Exception thrown by MDB involved in XA transaction
> --
>
> Key: GERONIMO-3354
> URL: https://issues.apache.org/jira/browse/GERONIMO-3354
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: transaction manager
>Affects Versions: 2.0, 2.0.x, 2.1
> Environment: Geronimo 2.0 (tomcat) build from 07/24 
> (http://people.apache.org/~prasad/binaries/20070724/)
> DayTrader 1.2 or 2.0 (any runtime mode) with asyn order processing enabled
>Reporter: Christopher James Blythe
>Priority: Critical
> Fix For: 2.0.x, 2.1
>
>
> The async order processing in DayTrader uses the TradeBrokerMDB to handle 
> complete order operations whenever a buy or sell is performed. When these 
> transactions are executed, the transaction appears to complete; however, the 
> following exception is written to the console and log file.
> According to Jencks, this seems to indicate that the tx info is not being 
> written to the transaction log. 
> 22:59:18,421 ERROR [Transaction] Please correct the integration and supply a 
> NamedXAResource
> java.lang.IllegalStateException : Cannot log transactions as [EMAIL 
> PROTECTED] is not a NamedXAResource.
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl$TransactionBranch.getResourceName(TransactionImpl.java
>  :697)
> at org.apache.geronimo.transaction.log.HOWLLog.prepare(HOWLLog.java:254)
> at 
> org.apache.geronimo.transaction.log.HOWLLog$$FastClassByCGLIB$$7315be2e.invoke()
> at net.sf.cglib.reflect.FastMethod.invoke (FastMethod.java:53)
> at 
> org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
> at 
> org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
> at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke 
> (GBeanInstance.java:830)
> 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$$ba0af455.prepare()
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.internalPrepare(TransactionImpl.java
>  :444)
> at 
> org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:316)
> at 
> org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:238)
> at 
> org.apache.openejb.core.transaction.TransactionPolicy.commitTransaction(TransactionPolicy.java:139)
> at 
> org.apache.openejb.core.transaction.TxRequired.afterInvoke(TxRequired.java:75)
> at org.apache.openejb.core.mdb.MdbContainer.afterDelivery 
> (MdbContainer.java:375)
> at 
> org.apache.openejb.core.mdb.EndpointHandler.afterDelivery(EndpointHandler.java:274)
> at 
> org.apache.openejb.core.mdb.EndpointHandler.invoke(EndpointHandler.java:164)
> at $Proxy36.afterDelivery(Unknown Source)
> at 
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:126)
> at 
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:65)
> at 
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:216)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
> at org.apache.activemq.ra.ServerSessionImpl.run( 
> ServerSessionImpl.java:165)
> at 
> org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:290)
> at 
> org.apache.geronimo.connector.work.pool.NamedRunnable.run(NamedRunnable.java:32)
> at org.apache.geronimo.pool.ThreadPool$1.run (ThreadPool.java:201)
> at 
> org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:801)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (GERONIMO-3496) Assemble servers out of plugins

[David Jencks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GERONIMO-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Jencks closed GERONIMO-3496.
--

Resolution: Fixed

rev 581510, accidental files removed rev 581511, tck servers fixed up rev 2450.

This works for me. I've run into several versioning problems and it's possible 
that others may find different ones than I did, so this might take some ironing 
out.

> Assemble servers out of plugins
> ---
>
> Key: GERONIMO-3496
> URL: https://issues.apache.org/jira/browse/GERONIMO-3496
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: buildsystem
>Affects Versions: 2.0.2
>Reporter: David Jencks
>Assignee: David Jencks
> Fix For: 2.1
>
>
> Assemble our servers out of plugins rather than just cars.  In practical 
> terms this means that the config.xm, config-substitutions.properties, and 
> artifact_aliases.properties files are constructed by aggregating the entries 
> from the geronimo-plugin.xmls for the car files/plugins.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.