Actually, I do not mind getting a lot of e-mails from something I really
care about. I would like to know what the outcome of these problems are. I
am having similar crashes except on Windows NT. Sometimes, during the
deployment I get a crash (Dr. Watson). Other times, the deployment
proceeds, but Orion just exists. I just start a few times, and it seems to
get past these troubles. So you see, I too am interested in the outcome.
If someone does not want to be innundated with e-mails, then they can setup
a filter, and move the e-mails in to a different folder when e-mails arrive
(that's what I do). Others, might choose to unsubscribe and use the WWW
access to the list archive to search. What ever the reason is, these
e-mails is all we have in terms of "latest documentation".
I hope that everyone continues to reply to the list, so that we can
collectively research the problems and know the answers before getting
stuck.
-AP_
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Karl Avedal
Sent: Thursday, April 06, 2000 10:41 AM
To: Orion-Interest
Cc: Orion-Interest
Subject: Re: Fatal problem with Orion and EJB
Hello Paolo,
What you see is, as you say, a JVM crash. Since Orion is written in pure
java, a JVM crash is always caused by a bug in the JVM. Sun has had alot
of trouble in getting 1.2 stable on Solaris and we try to work around
their bugs as much as possible, but in some cases it can be pretty
difficult since their Solaris jvm can crash on very common code.
What Orion version and JDK version are you using? (the Solaris JDK:s
have more version information than just 1.2.2)
And please do not reply with this information to the list, it's getting
very flooded and we are trying to limit the traffic on the list.
Thank you
Regards,
Karl Avedal
[EMAIL PROTECTED] wrote:
> Hi,
>
> I have tried to run EJB Orion demo. As claims the doc I have
> added to config/server.xml the line
>
> <application name="ejbsamples" path="../demo/ejb" />
>
> When I try to start OrionServer the JVM crashs
>
> SIGSEGV 11* segmentation violation
> si_signo [11]: SIGSEGV 11* segmentation violation
>
> Segmentation Fault (core dumped)
>
> My platform is Solaris 7 intel, Sun jdk 1.2.2
>
> Anyone have experimented in the same way ?
>
> Paolo Sommaruga
>
> Garda Access
> Garda (Vr), Italy
> http://www.garda-access.com/
>
>
>
