geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <>
Subject Re: [JMX] Streaming data to an MBean
Date Mon, 08 Sep 2003 17:49:03 GMT
	Well my hope would be to avoid a workaround such as a servlet.  
I'm hoping our basic JMX interface has some provision for streaming 
large transfers.  If that doesn't work out, we can work on the servlet 
angle.  But that's got its own complexities -- we'd need some kind of 
special handling so it's always deployed, even if the web container is 
otherwise set up for virtual hosting or tight security or something.  On 
the other hand, it would provide a convenient way to lock down deployment 
activity to system admins only, whereas the JMX interface seems to be wide 


On Mon, 8 Sep 2003, Siva wrote:
> I feel a 2 level staging environment,where a servlet maps
> a file upload to a local path and then starts deploying is
> better than a direct byte array load.
> Siva
> ----- Original Message -----
> From: "Aaron Mulder" <>
> To: <>
> Sent: Monday, September 08, 2003 5:34 PM
> Subject: [JMX] Streaming data to an MBean
> > The JSR-88 implementation needs to send the finished module to the
> > server to deploy, which can generally happen over the network.  The only
> > way I know of to invoke a server component this way is to defined an MBean
> > method that takes a byte array.  But I'd really rather avoid loading the
> > whole module in memory (I've seen 10MB EARs before, usually full of static
> > content and third-party libraries, and I'm sure that's not the biggest).
> >
> > Is there any way to stream the data to a JMX MBean, and let it
> > spool it to disk as it arrives?
> >
> > Or should we consider having something like an always-on servlet
> > that accepts application uploads from the JSR-88 deployer, puts them
> > somewhere sensible on disk, and returns a URL on the server filesystem
> > which then the JSR-88 deployer can pass with the DDs to a normal deploy
> > call on a deployer MBean?
> >
> > Thanks,
> > Aaron
> >

View raw message