===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Bugs item #880191, was opened at 2004-01-19 22:48
Message generated for change (Comment added) made by cazzius
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=880191group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Bugs item #849786, was opened at 2003-11-26 18:10
Message generated for change (Comment added) made by cazzius
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=849786group_id=22866
Category: JBossServer
Group: v3.2
Status: Closed
Resolution: Fixed
Priority:
Bugs item #880447, was opened at 2004-01-20 09:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=880447group_id=22866
Category: JBossServer
Group: v4.0
Status: Open
Resolution:
Hi people.
I'm new to the list, and new to CMP/CMR ejbs (I used Jboss 2.4 until now,
mostly with BMPs).
I try to to have a 1:N relationship between two beans, (SupportPackCMP and
PeripheralCMP), using Xdoclet tags. I'd like tables to be created by the
app. server
When I deploy under JBoss 3.2.3, I
Hi,
JBoss-User list is the right place to ask user questions. This list is
reserved for development discussions.
-- juha
On Tue, 20 Jan 2004 [EMAIL PROTECTED] wrote:
Hi people.
I'm new to the list, and new to CMP/CMR ejbs (I used Jboss 2.4 until now,
mostly with BMPs).
I try to to have a
Scott M Stark wrote:
This has been fixed by only unregistering the deployment UCL if the deployment
actually created the UCL as opposed to inherit the UCL from its containing
deployment. The current NPE behavior is an artifact of class loading that
is ocurring now, not any specific behavior
the jmx module unit tests are the ones we run against, the ones in
testsuite were never maintained.
At least 3 of the 4 failures on compliance are known issues (and reported
as such), I don't know about the JMX 1.2 notification emitter one.
The two errors are both related to classloading, at
Bugs item #880191, was opened at 2004-01-19 14:48
Message generated for change (Comment added) made by ioparra
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=880191group_id=22866
Category: JBossMX
Group: v3.2
Status: Closed
Resolution: Fixed
Priority: 5
Bugs item #877172, was opened at 2004-01-14 16:59
Message generated for change (Comment added) made by javajedi
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=877172group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
I'm looking into the testcase failure related to ModelMBean persistence
and the problem as stated earlier is that the attribute
interceptor/context
ModelAttributeInfo and descriptor are copies that are detached from the
ModelMBean. Hence, changes to the attribute do not result in changes in
the
If I follow what you're trying to do correctly, the reason for the bug is
that the context map descriptors are updated but the info reference we
return from getMBeanInfo is not,
in AbstractMBeanInvoker, for setters there's a finally block at the end
that updates the context maps on the return of
Out of these failures, the following need to be resolved before the
3.2.4RC1 release:
Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase
Test:testStrictPooling
Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase
Test:testUserXMBeanPersistentValues
Suite:
Is this enough as there are several places copies are being introduced:
- AbstractMBeanInvoker.preRegister
+ This calls initAttributeContexts(info.getAttributes());, which
makes a copy of
the MBeanAttributeInfo[]
- ModelMBeanInvoker.initAttributeContexts
+ This calls
I am looking into deadlock.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Scott M Stark
Sent: Tuesday, January 20, 2004 11:34 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2
WonderLand) Testsuite Results:
Since the spec requires a copy to be returned I think the only way to
avoid it is to create a JBoss specific impl. as you suggested in the
previous post.
-- Juha
On Tue, 20 Jan 2004, Scott M Stark wrote:
Is this enough as there are several places copies are being introduced:
-
What are the other 3 known compliance issues? 3.2 and head should be in
synch
on class loaders and I need to merge some of the changes made to the jmx
layer so I want to get these test working before doing the merge.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
In doing some testing of the RequiredModelMBean in the jmx 1.2.1RI
and our codebase, I see that we require a resource while the RI
does not. We allow the resource to simply be a new Object(), but
its not clear whether this is too strict.
Scott Stark
Chief Technology
JBOSS-HEAD:
/cygdrive/d/jboss-head/jmx
$ sh build.sh test-compliance-JBossMX
Searching for build.xml ...
Buildfile: d:\jboss-head\jmx\build.xml
...
[java] 1) testNotificationEmitterRemoveTripletFailsOnBroadcaster
(test.compliance.server.MBeanServerInvocationHandlerTestCase)
Bugs item #877172, was opened at 2004-01-14 13:59
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=877172group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
This does seem to be sufficient and the persistent attribute testcase in
the failing DeployXMBeanUnitTestCase is now working.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
There's a difference in running the JMX compliance suite between 3.2.3-RC2
checkout and the current 3.2.4-RC1 checkout (with JMX 1.2 head backport)
3.2.3-RC2
=
[EMAIL PROTECTED] /cygdrive/d/jboss-323-RC2/jboss-3.2/jmx
$ sh build.sh test-compliance-JBossMX
Searching for build.xml ...
Great, I can still read Java code then ;-)
-- Juha
On Tue, 20 Jan 2004, Scott M Stark wrote:
This does seem to be sufficient and the persistent attribute testcase in
the failing DeployXMBeanUnitTestCase is now working.
Scott Stark
Chief Technology Officer
Bugs item #860175, was opened at 2003-12-14 22:35
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=860175group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: Remind
Priority: 5
Bugs item #881012, was opened at 2004-01-20 20:10
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=881012group_id=22866
Category: Clustering
Group: v3.2
Status: Open
Resolution:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Sometimes, running deadlock test I see
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at java.util.ArrayList.ensureCapacity(ArrayList.java:170)
at java.util.ArrayList.add(ArrayList.java:354)
at
In java.lang.System.arraycopy...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Alexey Loubyansky
Sent: Wednesday, January 21, 2004 3:44 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2
WonderLand) Testsuite
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Not likely. I would guess this is due to concurrent access to the
unsynchronized threads ArrayList. What is the full stack that producing
this error?
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL
Bugs item #881012, was opened at 2004-01-20 17:10
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=881012group_id=22866
Category: Clustering
Group: v3.2
Status: Closed
Resolution: Invalid
Bugs item #881012, was opened at 2004-01-20 20:10
Message generated for change (Settings changed) made by macronetics
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=881012group_id=22866
Category: Clustering
Group: v3.2
Status: Open
Resolution: Invalid
Bugs item #881012, was opened at 2004-01-20 20:10
Message generated for change (Comment added) made by macronetics
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=881012group_id=22866
Category: Clustering
Group: v3.2
Status: Open
Resolution: Invalid
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
Bugs item #881012, was opened at 2004-01-20 17:10
Message generated for change (Comment added) made by starksm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=881012group_id=22866
Category: Clustering
Group: v3.2
Status: Closed
Resolution: Invalid
37 matches
Mail list logo
