d to allow this filter to do its work?
Thanks in advance.
--
Jim Brownfield
[EMAIL PROTECTED]
Radical System Solutions, Inc.
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://t
of files). I guess I have
no choice
Thanks again for your help,
Jim
>
> > -Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On Behalf Of
> > Jim Brownfield
> > Sent: Wednesday, February 19, 2003 3:08 PM
> > To: [EMAIL PROTECTED]
y help or suggestions would be greatly appreciated.
Thanks in advance!
Jim
--
Jim Brownfield
[EMAIL PROTECTED]
Radical System Solutions, Inc.
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexi
properties file, and I had to modify Larry's wrapper to fix some other
Informix problems (I couldn't get the SQLH_TYPE and SQLH_FILE parameters to
work). But it is logging in and accessing the database.
I didn't know about Larry's DB-locks problem, though. Now I'm wor
You do it in your application/applet. This problem is really independent of
JBoss. I had the same problem 6 weeks ago or so (I'm using 2.2.1). I
solved it a little differently by creating a PermissionsCollection with
AllPermission in it and setting the system policy to a new anonymous class
Pol
I saw that in the Monson-Haefel book also, and I didn't interpret it that
way, but I agree that you are probably right. I originally read this as
meaning the inner transaction was independent in the sense that it could be
rolled back independently within the context of the outer transaction.
Wou
This is probably not relavent, but I thought I'd throw it in.
I had a similar problem, and it turned out to be that somehow my MBean ended
up being put into jboss-auto.jcml twice without me knowing it. What was
happening was two of my MBeans were trying to start at the same time, and
the second
MBER(which normally would be
ok for non-jdbc accesses). When I hard-coded the port NUMBER entry in
sqlhosts, JBoss got through the configuration.
stupid Informix jdbc driver :)
--
Jim Brownfield
[EMAIL PROTECTED]
Radical System Solutions, Inc.
___
Hi Guys,
How do I cause my custom MBean's stop() method to be called using JBoss
2.2.1/JVM 1.2.2 (i.e. no shutdown hook)?
Neither "kill" nor the Shutdown class seem to cause it to be called
(although both shut down the server).
Jim
___
JBoss-user ma
Here's an example that works for me. YMMV. I've tried to remove all
application specific code, but still leave relavent timer MBean code. I
reset the timer on each timer call. You can probably set the timer up to
send periodically. The timerInterval is in seconds in this example (default
10 s
Title: Narrowing problems with tomcat and jboss 2.2.1
Someone correct me if I'm wrong, but I believe there are three solutions
possible:
1) Upgrade to the 1.3 JVM which includes the
RMI-IIOP
2) Install Sun's 1.2 add-on RMI-IIOP installation (you can only do
this if you're running on Win
t;
> Its simply a debug message that should be "Handing out a server session"
> in English. There appears to have been a slight translation problem when
> the message was added. You can safely ignore the message.
>
> - Original Message -
> From: "Jim Br
message, so presumably it's not too harmful.
However, since this message is printed for every published message, I'm
concerned that I am doing something stupid that is causing excess resource
utilization.
Is this a problem, or can I just turn off debug-level output to the logs?
Thank you in
I don't think this will
work unless you are willing to lock the entire table before you execute
this. Otherwise, you will have a race condition for the unique
key.
Jim
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Vinay
MenonSent: Frid
blems launching JBoss2.2.x from a user shell
>
>
> > "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.
> >
I believe this is dependent upon the underlying database implementation.
For instance, in Informix, if you have an autoincrement (called SERIAL type
in Informix), you could make the function call "DBINFO( 'sqlca.sqlerrd1' )"
to get the last value of a serial type that was created by the database
t
t 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:
0:54 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] What happens at 6 hours and 35 minutes?
>
>
> You might also try sucking down as much memory outside the process as
> possible to see if that is an issue as well.
>
> --- Jim Brownfield <[EMAIL PROTECTE
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
>
You need to add the "JNDI Class Library Ext" to your workbench.
Go to the menu Selected->Add->Project
Click on the "Add Project from the Repository"
Click on "JNDI Class Library Ext"
You may also need to add "JNDI Class Library Ext" to your class library path
for the applet. Do this by clicking
Turning off the JIT has allowed JBoss to run at least an extra hour (and
that's without playing with the system time). The SCO Openserver JVM must
have a bug in their JIT implementation .
Turning off the JIT will slow down JBoss, but that's probably not a problem
for us right now. I've got my
minutes?
>
>
> On Wed, 2 May 2001, Jim Brownfield wrote:
>
> > Thanks for the suggestions, Robert. I'll give that a try on
> the next pass.
> > At 6 hours a shot, I don't get very many tries during a day! :(
> Currently,
> > I've turned off the J
d 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 differ
gt; 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
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 n
o find a correlation that
might lead me to find what's happening. I am using the latest jboss/tomcat
binary distribution launched with run_with_tomcat.sh.
Anybody have any ideas?
Thanks,
Jim
--
Jim Brownfield
[EMAIL PROTECTED]
Radical System Solutions, Inc.
I am able to execute a simple client connection to a remote ejb entity bean
through VAJ 3.5.3 running on Win2K (the JBoss server is installed on a
remote SCO Openserver platform, which I'm waiting on to die at the
prescribed time :<( ). I have the JBoss packages imported into a project.
So it *c
more
experiments (like turning on the Java profiler), but I was wondering if
anyone had seen the problem before or had any ideas what JBoss might be
doing that the JVM can't handle (i.e. is it doing garbage collection every 6
hours or something?).
Any help would be greatly appreciated. Thank y
28 matches
Mail list logo
