On 23 Jul, Scott M Stark wrote:
Since this is a JBoss adapter I don't the benefit in supporting the PrintWriter
interface
for logging integration. If there was a reason to support PrintWriter I would use
log4j by default in the JmsLogger and expose Category type methods from JmsLogger.
If
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Buildfile: run_tests.xml
build:
prepare:
compile:
jar:
prepare:
Hi,
/home/lubega/jbossro/jbosstest/src/build/run_tests.xml:112: Process
fork failed.
--- Nested Exception ---
java.io.IOException: Resource temporarily unavailable
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.init(UNIXProcess.java:139)
This
Well, that depends on taste. When the JMS RA was written it was mean to
not be dependant on JBoss at all, but should be possible to use in any
App server. There was one (easy to fix dependancy then). Changes done
since then has tied it more closely to JBoss. I guess it would therefore
be ok
User: kimptoc
Date: 01/07/24 01:49:44
Modified:src/build run_tests.xml
Log:
added some environment info to the test report
Revision ChangesPath
1.23 +19 -1 jbosstest/src/build/run_tests.xml
Index: run_tests.xml
User: kimptoc
Date: 01/07/24 01:49:44
Modified:src/build/stylesheets summary1.xsl summary2.xsl
Log:
added some environment info to the test report
Revision ChangesPath
1.6 +9 -0 jbosstest/src/build/stylesheets/summary1.xsl
Index: summary1.xsl
On 24 Jul, Jason Dillon wrote:
Well, that depends on taste. When the JMS RA was written it was mean to
not be dependant on JBoss at all, but should be possible to use in any
App server. There was one (easy to fix dependancy then). Changes done
since then has tied it more closely to JBoss. I
User: kimptoc
Date: 01/07/24 03:33:10
Modified:src/bin run.bat run.sh
Log:
add facility pass in options to the java vm - by defining the environment variable
JAVA_OPTS
Revision ChangesPath
1.22 +1 -1 jboss/src/bin/run.bat
Index: run.bat
User: kimptoc
Date: 01/07/24 05:17:26
Modified:src/bin run.sh
Log:
added some info statements and don't try to guess HOTSPOT setting if JAVA_OPTS is
supplied
Revision ChangesPath
1.22 +13 -1 jboss/src/bin/run.sh
Index: run.sh
Oops - sounds like an oversite on (perhaps my part). These jar files just
go too many places and it's all by hand.
I'm several days behind in my e-mail has anybody fixed this since it was
posted? I think there might also be some issues with the JBossCX versions
of the j2ee jar files.
Cheers
Unfortunately, it doesn't suggest anything to me. Are you committing
before closing the connection? I know it's read only, but if postgres
works like firebird/interbase and the driver doesn't check enough for open
transactions when it closes a connection it may conceivably make a
difference.
Hello,
AFAIK, file locks are new to JDK 1.4 and the behivor can vary slightly on
different platforms.
Yes, but you can use a fake file locking mechanism as long as the JBoss
server is the only one to use these files.
As I understand it, select for update is used to get an exclusive lock on
Hi Bill,
just now I'll only pick up your table and complete what I can.
Select for update supported
---
Oracle YES 0)
Sybase ?
Informix ?
DB2?
Postgres ?
mySQL ?
BerkelyDB ?
SQL
All,
What's the status of JBossTX? Is there anyone working on it? Is there
a schedule? Plan?
Thanks,
drob
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
On Tue, 24 Jul 2001, Peter Antman wrote:
On 24 Jul, Jason Dillon wrote:
Well, that depends on taste. When the JMS RA was written it was mean to
not be dependant on JBoss at all, but should be possible to use in any
App server. There was one (easy to fix dependancy then). Changes done
Bugs item #444220, was opened at 2001-07-24 12:20
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=444220group_id=22866
Category: JBossCX
Group: v2.5 Rabbit Hole (unstable)
Status: Open
Resolution: None
Priority: 5
Submitted By: David Jencks (d_jencks)
I say keep it simple and working with jboss- use log4j directly. If
someone wants to use it elsewhere we can deal with that later. After all,
the spec doesn't specify that anything in particular needs to be logged,
does it?
presumably we could bundle log4j into the jar if someone wanted to
When Toby Allsop was developing the jca stuff in jbosscx he often wrote
that all resource access would be moved to the jca framework soon ( I hope
I'm not misquoting).
I think this means rabbit hole, and I think this is a good idea.
I think the time is NOW. Lets get everyone experimenting
Well, I'm running out of ideas. One more... even less likely... and
assuming postrgres has essentially the same versioning/snapshot machinery
as firebird...
At one point running the banktest I was getting deadlocks with read
committed transaction isolation which went away when I changed to
I thought the JBossPool stuff would still be used and JCA is just a wrapper
for it?
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Jencks
Sent: Tuesday, July 24, 2001 4:32 PM
To: jboss-dev
Subject: [JBoss-dev] Timeline for using only
Feature Requests item #444258, was opened at 2001-07-24 13:42
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376688aid=444258group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous
On Tue, 24 Jul 2001, David Jencks wrote:
When Toby Allsop was developing the jca stuff in jbosscx he often wrote
that all resource access would be moved to the jca framework soon ( I hope
I'm not misquoting).
I think this means rabbit hole, and I think this is a good idea.
I think the time
User: jules_gosnell
Date: 01/07/24 17:08:00
Modified:jetty/etc README
Log:
upgrade to latest versions of JBoss and Jetty for new release
only include JMX support from Jetty3Extra to cut down on release size
Revision ChangesPath
1.2 +16 -1
User: jules_gosnell
Date: 01/07/24 17:08:00
Modified:jettyTODO
Log:
upgrade to latest versions of JBoss and Jetty for new release
only include JMX support from Jetty3Extra to cut down on release size
Revision ChangesPath
1.3 +11 -3 contrib/jetty/TODO
User: jules_gosnell
Date: 01/07/24 17:08:01
Modified:jetty/src/build build.sh build.xml
Log:
upgrade to latest versions of JBoss and Jetty for new release
only include JMX support from Jetty3Extra to cut down on release size
Revision ChangesPath
1.5 +6 -6
Bugs item #444307, was opened at 2001-07-24 17:32
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=444307group_id=22866
Category: None
Group: v2.2.2 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Williams (mdub)
Assigned to:
User: user57
Date: 01/07/24 18:39:33
Modified:.modules
Log:
*** empty log message ***
Revision ChangesPath
1.4 +46 -0 CVSROOT/modules
Index: modules
===
RCS file:
User: user57
Date: 01/07/24 18:45:26
Modified:.modules
Log:
*** empty log message ***
Revision ChangesPath
1.6 +3 -1 CVSROOT/modules
Index: modules
===
RCS file:
JBoss daily test results
SUMMARY
Number of tests run: 145
Successful tests: 144
Errors:0
Failures: 1
[time of test: 25 July 2001 2:54 GMT]
[java.version: 1.3.0]
Sorry about the empty log, I tend to do that when using CVS from emacs. I
will try not to do it again. This change adds the admin module and fixes
the name of jbosstest.
--jason
On Tue, 24 Jul 2001, Jason Dillon wrote:
User: user57
Date: 01/07/24 18:45:26
Modified:.
User: user57
Date: 01/07/24 19:08:28
Modified:.modules
Log:
o place holder for a generic plugin module
Revision ChangesPath
1.7 +2 -0 CVSROOT/modules
Index: modules
===
RCS
Feature Requests item #444343, was opened at 2001-07-24 21:46
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376688aid=444343group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous
User: deerwood
Date: 01/07/24 21:56:51
Modified:src/main/org/jboss/ejb/plugins/jaws/metadata
JawsEntityMetaData.java
Log:
o Indentation and formatting according to project standards.
One spot found, where indentation does not match parser, possible Bug?
33 matches
Mail list logo
