RE: [JBoss-user] Stateful session remove?

2001-10-11 Thread Robert Schulz

I think the passivation problem is not
a serialization problem, as it works 
sometimes (in fact most of the time - in
our case around 550 out of 600 times).
I think it is some sort of coordination/
synchronisation problem between the Cache
and the container.

R.

> -Original Message-
> From: David You [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 12, 2001 2:49 AM
> To: Sternagel Annegret (PN-SYS/PE); [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] Stateful session remove?
> 
> 
> I have a few remoteHome Interfaces in the attribute.
> I think that should be fine? remotehome interface should be
> serializable, and do not hold much of the resources.
> I looked a few examples like the MDB examples on jboss web site. It
> seems a common practice to create remoteHome Interface in 
> EJBCreate and
> store there.
> 
> david
> 
> 
> -Original Message-
> From: Sternagel Annegret (PN-SYS/PE)
> [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 11, 2001 12:58 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] Stateful session remove?
> 
> 
> Yes, it seems that the passivating does not work.
> To get passivation to work make shure:
> - all SessionBean attributes must be serializable or transient
> - interfaces hold in the SessionBean should be released in
> ejbPassivate()
> and reinitialized in ejbActive()
> 
> Annegret
> 
> -Ursprüngliche Nachricht-
> Von: Robert Schulz [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 11. Oktober 2001 04:00
> An: 'David You'
> Cc: '[EMAIL PROTECTED]'
> Betreff: RE: [JBoss-user] Stateful session remove?
> 
> 
> Same problem here - started as on 2.4.0.
> Does not happen all the time, seems to
> be some sort of synchronization issue
> between the LRUEnterpriseContextCachePolicy
> and the SessionPersistenceManager ...
> 
> I could really figure out what's wrong (hard
> to debug, because it only happens sometimes) - I
> ended up changing the cache policy to 
> NoPassivationCachePolicy for statefull session
> beans.
> 
> In standardjboss.xml, in the stateful session
> bean section, change to
> 
> org.jboss.ejb.plugins.NoPassivationCachePolicy cache-poli
> cy>
> 
> Of course you stateful session beans won't get
> passivated anymore - which may or may not be 
> a problem.
> 
> If anyone has a fix to get the passivating one
> working properly, please let me know.
> 
> R.
> 
> 
> 
> > -Original Message
> > From: David You [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, October 11, 2001 10:46 AM
> > To: [EMAIL PROTECTED]
> > Subject: [JBoss-user] Stateful session remove?
> > 
> > 
> > I am using JBoss 2.4.1 with Tomcat in one JVM.
> > I use a statefull session bean as a control point to all 
> other beans.
> > and store the remote session interface in SessionData. 
> > I have the finalize of the SessionData to call the remove of the
> > stateful session bean.
> > 
> > Here is the exception I got, any ideas?
> > 
> > thanks
> > david
> > 
> > ===
> > 
> > 
> > 
> > [WorkflowService] TRANSACTION ROLLBACK EXCEPTION:Could not activate;
> > nested exce
> > ption is:
> > java.io.FileNotFoundException:
> > C:\JBoss-2.4.1_Tomcat-3.2.3\jboss\db\sess
> > ions\WorkflowService\1002756681497.ser (The system cannot 
> > find the file
> > specifie
> > d); nested exception is:
> > java.rmi.NoSuchObjectException: Could not activate; nested
> > exception is:
> > 
> > java.io.FileNotFoundException:
> > C:\JBoss-2.4.1_Tomcat-3.2.3\jboss\db\sess
> > ions\WorkflowService\1002756681497.ser (The system cannot 
> > find the file
> > specifie
> > d)
> > [WorkflowService] java.rmi.NoSuchObjectException: Could not 
> activate;
> > nested exc
> > eption is:
> > [WorkflowService]   java.io.FileNotFoundException:
> > C:\JBoss-2.4.1_Tomcat-3.2
> > .3\jboss\db\sessions\WorkflowService\1002756681497.ser (The system
> > cannot find t
> > he file specified)
> > [WorkflowService]   at
> > org.jboss.ejb.plugins.AbstractInstanceCache.get(Abstr
> > actInstanceCache.java:211)
> > [WorkflowService]   at
> > org.jboss.ejb.plugins.StatefulSessionInstanceIntercep
> > tor.invoke(StatefulSessionInstanceInterceptor.java:194)
> > [WorkflowService]   at
> > org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxI
> > nterceptorCMT.java:133)
> > [WorkflowService]   at
> > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransac
> > tions(TxInt

RE: [JBoss-user] Stateful session remove?

2001-10-10 Thread Robert Schulz

Same problem here - started as on 2.4.0.
Does not happen all the time, seems to
be some sort of synchronization issue
between the LRUEnterpriseContextCachePolicy
and the SessionPersistenceManager ...

I could really figure out what's wrong (hard
to debug, because it only happens sometimes) - I
ended up changing the cache policy to 
NoPassivationCachePolicy for statefull session
beans.

In standardjboss.xml, in the stateful session
bean section, change to

org.jboss.ejb.plugins.NoPassivationCachePolicy

Of course you stateful session beans won't get
passivated anymore - which may or may not be 
a problem.

If anyone has a fix to get the passivating one
working properly, please let me know.

R.



> -Original Message
> From: David You [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 11, 2001 10:46 AM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] Stateful session remove?
> 
> 
> I am using JBoss 2.4.1 with Tomcat in one JVM.
> I use a statefull session bean as a control point to all other beans.
> and store the remote session interface in SessionData. 
> I have the finalize of the SessionData to call the remove of the
> stateful session bean.
> 
> Here is the exception I got, any ideas?
> 
> thanks
> david
> 
> ===
> 
> 
> 
> [WorkflowService] TRANSACTION ROLLBACK EXCEPTION:Could not activate;
> nested exce
> ption is:
> java.io.FileNotFoundException:
> C:\JBoss-2.4.1_Tomcat-3.2.3\jboss\db\sess
> ions\WorkflowService\1002756681497.ser (The system cannot 
> find the file
> specifie
> d); nested exception is:
> java.rmi.NoSuchObjectException: Could not activate; nested
> exception is:
> 
> java.io.FileNotFoundException:
> C:\JBoss-2.4.1_Tomcat-3.2.3\jboss\db\sess
> ions\WorkflowService\1002756681497.ser (The system cannot 
> find the file
> specifie
> d)
> [WorkflowService] java.rmi.NoSuchObjectException: Could not activate;
> nested exc
> eption is:
> [WorkflowService]   java.io.FileNotFoundException:
> C:\JBoss-2.4.1_Tomcat-3.2
> .3\jboss\db\sessions\WorkflowService\1002756681497.ser (The system
> cannot find t
> he file specified)
> [WorkflowService]   at
> org.jboss.ejb.plugins.AbstractInstanceCache.get(Abstr
> actInstanceCache.java:211)
> [WorkflowService]   at
> org.jboss.ejb.plugins.StatefulSessionInstanceIntercep
> tor.invoke(StatefulSessionInstanceInterceptor.java:194)
> [WorkflowService]   at
> org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxI
> nterceptorCMT.java:133)
> [WorkflowService]   at
> org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransac
> tions(TxInterceptorCMT.java:307)
> [WorkflowService]   at
> org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInter
> ceptorCMT.java:99)
> [WorkflowService]   at
> org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterc
> eptor.java:195)
> [WorkflowService]   at
> org.jboss.ejb.StatefulSessionContainer.invoke(Statefu
> lSessionContainer.java:341)
> [WorkflowService]   at
> org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoke
> r.invoke(JRMPContainerInvoker.java:483)
> [WorkflowService]   at
> org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.in
> vokeContainer(GenericProxy.java:335)
> [WorkflowService]   at
> org.jboss.ejb.plugins.jrmp.interfaces.StatefulSession
> Proxy.invoke(StatefulSessionProxy.java:136)
> [WorkflowService]   at $Proxy22.remove(Unknown Source)
> [WorkflowService]   at
> com.eview.admin.SessionData.finalize(SessionData.java
> :29)
> [WorkflowService]   at
> java.lang.ref.Finalizer.invokeFinalizeMethod(Native M
> ethod)
> [WorkflowService]   at 
> java.lang.ref.Finalizer.runFinalizer(Unknown
> Source)
> [WorkflowService]   at java.lang.ref.Finalizer.access$100(Unknown
> Source)
> [WorkflowService]   at
> java.lang.ref.Finalizer$FinalizerThread.run(Unknown S
> ource)
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Performance...

2001-09-27 Thread Robert Schulz

Lots of stuff (been doing Java for a while ;-), but here
are some techniques (in extremly short format) when
you have gc problems.

1) Monitoring

  Find out what does not get collected. Either use
  a tool like OptimizeIt - but I find them a bit clunky 
  to use or do it "by hand":
  Identify your "key" objects - the ones which you 
  need to create for every page transition / request
  and instance count them (+1 in the constructor 
  -1 in finalize) and make the info available at any 
   time (we have a "MemoryStatus" servlet / 
   dump thread). Finalizing does not mean it gets
   collected, but not being finalized means it won't
   get collected.
   You need to be somewhat "strategic" on which
   objects to keep track of so the monitoring does
   not slow your app down.

2) Write "Destructors"

  Once you know what does not get collected, fix it.
  For frameworks I found it useful to have a _clean()
  method which gets called from the framework to
  unhook references (especially to cut circular 
  references) Especially key an eye on hashtables,
  vectors and any other reference hugging data 
  structures and clear() them when they are no longer
  needed.

3) Write a GC kicking / monitoring thread 

   Search this list for "GC kicking bean", I posted
   the code for an MBean for Jboss a few weeks
   ago.

Doing all this works fine for server side stuff. Last time
I was involved with client side (swing) Java was two years
ago and it was almost impossible to make Swing not
leak - the API just did not allow to clean up after you 
are done (e.g. removing all listeners was often not possible)
and the gc was not good enough to collect the complex
structures. This might have changed with 1.3 - I don't know. 
Comments anyone?

Hope this helps. Am interested in any futher approaches.
Cheers,

Robert.
> -Original Message-
> From: Cor Hofman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 27, 2001 7:21 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] Performance...
> 
> 
> Robert,
> 
> Are you willing to share some gc tricks with us.
> What is it you focussed on to make the gc behave.
> 
> Regards,
> 
>    Cor.
> 
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of 
> Robert Schulz
> Sent: Thursday, September 27, 2001 09:55
> To: '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] Performance...
> 
> 
> Jo napot kivanok (this is as far as my Hungarian will go)
> 
> We have a very similar setup
> 
> Single CPU P4-1.4G, 1G RAM, fast SCSI disk running
> RH 7.1, SUN JDK1.3.1, Apache, Resin, JBoss2.4 and Postgres.
> 
> This setup runs around 50 concurent users mucking around
> with the web app easily (we did not push it further as we
> only use it in-house at the moment) and we have it running
> for weeks with consistent response times. We talking hundreds
> of thousands of bean method invocations and millions of SQL
> queries. Due to the nature of the app, our session are all pretty
> long running (whereas yours sounds like a couple of pages per
> session app, right?)
> 
> The only thing with Postgres is to VACUUM it periodically
> if you have a lot of updates (we do it every 10 minutes which
> takes around 3 secs).
> 
> We have around 30 beans - jboss sits at about 48M (up from
> 39 for JBoss2.2) and our servlet engine at about (25) - however
> we did a lot of work to make sure our app logic gc-s properly.
> 
> Let us know how you go!
> 
> Robert.
> > -Original Message-
> > From: Jarecsni János [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 27, 2001 4:35 PM
> > To: JBoss-User
> > Subject: [JBoss-user] Performance...
> >
> >
> > Hi,
> >
> > we developed an antiquarian bookstore using Sun's RI (and taking the
> > Petstore as the basis for the architecture of our system -
> > more or less
> > successfully :-) Albeit I kept on telling my boss not to go
> > into production
> > with Sun RI, we did last week. Ads appeared, and so on. And
> > to turn to the
> > subject, dozens of users are now coming and the number is going up.
> >
> > What I experienced was that the server just gave up after an
> > hour and a half
> > or so. Response times grew, and finally it stalled. So, we
> > decided to switch
> > to JBoss (latest stable build), and we're now at the final
> > stage of this
> > transition. (The hardware is a two-way Intel PC, 800Mhz, with
> > 512 Megs of
> > RAM running Debian GNU/Linux [kernel 2.4]. The server's mere
> > duty is to run
> > J2EE and a PostgreSQL server plus two s

RE: [JBoss-user] Performance...

2001-09-27 Thread Robert Schulz

No, separate VMs.I look at it breifly but we don't
really need it and it looks quite messy to get right
in terms of class loading ...

R.

> -Original Message-
> From: Tahir Awan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 28, 2001 1:49 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] Performance...
> 
> 
> were you able to run JBoss 2.4 and Resin in same VM?
> If so, can you share the configuration?
> 
> Tahir
> 
> -Original Message-
> From: Robert Schulz [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 27, 2001 3:55 AM
> To: '[EMAIL PROTECTED]'
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] Performance...
> 
> 
> Jo napot kivanok (this is as far as my Hungarian will go)
> 
> We have a very similar setup
> 
> Single CPU P4-1.4G, 1G RAM, fast SCSI disk running
> RH 7.1, SUN JDK1.3.1, Apache, Resin, JBoss2.4 and Postgres.
> 
> This setup runs around 50 concurent users mucking around
> with the web app easily (we did not push it further as we 
> only use it in-house at the moment) and we have it running 
> for weeks with consistent response times. We talking hundreds 
> of thousands of bean method invocations and millions of SQL 
> queries. Due to the nature of the app, our session are all pretty
> long running (whereas yours sounds like a couple of pages per
> session app, right?)
> 
> The only thing with Postgres is to VACUUM it periodically
> if you have a lot of updates (we do it every 10 minutes which
> takes around 3 secs).
> 
> We have around 30 beans - jboss sits at about 48M (up from
> 39 for JBoss2.2) and our servlet engine at about (25) - however
> we did a lot of work to make sure our app logic gc-s properly.
> 
> Let us know how you go!
> 
> Robert.
> > -Original Message-
> > From: Jarecsni János [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 27, 2001 4:35 PM
> > To: JBoss-User
> > Subject: [JBoss-user] Performance...
> > 
> > 
> > Hi,
> > 
> > we developed an antiquarian bookstore using Sun's RI (and taking the
> > Petstore as the basis for the architecture of our system - 
> > more or less
> > successfully :-) Albeit I kept on telling my boss not to go 
> > into production
> > with Sun RI, we did last week. Ads appeared, and so on. And 
> > to turn to the
> > subject, dozens of users are now coming and the number is going up.
> > 
> > What I experienced was that the server just gave up after an 
> > hour and a half
> > or so. Response times grew, and finally it stalled. So, we 
> > decided to switch
> > to JBoss (latest stable build), and we're now at the final 
> > stage of this
> > transition. (The hardware is a two-way Intel PC, 800Mhz, with 
> > 512 Megs of
> > RAM running Debian GNU/Linux [kernel 2.4]. The server's mere 
> > duty is to run
> > J2EE and a PostgreSQL server plus two standalone Java apps 
> > that run some
> > scheduled tasks [sleeping mostly]).
> > 
> > My question is what we can expect from JBoss? I mean I have 
> > evil forebodings
> > as whether our application has been written correctly (in 
> > terms that JBoss
> > can run it optimally), because it was the very first J2EE app 
> > written at us,
> > and we had really no expert guidance at hand (only the 
> > Petstore example). I
> > have some hopes regarding the in-VM calls available in jBoss 
> > (no remote
> > calls between EJBs that run in the same VM), but what I'd 
> > really like to
> > know is what one needs to be able to serve hundreds of 
> > concurrent users???
> > So given that there are no severe architectural flaws in our 
> > application,
> > will jBoss be able to serve such a load without dramatic performance
> > degradation? Or should we apply some alternatives as server 
> clustering
> > and/or improve hardware (eg. use a separate machine as DB server)?
> > 
> > You know it's very important for me that this project 
> > succeeds since I get
> > criticisms every day saying that it would have all been done 
> > with PHP in a
> > few weeks time and would not crash even with hundreds of 
> > users... (which I
> > hardly believe). It would be so great to be able to prove 
> > that my idea to go
> > the J2EE way was right...
> > 
> > Thanks for your patience reading this and for your valuable answers!
> > 
> > Cheers,
> > 
> > János Jarecsni
> > Budapest, Hungary
> > 
> > 
> > ___
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Performance...

2001-09-27 Thread Robert Schulz

Jo napot kivanok (this is as far as my Hungarian will go)

We have a very similar setup

Single CPU P4-1.4G, 1G RAM, fast SCSI disk running
RH 7.1, SUN JDK1.3.1, Apache, Resin, JBoss2.4 and Postgres.

This setup runs around 50 concurent users mucking around
with the web app easily (we did not push it further as we 
only use it in-house at the moment) and we have it running 
for weeks with consistent response times. We talking hundreds 
of thousands of bean method invocations and millions of SQL 
queries. Due to the nature of the app, our session are all pretty
long running (whereas yours sounds like a couple of pages per
session app, right?)

The only thing with Postgres is to VACUUM it periodically
if you have a lot of updates (we do it every 10 minutes which
takes around 3 secs).

We have around 30 beans - jboss sits at about 48M (up from
39 for JBoss2.2) and our servlet engine at about (25) - however
we did a lot of work to make sure our app logic gc-s properly.

Let us know how you go!

Robert.
> -Original Message-
> From: Jarecsni János [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 27, 2001 4:35 PM
> To: JBoss-User
> Subject: [JBoss-user] Performance...
> 
> 
> Hi,
> 
> we developed an antiquarian bookstore using Sun's RI (and taking the
> Petstore as the basis for the architecture of our system - 
> more or less
> successfully :-) Albeit I kept on telling my boss not to go 
> into production
> with Sun RI, we did last week. Ads appeared, and so on. And 
> to turn to the
> subject, dozens of users are now coming and the number is going up.
> 
> What I experienced was that the server just gave up after an 
> hour and a half
> or so. Response times grew, and finally it stalled. So, we 
> decided to switch
> to JBoss (latest stable build), and we're now at the final 
> stage of this
> transition. (The hardware is a two-way Intel PC, 800Mhz, with 
> 512 Megs of
> RAM running Debian GNU/Linux [kernel 2.4]. The server's mere 
> duty is to run
> J2EE and a PostgreSQL server plus two standalone Java apps 
> that run some
> scheduled tasks [sleeping mostly]).
> 
> My question is what we can expect from JBoss? I mean I have 
> evil forebodings
> as whether our application has been written correctly (in 
> terms that JBoss
> can run it optimally), because it was the very first J2EE app 
> written at us,
> and we had really no expert guidance at hand (only the 
> Petstore example). I
> have some hopes regarding the in-VM calls available in jBoss 
> (no remote
> calls between EJBs that run in the same VM), but what I'd 
> really like to
> know is what one needs to be able to serve hundreds of 
> concurrent users???
> So given that there are no severe architectural flaws in our 
> application,
> will jBoss be able to serve such a load without dramatic performance
> degradation? Or should we apply some alternatives as server clustering
> and/or improve hardware (eg. use a separate machine as DB server)?
> 
> You know it's very important for me that this project 
> succeeds since I get
> criticisms every day saying that it would have all been done 
> with PHP in a
> few weeks time and would not crash even with hundreds of 
> users... (which I
> hardly believe). It would be so great to be able to prove 
> that my idea to go
> the J2EE way was right...
> 
> Thanks for your patience reading this and for your valuable answers!
> 
> Cheers,
> 
> János Jarecsni
> Budapest, Hungary
> 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] RE: freezing

2001-08-09 Thread Robert Schulz
java.lang.RuntimeException: Unable to register with 
> TransactionManager:
> javax.transaction.RollbackException: Already marked for rollback
> java.lang.RuntimeException: Unable to register with 
> TransactionManager:
> javax.transaction.RollbackException: Already marked for rollback
>   at
> org.jboss.minerva.factories.XAConnectionFactory.prepareObject(
> XAConnectionFactory.java:262)
> 
> java.lang.NullPointerException: I'm the one who caused it all 
> - expect to see
> some LOCKING-WAITING soon :) 
>   at
> org.jboss.zol.testbean.bean.EnterpriseEntityBean.getOtherField
> (EnterpriseEntityBean.java:133)
> 
>   at java.lang.reflect.Method.invoke(Native Method) 
> .. stack trace... 
> So when you see LOCKING-WAITING building up and if it is 
> caused by uncaught
> RuntimeException you should see a stacktrace of this exception in the
> server.log file and on the console. Just fix it and you're 
> back in the game.
> Otherwise it is normal that LOCKING-WAITING appears when 
> multiple clients try
> accessing the entity bean with particular primary key 
> concurrently. It just
> means that a client is waiting for some other client to 
> complete a method call
> - waiting for his turn. And if it waits for too long it 
> timesout and you see a
> nasty stack trace:
> Transaction XidImpl [ID=257, Global=NASSER/96, Branch=] timed out.
> status=STATUS_ACTIVE 
> TRANSACTION ROLLBACK EXCEPTION:Transaction marked for 
> rollback, possibly a
> timeout; nested exception is: 
> java.lang.RuntimeException: Transaction marked for 
> rollback, possibly
> a timeout 
>  java.lang.RuntimeException: Transaction marked for rollback, 
> possibly a
> timeout 
> at
> org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityI
> nstanceInterceptor.java:130)
> 
> at 
> 
> · From: Robert Schulz 
> · Subject: [jBoss-User] run out of transactions whilst 
> load testing 
> · Date: Thu, 01 Mar 2001 15:45:25 -0800 
> Not really a jBoss bug, but possibly worth while fixing: When 
> sending a
> non-parsable
> bmp SQL statement, the transaction it uses seems to never get closed.
> 
> I wrote a simple load test which just creates entity beans 
> and invokes a
> method on it.
> It worked fine for about 16,000 beans - about 100 or so queries where
> unparsable (I read
> the data from another table containing names and forgot to 
> escape quotes).
> Then the client
> freezes when invoking a remote method (well, I assume the 
> remote method
> never returns). It
> still shows up in the log. Other clients against the same 
> server also hang
> on method 
> invokation - find methods still work fine.
> 
> After a long time, the server spits out the following error message
> (multiple times)
> 
> Transaction XidImpl [ID=257, Global=robertpc/113256, Branch=] 
> timed out.
> Status = STATUS_ACTIVE
> 
> but the client's are still dead. 
> 
> As I said, not sure whether this is worth fixing (btw, this is
> jBoss-2.0FINAL).
> 
> Also, is there some documentation about jBoss specific 
> performance tuning
> anywhere? Stuff
> like
> 
> - transaction timeouts 
> - cache configurations
> 
> Any experiences / stuff which made a difference would be nice 
> as well. We
> run on Linux
> with postgres as the backend and resin as the client.
> 
> Cheers,
> 
> Robert.
> --
> Robert Schulz
> [EMAIL PROTECTED]
> 
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] dbase is acting way too slow

2001-07-16 Thread Robert Schulz


Not sure whether this helps, here is our conf, the relevant section is

  
 org.postgresql.Driver
  
  
PostgresDB
org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImp
l

jdbc:postgresql://127.0.0.1/WMS
120
notTelling
10
notTelling
false
false
false
true
12
180
false
true
1.0
0
  

Your url "jdbc:postgresql:acais://localhost:5432" is different ... if this
does not
cut it, run jboss without tomcat and see how this works. I am not really an
expert 
with this, as it "just worked" for us ;-)

R.

PS> Here our full conf - (jboss2.2.2, postgres 7.1.2, Linux 2.4.2-2
(standard RH7.1), Sun JDK1.3.1)
 
JBOSS.CONF




   


   


   
   




   


   








JBOSS.JCML



  
8083
  
  
1099
  
  
  
300
  
  
org.jboss.security.plugins.JaasSecurityManag
er
  

.. jdbc stuff here, see above ...

  
true
false
true
false
  
  
Default
:service=ContainerFactory
:service=EmbeddedTomcat
  
  
J2EE:service=J2eeDeployer
../deploy
  
  
  
  
MinervaXACMFactory

  org.opentools.minerva.connector.jboss.MinervaXACMFactory


  
  
  
  
10

8082
  
  
30
  


-Original Message-
From: G.L. Grobe [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 3:45 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] dbase is acting way too slow


Oh yeah, psql works just fine. And the same queries from psql are
sub-second. It's on the same box. I also use the 2.4.4 kernel. I'm sure it's
definately a config issue that I've got wrong somewheres, but I see nothing
wrong, of course, how would I know, heh ... it's my first time w/ JBoss and
I've still got queues to figure out after this. I had this same
configuration on Orion server so I know the code is fine.

- Original Message -
From: "Robert Schulz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 16, 2001 11:37 PM
Subject: RE: [JBoss-user] dbase is acting way too slow


> Have you tried connecting using psql?
> What happens when you run the same queries?
>
> How do you connect to the database? Maybe
> your networking is stuffed ... is it on
> the same box? Try pinging ...
>
> We use postgres against jboss (standalone, no tomcat)
> and Linux 2.4 and it works like a dream (we did some
> very superficial speed comparison against oracle and
> the performance for our type of app was about the same)
> and we have tables up to 500,000 rows ... the queries
> we have are not particularly complex though.
>
> The select you describe should be around 10-20ms
> or so ...
>
> R.
>
> -Original Message-
> From: G.L. Grobe [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 17, 2001 11:31 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] dbase is acting way too slow
>
>
> Well, seems I've finally got the database configured correctly, at least
it
> starts w/o any errors. But I'm still getting my same original behavior.
The
> problem I started to try and fix.
>
> My dbase queries are extremely slow, but they work. I'm doing a query
> through *7* records in a table w/ only 5 fields and it literally takes
10-20
> seconds for each query (that's 10-20 seconds for a 'select * from
mytable').
> I get the result sets back ok, but as I print out each query, just takes
> waay too long.
>
> As usual, thnxs for all the help.
>
> --- jboss output ---
> cassia(build):/u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss/bin$
> ./run_with_tomcat.sh
> JBOSS_CLASSPATH=:/u/public/jdk1.3/lib/tools.jar:run.jar:../lib/crimson.jar
> jboss.home = /u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss
> Using JAAS LoginConfig:
> file:/u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss/conf/tomcat/auth.conf
> Using configuration "tomcat"
> [root] Started Log4jService,
>
config=file:/u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss/conf/tomcat/log4j.prope
> rties
> [Info] Java version: 1.3.0,Sun Microsystems Inc.
> [Info] Java VM: Java HotSpot(TM) Server VM 1.3.0,Sun Microsystems Inc.
> [Info] System: Linux 2.4.4,i386
> [Shutdown] Shutdown hook added
> [Service Control] Initializing 27 MBeans
> [WebService] Initializing
> [WebService] Initialized
> [NamingService] Initializing
> [NamingService] Initialized
> [JNDIView] Initializing
> [JNDIView] Initialized
> [TransactionManagerService] Initializing
> [TransactionManagerService] Initialized
> [ClientUserTransactionService] Initializing
> [ClientUserTransactionService] Initialized
> [JaasSecurityManagerService] Initializing
> [JaasSecurityManagerService] Initialized
> [JdbcProvider] Initializing
> [JdbcProvider] Loaded JDBC-driver:org.postgresq

RE: [JBoss-user] dbase is acting way too slow

2001-07-16 Thread Robert Schulz

Have you tried connecting using psql?
What happens when you run the same queries?

How do you connect to the database? Maybe
your networking is stuffed ... is it on
the same box? Try pinging ...

We use postgres against jboss (standalone, no tomcat)
and Linux 2.4 and it works like a dream (we did some 
very superficial speed comparison against oracle and 
the performance for our type of app was about the same)
and we have tables up to 500,000 rows ... the queries
we have are not particularly complex though.

The select you describe should be around 10-20ms
or so ...

R.

-Original Message-
From: G.L. Grobe [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 11:31 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] dbase is acting way too slow


Well, seems I've finally got the database configured correctly, at least it
starts w/o any errors. But I'm still getting my same original behavior. The
problem I started to try and fix.

My dbase queries are extremely slow, but they work. I'm doing a query
through *7* records in a table w/ only 5 fields and it literally takes 10-20
seconds for each query (that's 10-20 seconds for a 'select * from mytable').
I get the result sets back ok, but as I print out each query, just takes
waay too long.

As usual, thnxs for all the help.

--- jboss output ---
cassia(build):/u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss/bin$
./run_with_tomcat.sh
JBOSS_CLASSPATH=:/u/public/jdk1.3/lib/tools.jar:run.jar:../lib/crimson.jar
jboss.home = /u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss
Using JAAS LoginConfig:
file:/u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss/conf/tomcat/auth.conf
Using configuration "tomcat"
[root] Started Log4jService,
config=file:/u/public/JBoss-2.4.0_Tomcat-3.2.2/jboss/conf/tomcat/log4j.prope
rties
[Info] Java version: 1.3.0,Sun Microsystems Inc.
[Info] Java VM: Java HotSpot(TM) Server VM 1.3.0,Sun Microsystems Inc.
[Info] System: Linux 2.4.4,i386
[Shutdown] Shutdown hook added
[Service Control] Initializing 27 MBeans
[WebService] Initializing
[WebService] Initialized
[NamingService] Initializing
[NamingService] Initialized
[JNDIView] Initializing
[JNDIView] Initialized
[TransactionManagerService] Initializing
[TransactionManagerService] Initialized
[ClientUserTransactionService] Initializing
[ClientUserTransactionService] Initialized
[JaasSecurityManagerService] Initializing
[JaasSecurityManagerService] Initialized
[JdbcProvider] Initializing
[JdbcProvider] Loaded JDBC-driver:org.postgresql.Driver
[JdbcProvider] Initialized
[XADataSourceLoader] Initializing
[XADataSourceLoader] Initialized
[XADataSourceLoader] Initializing
[XADataSourceLoader] Initialized
[ServerDataCollector] Initializing
[ServerDataCollector] Initialized
[ContainerFactory] Initializing
[ContainerFactory] Initialized
[EmbeddedTomcatServiceSX] Initializing
[EmbeddedTomcatServiceSX] Initialized
[JBossMQService] Initializing
[JBossMQService] Initialized
[JMSProviderLoader] Initializing
[Default] queue factory name: XAQueueConnectionFactory
[Default] topic factory name: XATopicConnectionFactory
[JMSProviderLoader] Initialized
[ServerSessionPoolLoader] Initializing
[ServerSessionPoolLoader] Initialized
[J2eeDeployer] Initializing
[J2eeDeployer] Initialized
[RARDeployer] Initializing
[RARDeployer] Initialized
[ConnectionManagerFactoryLoader] Initializing
[ConnectionManagerFactoryLoader] Initialized
[ConnectionManagerFactoryLoader] Initializing
[ConnectionManagerFactoryLoader] Initialized
[ConnectionManagerFactoryLoader] Initializing
[ConnectionManagerFactoryLoader] Initialized
[ConnectionFactoryLoader] Initializing
[ConnectionFactoryLoader] Initialized
[ConnectionFactoryLoader] Initializing
[ConnectionFactoryLoader] Initialized
[AutoDeployer] Initializing
[AutoDeployer] Initialized
[JMXAdaptorService] Initializing
[JMXAdaptorService] Initialized
[RMIConnectorService] Initializing
[RMIConnectorService] Initialized
[MailService] Initializing
[MailService] Initialized
[Service Control] Initialized 27 services
[Service Control] Starting 27 MBeans
[WebService] Starting
[Default] Started on port 8083
[Webserver] Codebase set to http://cassia:8083/
[Webserver] Started webserver on port 8083
[WebService] Started
[NamingService] Starting
[NamingService] Starting jnp server
[NamingService] Started jnpPort=1099, rmiPort=0, Client SocketFactory=null,
Server SocketFactory=null
[NamingService] InitialContext Environment:
[NamingService] key=java.naming.factory.initial,
value=org.jnp.interfaces.NamingContextFactory
[NamingService] key=java.naming.factory.url.pkgs,
value=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interface
s
[NamingService] Naming started on port 1099
[NamingService] Started
[JNDIView] Starting
[JNDIView] Started
[TransactionManagerService] Starting
[TransactionManagerService] Started
[ClientUserTransactionService] Starting
[ClientUserTransactionService] Started
[JaasSecurityManagerService] Starting
[Default] JAAS.startService, cachePolicy=null
[Default] JAAS.

RE: [JBoss-user] Out of memory error

2001-07-12 Thread Robert Schulz

Not sure whether this help ... we wrote a little
MBean which every 30 seconds runs System.gc() and
reports on used and allocated memory. Will take you
3 minutes to write, but if you are interested I'll post
the code. We use that to keep an eye on memory.

Another approach would be to first run a stress test only
against jboss (without tomcat, or with tomcat in a 
separate VM) - and monitor them separately. 

If there is a threading issue - have a look at the new
POSIX threading for Linux just released by IBM ...

We are pretty close to production as well and run
numerous stress test (creation of around 50,000 beans,
500,000+ SQL statements) and jboss never climbed over
50MB ... we use RH7.1 (Linux) 2.4, sun jdk1.3.1, 
postgres7.1.2 and resin in a separate VMs. We are only
using "core" EJB features (no MDBs, no SOAP, no integrated
Servlets, etc, etc ...)

Good luck and let us know how you go.


R.
-Original Message-
From: Jim Gloor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 12, 2001 12:14 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [JBoss-user] Out of memory error


We've been consistently having this problem, too, after about 5-6 hours
(~60,000 transactions) of stress testing.  We're using JBoss 2.2.1 + Tomcat
3.2.1 on a Linux box with 200 MB of RAM allocated for the JBoss VM.  Here's
a specific example of the error message:

Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested
53687
0924 bytes

We've been monitoring memory usage, and the JBoss VM was only using about
10% of the available memory at the time of the error, so that's clearly not
the problem.

We'll start monitoring thread usage, as per Jim Archer's comments, but in
the meantime, does anyone have any other insights/suggestions?  We'd
actually like to start using JBoss in a production system soon, but this
could be a real problem!


> "JA" == Jim Archer <> writes:
>
> JA> Saul, watch your thread usage. jBoss will usually throw an out of
> JA> memory exception when it can't create a new thread... On Solaris,
> JA> you have a hard limit of threads.
>
> JA> I don't know if this is your actual problem, but I thought I would
> JA> mention it.
>
> I think there should be a bug open.  We've had a lot of problems with
> this on a Linux box.
>
> -- 
>   Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com
> mailto: mailto:
> GSM: +44 (0)7909 960 751   DDI: +44 (0)20 7368 9708


Jim Gloor ([EMAIL PROTECTED])
Senior Software Engineer, Open Ratings, Inc.
928 Commonwealth Avenue
Boston, MA   02215-1204
(617) 582-5159

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] JBoss and Resin

2001-06-25 Thread Robert Schulz

Yup. Separate VMs. Not much to configure, really.
Couple of jar in the rights spots and done. Works
like a dream. There also have been a bunch of
postings on the newsgroups recently - have a search.


Cheers,

R.


-Original Message-
From: Dragos Haiduc [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 26, 2001 7:13
To: [EMAIL PROTECTED]
Subject: [JBoss-user] JBoss and Resin


Has anybody configured Resin and JBoss to run together(maybe in the same
VM)? 
Thx 
Dragos 
  

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] DEAR JBOSS USERS

2001-06-13 Thread Robert Schulz

Randy,

sorry for not getting back earlier - had a couple of days of ;-)

> 1.  What version of Resin are you using? 

1.1.5 and 1.2.?

> 2.  I assume you are using the latest Jboss? 

2.2Final, 2.2.1 and 2.2.2

> 3.  Can you share the code you used for the jndi link in the 
>  resin.config file? 

Yup. No link ;-)

> 4.  What jars from the jboss client directory did you load into 
> the Resin lib directory?

None. I stuffed around with ".../bin/wrapper.pl" - I usually 
find it really annoying to sort out what goes in which lib and 
ext and stuff and try and find how the VM gets started and "patch" 
the classpath till it is "right" ... I know not a clean solution,
but it works ;-)

> 5.  Anything else you did I might have forgot? 

Nope. Did not do anything else.


> I think I got everything right, but I just want to verify 
> with someone else
> using this wonderful combination, who got it to work.

It is a wonderful combination. Works like a charm - quick
and no odd effects and stuff. Played around with Tomcat for
a while ... "too hard".

But while we are at it ... maybe you want to share your resin.conf
Sounds like you have the nicer setup. I never really looked into 
cleaning it up, as it works for us.

Cheers,


Robert.
> 
> 
> 
> From: Robert Schulz <[EMAIL PROTECTED]> 
> To: "'[EMAIL PROTECTED]'" 
>  <[EMAIL PROTECTED]> 
> Subject: RE: [JBoss-user] DEAR JBOSS USERS 
> Date: Fri, 8 Jun 2001 12:49:21 +1000 
> Reply-To: [EMAIL PROTECTED] 
> 
> We are very happy with it - we are currently using 2.2 on 
> jdk1.3.0/Linux against postgres/Linux. We run resin as the 
> servlet engine in separate VMs plugged into apache. 
> 
> We have about 10 entitiy and 20 session beans and written a 
> fairly substantial web app on top of it and it works like 
> a dream. We have a reasonable amount of data in the database 
> (around 100,000 rows in the biggest table). I have to add that 
> we are only using the "core" EJB features (entity and session 
> beans) and took out all the other stuff (MDB, Tomcat/Jetty 
> integration, soap, ...) 
> 
> We are not in production yet but reasonably close to it - we have 
> done some load testing and it is looking good. 
> 
> The hardest part is (or used to be in PRE2.0) getting it to work 
> in the first place ... but in comparison to say oracle it is quite 
> easy (in comparison to postgres, it is quite hard). 
> 
> You need to spend a bit of time setting up a productive development 
> environment - I recommend a IDE of your choice (not entering this 
> discussion again) and a good build tool - we use ANT (and it rocks). 
> The hot deploy of jboss and the automatic checking of newer class 
> files of resin makes the develop / compile / run cycle really quick. 
> 
> Ok 'nough said. We love it - good opportunity to place a "BIG THANKS" 
> to the jboss team - keep up the good work! 
> 
> Cheers, 
> 
> Robert. 
> 
>
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] DEAR JBOSS USERS

2001-06-07 Thread Robert Schulz

We are very happy with it - we are currently using 2.2 on 
jdk1.3.0/Linux against postgres/Linux. We run resin as the 
servlet engine in separate VMs plugged into apache.

We have about 10 entitiy and 20 session beans and written a
fairly substantial web app on top of it and it works like 
a dream. We have a reasonable amount of data in the database 
(around 100,000 rows in the biggest table). I have to add that
we are only using the "core" EJB features (entity and session 
beans) and took out all the other stuff (MDB, Tomcat/Jetty 
integration, soap, ...)

We are not in production yet but reasonably close to it - we have
done some load testing and it is looking good.

The hardest part is (or used to be in PRE2.0) getting it to work
in the first place ... but in comparison to say oracle it is quite
easy (in comparison to postgres, it is quite hard).

You need to spend a bit of time setting up a productive development 
environment - I recommend a IDE of your choice (not entering this
discussion again) and a good build tool - we use ANT (and it rocks).
The hot deploy of jboss and the automatic checking of newer class
files of resin makes the develop / compile / run cycle really quick.

Ok 'nough said. We love it - good opportunity to place a "BIG THANKS"
to the jboss team - keep up the good work!

Cheers,

Robert.
> -Original Message-
> From: Faisal Abdallah [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 08, 2001 6:39
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] DEAR JBOSS USERS
> 
> 
> Dear Jboss users I am interested in hearing your experience 
> with Jboss . I
> ve been using it since jboss2.0 update ...nd  few improvements have
> occurred since .Till now it seems to me that IT can't, even, 
> carry out the
> simplest EJB tasks such as finder methods( ByPrimarykey(),findAll(
> ) and Collection findBy...( )
> Hope I can hear your views so I can try another decent EJB server
> many thinks
> 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] JBuilder Integration for edit/compile/test

2001-05-10 Thread Robert Schulz

We develop with JBuilder for JBoss - run your client out of JBuilder 
and deploy the EJB stuff into JBoss with ant - based scripts. With the
hot deploy stuff this works very well for us and you get a short 
development cycle.

R.

> -Original Message-
> From: Adam Lipscombe [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 11, 2001 10:30
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] JBuilder Integration for edit/compile/test
> 
> 
> Hi,
> 
> Is it possible to integrate JBoss with JBuilder4?
> 
> I need to create EJB's and minimise the edit/compile/test cycle.
> Ideally I want JB4 to compile and then deploy the bean to JBoss
> automatically.
> I believe (bit I haven't tried it) that JB4 can do this with 
> the Inprise App
> Server and Weblogic...
> 
> If anyone has achieved this I would love to know how...
> 
> 
> Thanks - Adam
> 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Re: JAWS: Is this a bug, or is there another rational

2001-05-07 Thread Robert Schulz

I think streaming into postgres only works with the "Fasttrack" API.
Have a look at the postgres JDBC doc - there are a few examples how 
to do it and I played around with it a while ago and it worked well. 
I think you have to downcast the statment and then there is a large
object API.

As far as I remember, the methods on statement dealing with streams 
are not implemented - have a look at the source.

Cheers,

Robert.

> -Original Message-
> From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 08, 2001 8:57
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [JBoss-user] Re: JAWS: Is this a bug, or is there another
> rational
> 
> 
> Hi Chris,
> 
> On Tue,  8 May 2001 08:32, you wrote:
> > method on its home interface.  When JBoss attempts to 
> insert a row into
> > the database for this new bean instance, it calls
> > PreparedStatement.setBinaryStream() for a column and the JDBC driver
> > throws an exception saying that 'InputStream as parameter not
> 
> I think you'll find this might be to do with the Postgres 
> JDBC driver.  I'm 
> not sure, but I have found several areas where the driver 
> isn't fully flushed 
> out.  I'd try writing a straight JDBC insert that uses the 
> setBinaryStream() 
> method.  
> 
> Apologies if I'm wrong here.
> 
> cheers
> dim
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] problems launching JBoss2.2.x from a user shell

2001-05-03 Thread Robert Schulz

"kill pid" shuts it down fine. You probably want to
write a startup script which writes the pid into a
file and a stop script which reads it from a file 
and kills it.

R.

> -Original Message-
> From: Jim Brownfield [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 04, 2001 8:34
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] problems launching JBoss2.2.x from a user
> shell
> 
> 
> Since "^C" supposedly shuts JBoss down gracefully, you should 
> be able to
> execute "kill -INT "  where "" is retrieved 
> from a "ps"
> command.
> 
> Jim
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Guy
> > Rouillier
> > Sent: Thursday, May 03, 2001 9:11 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-user] problems launching JBoss2.2.x from a user
> > shell
> >
> >
> > Having done this, is there a way to shut down JBoss gracefully,
> > so it has a
> > chance to shut down everything that is running in a controlled
> > fashion?  Or
> > do you just kill the process, and hope for the best?
> >
> > - Original Message -
> > From: "Jim Brownfield" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, May 03, 2001 11:40 AM
> > Subject: RE: [JBoss-user] problems launching JBoss2.2.x 
> from a user shell
> >
> >
> > > Hi Juan,
> > >
> > > try "nohup ./JBoss2.2.1/bin/run.sh &"
> > >
> > > This should keep the terminal group from axing your JBoss
> > subprocess when
> > > the terminal exits.
> > >
> > > Jim
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED]
> > > > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Juan Arraiza
> > > > Sent: Thursday, May 03, 2001 2:03 AM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: [JBoss-user] problems launching JBoss2.2.x 
> from a user shell
> > > >
> > > >
> > > > Hi all,
> > > > We are founding trouble when launching JBoss2.2.x as a 
> background
> > > > process from a user shell in Solaris 2.6. If we close that
> > user terminal
> > > > (or finish the X-Windows session) from which we have 
> launched JBoss,
> > > > JBoss dies.
> > > >
> > > > We launch JBoss typing:
> > > > ./JBoss2.2.1/bin/run.sh &
> > > >
> > > > In theory (although I confess I am not a great expert 
> in Unix), that
> > > > process we start does not depend on the terminal from 
> which we have
> > > > launched it (since it is launched as a background 
> process). As I said,
> > > > when we close that terminal, the process dissapears with it.
> > > >
> > > > Does anybody know why?
> > > >
> > > > TIA
> > > >
> > > > Juan
> > > >
> > >
> > >
> > > ___
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
> >
> >
> > ___
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] problems launching JBoss2.2.x from a user shell

2001-05-03 Thread Robert Schulz

man nohup

Cheers,

R.

User Commandsnohup(1)

NAME
 nohup - run a command immune to hangups

SYNOPSIS
 /usr/bin/nohup command  [ argument ... ]

 /usr/xpg4/bin/nohup command  [ argument ... ]

DESCRIPTION
 The nohup  utility invokes the named command with the  argu-
 ments   supplied.When  the  command  is  invoked,  nohup
 arranges for the SIGHUP signal to be ignored by the process.

 The nohup  utility can be used when it is known that command
 will take a long time to run and the user wants to logout of
 the terminal; when a shell exits, the system sends its chil-
 dren  SIGHUP  signals,  which  by  default  cause them to be
 killed. All  stopped,  running,  and  background  jobs  will
 ignore  SIGHUP  and continue running, if their invocation is
 preceded by the nohup  command or if the process programmat-
 ically has chosen to ignore SIGHUP.

> -Original Message-
> From: Juan Arraiza [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 03, 2001 19:03
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] problems launching JBoss2.2.x from a user shell
> 
> 
> Hi all,
> We are founding trouble when launching JBoss2.2.x as a background
> process from a user shell in Solaris 2.6. If we close that 
> user terminal
> (or finish the X-Windows session) from which we have launched JBoss,
> JBoss dies.
> 
> We launch JBoss typing:
> ./JBoss2.2.1/bin/run.sh &
> 
> In theory (although I confess I am not a great expert in Unix), that
> process we start does not depend on the terminal from which we have
> launched it (since it is launched as a background process). As I said,
> when we close that terminal, the process dissapears with it.
> 
> Does anybody know why?
> 
> TIA
> 
> Juan
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] What happens at 6 hours and 35 minutes?

2001-05-02 Thread Robert Schulz


Not sure whether this will help, but here are a couple of
suggestions ... Write a thread which dumps memory usage, 
calls System.gc() and dumps the time it takes into a file 
every 10 seconds or so. This might tell you whether the 
gc makes the JVM die. Next step is to implement a "state logging" 
singelton into which you call whenever you enter/leave "suspect 
parts" of the code and make the thread dump the state as well
continously ... this might help to narrow it down.

Does the crash depend on load, is it always after thye _exact_
same amount of time?

Overall yours is a pretty nasty problem, as you'll have to
wait 6 hours to see whether it makes a difference |-(

Good luck.

R.
> -Original Message-
> From: Jim Brownfield [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 03, 2001 8:52
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes?
> 
> 
> Thanks, Toby.
> 
> There's no backtrace on the threads, just the typical "Memory 
> fault: core
> dumped" message.  I will try the kill -SIGQUIT, and see if 
> that gives any
> insight.  The java profiling didn't provide anything useful.
> 
> Thanks again!
> Jim
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of 
> Toby Allsopp
> > Sent: Wednesday, May 02, 2001 3:01 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [JBoss-user] What happens at 6 hours and 35 minutes?
> >
> >
> > On Wed, May 02, 2001 at 02:42:43PM -0700, Jim Brownfield wrote:
> > > Thanks for the suggestion, but it's not 6:35A.M, it's 6 hours
> > and 35 minutes
> > > running time, and it doesn't matter when I start JBoss, but you
> > can set your
> > > clock by when the JVM will fail after you've started it.  I'm
> > sure there's a
> > > JVM problem with SCO's implementation, but unfortunately,
> > there's nothing I
> > > can do about that, SCO being such an awesome
> > > implementation.  I was hoping that someone 
> could say something
> > > like, "oh yeah, JBoss does  at about that time", and
> > I'd have a
> > > place to go to try to make a temporary workaround in the 
> JBoss code.  It
> > > could be that the JVM is doing something itself, but if 
> so, it's still
> > > related somehow to JBoss (or Tomcat, I suppose), since we have
> > other Java
> > > programs that run longer than 395 minutes.
> >
> > Ok, I'll make a more helpful effort than "fix JVM".
> >
> > When the JVM crashes, does it dump stacktraces for the running
> > threads?  I've
> > seen many JVMs do this, and it might give you a clue as to 
> what's going on
> > at the time.
> >
> > You could also try taking thread dumps (kill -3) up until 
> the time when it
> > crashes.
> >
> > Toby.
> >
> > ___
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
> 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



FW: [JBoss-user] PostgreSQL 7.1 Datasource setup

2001-04-22 Thread Robert Schulz

John,

Got a reply saying "mail to long" - here the mail (see below) without
standardjaws.xml attached, only the relevant changed bits:

 PostgresDB 
 PostgreSQL 

  

This standardjaws is from jBoss2.0 times, we just keep 
copying the config files over and adapting them when
moving to a new version ...

Here is the rest of the email:

> -Original Message-
> From: Robert Schulz 
> Sent: Sunday, 22 April 2001 17:59
> To: '[EMAIL PROTECTED]'
> Subject: RE: [JBoss-user] PostgreSQL 7.1 Datasource setup
> 
> 
> Haa .. another change we made so long ago for postgres, that 
> I forgot ... sorry.
> In standardjaws.xml it seems to setup the defaultDS which 
> points to hypersonic,
> which must somehow also trigger the black box db thing - 
> again, don't really
> have time to dig around this (especially as I don't want to 
> use hypersonic).
> Attached our standardjaws.xml (stripped of everything we 
> don't need / understand).
> 
> Hope this will do the trick.
> 
> Cheers,
> 
> R.
> 
> PS> This standardjaws name change will now of course dripple 
> through all your
> deployment descriptors for you beans. Your jboss.xml-s 
> (in META-INF) should
> look like
>   
> 
> 
>   
>  res-class="org.jboss.ejb.deployment.JDBCResource">
>   FOOBAR
>   java:/PostgresDB
> 
>   
> 
> and then in the same file something like
> 
>   
> 
> 
>   SomeBeanName
>   
> ResourceRefName
> FOOBAR
>   
> 
> 
> and in your code use "java:comp/env/ResourceRefName" to get 
> to the connection pool.
> 
> 
> > -Original Message-
> > From: John Menke [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, 20 April 2001 12:12
> > To: [EMAIL PROTECTED]
> > Subject: RE: [JBoss-user] PostgreSQL 7.1 Datasource setup
> > 
> > 
> > Robert,
> > 
> > I used your versions of jboss.conf and jboss.jcml with the 
> > adjustments for
> > jdbc url. (Thanks:))  It looks like it ran well.  Take a look 
> > at the log
> > though.  I have this phantom datasource at the bottom again!! 
> >  Where is
> > DefaultDB coming from?? For that matter where is BlackBoxDB 
> > coming from? It
> > is not mentioned in jboss.jcml!!?
> > 
> > CLASSPATH=/usr/tomcat/webapps/cocoon/WEB-INF/lib:/usr/local/jC
> > VS-5.2.2/jars/
> > jcvsii.jar:run.jar:../lib/crimson.jar
> > jboss.home = /usr/local/jboss
> > Using configuration "default"
> > [Info] Java version: 1.3.0,Sun Microsystems Inc.
> > [Info] Java VM: Java HotSpot(TM) Server VM 1.3.0,Sun 
> Microsystems Inc.
> > [Info] System: Linux 2.2.14-5.0,i386
> > [Shutdown] Shutdown hook added
> > [Service Control] Registered with server
> > [Service Control] Initializing 26 MBeans
> > [Webserver] Initializing
> > [Webserver] Initialized
> > [Naming] Initializing
> > [Naming] Initialized
> > [JNDIView] Initializing
> > [JNDIView] Initialized
> > [Transaction manager] Initializing
> > [Transaction manager] Initialized
> > [JDBC provider] Initializing
> > [JDBC provider] Loaded JDBC-driver:org.postgresql.Driver
> > [JDBC provider] Initialized
> > [PostgresDB] Initializing
> > [PostgresDB] Initialized
> > [Container factory] Initializing
> > [Container factory] Initialized
> > [J2EE Deployer Default] Initializing
> > [J2EE Deployer Default] Initialized
> > [Auto deploy] Initializing
> > [Auto deploy] Initialized
> > [ConnectionManagerFactoryLoader] Initializing
> > [MinervaXACMFactory] Initialized
> > [JMX RMI Adaptor] Initializing
> > [JMX RMI Adaptor] Initialized
> > [JMX RMI Connector] Initializing
> > [JMX RMI Connector] Initialized
> > [ConnectionFactoryLoader] Initializing
> > [BlackBoxDS] Initialized
> > [DefaultDS] Initializing
> > [DefaultDS] Initialized
> > [ConnectionManagerFactoryLoader] Initializing
> > [MinervaNoTransCMFactory] Initialized
> > [InstantDB] Initializing
> > [InstantDB] Initialized
> > [RARDeployer] Initializing
> > [RARDeployer] Initialized
> > [JBossMQ] Initializing
> > [JBossMQ] Initialized
> > [JAAS Security Manager] Initializing
> > [JAAS Security Manager] Initialized
> > [jdbc/PostgresDB] Initializing
> > [jdbc/PostgresDB] Initialized
> > [StdJMSPool] Initializing
> > [StdJMSPool] Initialized
> > [DefaultJMSProvider] Initializing
> > [DefaultJMSProvider] Initialized
> > [Mail Service] Initializing
> > [Mail Service] Initialized
> > [ConnectionMan

RE: [JBoss-user] PostgreSQL 7.1 Datasource setup

2001-04-19 Thread Robert Schulz

We run RH7.0 with jBoss2.2 and Postgres7.1b5 - works like a dream.
Attached is out jboss.conf and jboss.jcml - have look at it. Will
not fit your need exactly, as we don't use tomcat and I also ripped
other MBeans which we don't need, but the postgres stuff should be 
the same (change connection info) - just diff the files to see what's 
different.

For testing, just put

host all 0.0.0.0 0.0.0.0   trust

in pg_hba.conf.

Hope this helps!
Cheers,

Robert.

> -Original Message-
> From: John Menke [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 20 April 2001 7:20
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] PostgreSQL 7.1 Datasource setup
> 
> 
> It was related to that. (pg_hba.conf)  I had an entry for 
> localhost in the
> pg_hba.conf.  For some reason Postgresql was seeing the JBoss 
> connection
> coming from my local network IP address instead of localhost. 
> I determined
> this by trying to connect to a JSP page that uses the 
> database from Tomcat.
> It gave an error pointing to the local address.  I added the 
> local address
> in the pg_hba.conf and Tomcat worked.  So then I tried the 
> Jboss startup
> again.  It seemed to work as it printed that the PostgreDB 
> pool was created
> in the log,  BUT... at the very end of the log, I get the 
> same message as
> before...  Very strange.  I have included both the JBOSS.jcml 
> and the log
> file below:
> 
> 
> 
> 
> THIS IS THE JBOSS.JCML FILE
> 
> 
> 
> 
> 
> 
> 
>   
>name="DefaultDomain:service=Webserver">
> 8083
>   
> 
>   
>name="DefaultDomain:service=Naming">
> 1099
>   
>name="DefaultDomain:service=JNDIView" />
> 
> 
>   
>name="DefaultDomain:service=TransactionManager">
> 300
>   
> 
>   
> 
>   
>   
> 
>   
>name="Security:name=JaasSecurityManager">
>  name="SecurityManagerClassName">org.jboss.security.plugins.Jaa
> sSecurityManag
> er
>   
> 
>   
> 
>   
>name="DefaultDomain:service=JdbcProvider">
>   name="Drivers">org.hsql.jdbcDriver,org.enhydra.instantdb.jdbc.
> idbDriver,org.
> postgresql.Driver
>   
> 
>name="DefaultDomain:service=Hypersonic">
> 1476
> true
> default
> false
>   
> 
>name="DefaultDomain:service=XADataSource,name=InstantDB">
> InstantDB
>  name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.X
> ADataSourceImp
> l
> 
>  name="URL">jdbc:idb:../conf/default/instantdb.properties
> 120
> 
> 10
> 
> false
> false
> false
> true
> 12
> 180
> false
> false
> 1.0
> 0
>   
> 
>name="DefaultDomain:service=XADataSource,name=DefaultDS">
> DefaultDS
>  name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.X
> ADataSourceImp
> l
> 
>  name="URL">jdbc:HypersonicSQL:hsql://localhost:1476
> 120
> sa
> 10
> 
> false
> false
> false
> true
> 12
> 180
> false
> false
> 1.0
> 0
>   
> 
>   name="DefaultDomain:service=XADataSource,name=PostgresDB">
> PostgresDB
>  name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.X
> ADataSourceImp
> l
> 
>  name="URL">jdbc:postgresql://localhost:5432/ejb
> 120
> ejbUser
> 10
> ejbPassword
> false
> false
> false
> true
> 12
> 180
> false
> false
> 1.0
> 0
>   
> 
>   
> 
>name=":service=ContainerFactory">
> true
> false
> true
> false
>   
> 
>   
> 
>   
> 
>   
>name="DefaultDomain:service=JBossMQ" />
>name=":service=JMSProviderLoader,name=JBossMQProvider">
> DefaultJMSProvider
>  name="ProviderAdapterClass">org.jboss.jms.jndi.JBossMQProvider
> 
>   
>name=":service=ServerSessionPoolMBean,name=StdJMSPool">
> StdJMSPool
>  name="PoolFactoryClass">org.jboss.jms.asf.StdServerSessionPool
> Factory bute>
>   
> 
> 
>   
>name="J2EE:service=J2eeDeployer">
> Default
>  name="JarDeployerName">:service=ContainerFactory
>  name="WarDeployerName">:service=EmbeddedTomcat
>   
> 
>name="EJB:service=AutoDeployer">
> J2EE:service=J2eeDeployer
> ../deploy
>   
> 
>   
>name="JCA:service=RARDeployer">
>   
> 
>   
>
> name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaN
> oTransCMFactor
> y">
> MinervaNoTransCMFactory
>  name="FactoryClass">org.opentools.minerva.connector.jboss.Mine
> rvaNoTransCMFa
> ctory
> 
>   
> 
>   
>
> name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaS
> haredLocalCMFa
> ctory">
>  name="FactoryName">MinervaSharedLocalCMFactory
>  name="FactoryClass">org.opentools.minerva.connector.jboss.Mine
> rvaSharedLocal
> CMFactory
> 
>   
> 
>   
>
> name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaX
> ACMFactory">
> MinervaXACMFactory
>  name="FactoryClass">org.opentools.minerva.connector.jboss.Mine
> rvaXACMFactory
> 
> 
>   
> 
>   
> name="JCA:

RE: [JBoss-user] Not so much JBoss, but XSL/XSLT

2001-04-17 Thread Robert Schulz



Don't 
know about XSL but this sounds like a VM garbage collection 
problem.
What 
seems to happen with large heap sizes is that it keeps allocating 
without
collecting and then gets tangled up when trying to collect ... try 
clustering over
a 
number of smaller heap size virtual machines. Also, use some profileing 
tool
(optimize it) to see what's happening and whether you are hanging on 
to no longer
needed 
objects.
 
R.

  -Original Message-From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]]Sent: Wednesday, 18 April 2001 
  8:29To: [EMAIL PROTECTED]Subject: 
  [JBoss-user] Not so much JBoss, but XSL/XSLTSorry to post this here, but I know more eyes will see 
  it. We've looked at a number of 
  different XSL/XSLT Processors and 
  found one that is documented fairly well, runs fast, but apparently doesn't scale very well. 
  For example, at up to loads of about 300 
  users it performs very well. 
   But, go beyond that, say to 500 users and it just crawls like a dog - running on a 4-CPU (700MHz each) 
  box with 4G ram!!  The cpus are 
  running at about 80% capacity and our 
  memory usage is over 1G (for whatever reason, we can't set the heap size any larger than that). 
  So - anyone have any experiences with XSL 
  transformations and 
  scalability?? I'd love to 
  know. Robert


RE: [JBoss-user] problem in running jboss server

2001-04-16 Thread Robert Schulz

stick crimson.jar in your classpath when starting jboss (modify the startup
script)
he jar is in lib

R.

> -Original Message-
> From: Munavar Baig Mogal [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 17 April 2001 14:24
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] problem in running jboss server
> 
> 
> Hi ,
> 
>   I am new to JBoss . I am trying to install and run jboss 
> server . While
> running i am getting this exception. Pls if anybody have 
> solution mail to
> me.
> 
>   Thanx in advancd.
> 
> Regards
> Munavar.
> 
> *  Actual Exceptions here
> **
> 
> jboss.home = D:\AppServerJboss\jboss-2.1
> Using configuration "default"
> [Info] Java version: 1.3.0,Sun Microsystems Inc.
> [Info] Java VM: Java HotSpot(TM) Client VM 1.3.0-C,Sun 
> Microsystems Inc.
> [Info] System: Windows NT 4.0,x86
> [Shutdown] Shutdown hook added
> [Service Control] Registered with server
> Exception in thread "main" [Default]
> javax.xml.parsers.FactoryConfigurationError
> : java.lang.ClassNotFoundException:
> org.apache.crimson.jaxp.DocumentBuilderFacto
> ryImpl
> [Default]   at
> javax.xml.parsers.DocumentBuilderFactory.newInstance(Document
> BuilderFactory.java:118)
> [Default]   at org.jboss.Main.(Main.java:192)
> [Default]   at org.jboss.Main$1.run(Main.java:107)
> [Default]   at java.security.AccessController.doPrivileged(Native
> Method)
> [Default]   at org.jboss.Main.main(Main.java:103)
> [Default] Shutting down
> [Service Control] Stopping 3 MBeans
> [Service Control] Stopped 3 services
> [Service Control] Destroying 3 MBeans
> [Service Control] Destroyed 3 services
> [Default] Shutdown complete
> **
> ***
> 
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] JAXP problem

2001-04-14 Thread Robert Schulz



Had 
the same problem - stick the crimson.jar in the classpath of the VM when 
starting JBoss (in run.sh or whatever it is called)
 
R.
 

  -Original Message-From: Evan Lauersen 
  [mailto:[EMAIL PROTECTED]]Sent: Saturday, 14 April 2001 
  7:23To: [EMAIL PROTECTED]Subject: 
  [JBoss-user] JAXP problem
  
  I'm having the following error starting up JBoss 
  for the first time:
   
  Exception in thread "main" [Default] 
  javax.xml.parsers.FactoryConfigurationError: 
  org.apache.crimson.jaxp.DocumentBuilderFactoryImpl[Default]   
  at javax.xml.parsers.DocumentBuilderFactory.newInstance(Document
   
  if I comment out the JAX stuff in run.bat  
  the server comes up, I'm using the default run.bat (uses 
  crimson.jar)
   
  Any help with this would be 
  appreciated
   
   
  (win2k, jdk1.3, jboss 2.2 with 
  tomcat)


RE: [JBoss-user] Segmentation violation on Linux ....

2001-04-03 Thread Robert Schulz

I used to get seg faults when running hotspot and stuffing 
up classpaths / class versions - however, your's seems to 
be "classic", ie. non hotspot ... nevertheless, make sure
your classpath is correct and everything in the classpath
can be serialized back and forth as needed.

R.

> -Original Message-
> From: swarajit [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 4 April 2000 5:21
> To: jboss; jboss
> Subject: [JBoss-user] Segmentation violation on Linux 
> 
> 
> Hi,
> I'm using JBOSS on Linux and jdk1.2.2. I tried to run Enitity
> Bean(CMP) but it's giving the following dump 
> Thanks and regards
> Swarajit
> 
> RegistrationEntityBean] in setEntityContext
> [RegistrationEntityBean] in ejbActivate
> method unknown (eip = 0)
> SIGSEGV   11*  segmentation violation
> si_signo [11]: SIGSEGV   11*  segmentation violation
> si_errno [0]: Success
> si_code [0]: SI_USER [pid: 0, uid: 0]
> stackpointer=0x44ba1450
> 
> Full thread dump Classic VM (1.2.2-RC2-K, green threads):
> "Thread-12" (TID:0x40e62890, sys_thread_t:0x81a0a50, state:CW)
> prio=5
> at java.lang.Object.wait(Native Method)
> at
> org.jboss.util.timeout.TimeoutFactory.doWork(TimeoutFactory.java:506)
> at
> org.jboss.util.timeout.TimeoutFactory.access$1(TimeoutFactory.java:4)
> RegistrationEntityBean] in setEntityContext
> [RegistrationEntityBean] in ejbActivate
> method unknown (eip = 0)
> SIGSEGV   11*  segmentation violation
> si_signo [11]: SIGSEGV   11*  segmentation violation
> si_errno [0]: Success
> si_code [0]: SI_USER [pid: 0, uid: 0]
> stackpointer=0x44ba1450
> 
> Full thread dump Classic VM (1.2.2-RC2-K, green threads):
> "Thread-12" (TID:0x40e62890, sys_thread_t:0x81a0a50, state:CW)
> prio=5
> at java.lang.Object.wait(Native Method)
> at
> org.jboss.util.timeout.TimeoutFactory.doWork(TimeoutFactory.java:506)
> at
> org.jboss.util.timeout.TimeoutFactory.access$1(TimeoutFactory.java:4)
> 
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
> 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user