Vince.Power_at_medavie.bluecross.ca wrote:
> Thanks, I set that variable and now to see if it makes a difference.
>
> On another note; all of the Unknown transactions I see in Glassfish
> seem to be a created when I use the JBI BPEL engine, has one one seen
> similar behavior?
Unfortunately, component name and resource names will work only with
standard Java EE components.
regards
sankar
>
> Regards,
> Vince
>
>
>
> *sankara rao bhogi <Sankara.Rao_at_Sun.COM>*
> Sent by: Sankara.Rao_at_Sun.COM
>
> 07/17/2009 06:10 AM
> Please respond to
> users_at_glassfish.dev.java.net
>
>
>
> To
> users_at_glassfish.dev.java.net
> cc
>
> Subject
> Re: Question about Transactions
>
>
>
>
>
>
>
>
>
> Vince,
>
> Transaction Id, Transaction State, Elapsed Time(milliseconds), component
> Name( which started the transaction), resource names(list of resources
> being accessed) are the five columns supposed to be in the monitoring
> data.
>
> Transaction time out can be configured with the help
> transaction-service.timeout-in-seconds attribute in the domain.xml, by
> default it means no time out, you can configure it to positive value.
>
> Can you set transaction-service monitoring to OFF and set it back again
> to HIGH or LOW and see of you get any difference in the monitoring data.
>
> regards
> sankar
>
> Vince.Power_at_medavie.bluecross.ca wrote:
> > In my container I have about 64,000 transactions listed as active in
> > my monitoring (and another 121,000 committed), and they all look like
> > the following:
> >
> 24A10000F440788262636C7838382E61746C2E626C756563726F73732E63612C706F73436C61696D7350726F636573736F722D30312C503333373030Active
>
> > 367 unknown 0000000000017C79_00 NoTransaction 314
> >
> > Is there anyway to get more details on the transaction beyond this
> > (like which EJBs they are using) and is there a value I can set to
> > force them to timeout after a certain amount of time?
> >
> > Thanks,
> > Vince
> >
>
>
>
> -----------------------------------------------------------------------
> This communication, including any attached documentation, is intended
> only for the person or entity to which it is addressed, and may
> contain confidential, personal, and/or privileged information. Any
> unauthorized disclosure, copying, or taking action on the contents is
> strictly prohibited. If you have received this message in error,
> please contact us immediately so we may correct our records. Please
> then delete or destroy the original transmission and any subsequent
> reply. Thank you.
>
> La présente communication, y compris toute pièce qui y a été jointe,
> est destinée uniquement à la personne ou à l’entité à laquelle elle a
> été adressée, et contient des renseignements à caractère confidentiel
> et personnel. Toute diffusion ou reproduction non autorisée ou toute
> intervention entreprise relativement à son contenu est strictement
> interdite. Si vous avez reçu ce message par erreur, veuillez nous le
> signaler immédiatement afin que nous puissions effectuer la correction
> à nos dossiers. Veuillez par la suite supprimer ou détruire le contenu
> de la transmission originale ainsi que toute réponse ultérieure. Merci.
> -----------------------------------------------------------------------