RE: Transaction problems

2001-07-13 Thread J Davis

We would also be interested in a solution to this problem as we have
encountered the same thing.  We are using 1.5.2 and Oracle 8.1.6 for our
situation.
We have also run into an issue where if you start a transaction and
inside hit a lot of different data/ejbs the Orion server maxes out it's
CURSOR allocation to oracle.  It creates a new connection and continues
on, but the error is thrown to the logs and can cause some code to skip
steps (due to catching the exception). We were assuming that since the
transaction was still open Orion was not closing any cursors to wait for
a commit, but we don't really know what is going on in the background.

Any ideas?

Greg


-Original Message-
From: Christian Bagnoli [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 6:00 AM
To: Orion-Interest
Subject: Transaction problems


Hi,

we're implementing an entity bean with transactional (container managed)
methods. This bean is accessed by
a session statefull bean. We have transactional problem when a method
fails
(that is throws an EJBException) because orion doesn't rollback the
transaction.
Does anybody figure out how to make orion rollback the transaction?
We have also tried with a session stateless/stateful having the same
problem
.
Also implementing the SessionSycronization interface doesn't trap the
transaction
boundaries.

Our data-source.xml is:

data-source
  class=com.evermind.sql.DriverManagerDataSource
  name=SetmoveDS
  location=jdbc/SetmoveDS
  xa-location=jdbc/xa/MySetmoveDS
  ejb-location=jdbc/myEJBDS
  connection-driver=oracle.jdbc.OracleDriver
  username=test
  password=test
  url=jdbc:oracle:thin:test/test@testsun:1521:test
  inactivity-timeout=30
 /

we use orion 1.5.2.

the ejb-jar.xml is:
.
 session
   display-nameLogEntJAR/display-name
   descriptionLogEntJAR/description
   ejb-nameMyLogEnt/ejb-name
   homesetmove.beans.logica.LogEntHome/home
   remotesetmove.beans.logica.LogEnt/remote
   ejb-classsetmove.beans.logica.LogEntEJB/ejb-class
   session-typeStateful/session-type
   transaction-typeContainer/transaction-type
   ejb-ref
ejb-ref-nameMyEntUtente/ejb-ref-name
ejb-ref-typeEntity/ejb-ref-type
homesetmove.beans.logica.EntUtenteHome/home
remotesetmove.beans.logica.EntUtente/remote
   /ejb-ref
  /session
.
  entity
   display-nameEntUtenteJAR/display-name
   descriptionEntUtenteJAR/description
   ejb-nameMyEntUtente/ejb-name
   homesetmove.beans.logica.EntUtenteHome/home
   remotesetmove.beans.logica.EntUtente/remote
   ejb-classsetmove.beans.logica.EntUtenteEJB/ejb-class
   persistence-typeBean/persistence-type
   prim-key-classjava.lang.String/prim-key-class
   reentrantfalse/reentrant
   resource-ref
descriptiondescription/description
res-ref-namejdbc/SetmoveDS/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
   /resource-ref
  /entity
.
container-transaction
method
ejb-nameLogEntEJB/ejb-name
method-name*/method-name
   /method
   method
ejb-nameEntUtenteEJB/ejb-name
method-name*/method-name
   /method
  /container-transaction

thanks a lot.

Christian








RE: Customizing CMP deployment

2001-03-12 Thread J Davis

Once the application-deployment directory is created update the
orion-ejb-jar.xml and change the Table tag.

entity-deployment name="BeanName" location="BeanName"
wrapper="BeanNameHome_EntityHomeWrapper2" table="New-Table-Name-Here"
data-source="jdbc/yourDataSource"


Later...

Greg
-Original Message-
From: Sergei Batiuk [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 8:51 AM
To: Orion-Interest
Subject: Customizing CMP deployment


Is there any way to customize deployment of CMP bean - to indicate the
table
name in the database to which the entity bean should map its persistence
(in
case the name of the table is different from the bean name) or the data
source to connect to. As far as I know orion-ejb-jar.xml is responsible
for
these properties, but it has no effect ibefore/i the deployment. Is
there an orion-specific (or some other) way to deliver such information
to
the container?








RE: Applet BEAN JNDI Errors

2001-03-06 Thread J Davis

Did you ever get a fix to this?  We seem to be getting a similar error
trying to get an InitialContext from an object when load testing.
Unfortunately it is not consistently happening to where we have been able to
track the problem down.

Any ideas? 

-Original Message-
From: John McManus [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 21, 2001 3:59 PM
To: Orion-Interest
Subject: Applet BEAN JNDI Errors


Make it stop :(

I'm getting the following error trying when I do a new
InitialContext(env) in my applet.
After fighting thru security issues and whatnot, I not have the
following error:

Opening
http://traveller.pc.peakss.com:8000/cems-primer/com/evermind/server/administ
ration/ApplicationServerAdminstrator.class

Connecting
http://traveller.pc.peakss.com:8000/cems-primer/com/evermind/server/administ
ration/ApplicationServerAdminstrator.class
with no proxy

*** Error in my applet follows *

javax.naming.NamingException: Error reading application-client
descriptor: Error looking up EJBHome: Lookup error:
java.io.StreamCorruptedException: Caught EOFException while reading the
stream header; nested exception is:
java.io.StreamCorruptedException: Caught EOFException while reading the
stream header

at
com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext
(JAX)

at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)

at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)

at javax.naming.InitialContext.init(Unknown Source)

at javax.naming.InitialContext.init(Unknown Source)

at TestApplet2.jButton1_actionPerformed(TestApplet2 *Notice* that the
class ApplicationServerAdminstriator.class is *misspelled*
In my application log I get a 404 (not found) when I try to do a get of
the class that *SHOULD*
be:

com.evermind.server.administrator.ApplicationServerAdministrator NOT
com.evermind.server.administrator.ApplicationServerAdminstrator (missing
an I??)

Is this what's causing the NamingException and why I can't find the
bean?  It appears to be deoplyed correctly if I use the console to see
my application.

*Does anyone have an applet calling a bean via jndi that works with
orion?*  I've been working on this for 1 week and have been fighting
thru various errors.

Ag The pain the pain.

Thanks for any help in advance.


--
***
  |^^|
  |  |
  |  _  _| John B McManus
  | (.)(.) email: [EMAIL PROTECTED]
  @  _)phone: (303)734-6002
   | ,___|
   |   /

***


--
***
  |^^|
  |  |
  |  _  _| John B McManus
  | (.)(.) email: [EMAIL PROTECTED]
  @  _)phone: (303)734-6002
   | ,___|
   |   /








RE: More than one InitialContext

2000-12-15 Thread J Davis

Can you cast some votes on 215/216 in buzilla, it may help fix this bug
faster.

-Original Message-
From: Peter van Rensburg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 14, 2000 10:21 AM
To: Orion-Interest
Cc: 'Karl Avedal' (E-mail)
Subject: RE: More than one InitialContext


Hi

I have noticed a similiar issue. We have two frontend corba servers
communicating with a virtual application server. Latter is two orion servers
behind two Foundry Layer4/7 switches running symmetric load balancing. When
one application server goes down the switches moves future connections to
the remaining server. The corba servers sets up the InitialContext everytime
it speaks to the application servers. Depending in which stage the
connection were, a NamingException is thrown or the communication continues
after a brief pause (during switch over). When the corba servers do receive
a NamingException, it will continue communicating with the remaining
application server but locks up inside the InitialContext constructor
moments after that. It would appear that this constructor sets up the actual
connection to the application server or keep the persistent connection open.
A NullPointerException as outlined in Greg's mail below, is thrown when
trying to close the context (aka connection).
Even using the undocumented optioned dedicated.connection="true" one still
cannot call the close() method on the context. Has this method been
implemented at all? Using this option however causes the VM to run out of
memory eventually.

Karl, Greg, has any progress been made here? Any ideas as to what exactly is
wrong here?

Regards,
Peter van Rensburg

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of J Davis
 Sent: 12 December 2000 09:53
 To: Orion-Interest
 Cc: 'Karl Avedal' (E-mail)
 Subject: RE: More than one InitialContext


 It looks like this is a bug if coming from a client-application.  It seems
 if you create a initial context within the same instance of a class, and
 then close and try to re-open another InitialContext it will
 fail. I tested
 this again today making my test class runnable and spawning three
 instances
 of it off into three threads.  This works fine, but if you attempt to make
 the same instance of one of the threads call InitialCOntext twice(after
 closing and setting it to null just in case) it throws the
 NullPointerException. I am currently in conversation with Karl about this.
 It has been reported as bug #210,215,  216.  Hopefully this will get
 resolved soon.  Curruently it is forcing us to look at other servers as a
 fallback plan until this can be fixed.

 Later

 Greg


 -Original Message-
 From: Guilherme Ceschiatti [mailto:[EMAIL PROTECTED]]
 Sent: Sunday, December 03, 2000 9:12 AM
 To: Orion-Interest
 Subject: More than one InitialContext


 Hi.

 I'd like to konw if it's possible to have more than on
 InitialContext in the

 same app, one for each app server I have.

 --

 []s
 Guilherme Ceschiatti
 http://listando.net
 [EMAIL PROTECTED]










RE: More than one InitialContext

2000-12-12 Thread J Davis

It looks like this is a bug if coming from a client-application.  It seems
if you create a initial context within the same instance of a class, and
then close and try to re-open another InitialContext it will fail. I tested
this again today making my test class runnable and spawning three instances
of it off into three threads.  This works fine, but if you attempt to make
the same instance of one of the threads call InitialCOntext twice(after
closing and setting it to null just in case) it throws the
NullPointerException. I am currently in conversation with Karl about this.
It has been reported as bug #210,215,  216.  Hopefully this will get
resolved soon.  Curruently it is forcing us to look at other servers as a
fallback plan until this can be fixed.

Later

Greg


-Original Message-
From: Guilherme Ceschiatti [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 03, 2000 9:12 AM
To: Orion-Interest
Subject: More than one InitialContext


Hi.

I'd like to konw if it's possible to have more than on InitialContext in the

same app, one for each app server I have.

-- 

[]s
Guilherme Ceschiatti
http://listando.net
[EMAIL PROTECTED]






RE: OR mapping with Oracle

2000-12-01 Thread J Davis

I beleive primary keys must be Serializalble.  Try using an Integer object
instead.

Later 

Greg

-Original Message-
From: Hegyi Tibor [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 01, 2000 2:47 AM
To: Orion-Interest
Subject: OR mapping with Oracle


Hi guys, 

Coupld you please help with teh below problem? I haven't found any solution
yet.

I am using Orion 1.3.8, Oracle 8.1.5.
I want to use a Compound object as a primary key to my CMP Entity Bean.
This PK class has one public member key of int datatype.

The PK class:
public class ProductPK implements java.io.Serializable {
  public int key;   //this should be mapped to a column in the Oracle
bean table
  public ProductPK(int key) {
this.key=key;
  }
}

I edited orion-ejb-jar.xml to map the primary key field (this is necessary I
think, because Oracle maps Serializable objects to blobs that cannot be part
of primary keys):

primkey-mapping
cmp-field-mapping name="key"
fields
cmp-field-mapping name="key" persistence-name="key" /
/fields
/cmp-field-mapping
/primkey-mapping

The error message I always got:

Auto-deploying beantest-ejb.jar (orion-ejb-jar.xml had been updated since
the previous deployment)... ProductRemote_EntityBeanWrapper0.java:781:
Incompatible type for method. Can't convert beantest.ejb.ProductPK to int.
statement.setInt(4, object.key);
  ^
ProductHome_EntityHomeWrapper7.java:388: Incompatible type for method. Can't
convert beantest.ejb.ProductPK to int.
statement.setInt(4, response.object.key);
   ^
2 errors
Error compiling file:/E:/Java/BeanTest/build/beantest/beantest-ejb.jar:
Syntax error in source

I've already looked at OrionSupport and the mailing list archive, but found
no solution ti this problem.

Any idea would be gratefully appreciated!

Tibor







RE: how do i deploy ear

2000-11-30 Thread J Davis



Try 
using the absolute pasth in the server.xml's path=""(i.e. 
path="c:/myDir/B2B.ear" or path="/test/B2B.ear"

See if 
that helps.

Later...

Greg

  -Original Message-From: umesh sonavane 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, November 30, 2000 12:59 
  AMTo: Orion-InterestSubject: how do i deploy 
  ear
  Hi everyBody
  
  Ihave already created an B2B.ear file now i 
  want to deploytool it into orion server how do i do that
  
  in server.xml i have this
   
  application name = 
  "B2B" 
  path="B2B.ear" /
  
  and in default-web-site.xml i have 
  this
  
   web-app 
  application="B2B" name="war-ic.war" 
  root="tmib2b" /
  when i start the server its gives me following 
  error 
  
  C:\orionjava -jar orion.jarError 
  instantiating application at file:/C:/orion/config/B2B.ear: Unable to 
  find/read assembly info for C:\orion\config\B2B 
  (META-INF/application.xml)Orion/1.3.8 initialized
  
  
  can anybody tell me how to deploy when i have 
  already made a ear file and want to deploy it in orion server
  
  Umesh 
Sonavane


URGENT!!!:Problems using RMI to the Orion Server.

2000-11-21 Thread J Davis

I am Re-posting This with an Urgent call because I have not heard anything
and this is an important issue that will decide wether or not we can use the
Orion server in prodUction.  We updated to 1.4.0 to see if that would fix
the problem but it still exists.  The connection never leaves the
ESTABLISHED state unlse the JRUN server shuts down killing the VM it's
running in.

Unfortunately I can't seem to get the autoupdate to work because our proxy
requires a login  password to get out.  Does anyone know how to set the
proxy login and password at the comman line, or ia orion supposed to ask it
from me when autoupdate runs?

Thanx

Greg
-Original Message-
From: J Davis [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 16, 2000 10:28 AM
To: Orion-Interest
Subject: Problems using RMI to the Orion Server.


We seem to be having a problem with RMI connection.  Unfortunately we have
some software here(B2B application called Netfish) that only runs on JRUN
2.3.3 or I-Planet.  This is running on a Sun box running Solaris 2.8.
  
It has a Java object that acts as a workflow and connects to out Orion 1.3.8
EJB server(Running on Win2K on a PC Server) to get an EJB. When it calls
InitialContext() the first time it works great.  The object does it's job,
closes the context and goes away.  The next time the workflow is called it
gets a socket exception because the socket is still set as CONNECTED instead
of TIMEWAIT on the server with Netfish.  If the same call is done or JRUN
3.0 or BEA's Weblogic server it puts the socket connection back to TIMEWAIT
after the call and it works fine. 

We never had a problem with our standalone apps or the web server and I
think that was due to the application closing when it was done.  But the
JRUN server stays up so the socket is not automaticaly set to TIME-WAIT by
the system.  Is this a capability of Orion to leave the connection locked,
and thus do we need to add some code to clode it in a better way than
context.close()?  Or is this a bug that has already been addressed and fixed
in future versions, and if so is there a planned date for a newer stable
release than 1.3.8? 

Unfortunately this had really got our Management in a tizzy over the whole
thing and now they don't want to purchase a license until we figure it out
so I can't really gat any infor from the support guys.

Any help here would be great


Thanx

Greg







Problems using RMI to the Orion Server.

2000-11-16 Thread J Davis

We seem to be having a problem with RMI connection.  Unfortunately we have
some software here(B2B application called Netfish) that only runs on JRUN
2.3.3 or I-Planet.  This is running on a Sun box running Solaris 2.8.
  
It has a Java object that acts as a workflow and connects to out Orion 1.3.8
EJB server(Running on Win2K on a PC Server) to get an EJB. When it calls
InitialContext() the first time it works great.  The object does it's job,
closes the context and goes away.  The next time the workflow is called it
gets a socket exception because the socket is still set as CONNECTED instead
of TIMEWAIT on the server with Netfish.  If the same call is done or JRUN
3.0 or BEA's Weblogic server it puts the socket connection back to TIMEWAIT
after the call and it works fine. 

We never had a problem with our standalone apps or the web server and I
think that was due to the application closing when it was done.  But the
JRUN server stays up so the socket is not automaticaly set to TIME-WAIT by
the system.  Is this a capability of Orion to leave the connection locked,
and thus do we need to add some code to clode it in a better way than
context.close()?  Or is this a bug that has already been addressed and fixed
in future versions, and if so is there a planned date for a newer stable
release than 1.3.8? 

Unfortunately this had really got our Management in a tizzy over the whole
thing and now they don't want to purchase a license until we figure it out
so I can't really gat any infor from the support guys.

Any help here would be great


Thanx

Greg





RE: HIGH PRIORITY:Contact Information??????

2000-10-31 Thread J Davis

Actaully we did that, about 5 times with no reply.   That is what was most
annoying

Thanx to everyone else for the other e-mail addresses



-Original Message-
From: Kemp Randy-W18971 [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 7:36 AM
To: Orion-Interest
Subject: RE: HIGH PRIORITY:Contact Information??


I would send another email to sales and one to support.  It's possible
someone just skipped reading the email.  Just be sure the subject heading
says something like READY TO PAY CASH. 

-Original Message-
From: Russ White [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 31, 2000 6:31 AM
To: Orion-Interest
Subject: RE: HIGH PRIORITY:Contact Information??


IMHO
If they have not been getting back to you...

Deploy now. License later.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of J Davis
 Sent: Monday, October 30, 2000 7:58 PM
 To: Orion-Interest
 Subject: HIGH PRIORITY:Contact Information??
 
 
 Does anyone have any contact information for Orion.  We have been trying
to
 contact them for over two weeks about purchasing and licenses, and no one
 has gotten back to us.  The seem to only have an E-mail address for sales
on
 their site and we cannot find any sort of phone number or other e-mail
that
 will work.  Any help here would be greatly appreciated.  Orion has been by
 far the fastest, smoothest EJB server we have found for it's cost and we
 want to purchase it.  Unfortuanately if we cannot get a hold of anyone we
 will have to take our business elsewhere.
 
 
 Thanx
 
 
 Greg
 
 
 






HIGH PRIORITY:Contact Information??????

2000-10-30 Thread J Davis

Does anyone have any contact information for Orion.  We have been trying to
contact them for over two weeks about purchasing and licenses, and no one
has gotten back to us.  The seem to only have an E-mail address for sales on
their site and we cannot find any sort of phone number or other e-mail that
will work.  Any help here would be greatly appreciated.  Orion has been by
far the fastest, smoothest EJB server we have found for it's cost and we
want to purchase it.  Unfortuanately if we cannot get a hold of anyone we
will have to take our business elsewhere.


Thanx


Greg





RE: Can't call an EJB from Within another EJB

2000-10-26 Thread J Davis

It was the EJB-REF Tag.  I missed that the first time through the docs.
Thankx goes to Jim and Sven!

Greg

-Original Message-
From: Jim Archer [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 26, 2000 12:16 AM
To: Orion-Interest
Cc: J Davis
Subject: Re: Can't call an EJB from Within another EJB


Remember that your EJB-REF tage are scoped within each bean, so that the 
same tag name can refer to different things, depending upon which bean it 
is defined in. So, my guess is that you didn't include an EJB-REF tag *in 
the bean definition* for the bean you want to reference.

If thats not the problem, post your deployment descriptor for us to look at.

Jim


--On Wednesday, October 25, 2000 11:21 AM -0600 J Davis 
[EMAIL PROTECTED] wrote:

 We have gotten our Orion server(1.3.8) to work with EJBs on a singular
 level(i.e. we can call EJB A, B or C and it works fine.)  But If one of
 our EJB's tries to call another(i.e. A calls B)  A throws a naming
 exception that it can't find the EJB reference when doing a jndi lookup.
 Is there a dependency tag or something within one of the XML files that
 denotes EJB dependencies on one another?  I'm sure this is something
 simple, but it is getting annoying.













Can't call an EJB from Within another EJB

2000-10-25 Thread J Davis

We have gotten our Orion server(1.3.8) to work with EJBs on a singular
level(i.e. we can call EJB A, B or C and it works fine.)  But If one of our
EJB's tries to call another(i.e. A calls B)  A throws a naming exception
that it can't find the EJB reference when doing a jndi lookup.  Is there a
dependency tag or something within one of the XML files that denotes EJB
dependencies on one another?  I'm sure this is something simple, but it is
getting annoying.







RE: Ok. I feel dumb. Data Sources and MS SQL.

2000-10-25 Thread J Davis

I checked it out on our machines and the Data source below works like a
champ for me.  I am using Win2K Advanced server and SQLServer 7.  Just make
sure your ODBC dirver is setup correctly.

Later...

Greg

-Original Message-
From: Kurt Hoyt [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 25, 2000 7:06 AM
To: Orion-Interest
Subject: RE: Ok. I feel dumb. Data Sources and MS SQL.


I hate to be the bearer of bad news, but you'll have to spring for a type 4
JDBC driver. We bought the one from Inet Software called "Sprinta 2000". The
price was reasonable and it performs comparably with the best of them.
That's how we got Orion and SQL Server 7 and Win2K to work together.

Kurt in Atlanta

-Original Message-
From: Kimberley Scott [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 24, 2000 9:16 PM
To: Orion-Interest
Subject: Ok. I feel dumb. Data Sources and MS SQL.


Hiya,

Feeling real stupid here. I'm examining data sources and getting totally
confused. Maybe I'm just burnt out. Haven't had a holiday in five years.
Sigh.

Back to business. We're *forced* to use Microsoft SQL 7 and Win2K. How do I
set up the datasource xml file to handle this? I can't seem to find anything
on this in the email lists on in the docs. The only drivers I have are the
ODBC bridges (The invisible hidden MS one and the standard Sun one) and I'm
not paying for a Type IV driver at the outrageous prices I've been presented
with from BEA and the like. Has anyone done this before or can point me in
the right direction?

A tired developer who's feeling very old and dim...

Kimberley Scott
Senior Web Developer
Peakhour Pty Ltd
http://smartoffice.com.au - just built. needs work. ASP/COM Sigh. What can
I say?
http://peakhour.com.au - corporate site
http://www.geocities.com/kimmie_scott -me








RE: EJB Problem

2000-10-23 Thread J Davis

I have looked into it further and thought it was a missing ejb-link tag in
web.xml to no avail.  I have noticed that the ejb-ref-mapping tags are
being created by Orion when it deploys the web application in the
orion-web.xml file.  This is a very bizarre problem for me. Here is the
error from the std-out.log:
javax.naming.NameNotFoundException: ProfileEntity not found
at com.evermind.server.rmi.RMIContext.lookup(JAX)
at com.evermind.server.hi.f_(JAX)
at com.evermind.server.hi.lookup(JAX)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at
com.micronpc.api.configurator.ActiveModelBean.init(ActiveModelBean.java:16
9)
at
com.micronpc.api.configurator.ActiveModelBean.init(ActiveModelBean.java:11
5)
at
com.micronpc.api.configurator.ActiveModelBean.init(ActiveModelBean.java:93
)
at
com.micronpc.api.configurator.ConfigRequestXmlHandler.extractConfigRequest(C
onfigRequestXmlHandler.java:127)
at
com.micronpc.api.configurator.ConfigRequestXmlHandler.getActiveModel(ConfigR
equestXmlHandler.java:59)
at ModelHTML.setXmlFileName(ModelHTML.java:278)
at
__jspPage2_VND_RSEntry_configurator_jsp._jspService(__jspPage2_VND_RSEntry_c
onfigurator_jsp.java:41)
at com.orionserver.http.OrionHttpJspPage.service(JAX)
at com.evermind.server.http.HttpApplication.w5(JAX)
at com.evermind.server.http.JSPServlet.service(JAX)
at com.evermind.server.http.d1.si(JAX)
at com.evermind.server.http.d1.forward(JAX)
at com.evermind.server.http.ed.sp(JAX)
at com.evermind.server.http.ed.so(JAX)
at com.evermind.util.f.run(JAX)

Here is what the orion-web.xml looks like:
?xml version="1.0"? !DOCTYPE orion-web-app PUBLIC "-//Evermind//DTD Orion
Web Application 2.3//EN" "http://www.orionserver.com/dtds/orion-web.dtd"
orion-web-app
deployment-version="1.3.8"
development="true"
jsp-cache-directory="./persistence"
temporary-directory="./temp"
servlet-webdir="/servlet/"
   session-tracking /
ejb-ref-mapping name="QuoteEntity" /  
ejb-ref-mapping name="ModelQuoteEntity" / 
ejb-ref-mapping name="ProfileEntity" /
ejb-ref-mapping name="ConfiguratorSession" /  
ejb-ref-mapping name="B2BLookupEntity" / 
/orion-web-app 

My ActiveModelBean has a main that works fine from a remote machine or from
the server on the command line.  All it does is call the constructor which
creates/loads 3 entity beans.  On the web server I have a
Servlet(ConfigRequestXmlHandler) that tries to construct the object.  It
creates the context within the object fine, but as soon as I try to fetch
the first interface it throws the error. 

Any ideas?

Greg


-Original Message-
From: J Davis [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 23, 2000 5:10 PM
To: Orion-Interest
Subject: EJB Problem


I am having a problem that is probably really simple but I can't seem to
figure it out.  I have deployed some EJBs on the server and I can connect to
them fine from a remote application using the jndi.properties and
application-client.xml file.  But when I try to hit the EJBs from the same
bean within a servlet on the same server it throws a namingException saying
it can't find my EJB in the namespace.  I ensured the ejb-ref tags were in
the web.xml file in WEB-INF of the web space. Is there any other place I
need to reference the ejbs for the web-server side of orion?

Thanx,

Greg