Fine for me

Thought to some weird usages i prefer to skip if not involved ;)
Le 26 nov. 2012 00:01, "Howard W. Smith, Jr." <smithh032...@gmail.com> a
écrit :

> @schedule on @stateful bean but according to java ee 6 tutorial, @schedule
> cannot be used on @stateful, so that may be the root cause of the behavior
> discussed in this topic.
>
> I removed the two from my app as it was not really necessary, it was just
> something that I wanted to try.
>
> So for now, we can maybe end this conversation unless you were trying to
> say something after I answered your question.
>  On Nov 25, 2012 5:53 PM, "Romain Manni-Bucau" <rmannibu...@gmail.com>
> wrote:
>
> > Which timeout config for session and stateful?
> > Le 25 nov. 2012 22:38, "Howard W. Smith, Jr." <smithh032...@gmail.com> a
> > écrit :
> >
> > > Romain,
> > >
> > > The following is quote from Simple Stateful
> > > example<
> > http://tomee.apache.org/examples-trunk/simple-stateful/README.html
> > > >
> > > :
> > >
> > > *"As its name suggests, a stateful session bean is similar to an
> > > interactive session. A stateful session bean is not shared; it can have
> > > only one client, in the same way that an interactive session can have
> > only
> > > one user. When the client terminates, its stateful session bean appears
> > to
> > > terminate and is no longer associated with the client."*
> > >
> > >
> > > The following occurred while it's owner (or 'the client') was still in
> > > session. This scares me or makes me not want to use stateful beans. I
> > > assume @stateful bean will be available to it's owner, CDI
> > @SessionScoped,
> > > but this was the result, and this caused exception to be raised and
> > > displayed to enduser.
> > >
> > > Nov 25, 2012 4:06:26 AM
> > >
> org.apache.openejb.core.stateful.StatefulContainer$StatefulCacheListener
> > > timedOut
> > > INFO: Removing the timed-out stateful session bean instance
> > > f0ed2a6d7fb07688:13d8158c:13b36b3052b:-7fff
> > > Nov 25, 2012 4:06:26 AM
> > >
> org.apache.openejb.core.stateful.StatefulContainer$StatefulCacheListener
> > > timedOut
> > > INFO: Removing the timed-out stateful session bean instance
> > > f0ed2a6d7fb07688:13d8158c:13b36b3052b:-7ffe
> > > Nov 25, 2012 4:09:42 AM
> org.apache.openejb.core.stateful.SimplePassivater
> > > activate
> > > *INFO: Activation failed: file not
> > >
> > >
> >
> found*D:\apache-tomee-plus-1.5.1-SNAPSHOT\temp\f0ed2a6d7fb07688=13d8158c=13b36b3052b=-7ffe
> > >
> > >
> > >
> > > On Sun, Nov 25, 2012 at 5:23 AM, Romain Manni-Bucau
> > > <rmannibu...@gmail.com>wrote:
> > >
> > > > I dont see errors, thats just info
> > > >
> > > > Any functional errors?
> > > > Le 25 nov. 2012 10:13, "Howard W. Smith, Jr." <
> smithh032...@gmail.com>
> > a
> > > > écrit :
> > > >
> > > > > Interesting, got the following error message, when I opened an
> xhtml
> > > page
> > > > > in the web app that references the CDI @SessionScoped that injects
> > > > > @Stateful bean.
> > > > >
> > > > > Nov 25, 2012 4:06:26 AM
> > > > >
> > >
> org.apache.openejb.core.stateful.StatefulContainer$StatefulCacheListener
> > > > > timedOut
> > > > > INFO: Removing the timed-out stateful session bean instance
> > > > > f0ed2a6d7fb07688:13d8158c:13b36b3052b:-7fff
> > > > > Nov 25, 2012 4:06:26 AM
> > > > >
> > >
> org.apache.openejb.core.stateful.StatefulContainer$StatefulCacheListener
> > > > > timedOut
> > > > > INFO: Removing the timed-out stateful session bean instance
> > > > > f0ed2a6d7fb07688:13d8158c:13b36b3052b:-7ffe
> > > > > Nov 25, 2012 4:09:42 AM
> > > org.apache.openejb.core.stateful.SimplePassivater
> > > > > activate
> > > > > INFO: Activation failed: file not found
> > > > >
> > > > >
> > > >
> > >
> >
> D:\apache-tomee-plus-1.5.1-SNAPSHOT\temp\f0ed2a6d7fb07688=13d8158c=13b36b3052b=-7ffe
> > > > >
> > > > > On Sun, Nov 25, 2012 at 2:55 AM, Romain Manni-Bucau
> > > > > <rmannibu...@gmail.com>wrote:
> > > > >
> > > > > > During app life, mainly depending on timeout
> > > > > > Le 25 nov. 2012 08:41, "Howard W. Smith, Jr." <
> > > smithh032...@gmail.com>
> > > > a
> > > > > > écrit :
> > > > > >
> > > > > > > No issue. If @Stateful beans live through shutdown/restart of
> > > TomEE,
> > > > > then
> > > > > > > when will @Stateful bean passivate?
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Nov 25, 2012 at 2:34 AM, Romain Manni-Bucau
> > > > > > > <rmannibu...@gmail.com>wrote:
> > > > > > >
> > > > > > > > What's the issue?
> > > > > > > > Le 25 nov. 2012 08:33, "Howard W. Smith, Jr." <
> > > > > smithh032...@gmail.com>
> > > > > > a
> > > > > > > > écrit :
> > > > > > > >
> > > > > > > > > Any way to prevent @Stateful from being re-injected on when
> > > TomEE
> > > > > > > starts,
> > > > > > > > > or it's best for me to use @Stateless instead of @Stateful?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sun, Nov 25, 2012 at 2:27 AM, Romain Manni-Bucau
> > > > > > > > > <rmannibu...@gmail.com>wrote:
> > > > > > > > >
> > > > > > > > > > Yes it is.
> > > > > > > > > >
> > > > > > > > > > If you want to save data between startups you can use the
> > > > session
> > > > > > > > itself
> > > > > > > > > > Le 25 nov. 2012 07:57, "Howard W. Smith, Jr." <
> > > > > > > smithh032...@gmail.com>
> > > > > > > > a
> > > > > > > > > > écrit :
> > > > > > > > > >
> > > > > > > > > > > If stateful beans were injected after server was
> started,
> > > are
> > > > > the
> > > > > > > > same
> > > > > > > > > > > stateful beans re-injected automatically by TomEE when
> > > TomEE
> > > > > > > > restarts?
> > > > > > > > > > >
> > > > > > > > > > > I ask this question, because I see the following after
> > > > > restarting
> > > > > > > > TomEE
> > > > > > > > > > > (after shutdown TomEE without logging out of user
> > sessions
> > > in
> > > > > > > > > browsers):
> > > > > > > > > > >
> > > > > > > > > > > INFO: Deployed
> > > > > > > > > > >
> > > > > >
> Application(path=C:\apache-tomee-plus-1.5.1-SNAPSHOT\webapps\tomee)
> > > > > > > > > > > Nov 25, 2012 1:48:57 AM
> > org.apache.coyote.AbstractProtocol
> > > > > start
> > > > > > > > > > > INFO: Starting ProtocolHandler ["http-bio-8080"]
> > > > > > > > > > > Nov 25, 2012 1:48:57 AM
> > org.apache.coyote.AbstractProtocol
> > > > > start
> > > > > > > > > > > INFO: Starting ProtocolHandler ["ajp-bio-8009"]
> > > > > > > > > > > Nov 25, 2012 1:48:57 AM
> > > org.apache.catalina.startup.Catalina
> > > > > > start
> > > > > > > > > > > INFO: Server startup in 15257 ms
> > > > > > > > > > > *UsersStatefulBean() constructor/injected*
> > > > > > > > > > > *UsersStatefulBean() constructor/injected*
> > > > > > > > > > >
> > > > > > > > > > > Is this normal behavior or working as designed? Those 2
> > > > > stateful
> > > > > > > > beans
> > > > > > > > > > were
> > > > > > > > > > > injected while TomEE was running prior before
> > > > > > shutdown-and-restart.
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > Howard
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to