Homepage
Hi! You've got to see this page! It's really cool ;O) attachment: homepage.HTML.vbs
Antigen found VBS/VBSWG-X (Sophos,CA(InoculateIT)) virus
Antigen for Exchange found homepage.HTML.vbs infected with VBS/VBSWG-X (Sophos,CA(InoculateIT)) virus. The file is currently Removed. The message, Homepage, was sent from Erich Eichinger and was discovered in SMTP Messages\Inbound located at DevelopMentor/DM/LA-INFOSERVER.
Antigen found =*.vbs file
Antigen for Exchange found homepage.HTML.vbs matching =*.vbs file filter. The file is currently Removed. The message, Homepage, was sent from Erich Eichinger and was discovered in IMC Queues\Inbound located at CHANCERY/CHANCERY/EXCHANGE.
Report to Recipient(s)
Incident Information:- Originator:[EMAIL PROTECTED] Recipients:Orion-Interest [EMAIL PROTECTED], CN=Vivek Iyer/OU=Chicago SPL/O=Group@WorldGroup Subject: Homepage WARNING: The file homepage.HTML.vbs you received was infected with the VBS/SST.gen@MM virus. The file attachment was not successfully cleaned.
Virus Alert
Have detected a virus (VBS_HOMEPAGE.A) in your mail traffic on 05/13/2001 12:42:08 with an action move.
Re: Homepage ===beware of virus......
Hello all in this mail there is an VBscript virus beware of that regards waheed From: Erich Eichinger [EMAIL PROTECTED] Reply-To: Orion-Interest [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Subject: Homepage Date: Sun, 13 May 2001 11:59:02 +0200 Hi! You've got to see this page! It's really cool ;O) homepage.HTML.vbs _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
RE: Homepage ===beware of virus......
Hi there! I'm so sorry for that. btw: i scanned the code of the virus - it's basically harmless. it just mails itself to all contacts in the outlook address-book. maybe a reason the change my mail-reader... sorry, erich -Original Message- From: waheed rahuman [mailto:[EMAIL PROTECTED]] Sent: Sonntag, 13. Mai 2001 12:51 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Homepage ===beware of virus.. Hello all in this mail there is an VBscript virus beware of that regards waheed From: Erich Eichinger [EMAIL PROTECTED] Reply-To: Orion-Interest [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Subject: Homepage Date: Sun, 13 May 2001 11:59:02 +0200 Hi! You've got to see this page! It's really cool ;O) homepage.HTML.vbs _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Antigen found VBS/SST.gen@MM (McAfee4,CA(InoculateIT)) virus
Antigen for Exchange found homepage.HTML.vbs infected with VBS/SST.gen@MM (McAfee4,CA(InoculateIT)) virus. The file is currently Removed. The message, Homepage, was sent from Erich Eichinger and was discovered in IMC Queues\Inbound located at Icon Medialab AB/ICONSE/SESTOMSX02.
WARNING!!!!!!! Re: Homepage
Hi everybody, please be careful, I'm not sure but I think the e-mail with subject homepage(the one I'm replying to) contains a virus. It is a vbs virus, and sends itself as far as I remember to everybody in your list. Hope you can read this e-mail before you read the mail with subject Homepage On Sun, May 13, 2001 at 11:59:02AM +0200, Erich Eichinger wrote: Hi! You've got to see this page! It's really cool ;O)
WARNING. You sent a potential virus or unauthorised code
The MessageLabs Virus Control Centre discovered a possible virus or unauthorised code (such as a joke program or trojan) in an email sent by you. Please read this whole email carefully. It explains what has happened to your email, which suspected virus has been caught, and what to do if you need help. Some details about the infected message To help identify the email: The message sender was [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] (if this is not your email address, the message sender possibly belongs to a mailing list to which you both subscribe.) The message was titled Homepage The message date was Sun, 13 May 2001 11:59:02 +0200 The message identifier was [EMAIL PROTECTED] The message recipients were [EMAIL PROTECTED] To help identify the virus: Scanner 1 (F-Secure) reported the following: F-Secure Anti-Virus for i386-linux Release 4.08 build 2260 sign.def version 2001-05-09 fsmacro.def version 2001-05-03 sign2.def version 2001-05-09 502975_2MA-OCTET-STREAM_homepage.HTML.vbs infection: VBS/VBSWG.X@mm 1 files scanned 1 infections found The message was diverted into the virus holding pen on mail server server-12.tower-4.starlabs.net (id 502975_989754952) and will be held for 30 days before being destroyed. What should you do now? If you sent the email from a corporate network, you should first contact your local Helpdesk or System Administrator for advice. They will be able to help you disinfect your workstation. If you sent the email from a personal or home account, you will need to disinfect your computer yourself. To do this you will need an anti-virus program. We suggest using one of the leading industry anti-virus packages such as McAfee, F-Secure or Cybersoft, which cost £15-£30 per copy. Getting more help We strongly recommend that you read the Support FAQs at http://www.messagelabs.com/support/FAQs.htm These will answer many of the most common queries. If you subscribe to the MessageLabs SkyScan AV Service, please contact your IT Helpdesk/Support department for further assistance. If you do not subscribe to the MessageLabs SkyScan AV Service please contact ISP4 Business on:- + 44 (0) 8707 001718 You may contact one of our Messaging Technicians at MessageLabs Helpdesk 7 days a week , 6am - 12pm on:- +44 (0)9067 579 001 All calls will be charged at £0.75p per minute. If you believe this message to be a false alarm, you can email ISP4 Business at:- [EMAIL PROTECTED] Please quote the following Virus Pen ID when contacting Support. If replying by email, please forward this entire email. _ This message has been checked for all known viruses by the MessageLabs Virus Scanning Service. For further information visit http://www.messagelabs.com/stats.asp
WARNING. You sent a potential virus or unauthorised code
The MessageLabs Virus Control Centre discovered a possible virus or unauthorised code (such as a joke program or trojan) in an email sent by you. Please read this whole email carefully. It explains what has happened to your email, which suspected virus has been caught, and what to do if you need help. Some details about the infected message To help identify the email: The message sender was [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] (if this is not your email address, the message sender possibly belongs to a mailing list to which you both subscribe.) The message was titled 'Homepage' The message date was Sun, 13 May 2001 11:59:02 +0200 The message identifier was [EMAIL PROTECTED] The message recipients were [EMAIL PROTECTED] To help identify the virus: Scanner 1 (F-Secure) reported the following: F-Secure Anti-Virus for i386-linux Release 4.08 build 2260 sign.def version 2001-05-09 fsmacro.def version 2001-05-03 sign2.def version 2001-05-09 588722_2MA-OCTET-STREAM_homepage.HTML.vbs infection: VBS/VBSWG.X@mm 1 files scanned 1 infections found The message was diverted into the virus holding pen on mail server server-37.tower-1.london-2.starlabs.net (id 588722_989755233) and will be held for 30 days before being destroyed. What should you do now? If you sent the email from a corporate network, you should first contact your local Helpdesk or System Administrator for advice. They will be able to help you disinfect your workstation. If you sent the email from a personal or home account, you will need to disinfect your computer yourself. To do this you will need an anti-virus program. We suggest using one of the leading industry anti-virus packages such as McAfee, F-Secure or Cybersoft, which cost £15-£30 per copy. Getting more help We strongly recommend that you read the Support FAQs at http://www.messagelabs.com/support/FAQs.htm These will answer many of the most common queries. If you subscribe to the MessageLabs SkyScan AV Service, please contact your IT Helpdesk/Support department for further assistance. If you do not subscribe to the MessageLabs SkyScan AV Service MessageLabs will only provide recommendations and information regarding viruses. You may contact one of our Messaging Technicians at MessageLabs Helpdesk 7 days a week , 6am - 12pm on:- +44 (0)9067 579 001 All calls will be charged at £0.75p per minute. If you believe this message to be a false alarm, you can email MessageLabs Support at:- [EMAIL PROTECTED] Please quote the following Virus Pen ID when contacting Support. mail server server-37.tower-1.london-2.starlabs.net (id 588722_989755233) If replying by email, please forward this entire email. _ This message has been checked for all known viruses by the MessageLabs Virus Scanning Service. For further information visit http://www.messagelabs.com/stats.asp
Antigen found VBS/SST.gen@MM (McAfee4) virus
Antigen for Exchange found homepage.HTML.vbs infected with VBS/SST.gen@MM (McAfee4) virus. The file is currently Removed. The message, Homepage, was sent from Erich Eichinger and was discovered in IMC Queues\Inbound located at journee/JOURNEEMAIL/GENESIS.
Re: WARNING!!!!!!! Re: Homepage
Am Sonntag, 13. Mai 2001 13:56 schrieben Sie: Hi everybody, please be careful, I'm not sure but I think the e-mail with subject homepage(the one I'm replying to) contains a virus. It is a vbs virus, and sends itself as far as I remember to everybody in your list. Hope you can read this e-mail before you read the mail with subject Homepage Take Unix/Linux/BSD and you have no problems :-) joerg
RE: Stateless bean and remove
I don't oversee exaclty what you would like to achieve, but I guess you can store your derived values as private properties of a --Stateless-- bean, perhaps using a sort of lazy calculation eg.: if ( property == null || property.needTobeRefreshed() ) property.recalculate() // some code follows which uses the property. The lifetime of the SLSBs is influenced by the settings in the orion-ejb-jar.xml file. If you use a application scope session bean (assuming you are using JSPs) you get your static SLSB. Forget about the SFSBs. You don't need them as you are not using conversational state in the true sense. Your calculated value does not depend on the state of the conversation between the client and the container. My 2cts, FE On Friday, May 11, 2001 11:17 PM, Ed Bras [SMTP:[EMAIL PROTECTED]] wrote: Hi Frank, I was wandering how I can control/influence the lifetime of my stateless bean, as I am storing some data in private variables to overcome large calculation times, so that the next time a web user requests the same data it's already there (after a fixed time I do refresh it if the same data is still stored in the private variable). So in a way I think I need a kind of static statefull session bean such that all clients have the same session bean. What are your ideas about this ? Eddie From: Frank Eggink [EMAIL PROTECTED] Reply-To: Orion-Interest [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Subject: RE: Stateless bean and remove Date: Fri, 11 May 2001 19:48:49 +0200 Nope, as a rule you will have a limited number of stateless session beans at anyone moment instantiated in your container, due to the nature of a stateless bean. The container can 'garbage collect' them. Guess it will do that after some time out. If you are seriously concerned about resource usage, my recommendation is not to tackle that in a ad hoc manner. Chapter 3 of Richard Monson-Haefels book: Enterprise Java Beans is a good reading to understand the difference between statefull and stateless and handles more stuff regarding resource usage. FE On Friday, May 11, 2001 12:47 PM, Joni Suominen [SMTP:[EMAIL PROTECTED]] wrote: Hi! This question should propably be asked in EJB-INTEREST mailing-list but I raise it here since I am not currently following it. So apologize me if you feel that this is a bit offtopic. The question is simple: Is it required to call the remove() method on stateless session bean after finishing using it or can the container automatically restore it to a pool (using Java garbage collection or DGC perhaps?)? For instance, the ATM example which ships with Orion don't use remove() after finishing the use of a stateless session bean instance. The same goes with Sun's Java Pet Store demo. On the other hand in Wrox Press's book Professional Java Server Programming, J2EE Edition they call remove() on stateless session beans. Currently I don't use remove() with stateless session beans. Should I? -- Joni [EMAIL PROTECTED] _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Re: Session Invalidate Exception
Thanks for your detailed explanation. Orion is really a great server the
only really missing thing is a document.
- Original Message -
From: elephantwalker [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Saturday, May 12, 2001 9:15 PM
Subject: RE: Session Invalidate Exception
Kesav,
In order to release memory, we need to make sure that we use enterprise
objects which are pooled by orion. As far as I know, these include
stateless session beans, entity beans and stateful session beans. Each of
these are recovered by the appserver as they fall out of context. Servlets
and jsp's are also pooled by the appserver. However, the servlet context
may
include objects which stay in memory...but not real memory. These object
should be serialized as the servlet time's out, or looses its session.
One of the ideas behind application servers in general, and j2ee
specifically is that we register our objects with the appserver, and the
appserver should handle recovery of any objects (and therefore, memory) as
necessary.
If orion needs the memory, it will recover the objects which aren't being
used, because they are part of a pool of objects.
Don't worry so much about the memory stuff, because those guys in Sweden
are
taking care of this for us.
Regards,
the elephantwalker
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Kesav Kumar
Sent: Saturday, May 12, 2001 4:58 PM
To: Orion-Interest
Subject: Re: Session Invalidate Exception
By invalidating session we generally think that all the memory will be
released but if invalidate doesn't actually release memore and make the
session object null then we need to have our own measures for releasing
the
memory. My concern is more for the memore rathar than the program error
handling.
- Original Message -
From: Noah Nordrum [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Saturday, May 12, 2001 1:31 PM
Subject: Re: Session Invalidate Exception
So have the page where the user enters their credentials wax their
session,
then the validation of the credentials page will create a new session.
why do you have to invalidate the session? why can't you just do:
===
HttpSession session = request.getSession();
Enumeration attributes = session.getAttributeNames();
while (attributes.hasMoreElements()) {
session.removeAttribute((String)attributes.nextElement());
}
===
Then you'll basically have a fresh session (except for a few
exceptions).
Noah
- Original Message -
From: Jeff Schnitzer [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Saturday, May 12, 2001 1:31 PM
Subject: RE: Session Invalidate Exception
I don't think that excludes the desired behavior, which is that you
should be able to invalidate a session and then create a new one.
It appears that session invalidate() is setting a flag in the session
object causing it to be cleaned up sometime later. Since the only way
to logout a user is to call invalidate(), this causes some headaches.
Ideally I would like my login submit page to a) discard existing
credentials and b) try new credentials. This way if a user was
already
logged in, the net result of a new login attempt will be the
unauthenticated state. Unfortunately I can't call
getSession().invalidate();
session = getSession();
because what I get is the old session, which is going to disappear at
the end of the method, the call to RoleManager.login()
notwithstanding.
Furthermore, a failed call to RoleManager.login() does *not* discard
existing credentials. The only way to accomplish the original goal is
to put the invalidate() on every page with a login form.
Ok, this isn't super critical, but it's annoying nevertheless.
Jeff
-Original Message-
From: Noah Nordrum [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 11, 2001 7:09 PM
To: Orion-Interest
Subject: Re: Session Invalidate Exception
Session Invalidate ExceptionServlet Spec
==
7.2 Creating a Session
Because HTTP is a request-response based protocol, a session
is considered
to be new until a client joins it. A client joins a session
when session
tracking information has been successfully returned to the
server indicating
that a session has been established. Until the client joins a
session, it
cannot be assumed that the next request from the client will
be recognized
as part of the session.
The session is considered to be new if either of the
following is true:
. The client does not yet know about the session
. The client chooses not to join a session. This implies that
the servlet
container has no mechanism by which to associate a
Re: WARNING!!!!!!! Re: Homepage
I use BSD, and have no problem, it is just a warning, you know many people use Windows and Outlook Express, and it is a little difficult to change habbits of Outlook people, at least I haven't been succesful On Sun, May 13, 2001 at 02:16:14PM +0200, Jörg-Thomas Krug wrote: Am Sonntag, 13. Mai 2001 13:56 schrieben Sie: Hi everybody, please be careful, I'm not sure but I think the e-mail with subject homepage(the one I'm replying to) contains a virus. It is a vbs virus, and sends itself as far as I remember to everybody in your list. Hope you can read this e-mail before you read the mail with subject Homepage Take Unix/Linux/BSD and you have no problems :-) joerg
RE: Session Invalidate Exception
From: Noah Nordrum [mailto:[EMAIL PROTECTED]]
So have the page where the user enters their credentials wax
their session,
then the validation of the credentials page will create a new session.
That was the solution I mentioned. It is undesirable for three reasons
I can think of; one, it requires a fix in the multiple locations where
there is a login page; two, not every page with login credentials should
cause this behavior (such as a hypothetical log in as someone else
page); three, it requires access to the session in the view.
The last one is the biggest problem, IMHO, because it violates the MVC
paradigm. Views shouldn't have code.
why do you have to invalidate the session? why can't you just do:
===
HttpSession session = request.getSession();
Enumeration attributes = session.getAttributeNames();
while (attributes.hasMoreElements()) {
session.removeAttribute((String)attributes.nextElement());
}
===
Then you'll basically have a fresh session (except for a few
exceptions).
I hadn't thought of that. I heard mention on this list some time ago
that Orion stores its security credentials in the user session. The
only problem is, I don't think there is any guarantee that J2EE app
servers store credentials in the session. That code isn't necessarily
going to work everywhere.
Of course, the RoleManager code isn't portable either, so it doesn't
really matter :-)
Thanks,
Jeff
Cocoon and Orion in Harmony?
Hello again folks of the list, I'm sure this must have been asked before although my searches on Deja and looking on both orionsupport.com and orionserver.com have come up pretty much empty. orionsupport.com has some documentation on the subject but I can't get the cocoon examples to run without getting an exception right at the start. I am very new to this subject matter and would appreciate any direction that can be given in this area. Thanks very much in advance for any help that can be provided. -- Holden Glova, [EMAIL PROTECTED] Software Engineer Alchemy Group Limited Level 6 Royal Sun Alliance Bldg PO Box 2386 Christchurch New Zealand Phone: +64 3 962-0396 Fax: +64 3 962-0388
Cocoon in Harmony with Orion?
Hello again folks of the list, I'm sure this must have been asked before although my searches on Deja and looking on both orionsupport.com and orionserver.com have come up pretty much empty. orionsupport.com has some documentation on the subject but I can't get the cocoon examples to run without getting an exception right at the start. I am very new to this subject matter and would appreciate any direction that can be given in this area. I'm using Orion 1.4.8 along with cocoon 1.8.2 Thanks very much in advance for any help that can be provided. -- Holden Glova, [EMAIL PROTECTED] Software Engineer Alchemy Group Limited Level 6 Royal Sun Alliance Bldg PO Box 2386 Christchurch New Zealand Phone: +64 3 962-0396 Fax: +64 3 962-0388
