Re: [JBoss-dev] org.jboss.mx.interceptor: Does it work?

2003-03-01 Thread Adrian Brock
Hi,

This would work if there was a way to configure it.
See the FIXME in ModelMBeanInvoker.preRegister
Regards,
Adrian
From: David Klimek [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] org.jboss.mx.interceptor: Does it work?
Date: Sat, 01 Mar 2003 12:05:38 +0100
Hello,

I have add logging to org.jboss.mx.interceptor.LogInterceptor but it seems 
that method invoke is never called.

public Object invoke(Invocation invocation) {
  long begin = System.currentTimeMillis();
  try {
 return getNext().invoke(invocation);
  } finally {
 logInvocation(invocation, begin, System.currentTimeMillis());
  }
}
The interceptor stack with LogInterceptor is created possibly in 
ModelMBeanInvoker.

Am I missing something or this part of jboss is just not finished.
I have done these experiments on JBoss3.2 RC1.
Does it work in HEAD?

Thank's
David
--
http://www.sweb.cz/david.klimek


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


_
MSN Messenger - fast, easy and FREE! http://messenger.msn.co.uk


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] org.jboss.mx.interceptor: Does it work?

2003-03-01 Thread David Klimek
Adrian Brock wrote:
 Hi,

 This would work if there was a way to configure it.
 See the FIXME in ModelMBeanInvoker.preRegister
Hi, thank you very much for help. My mistake.

Actually I had programaticaly add LogInterceptor into stack but below 
ObjectReferenceInterceptor so method invoke was not called.

bad code
...
  this.stack = new LogInterceptor(); // add LogInterceptor
  this.stack = new ObjectReferenceInterceptor(resource,
  infoSupport).insertLast(this.stack);

/bad code
David

From: David Klimek [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] org.jboss.mx.interceptor: Does it work?
Date: Sat, 01 Mar 2003 12:05:38 +0100
Hello,

I have add logging to org.jboss.mx.interceptor.LogInterceptor but it 
seems that method invoke is never called.

public Object invoke(Invocation invocation) {
  long begin = System.currentTimeMillis();
  try {
 return getNext().invoke(invocation);
  } finally {
 logInvocation(invocation, begin, System.currentTimeMillis());
  }
}
The interceptor stack with LogInterceptor is created possibly in 
ModelMBeanInvoker.

Am I missing something or this part of jboss is just not finished.
I have done these experiments on JBoss3.2 RC1.
Does it work in HEAD?

Thank's
David
--
http://www.sweb.cz/david.klimek


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


_
MSN Messenger - fast, easy and FREE! http://messenger.msn.co.uk


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



--
http://www.sweb.cz/david.klimek


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [ jboss-Bugs-693861 ] PooledInvoker has a memory leak

2003-03-01 Thread SourceForge.net
Bugs item #693861, was opened at 2003-02-26 19:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=693861group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bob Cotton (bcotton969)
Assigned to: Nobody/Anonymous (nobody)
Summary: PooledInvoker has a memory leak

Initial Comment:
I think I found the memory leak in the PooledInvoker.

org.jboss.invovation.pooled.server.ServerThread has an
ivar:
ObjectInputStream in;

I believe there is one ServerThread per client, and
each object read
from in.readObject() is stored in the ObjectInputStream
until that
stream is destroyed.

JProbe shows

ServerThread-
  (ObjectInputStream)in-
(ArrayList)wireHandle2Object-
  (Object[]) elementData-
(MarshalledInvocation)-
  (Object[])args-
(MyData)

The ObjectInputStream's ArrayList has a
MarshalledInvocation for every
call that was made from the client.

I don't see any public reset method on
ObjectInputStream, so It would
seem you would need to create a new one for every
invocation inside
the while(running) loop.

- Bob

--

Comment By: Bob Cotton (bcotton969)
Date: 2003-03-01 16:20

Message:
Logged In: YES 
user_id=424902

JProbe shows nothing on the server side. But I did re-create
the test. 3.2 branch from CVS, patch in 50 msgs/sec, patch
out 1000 msgs/sec.

- Bob

--

Comment By: Bob Cotton (bcotton969)
Date: 2003-02-28 22:22

Message:
Logged In: YES 
user_id=424902

yes, 25 times slower. I'm running under JProbe now. will
keep you updated.

- Bob

--

Comment By: Bill Burke (patriot1burke)
Date: 2003-02-28 21:23

Message:
Logged In: YES 
user_id=176497

25 times slower!!!/??  Doesn't make sense at all.  All I did was do 
ObjectOutputStream.reset and sent an extra byte over the wire.

Or are you saying the PooledInvoker allowed you to be 25 times 
faster?  Is there a typo there?

--

Comment By: Bob Cotton (bcotton969)
Date: 2003-02-28 21:13

Message:
Logged In: YES 
user_id=424902

I applied your changes to Branch.3.2 and my throughput
testing went from 1250 messages/sec to 50 messages/sec.

Attached is my patch for the backport to 3.2

This is based on today's cvs, branch 3.2

--

Comment By: Bill Burke (patriot1burke)
Date: 2003-02-26 20:07

Message:
Logged In: YES 
user_id=176497

Thanks man.  I knew there was a memory leak, I just couldn't find 
it.  Of course I was too lazy not to use optimizeit or something 
similar

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=693861group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] RARDeployment - what happened to it?

2003-03-01 Thread Nolan Wright
Thanks.  I was able to get things working by using the *-ds.xml.  One
question: if I have a service that depends on a data source, is there a
way I can specify that dependency?  


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
David Jencks
Sent: Friday, February 28, 2003 3:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] RARDeployment - what happened to it?

Not in jb4 you don't, it's been quite rewritten.  What exactly are you
having problems with?

You pretty much need to use the *-ds.xml files with jb4: if you want to
use
a *-service.xml file to deploy a datasource you need to include an
xmbean
configuration to deploy the ManagedConnectionFactory inside the
*-service.xml which is at best hard to understand for humans.

david jencks

On 2003.02.28 15:24 Tom Elrod wrote:
 What happened to the RARDeployment class that was in the
 org.jboss.resource.connectionmanager package?  Needed it for
connection
 pooling in data
 source xml.
 
 
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results: 1-March-2003

2003-03-01 Thread scott . stark


JBoss daily test results

SUMMARY

Number of tests run:   1089



Successful tests:  994

Errors:75

Failures:  20





[time of test: 2003-03-01.17-35 GMT]
[java.version: 1.4.1_01]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_01-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Windows 2000]
[os.arch: x86]
[os.version: 5.0]

See http://users.jboss.org/~starksm/HEAD/2003-03-01.17-35 for
the junit report of this test.

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   BankStressTestCase
Test:testTeller(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testBank(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testMultiThread(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testTransaction(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testTransfer(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testReadOnly(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testPassivation(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testFinder(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   BankStressTestCase
Test:testServerFound(org.jboss.test.bankiiop.test.BankStressTestCase)
Type:error
Exception:   java.rmi.RemoteException
Message: CORBA UNKNOWN 0 No; nested exception is:   org.omg.CORBA.UNKNOWN: 
org.omg.CORBA.portable.UnknownException  vmcid: 0x0  minor code: 0  completed: No
-



Suite:   CircularityUnitTestCase
Test:
testDuplicateClass(org.jboss.test.classloader.test.CircularityUnitTestCase)
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: java.lang.NullPointerException
-



Suite:   CircularityUnitTestCase
Test:testUCLOwner(org.jboss.test.classloader.test.CircularityUnitTestCase)
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: java.lang.IllegalStateException: T1 failed to load Class2
-



Suite:   CircularityUnitTestCase
Test:testLoading(org.jboss.test.classloader.test.CircularityUnitTestCase)
Type:error
Exception:   javax.management.RuntimeMBeanException
Message: 

[JBoss-dev] [ jboss-Bugs-692157 ] UnifiedClassLoader.getResources not working

2003-03-01 Thread SourceForge.net
Bugs item #692157, was opened at 2003-02-24 02:53
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=692157group_id=22866

Category: JBossMX
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Laurent Wozniak (lwozniak)
Assigned to: Scott M Stark (starksm)
Summary: UnifiedClassLoader.getResources not working

Initial Comment:
Hello,
I've just moved from JBoss 2.4.x to 3.0.x (3.0.4)
and found the following bug:
UnifiedClassLoader.getResources() does not return all the
resources under a specific name.

UnifiedClassLoader.getResource() can return a value while
UnifiedClassLoader.getResources() is returning an empty
enumeration for the same resource.

I looked in the source code and found that:
* UnifiedClassLoader inherit from URLClassLoader
* UnifiedClassLoader override getResource()
* UnifiedClassLoader does not override getResources()

java.lang.ClassLoader.getResources() is final but it calls
findResources() which is not.

UnifiedClassLoader.findResources() is simply not
implemented.
LoaderRepository does not implement this functionnality
either.

I've implemented the missing methods, now it works fine
on my local workstation.
But I don't know what I'm supposed to do to give you
the modifications I made.

Cheers,
Laurent


--

Comment By: Scott M Stark (starksm)
Date: 2003-03-01 10:34

Message:
Logged In: YES 
user_id=175228

The equivalent functionality has been added to the 3.0  and
higher branches.

--

Comment By: Laurent Wozniak (lwozniak)
Date: 2003-02-25 01:21

Message:
Logged In: YES 
user_id=719431

Here is the patch.
I've created it following the rules found at:
http://www.netbeans.org/devhome/community/contrib-patches.html


--

Comment By: Juha Lindfors (juhalindfors)
Date: 2003-02-24 04:13

Message:
Logged In: YES 
user_id=175239

create a diff of your local modified version against the version 
in the CVS and attach it


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=376685aid=692157group_id=22866


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] 4.0 and JDK 1.4.1 discussion

2003-03-01 Thread Hunter Hillegas
I've heard it is coming on Monday 3/3/03. We'll see.

Hunter

 From: Jason Dillon [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 Date: Sat, 1 Mar 2003 13:48:19 +0700
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] 4.0 and JDK 1.4.1 discussion
 
 Still waiting for a final for Mac OS X :(



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 1-March-2003

2003-03-01 Thread scott . stark


JBoss daily test results

SUMMARY

Number of tests run:   1137



Successful tests:  1131

Errors:6

Failures:  0





[time of test: 2003-03-01.18-50 GMT]
[java.version: 1.4.1_01]
[java.vendor: Sun Microsystems Inc.]
[java.vm.version: 1.4.1_01-b01]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Windows 2000]
[os.arch: x86]
[os.version: 5.0]

Useful resources:

- http://users.jboss.org/~starksm/Branch_3_2/2003-03-01.18-50 for
the junit report of this test.


NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   SecurityUnitTestCase
Test:runValidDynDurSub(org.jboss.test.jbossmq.test.SecurityUnitTestCase)
Type:error
Exception:   java.lang.InternalError
Message: Test timeout
-



Suite:   DeployXMBeanUnitTestCase
Test:testDeployUserXMBean(org.jboss.test.jmx.test.DeployXMBeanUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested 
throwable: (org.jboss.deployment.DeploymentException: Error parsing the XML file: 
org.xml.sax.SAXParseException: Attribute persistPolicy with value Never must have 
a value from the list NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER .; - nested throwable: 
(javax.management.NotCompliantMBeanException: Error parsing the XML file: 
org.xml.sax.SAXParseException: Attribute persistPolicy with value Never must have 
a value from the list NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER .))
-



Suite:   MissingClassUnitTestCase
Test:
testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: create operation failed for package 
file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - 
nested throwable: (javax.management.InstanceNotFoundException: 
jboss.test:name=missingclasstest is not registered.)
-



Suite:   JSR77SpecUnitTestCase
Test:testNavigation(org.jboss.test.management.test.JSR77SpecUnitTestCase)
Type:error
Exception:   javax.management.InstanceNotFoundException
Message: 
jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar
 is not registered.
-



Suite:   HttpsUnitTestCase
Test:testJSSE(org.jboss.test.security.test.HttpsUnitTestCase)
Type:error
Exception:   java.net.BindException
Message: Address already in use: JVM_Bind
-



Suite:   SRPUnitTestCase
Test:testEchoArgs(org.jboss.test.security.test.SRPUnitTestCase)
Type:error
Exception:   java.lang.reflect.UndeclaredThrowableException
Message: 
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 1-March-2003

2003-03-01 Thread scott . stark


JBoss daily test results

SUMMARY

Number of tests run:   1049



Successful tests:  1044

Errors:1

Failures:  4





[time of test: 2003-03-01.12-05 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1_03-69]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.2.4]

See http://users.jboss.org/~starksm/Branch_3_0/2003-03-01.12-05
for details of this test. 

NOTE: If there are any errors shown above - this mail is only highlighting 
them - it is NOT indicating that they are being looked at by anyone.

It is assumed that whoever makes change(s) to jboss that 
break the test will be fixing the test or jboss, as appropriate!





DETAILS OF ERRORS



Suite:   MissingClassUnitTestCase
Test:
testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase)
Type:error
Exception:   org.jboss.deployment.DeploymentException
Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: 
(javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not 
registered.)
-



Suite:   SecurityUnitTestCase
Test:testSecureHttpInvoker(org.jboss.test.naming.test.SecurityUnitTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   SecurityUnitTestCase
Test:
testSecureHttpInvokerFailure(org.jboss.test.naming.test.SecurityUnitTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Should not have been able to lookup(invokers)
-



Suite:   BeanStressTestCase
Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: expected a client deadlock for AB BA
-



Suite:   HelloClusteredHttpStressTestCase
Test:testCNFEObject(org.jboss.test.hello.test.HelloClusteredHttpStressTestCase)
Type:failure
Exception:   junit.framework.AssertionFailedError
Message: Was able to invoke remove
-




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Build system speed improvements

2003-03-01 Thread Jason Dillon
I just committed a tiny change to the build system which allows a 
module to bypass the compile/output phase when the module has already 
been built and is up to date.

It works using the uptodate task and checking the ${module.source} 
tree, module build files and project build files against a build marker 
(output/build-marker) which is created/touched at the end of the output 
generation target.

I am seeing a 5x speed increase when rebuilding an already built 
project (30s vs 2m 30s) .  Normally this will never happen, but it will 
still speed up project builds when only one or two modules change.

If you want to turn this functionality off you can set 
build-bypass.disabled=true on the command line or in local.properties.

Lastly I only updated the build.xml files for modules which are part of 
the default build.  Feel free to update the other modules as needed.  
Something similar might make the testsuite much easier to run over and 
over... who knows.

As always I tested this on my machine, but shit happens... to me... a 
lot.  If this totally breaks your build please let me know.  I do not 
think it will, it is small and uses standard Ant.

--jason



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] A problem on JBOSS 3.2.0 RC2

2003-03-01 Thread caigao
hi, everyone.
I had test the JBossTemplateSamples on JBoss 3.0.4, they work well,
but when i test the cmp2 program in JBoss 3.2.0 RC2 it throw a
Exception.
I had build and deploy the ganster-cmp2.jar into the deploy
directory, when i take an ant setup it throws this:

/*
[junit] 1)
testSetUp(org.jboss.docs.cmp2.crimeportal.CrimePortalSetUp)
[junit] javax.naming.NameNotFoundException: EJBTestRunner not bound
[junit] at
org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
[junit] at
org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
[junit] at
org.jnp.server.NamingServer.getObject(NamingServer.java:509)
[junit] at
org.jnp.server.NamingServer.lookup(NamingServer.java:282)
[junit] at
org.jnp.server.NamingServer.lookup(NamingServer.java:256)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
*/

the platform is Redhat Linux 8 and jdk1.4.1_01 and JBoss-Tomcat 3.2.0
RC2.but the same env in Windows XP platform is work fine.When I take
ant setup and ant test ant ant test-gui in Windows XP there have
no problem.
WHY???
thanks.




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] RARDeployment - what happened to it?

2003-03-01 Thread David Jencks
Sure.  The *-ds.xml file gets xsl-transformed into 3 mbeans/datasource, so
just pick the ConnectionManager one and depend on it.  You can find the
exact object name in the jmx-console after you deploy the *-ds.xml file.

david

On 2003.03.01 11:16 Nolan Wright wrote:
 Thanks.  I was able to get things working by using the *-ds.xml.  One
 question: if I have a service that depends on a data source, is there a
 way I can specify that dependency?  
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 David Jencks
 Sent: Friday, February 28, 2003 3:43 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] RARDeployment - what happened to it?
 
 Not in jb4 you don't, it's been quite rewritten.  What exactly are you
 having problems with?
 
 You pretty much need to use the *-ds.xml files with jb4: if you want to
 use
 a *-service.xml file to deploy a datasource you need to include an
 xmbean
 configuration to deploy the ManagedConnectionFactory inside the
 *-service.xml which is at best hard to understand for humans.
 
 david jencks
 
 On 2003.02.28 15:24 Tom Elrod wrote:
  What happened to the RARDeployment class that was in the
  org.jboss.resource.connectionmanager package?  Needed it for
 connection
  pooling in data
  source xml.
  
  
  
  
  
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 
 


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-01 Thread chris

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

org.jboss.ejb.EJBDeployer -- EJBDeployerMBean qualified to EJBDeployerMBean
org.jboss.ejb.ContainerPlugin -- Service qualified to Service
org.jboss.ejb.InstanceCache -- StatisticsProvider qualified to StatisticsProvider
org.jboss.ejb.EntityEnterpriseContext -- EJBContextImpl qualified to EJBContextImpl
org.jboss.invocation.Invoker -- Remote qualified to Remote
org.jboss.ejb.StatefulSessionContainer -- AbstractContainerInterceptor qualified to 
AbstractContainerInterceptor
org.jboss.ejb.EjbModule -- EjbModuleMBean qualified to EjbModuleMBean
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager -- 
StatefulSessionFilePersistenceManagerMBean qualified to 
StatefulSessionFilePersistenceManagerMBean
org.jboss.ejb.timer.AbstractTimerSource -- AbstractTimerSourceMBean qualified to 
AbstractTimerSourceMBean
org.jboss.ejb.timer.FilePersistenceManager -- FilePersistenceManagerMBean qualified 
to FilePersistenceManagerMBean
org.jboss.ejb.timer.SchedulerTimerSource -- SchedulerTimerSourceMBean qualified to 
SchedulerTimerSourceMBean
org.jboss.invocation.InvokerXAResource -- InvokerXAResourceMBean qualified to 
InvokerXAResourceMBean
org.jboss.invocation.XATerminatorContainer -- XATerminatorContainerMBean qualified to 
XATerminatorContainerMBean
org.jboss.invocation.http.server.HttpInvokerMBean -- ServiceMBean qualified to 
ServiceMBean
org.jboss.invocation.local.LocalInvoker -- LocalInvokerMBean qualified to 
LocalInvokerMBean
org.jboss.invocation.jrmp.server.JRMPInvoker -- JRMPInvokerMBean qualified to 
JRMPInvokerMBean
org.jboss.invocation.pooled.server.PooledInvoker -- PooledInvokerMBean qualified to 
PooledInvokerMBean
org.jboss.invocation.trunk.client.ConnectionManager -- ConnectionManagerMBean 
qualified to ConnectionManagerMBean
org.jboss.invocation.trunk.client.TrunkInvokerProxy -- TrunkInvokerProxyMBean 
qualified to TrunkInvokerProxyMBean
org.jboss.invocation.trunk.server.TrunkInvoker -- TrunkInvokerMBean qualified to 
TrunkInvokerMBean
org.jboss.jms.asf.ServerSessionPoolLoader -- ServerSessionPoolLoaderMBean qualified 
to ServerSessionPoolLoaderMBean
org.jboss.jms.jndi.JMSProviderLoader -- JMSProviderLoaderMBean qualified to 
JMSProviderLoaderMBean
org.jboss.jmx.connector.RemoteMBeanServer -- MBeanServer qualified to MBeanServer
org.jboss.jmx.connector.notification.JMSNotificationListener -- 
JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean
org.jboss.jmx.connector.notification.RMINotificationListener -- 
RMINotificationListenerMBean qualified to RMINotificationListenerMBean
org.jboss.jmx.adaptor.rmi.RMIAdaptorService -- RMIAdaptorServiceMBean qualified to 
RMIAdaptorServiceMBean
org.jboss.jmx.adaptor.xml.XMLAdaptorService -- XMLAdaptorServiceMBean qualified to 
XMLAdaptorServiceMBean
org.jboss.jmx.adaptor.xml.XMLTestService -- XMLTestServiceMBean qualified to 
XMLTestServiceMBean
org.jboss.jmx.connector.rmi.RMIConnectorImpl -- RMIConnectorImplMBean qualified to 
RMIConnectorImplMBean
org.jboss.jmx.connector.ejb.EJBConnector -- EJBConnectorMBean qualified to 
EJBConnectorMBean
org.jboss.jmx.connector.ConnectorFactoryService -- ConnectorFactoryServiceMBean 
qualified to ConnectorFactoryServiceMBean
org.jboss.jmx.connector.notification.PollingNotificationListener -- 
PollingNotificationListenerMBean qualified to PollingNotificationListenerMBean
org.jboss.logging.Log4jService -- Log4jServiceMBean qualified to Log4jServiceMBean
org.jboss.logging.Log4jSocketServer -- Log4jSocketServerMBean qualified to 
Log4jSocketServerMBean
org.jboss.naming.ExternalContext -- ExternalContextMBean qualified to 
ExternalContextMBean
org.jboss.naming.JNDIView -- JNDIViewMBean qualified to JNDIViewMBean
org.jboss.naming.NamingAlias -- NamingAliasMBean qualified to NamingAliasMBean
org.jboss.naming.NamingService -- NamingServiceMBean qualified to NamingServiceMBean
org.jboss.web.AbstractWebContainer -- AbstractWebContainerMBean qualified to 
AbstractWebContainerMBean
WARNING: Some classes refer to other classes that were not found among the sources or 
on the classpath.
 (Perhaps the referred class doesn't exist? Hasn't been generated yet?)
 The referring classes do not import any fully qualified classes matching 
these classes.
 Since at least one package is imported, it is impossible for xjavadoc to 
figure out
 what package the referred classes belong to. The classes are:
org.jboss.web.WebService -- WebServiceMBean qualified to WebServiceMBean

BUILD FAILED

[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed

2003-03-01 Thread chris

=
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS=
=

JAVA VERSION DETAILS
java version 1.3.1_06
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01)
Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode)

=

HERE ARE THE LAST 50 LINES OF THE LOG FILE

org.jboss.ejb.EJBDeployer -- EJBDeployerMBean qualified to EJBDeployerMBean
org.jboss.ejb.ContainerPlugin -- Service qualified to Service
org.jboss.ejb.InstanceCache -- StatisticsProvider qualified to StatisticsProvider
org.jboss.ejb.EntityEnterpriseContext -- EJBContextImpl qualified to EJBContextImpl
org.jboss.invocation.Invoker -- Remote qualified to Remote
org.jboss.ejb.StatefulSessionContainer -- AbstractContainerInterceptor qualified to 
AbstractContainerInterceptor
org.jboss.ejb.EjbModule -- EjbModuleMBean qualified to EjbModuleMBean
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager -- 
StatefulSessionFilePersistenceManagerMBean qualified to 
StatefulSessionFilePersistenceManagerMBean
org.jboss.ejb.timer.AbstractTimerSource -- AbstractTimerSourceMBean qualified to 
AbstractTimerSourceMBean
org.jboss.ejb.timer.FilePersistenceManager -- FilePersistenceManagerMBean qualified 
to FilePersistenceManagerMBean
org.jboss.ejb.timer.SchedulerTimerSource -- SchedulerTimerSourceMBean qualified to 
SchedulerTimerSourceMBean
org.jboss.invocation.InvokerXAResource -- InvokerXAResourceMBean qualified to 
InvokerXAResourceMBean
org.jboss.invocation.XATerminatorContainer -- XATerminatorContainerMBean qualified to 
XATerminatorContainerMBean
org.jboss.invocation.http.server.HttpInvokerMBean -- ServiceMBean qualified to 
ServiceMBean
org.jboss.invocation.local.LocalInvoker -- LocalInvokerMBean qualified to 
LocalInvokerMBean
org.jboss.invocation.jrmp.server.JRMPInvoker -- JRMPInvokerMBean qualified to 
JRMPInvokerMBean
org.jboss.invocation.pooled.server.PooledInvoker -- PooledInvokerMBean qualified to 
PooledInvokerMBean
org.jboss.invocation.trunk.client.ConnectionManager -- ConnectionManagerMBean 
qualified to ConnectionManagerMBean
org.jboss.invocation.trunk.client.TrunkInvokerProxy -- TrunkInvokerProxyMBean 
qualified to TrunkInvokerProxyMBean
org.jboss.invocation.trunk.server.TrunkInvoker -- TrunkInvokerMBean qualified to 
TrunkInvokerMBean
org.jboss.jms.asf.ServerSessionPoolLoader -- ServerSessionPoolLoaderMBean qualified 
to ServerSessionPoolLoaderMBean
org.jboss.jms.jndi.JMSProviderLoader -- JMSProviderLoaderMBean qualified to 
JMSProviderLoaderMBean
org.jboss.jmx.connector.RemoteMBeanServer -- MBeanServer qualified to MBeanServer
org.jboss.jmx.connector.notification.JMSNotificationListener -- 
JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean
org.jboss.jmx.connector.notification.RMINotificationListener -- 
RMINotificationListenerMBean qualified to RMINotificationListenerMBean
org.jboss.jmx.adaptor.rmi.RMIAdaptorService -- RMIAdaptorServiceMBean qualified to 
RMIAdaptorServiceMBean
org.jboss.jmx.adaptor.xml.XMLAdaptorService -- XMLAdaptorServiceMBean qualified to 
XMLAdaptorServiceMBean
org.jboss.jmx.adaptor.xml.XMLTestService -- XMLTestServiceMBean qualified to 
XMLTestServiceMBean
org.jboss.jmx.connector.rmi.RMIConnectorImpl -- RMIConnectorImplMBean qualified to 
RMIConnectorImplMBean
org.jboss.jmx.connector.ejb.EJBConnector -- EJBConnectorMBean qualified to 
EJBConnectorMBean
org.jboss.jmx.connector.ConnectorFactoryService -- ConnectorFactoryServiceMBean 
qualified to ConnectorFactoryServiceMBean
org.jboss.jmx.connector.notification.PollingNotificationListener -- 
PollingNotificationListenerMBean qualified to PollingNotificationListenerMBean
org.jboss.logging.Log4jService -- Log4jServiceMBean qualified to Log4jServiceMBean
org.jboss.logging.Log4jSocketServer -- Log4jSocketServerMBean qualified to 
Log4jSocketServerMBean
org.jboss.naming.ExternalContext -- ExternalContextMBean qualified to 
ExternalContextMBean
org.jboss.naming.JNDIView -- JNDIViewMBean qualified to JNDIViewMBean
org.jboss.naming.NamingAlias -- NamingAliasMBean qualified to NamingAliasMBean
org.jboss.naming.NamingService -- NamingServiceMBean qualified to NamingServiceMBean
org.jboss.web.AbstractWebContainer -- AbstractWebContainerMBean qualified to 
AbstractWebContainerMBean
WARNING: Some classes refer to other classes that were not found among the sources or 
on the classpath.
 (Perhaps the referred class doesn't exist? Hasn't been generated yet?)
 The referring classes do not import any fully qualified classes matching 
these classes.
 Since at least one package is imported, it is impossible for xjavadoc to 
figure out
 what package the referred classes belong to. The classes are:
org.jboss.web.WebService -- WebServiceMBean qualified to WebServiceMBean

BUILD FAILED