marc fleury wrote:
|For objects that do a lot of stuff in set*Context, yes. Common
|operations are lookup of home objects, and to create data structures. In
|those cases pooling is essential.
it is the ***reuse*** that really fucks us up. We can prefab some
instances and keep pools at a
|That could work, yes. If you do on demand it's back to
|wait-on-init-land, but replenishing in background could be ok.
Even better (checked in yesterday) create on free, don't reuse, let the
passivation thread replenish it.
And then sometime far away in the distance outside my cockpit window,
Here is what I'm going to do.
1. Merge the current main branch of the manual module to the 2.2 branch
since main has been used for the 2.2 version verification updates. The
branch tag is Branch_2_2
2. Create a 2.4 branch from the current main branch. The branch tag will
be Branch_2_4
If your
User: starksm
Date: 01/07/05 11:42:25
Modified:src/examples/resources jndi.properties
Log:
Don't use the jnp protocol in the provider url as its not needed
and does not work with versions prior to 2.2.x
Revision ChangesPath
1.3 +1 -1
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of marc
fleury
Sent: Wednesday, July 04, 2001 9:09 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] comments on new instance interceptors and
locking
[snip
|- I really think that doing a wait()
User: starksm
Date: 01/07/05 12:02:22
Modified:src/resources/org/jboss/metadata jaws.dtd jboss.dtd
Log:
Add the DOCTYPE declarations that should be used with documents that
conform to the dtds
Revision ChangesPath
1.10 +3 -0
User: starksm
Date: 01/07/05 12:06:10
Modified:src/resources/org/jboss/metadata jboss-web.dtd
Log:
Make the URI prefix consistent with the other dtds
Revision ChangesPath
1.4 +1 -1 jboss/src/resources/org/jboss/metadata/jboss-web.dtd
Index:
I don't know what happened to the dtds so I restored them in the doco_files
web site dir for now. These should be coming from the
src/resources/org/jboss/metadata
of the jboss cvs module as these are the authoritative version of the dtds
that are bundled
with the jboss.jar and used by the local
User: user57
Date: 01/07/05 00:05:59
Modified:src/main/org/jboss/test/jmsra/test AllJUnitTests.java
RaTest.java
Log:
Revision ChangesPath
1.3 +5 -4 jbosstest/src/main/org/jboss/test/jmsra/test/AllJUnitTests.java
Index:
they now deploy/test/undeploy.
The daily test should now only fail ond the xa test. Can only run tests
agains instance just started, second and thirdattempts result in error.
--jason
Happy July 4th =)
* beer is good my friends *
___
User: user57
Date: 01/07/05 00:05:59
Modified:src/main/org/jboss/test/mdb/test Main.java
Log:
Revision ChangesPath
1.6 +138 -138 jbosstest/src/main/org/jboss/test/mdb/test/Main.java
Index: Main.java
User: alborini
Date: 01/07/04 23:48:04
Modified:.log_accum.pl
Log:
Problem with user ?
Revision ChangesPath
1.3 +2 -2 CVSROOT/log_accum.pl
Index: log_accum.pl
===
RCS file:
User: user57
Date: 01/07/05 00:05:58
Modified:src/main/org/jboss/test/jmsra/bean PublisherBean.java
PublisherCMPBean.java
Log:
Revision ChangesPath
1.4 +102 -42 jbosstest/src/main/org/jboss/test/jmsra/bean/PublisherBean.java
User: starksm
Date: 01/07/05 12:44:38
Modified:src/docs/images Tag: Branch_2_2 netbeans-debug.png
netbeans-project.png
Log:
Merge the current main branch to 2.2
Revision ChangesPath
No revision
No
Wow it's an old one.
I solve my problem by adding a toString() method to the PK class.
I don't see the reason why it helped me but it does.
For some reason the get() on the cache (with the ID, this is the PK) can not
find an existing bean and load a new one (see Activated bean MasterDO in
the
MAIL ESSENTIALS SENDER NOTIFICATION
The following message:
TO: [EMAIL PROTECTED]
FROM:[EMAIL PROTECTED]
DATE: Thu, 5 Jul 2001 21:50:35 +0200
Subject: RE: [JBoss-dev] container-cache-conf 1/1
has been quarantined by Mail Essentials for the following reason(s):
Body contains
User: starksm
Date: 01/07/05 12:52:28
Added: src/examples/org/jboss/docs/cmp/cd Tag: Branch_2_2 List.java
Lookup.java Remove.java Upload.java
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No revision
User: starksm
Date: 01/07/05 12:52:29
Added: src/examples/org/jboss/docs/cmp/cd/resources Tag: Branch_2_2
cds.txt ejb-jar.xml jboss.xml
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No revision
User: starksm
Date: 01/07/05 12:52:28
Added: src/examples/build Tag: Branch_2_2 build.xml readme.txt
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No revision
No revision
1.10.2.1 +0 -0
User: starksm
Date: 01/07/05 12:52:30
Added: src/examples/org/jboss/docs/cmp/cd/utils Tag: Branch_2_2
FileLineReader.java TokenizerWithBlanks.java
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No
User: starksm
Date: 01/07/05 12:52:32
Added: src/examples/resources Tag: Branch_2_2 jndi.properties
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No revision
No revision
1.3.2.1 +0 -0
User: starksm
Date: 01/07/05 12:52:31
Added: src/examples/org/jboss/docs/jaas/howto Tag: Branch_2_2
BuildDatabase.java SecureEJBServlet.java
Session.java SessionClient.java SessionHome.java
User: starksm
Date: 01/07/05 12:52:31
Added: src/examples/org/jboss/docs/javamail Tag: Branch_2_2
Mailer.java MailerBean.java MailerHome.java
MailerServlet.java application.xml build.xml
ejb-jar.xml home.html
User: starksm
Date: 01/07/05 12:52:29
Added: src/examples/org/jboss/docs/cmp/cd/build Tag: Branch_2_2
build-client.xml build-cmp-cd-compile.xml
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No revision
User: starksm
Date: 01/07/05 12:52:29
Added: src/examples/org/jboss/docs/cmp/cd/interfaces Tag:
Branch_2_2 CD.java CDCollection.java
CDCollectionHome.java CDExistsException.java
CDHome.java
Log:
Merge the
User: starksm
Date: 01/07/05 12:52:29
Added: src/examples/org/jboss/docs/cmp/cd/bean Tag: Branch_2_2
CDBean.java CDCollectionBean.java
Log:
Merge the main examples to the 2.2 branch
Revision ChangesPath
No revision
No
it's a really odd one, the only place we use toString is in the passivation
engines (store to file) so you are looking at something else besides the
cache.
Find what's screwed up it is an interesting one,
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On
MAIL ESSENTIALS SENDER NOTIFICATION
The following message:
TO: [EMAIL PROTECTED]
FROM:[EMAIL PROTECTED]
DATE: 5 Jul 2001 16:13:19 -0400
Subject: [JBoss-dev] Mail Delivery Status Notification
has been quarantined by Mail Essentials for the following reason(s):
Body contains
MAIL ESSENTIALS SENDER NOTIFICATION
The following message:
TO: [EMAIL PROTECTED]
FROM:[EMAIL PROTECTED]
DATE: Thu, 5 Jul 2001 16:13:41 -0400
Subject: RE: [JBoss-dev] container-cache-conf 1/1
has been quarantined by Mail Essentials for the following reason(s):
Body contains
On Thu, 5 Jul 2001, Scott M Stark wrote:
I don't know what happened to the dtds so I restored them in the doco_files
web site dir for now. These should be coming from the
src/resources/org/jboss/metadata
of the jboss cvs module as these are the authoritative version of the dtds
that are
User: starksm
Date: 01/07/05 12:25:14
Modified:doco_files jboss-web.dtd
Log:
Make the URL prefix consistent with the other dtds
Revision ChangesPath
1.2 +1 -1 newsite/doco_files/jboss-web.dtd
Index: jboss-web.dtd
One of the jbosstest unit tests should be the validation of all
standard/default
descriptors against the dtd they are to conform to.
Also, we (which doesn't have to mean you) should probably update
standardjboss.xml with the DOCTYPE. Unfortunately, I don't think it
validates, so some
Incredible,
My session bean receive a PK (a very stupid Serializable object).
1. If I do nothing on it and pass to the Home of my entity bean (fbpk), no
problem - I don't need my toString()
2. If I access it by a java.lang.Object method (toString()) I have the
problem.
3. If I acces it by one of
Incredible,
My session bean receive a PK (a very stupid Serializable object).
1. If I do nothing on it and pass to the Home of my entity bean (fbpk), no
problem - I don't need my toString()
2. If I access it by a java.lang.Object method (toString()) I have the
problem.
3. If I acces it by one of
User: user57
Date: 01/07/05 17:38:51
Modified:src/main/org/jboss/test/xa/interfaces XATest.java
Log:
o changed xatest.sh to use the JUnit runner cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a
User: user57
Date: 01/07/05 17:38:51
Modified:src/resources/xa/META-INF jboss.xml
Log:
o changed xatest.sh to use the JUnit runner cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a
User: user57
Date: 01/07/05 17:38:51
Modified:src/build/subprojects build-xa.xml
Log:
o changed xatest.sh to use the JUnit runner cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a createTables()
User: user57
Date: 01/07/05 17:38:50
Modified:src/bin mq-test.sh xatest.sh
Log:
o changed xatest.sh to use the JUnit runner cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a createTables()
User: user57
Date: 01/07/05 17:38:51
Modified:src/main/org/jboss/test/xa/bean XATestBean.java
Log:
o changed xatest.sh to use the JUnit runner cleaned up classpath.
o cleaned up commandline in mq-test.sh.
o Changed XATest so that it deploys/tests/undeploys.
o Added a
I fixed the XATest so that it will function with the default configuration
of jboss from cvs. Which means that if you start up jboss, then run the
test suite, you should get zero errors and zero failures. =)
It will still have issues if you attempt to run the suite more than once
against the
This package should shortly be appearing at
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/jboss/binaries/JBoss-2.4.0BETA_Jetty-3.1.RC5-3.zip?rev=1.1
I hope it fixes pretty much all outstanding issues.
If the usual suspects would be kind enough to download it and play with
it, I
Hi,
Not quite sure if I am off-track here, but:
If you want to avoid loosing statistics, you
might want to consider combining these two
methods into a single atomic call.
For example, if you want to count bean invocations,
and do not want to drop a single invocation from
your statistics.
If
JBoss daily test results
SUMMARY
Number of tests run: 94
Successful tests: 93
Errors:1
Failures: 0
[time of test: 6 July 2001 2:47]
See http://lubega.com for
User: user57
Date: 01/07/05 19:13:38
Modified:src/build/subprojects build-bank.xml build-bmp.xml
build-cts.xml build-dbtest.xml build-hello.xml
build-load.xml build-lock.xml build-readahead.xml
build-testbean.xml
User: user57
Date: 01/07/05 19:13:08
Modified:src/bin bmptest.sh dbtest.sh locktest.sh
Log:
o using JUnit runner instead of main() in test.
Revision ChangesPath
1.5 +6 -1 jbosstest/src/bin/bmptest.sh
Index: bmptest.sh
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/cts/test AllJUnitTests.java
Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.13 +8 -5
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/testbean/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.8 +37 -2
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/jrmp/test TestCustomSockets.java
TestDynLoading.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.3
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/security/test TestEJBSpec.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.7 +29 -2
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/readahead/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +32 -10
User: user57
Date: 01/07/05 19:29:22
Modified:src/main/org/jboss/test/web/test TestWebIntegration.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.8 +26 -2
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/util Deploy.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.4 +47 -27jbosstest/src/main/org/jboss/test/util/Deploy.java
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/perf/test TestProbe.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +29 -3
User: user57
Date: 01/07/05 19:29:21
Modified:src/main/org/jboss/test/naming/test TestENC.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.3 +23 -2
User: user57
Date: 01/07/05 19:29:19
Modified:src/main/org/jboss/test/bank/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +32 -5
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/dbtest/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.8 +27 -1
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/jmsra/test AllJUnitTests.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.4 +4 -3
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/hello/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +32 -3
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/idgen/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.2 +31 -4
User: user57
Date: 01/07/05 19:29:20
Modified:src/main/org/jboss/test/bmp/test Main.java
Log:
o Changed all tests which deploy one or more jars to undeploy after
testing.
Revision ChangesPath
1.3 +33 -8
Ok, please dont hang me, not now :-) I know that i'm not given you much details and no
clean and short testcase but i still wanted to trigger your brains to give me some
advice of how to preceed my debugging.
Fact: Using CVS brancs 2.4 from 2001-07-04. CMP entity beans, commit option A, tuned
Hi Ole
Thanx but I think this was not the intention in the
JSR-77 but just to know how your app. server
is doing.
For the other part you mentioned I would just
add an interceptor which keeps track off that
because I think you want to make this persistent
etc.
Have fun - Andy
- Original
Hi, guys
I posted previously about support for JSR-77 and enabling extensive
profiling/monitoring in JBoss. No one followed up on that, so I'll put in
my 2 cents worth of ideas in this thread.
I could not find the JSR-77 spec but have a bunch of ideas, please look at
my post
User: user57
Date: 01/07/05 20:17:09
Modified:src/main/org/jboss/configuration ConfigurationService.java
Log:
o using Log4j to log.
Revision ChangesPath
1.34 +11 -12jboss/src/main/org/jboss/configuration/ConfigurationService.java
Index:
User: user57
Date: 01/07/05 20:22:15
Modified:src/main/org/jboss/ejb ContainerFactory.java
Log:
Changed the name passed to Log.createLog() to a fq classname.
Revision ChangesPath
1.81 +2 -2 jboss/src/main/org/jboss/ejb/ContainerFactory.java
Index:
You must not be passing -classic to the jvm running JBoss as I use bugseeker
with a dual P3 500 with 512 Mb and its very fast. The jboss command line
should be:
set
DBG=-classic -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,addres
s=12345,suspend=y
java %DBG% -classpath %CLASSPATH%
User: user57
Date: 01/07/05 20:40:28
Modified:src/main/org/jboss/ejb/plugins
EnterpriseContextCachePolicy.java
Log:
o changed log category to org.jboss.ejb.plugins.BeanCache
Revision ChangesPath
1.6 +2 -3
|Not quite sure if I am off-track here, but:
|
|If you want to avoid loosing statistics, you
|might want to consider combining these two
|methods into a single atomic call.
|
|For example, if you want to count bean invocations,
|and do not want to drop a single invocation from
|your statistics.
Is there any reason why JBossMQ does not use the Log4j api for logging? I
am having a hard time tracking down this EOFException problem due to either
the lack of messages or a complete overload of them. If Log4j was used
here (with category names set to classnames), I could turn down the
|The only reason that I can think not to use Log4j is that we then force
|clients to have Log4j and configure it. Is that such a bad thing?
The only reason I can think of is that no one has coded it ;)
marcf
|
|--jason
|
|
|___
|Jboss-development
So are there any objections to changing all JBossMQ logging to Log4j? If
not then I am gonna do it, these System.out's are driving me crazy
(especially when mixed in with Log4j output).
--jason
On Fri, 6 Jul 2001, marc fleury wrote:
|The only reason that I can think not to use Log4j is that
not found :(
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Julian Gosnell
|Sent: Thursday, July 05, 2001 8:58 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] JBoss-2.4.0BETA_Jetty-3.1.RC5-3.zip - on it's
|way...
|
|
|
|This package should
The only reason log4j is not used is because no one has done it. Clients are
already required to use log4j if they want integration with the JBoss
logging
facility as of 2.4 so that is not a reason.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
Hi Anatoly
It was me that told you that deployement is part of another JSR.
I read you email again and I still see most of it as part of the
deployment which goes in the right direction for a full blown
J2EE app. server but I want just to make the small step to
provide some statistics out of
74 matches
Mail list logo
