Number of tests run: 669
Successful tests: 665
Errors:4
Failures: 0
[time of test: 14 July 2002 0:31 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
Bugs item #575946, was opened at 2002-07-01 05:51
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=575946group_id=22866
Category: JBossSX
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Bruno Lowagie (blowagie)
Assigned to: Scott M
Bugs item #575967, was opened at 2002-07-01 07:00
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=575967group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Bruno Lowagie (blowagie)
David Jencks wrote:
I still need to find out why the autoredeploy is giving problems...
I had posted this on forums on the JBoss site, but not here, so FWIW,
here is my analysis of hot-deployment problems on JBoss 3.0.0. I have
recently managed to get HEAD to build on my machine (was using
hi,
i have a problem using jboss2.4.4 server with postgresql 7.x.
when i start a server, it runs perfectly for an hour or two. after
some time, it starts throwing XAException. actually the
application is not closing but the data is not updating to the
database.
some times if i give small
It's amazing, guys go to the pain of subscribing here and then post user
questions.
Please ignore
Thanks
marcf
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On
Behalf Of ravindra v
Sent: Sunday, July 14, 2002 6:21 AM
To: [EMAIL PROTECTED]
Subject:
Scott,
Let's give this bruno guy RW, I like guys that posts solutions to the
bugs repository :)
marcf
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On
Behalf Of [EMAIL PROTECTED]
Sent: Sunday, July 14, 2002 5:14 AM
To: [EMAIL PROTECTED]
Subject:
In both 3.0 and 3.1 the specification of the invoker to use for a
bean is being done in the enterprise-beans element rather than in a
container-configuration element. The invoker(s) is really more of a
container config element associated with the client interceptor stack
which is defined in the
Scott,
It is very useful having this automated posting and I use it to double
check that my changes haven't broken anything
Is there any chance of fixing the URLs so that we can check if it is our
module that is responsible for the errors/failures
Cheers,
Jules
In both 3.0 and 3.1 the specification of the invoker to use
for a bean is being done in the enterprise-beans element
rather than in a container-configuration element. The
invoker(s) is really more of a container config element
associated with the client interceptor stack which is defined
There is a chance once I get done with the first draft of the 3.0 docs.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jules Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent:
The enterprise-beans section should be for deployment bindings from
the ejb-jar.xml/enterprise-beans section. The invocation protocol for all
stateless session beans should be defined at a container related level,
not a particular instance of a session bean. Right now we have
functionally related
What I would like to see is something like this:
jboss
enterprise-beans
session
ejb-nameMySession/ejb-name
configuration-nameStandard Stateless
SessionBean/configuration-name
client-configuration-names
Number of tests run: 619
Successful tests: 594
Errors:23
Failures: 2
[time of test: 14 July 2002 12:30 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
The
invocation protocol for all stateless session beans should be
defined at a container related level, not a particular
Negative, detached invokers.
In the future you will configure your client at the JMX level. Saying
for this client give me this interface, this stack of client
This is pretty much what we have in 3.1. Look at the jboss.xml file of
the hellojrmpiiop test:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbosstest/src/resources/hellojrmpiiop/META-INF/jboss.xml?rev=1.1content-type=text/vnd.viewcvs-markup
Cheers,
Francisco
On Sun, 14 Jul 2002, Scott
Hi,
could it be possible that there is an error in the MainDeployer? Assume the following
scenario:
ear
war (references jar1 and jar2 via manifest)
jar1 - contains ejb/normal classes
jar2 - same as above
The MainDeployer loads the ear and extracts the war. It assigns a
Number of tests run: 669
Successful tests: 664
Errors:4
Failures: 1
[time of test: 14 July 2002 14:59 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
Ok, I see what 3.1 is doing and that looks good. I'm going to try
to have 3.0.1 be similar sans the multiple invokers.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Francisco Reverbel [EMAIL PROTECTED]
19 matches
Mail list logo
