Christian Kaiser wrote: > I would really like to know why you don't recommend this. Is it for > performance reasons? Isn't the same thing when I change the tools scope > to 'request'? Yes, performance is the key here. The difference is that this switch makes *all* tools refresh themselves on every request, while the scope change affects your single tool only. Again, I can only emphasize that RunData objects should not be used in any other scope than request. Because they are pooled, recycled and reused, your tool might end up in using the data of another request - which is the case if the RunData object you just used is assigned to a different thread or session. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
I have never had a problem accessing pull tools from Velocity, whether the page contains Javascript that causes the form submittal (because of a mouse click, the browser closing, etc) or whether the user is hammering away at the keyboard. What is puzzling is how the tool is accessing a null reference to RunData since you are passing in the $data parameter from within the template. I have literally beaten/stress tested my forms to intentionally generate overlapping requests, and I make heavy use of pull tools (that I have written myself), and I have never had this type of null $data reference within a tool. From my experience the pull tool concept is sound. It sounds as if one of the tools you are are accessing is not re-entrant, meaning that internally it is storing a temporary reference to RunData (rather than internally passing RunData as a parameter to every internal method call). Then at some insignificant time later within the same sequence of steps it is trying to reference this temporarily stored reference. In a hard hitting, asynchronous model this could obviously fail. (Or instead of a reference to RunData, a tool could also be trying to access the same long running resource, data retrieval, storing data, etc, in which case it would need to control access to the resource, or maintain state using an external resource). From what I understand, no matter how quickly you submit overlapping requests (even for the same session), each will have its own unique instance of RunData, so the RunData model itself is probably not the issue. What happens within the application when these different requests are asynchronously accessing the same resources can be solved through the implementation of the tool. Christian Kaiser wrote: >> (1) You create an object and while initializing it you store a reference >> to RunData. A reference to this object is stored in the session. >> ... >> > > > > My code doesn't store objects to RunData. Turbines does. > > > Hm, the pull tools i am talking about are using TurbineServices. > > These services are fetched from Turbine with the RunData as parameter. > The services uses a key from the session to get specific data. > Just to repeat it: If rundata.isDisposed --> session is null --> NPE. > > This approach was designed by Henning Schmiedehausen a while ago, so I > assume thats ok. This was with turbine version 2.3.1 resp 2.3.2-rc1 > > Maybe we shouldn't have upgraded to 2.3.3. ?? > > > My conclusion of turbine behaviour for now: > > If you use simple http requests (non-ajax), you won't have too much > trouble besides some ERROR logs resulting from a disposed rundata. > This may happen if a user doesn't wait for a long request to return, and > sends another request which overtakes the first one. > The user would not note anything, because his second request will be > performed correctly. > So, we have only errors in the log files as result. Ok, in bad designed > software it may lead to data inconsistency, but that might be too far > fetched for now. > > Things get worse, if you have asynchronous ajax requests AND you use > pull tools from velocity templates to generate the response. > > In this case, I suggest to refresh the rundata in all used tools per > request. > > christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > >
> (1) You create an object and while initializing it you store a reference > to RunData. A reference to this object is stored in the session. > ... My code doesn't store objects to RunData. Turbines does. Hm, the pull tools i am talking about are using TurbineServices. These services are fetched from Turbine with the RunData as parameter. The services uses a key from the session to get specific data. Just to repeat it: If rundata.isDisposed --> session is null --> NPE. This approach was designed by Henning Schmiedehausen a while ago, so I assume thats ok. This was with turbine version 2.3.1 resp 2.3.2-rc1 Maybe we shouldn't have upgraded to 2.3.3. ?? My conclusion of turbine behaviour for now: If you use simple http requests (non-ajax), you won't have too much trouble besides some ERROR logs resulting from a disposed rundata. This may happen if a user doesn't wait for a long request to return, and sends another request which overtakes the first one. The user would not note anything, because his second request will be performed correctly. So, we have only errors in the log files as result. Ok, in bad designed software it may lead to data inconsistency, but that might be too far fetched for now. Things get worse, if you have asynchronous ajax requests AND you use pull tools from velocity templates to generate the response. In this case, I suggest to refresh the rundata in all used tools per request. christian --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
> services.PullService.tools.per.request.refresh=true Nice, thanks for the hint. > I do not recommend this for production use, however. I would really like to know why you don't recommend this. Is it for performance reasons? Isn't the same thing when I change the tools scope to 'request'? christian --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Christian Kaiser wrote: > It seems I get same sessions for different RunData instances. ... and vice versa. This is because RunData objects are pooled. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Christian Kaiser wrote: > I can prevent from this, when I set the tool in a request scope. Yes, this is the way to do it. > That means the refresh method of the RunDataApplicationTool is not > called, but the Rundata is passed to the Tool with the init method. The refresh()-method call can be forced by setting services.PullService.tools.per.request.refresh=true The comment in the original TurbineResources.properties file is like this (which explains it all) ---8<--- # This determines whether the non-request tools are refreshed # on each request (request tools aren't ever, because they're # instantiated for the request only anyway). services.PullService.tools.per.request.refresh=true ---8<--- I do not recommend this for production use, however. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Let me see if I have this straight... (1) You create an object and while initializing it you store a reference to RunData. A reference to this object is stored in the session. ... (2) Another event takes place causing you to reference the session object, where you in turn attempt to use the original reference to your original RunData object ... Instead of (1) and (2) simply include a reference of RunData as a parameter to the methods on your object... Do not store any references to any instance of RunData. Also, you should not care if you are working with different instances of RunData as each instance is single use (per event). FYI... I would use a parameter approach rather than an init approach... Depending upon implementations, I have seen cases where the form object gets called, then the event, and then the form gets called redundantly... Even if you are referencing an event (where you might always expect the event to be first in the sequence). ... If you are worried about maintaining state just use the methods on the current RunData instance to access whatever you have stored in the session. Your state is maintained in the session, and not in any particular instance of RunData. Christian Kaiser wrote: > I think I got it now. > Please correct me if I misconceive. > log: > > 14:51:27,027 [TP-Processor8] DEBUG ...BmsRunData > recycle ...BmsRunData@1f3bb61 > 14:51:27,033 [TP-Processor8] DEBUG ...ModelTool - > refresh ...BmsRunData@1f3bb61 > > 14:51:27,168 [TP-Processor2] DEBUG ...BmsRunData - > recycle ...BmsRunData@3e65be > 14:51:27,183 [TP-Processor2] DEBUG ...ModelTool - > refresh ...BmsRunData@3e65be > 14:51:27,245 [TP-Processor2] DEBUG ...BmsRunData - > dispose ...BmsRunData@3e65be > > 14:51:27,249 [TP-Processor8] ERROR ...ModelTool - NPE > for ...BmsRunData@3e65be > 14:51:27,256 [TP-Processor8] DEBUG ...BmsRunData - > dispose ...BmsRunData@1f3bb61 > > > Processor2 overtakes Processor8. > > The modeltool runs in session scope, so only one instance of it exists. > After P8 refreshes the rundata in the tool, > P2 overwrites it with its rundata. > P2 finished and disposed the rundata. > The model tool in P8 has a disposed rundata. > > > I can prevent from this, when I set the tool in a request scope. > That means the refresh method of the RunDataApplicationTool is not > called, but the Rundata is passed to the Tool with the init method. > The tool gets initialized on every request. > > Thats about it for now. > Feel free to add your thoughts. > Thanks for your hints, so far. > > Christian > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
I think I got it now. Please correct me if I misconceive. log: 14:51:27,027 [TP-Processor8] DEBUG ...BmsRunData recycle ...BmsRunData@1f3bb61 14:51:27,033 [TP-Processor8] DEBUG ...ModelTool - refresh ...BmsRunData@1f3bb61 14:51:27,168 [TP-Processor2] DEBUG ...BmsRunData - recycle ...BmsRunData@3e65be 14:51:27,183 [TP-Processor2] DEBUG ...ModelTool - refresh ...BmsRunData@3e65be 14:51:27,245 [TP-Processor2] DEBUG ...BmsRunData - dispose ...BmsRunData@3e65be 14:51:27,249 [TP-Processor8] ERROR ...ModelTool - NPE for ...BmsRunData@3e65be 14:51:27,256 [TP-Processor8] DEBUG ...BmsRunData - dispose ...BmsRunData@1f3bb61 Processor2 overtakes Processor8. The modeltool runs in session scope, so only one instance of it exists. After P8 refreshes the rundata in the tool, P2 overwrites it with its rundata. P2 finished and disposed the rundata. The model tool in P8 has a disposed rundata. I can prevent from this, when I set the tool in a request scope. That means the refresh method of the RunDataApplicationTool is not called, but the Rundata is passed to the Tool with the init method. The tool gets initialized on every request. Thats about it for now. Feel free to add your thoughts. Thanks for your hints, so far. Christian --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
It seems I get same sessions for different RunData instances. 2009-12-02 10:48:37,132 [TP-Processor1] DEBUG ...BmsRunData - recycle ...BmsRunData@edd8bc SessionID No Session 2009-12-02 10:48:37,139 [TP-Processor1] DEBUG ...ModelTool - refresh ...BmsRunData@edd8bc SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,141 [TP-Processor1] DEBUG ...BmsRunData - dispose ...BmsRunData@edd8bc SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,315 [TP-Processor3] DEBUG ...BmsRunData - recycle ...BmsRunData@402c41 SessionID No Session 2009-12-02 10:48:37,323 [TP-Processor3] DEBUG ...ModelTool - refresh ...BmsRunData@402c41 SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,488 [TP-Processor3] DEBUG ...BmsRunData - dispose ...BmsRunData@402c41 SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,776 [TP-Processor8] DEBUG ...BmsRunData - recycle ...BmsRunData@edd8bc SessionID No Session 2009-12-02 10:48:37,784 [TP-Processor8] DEBUG ...ModelTool - refresh ...BmsRunData@edd8bc SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,793 [TP-Processor8] DEBUG ...BmsRunData - dispose ...BmsRunData@edd8bc SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,979 [TP-Processor5] DEBUG ...BmsRunData - recycle ...BmsRunData@402c41 SessionID No Session 2009-12-02 10:48:37,987 [TP-Processor5] DEBUG ...ModelTool - refresh ...BmsRunData@402c41 SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 2009-12-02 10:48:37,990 [TP-Processor5] DEBUG ...BmsRunData - dispose ...BmsRunData@402c41 SessionID 13E9EEE6182B2F7E8D9053C08676FFE1 greetings christian Am Dienstag, den 01.12.2009, 18:59 -0600 schrieb Tony Oslund: > Are you getting new sessions? > > You stated that you have different instances of rundata. > > Are you getting unique session id's? > > Tony > > On Dec 1, 2009, at 3:05 AM, Christian Kaiser <christian.kaiser@bluecellnetworks.com > > wrote: > > > Am Montag, den 30.11.2009, 19:12 +0000 schrieb Sheldon Ross: > >> > >> Are you sure your action is not generating a form submittal at the > >> same time as an ajax request? > > > > Yes I am sure. > > I can provoke this by entering two URLs in the browser, one after the > > other. > > > > christian > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > > For additional commands, e-mail: user-help@turbine.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > Christian Kaiser | Softwareentwicklung blue cell networks GmbH Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67 121 | fax: +49 (0) 951-30 20 67 201 email: christian.kaiser@bluecellnetworks.com | skype: bcn_christian.kaiser | web: www.bluecellnetworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Are you getting new sessions? You stated that you have different instances of rundata. Are you getting unique session id's? Tony On Dec 1, 2009, at 3:05 AM, Christian Kaiser <christian.kaiser@bluecellnetworks.com > wrote: > Am Montag, den 30.11.2009, 19:12 +0000 schrieb Sheldon Ross: >> >> Are you sure your action is not generating a form submittal at the >> same time as an ajax request? > > Yes I am sure. > I can provoke this by entering two URLs in the browser, one after the > other. > > christian > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
maybe it has to do with scope of the pull tools I am using.
I use the ModelService, done by Henning, maybe you know it.
The model tool runs in authorized scope and uses the contents of the
rundata to get a model.
As far as I understand it, a rundata object will be passed to the tool
when the session gets initialized.
This tool will be used by all requests. It may happen that the rundata
object, stored in the tool, is disposed when some request wants to fetch
a model with it.
I tried to put the tool in request scope. But it seems that the tool
doesn't get a refresh call with the rundata object in that scope.
I am not sure if I am on the right path, but hopefully this helps you to
understand my set up.
christian
Am Dienstag, den 01.12.2009, 11:08 +0100 schrieb Christian Kaiser:
> logs proof that there are multiple RunData Objects:
>
> 2009-12-01 11:03:08,673 [TP-Processor6] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- recycle de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:08,752 [TP-Processor6] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- dispose de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:08,981 [TP-Processor8] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- recycle de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:09,109 [TP-Processor8] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- dispose de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:09,357 [TP-Processor8] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- recycle de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:09,557 [TP-Processor2] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- dispose de.beamzone.sm.service.rundata.BmsRunData@296a42
> 2009-12-01 11:03:09,795 [TP-Processor8] ERROR de.beamzone.sm.tools.ModelTool - Cannot
get model Campaign for RunData de.beamzone.sm.service.rundata.BmsRunData@296a42. Error: java.lang.NullPointerException
> 2009-12-01 11:03:09,984 [TP-Processor8] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- dispose de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:10,385 [TP-Processor7] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- recycle de.beamzone.sm.service.rundata.BmsRunData@296a42
> 2009-12-01 11:03:10,392 [TP-Processor7] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- dispose de.beamzone.sm.service.rundata.BmsRunData@296a42
> 2009-12-01 11:03:10,573 [TP-Processor3] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- recycle de.beamzone.sm.service.rundata.BmsRunData@1afc148
> 2009-12-01 11:03:10,603 [TP-Processor3] DEBUG de.beamzone.sm.service.rundata.BmsRunData
- dispose de.beamzone.sm.service.rundata.BmsRunData@1afc148
>
>
>
> Am Dienstag, den 01.12.2009, 10:00 +0100 schrieb Christian Kaiser:
> > First of all, thanks for your answers. :-)
> >
> > Am Montag, den 30.11.2009, 18:34 +0100 schrieb Thomas Vandahl:
> > > Christian Kaiser wrote:
> > > > If the ajax request is the first request to finish, it disposes the
> > > > RunData.
> > > > This leads to bad behavour of my http request, because this request has
> > > > to deal with a disposed RunData.
> > >
> > > RunData is a per-request object that is borrowed from a pool at request
> > > creation and returned (and recycled) at request completion. A RunData
> > > object is not meant to be shared between different requests. If you
> > > believe you must do this, you have a serious design problem in your
> > > software.
> >
> > Ok, I don't believe I must do this.
> > I thought it is meant to be that way.
> >
> >
> >
> >
> >
> > >
> > > Then again, your main screen request and your Ajax request are totally
> > > unrelated from Turbine's point of view. They should use two different
> > > RunData objects anyway.
> >
> > Concerning your previous mentioned point, I don't think that this issue
> > is Ajax related any more. I face the same problem with ordinary
> > requests, sent fast in row.
> > If one request overtakes the other while processing, it ends up in a
> > disposed Rundata of the first request, too.
> >
> >
> > >
> > > > Is this a common problem?
> > > > Can I prevent from it?
> > >
> > > No, this should not happen at any time.
> > >
> > That sounds promising.
> > >
> > > > Please let me now if I can provide you with additional information.
> > >
> > > Well, yes. Let's have a look at some code. This problem sounds very
> > > strange to me.
> > >
> > >
> > >
> >
> > I overwrote The DefaultTurbineRunData. ( I think this was to identify disposed rundata
??).
> >
> > /**
> > *
> > * Gets the servlet session information. Return null if data expired.
> > *
> > * @return the session.
> > */
> > public HttpSession getSession() {
> > HttpServletRequest request = getRequest();
> >
> > if (request == null) {
> >
> > return null;
> >
> > }
> >
> > return request.getSession();
> > }
> >
> > Let me know which other code is of interest.
> >
> > Thanks,
> > christian
> >
> >
> >
> > > Bye, Thomas.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> > > For additional commands, e-mail: user-help@turbine.apache.org
> > >
> >
> >
> > Christian Kaiser | Softwareentwicklung
> >
> > blue cell networks GmbH
> >
> >
> >
> > Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67
> > 121 | fax: +49 (0) 951-30 20 67 201
> >
> > email: christian.kaiser@bluecellnetworks.com | skype:
> > bcn_christian.kaiser | web: www.bluecellnetworks.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> > For additional commands, e-mail: user-help@turbine.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
>
Christian Kaiser | Softwareentwicklung
blue cell networks GmbH
Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67
121 | fax: +49 (0) 951-30 20 67 201
email: christian.kaiser@bluecellnetworks.com | skype:
bcn_christian.kaiser | web: www.bluecellnetworks.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
For additional commands, e-mail: user-help@turbine.apache.org
logs proof that there are multiple RunData Objects:
2009-12-01 11:03:08,673 [TP-Processor6] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - recycle
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:08,752 [TP-Processor6] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - dispose
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:08,981 [TP-Processor8] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - recycle
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:09,109 [TP-Processor8] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - dispose
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:09,357 [TP-Processor8] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - recycle
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:09,557 [TP-Processor2] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - dispose
de.beamzone.sm.service.rundata.BmsRunData@296a42
2009-12-01 11:03:09,795 [TP-Processor8] ERROR
de.beamzone.sm.tools.ModelTool - Cannot get model Campaign for RunData
de.beamzone.sm.service.rundata.BmsRunData@296a42. Error:
java.lang.NullPointerException
2009-12-01 11:03:09,984 [TP-Processor8] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - dispose
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:10,385 [TP-Processor7] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - recycle
de.beamzone.sm.service.rundata.BmsRunData@296a42
2009-12-01 11:03:10,392 [TP-Processor7] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - dispose
de.beamzone.sm.service.rundata.BmsRunData@296a42
2009-12-01 11:03:10,573 [TP-Processor3] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - recycle
de.beamzone.sm.service.rundata.BmsRunData@1afc148
2009-12-01 11:03:10,603 [TP-Processor3] DEBUG
de.beamzone.sm.service.rundata.BmsRunData - dispose
de.beamzone.sm.service.rundata.BmsRunData@1afc148
Am Dienstag, den 01.12.2009, 10:00 +0100 schrieb Christian Kaiser:
> First of all, thanks for your answers. :-)
>
> Am Montag, den 30.11.2009, 18:34 +0100 schrieb Thomas Vandahl:
> > Christian Kaiser wrote:
> > > If the ajax request is the first request to finish, it disposes the
> > > RunData.
> > > This leads to bad behavour of my http request, because this request has
> > > to deal with a disposed RunData.
> >
> > RunData is a per-request object that is borrowed from a pool at request
> > creation and returned (and recycled) at request completion. A RunData
> > object is not meant to be shared between different requests. If you
> > believe you must do this, you have a serious design problem in your
> > software.
>
> Ok, I don't believe I must do this.
> I thought it is meant to be that way.
>
>
>
>
>
> >
> > Then again, your main screen request and your Ajax request are totally
> > unrelated from Turbine's point of view. They should use two different
> > RunData objects anyway.
>
> Concerning your previous mentioned point, I don't think that this issue
> is Ajax related any more. I face the same problem with ordinary
> requests, sent fast in row.
> If one request overtakes the other while processing, it ends up in a
> disposed Rundata of the first request, too.
>
>
> >
> > > Is this a common problem?
> > > Can I prevent from it?
> >
> > No, this should not happen at any time.
> >
> That sounds promising.
> >
> > > Please let me now if I can provide you with additional information.
> >
> > Well, yes. Let's have a look at some code. This problem sounds very
> > strange to me.
> >
> >
> >
>
> I overwrote The DefaultTurbineRunData. ( I think this was to identify disposed rundata
??).
>
> /**
> *
> * Gets the servlet session information. Return null if data expired.
> *
> * @return the session.
> */
> public HttpSession getSession() {
> HttpServletRequest request = getRequest();
>
> if (request == null) {
>
> return null;
>
> }
>
> return request.getSession();
> }
>
> Let me know which other code is of interest.
>
> Thanks,
> christian
>
>
>
> > Bye, Thomas.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> > For additional commands, e-mail: user-help@turbine.apache.org
> >
>
>
> Christian Kaiser | Softwareentwicklung
>
> blue cell networks GmbH
>
>
>
> Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67
> 121 | fax: +49 (0) 951-30 20 67 201
>
> email: christian.kaiser@bluecellnetworks.com | skype:
> bcn_christian.kaiser | web: www.bluecellnetworks.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
For additional commands, e-mail: user-help@turbine.apache.org
Am Montag, den 30.11.2009, 19:12 +0000 schrieb Sheldon Ross: > > Are you sure your action is not generating a form submittal at the > same time as an ajax request? Yes I am sure. I can provoke this by entering two URLs in the browser, one after the other. christian --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
First of all, thanks for your answers. :-)
Am Montag, den 30.11.2009, 18:34 +0100 schrieb Thomas Vandahl:
> Christian Kaiser wrote:
> > If the ajax request is the first request to finish, it disposes the
> > RunData.
> > This leads to bad behavour of my http request, because this request has
> > to deal with a disposed RunData.
>
> RunData is a per-request object that is borrowed from a pool at request
> creation and returned (and recycled) at request completion. A RunData
> object is not meant to be shared between different requests. If you
> believe you must do this, you have a serious design problem in your
> software.
Ok, I don't believe I must do this.
I thought it is meant to be that way.
>
> Then again, your main screen request and your Ajax request are totally
> unrelated from Turbine's point of view. They should use two different
> RunData objects anyway.
Concerning your previous mentioned point, I don't think that this issue
is Ajax related any more. I face the same problem with ordinary
requests, sent fast in row.
If one request overtakes the other while processing, it ends up in a
disposed Rundata of the first request, too.
>
> > Is this a common problem?
> > Can I prevent from it?
>
> No, this should not happen at any time.
>
That sounds promising.
>
> > Please let me now if I can provide you with additional information.
>
> Well, yes. Let's have a look at some code. This problem sounds very
> strange to me.
>
>
>
I overwrote The DefaultTurbineRunData. ( I think this was to identify disposed rundata ??).
/**
*
* Gets the servlet session information. Return null if data expired.
*
* @return the session.
*/
public HttpSession getSession() {
HttpServletRequest request = getRequest();
if (request == null) {
return null;
}
return request.getSession();
}
Let me know which other code is of interest.
Thanks,
christian
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
>
Christian Kaiser | Softwareentwicklung
blue cell networks GmbH
Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67
121 | fax: +49 (0) 951-30 20 67 201
email: christian.kaiser@bluecellnetworks.com | skype:
bcn_christian.kaiser | web: www.bluecellnetworks.com
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
For additional commands, e-mail: user-help@turbine.apache.org
Are you sure your action is not generating a form submittal at the same time as an ajax request? For instance, if you have a <button> object on a page with in a form, in most browsers that will submit the form even if you only wanted the button onclick listener to launch an ajax event. Sheldon Ross > Subject: ajax and rundata disposal > From: christian.kaiser@bluecellnetworks.com > To: user@turbine.apache.org > Date: Mon, 30 Nov 2009 16:42:59 +0100 > > Dear Turbine Users, > > I have hard times with the disposal of the rundata. > > I integrated the json-rpc service in my turbine 2.3.3 application. > > Now when worst comes to worst, a common http request (user click) is > sent at the same time as an automated ajax request that tries to build > up the last site. > > If the ajax request is the first request to finish, it disposes the > RunData. > This leads to bad behavour of my http request, because this request has > to deal with a disposed RunData. > > > Is this a common problem? > Can I prevent from it? > > Thanks in advance for your help. > > Please let me now if I can provide you with additional information. > > christian > > > > > > > > > > Christian Kaiser | Softwareentwicklung > > blue cell networks GmbH > > > > Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67 > 121 | fax: +49 (0) 951-30 20 67 201 > > email: christian.kaiser@bluecellnetworks.com | skype: > bcn_christian.kaiser | web: www.bluecellnetworks.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > _________________________________________________________________ Hotmail: Trusted email with Microsoft's powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141664/direct/01/ http://clk.atdmt.com/GBL/go/177141664/direct/01/
Christian Kaiser wrote: > If the ajax request is the first request to finish, it disposes the > RunData. > This leads to bad behavour of my http request, because this request has > to deal with a disposed RunData. RunData is a per-request object that is borrowed from a pool at request creation and returned (and recycled) at request completion. A RunData object is not meant to be shared between different requests. If you believe you must do this, you have a serious design problem in your software. Then again, your main screen request and your Ajax request are totally unrelated from Turbine's point of view. They should use two different RunData objects anyway. > Is this a common problem? > Can I prevent from it? No, this should not happen at any time. > Please let me now if I can provide you with additional information. Well, yes. Let's have a look at some code. This problem sounds very strange to me. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Dear Turbine Users, I have hard times with the disposal of the rundata. I integrated the json-rpc service in my turbine 2.3.3 application. Now when worst comes to worst, a common http request (user click) is sent at the same time as an automated ajax request that tries to build up the last site. If the ajax request is the first request to finish, it disposes the RunData. This leads to bad behavour of my http request, because this request has to deal with a disposed RunData. Is this a common problem? Can I prevent from it? Thanks in advance for your help. Please let me now if I can provide you with additional information. christian Christian Kaiser | Softwareentwicklung blue cell networks GmbH Hainstraße 14 | 96047 Bamberg, Germany | phone:+49 (0) 951-30 20 67 121 | fax: +49 (0) 951-30 20 67 201 email: christian.kaiser@bluecellnetworks.com | skype: bcn_christian.kaiser | web: www.bluecellnetworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
The Fulcrum Intake team is pleased to announce the fulcrum-intake-1.0.6 release! Fulcrum Intake Service Changes in this version include: New features: o Added locale handling to Intake, added user-defined field types. Fixed Bugs: o Catch only Exceptions that are actually thrown. o Intake won't use interfaces for the mapTo() method. Issue: TRB-11. Thanks to Evan Koffler. o The number validators did not set an invalid number message when initialized with the default constructor Issue: TRB-74. Thanks to Susi Berrington. o Intake did not correctly parse the message of a rule or required-message from intake.xml Issue: TRB-68. Thanks to Ronny Voelker. o Intake was not handling empty values correctly. Issue: TRB-9. Thanks to Jürgen Hoffmann. o Intake was not loading the correct Default Validators when the rules for a field are empty. Issue: TRB-14. Thanks to Jürgen Hoffmann. Changes: o Moved the initialization code of the service implementation to initialize() o Removed the dependency on ORO by replacing the regular expression handling with java.util.regexp. This might have slight implications on the regexp syntax. o Use the localize features of the parser to simplify the value assignment in Intake fields. Made handling of empty values consistent over all number field types. o Updated locale handling to use the new localized parameter parser. This removes the dependency from LocalizationService o Intake now handles the case where the mapToObject does not map to all fields in the group. Issue: TRB-9. Thanks to Jürgen Hoffmann. o Update to Apache License 2.0 o Use inherited getLogger() instead of Log in classes extending AbstractLogEnabled. Removed: o Removed the Intake class. It was duplicating the IntakeServiceFacade. Have fun! -Fulcrum Intake team --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Yes. - Madhu -----Original Message----- From: Thomas Vandahl [mailto:tv@apache.org] Sent: Sunday, November 22, 2009 10:27 PM To: Turbine Users List Subject: Re: Does links need to be case sensitive? On 19.11.09 15:38, Ludwig Magnusson wrote: > Hello! > > We had a problem with our screen classes. In some cases they weren't loaded. > I noticed that the loading was screen-sensitive so that if I typed in the > url www.mydomain.com/mypage.vm and the site had a screen class called > MyPage.java, it was never executed. > > > > Is there any way around this? Yes. The mapping of templates to classes is done by the JavaScreenFactory IIRC. This factory is pluggable so you can roll your own. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org "Legal Disclaimer: This electronic message and all contents contain information from Cybage Software Private Limited which may be privileged, confidential, or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution, or use of the contents of this message is strictly prohibited. If you have received this electronic message in error please notify the sender by reply e-mail to and destroy the original message and all copies. Cybage has taken every reasonable precaution to minimize the risk of malicious content in the mail, but is not liable for any damage you may sustain as a result of any malicious content in this e-mail. You should carry out your own malicious content checks before opening the e-mail or attachment." www.cybage.com --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
On 19.11.09 15:38, Ludwig Magnusson wrote: > Hello! > > We had a problem with our screen classes. In some cases they weren't loaded. > I noticed that the loading was screen-sensitive so that if I typed in the > url www.mydomain.com/mypage.vm and the site had a screen class called > MyPage.java, it was never executed. > > > > Is there any way around this? Yes. The mapping of templates to classes is done by the JavaScreenFactory IIRC. This factory is pluggable so you can roll your own. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Hi,
I do. We had a strange deaths of our turbine web apps last year. The
problem was at 64b Java at Linux in version 1.6.0 between updates 5 and
8 (approximately). We always received the trace, that the java proces
died, and always at the same place. We discovered, that it was in the
village library, but the problem couldn't be repeatable at developer's
boxes. Afterwards we discovered, that the problem was in the java hot
spot and it occured only, when the village library wasn't processed via
the hot spot in approximately 10 minutes after the start. If it happened
later, the proces died. Everything runs well after the big Java 6 update
nr. 10. There are no more problems from that time.
But still, our crash looked different, no nice informations about the
shutdown in the log file, just the core dump ;-)
Best regards
Tom
Thomas Vandahl wrote:
> Sheldon Ross wrote:
>
>> Tomcat is shutting down. There are no java processes on the server after this happens.
The machine itself is still up and running fine.
>>
>
> Look into catalina.out if it exists. Sometimes the JVM just decides to
> die. BTW: Anyone having experience with JAI crashing/hanging the JVM?
>
>
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org
> For additional commands, e-mail: user-help@turbine.apache.org
>
--
HSF logo
Ing. Tomas Metz jr.
HSF spol. s r. o.
tel : +420 352 638 111
mob : +420 724 005 323
email : tomm@hsf.cz
jabber: tom.metz@jabber.cz
www : www.hsf.cz <http://www.hsf.cz>
<http://www.hsf.cz>
Tato zpráva obsahuje důvěrné a/nebo právně chráněné informace. Pokud
nejste správným adresátem, popÅ™ÃpadÄ› jste obdržel(a) tuto zprávu omylem,
informujte, prosÃm, obratem odesÃlatele a smažte tuto zprávu. Nedovolené
kopÃrovánà a pÅ™eposÃlánà této zprávy nenà dovoleno.
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese
E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
The fulcrum-xslt-team is pleased to announce the fulcrum-xslt-1.1.0.jar release! Fulcrum XSLT Service Changes in this version include: New features: o Added an additional transform() method which takes no XML input document. o Added a regression test which really does a XSL transformation. o Moved to M2 build Changes: o Synced with 2_3 branch (excluding the replacement of the cache Map() with a LRUMap()). Thanks to Thomas Vandahl for the patches. Issue: TRB-19. Thanks to Thomas Vandahl. Have fun! -fulcrum-xslt-team --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Hello! We had a problem with our screen classes. In some cases they weren't loaded. I noticed that the loading was screen-sensitive so that if I typed in the url www.mydomain.com/mypage.vm and the site had a screen class called MyPage.java, it was never executed. Is there any way around this? /Ludwig
Sheldon Ross wrote: > Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. Look into catalina.out if it exists. Sometimes the JVM just decides to die. BTW: Anyone having experience with JAI crashing/hanging the JVM? Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Another thought (a long shot) - if your tomcat service is running chrooted or in a more complicated linux/unix virtualization environment, running a script to stop a service on the host machine (i.e. outside one of the containers) can have unintended side-effects on instances of the same service running in the containers. Confused the heck out of me when it happened on my dev box. Jonathan Essex Consultant, Professional Services Misys Solutions for Banking 63 boulevard Hausmann 75008 Paris, France -----Original Message----- From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] Sent: 16 November 2009 19:55 To: user@turbine.apache.org Subject: RE: Weird Tomcat issue. Thanks for all the suggestions. I'll definitely be considering/investigating each one. This gives me some places to start, I'll report back when I get it sorted. Thanks Sheldon Ross > Date: Mon, 16 Nov 2009 12:29:58 -0600 > From: tonyo@prepare-enrich.com > To: user@turbine.apache.org > Subject: Re: Weird Tomcat issue. > > A few other things... > > Have you recently upgraded Java on the server, or been applying patches? > > > Sheldon Ross wrote: > > Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. > > > > The servers are secured on a Linux machine behind a firewall. > > > > The auth.logs show noone logging/sshing in when the shutdown occurs. > > > > I'm using an Apache front end and using modjk to connect to Tomcat. > > > > Like I said it's really weird. > > > > I've sort of remedied it by putting "ps -e | grep java || /etc/init.d/tomcat start" in crontab > > But as you can imagine that is far less than Ideal. > > > > > >> Date: Mon, 16 Nov 2009 11:27:07 -0600 > >> From: tonyo@prepare-enrich.com > >> To: user@turbine.apache.org > >> Subject: Re: Weird Tomcat issue. > >> > >> When you say "it" is shutting down, are you referring to tomcat, or to > >> Turbine. > >> > >> What version of Tomcat and Turbine? > >> > >> When this happens can you still directly reference "any" ports on the > >> tomcat server. (say port 80, etc) > >> > >> What environment are you running it on (Linux, Windows) > >> > >> Are you using the connector? > >> > >> Things don't typically just start happening without a reason... so is > >> access to this server controlled? Is it only you accessing it, your > >> team, etc? Can you pinpoint an approximate time that it started happening? > >> > >> > >> Sheldon Ross wrote: > >> > >>> I just recently started having this weird issue with Tomcat and Turbine. > >>> It appears like its just shutting down cleanly, only we are NOT shutting it down. > >>> > >>> It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. > >>> > >>> Any thoughts? > >>> > >>> Servlet log: > >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 > >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp ] - Stopping filters > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() > >>> > >>> Turbine log: > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService > >>> 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService > >>> 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService > >>> 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService > >>> 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! > >>> > >>> > >>> > >>> > >>> > >>> _________________________________________________________________ > >>> Hotmail: Trusted email with Microsoft's powerful SPAM protection. > >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ > >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > >> For additional commands, e-mail: user-help@turbine.apache.org > >> > >> > > > > _________________________________________________________________ > > Bing brings you maps, menus, and reviews organized in one place. > > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=T EXT_MFESRP_Local_MapsMenu_Resturants_1x1 > > > _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/ "Misys" is the trade name for Misys plc (registered in England and Wales). Registration Number: 01360027. Registered office: One Kingdom Street, London W2 6BL, United Kingdom. For a list of Misys group operating companies please go to http://www.misys.com/corp/About_Us/misys_operating_companies.html. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys plc. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Thanks for all the suggestions. I'll definitely be considering/investigating each one. This gives me some places to start, I'll report back when I get it sorted. Thanks Sheldon Ross > Date: Mon, 16 Nov 2009 12:29:58 -0600 > From: tonyo@prepare-enrich.com > To: user@turbine.apache.org > Subject: Re: Weird Tomcat issue. > > A few other things... > > Have you recently upgraded Java on the server, or been applying patches? > > > Sheldon Ross wrote: > > Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. > > > > The servers are secured on a Linux machine behind a firewall. > > > > The auth.logs show noone logging/sshing in when the shutdown occurs. > > > > I'm using an Apache front end and using modjk to connect to Tomcat. > > > > Like I said it's really weird. > > > > I've sort of remedied it by putting "ps -e | grep java || /etc/init.d/tomcat start" in crontab > > But as you can imagine that is far less than Ideal. > > > > > >> Date: Mon, 16 Nov 2009 11:27:07 -0600 > >> From: tonyo@prepare-enrich.com > >> To: user@turbine.apache.org > >> Subject: Re: Weird Tomcat issue. > >> > >> When you say "it" is shutting down, are you referring to tomcat, or to > >> Turbine. > >> > >> What version of Tomcat and Turbine? > >> > >> When this happens can you still directly reference "any" ports on the > >> tomcat server. (say port 80, etc) > >> > >> What environment are you running it on (Linux, Windows) > >> > >> Are you using the connector? > >> > >> Things don't typically just start happening without a reason... so is > >> access to this server controlled? Is it only you accessing it, your > >> team, etc? Can you pinpoint an approximate time that it started happening? > >> > >> > >> Sheldon Ross wrote: > >> > >>> I just recently started having this weird issue with Tomcat and Turbine. > >>> It appears like its just shutting down cleanly, only we are NOT shutting it down. > >>> > >>> It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. > >>> > >>> Any thoughts? > >>> > >>> Servlet log: > >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 > >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp] - Stopping filters > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping > >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete > >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() > >>> > >>> Turbine log: > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService > >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService > >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService > >>> 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService > >>> 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService > >>> 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService > >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService > >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService > >>> 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! > >>> > >>> > >>> > >>> > >>> > >>> _________________________________________________________________ > >>> Hotmail: Trusted email with Microsoft's powerful SPAM protection. > >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ > >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ > >>> > >>> > >>> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > >> For additional commands, e-mail: user-help@turbine.apache.org > >> > >> > > > > _________________________________________________________________ > > Bing brings you maps, menus, and reviews organized in one place. > > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 > > > _________________________________________________________________ Hotmail: Trusted email with powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141665/direct/01/
A few other things... Have you recently upgraded Java on the server, or been applying patches? Sheldon Ross wrote: > Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. > > The servers are secured on a Linux machine behind a firewall. > > The auth.logs show noone logging/sshing in when the shutdown occurs. > > I'm using an Apache front end and using modjk to connect to Tomcat. > > Like I said it's really weird. > > I've sort of remedied it by putting "ps -e | grep java || /etc/init.d/tomcat start" in crontab > But as you can imagine that is far less than Ideal. > > >> Date: Mon, 16 Nov 2009 11:27:07 -0600 >> From: tonyo@prepare-enrich.com >> To: user@turbine.apache.org >> Subject: Re: Weird Tomcat issue. >> >> When you say "it" is shutting down, are you referring to tomcat, or to >> Turbine. >> >> What version of Tomcat and Turbine? >> >> When this happens can you still directly reference "any" ports on the >> tomcat server. (say port 80, etc) >> >> What environment are you running it on (Linux, Windows) >> >> Are you using the connector? >> >> Things don't typically just start happening without a reason... so is >> access to this server controlled? Is it only you accessing it, your >> team, etc? Can you pinpoint an approximate time that it started happening? >> >> >> Sheldon Ross wrote: >> >>> I just recently started having this weird issue with Tomcat and Turbine. >>> It appears like its just shutting down cleanly, only we are NOT shutting it down. >>> >>> It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. >>> >>> Any thoughts? >>> >>> Servlet log: >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp] - Stopping filters >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() >>> >>> Turbine log: >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService >>> 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService >>> 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService >>> 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService >>> 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! >>> >>> >>> >>> >>> >>> _________________________________________________________________ >>> Hotmail: Trusted email with Microsoft's powerful SPAM protection. >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> >> > > _________________________________________________________________ > Bing brings you maps, menus, and reviews organized in one place. > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 >
What version of Tomcat? What version of the connector? Just a thought, but you might start by changing the passwords on the server, just in case you have an angry co-worker or two. Personally, I have run into bizarre issues similar to this but in my case I have been able to track it down to one of the following. (1) New enterprise firewall that would drop the modjk connections. (2) New version of apache that required a newer version of modjk, that in turn required new worker settings, that in turn required new tomcat server.xml settings. (3) Accidental deployment of multiple jar files containing references to the same classes. In my case accidentally backing them up into a directory under WEB-INF/lib (4) Modifying the logging settings of the server, and misconfiguring it. (5) Running Tomcat 6 with some of the more critical jars under WEB-INF/lib rather than /<tomcat root>/lib (6) NOT using the tomcat connection pool (this one caused very random issues with Tomcat 6) (I was using an older connection pool approach) (7) Exhausting memory on the server, or not configuring the tomcat java process with enough memory. (8) Running multiple conflicting instances of tomcat on the same server (port overlap, etc) (9) NIC card problems/dropped network connections (10) uploading files of enormous size and not configuring for it Do you have the option to run a test instance of Tomcat on another server? If nothing has changed on the server, then you might just be running into hardware problems. I had a mother board start to fail in one of our tomcat servers and it caused all kinds of unstable performance until we figured it out. Sheldon Ross wrote: > Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. > > The servers are secured on a Linux machine behind a firewall. > > The auth.logs show noone logging/sshing in when the shutdown occurs. > > I'm using an Apache front end and using modjk to connect to Tomcat. > > Like I said it's really weird. > > I've sort of remedied it by putting "ps -e | grep java || /etc/init.d/tomcat start" in crontab > But as you can imagine that is far less than Ideal. > > >> Date: Mon, 16 Nov 2009 11:27:07 -0600 >> From: tonyo@prepare-enrich.com >> To: user@turbine.apache.org >> Subject: Re: Weird Tomcat issue. >> >> When you say "it" is shutting down, are you referring to tomcat, or to >> Turbine. >> >> What version of Tomcat and Turbine? >> >> When this happens can you still directly reference "any" ports on the >> tomcat server. (say port 80, etc) >> >> What environment are you running it on (Linux, Windows) >> >> Are you using the connector? >> >> Things don't typically just start happening without a reason... so is >> access to this server controlled? Is it only you accessing it, your >> team, etc? Can you pinpoint an approximate time that it started happening? >> >> >> Sheldon Ross wrote: >> >>> I just recently started having this weird issue with Tomcat and Turbine. >>> It appears like its just shutting down cleanly, only we are NOT shutting it down. >>> >>> It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. >>> >>> Any thoughts? >>> >>> Servlet log: >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 >>> 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp] - Stopping filters >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping >>> 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete >>> 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() >>> >>> Turbine log: >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService >>> 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService >>> 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService >>> 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService >>> 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService >>> 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService >>> 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService >>> 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService >>> 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! >>> >>> >>> >>> >>> >>> _________________________________________________________________ >>> Hotmail: Trusted email with Microsoft's powerful SPAM protection. >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ >>> http://clk.atdmt.com/GBL/go/177141664/direct/01/ >>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> >> > > _________________________________________________________________ > Bing brings you maps, menus, and reviews organized in one place. > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 >
Tomcat is shutting down. There are no java processes on the server after this happens. The machine itself is still up and running fine. The servers are secured on a Linux machine behind a firewall. The auth.logs show noone logging/sshing in when the shutdown occurs. I'm using an Apache front end and using modjk to connect to Tomcat. Like I said it's really weird. I've sort of remedied it by putting "ps -e | grep java || /etc/init.d/tomcat start" in crontab But as you can imagine that is far less than Ideal. > Date: Mon, 16 Nov 2009 11:27:07 -0600 > From: tonyo@prepare-enrich.com > To: user@turbine.apache.org > Subject: Re: Weird Tomcat issue. > > When you say "it" is shutting down, are you referring to tomcat, or to > Turbine. > > What version of Tomcat and Turbine? > > When this happens can you still directly reference "any" ports on the > tomcat server. (say port 80, etc) > > What environment are you running it on (Linux, Windows) > > Are you using the connector? > > Things don't typically just start happening without a reason... so is > access to this server controlled? Is it only you accessing it, your > team, etc? Can you pinpoint an approximate time that it started happening? > > > Sheldon Ross wrote: > > I just recently started having this weird issue with Tomcat and Turbine. > > It appears like its just shutting down cleanly, only we are NOT shutting it down. > > > > It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. > > > > Any thoughts? > > > > Servlet log: > > 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 > > 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 > > 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp] - Stopping filters > > 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping > > 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions > > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser > > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions > > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions > > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete > > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() > > > > Turbine log: > > 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! > > 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService > > 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService > > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService > > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService > > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService > > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService > > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService > > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService > > 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService > > 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService > > 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService > > 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService > > 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService > > 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService > > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService > > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService > > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService > > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService > > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService > > 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! > > > > > > > > > > > > _________________________________________________________________ > > Hotmail: Trusted email with Microsoft's powerful SPAM protection. > > http://clk.atdmt.com/GBL/go/177141664/direct/01/ > > http://clk.atdmt.com/GBL/go/177141664/direct/01/ > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > _________________________________________________________________ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1
When you say "it" is shutting down, are you referring to tomcat, or to Turbine. What version of Tomcat and Turbine? When this happens can you still directly reference "any" ports on the tomcat server. (say port 80, etc) What environment are you running it on (Linux, Windows) Are you using the connector? Things don't typically just start happening without a reason... so is access to this server controlled? Is it only you accessing it, your team, etc? Can you pinpoint an approximate time that it started happening? Sheldon Ross wrote: > I just recently started having this weird issue with Tomcat and Turbine. > It appears like its just shutting down cleanly, only we are NOT shutting it down. > > It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. > > Any thoughts? > > Servlet log: > 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 > 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 > 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp] - Stopping filters > 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping > 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete > 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() > > Turbine log: > 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! > 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService > 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService > 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService > 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService > 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService > 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService > 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService > 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService > 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService > 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService > 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! > > > > > > _________________________________________________________________ > Hotmail: Trusted email with Microsoft's powerful SPAM protection. > http://clk.atdmt.com/GBL/go/177141664/direct/01/ > http://clk.atdmt.com/GBL/go/177141664/direct/01/ > > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
I just recently started having this weird issue with Tomcat and Turbine. It appears like its just shutting down cleanly, only we are NOT shutting it down. It's really weird. Everything seems to be running fine, there's no errors in the logs before this happens. It's like it's just randomly deciding to shutdown. Any thoughts? Servlet log: 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1258162412651 sessioncount 0 2009-11-13 18:33:32,651 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] DEBUG org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.core.ContainerBase.[Catalina].[afriezedev].[/simmapp] - Stopping filters 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Stopping 2009-11-13 18:33:54,494 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading persisted sessions 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Saving persisted sessions to SESSIONS.ser 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading 0 sessions 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Expiring 0 persisted sessions 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.catalina.session.ManagerBase - Unloading complete 2009-11-13 18:33:54,495 [Thread-32] DEBUG org.apache.jasper.servlet.JspServlet - JspServlet.destroy() Turbine log: 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down all services! 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: VelocityService 2009-11-13 18:33:55,532 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XSLTService 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: TemplateService 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PullService 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: CryptoService 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SecurityService 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UploadService 2009-11-13 18:33:55,535 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: UniqueIdService 2009-11-13 18:33:55,538 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: XmlRpcService 2009-11-13 18:33:55,545 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: GlobalCacheService 2009-11-13 18:33:55,549 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: MimeTypeService 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: LocalizationService 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AssemblerBrokerService 2009-11-13 18:33:55,552 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: ServletService 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: RunDataService 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: PoolService 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: FactoryService 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: AvalonComponentService 2009-11-13 18:33:55,555 [Thread-32] INFO org.apache.turbine.services.BaseServiceBroker - Shutting down service: SessionService 2009-11-13 18:33:55,852 [Thread-32] INFO org.apache.turbine.Turbine - Turbine: Done shutting down! _________________________________________________________________ Hotmail: Trusted email with Microsoft's powerful SPAM protection. http://clk.atdmt.com/GBL/go/177141664/direct/01/ http://clk.atdmt.com/GBL/go/177141664/direct/01/
Hi Jürgen! I have now configured a skeleton turbine project with torque for maven 2. If you still have some files for me I would appreciate them. Always good with input. /Ludwig -----Original Message----- From: Jürgen Hoffmann [mailto:hoffmann@apache.org] Sent: den 6 november 2009 10:37 To: Turbine Users List Subject: Re: What is the state of turbine? Hi Ludwig, glad to hear that. I will create an empty eclipse project file for you to use. Kind regards Juergen Hoffmann Am 06.11.2009 um 10:09 schrieb Ludwig Magnusson: > Jürgen, the hero of the day! > > Your mail touched the heart of my fellow developer and it now seems > as if we > are going to use turbine. > I would really appreciate the documents on how to use M2. > /Ludwig > > -----Original Message----- > From: Jürgen Hoffmann [mailto:hoffmann@apache.org] > Sent: den 5 november 2009 20:55 > To: Turbine Users List > Subject: Re: What is the state of turbine? > > Hi Ludwig, > > I did not say that there is nobody working on turbine. You just have > to understand that the turbine 2.3.3 release is pretty stable as it is > right now. It provides tools for everything you need in web > applications. Even JSON Integration. > > M.E.T.A. is some years old. It was developed by Henning Schmiedehausen > who is now the Velocity PMC Chair. Turbine has evolved many projects > like maven and torque themselves. That said, there has been a lot of > development inside of turbine over the past years. Even a little too > much. That said, the core developers are currently working on > straightening up TRUNK. > > fulcrum provides components which once coupled in turbine are now > decoupled of it. If you have ever tried to decouple something > yourself, you should agree, that this can be tedious work. Siegfried > and Thomas are doing a wonderful job on doing just that. They are > moving the build process over to a m2 build system as well. > > And to be honest, I asked the same question you asked a couple of > years ago http://markmail.org/thread/xaxk2fssigffu3ji As you can see > now is 2009 and you can still get support. > > Turbine 2.3.3 is well tested. There should be no problems inside the > framework when you use it. > > If you need m2, I can provide you with docs on how to set it up. Other > than that, I have been using turbine for years, and it has never let > me down, and there have not been things, i wasn't able to do with > turbine. > > Kind regards > > Juergen Hoffmann > > Am 05.11.2009 um 19:53 schrieb Ludwig Magnusson: > >> Let me reply to both Sheldon and Jürgen. >> The main concern of my team is that the project will close down. >> What will >> happened then? What if other frameworks develop interesting features >> and >> turbine stays behind? >> >> Jürgen: >> I defenetly respect that people has other priorities and I most >> certaly do >> not require anyone to put any time into this. But if the situation >> is as it >> is, then I wonder if a few people busy at work and engaged in other >> projects >> are enough to carry an open source framework like turbine. I really >> have no >> idea what it takes. >> >> Sheldon: >> I also believe that turbine is stalbe and robust if you have an >> application >> running it. But there is actually a lot of bugs connected to M.E.T.A >> and the >> setting up of a new project. >> Perhaps this is a thing that blocks new users? >> /Ludwig >> >> -----Original Message----- >> From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] >> Sent: den 5 november 2009 19:33 >> To: user@turbine.apache.org >> Subject: RE: What is the state of turbine? >> >> >> I have used both Struts and Turbine, but for the couple production >> sites we >> run I use Turbine. >> I've never really like the Bean/JSP approach Struts uses. Not a big >> fan of >> php either. >> Once you understand exactly how Turbine works, it's extremely easy >> to do >> whatever you want with it. >> >> Maybe its just me, but Turbine does everything I need and has for >> awhile. >> Maybe that contributes to why this list is quiet. >> >> Just my ancedotal 2 cents, >> >> Sheldon Ross >> >>> Subject: Re: What is the state of turbine? >>> From: hoffmann@apache.org >>> Date: Thu, 5 Nov 2009 17:17:25 +0100 >>> To: user@turbine.apache.org >>> >>> Hi Ludwig, >>> >>> we have setup turbine to be built by m2. Turbine is not dead. Only >>> the >>> people developing on it, are either busy at their work, or involved >>> into further uncouling of the core serivces inside the fulcrum >>> project >>> (Thomas Vandahl) >>> >>> If you need support getting your app running and other things like >>> build your app using m2, I can really help you. >>> >>> Although there are only few active developers, the few know turbine >>> to >>> its bones. So just ask >>> >>> Kind regards >>> >>> Juergen >>> >>> Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: >>> >>>> Hello! >>>> >>>> I am currently working in a big web application project with a few >>>> fellow >>>> developers. When we started out we were discussing a lot on which >>>> framework >>>> to use. I was familiar with turbine and I liked it very much. >>>> However the >>>> others were skeptical since there is very few persons involved in >>>> turbine at >>>> the moment. We decided to work with php and Zend and we have made a >>>> quite >>>> cool alpha version of out app. However, me and the other main >>>> developer >>>> (both computer engineers) have realized that the php community does >>>> not have >>>> very good understanding of concepts as best practices when it >>>> comes to >>>> object orienting, testing, database management and so on. >>>> Especially >>>> for >>>> complex applications. We are now considering switching framework >>>> and >>>> we are >>>> looking at java-based frameworks. (Because java rules) >>>> >>>> >>>> >>>> We have looked at other apache frameworks such as tapestry and >>>> struts (which >>>> are much more active). But to me it seems as if they do not address >>>> the >>>> things that I really like about turbine and that I feel are basic >>>> in >>>> the >>>> kind of application we are developing. For instance no other >>>> framework seems >>>> to have a user class (or interface) which I think is a basic >>>> feature >>>> since >>>> validations on the user are done on almost every page. Further on, >>>> if there >>>> is some kind of permission system, it is always role-based and not >>>> group-role-based which we need. >>>> >>>> >>>> >>>> So my question is.. Is turbine dying? Or is it already dead? And >>>> why? >>>> >>>> I am not _that_ experienced in developing complex web applications. >>>> Does >>>> turbine have some kind of major flaw that I don't see? >>>> >>>> >>>> >>>> What I like and what I am looking for is this: >>>> >>>> - The security system - group-role-based >>>> >>>> - Tight integration with velocity (which of course can be >>>> accomplished in other frameworks as struts). And what I like with >>>> velocity >>>> is that the templates looks very much like static html, i.e. they >>>> are very >>>> readable. I don't like jsp. >>>> >>>> - The torque object model that is generated >>>> >>>> - A clear file structure for the environment. (What I >>>> like in >>>> turbine is that I can create a folder for x number of pages and >>>> then >>>> create >>>> a default.java class in the corresponding package and have the same >>>> permission check for all those pages) >>>> >>>> >>>> >>>> The biggest flaw I think turbine has is that it isn't really >>>> maven 2 >>>> compatible. I really like working with maven, but I prefer not to >>>> use >>>> version 1. >>>> >>>> >>>> >>>> I'm just sending this since I think it's sad that it is not used >>>> anymore and >>>> I wonder why. >>>> >>>> Any reply/discussion would be appreciated. >>>> >>>> /Ludwig >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >>> For additional commands, e-mail: user-help@turbine.apache.org >>> >> >> _________________________________________________________________ >> Bing brings you maps, menus, and reviews organized in one place. >> > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_ >> MFESRP_Local_MapsMenu_Resturants_1x1 >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Great! Do you mean a project that contains a pom-file and properties files for turbine, velocity and torque? Or did I misunderstand? /Ludwig -----Original Message----- From: Jürgen Hoffmann [mailto:hoffmann@apache.org] Sent: den 6 november 2009 10:37 To: Turbine Users List Subject: Re: What is the state of turbine? Hi Ludwig, glad to hear that. I will create an empty eclipse project file for you to use. Kind regards Juergen Hoffmann Am 06.11.2009 um 10:09 schrieb Ludwig Magnusson: > Jürgen, the hero of the day! > > Your mail touched the heart of my fellow developer and it now seems > as if we > are going to use turbine. > I would really appreciate the documents on how to use M2. > /Ludwig > > -----Original Message----- > From: Jürgen Hoffmann [mailto:hoffmann@apache.org] > Sent: den 5 november 2009 20:55 > To: Turbine Users List > Subject: Re: What is the state of turbine? > > Hi Ludwig, > > I did not say that there is nobody working on turbine. You just have > to understand that the turbine 2.3.3 release is pretty stable as it is > right now. It provides tools for everything you need in web > applications. Even JSON Integration. > > M.E.T.A. is some years old. It was developed by Henning Schmiedehausen > who is now the Velocity PMC Chair. Turbine has evolved many projects > like maven and torque themselves. That said, there has been a lot of > development inside of turbine over the past years. Even a little too > much. That said, the core developers are currently working on > straightening up TRUNK. > > fulcrum provides components which once coupled in turbine are now > decoupled of it. If you have ever tried to decouple something > yourself, you should agree, that this can be tedious work. Siegfried > and Thomas are doing a wonderful job on doing just that. They are > moving the build process over to a m2 build system as well. > > And to be honest, I asked the same question you asked a couple of > years ago http://markmail.org/thread/xaxk2fssigffu3ji As you can see > now is 2009 and you can still get support. > > Turbine 2.3.3 is well tested. There should be no problems inside the > framework when you use it. > > If you need m2, I can provide you with docs on how to set it up. Other > than that, I have been using turbine for years, and it has never let > me down, and there have not been things, i wasn't able to do with > turbine. > > Kind regards > > Juergen Hoffmann > > Am 05.11.2009 um 19:53 schrieb Ludwig Magnusson: > >> Let me reply to both Sheldon and Jürgen. >> The main concern of my team is that the project will close down. >> What will >> happened then? What if other frameworks develop interesting features >> and >> turbine stays behind? >> >> Jürgen: >> I defenetly respect that people has other priorities and I most >> certaly do >> not require anyone to put any time into this. But if the situation >> is as it >> is, then I wonder if a few people busy at work and engaged in other >> projects >> are enough to carry an open source framework like turbine. I really >> have no >> idea what it takes. >> >> Sheldon: >> I also believe that turbine is stalbe and robust if you have an >> application >> running it. But there is actually a lot of bugs connected to M.E.T.A >> and the >> setting up of a new project. >> Perhaps this is a thing that blocks new users? >> /Ludwig >> >> -----Original Message----- >> From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] >> Sent: den 5 november 2009 19:33 >> To: user@turbine.apache.org >> Subject: RE: What is the state of turbine? >> >> >> I have used both Struts and Turbine, but for the couple production >> sites we >> run I use Turbine. >> I've never really like the Bean/JSP approach Struts uses. Not a big >> fan of >> php either. >> Once you understand exactly how Turbine works, it's extremely easy >> to do >> whatever you want with it. >> >> Maybe its just me, but Turbine does everything I need and has for >> awhile. >> Maybe that contributes to why this list is quiet. >> >> Just my ancedotal 2 cents, >> >> Sheldon Ross >> >>> Subject: Re: What is the state of turbine? >>> From: hoffmann@apache.org >>> Date: Thu, 5 Nov 2009 17:17:25 +0100 >>> To: user@turbine.apache.org >>> >>> Hi Ludwig, >>> >>> we have setup turbine to be built by m2. Turbine is not dead. Only >>> the >>> people developing on it, are either busy at their work, or involved >>> into further uncouling of the core serivces inside the fulcrum >>> project >>> (Thomas Vandahl) >>> >>> If you need support getting your app running and other things like >>> build your app using m2, I can really help you. >>> >>> Although there are only few active developers, the few know turbine >>> to >>> its bones. So just ask >>> >>> Kind regards >>> >>> Juergen >>> >>> Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: >>> >>>> Hello! >>>> >>>> I am currently working in a big web application project with a few >>>> fellow >>>> developers. When we started out we were discussing a lot on which >>>> framework >>>> to use. I was familiar with turbine and I liked it very much. >>>> However the >>>> others were skeptical since there is very few persons involved in >>>> turbine at >>>> the moment. We decided to work with php and Zend and we have made a >>>> quite >>>> cool alpha version of out app. However, me and the other main >>>> developer >>>> (both computer engineers) have realized that the php community does >>>> not have >>>> very good understanding of concepts as best practices when it >>>> comes to >>>> object orienting, testing, database management and so on. >>>> Especially >>>> for >>>> complex applications. We are now considering switching framework >>>> and >>>> we are >>>> looking at java-based frameworks. (Because java rules) >>>> >>>> >>>> >>>> We have looked at other apache frameworks such as tapestry and >>>> struts (which >>>> are much more active). But to me it seems as if they do not address >>>> the >>>> things that I really like about turbine and that I feel are basic >>>> in >>>> the >>>> kind of application we are developing. For instance no other >>>> framework seems >>>> to have a user class (or interface) which I think is a basic >>>> feature >>>> since >>>> validations on the user are done on almost every page. Further on, >>>> if there >>>> is some kind of permission system, it is always role-based and not >>>> group-role-based which we need. >>>> >>>> >>>> >>>> So my question is.. Is turbine dying? Or is it already dead? And >>>> why? >>>> >>>> I am not _that_ experienced in developing complex web applications. >>>> Does >>>> turbine have some kind of major flaw that I don't see? >>>> >>>> >>>> >>>> What I like and what I am looking for is this: >>>> >>>> - The security system - group-role-based >>>> >>>> - Tight integration with velocity (which of course can be >>>> accomplished in other frameworks as struts). And what I like with >>>> velocity >>>> is that the templates looks very much like static html, i.e. they >>>> are very >>>> readable. I don't like jsp. >>>> >>>> - The torque object model that is generated >>>> >>>> - A clear file structure for the environment. (What I >>>> like in >>>> turbine is that I can create a folder for x number of pages and >>>> then >>>> create >>>> a default.java class in the corresponding package and have the same >>>> permission check for all those pages) >>>> >>>> >>>> >>>> The biggest flaw I think turbine has is that it isn't really >>>> maven 2 >>>> compatible. I really like working with maven, but I prefer not to >>>> use >>>> version 1. >>>> >>>> >>>> >>>> I'm just sending this since I think it's sad that it is not used >>>> anymore and >>>> I wonder why. >>>> >>>> Any reply/discussion would be appreciated. >>>> >>>> /Ludwig >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >>> For additional commands, e-mail: user-help@turbine.apache.org >>> >> >> _________________________________________________________________ >> Bing brings you maps, menus, and reviews organized in one place. >> > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_ >> MFESRP_Local_MapsMenu_Resturants_1x1 >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Hi Ludwig, glad to hear that. I will create an empty eclipse project file for you to use. Kind regards Juergen Hoffmann Am 06.11.2009 um 10:09 schrieb Ludwig Magnusson: > Jürgen, the hero of the day! > > Your mail touched the heart of my fellow developer and it now seems > as if we > are going to use turbine. > I would really appreciate the documents on how to use M2. > /Ludwig > > -----Original Message----- > From: Jürgen Hoffmann [mailto:hoffmann@apache.org] > Sent: den 5 november 2009 20:55 > To: Turbine Users List > Subject: Re: What is the state of turbine? > > Hi Ludwig, > > I did not say that there is nobody working on turbine. You just have > to understand that the turbine 2.3.3 release is pretty stable as it is > right now. It provides tools for everything you need in web > applications. Even JSON Integration. > > M.E.T.A. is some years old. It was developed by Henning Schmiedehausen > who is now the Velocity PMC Chair. Turbine has evolved many projects > like maven and torque themselves. That said, there has been a lot of > development inside of turbine over the past years. Even a little too > much. That said, the core developers are currently working on > straightening up TRUNK. > > fulcrum provides components which once coupled in turbine are now > decoupled of it. If you have ever tried to decouple something > yourself, you should agree, that this can be tedious work. Siegfried > and Thomas are doing a wonderful job on doing just that. They are > moving the build process over to a m2 build system as well. > > And to be honest, I asked the same question you asked a couple of > years ago http://markmail.org/thread/xaxk2fssigffu3ji As you can see > now is 2009 and you can still get support. > > Turbine 2.3.3 is well tested. There should be no problems inside the > framework when you use it. > > If you need m2, I can provide you with docs on how to set it up. Other > than that, I have been using turbine for years, and it has never let > me down, and there have not been things, i wasn't able to do with > turbine. > > Kind regards > > Juergen Hoffmann > > Am 05.11.2009 um 19:53 schrieb Ludwig Magnusson: > >> Let me reply to both Sheldon and Jürgen. >> The main concern of my team is that the project will close down. >> What will >> happened then? What if other frameworks develop interesting features >> and >> turbine stays behind? >> >> Jürgen: >> I defenetly respect that people has other priorities and I most >> certaly do >> not require anyone to put any time into this. But if the situation >> is as it >> is, then I wonder if a few people busy at work and engaged in other >> projects >> are enough to carry an open source framework like turbine. I really >> have no >> idea what it takes. >> >> Sheldon: >> I also believe that turbine is stalbe and robust if you have an >> application >> running it. But there is actually a lot of bugs connected to M.E.T.A >> and the >> setting up of a new project. >> Perhaps this is a thing that blocks new users? >> /Ludwig >> >> -----Original Message----- >> From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] >> Sent: den 5 november 2009 19:33 >> To: user@turbine.apache.org >> Subject: RE: What is the state of turbine? >> >> >> I have used both Struts and Turbine, but for the couple production >> sites we >> run I use Turbine. >> I've never really like the Bean/JSP approach Struts uses. Not a big >> fan of >> php either. >> Once you understand exactly how Turbine works, it's extremely easy >> to do >> whatever you want with it. >> >> Maybe its just me, but Turbine does everything I need and has for >> awhile. >> Maybe that contributes to why this list is quiet. >> >> Just my ancedotal 2 cents, >> >> Sheldon Ross >> >>> Subject: Re: What is the state of turbine? >>> From: hoffmann@apache.org >>> Date: Thu, 5 Nov 2009 17:17:25 +0100 >>> To: user@turbine.apache.org >>> >>> Hi Ludwig, >>> >>> we have setup turbine to be built by m2. Turbine is not dead. Only >>> the >>> people developing on it, are either busy at their work, or involved >>> into further uncouling of the core serivces inside the fulcrum >>> project >>> (Thomas Vandahl) >>> >>> If you need support getting your app running and other things like >>> build your app using m2, I can really help you. >>> >>> Although there are only few active developers, the few know turbine >>> to >>> its bones. So just ask >>> >>> Kind regards >>> >>> Juergen >>> >>> Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: >>> >>>> Hello! >>>> >>>> I am currently working in a big web application project with a few >>>> fellow >>>> developers. When we started out we were discussing a lot on which >>>> framework >>>> to use. I was familiar with turbine and I liked it very much. >>>> However the >>>> others were skeptical since there is very few persons involved in >>>> turbine at >>>> the moment. We decided to work with php and Zend and we have made a >>>> quite >>>> cool alpha version of out app. However, me and the other main >>>> developer >>>> (both computer engineers) have realized that the php community does >>>> not have >>>> very good understanding of concepts as best practices when it >>>> comes to >>>> object orienting, testing, database management and so on. >>>> Especially >>>> for >>>> complex applications. We are now considering switching framework >>>> and >>>> we are >>>> looking at java-based frameworks. (Because java rules) >>>> >>>> >>>> >>>> We have looked at other apache frameworks such as tapestry and >>>> struts (which >>>> are much more active). But to me it seems as if they do not address >>>> the >>>> things that I really like about turbine and that I feel are basic >>>> in >>>> the >>>> kind of application we are developing. For instance no other >>>> framework seems >>>> to have a user class (or interface) which I think is a basic >>>> feature >>>> since >>>> validations on the user are done on almost every page. Further on, >>>> if there >>>> is some kind of permission system, it is always role-based and not >>>> group-role-based which we need. >>>> >>>> >>>> >>>> So my question is.. Is turbine dying? Or is it already dead? And >>>> why? >>>> >>>> I am not _that_ experienced in developing complex web applications. >>>> Does >>>> turbine have some kind of major flaw that I don't see? >>>> >>>> >>>> >>>> What I like and what I am looking for is this: >>>> >>>> - The security system - group-role-based >>>> >>>> - Tight integration with velocity (which of course can be >>>> accomplished in other frameworks as struts). And what I like with >>>> velocity >>>> is that the templates looks very much like static html, i.e. they >>>> are very >>>> readable. I don't like jsp. >>>> >>>> - The torque object model that is generated >>>> >>>> - A clear file structure for the environment. (What I >>>> like in >>>> turbine is that I can create a folder for x number of pages and >>>> then >>>> create >>>> a default.java class in the corresponding package and have the same >>>> permission check for all those pages) >>>> >>>> >>>> >>>> The biggest flaw I think turbine has is that it isn't really >>>> maven 2 >>>> compatible. I really like working with maven, but I prefer not to >>>> use >>>> version 1. >>>> >>>> >>>> >>>> I'm just sending this since I think it's sad that it is not used >>>> anymore and >>>> I wonder why. >>>> >>>> Any reply/discussion would be appreciated. >>>> >>>> /Ludwig >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >>> For additional commands, e-mail: user-help@turbine.apache.org >>> >> >> _________________________________________________________________ >> Bing brings you maps, menus, and reviews organized in one place. >> > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_ >> MFESRP_Local_MapsMenu_Resturants_1x1 >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Jürgen, the hero of the day! Your mail touched the heart of my fellow developer and it now seems as if we are going to use turbine. I would really appreciate the documents on how to use M2. /Ludwig -----Original Message----- From: Jürgen Hoffmann [mailto:hoffmann@apache.org] Sent: den 5 november 2009 20:55 To: Turbine Users List Subject: Re: What is the state of turbine? Hi Ludwig, I did not say that there is nobody working on turbine. You just have to understand that the turbine 2.3.3 release is pretty stable as it is right now. It provides tools for everything you need in web applications. Even JSON Integration. M.E.T.A. is some years old. It was developed by Henning Schmiedehausen who is now the Velocity PMC Chair. Turbine has evolved many projects like maven and torque themselves. That said, there has been a lot of development inside of turbine over the past years. Even a little too much. That said, the core developers are currently working on straightening up TRUNK. fulcrum provides components which once coupled in turbine are now decoupled of it. If you have ever tried to decouple something yourself, you should agree, that this can be tedious work. Siegfried and Thomas are doing a wonderful job on doing just that. They are moving the build process over to a m2 build system as well. And to be honest, I asked the same question you asked a couple of years ago http://markmail.org/thread/xaxk2fssigffu3ji As you can see now is 2009 and you can still get support. Turbine 2.3.3 is well tested. There should be no problems inside the framework when you use it. If you need m2, I can provide you with docs on how to set it up. Other than that, I have been using turbine for years, and it has never let me down, and there have not been things, i wasn't able to do with turbine. Kind regards Juergen Hoffmann Am 05.11.2009 um 19:53 schrieb Ludwig Magnusson: > Let me reply to both Sheldon and Jürgen. > The main concern of my team is that the project will close down. > What will > happened then? What if other frameworks develop interesting features > and > turbine stays behind? > > Jürgen: > I defenetly respect that people has other priorities and I most > certaly do > not require anyone to put any time into this. But if the situation > is as it > is, then I wonder if a few people busy at work and engaged in other > projects > are enough to carry an open source framework like turbine. I really > have no > idea what it takes. > > Sheldon: > I also believe that turbine is stalbe and robust if you have an > application > running it. But there is actually a lot of bugs connected to M.E.T.A > and the > setting up of a new project. > Perhaps this is a thing that blocks new users? > /Ludwig > > -----Original Message----- > From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] > Sent: den 5 november 2009 19:33 > To: user@turbine.apache.org > Subject: RE: What is the state of turbine? > > > I have used both Struts and Turbine, but for the couple production > sites we > run I use Turbine. > I've never really like the Bean/JSP approach Struts uses. Not a big > fan of > php either. > Once you understand exactly how Turbine works, it's extremely easy > to do > whatever you want with it. > > Maybe its just me, but Turbine does everything I need and has for > awhile. > Maybe that contributes to why this list is quiet. > > Just my ancedotal 2 cents, > > Sheldon Ross > >> Subject: Re: What is the state of turbine? >> From: hoffmann@apache.org >> Date: Thu, 5 Nov 2009 17:17:25 +0100 >> To: user@turbine.apache.org >> >> Hi Ludwig, >> >> we have setup turbine to be built by m2. Turbine is not dead. Only >> the >> people developing on it, are either busy at their work, or involved >> into further uncouling of the core serivces inside the fulcrum >> project >> (Thomas Vandahl) >> >> If you need support getting your app running and other things like >> build your app using m2, I can really help you. >> >> Although there are only few active developers, the few know turbine >> to >> its bones. So just ask >> >> Kind regards >> >> Juergen >> >> Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: >> >>> Hello! >>> >>> I am currently working in a big web application project with a few >>> fellow >>> developers. When we started out we were discussing a lot on which >>> framework >>> to use. I was familiar with turbine and I liked it very much. >>> However the >>> others were skeptical since there is very few persons involved in >>> turbine at >>> the moment. We decided to work with php and Zend and we have made a >>> quite >>> cool alpha version of out app. However, me and the other main >>> developer >>> (both computer engineers) have realized that the php community does >>> not have >>> very good understanding of concepts as best practices when it >>> comes to >>> object orienting, testing, database management and so on. Especially >>> for >>> complex applications. We are now considering switching framework and >>> we are >>> looking at java-based frameworks. (Because java rules) >>> >>> >>> >>> We have looked at other apache frameworks such as tapestry and >>> struts (which >>> are much more active). But to me it seems as if they do not address >>> the >>> things that I really like about turbine and that I feel are basic in >>> the >>> kind of application we are developing. For instance no other >>> framework seems >>> to have a user class (or interface) which I think is a basic feature >>> since >>> validations on the user are done on almost every page. Further on, >>> if there >>> is some kind of permission system, it is always role-based and not >>> group-role-based which we need. >>> >>> >>> >>> So my question is.. Is turbine dying? Or is it already dead? And >>> why? >>> >>> I am not _that_ experienced in developing complex web applications. >>> Does >>> turbine have some kind of major flaw that I don't see? >>> >>> >>> >>> What I like and what I am looking for is this: >>> >>> - The security system - group-role-based >>> >>> - Tight integration with velocity (which of course can be >>> accomplished in other frameworks as struts). And what I like with >>> velocity >>> is that the templates looks very much like static html, i.e. they >>> are very >>> readable. I don't like jsp. >>> >>> - The torque object model that is generated >>> >>> - A clear file structure for the environment. (What I >>> like in >>> turbine is that I can create a folder for x number of pages and then >>> create >>> a default.java class in the corresponding package and have the same >>> permission check for all those pages) >>> >>> >>> >>> The biggest flaw I think turbine has is that it isn't really maven 2 >>> compatible. I really like working with maven, but I prefer not to >>> use >>> version 1. >>> >>> >>> >>> I'm just sending this since I think it's sad that it is not used >>> anymore and >>> I wonder why. >>> >>> Any reply/discussion would be appreciated. >>> >>> /Ludwig >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> > > _________________________________________________________________ > Bing brings you maps, menus, and reviews organized in one place. > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_ > MFESRP_Local_MapsMenu_Resturants_1x1 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
On 05.11.09 19:53, Ludwig Magnusson wrote: > Let me reply to both Sheldon and Jürgen. > The main concern of my team is that the project will close down. What will > happened then? What if other frameworks develop interesting features and > turbine stays behind? Well, this one is easy. If you see a feature missing, come on and contribute. There is a proposal for OSGi integration, the new architecture allows for easier extension etc etc. We will be happy to integrate whatever seems to fit. As you can see, we released more than a fistful of components to be integrated in Turbine 4.0 alone this year. Dead projects look different. > I also believe that turbine is stalbe and robust if you have an application > running it. But there is actually a lot of bugs connected to M.E.T.A and the > setting up of a new project. > Perhaps this is a thing that blocks new users? Difficult question. I never used META myself. In any case, feel free to address whatever you feel needs to be changed. This is an open source project after all. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Hi Ludwig, I did not say that there is nobody working on turbine. You just have to understand that the turbine 2.3.3 release is pretty stable as it is right now. It provides tools for everything you need in web applications. Even JSON Integration. M.E.T.A. is some years old. It was developed by Henning Schmiedehausen who is now the Velocity PMC Chair. Turbine has evolved many projects like maven and torque themselves. That said, there has been a lot of development inside of turbine over the past years. Even a little too much. That said, the core developers are currently working on straightening up TRUNK. fulcrum provides components which once coupled in turbine are now decoupled of it. If you have ever tried to decouple something yourself, you should agree, that this can be tedious work. Siegfried and Thomas are doing a wonderful job on doing just that. They are moving the build process over to a m2 build system as well. And to be honest, I asked the same question you asked a couple of years ago http://markmail.org/thread/xaxk2fssigffu3ji As you can see now is 2009 and you can still get support. Turbine 2.3.3 is well tested. There should be no problems inside the framework when you use it. If you need m2, I can provide you with docs on how to set it up. Other than that, I have been using turbine for years, and it has never let me down, and there have not been things, i wasn't able to do with turbine. Kind regards Juergen Hoffmann Am 05.11.2009 um 19:53 schrieb Ludwig Magnusson: > Let me reply to both Sheldon and Jürgen. > The main concern of my team is that the project will close down. > What will > happened then? What if other frameworks develop interesting features > and > turbine stays behind? > > Jürgen: > I defenetly respect that people has other priorities and I most > certaly do > not require anyone to put any time into this. But if the situation > is as it > is, then I wonder if a few people busy at work and engaged in other > projects > are enough to carry an open source framework like turbine. I really > have no > idea what it takes. > > Sheldon: > I also believe that turbine is stalbe and robust if you have an > application > running it. But there is actually a lot of bugs connected to M.E.T.A > and the > setting up of a new project. > Perhaps this is a thing that blocks new users? > /Ludwig > > -----Original Message----- > From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] > Sent: den 5 november 2009 19:33 > To: user@turbine.apache.org > Subject: RE: What is the state of turbine? > > > I have used both Struts and Turbine, but for the couple production > sites we > run I use Turbine. > I've never really like the Bean/JSP approach Struts uses. Not a big > fan of > php either. > Once you understand exactly how Turbine works, it's extremely easy > to do > whatever you want with it. > > Maybe its just me, but Turbine does everything I need and has for > awhile. > Maybe that contributes to why this list is quiet. > > Just my ancedotal 2 cents, > > Sheldon Ross > >> Subject: Re: What is the state of turbine? >> From: hoffmann@apache.org >> Date: Thu, 5 Nov 2009 17:17:25 +0100 >> To: user@turbine.apache.org >> >> Hi Ludwig, >> >> we have setup turbine to be built by m2. Turbine is not dead. Only >> the >> people developing on it, are either busy at their work, or involved >> into further uncouling of the core serivces inside the fulcrum >> project >> (Thomas Vandahl) >> >> If you need support getting your app running and other things like >> build your app using m2, I can really help you. >> >> Although there are only few active developers, the few know turbine >> to >> its bones. So just ask >> >> Kind regards >> >> Juergen >> >> Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: >> >>> Hello! >>> >>> I am currently working in a big web application project with a few >>> fellow >>> developers. When we started out we were discussing a lot on which >>> framework >>> to use. I was familiar with turbine and I liked it very much. >>> However the >>> others were skeptical since there is very few persons involved in >>> turbine at >>> the moment. We decided to work with php and Zend and we have made a >>> quite >>> cool alpha version of out app. However, me and the other main >>> developer >>> (both computer engineers) have realized that the php community does >>> not have >>> very good understanding of concepts as best practices when it >>> comes to >>> object orienting, testing, database management and so on. Especially >>> for >>> complex applications. We are now considering switching framework and >>> we are >>> looking at java-based frameworks. (Because java rules) >>> >>> >>> >>> We have looked at other apache frameworks such as tapestry and >>> struts (which >>> are much more active). But to me it seems as if they do not address >>> the >>> things that I really like about turbine and that I feel are basic in >>> the >>> kind of application we are developing. For instance no other >>> framework seems >>> to have a user class (or interface) which I think is a basic feature >>> since >>> validations on the user are done on almost every page. Further on, >>> if there >>> is some kind of permission system, it is always role-based and not >>> group-role-based which we need. >>> >>> >>> >>> So my question is.. Is turbine dying? Or is it already dead? And >>> why? >>> >>> I am not _that_ experienced in developing complex web applications. >>> Does >>> turbine have some kind of major flaw that I don't see? >>> >>> >>> >>> What I like and what I am looking for is this: >>> >>> - The security system - group-role-based >>> >>> - Tight integration with velocity (which of course can be >>> accomplished in other frameworks as struts). And what I like with >>> velocity >>> is that the templates looks very much like static html, i.e. they >>> are very >>> readable. I don't like jsp. >>> >>> - The torque object model that is generated >>> >>> - A clear file structure for the environment. (What I >>> like in >>> turbine is that I can create a folder for x number of pages and then >>> create >>> a default.java class in the corresponding package and have the same >>> permission check for all those pages) >>> >>> >>> >>> The biggest flaw I think turbine has is that it isn't really maven 2 >>> compatible. I really like working with maven, but I prefer not to >>> use >>> version 1. >>> >>> >>> >>> I'm just sending this since I think it's sad that it is not used >>> anymore and >>> I wonder why. >>> >>> Any reply/discussion would be appreciated. >>> >>> /Ludwig >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> > > _________________________________________________________________ > Bing brings you maps, menus, and reviews organized in one place. > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_ > MFESRP_Local_MapsMenu_Resturants_1x1 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org >
Let me reply to both Sheldon and Jürgen. The main concern of my team is that the project will close down. What will happened then? What if other frameworks develop interesting features and turbine stays behind? Jürgen: I defenetly respect that people has other priorities and I most certaly do not require anyone to put any time into this. But if the situation is as it is, then I wonder if a few people busy at work and engaged in other projects are enough to carry an open source framework like turbine. I really have no idea what it takes. Sheldon: I also believe that turbine is stalbe and robust if you have an application running it. But there is actually a lot of bugs connected to M.E.T.A and the setting up of a new project. Perhaps this is a thing that blocks new users? /Ludwig -----Original Message----- From: Sheldon Ross [mailto:ross_sheldon@hotmail.com] Sent: den 5 november 2009 19:33 To: user@turbine.apache.org Subject: RE: What is the state of turbine? I have used both Struts and Turbine, but for the couple production sites we run I use Turbine. I've never really like the Bean/JSP approach Struts uses. Not a big fan of php either. Once you understand exactly how Turbine works, it's extremely easy to do whatever you want with it. Maybe its just me, but Turbine does everything I need and has for awhile. Maybe that contributes to why this list is quiet. Just my ancedotal 2 cents, Sheldon Ross > Subject: Re: What is the state of turbine? > From: hoffmann@apache.org > Date: Thu, 5 Nov 2009 17:17:25 +0100 > To: user@turbine.apache.org > > Hi Ludwig, > > we have setup turbine to be built by m2. Turbine is not dead. Only the > people developing on it, are either busy at their work, or involved > into further uncouling of the core serivces inside the fulcrum project > (Thomas Vandahl) > > If you need support getting your app running and other things like > build your app using m2, I can really help you. > > Although there are only few active developers, the few know turbine to > its bones. So just ask > > Kind regards > > Juergen > > Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: > > > Hello! > > > > I am currently working in a big web application project with a few > > fellow > > developers. When we started out we were discussing a lot on which > > framework > > to use. I was familiar with turbine and I liked it very much. > > However the > > others were skeptical since there is very few persons involved in > > turbine at > > the moment. We decided to work with php and Zend and we have made a > > quite > > cool alpha version of out app. However, me and the other main > > developer > > (both computer engineers) have realized that the php community does > > not have > > very good understanding of concepts as best practices when it comes to > > object orienting, testing, database management and so on. Especially > > for > > complex applications. We are now considering switching framework and > > we are > > looking at java-based frameworks. (Because java rules) > > > > > > > > We have looked at other apache frameworks such as tapestry and > > struts (which > > are much more active). But to me it seems as if they do not address > > the > > things that I really like about turbine and that I feel are basic in > > the > > kind of application we are developing. For instance no other > > framework seems > > to have a user class (or interface) which I think is a basic feature > > since > > validations on the user are done on almost every page. Further on, > > if there > > is some kind of permission system, it is always role-based and not > > group-role-based which we need. > > > > > > > > So my question is.. Is turbine dying? Or is it already dead? And why? > > > > I am not _that_ experienced in developing complex web applications. > > Does > > turbine have some kind of major flaw that I don't see? > > > > > > > > What I like and what I am looking for is this: > > > > - The security system - group-role-based > > > > - Tight integration with velocity (which of course can be > > accomplished in other frameworks as struts). And what I like with > > velocity > > is that the templates looks very much like static html, i.e. they > > are very > > readable. I don't like jsp. > > > > - The torque object model that is generated > > > > - A clear file structure for the environment. (What I like in > > turbine is that I can create a folder for x number of pages and then > > create > > a default.java class in the corresponding package and have the same > > permission check for all those pages) > > > > > > > > The biggest flaw I think turbine has is that it isn't really maven 2 > > compatible. I really like working with maven, but I prefer not to use > > version 1. > > > > > > > > I'm just sending this since I think it's sad that it is not used > > anymore and > > I wonder why. > > > > Any reply/discussion would be appreciated. > > > > /Ludwig > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > _________________________________________________________________ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_ MFESRP_Local_MapsMenu_Resturants_1x1 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
Definitely my preferred tool of choice. Tony Oslund On Nov 5, 2009, at 12:34 PM, "Sheldon Ross" <ross_sheldon@hotmail.com> wrote: > > I have used both Struts and Turbine, but for the couple production > sites we run I use Turbine. > I've never really like the Bean/JSP approach Struts uses. Not a big > fan of php either. > Once you understand exactly how Turbine works, it's extremely easy > to do whatever you want with it. > > Maybe its just me, but Turbine does everything I need and has for > awhile. Maybe that contributes to why this list is quiet. > > Just my ancedotal 2 cents, > > Sheldon Ross > >> Subject: Re: What is the state of turbine? >> From: hoffmann@apache.org >> Date: Thu, 5 Nov 2009 17:17:25 +0100 >> To: user@turbine.apache.org >> >> Hi Ludwig, >> >> we have setup turbine to be built by m2. Turbine is not dead. Only >> the >> people developing on it, are either busy at their work, or involved >> into further uncouling of the core serivces inside the fulcrum >> project >> (Thomas Vandahl) >> >> If you need support getting your app running and other things like >> build your app using m2, I can really help you. >> >> Although there are only few active developers, the few know turbine >> to >> its bones. So just ask >> >> Kind regards >> >> Juergen >> >> Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: >> >>> Hello! >>> >>> I am currently working in a big web application project with a few >>> fellow >>> developers. When we started out we were discussing a lot on which >>> framework >>> to use. I was familiar with turbine and I liked it very much. >>> However the >>> others were skeptical since there is very few persons involved in >>> turbine at >>> the moment. We decided to work with php and Zend and we have made a >>> quite >>> cool alpha version of out app. However, me and the other main >>> developer >>> (both computer engineers) have realized that the php community does >>> not have >>> very good understanding of concepts as best practices when it >>> comes to >>> object orienting, testing, database management and so on. Especially >>> for >>> complex applications. We are now considering switching framework and >>> we are >>> looking at java-based frameworks. (Because java rules) >>> >>> >>> >>> We have looked at other apache frameworks such as tapestry and >>> struts (which >>> are much more active). But to me it seems as if they do not address >>> the >>> things that I really like about turbine and that I feel are basic in >>> the >>> kind of application we are developing. For instance no other >>> framework seems >>> to have a user class (or interface) which I think is a basic feature >>> since >>> validations on the user are done on almost every page. Further on, >>> if there >>> is some kind of permission system, it is always role-based and not >>> group-role-based which we need. >>> >>> >>> >>> So my question is.. Is turbine dying? Or is it already dead? And >>> why? >>> >>> I am not _that_ experienced in developing complex web applications. >>> Does >>> turbine have some kind of major flaw that I don't see? >>> >>> >>> >>> What I like and what I am looking for is this: >>> >>> - The security system - group-role-based >>> >>> - Tight integration with velocity (which of course can be >>> accomplished in other frameworks as struts). And what I like with >>> velocity >>> is that the templates looks very much like static html, i.e. they >>> are very >>> readable. I don't like jsp. >>> >>> - The torque object model that is generated >>> >>> - A clear file structure for the environment. (What I >>> like in >>> turbine is that I can create a folder for x number of pages and then >>> create >>> a default.java class in the corresponding package and have the same >>> permission check for all those pages) >>> >>> >>> >>> The biggest flaw I think turbine has is that it isn't really maven 2 >>> compatible. I really like working with maven, but I prefer not to >>> use >>> version 1. >>> >>> >>> >>> I'm just sending this since I think it's sad that it is not used >>> anymore and >>> I wonder why. >>> >>> Any reply/discussion would be appreciated. >>> >>> /Ludwig >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org >> For additional commands, e-mail: user-help@turbine.apache.org >> > > _________________________________________________________________ > Bing brings you maps, menus, and reviews organized in one place. > http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org For additional commands, e-mail: user-help@turbine.apache.org
I have used both Struts and Turbine, but for the couple production sites we run I use Turbine. I've never really like the Bean/JSP approach Struts uses. Not a big fan of php either. Once you understand exactly how Turbine works, it's extremely easy to do whatever you want with it. Maybe its just me, but Turbine does everything I need and has for awhile. Maybe that contributes to why this list is quiet. Just my ancedotal 2 cents, Sheldon Ross > Subject: Re: What is the state of turbine? > From: hoffmann@apache.org > Date: Thu, 5 Nov 2009 17:17:25 +0100 > To: user@turbine.apache.org > > Hi Ludwig, > > we have setup turbine to be built by m2. Turbine is not dead. Only the > people developing on it, are either busy at their work, or involved > into further uncouling of the core serivces inside the fulcrum project > (Thomas Vandahl) > > If you need support getting your app running and other things like > build your app using m2, I can really help you. > > Although there are only few active developers, the few know turbine to > its bones. So just ask > > Kind regards > > Juergen > > Am 05.11.2009 um 11:37 schrieb Ludwig Magnusson: > > > Hello! > > > > I am currently working in a big web application project with a few > > fellow > > developers. When we started out we were discussing a lot on which > > framework > > to use. I was familiar with turbine and I liked it very much. > > However the > > others were skeptical since there is very few persons involved in > > turbine at > > the moment. We decided to work with php and Zend and we have made a > > quite > > cool alpha version of out app. However, me and the other main > > developer > > (both computer engineers) have realized that the php community does > > not have > > very good understanding of concepts as best practices when it comes to > > object orienting, testing, database management and so on. Especially > > for > > complex applications. We are now considering switching framework and > > we are > > looking at java-based frameworks. (Because java rules) > > > > > > > > We have looked at other apache frameworks such as tapestry and > > struts (which > > are much more active). But to me it seems as if they do not address > > the > > things that I really like about turbine and that I feel are basic in > > the > > kind of application we are developing. For instance no other > > framework seems > > to have a user class (or interface) which I think is a basic feature > > since > > validations on the user are done on almost every page. Further on, > > if there > > is some kind of permission system, it is always role-based and not > > group-role-based which we need. > > > > > > > > So my question is.. Is turbine dying? Or is it already dead? And why? > > > > I am not _that_ experienced in developing complex web applications. > > Does > > turbine have some kind of major flaw that I don't see? > > > > > > > > What I like and what I am looking for is this: > > > > - The security system - group-role-based > > > > - Tight integration with velocity (which of course can be > > accomplished in other frameworks as struts). And what I like with > > velocity > > is that the templates looks very much like static html, i.e. they > > are very > > readable. I don't like jsp. > > > > - The torque object model that is generated > > > > - A clear file structure for the environment. (What I like in > > turbine is that I can create a folder for x number of pages and then > > create > > a default.java class in the corresponding package and have the same > > permission check for all those pages) > > > > > > > > The biggest flaw I think turbine has is that it isn't really maven 2 > > compatible. I really like working with maven, but I prefer not to use > > version 1. > > > > > > > > I'm just sending this since I think it's sad that it is not used > > anymore and > > I wonder why. > > > > Any reply/discussion would be appreciated. > > > > /Ludwig > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@turbine.apache.org > For additional commands, e-mail: user-help@turbine.apache.org > _________________________________________________________________ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1