[JBoss-user] Flash Remoting MX with JBoss

2002-12-04 Thread G.Nagarajan
hi all, I came across "Flash Remoting MX" from macromedia. It is supposed to provide some direct access to a back end application server which can be JBoss. This seems to be a good idea. Developing a good user interface with swing and applets takes so much time and requires skilled programmers. Als

RE: [JBoss-user] reconnect(ConnectionRecord cr) called with a non null ManagedConnection that was not killed

2002-11-28 Thread G.Nagarajan
with a > non null ManagedConnection that was not killed > > > What do the getConnection and closeConnection methods do? > > It's a good idea to do > > Connection c = ds.getConnection(); > try { > //do work > } > finally > { > c.close(); > } > > david

RE: [JBoss-user] The THANKSGIVING PLAN -- compensation plan

2002-11-28 Thread G.Nagarajan
here is my thanks :-) Nagarajan. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury > Sent: Thursday, November 28, 2002 11:47 PM > To: Jboss-Development@Lists. Sourceforge. Net; > [EMAIL PROTECTED] > Cc: 'daniel fleury' > Subject: [JBoss-us

RE: [JBoss-user] reconnect(ConnectionRecord cr) called with a non null ManagedConnection that was not killed

2002-11-28 Thread G.Nagarajan
Castor is good at > it. Please provide more details. > > david jencks > > On 2002.11.28 12:38:50 -0500 G.Nagarajan wrote: > > hi, > > I am using JBoss 3.0 with Postgres as the database. I am getting > > these errors. Can anyone tell me when this exception is th

[JBoss-user] reconnect(ConnectionRecord cr) called with a non null ManagedConnection that was not killed

2002-11-28 Thread G.Nagarajan
hi, I am using JBoss 3.0 with Postgres as the database. I am getting these errors. Can anyone tell me when this exception is thrown and how to catch it? Thanks, Nagarajan. 18:18:22,937 WARN [LocalTxConnectionManager] reconnecting a connection handle that still has a managedConnection! org.jboss.

RE: [JBoss-user] sources of memory leakage (more details)

2002-09-23 Thread G.Nagarajan
some things that you might want to look out for are - excessive recursion - using the patterns in log4j logging. The pattern for printing the line number, program name etc eat up lots of memory. These are not shown in the jvm stack and therefore will not show in any memory profiler. -