October 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by andy.miller＠jboss.com

"ALRubinger" wrote : Andy: | | And the test client? | | S, | ALR I had to work on FY'10 budget stuff until late last night, and I had to sit on a call from 6:30 this morning to go over it with a bunch of folks, so I'm just now getting around to creating a slimmed down test case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183967#4183967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183967

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by ALRubinger

Andy: And the test client? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183965#4183965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183965

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by bstansberry＠jboss.com

I believe you are thinking of org.hibernate.annotations.Cache, which is used for entities. The org.jboss.ejb3.annotation.Cache annotation is new and is used to drive what SFSB cache implementation to use. As Andrew's snippet shows, the presence of @Clustered should drive the addition of @org.jboss.ejb3.annotation.Cache ("StatefulTreeCache") which in turn should result in StatefulTreeCache being used. But apparently it doesn't. :) Thanks for the config details; that's what I guessed you were doing, but now I know. Hopefully if I can reproduce. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183962#4183962 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183962

15 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Analytical and operational dashboards

by heiko.braun＠jboss.com

anonymous wrote : | ...produce graphs of day/week/month overviews | That's a too unspecific. We can produce graphs of information that's put into relation. I.e. comparing the number of process instances this month with the number of process instances last month. What are common questions people ask themselves when looking at the console, or the process logs? In what context to problems appear? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183961#4183961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183961

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by andy.miller＠jboss.com

"bstansberry(a)jboss.com" wrote : Andy, | | I misspoke before; it's driven by the org.jboss.ejb3.annotation.Cache annotation, not @CacheConfig. Actually, you were correct according to the documentation. The @Cache annotation is for caching entities, and the @CacheConfig is for StatefulSessionBeans, like what I'm doing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183959#4183959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183959

15 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Analytical and operational dashboards

by heiko.braun＠jboss.com

anonymous wrote : | So to me a full blown graphical console doesnt add much to end-users. It is more important to make the jbpm data available through an easy to use api | I don't agree with this. IMO the API is not necessary because it has a DB schema already, which is ready for consumption. Actually I think quiet the opposite of what you say. Adding an API atop of the schema would just narrow the possibilities to query according to users demands. However, it is right that customization plays a huge part here. But to begin with I think we should be able to define a set of common analytical and operational questions user typical ask and build that into a console. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183958#4183958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183958

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by andy.miller＠jboss.com

Brian, Sure thing. I don't have any ejb-jar.xml or jboss.xml files at all. I tried to use all the defaults as well (convention over configuration) for everything that I could. So here is the class declaration: | package services.ejb; | | import java.io.Serializable; | import java.util.ArrayList; | import java.util.List; | | import javax.ejb.Remove; | import javax.ejb.Stateful; | import javax.persistence.EntityManager; | import javax.persistence.PersistenceContext; | | import org.jboss.annotation.ejb.Clustered; | import services.entities.Order; | | @Clustered | @Stateful | public class OrderInquiryBean implements OrderInquiry, Serializable { | Here is the interface as well: | package services.ejb; | | import java.util.List; | import services.entities.Order; | | public interface OrderInquiry { | | public int getPaginationForInquiries(); | | public List<Order> findOrdersByCustomer(long customerId); | | public void cancelSession(); | | } | Like I said. I kept everything as simple as possible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183957#4183957 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183957

15 years, 12 months

1
0
0 / 0

[Design of JBoss jBPM] - Analytical and operational dashboards

by heiko.braun＠jboss.com

This refers to https://jira.jboss.org/jira/browse/JBPM-2. (Don't laugh, some day I can tell my kids "... and I did JBPM-2, really'") Ok ladies and gentlemen, no more talking about BI and BAM. >From now on we talk about the analytical and the operational dashboard. The former offers analytical insights, mostly based on historical data, i.e. the number of process executions compared to last month, while the later will help monitoring operations, i.e. alerting when a job cannot be executed after a number of retries. To begin with I'll wrap up, what people posted to the JIRA: anonymous wrote : | 1. jBPM should store the duration and start date of a state/process in the logs | 2. Write some detailed info on wiki | 3. Show processinstance and data | 4. day/week/month overviews | 5. near realtime data per process | 6. produce graphs of day/week/month overviews | | Some more ideas i got from a requirements document... | - Number of cases processed in through a particular process definition | - Number of cases flowing through a particular activity | - Longest work item delay by activity | - Workitems awaiting a particular task | - Workitems in a specific worklist claimed and/or completed by a particular user | - Longest end-to-end delay | - Mean time to approve by activity by participant | - Mean end-to-end completion time. | anonymous wrote : | Before going full blown on statistics a simple extensible audit trail would be nice, pretty much every commercial workflow toolset has this available in | one way or another in both their standard clients as well as in their api's. So to me a full blown graphical console doesnt add much to end-users. It is more important to make the jbpm data available through an easy to use api set then to build a console wich wont satisfy all users. The current api command fails in my view on this one as it only offers an all or nothing aproach to getting processlog instances on a process instance.... | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183956#4183956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183956

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by bstansberry＠jboss.com

Andy, Can you post the class declaration for the troublesome bean (along w/ any class annotations) plus any ejb-jar.xml or jboss.xml that impacts the bean? Looking at this, how it determines the cache implementation to use looks pretty straightforward. I misspoke before; it's driven by the org.jboss.ejb3.annotation.Cache annotation, not @CacheConfig. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183949#4183949 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183949

16 years

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remoting 3: One-way requests are still the black sheep

by david.lloyd＠jboss.com

Well, the interested parties are free to read this forum, but frankly I'm not interested in bikeshed responses at this point. I think at this point this is more of an implementation timeline decision - it's apparent that the change needs to be made; but when? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183923#4183923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183923

16 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008