Stateless and stateful

Hi all,
Can any one give some idea about stateless and stateful in BSP's ?

Hi,
All is well explained in
http://help.sap.com/saphelp_nw70/helpdata/EN/cc/d6eefc28f711d5991f00508b6b8b11/frameset.htm
and
http://help.sap.com/saphelp_nw70/helpdata/EN/cc/d6eef628f711d5991f00508b6b8b11/frameset.htm
Eddy

Similar Messages

Jcom vb-ejb(both stateless and stateful)'s problem

I try the jcom sample on wls7.0sp4,it's ok.(the sample used entityBean)
then,I try the session bean(both stateless and stateful),some problem occur :
<2003/10/29 17:31:54:JST> <Error> <COM> <210000> <IOXIDResolver opNum 5 invoked.
This method is not implemented.>
<2003/10/29 17:31:55:JST> <Error> <COM> <210000> <IOXIDResolver opNum 5 invoked.
This method is not implemented.>
<2003/10/29 17:31:55:JST> <Error> <COM> <210000> <Export of object: examples.ejb
[email protected] barred>
the client vb source :
Set objTemp = GetObject("examplesServer:jndi:ejb20-statefulSession-TraderHome")
//the statement is wrong!!
Set mobjHome = objNarrow.narrowobjTemp, "examples.ejb20.basic.statelessSession.TraderHome")
can anyone help me?
thks!
p.s: the jndi name is correct.

A deployed bean can not be both stateful and stateless. You must specify the session-type in the deployment descriptor. The reason that deployed beans must be either stateful or stateless is that the ejb container must know how to handle them. Stateful and stateless beans have very different life cycles as I'm sure HeadFirstEJB pointed out.
What HeadFirstEJB might have been trying to say is that if you have a no-arg create along with other create methods, you may be able to deploy the bean as stateless in one environment and stateful in another. I can't think of any reason you might want to do this but I suppose there might be some valid reasons out there.

Stateless and Stateful beans.

Please tell me what are the important differences between stateless, and stateful beans.
Thanks in advance.

See this thread
http://forum.java.sun.com/thread.jsp?forum=13&thread=529706&tstart=15&trange=15

Question about operations allowed in methods of stateless and stateful bean

Hello,
Can anyone tell me why ejbRemove and ejbCreate are allowed entreprise beans and resource manager access in stateful session beans and not in stateless session beans?
Thanks in advance,
Julien Martin.

Salut Julien,
Can anyone tell me why ejbRemove and ejbCreate are
allowed entreprise beans and resource manager access
in stateful session beans and not in stateless session
beans?I'm not sure I fully understand your question, but here is some information that may answer it.
The user is the one who creates and removes a stateful session bean. The container is the one who creates and removes a stateless session bean. So the user can pass any parameters to the create of a SFSB because he theorically knows what to pass. The container doesn't, and doesn't want to. It just wants to create SLSB to pool them, but it doesn't pool SFSB.
Maybe it doesn't answer your question. Can you reformulate?
Kexkey

As I was installing the Windows 7 on my Imac and stated how I wanted to divide the drive I put 160, but I want to add more space how can I can the drive space to from 160 to 250? please help thank you.

As I was installing the Windows 7 on my Imacwith the bootcamp and stated how I wanted to divide the drive I put 160, but I want to add more space because of the adobe software it will not install two of them, so how can I add more on the drive space to from 160 to 250? please help thank you.

I'm not sure this is what you're looking for, but it might help:
"If you made the Windows partition too small
First, back up all the information on your Windows partition. Then run Boot Camp
Assistant to restore your disk to a single volume. Restart your computer and use Boot
Camp Assistant to partition the disk again and reinstall Windows. Don’t forget to install
the Boot Camp drivers after installing Windows."
(from Bootcamp Assistant Manual see pg 22)

While using my pad it suddenly stopped and stated that I neede to activate it. Now it wont activate even though it had already been activated. What do I do?

while using my pad it suddenly stopped and stated that I neede to activate it. Now it wont activate even though it had already been activated. What do I do?

Everytime I try to do an activation it later tells me that it could not activate because the activation server is temporarily unavailable. I ready to throw it.

PO for LAN failover and stateful failover link?

Hi.. We have 2 x ASA 5520s running ver 9.0. We plan to aggregate the 2 interfaces used for LAN failover and stateful failover into a lacp PO. So both the ASAs are connected to each other directly using these 2 interfaces and then we logically make it a one PO. We then assign the PO intface an ip. Is this supported?

You can use any unused interface (physical, redundant, or EtherChannel) as the failover link. (Source)
That said, It would be an uncommon implementation. I almost always see them on separate physical interfaces.

Database locking (state versus stateless) and indexes on oracle database

Does anyone have a link to a document talking about database locking (state versus stateless) and talking about indexes in oracle database?

No version information and no information as to what you mean by "locking" so no help is possible.
You could mean LOCK TABLE in version 7.3.4 or SELECT FOR UPDATE in 11.1.0.7 or something else entirely.

Re: User Session using ServletSession and Stateful EJB in Cluster

          Sorry , I didn't use WLS 6.0, we use wls 5.1 in production.
          But in Wls 6.0, in some situations , the state of the stateful session bean can be lost. So it's not so reliable. You have to deal with it in the client code. Instead, servlet is a reliable solution.
          In order to test under wls6.0, you can store the handle of the EJBObject in the HttpSession, not in jndi, cos if the instance fails, all its objects will be removed by remaining instances from jndi. In another instance, you get the handle, and try to get the EJBObject.
          In wls5.1, some information like the server url must be embeded inside the handle. But in wls6.0, I don't know how they deal with it.
          I am looking forward to your results
          "Anuj Soni" <[email protected]> wrote:
          >
          >What kind of clustering problems you had with WL6.0 for Stateful session beans ? It will be helpful for me to know before hand.
          >
          >BTW, how were you able to test stateful session beans in a cluster under WL6.0 i.e. were you storing the Handle or EJBObject in HttpSession or did you store it in JNDI ?
          >
          >Thanks,
          >
          >Anuj
          >"Tao Zhang" <[email protected]> wrote:
          >>Although it's very advanced to take advantage of both http session and
          >>stateful session bean replication, but if you rely on the stateful session
          >>bean's state, you will be in trouble. Because the support of stateful
          >>session bean's replication is not perfect in wls6.0. We already chaned
          >>almost all stateful session beans into servlets or entity beans.
          >>
          >>I am not sure about the handle of the EJBObject. I think it should be able
          >>to reconstruct for us otherwise we can't use the handle any more.
          >>
          >>You can do a test. BTW, could you tell me the result?
          >>
          >>Thanks.
          >>
          >>Anuj Soni <[email protected]> wrote in message
          >>news:[email protected]...
          >>>
          >>> Hi,
          >>>
          >>> I am designing the workflow for my web application using a Stateful
          >>session bean. As Weblogic 6.0 supports clustering of stateful session bean
          >>and HttpSession(in-memory replication), I want to use the combination of
          >>both techniques to provide load-balancing and fail-over safety for user
          >>sessions and their corresponding workflows.
          >>>
          >>> The question I have is that, Is Handle obtained using
          >>EJBObject.getHandle(), fail-over safe (for a clusterable stateful bean), so
          >>that I can reconstruct the reference to EJBObject on the secondary server
          >>incase of primary server crash.
          >>>
          >>> My understanding is that I should store Handle in the HttpSession as it is
          >>Serializable not the EJBObject. The weblogic 6.0 document only talks about
          >>the replica-awareness of EJBObject.
          >>>
          >>> If my above assumption is incorrect, Can you tell me how else I can
          >>achieve my goal ?
          >>>
          >>> Thanks in advance.
          >>>
          >>> Anuj Soni
          >>
          >>
          >


Any one tested this scenario yet? i.e: storing the handle to an EJB object and then trying to re-use after the HttpSession is restored?
          Thanks.

ASA connection rate and stateful packet inspections rate limiting

Can anyone please send me a link or links on how configuring "connection rate" and "stateful packet inspections rate" on an ASA?
It seems not easy to find the links
thanks,
Han

Hi Han,
I assume you're referring to the use of resource classes to limit the connection build and inspection rates? If so, this is only available in multiple context mode. You can find some config examples for that feature here:
http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/mode_contexts.html#wp1142960
-Mike

Stateless Vs Stateful - Codegen Just Like Ghost

Hi all,
Does anyone encounter such error?
Every time we have this error, we got no idea at all.
Sometimes it disappaer itself, sometimes it comes.
The solution just finally repack everything from the bottom up using
deploytool.
This time, I have one old EAR running well.
I put an updated an EJB class in /APPS/ and then restart server.
It works well. (Note : No EJB method signature change)
But if I pack the class into the old EAR using deploytool, the error
ocurrs when running the application. Everything others keep the same.
I have tried using ANT to pack the EAR from the bottom up.
The error still exists. Modifying the GUID of the EJB
doesn't make any better result.
We have report the "Stateless vs. Stateful - Codegen vs. Propertie"
to iPlanet support very earlier. The answer is official,
"Try to cleanup the application in the registry or repack"
ps. Every deployment I will use kregedit to check whether the registry
deleted
or not first.
Any ideas greatly appreciated.
Clement
KJS Log
Missing identifier: Stateless vs. Stateful - Codegen vs. Properties file
mismatc
h : home_initMeta1 in resource: eb
[21/May/2001 13:58:19:9] error: EB-Stateless vs. Stateful - Codegen vs.
Properti
es file mismatch : home_initMeta1: Missing id! Stateless vs. Stateful -
Codegen
vs. Properties file mismatch : home_initMeta1
[21/May/2001 13:58:19:9] error: EB-010: Unable to initialize transport
for home
with guid {DBBD3EC0-5B27-11D5-B21C-000021FBF50D}
2001-05-21 13:58:19,928 [ibscs2:8200] ERROR (FormServlet.java:71)- ***
System F
ailure Notice *** ServiceException : CODE =4 Nested Exception in
ServiceLocator.
java : getHome - Couldn't activate home for name: FreeTrialFacadeEJB

Some may say it is bug of iAS SP1 or SP1 Revision B.
But I am using iAS SP2.
Clement
Clement wrote:
>
Hi all,
Does anyone encounter such error?
Every time we have this error, we got no idea at all.
Sometimes it disappaer itself, sometimes it comes.
The solution just finally repack everything from the bottom up using
deploytool.
This time, I have one old EAR running well.
I put an updated an EJB class in /APPS/ and then restart server.
It works well. (Note : No EJB method signature change)
But if I pack the class into the old EAR using deploytool, the error
ocurrs when running the application. Everything others keep the same.
I have tried using ANT to pack the EAR from the bottom up.
The error still exists. Modifying the GUID of the EJB
doesn't make any better result.
We have report the "Stateless vs. Stateful - Codegen vs. Propertie"
to iPlanet support very earlier. The answer is official,
"Try to cleanup the application in the registry or repack"
ps. Every deployment I will use kregedit to check whether the registry
deleted
or not first.
Any ideas greatly appreciated.
Clement
KJS Log
Missing identifier: Stateless vs. Stateful - Codegen vs. Properties file
mismatc
h : home_initMeta1 in resource: eb
[21/May/2001 13:58:19:9] error: EB-Stateless vs. Stateful - Codegen vs.
Properti
es file mismatch : home_initMeta1: Missing id! Stateless vs. Stateful -
Codegen
vs. Properties file mismatch : home_initMeta1
[21/May/2001 13:58:19:9] error: EB-010: Unable to initialize transport
for home
with guid {DBBD3EC0-5B27-11D5-B21C-000021FBF50D}
2001-05-21 13:58:19,928 [ibscs2:8200] ERROR (FormServlet.java:71)- ***
System F
ailure Notice *** ServiceException : CODE =4 Nested Exception in
ServiceLocator.
java : getHome - Couldn't activate home for name: FreeTrialFacadeEJB
Name: scwong.vcf
scwong.vcf Type: VCard (text/x-vcard)
Encoding: 7bit
Description: Card for Clement

Stateless Vs. Stateful

In the Web Services documentation, it looks like Stateless is the prefer way since the server will manage sessions for you. You don't have to pass in the jsessionid everytime.
Is there a reason why you would use Stateful approach and manage your session yourself?
Thanks
I'm using CRMOD V6

Probably the primary reason that you would go stateful is if you were dealing with a large quantity of records (for example, extracting data from CRMOD). And you want the data to come back in a sorted order, but the record byte size exceeded the XML 20k limit. By using the pagesize to manage the 20k byte boundary on the message, yet still using the other aspects of the query... such as the sort order.

Java UserControls are stateless or stateful?

I read, and I could verify it, that UserControls are accessed via a generic SLSB
(stateless SessionBean). But when a UserControl, created with variables, is called
from a PageFlow, each user session uses its own UserControll instance with the
appropriate state info (stored in the variables).
My questions is: How is this possible if we are invoking it via a SLSB?. Can we
suppose that this is a correct behaviour and we can design assuming it?.
Thanx.

Some may say it is bug of iAS SP1 or SP1 Revision B.
But I am using iAS SP2.
Clement
Clement wrote:
>
Hi all,
Does anyone encounter such error?
Every time we have this error, we got no idea at all.
Sometimes it disappaer itself, sometimes it comes.
The solution just finally repack everything from the bottom up using
deploytool.
This time, I have one old EAR running well.
I put an updated an EJB class in /APPS/ and then restart server.
It works well. (Note : No EJB method signature change)
But if I pack the class into the old EAR using deploytool, the error
ocurrs when running the application. Everything others keep the same.
I have tried using ANT to pack the EAR from the bottom up.
The error still exists. Modifying the GUID of the EJB
doesn't make any better result.
We have report the "Stateless vs. Stateful - Codegen vs. Propertie"
to iPlanet support very earlier. The answer is official,
"Try to cleanup the application in the registry or repack"
ps. Every deployment I will use kregedit to check whether the registry
deleted
or not first.
Any ideas greatly appreciated.
Clement
KJS Log
Missing identifier: Stateless vs. Stateful - Codegen vs. Properties file
mismatc
h : home_initMeta1 in resource: eb
[21/May/2001 13:58:19:9] error: EB-Stateless vs. Stateful - Codegen vs.
Properti
es file mismatch : home_initMeta1: Missing id! Stateless vs. Stateful -
Codegen
vs. Properties file mismatch : home_initMeta1
[21/May/2001 13:58:19:9] error: EB-010: Unable to initialize transport
for home
with guid {DBBD3EC0-5B27-11D5-B21C-000021FBF50D}
2001-05-21 13:58:19,928 [ibscs2:8200] ERROR (FormServlet.java:71)- ***
System F
ailure Notice *** ServiceException : CODE =4 Nested Exception in
ServiceLocator.
java : getHome - Couldn't activate home for name: FreeTrialFacadeEJB
Name: scwong.vcf
scwong.vcf Type: VCard (text/x-vcard)
Encoding: 7bit
Description: Card for Clement

MDB and Stateful SB

Hi,
I have a MDB that delegates message processing to stateful SB. My question is: does weblogic treats every new request to statefulSB, resulting from new JMS message, as a new client (and consequently, uses new instance of StatefulSB) or all messages are beeing processed under the same bean instance?
It seems, that since there is no client identity in MDB (anonyumous, or predefined in run-as element principal), then all requests to stateful SB should be delegated to the same instance of bean. However, checking hashCode inside statefulSB's method shows that they are different.
Could you give me some light on this?
TIA,
Vladimir

I'd say that depends on how you coded your mdb.
If you only perform a lookup once when you're mdb initialzes, you'll have one client session bean per mdb. (although I'd recommend lazily loading the session bean once during the first request cache it for further results by means of an instance variable for example)
If you perform a lookup every time you receive a message you'll create a new client for every message. This approach is generally not used unless you're using a stateful session bean which wouldn't be a very good solution because session beans are supposedly bad on performance and memory use as well as not being thread safe. (can be implemented as such though but why use a statefull session bean then?).
How many session beans factually get created depends on your workload and configuration. There's typically a pool of session beans that get reused. They go through cycles of passivation and activation.
In your case what you seem to be doing doesn't actually seem like a good idea.
A statefull session bean shouldn't be called concurrently so you should create a new one for every message which will result in poor performance of you have many mdb's. The best solutions is to have a stateless session bean lookup once that handles all messages per mdb instance.

ESB and Stateful web services

Folks,
I’ve got two web services that are called in succession. The first web service performs a search and caches the results on the server, returning only some basic information about how many results were found (in the payload) and a session id (as an attribute in a HTTP header). The second service is called afterwards, passing some page request information (in payload) and the session id (in the HTTP header). The session id is used to find the appropriate search results and return them lazily (based the given page request information).
The web service requests are done through ESB and OWSM. My problem, however, is that according to the ESB developer’s guide (http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28211.pdf , page 5-29, ‘Limitations of ESB Header Support’) ESB is not capable of setting header attributes (at least not SOAP header attributes).
Is it possible to use stateful web services with the ESB? If so, how is the SessionID handled on the ESB and how is it correlated with the clients of the ESB who are getting the results back from this stateful web service?
Thanks in advance,
Joseph

Dave,
We have invoked the two services mentioned above in four different manners using Java code.
1. We are invoking the services through ESB with no success. The HTTP header (set-cookie) never makes it back.
2. We are invoking the services through Web Services Manager (the services are registered directly with OWSM) with no success. The HTTP header (set-cookie) never makes it back.
3. We are invoking the services through Web Services Manager (with ESB providing a wrapper for the services) with no success. The HTTP header never (set-cookie) makes it back.
4. Invoking the services directly (no OWSM, no ESB). This method is successful. HTTP headers are being exchanged without incident.
We are using Ethereal to check out the traffic going back and forth so we can see the SOAP headers getting propagated back and forth as you had mentioned. The problem is that the HTTP headers (as mentioned in my first posting) containing the session information are getting dropped when using ESB or Web Services Manager.
Any suggestions?
Thanks,
Joseph

Stateless and stateful

Similar Messages

Maybe you are looking for