Undeliverable:
Important information! This e-mail has not been delivered to [EMAIL PROTECTED] The receiver's mailbox is full. When the mailbox has been emptied you will be able to resend this e-mail. Best regards Telia Internet
RMI Clustering HOW-TO.
OKAY. Here it goes. Prerequisites. (tested on 1.5.2 problems on 1.4.5) A. Setting up the cluster. A.1. RMI.XML: A.1.1 EXPLICITLYbind to the machine's IP rmi-server host="machine_ip_or_adress" A.1.2SAME cluster configuration on all machines cluster username="clusteruser" password="clusterpass"/ If you want you can use a nonstandard MCast IP and Port, but it HAS TO BE the same for all machines A.2. Application set-up. One and the same Application name for the clustered app. Like this in server.xml (on all machines): application name="Cluster" path="../applications/Cluster" / Deployment source doesn't count. The NAME HAS TO BE THE SAME. B. Tips for correct working. B.1. This is NOT full cluster: B.1.1An EJB is searched on othe machines if it is not present on the current one. If Machine A has bean BeanA any other bean, trying to access BeanA will be used from this machine only. B.1.2 Once you get a reference to a bean you will not get a reference to the same bean on another machine. If Machine A does not have BeanA and wants to use it, it will look it up on the cluster and use the LAST ONE, that has been found (i.e if MachineC has been the last to boot-up and has BeanA, then machine A will use the bean from Machine C. B.1.P.S.I hope this will be fixed soon. B.2. Deploy your entity beans in one place only. Do so with your stateful session beans also. C. Additional info. C.1 JMS. One can use the JMS server on one machine. This way anyone lookingfor a QUEUE or TOPIC will find it on that one. EX. in jms.xml: queue-connection-factory host="192.168.2.111" port="9129" username="admin" password="123" location="jms/QueueConnectionFactory" / topic-connection-factory host="192.168.2.111" port="9129" username="admin" password="123" location="jms/TopicConnectionFactory" / TRADE OFF: When the JMS server machine shuts down and boots up. Every other machine has to be restarted in order to reregister the QUEUE and TOPIC clients. PLUSES: MDBs are synchronized. Keep in mind the JMS technology a TOPIC message is received on all machines. A QUEUE message is received by only one. However that means, that in most cases (but not always) the QUEUE message will be received by one and the same client. P.S. There is still quite some job to be done on the clustering, but for now this is more than nothing. Personally I'll have to create my own execution scheduler, that will be responsible for round-robin execution of my clustered SLSBs. Well... Not much, but at least works :( Lachezar
Re: spam?
hahahhahaaa - sounds like someone simply replied to the wrong message =) Boris Garbuzov wrote: Guys, what is happening? Too many strange messages. -- Kevin Duffey wrote: Hi Melissa, I didn't get the size for him. To be honest..I cam was working on content and part of my front-end framework the last few times. I will figure this out soon for him and let him know. Next weekend is bad for me to meet too..got two graduations and a special mothers-day/fathers-day dinner for my parents who are in from Florida. But sometime during the week, especially Wednesday night or Thursday would be fine. Site is up. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Scot Weber Sent: Thursday, June 14, 2001 5:27 PM To: Orion-Interest Subject: Re: debug jsp pages and where is the source Wendell, orion-web-app jsp-cache-directory=./persistence servlet-webdir=/servlet development=false-- Change this to true persistence-path=./persistence/state.ser Then . . . Assuming all things are equal and you have a default web app called 'devel-default-web-app' bound to the server you're working with, the persistence (and subsequently the .java files for the .jsp's) will be in the path: /u/orion/application-deployments/default/devel-default-web-app/persistence http://www.mydomain.com/index.jsp will produce the files /u/orion/application-deployments/default/devel-default-web-app/per sistence/index.jsp.java /u/orion/application-deployments/default/devel-default-web-app/per sistence/index.jsp.jspCache peace - scot Wendell Nichols wrote: Well I made the jsp page work by explicitly importing java.lang.String, as opposed to java.lang.* as I had done for other servers. Because this shouldn't bother other servers I'm ok with it. I still need to have access to the jsp.java files for debugging purposes before Orion will be an acceptable server for me... ... snip ... Any help would be appreciated.. Wendell Nichols Amdahl Software Ltd. and Fujitsu Apserv. -- scot weber - [EMAIL PROTECTED] - Given a choice between a folly and a sacrament, one should always choose the folly -- because we know a sacrament will not bring us closer to God and there's always a chance that a folly will. - Erasmus The only man who never makes a mistake is the man who never does anything. - Theodore Roosevelt. -- scot weber - [EMAIL PROTECTED] - Given a choice between a folly and a sacrament, one should always choose the folly -- because we know a sacrament will not bring us closer to God and there's always a chance that a folly will. - Erasmus The only man who never makes a mistake is the man who never does anything. - Theodore Roosevelt.
Automatic recompilation of beans/servlets
Hi, I recently made the switch from Resin to Orion Server and am mostly pleased. The only thing I cannot get working is the automatic recompilation of beans and servlets. I have development=true set in my global-web-app.xml file, and JSPs are recompiling when changed correctly. Servlets and JavaBeans (not EJBs) are not. I have my source files in the same directory as the class files. (WEB-INF/classes/com/goldbarter/servlets/GoldStatus.java for example) When doing an ls -l on the directory, the moddate for the .java is much later than the .class. I don't think there's any time synchronization issue. Thanks, -Todd Lipcon Goldbarter.com -- It's not that easy being green; Having to spend each day the color of the leaves. When I think it could be nicer being red, or yellow or gold... or something much more colorful like that. -Kermit the Frog
Re: Automatic recompilation of beans/servlets
For the servlet, I think the source has to be under /WEB-INF/src for the auto-compilation. Probably for the beans too. Nick At 01:02 PM 6/17/01 -0400, you wrote: Hi, I recently made the switch from Resin to Orion Server and am mostly pleased. The only thing I cannot get working is the automatic recompilation of beans and servlets. I have development=true set in my global-web-app.xml file, and JSPs are recompiling when changed correctly. Servlets and JavaBeans (not EJBs) are not. I have my source files in the same directory as the class files. (WEB-INF/classes/com/goldbarter/servlets/GoldStatus.java for example) When doing an ls -l on the directory, the moddate for the .java is much later than the .class. I don't think there's any time synchronization issue. Thanks, -Todd Lipcon Goldbarter.com -- It's not that easy being green; Having to spend each day the color of the leaves. When I think it could be nicer being red, or yellow or gold... or something much more colorful like that. -Kermit the Frog
Re: messages
Boris Garbuzov wrote: Guys, why am I getting these messages? I'm getting the same thing. Ross - ject: Undeliverable: Date: Sat, 16 Jun 2001 19:58:05 +0200 (CEST) From: Mail Delivery Subsystem [EMAIL PROTECTED] Reply-To: Orion-Interest [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] References: 1 Important information! This e-mail has not been delivered to [EMAIL PROTECTED] The receiver's mailbox is full. When the mailbox has been emptied you will be able to resend this e-mail. Best regards Telia Internet
Re: RMI Clustering done. Now want more.
hi lachezar, i've got clustering working for our app but haven't used the rmi.xml clustering settings. the app seems to failover ok to another machine in the cluster if i switch a machine off, etc,. we use only stateless session beans and so i wondered if only entity bean information was exchanged over the port specified in rmi.xml what's all this stuff for in rmi.xml cluster host=230.0.0.1 id=123 password=123abc port=9127 username=cluster-user / Tag that is defined if the application is to be clustered. Used to set up a local multicast cluster. A username and password used for the servers to intercommunicate also needs to be specified. host - The multicast host/ip to transmit and receive cluster data on. The default is 230.0.0.1. id - The id (number) of this cluster node to identify itself with in the cluster. The default is based on local machine IP. password - The password configured for cluster access. Needs to match that of the other nodes in the cluster. port - The port to transmit and receive cluster data on. The default is 9127. username - The username configured for cluster access. Needs to match that of the other nodes in the cluster. thanks, greg. - Original Message - From: Lachezar Dobrev To: Orion-Interest Sent: Friday, June 15, 2001 6:18 PM Subject: RMI Clustering done. Now want more. Hello. OK. I was able to (at last) run the RMI clustering. It now works. But... I have a question... Now I can put up a cluster, and when a bean does not exist on the server it is searched on the cluster and used. However if it is deployed on more than one machine... It is not found on all of them, but rather on only one. For simplicity let's assume we have OrionA, OrionB, OrionC and OrionD. a) on all machines we have EnterpriseBean1 deployed. It accesses EnterpriseBean2 b) machine OrionA does not have EnterpriseBean2 deployed. c) machines OrionB, OrionC and OrionD have EnterpriseBean2 deployed. d) all machines have a RMI cluster set-up and working. (BTW) Because I needed quite some time to understand why the cluster was not working I am eager to help anyone, that needs help on the subject. If machine OrionA runs EnterpriseBean1 it will have to look-up EnterpriseBean2, which is used by EnterpriseBean1. There is no problem to find that bean (it exists on the cluster). However... Once EnterpriseBean2 is used on OrionC it keeps using that one. Why? Also. If we deploy EnterpriseBean2 on OrionA it is always found there and not on ANY other cluster machine. 1. How does Orion know on which machine to use the bean? The last one, that wakes up? 2. Is there a way to implement (at least) a round-robin technique to access the clustered bean on more than one server? I mean... When I look-up EnterpriseBean2... I would like to have a different server answering every time. Round-robin is sufficient, even though a loadbalancing technique would be better appropriate. Ok. Waiting forward to hearing from you all... P.S. Another question... CAN I TURN WEB-SERVICES OFF??? I tried removing the default-web-app tag in the server.xml, but it starts complaining about no default web-app :((( I want to have some Orion servers to act as EJB only servers. Lachezar
Sucessful installation of Cocoon 1.8.2 on Orion 1.4.5
Dear Orion Interest Group: Look at: http://candlelightsoftware.com/cocoon.html for details. Steve Steven P. Punte Candlelight Software By Candlelight If Necessary! [EMAIL PROTECTED] http://candlelightsoftware.com
.ear files + library tags + DB drivers
i've sort of had success with this but been unable to install the database driver jar file using this technique. i suspect it's a classloader order problem. i receive an error message from orion "Error initializing data-source . 'com.inet.tds.TdsDriver' not found. 1. when i put Una2000.jar (the db driver jar) in the orion lib directory i receive no error messages. 2. the other jars that i have bundled with the .ear file seem to be accessible through the library entry i created in the orion-application.xml file. is there some trick in getting the library stuff processed before orion starts checking datasources, etc. thanks, greg. - Original Message - From: Tim Drury To: Orion-Interest Sent: Friday, June 08, 2001 11:20 PM Subject: RE: simplifying EAR deployment Greg, put the 3rd party jars in $EAR_ROOT/lib then edit your orion-application.xml file (in $EAR_ROOT/META-INF or $EAR_ROOT/orion for slightly older versions of orion) adding: library path="./lib" /. If you don't have orion-application.xml, deploy your app once and grab the auto-generated copy from orion/application-deployment/yourapp. put the copy in your source tree, edit it, and add it to your ear for subsequent deployments. -tim efnet #java joeblowgt -Original Message-From: Greg Matthews [mailto:[EMAIL PROTECTED]]Sent: Thursday, June 07, 2001 8:44 PMTo: Orion-InterestSubject: simplifying EAR deployment dear all, is there any way to have 3rd party jar files included in an EAR then deployed into the orion\lib directory. i'm trying to minimise the number of steps our clients have to perform when installing our app. thanks, greg
Administration
Hi, Is It possible Admin Orion remotely ??? Alessandro Fustini Java Developer e-mail: [EMAIL PROTECTED]
