admin -restart does not work correctly
On my Linux box (kernel 2.4) the command $ java -jar /opt/orion/admin.jar ormi://localhost/ admin adminpassword -restart doesn't work. The following messages are written to the console where orion server is running: Error starting RMI-Server: IO Error: Address already in use Error starting HTTP-Server: Address already in use A shutdown after issuing the restart command doesn't work either. Any hints what I'm missing would be highly appreciated. michael -- Dipl.-Math. (fh) Michael Simons UNIOPT AG // unique logistic optimization Maximilianstr. 29; D-93047 Regensburg phone: ++49(0)941/59578-0 http://www.uniopt.net/
Re: admin -restart does not work correctly
You are (which certainly is recommended) running Orion as a non-root process. Non-root processes are not allowed to rebind (unfortunately I can't explain closer, because I don't have the details). The answer is: it's normal. If you necessarily need to use restart, run as root (there might be some other way). Markus On Thu, Sep 27, 2001 at 09:43:30AM +0200, Michael Simons wrote: On my Linux box (kernel 2.4) the command $ java -jar /opt/orion/admin.jar ormi://localhost/ admin adminpassword -restart doesn't work. The following messages are written to the console where orion server is running: Error starting RMI-Server: IO Error: Address already in use Error starting HTTP-Server: Address already in use A shutdown after issuing the restart command doesn't work either. Any hints what I'm missing would be highly appreciated. michael -- Dipl.-Math. (fh) Michael Simons UNIOPT AG // unique logistic optimization Maximilianstr. 29; D-93047 Regensburg phone: ++49(0)941/59578-0 http://www.uniopt.net/ -- Markus Holmberg [EMAIL PROTECTED]
Re: admin -restart does not work correctly
On Thu, 27 Sep 2001, Michael Simons wrote: On my Linux box (kernel 2.4) the command $ java -jar /opt/orion/admin.jar ormi://localhost/ admin adminpassword -restart doesn't work. The following messages are written to the console where orion server is running: Error starting RMI-Server: IO Error: Address already in use Error starting HTTP-Server: Address already in use A shutdown after issuing the restart command doesn't work either. Any hints what I'm missing would be highly appreciated. michael Take a look at orionsupport.com about shutdown orion server. You need to use -force to do the shutdown. As for the restart, it's not documented there. So just stop, then start. The address already in use error msg is because the shutdown is not clean, the port is still in use. XW
DataSourceUserManager ... Restart App to get new group?
I have noticed that if I add a new group to the data source for a particular user that they will not have that group's rights until Orion is restarted. Is this normal? Is there a way to refresh the user's rights without restarting the server? I tried to invalidate their session with orionconsole, but that did not work. Thanks! Jeremy - [EMAIL PROTECTED]
Exception occurs when client is first started after orion restart...
I start Orion 1.4.7 and then run my client. I get an exception. I run the client again, this time it works correctly. The client does not have any persistent state, so the "SAME" code and functions are executed every time. The following trace shows, the first time I run, and then the second time I run. Does anyone have any idea of what is going on? C:\work\individualnetwork\model\user\testjava com.indnet.model.user.test.Client javax.naming.NamingException: Error reading application-client descriptor: No location specified and no suitable instance of the type 'com.indnet.model.IdSession' found for the ejb-ref com.indnet.model.Id at com.evermind.server.ApplicationClientInitialContextFactory.getInitialContext (JAX) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246) at javax.naming.InitialContext.init(InitialContext.java:222) at javax.naming.InitialContext.init(InitialContext.java:178) at com.indnet.model.common.InitialContextFinder.getContext(InitialContextFinder .java:26) at com.indnet.model.common.InitialContextFinder.getInitialContext(InitialContex tFinder.java:13) at com.indnet.model.common.HomeFinder.getHome(HomeFinder.java:28) at com.indnet.model.user.UserEntityHomeFinder.getHome(UserEntityHomeFinder.java :20) at com.indnet.model.user.test.Client.main(Client.java:16) Exception in thread "main" C:\work\individualnetwork\model\user\testjava com.indnet.model.user.test.Client 156 C:\work\individualnetwork\model\user\test The exception is talking about com.indnet.model.IdSession, but I am not even using this in my client, here is how my application-client looks like: application-client ejb-ref ejb-ref-namecom.indnet.model.User/ejb-ref-name ejb-ref-typeEntity/ejb-ref-type homecom.indnet.model.user.UserEntityHome/home remotecom.indnet.model.user.UserEntity/remote ejb-linkcom.indnet.model.User/ejb-link /ejb-ref /application-client Any ideas? Thanks. -AP_
RE: Problem retrieving dependents after Orion restart
IMHO, it is unwise to be using EJB2.0 dependent objects at this point because this is a part of the spec which is likely to change wildly. There have even been significant changes between pd1 (when Orion's implementation was built) and pfd. You can circumvent the relationship table by creating a unidrectional relationship from Phone to Person and a finder method for Phone which is "findByPerson". If you put a getPhone() method on Person, it can hide the call to the finder on Phone. Jeff -Original Message- From: Alex Paransky [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 10:37 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Has any one been able to get the Entity(1) to Dependent(N) relationship working? I am thinking of removing Dependent objects and just using Entity Beans. However, in the way Orion handles relationships, I will have an extra table I do not really need. If I have a PersonEntity relating to PhoneEntity in a 1-N scenario, then Orion attempts to create PersonEntity-PhoneEntity join table. Is there a way to modify orion-ejb-jar.xml to avoid this type of scenario. All my Entities are identified with integer key, so my phone table simply contains a field called 'ownerId'. Different types of entities can have phones, but since all the entities are identified with the same type of primary key, I can store that in the 'ownerId' field in the phone table. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To: Orion-Interest Subject: Problem retrieving dependents after Orion restart I have an entity bean with 1-N relationships to dependents. I have two clients, the first client executes a method on a session that populates and works with the data. The second client tries to access the data. When I run the first client followed by the second client, second client works correctly. When I run the first client, then RESTART ORION, then run second client, second client fails to find dependents (but they are there, in the table). Here is the output: Orion/1.4.7 initialized Create person entity Add phone1 Add phone2 Add phone3 Phone: 8551 (818) 541-0029 1 Phone: 8552 None 2 Phone: 8553 (310) 880-5962 3 Deleting last phone Phones: [Lejb.util.Value;@44006e [apara@junior orion]$ ./go Orion/1.4.7 initialized Phones: null First we create a new person entity, set the phones (dependents), then list the phones, finally delete the last phone. Then restarting orion, we try to lookup the phone dependents. Phones returns as null. The table contains correct values. Phones ARE there. What could be wrong? -AP_
RE: Problem retrieving dependents after Orion restart
You can also enforce the dependency (cascade delete) by overriding void ejbRemove() throws RemoteException in your EJB class to find all dependents by your bean and .remove() them. Cheers, Dan. At 00:53 06/03/2001 -0800, you wrote: IMHO, it is unwise to be using EJB2.0 dependent objects at this point because this is a part of the spec which is likely to change wildly. There have even been significant changes between pd1 (when Orion's implementation was built) and pfd. You can circumvent the relationship table by creating a unidrectional relationship from Phone to Person and a finder method for Phone which is "findByPerson". If you put a getPhone() method on Person, it can hide the call to the finder on Phone. Jeff -Original Message- From: Alex Paransky [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 10:37 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Has any one been able to get the Entity(1) to Dependent(N) relationship working? I am thinking of removing Dependent objects and just using Entity Beans. However, in the way Orion handles relationships, I will have an extra table I do not really need. If I have a PersonEntity relating to PhoneEntity in a 1-N scenario, then Orion attempts to create PersonEntity-PhoneEntity join table. Is there a way to modify orion-ejb-jar.xml to avoid this type of scenario. All my Entities are identified with integer key, so my phone table simply contains a field called 'ownerId'. Different types of entities can have phones, but since all the entities are identified with the same type of primary key, I can store that in the 'ownerId' field in the phone table. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To: Orion-Interest Subject: Problem retrieving dependents after Orion restart I have an entity bean with 1-N relationships to dependents. I have two clients, the first client executes a method on a session that populates and works with the data. The second client tries to access the data. When I run the first client followed by the second client, second client works correctly. When I run the first client, then RESTART ORION, then run second client, second client fails to find dependents (but they are there, in the table). He
RE: Problem retrieving dependents after Orion restart
I can find the EntityBean correctly, it's when the public abstract Collection getPhoneDependents() is called, that I get a null object from this call. If the server is not restarted between the creation of the Person entity, and adding some phone numbers, the getPhoneDependents() properly returns the collection. If the server IS restarted, then null is returned. Again, everything appears to be stored correctly in the database it's self. All the fields which need to be populated are. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randahl Fink Isaksen Sent: Monday, March 05, 2001 11:59 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart I had the same symptom once, I had declared my primary keys as Integer and returned int rather than Integer in my ejbCreate methods. Have you accidently done the same??? Anyways, it seems Orion is quite non-informative about semantical errors, so I have entered a bug report about this issue (#349). R. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: 6. marts 2001 04:59 To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart I have been playing with the simple example some more, and still cannot resolve the issue. The strange thing is that it seems to write the data to the tables correctly. All the fields are filled in as expected, it just fails to read the data back after restart. I am not sure the best way to proceed. Here are the layout for the tables which are being used: Person Table: ++---+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | ++---+--+-+-+---+ | id | bigint(20)| | PRI | 0 | | | salutation | varchar(255) | YES | | NULL| | | name | varchar(255) | YES | | NULL| | | email | varchar(255) | YES | | NULL| | | createDate | timestamp(14) | YES | | NULL| | | modifyDate | timestamp(14) | YES | | NULL| | | parentId | bigint(20)| YES | | NULL| | | parentRelation | bigint(20)| YES | | NULL| | ++---+--+-+-+---+ Phones Table: +-+--+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | +-+--+--+-+-+---+ | id | bigint(20) | | | 0 | | | number | varchar(255) | YES | | NULL| | | ownerId | bigint(20) | YES | | NULL| | +-+--+--+-+-+---+ In the PhonesTable ownerId is the foreign key for person.id field. The following join properly returns the data: select * from ejb_person_PersonEntity pe, ejb_phones ph where pe.id = ph.ownerId; Does any one know what the problem is? Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.Perso
RE: Problem retrieving dependents after Orion restart
So is most of your development using Entity/Session beans? Are you using EJB20 Entity style beans (using abstract methods?), or are you still using EJB1.1 style beans. Are EJB20 queries safe to use with Orion? Do they work? Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dan North Sent: Tuesday, March 06, 2001 8:52 AM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart You can also enforce the dependency (cascade delete) by overriding void ejbRemove() throws RemoteException in your EJB class to find all dependents by your bean and .remove() them. Cheers, Dan. At 00:53 06/03/2001 -0800, you wrote: IMHO, it is unwise to be using EJB2.0 dependent objects at this point because this is a part of the spec which is likely to change wildly. There have even been significant changes between pd1 (when Orion's implementation was built) and pfd. You can circumvent the relationship table by creating a unidrectional relationship from Phone to Person and a finder method for Phone which is "findByPerson". If you put a getPhone() method on Person, it can hide the call to the finder on Phone. Jeff -Original Message- From: Alex Paransky [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 10:37 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Has any one been able to get the Entity(1) to Dependent(N) relationship working? I am thinking of removing Dependent objects and just using Entity Beans. However, in the way Orion handles relationships, I will have an extra table I do not really need. If I have a PersonEntity relating to PhoneEntity in a 1-N scenario, then Orion attempts to create PersonEntity-PhoneEntity join table. Is there a way to modify orion-ejb-jar.xml to avoid this type of scenario. All my Entities are identified with integer key, so my phone table simply contains a field called 'ownerId'. Different types of entities can have phones, but since all the entities are identified with the same type of primary key, I can store that in the 'ownerId' field in the phone table. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To: Orion-Interest Subject: Problem retrieving dependents after Orion restart I have an
RE: Problem retrieving dependents after Orion restart
Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To: Orion-Interest Subject: Problem retrieving dependents after Orion restart I have an entity bean with 1-N relationships to dependents. I have two clients, the first client executes a method on a session that populates and works with the data. The second client tries to access the data. When I run the first client followed by the second client, second client works correctly. When I run the first client, then RESTART ORION, then run second client, second client fails to find dependents (but they are there, in the table). Here is the output: Orion/1.4.7 initialized Create person entity Add phone1 Add phone2 Add phone3 Phone: 8551 (818) 541-0029 1 Phone: 8552 None 2 Phone: 8553 (310) 880-5962 3 Deleting last phone Phones: [Lejb.util.Value;@44006e [apara@junior orion]$ ./go Orion/1.4.7 initialized Phones: null First we create a new person entity, set the phones (dependents), then list the phones, finally delete the last phone. Then restarting orion, we try to lookup the phone dependents. Phones returns as null. The table contains correct values. Phones ARE there. What could be wrong? -AP_
RE: Problem retrieving dependents after Orion restart
I have been playing with the simple example some more, and still cannot resolve the issue. The strange thing is that it seems to write the data to the tables correctly. All the fields are filled in as expected, it just fails to read the data back after restart. I am not sure the best way to proceed. Here are the layout for the tables which are being used: Person Table: ++---+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | ++---+--+-+-+---+ | id | bigint(20)| | PRI | 0 | | | salutation | varchar(255) | YES | | NULL| | | name | varchar(255) | YES | | NULL| | | email | varchar(255) | YES | | NULL| | | createDate | timestamp(14) | YES | | NULL| | | modifyDate | timestamp(14) | YES | | NULL| | | parentId | bigint(20)| YES | | NULL| | | parentRelation | bigint(20)| YES | | NULL| | ++---+--+-+-+---+ Phones Table: +-+--+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | +-+--+--+-+-+---+ | id | bigint(20) | | | 0 | | | number | varchar(255) | YES | | NULL| | | ownerId | bigint(20) | YES | | NULL| | +-+--+--+-+-+---+ In the PhonesTable ownerId is the foreign key for person.id field. The following join properly returns the data: select * from ejb_person_PersonEntity pe, ejb_phones ph where pe.id = ph.ownerId; Does any one know what the problem is? Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To: Orion-Interest Subject: Problem retrieving dependents after Orion restart I have an entity bean with 1-N relationships to dependents. I have two clients, the first client executes a method on a session that populates and works with the data. The second client tries to access the data. When I run the first client followed by the second client, second client works correctly. When I run the first client, then RESTART ORION, then run second client, second client fails to find dependents (but they are t
RE: Problem retrieving dependents after Orion restart
Has any one been able to get the Entity(1) to Dependent(N) relationship working? I am thinking of removing Dependent objects and just using Entity Beans. However, in the way Orion handles relationships, I will have an extra table I do not really need. If I have a PersonEntity relating to PhoneEntity in a 1-N scenario, then Orion attempts to create PersonEntity-PhoneEntity join table. Is there a way to modify orion-ejb-jar.xml to avoid this type of scenario. All my Entities are identified with integer key, so my phone table simply contains a field called 'ownerId'. Different types of entities can have phones, but since all the entities are identified with the same type of primary key, I can store that in the 'ownerId' field in the phone table. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To: Orion-Interest Subject: Problem retrieving dependents after Orion restart I have an entity bean with 1-N relationships to dependents. I have two clients, the first client executes a method on a session that populates and works with the data. The second client tries to access the data. When I run the first client followed by the second client, second client works correctly. When I run the first client, then RESTART ORION, then run second client, second client fails to find dependents (but they are there, in the table). Here is the output: Orion/1.4.7 initialized Create person entity Add phone1 Add phone2 Add phone3 Phone: 8551 (818) 541-0029 1 Phone: 8552 None 2 Phone: 8553 (310) 880-5962 3 Deleting last phone Phones: [Lejb.util.Value;@44006e [apara@junior orion]$ ./go Orion/1.4.7 initialized Phones: null First we create a new person entity, set the phones (dependents), then list the phones, finally delete the last phone. Then restarting orion, we try to lookup the phone dependents. Phones returns as null. The table contains correct values. Phones ARE there. What could be wrong? -AP_
RE: Problem retrieving dependents after Orion restart
I had the same symptom once, I had declared my primary keys as Integer and returned int rather than Integer in my ejbCreate methods. Have you accidently done the same??? Anyways, it seems Orion is quite non-informative about semantical errors, so I have entered a bug report about this issue (#349). R. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: 6. marts 2001 04:59 To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart I have been playing with the simple example some more, and still cannot resolve the issue. The strange thing is that it seems to write the data to the tables correctly. All the fields are filled in as expected, it just fails to read the data back after restart. I am not sure the best way to proceed. Here are the layout for the tables which are being used: Person Table: ++---+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | ++---+--+-+-+---+ | id | bigint(20)| | PRI | 0 | | | salutation | varchar(255) | YES | | NULL| | | name | varchar(255) | YES | | NULL| | | email | varchar(255) | YES | | NULL| | | createDate | timestamp(14) | YES | | NULL| | | modifyDate | timestamp(14) | YES | | NULL| | | parentId | bigint(20)| YES | | NULL| | | parentRelation | bigint(20)| YES | | NULL| | ++---+--+-+-+---+ Phones Table: +-+--+--+-+-+---+ | Field | Type | Null | Key | Default | Extra | +-+--+--+-+-+---+ | id | bigint(20) | | | 0 | | | number | varchar(255) | YES | | NULL| | | ownerId | bigint(20) | YES | | NULL| | +-+--+--+-+-+---+ In the PhonesTable ownerId is the foreign key for person.id field. The following join properly returns the data: select * from ejb_person_PersonEntity pe, ejb_phones ph where pe.id = ph.ownerId; Does any one know what the problem is? Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 6:13 PM To: Orion-Interest Subject: RE: Problem retrieving dependents after Orion restart Here is an excerpt from orion-ejb-jar.xml, can someone tell me if I have something configured incorrectly. Again, the data is properly written to the database, it is just NOT READ when orion is restarted and getPhoneDependents() api is executed. entity-deployment name="ejb.person.PersonEntity" location="ejb.person.PersonEntity" wrapper="PersonEntityHome_EntityHomeWrapper33" table="ejb_person_PersonEntity" data-source="jdbc/siteDS" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping cmp-field-mapping name="salutation" persistence-name="salutation" / cmp-field-mapping name="name" persistence-name="name" / cmp-field-mapping name="email" persistence-name="email" / cmp-field-mapping name="phoneDependents" collection-mapping table="ejb_phones" primkey-mapping cmp-field-mapping fields cmp-field-mapping name="id" persistence-name="id" / /fields /cmp-field-mapping /primkey-mapping value-mapping type="ejb.person.PersonPhone" cmp-field-mapping name="value" properties cmp-field-mapping name="id" persistence-name="id" / cmp-field-mapping name="number" persistence-name="number" / cmp-field-mapping name="person" entity-ref home="ejb.person.PersonEntity" cmp-field-mapping name="person" fields cmp-field-mapping name="id" persistence-name="ownerId" / /fields /cmp-field-mapping /entity-ref /cmp-field-mapping /properties /cmp-field-mapping /value-mapping /collection-mapping /cmp-field-mapping ejb-ref-mapping name="ejb/id" / /entity-deployment Again, the ejb.person.PersonEntity has a 1 to N relation with dependend ejb.pers.PersonPhone. Thanks. -AP_ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alex Paransky Sent: Monday, March 05, 2001 1:18 PM To
login issue after restart of application
Dear group, I have noticed that if I restart an application to redeployI am no longer able to login into my site. What causes this...and is there a work around. I am using 1.2.9. Regards, Elephantwalker
2 problems with orion: restart and pageContext variable
I have two problems with the orionserver. 1. Orion takes not implicit the pageContext instance in the JSP-page. There are exist a solution for this problem ? 2. I want restart my orionserver: java -jar admin.jar ormi://localhost:8080 admin 123 -restart Error: javax.naming.NamingException: Lookup error: java.io.StreamCorruptedExcept ion: Caught EOFException while reading the stream header; nested exception is: java.io.StreamCorruptedException: Caught EOFException while reading the stream header orionserver throws the same error under linux and win2000. I use jdk1.2.2_07 Who can my help ??? Please write to: Thanxz ... Matthias Buchhorn [EMAIL PROTECTED]
Re: 2 problems with orion: restart and pageContext variable
I think for part 2. the port number 8080 maybe wrong, i don't specify a port number when using admin.jar example : java -jar admin.jar ormi://localhost admin niloc -deploy -file H:\dev\soap\rel\soap.ear -deploymentName soap so i think it uses the default port number for ormi.. colin. Matthias Buchhorn wrote: I have two problems with the orionserver. 1. Orion takes not implicit the pageContext instance in the JSP-page. There are exist a solution for this problem ? 2. I want restart my orionserver: java -jar admin.jar ormi://localhost:8080 admin 123 -restart Error: javax.naming.NamingException: Lookup error: java.io.StreamCorruptedExcept ion: Caught EOFException while reading the stream header; nested exception is: java.io.StreamCorruptedException: Caught EOFException while reading the stream header orionserver throws the same error under linux and win2000. I use jdk1.2.2_07 Who can my help ??? Please write to: Thanxz ... Matthias Buchhorn [EMAIL PROTECTED]
Restart.
The only time I get this particular 'java.net.ConnectException' on a -restart is if the server is not actually running. I guess it has something to do with the port that the 'ormi://servername' argument ends up picking. Try not specifying a port (worked for me) or specifying the default rmi port (defined in some people's orion/config/rmi.xml file...?) - Original Message - From: "Luis M Bernardo" [EMAIL PROTECTED] To: "Orion-Interest" [EMAIL PROTECTED] Sent: Monday, October 09, 2000 5:17 PM Subject: RE: New 2 Orion. On Sat, 7 Oct 2000, Nathan Phelps wrote: 1.) You can cleanly shut Orion down using the following command: java -jar admin.jar ormi://yourservername admin youradminpw -shutdown Or, you can use the Orion console by right-clicking on the Server and choosing Shutdown from the Context-sensitive menu. does the -restart switch also works? it doesn't work with me. this is the error I get: C:\orionjava -jar admin.jar ormi://localhost admin xx -shutdown C:\orionjava -jar admin.jar ormi://localhost admin henp123 -restart Error: javax.naming.NamingException: Lookup error: java.net.ConnectException: Co nnection refused: no further information; nested exception is: java.net.ConnectException: Connection refused: no further information what is the difference between "java -jar admin -restart" and "java -jar orion.jar"? thanks.
(try 2) Programmatic remote shutdown/start/restart of a web-app orion server
Hi: I know that I can use "java -jar admin.jar etc" from the commandline on host 1 to stop and restart Orion on host 2. This, however, requires admin.jar (and others?) on host 1. Can someone tell me if there is a programmatic method, that does not require any installation of Orion on host 1 for any of the following, and if there is, how to do it for each case? 1. from host 1, shutdown a web-application running on host 2 2. from host 1, start a web-application running on host 2 3. from host 1, restart a web-application running on host 2 4. from host 1, shutdown Orion on host 2 5. from host 1, restart Orion on host 2 Again, I'm looking for a *programmatic* way to do this. If this means admin.jar on host 1, where's the API docs for making calls of this guy without having to resort to the commandline? Right now, we're resorting to doing these things by using the commandline, manually, and writing code to remove web-apps out of the application.xml and default-web-site.xml files. This doesn't seem like a great solution... Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com
Remote start/stop/restart of web-app server
Forgive me if this was already asked, but it seems like my last post did not make it to the mailing list. Anyway, from host 1 that has no Orion installed on it, is there a way to 1. start a web-application (make it available for requests) 2. stop a web-application 3. restart a web-application 4. stop the server 5. restart the server on host 2? From what I can tell, it seems like the only way to do #4 #5 is by installing admin.jar on host 1 and calling it by commandline "java -jar admin.jar options". I see no way for #1 - #3. I can do #1 - #3 locally by modifying the XML config files, but, again, I need to do it from remote. Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com
Programmatic remote shutdown/start/restart of a web-application orion server
Hi: I know that I can use "java -jar admin.jar etc" from the commandline on my local machine to stop and restart a remote Orion server. This, however, requires admin.jar (and others?) on my local machine. Can someone tell me if there is a programmatic method, that does not require any installation of Orion on my local machine for any of the following, and if there is, how to do it for each case? 1. shutdown a web-application running on a remote Orion server 2. start a web-application running on a remote Orion server 3. restart a web-application running on a remote Orion server 4. shutdown a remote Orion server 5. restart a remote Orion server Again, I'm looking for a *programmatic* way to do this. If this means admin.jar on the local machine, where's the API docs for making calls of this guy without having to resort to the commandline? Thanks, Kit Cragin VP of Product Development Mongoose Technology, Inc. www.mongoosetech.com
Cluster stuff..restart of one server doesn't pick up running servers session data...
Hi, Clustering was a breeze, but when I shut down one server, leaving the other one up, why is it when the restart is done the newly restarted Orion doesn't get replicated the sessions any longer? This seems to be a bug to me..when the server starts up in cluster mode, doesn't it ping the other(s) somehow, so that the other(s) would then replicate thier session info to the newly started one? On the same page with this would be if I added more hardware shouldn't when they come up..they get replicated out to? My thought here is that if I have say 2 or 3 servers, I may like to update one of them at a time. So I can bring one down, update it, bring it up, then do the next one, etc. Ofcourse, I would rather deploy the .war file directly if that is possible, but I am not sure how that affects existing sessions if one or more objects in an existing session are part of the code that was uploaded. Thanks.
Shutdown or Restart... Any answers yet?
I'm searching the archives and not finding an answer, just many, many questions on the same subject. So, I'd like to know if anyone found an answer. Phil
Remote Restart
I am using Orion 1.0. I remotely modified the data-sources.xml file. Then I remotely issued a restart command as follows: java -jar admin.jar ormi://myHost admin admin -restart Problem is, the new datasource that I added is not recognized by my jsp pages. Thus, it seems that the restart didn't work. Any suggestions? Is thus a bug? Dave
