OrionTime out

2002-01-14 Thread John Tsimikas

Orion occasionally returns the following error when calling certain EJBs
within my java app.

com.evermind.server.rmi.OrionRemoteException: Transaction was rolled
back: timed out

All the EJBs are stateless and are bean managed.

I would like to increase the timeout value, but the only tag I can find
is a tag called
session-timeout in web.xml and this doesn't seem appropriate.

I would appreciate if anyone could point me in the right direction.

John









RE: OrionTime out

2002-01-14 Thread Tommy Wassgren

In server.xml you can add the following tag:

transaction-config timeout=60 /

Tommy

-Original Message-
From: John Tsimikas [mailto:[EMAIL PROTECTED]]
Sent: 14 January 2002 15:20
To: Orion-Interest
Subject: OrionTime out


Orion occasionally returns the following error when calling certain EJBs
within my java app.

com.evermind.server.rmi.OrionRemoteException: Transaction was rolled
back: timed out

All the EJBs are stateless and are bean managed.

I would like to increase the timeout value, but the only tag I can find
is a tag called
session-timeout in web.xml and this doesn't seem appropriate.

I would appreciate if anyone could point me in the right direction.

John









RE: can't figure out this one. need help: logging, reloading custom usermanager class

2002-01-14 Thread Alex Paransky

Can you be a little bit more specific as to what is not working?  I just
spend 2 days trying to get EJBUserManager to work, and I am happy to report
that I was successful.  I assume your functions are getting called, so you
have properly registered your user manager is the orion-application.xml.
What specifically is not working?

-AP_

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jesse Schoch
Sent: Friday, January 11, 2002 11:21 AM
To: Orion-Interest
Subject: can't figure out this one. need help: logging, reloading custom
usermanager class


ok so i tried to write a custom usermanager but it will not work and will
not give me any clue as to why.  I have followed the directions on the
support site, and have turned on -verbosity 10, i think i may have had it
wrong the first time i compiled it but i don't know how to find out what
version of my class i am using.

Is there a way to see the date of the class file that's loaded?  how do you
insure that it is reloaded?  i've done touch application.xml web.xml and
every other xml that i can think of.

here is my code. it compiles fine, and this is from my active login system
so i'm pretty sure the code works.  how do i get the damn logging to work?
System.out.println() does not show up on my logs or STDOUT from running
orion.jar

package jesse;

import java.util.*;
import com.orionsupport.security.SimpleUserManager;
import java.sql.*;
import java.io.*;
import javax.sql.*;
import javax.naming.*;
//
// fuck some shit up with da user manager.
//

public class uM extends SimpleUserManager
{
private Map users  = new HashMap();
protected boolean userExists( String username )
{
boolean result = false;
try
{
Context ctx = new InitialContext();
DataSource ds = (DataSource) ctx.lookup(jdbc/mysql);
Connection con = ds.getConnection();
Statement st = con.createStatement();
Statement st2 = con.createStatement();
String q = select count(*) from stamps.users where
username='+username+';
ResultSet rs = st.executeQuery(q);
int test = rs.getInt(1);
if (test == 1)
{
result = true;
}
if (result){}
else {System.out.println(user:  +username+ does not 
exist\n);}
con.close();
}
catch (SQLException e)
{System.out.println(SQL error: +e);}
catch (NamingException er)
{System.out.println(jndi naming error+ er);}
return result;

}

  protected boolean checkPassword( String username, String password )
{
boolean result = false;
try
{
Context ctx = new InitialContext();
DataSource ds = (DataSource) ctx.lookup(jdbc/mysql);
Connection con = ds.getConnection();
Statement st = con.createStatement();
Statement st2 = con.createStatement();
if (userExists(username))
{
String q = select password user_id from stamps.users where
username='+username+';
ResultSet rs = st.executeQuery(q);
while (rs.next())
{
String u = rs.getString(2);
String p = rs.getString(1);
String q2 = select password('+password+');
ResultSet rs2 = st2.executeQuery(q2);
rs2.next();
String enpass = rs2.getString(1);
if (p.equals(enpass))
{
result = true;
users.put(username,u);
}
}
}
if (result){}
else {System.out.println(user:  +username+ failed pass check\n);}
con.close();
}
catch (SQLException e)
{System.out.println(SQL error: +e);}
catch (NamingException er)
{System.out.println(jndi naming error+ er);}
return result;
}
  protected boolean inGroup( String username, String groupname )
{
return true;
}
  protected String getUID(String username)
{
String result = (String)users.get(username);
return result;
}
}





Orion + JDO

2002-01-14 Thread Roman Seleznev



Hello , 

Does anybody expects JDO built-in implementations 
into
app servers such as Orion ?

Regards , Roman.


Re: OrionTime out

2002-01-14 Thread DPietro

I wont swear this is the answer, but in the data-sources file there is a 
inactivity-timeout tag that you may need to set. 
Min happens to be =30 I assume this means minutes.





John Tsimikas [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/14/02 10:20 AM
Please respond to Orion-Interest

 
To: Orion-Interest [EMAIL PROTECTED]
cc: 
Subject:OrionTime out


Orion occasionally returns the following error when calling certain EJBs
within my java app.

com.evermind.server.rmi.OrionRemoteException: Transaction was rolled
back: timed out

All the EJBs are stateless and are bean managed.

I would like to increase the timeout value, but the only tag I can find
is a tag called
session-timeout in web.xml and this doesn't seem appropriate.

I would appreciate if anyone could point me in the right direction.

John













JMS Question

2002-01-14 Thread Robert Hedin

I've inherited some code and it doesn't look complete, and I'm not even sure
that it will work- at least with Orion. So...

We've got multiple servers- some are always connected, some are only
connected periodically, some are only connected when the sysadmin physically
performs some task and then only for a limited time.

The goal is that we'd like to be able to push a message to a specific
server through user control. We know all of the addresses of all the
possible machines ahead of time, so having the user enter a JNDI name is not
an issue, and I can setup a servlet/whatever to provide this selection
process.

The previous programmer on this project thought that JMS would be a good
solution for this, with each server being a JMS server. However I'm not
certain that this is going to work-- at least not with Orion out of the box.

Current Basic flow:

Client creates a temporary queue for message responses
Client selects a particular machine (i.e. JNDI name)
We write to a Queue on the remote server, setting reply to to be the temp
queue on the local JMS server.
Remote system processes message and sends back a response to the temp queue.

Is the above in any way, shape, or form feasible with Orion? I've been doing
a crash course on JMS (thanks to O'reilly), but after reading the books and
the Orion docs, I'm thinking that this may be better suited for a servlet
based approach.

Any help is appreciated!

robert hedin
NDS Systems, Inc.






RE: Orion JSDK2.3

2002-01-14 Thread The elephantwalker

1.5.3 uses the jsdk2.3 spec, not the pfd 2, which was in 1.5.2. You can
check this by looking in the orion.jar distribution in 1.5.3, and see that
the filter interface in javax.servlet.Filter uses the proper methods jsdk2.3
methods for Filter, destroy(), doFilter() and init().

The old pdf 2 spec had the methods doFilter(), setFilterConfig() and
getFilterConfig(), which is what you find in the 1.5.2 distribution.

Regards,

the elephantwalker
www.elephantwalker.com


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lopez
Sent: Monday, January 14, 2002 8:25 AM
To: Orion-Interest
Subject: Orion  JSDK2.3


Hi,
There are two things that are quite annoying in the current version of Orion
and that have been defined/changed  in the final JSDK2.3 spec. First one is
that the name of the methods defined in the servlet filters are now
diferent, thus pure JSDK2.3 filters don't work in Orion. Second one is that
classloader order/precedence has been more clearly specified and it is not
necessary to hack XML parsers, for example anymore. Any news about when is
the JSDK2.3 final spec going to be implemented in Orion? Does the OC4J
version already implement it?
I have some customers who are considering going to Resin, just for those
very reasons, and I can't find any sound proof to confront their reasoning,
as we are ourselves considering migrating to other containers. Even Tomcat 4
implements now a more current spec than Orion!
From the outside, nobody would say that Orion keeps going on, but just OC4J.

regards,
D.