Re: Unknown Source
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Orion never had classes open they always obfuscate the class files. You would never see the stack trace meaningful. Oc4j has proper classes so you can get proper stack trace. - - Original Message - From: Adam Cassar [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, April 16, 2002 2:51 PM Subject: Unknown Source Hi Guys, I am having a problem with v1.5.4 of Orion. In stack traces it displays the line number everywhere except for the EJB's! I know it used to work, any ideas on what to look for? -BEGIN PGP SIGNATURE- Version: PGPfreeware 7.0.3 for non-commercial use http://www.pgp.com iQA/AwUBPL0UwQFy+fQ1CDihEQKsTQCfdSFFA0FUBlsRW/3XY1zenXs8JuwAoKYT HyzRIZ/9kPEUwnon5SKvcaH9 =BaR1 -END PGP SIGNATURE-
RE: Unknown Source (2nd attempt)
Thanks! I'll give it a try. My concern is that this solution doesn't seem to be a J2EE solution, but more of a Orion specific one. On further thought towards my initial question, I wonder if there isn't a simpler solution, it seems to me that one should be able to reference the remote machine without any modifications to the config files. Something like this: Hashtable env = new Hashtable(5); env.put(Context.INITIAL_CONTEXT_FACTORY, com.evermind.server.ApplicationClientInitialContextFactory); env.put(Context.PROVIDER_URL, host); env.put(Context.SECURITY_PRINCIPAL, username); env.put(Context.SECURITY_CREDENTIALS, password); InitialContext ic = new InitialContext(env); Where host is any accessible machine that is running the ejb app in question, and is set up to handle the username and password sent. This code works fine if host is localhost, why not with a remote host? Eric. -Original Message- From: Jason Smith [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 26, 2001 6:02 AM To: Orion-Interest Subject: RE: Unknown Source (2nd attempt) Look in the archives for my post from April 3, 2001, entitled: Orion(web) - Orion(ejb) communication rough mini how to You must make sure that your EJB machine (referenced from your Web machine's rmi.xml) contains at least the same applications as the Web machine (see my Warning note in original post). -jaon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Knight Sent: Wednesday, April 25, 2001 2:42 PM To: Orion-Interest Subject: Unknown Source (2nd attempt) We have our project happily working with the web component and the ejb components living on a single machine. We'd now like to separate them, each on separate Orion boxes. We tried following some of the explanations on the Orion mailing list archive, but the ejb machine complains loudly about a NullPointerException - at ObjectInputStream.InputClassDescription (Unknown Source) when we start up the web machine. So it seems the client machine is trying to connect to the ejb machine but it's failing for some reason... We made the following settings on the client machine: in the orion-application.xml file for the web deployment we add the following line: ejb-module remote=true path=EJBCOMP / (EJBCOMP is the name of the ejb component) and this to the rmi.xml file: server host=n.n.n.n username=admin password=123/ where n.n.n.n is the machine with the ejb component. the username and password seem to be the default admin info in the principals.xml file. What are we missing? Are we supposed to register the client with the ejb host somehow besides a username and password? Thanks very much! --- Eric Knight Ninth House Network [EMAIL PROTECTED]
RE: Unknown Source (2nd attempt)
Look in the archives for my post from April 3, 2001, entitled: Orion(web) - Orion(ejb) communication rough mini how to You must make sure that your EJB machine (referenced from your Web machine's rmi.xml) contains at least the same applications as the Web machine (see my Warning note in original post). -jaon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Knight Sent: Wednesday, April 25, 2001 2:42 PM To: Orion-Interest Subject: Unknown Source (2nd attempt) We have our project happily working with the web component and the ejb components living on a single machine. We'd now like to separate them, each on separate Orion boxes. We tried following some of the explanations on the Orion mailing list archive, but the ejb machine complains loudly about a NullPointerException - at ObjectInputStream.InputClassDescription (Unknown Source) when we start up the web machine. So it seems the client machine is trying to connect to the ejb machine but it's failing for some reason... We made the following settings on the client machine: in the orion-application.xml file for the web deployment we add the following line: ejb-module remote=true path=EJBCOMP / (EJBCOMP is the name of the ejb component) and this to the rmi.xml file: server host=n.n.n.n username=admin password=123/ where n.n.n.n is the machine with the ejb component. the username and password seem to be the default admin info in the principals.xml file. What are we missing? Are we supposed to register the client with the ejb host somehow besides a username and password? Thanks very much! --- Eric Knight Ninth House Network [EMAIL PROTECTED]
RE: Unknown Source (2nd attempt)
The solution that I tried (see my post from yesterday: Orion JNDI using web-to-ejb and client-to-ejb) uses JNDI and orion's RMIInitialContextFactory. You may want to try that. At 12:32 4/26/2001 -0700, you wrote: Thanks! I'll give it a try. My concern is that this solution doesn't seem to be a J2EE solution, but more of a Orion specific one. On further thought towards my initial question, I wonder if there isn't a simpler solution, it seems to me that one should be able to reference the remote machine without any modifications to the config files. Something like this: Hashtable env = new Hashtable(5); env.put(Context.INITIAL_CONTEXT_FACTORY, com.evermind.server.ApplicationClientInitialContextFactory); env.put(Context.PROVIDER_URL, host); env.put(Context.SECURITY_PRINCIPAL, username); env.put(Context.SECURITY_CREDENTIALS, password); InitialContext ic = new InitialContext(env); Where host is any accessible machine that is running the ejb app in question, and is set up to handle the username and password sent. This code works fine if host is localhost, why not with a remote host? Eric. -Original Message- From: Jason Smith [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 26, 2001 6:02 AM To: Orion-Interest Subject: RE: Unknown Source (2nd attempt) Look in the archives for my post from April 3, 2001, entitled: Orion(web) - Orion(ejb) communication rough mini how to You must make sure that your EJB machine (referenced from your Web machine's rmi.xml) contains at least the same applications as the Web machine (see my Warning note in original post). -jaon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eric Knight Sent: Wednesday, April 25, 2001 2:42 PM To: Orion-Interest Subject: Unknown Source (2nd attempt) We have our project happily working with the web component and the ejb components living on a single machine. We'd now like to separate them, each on separate Orion boxes. We tried following some of the explanations on the Orion mailing list archive, but the ejb machine complains loudly about a NullPointerException - at ObjectInputStream.InputClassDescription (Unknown Source) when we start up the web machine. So it seems the client machine is trying to connect to the ejb machine but it's failing for some reason... We made the following settings on the client machine: in the orion-application.xml file for the web deployment we add the following line: ejb-module remote=true path=EJBCOMP / (EJBCOMP is the name of the ejb component) and this to the rmi.xml file: server host=n.n.n.n username=admin password=123/ where n.n.n.n is the machine with the ejb component. the username and password seem to be the default admin info in the principals.xml file. What are we missing? Are we supposed to register the client with the ejb host somehow besides a username and password? Thanks very much! --- Eric Knight Ninth House Network [EMAIL PROTECTED]