Hello John:
In first place I want to thank you for your quick answer and your interest,
also i want to beg your pardon for a mistake in the original mail, just in
the most important place in the mail, when i say you the returned exception
text, the correct expression returned is:
javax.naming.CommunicationException: Unknown service: 10.168.18.33:2481:orcl
We've tried to test the example you told me but couldn't pass the deployment
operation, there is an error in the deployejb execution that appears very
difficult to resolve.
Just like you are very interested in this, i'm going to detail you the
problem:
For testing we have three different components:
1. An EJB called TestAlfa that is deployed in the /test environment with
system schema.
2. An EJB called TestBravo in the same way.
3. A client side with three main functions: One for test the TestAlfa EJB
directly, another one for test the TestBravo EJB directly and another one
that calls a special function in the TestAlfa bean in order to access the
TestBravo bean through the TestAlfa bean.
Results:
We have no problem in deploying all EJBs.
Both client main functions that access to each EJB directly works properly.
The main function that access the Beta through Alfa returns the error shown
(if we catch the exception "javax.naming.NamingException" no error is
returned but neither any value from the method).
There is another component in our environment, is an EJB that access to an
LDAP directory service, if the code portion for access is in an isolated
java file it works but inside a bean doesn't work.
We have been thinking about the problem and we have some ideas. Can you tell
what could be the right?
1. All the examples in the documentation uses the scott schema and we're
using system schema.
2. We've seen that all classes in Oracle8i are in the sys schema and not in
the system, so we have tried to include these in the deployment profile.
3. The problem for access an EJB from another may be similar with the
problem for access an LDAP from an EJB, maybe a problem with general classes
deployment?
I can send you the source code for all the testing workspace.
Thank you very much.
Carlos.
-----Mensaje original-----
De: John O'Duinn <[EMAIL PROTECTED]>
Para: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Fecha: s�bado 30 de octubre de 1999 2:11
Asunto: Re: Communication between EJB's in Oracle8i
>>hi;
>>
>>Just from a quick glance at the error, it looks like you have a syntax
>>error in your connect string and are missing the port number on the
server,
>>which would lead to this sortof error. It should be in the format of
>><machinename>:<portnum>:<sid>. Its even possible to have
>><machinename>:<portnum> in certain cases. But omitting the portnum will
not
>>work.
>>
>>Have you tried running the
>>$ORACLE_HOME/javavm/demo/examples/ejb/session/clientserverserver on your
>>installation? All those samples are all configured to work on a typical
>>installation, and that particular one "clientserverserver" shows you an
EJB
>>calling another EJB on the same server. If that sample doesnt work, then
>>something is wrong with your installation.
>>
>>If that sample does work, then your installation is ok. If your program
>>still fails, and you cant spot the difference, let me know, ok?
>>
>>take care
>>John.
>>=====
>>At 02:01 AM 10/29/99 , you wrote:
>>>Hello:
>>>
>>>I've problems when i try to communicate two differents EJB's in Oracle 8i
>>>deployed in the same machine, it returns me the exception:
>>>
>>>javax.naming.CommunicationException: Unknown service: 10.168.18.33:orcl
>>>
>>>If i try to catch the exception it returns me no error but is not able to
>>>call any method in the EJB.
>>>The communication between a client application and an EJB goes good.
>>>People form Oracle answered me that there must be an error in my DNS, but
>>>this can't be the problem because the three components of my testing
>>>environment are running in the same machine and the client application
>finds
>>>the first EJB without any problem and i've test in the URL direction for
>the
>>>lookup method the name of the machine, the IP direction, the localhost
>>>expresion and the IP 127.0.0.1 and it doesn't work.
>>>I've also tested the 'thisServer' option in the URL but if i change the
>>>second EJB location (in a different server) neither it works.
>>>
>>>Thanks a million!!!
>>>
>>>PS1: I can send you the source code to review it.
>>>
>>>PS2: Somebody in this forum (from Oracle) told me that i should ask this
>>>kind of questions in an Oracle forum, well, we're Oracle partners and
this
>>>question has been inserted in two different Oracle forums and their
>answers
>>>were not correctly answered, by this, i'm asking you.
>>>
>>>=========================================================================
=
>=
>>>To unsubscribe, send email to [EMAIL PROTECTED] and include in the
>body
>>>of the message "signoff EJB-INTEREST". For general help, send email to
>>>[EMAIL PROTECTED] and include in the body of the message "help".
>>>
>>
>>
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
