RE: [JBoss-dev] FW: [jboss-cvs] build/jboss ...

2006-03-18 Thread Francisco Reverbel
Ok, thanks. Comment added.

On Fri, 2006-03-17 at 03:59 -0600, Dimitris Andreadis wrote:
 http://jira.jboss.com/jira/browse/JBAS-2955
 
 If Franscisco wants to add any comments on the upgrade. 
 
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On 
  Behalf Of Scott M Stark
  Sent: 16 March, 2006 21:12
  To: jboss-development@lists.sourceforge.net; Francisco Reverbel
  Subject: RE: [JBoss-dev] FW: [jboss-cvs] build/jboss ...
  
  Yes. 
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On Behalf Of 
   Ryan Campbell
   Sent: Thursday, March 16, 2006 10:45 AM
   To: Francisco Reverbel
   Cc: jboss-development@lists.sourceforge.net
   Subject: [JBoss-dev] FW: [jboss-cvs] build/jboss ...
   
   We need a JIRA task in the JBAS project for any 3rd party library 
   upgrades so that they show up in the changelog, right?
   
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] On Behalf Of 
   Francisco Reverbel
   Sent: Thursday, March 16, 2006 12:02 AM
   To: [EMAIL PROTECTED]
   Subject: [jboss-cvs] build/jboss ...
   
 User: reverbel
 Date: 06/03/16 01:01:30
   
 Modified:jbossTag: Branch_4_0 build-thirdparty.xml
 Log:
 JacORB upgrade to release 2.2.3.
 
 Revision  ChangesPath
 No   revision
 
 
 No   revision
 
 
 1.1.2.83  +1 -1  build/jboss/build-thirdparty.xml
 
 (In the diff below, changes in quantity of whitespace are not 
   shown.)
 
 Index: build-thirdparty.xml
 
  ===
 RCS file: /cvsroot/jboss/build/jboss/build-thirdparty.xml,v
 retrieving revision 1.1.2.82
 retrieving revision 1.1.2.83
 diff -u -b -r1.1.2.82 -r1.1.2.83
 --- build-thirdparty.xml6 Mar 2006 06:23:25 -   1.1.2.82
 +++ build-thirdparty.xml16 Mar 2006 06:01:30 -  1.1.2.83
 @@ -87,7 +87,7 @@
componentref name=hibernate-entitymanager
   version=3.1beta6/
componentref name=hsqldb version=1.8.0.2/
componentref name=ibm-wsdl4j version=1.5.2/
 -  componentref name=jacorb version=2.2.1jboss/
 +  componentref name=jacorb version=2.2.3/
componentref name=javassist version=3.1RC2/
componentref name=jaxen version=1.1beta4/
componentref name=jboss/aop version=1.3.4/
 
 
 
   
   
   ---
   This SF.Net email is sponsored by xPML, a groundbreaking scripting 
   language that extends applications into web and mobile 
  media. Attend 
   the live webcast and join the prime developer group 
  breaking into this 
   new coding territory!
   http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720;
   dat=121642
   ___
   jboss-cvs-commits mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
   
   
   ---
   This SF.Net email is sponsored by xPML, a groundbreaking scripting 
   language that extends applications into web and mobile 
  media. Attend 
   the live webcast and join the prime developer group 
  breaking into this 
   new coding territory!
   http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
   ___
   JBoss-Development mailing list
   JBoss-Development@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/jboss-development
   
  
  
  ---
  This SF.Net email is sponsored by xPML, a groundbreaking 
  scripting language that extends applications into web and 
  mobile media. Attend the live webcast and join the prime 
  developer group breaking into this new coding territory!
  http://sel.as-us.falkag.net/sel?cmd=kkid0944bid$1720dat1642
  ___
  JBoss-Development mailing list
  JBoss-Development@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] Moving org.jboss.naming.* from server into naming module

2006-02-28 Thread Francisco Reverbel
+1

I ran into the very same issue while working on the DTM. See 

   http://jira.jboss.com/jira/browse/JBAS-2190

Regards,

Francisco

On Mon, 2006-02-27 at 15:26 -0600, Scott M Stark wrote:
 We have a number of org.jnp.interfaces.NamingContextFactory subclasses
 that are in the server module which should really be in the naming
 module to avoid unnecessary dependencies on the server module, and
 jboss.jar:
 
 org.jboss.naming.BridgeNamingContextFactory
 org.jboss.naming.NamingContextFactory
 org.jboss.iiop.naming.ORBInitialContextFactory
 
 The issue came up when looking at these security related variations
 which should subclass the org.jboss.naming.NamingContextFactory version
 to pickup its ability to remember non-default InitialContextFactory
 environment settings:
 org.jboss.security.jndi.LoginInitialContextFactory
 org.jboss.security.jndi.JndiLoginInitialContextFactory
 
 I'm tempted to move all of the server org.jboss.naming.* classes into
 the naming module to avoid spliting this package across jars, but there
 jboss-system dependencies, and jmx dependencies that require further
 refactoring. It should probably be done anyway in preparation for the mc
 migration. I'll wait a day for feedback before starting this move. If I
 do move this over to naming I want to move the cvs history along with
 it.
 
 
 Scott Stark
 VP Architecture  Technology
 JBoss Inc.
  
  
 
 
 ---
 This SF.Net email is sponsored by xPML, a groundbreaking scripting language
 that extends applications into web and mobile media. Attend the live webcast
 and join the prime developer group breaking into this new coding territory!
 http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642
 ___
 JBoss-Development mailing list
 JBoss-Development@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/jboss-development



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk

2006-02-14 Thread Francisco Reverbel
Yes, I see that the VerifyError is thrown when you run the IDL compiler.
It looks like a JVM bug.

Even though I know JacORB's implementation of the ORB run-time library
fairly well, I have never looked at the IDL compiler. Do you know if a
VerifyError also happens at run time, with JacORB's ORB on a 64-bit JVM?
Or the problem happens only during IDL compilation?
 
On Mon, 2006-02-13 at 17:11 -0600, Ryan Campbell wrote:
 Francisco,
 
  
 
 Just to make it clear, we are trying to build JBoss on 64bit JVM’s and
 we get this fatal exception when trying to run the jacorb parser:
 
  
 
 Exception in thread main java.lang.VerifyError: (class: 
 org/jacorb/idl/parser,
 method: clinit signature: ()V) Call to wrong initialization method 
 
  
 
 Can you patch this?  We aren’t getting a response from the jacorb
 list.
 
  
 

 __
 From:[EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Rajesh Rajasekaran
 Sent: Monday, February 13, 2006 5:04 PM
 To: jboss-development@lists.sourceforge.net
 Cc: Francisco Reverbel
 Subject: [JBoss-dev] FW: Could not run jacorb on 64 bit jdk
 
 
  
 
  
 
  
 

 __
 From: Rajesh Rajasekaran 
 Sent: Friday, February 10, 2006 12:05 PM
 To: '[EMAIL PROTECTED]'
 Subject: Could not run jacorb on 64 bit jdk
 
 
  
 
 This is related to the bug #468
 
 http://www.jacorb.org/cgi-bin/bugzilla/long_list.cgi?buglist=468
 
  
 
 We are trying to support Jboss on 64 bit jdk’s and this bug is a major
 blocker.
 
 A fix for this ASAP would help us proceed with our process.
 
  
 
 Thanks
 
 Rajesh 
 
 JBoss QA
 
 



---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JTA and JTS on JBoss] - Re: Where should UserTransaction live?

2005-04-24 Thread reverbel
Some usertx classes have dependencies on other server module classes, so for 
now I have moved to the transaction module just the class 
ServerVMClientUserTransaction. The remaining usertx classes are still in the 
server module.

Francisco


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875187#3875187

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875187


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of the JBoss EJB Container] - Inter-server ejb-refs?

2005-04-24 Thread reverbel
Does JBoss support  inter-server ejb-refs in the non-IIOP case? 

In the IIOP case, this jboss.xml excerpt speficies an ejb-ref to an EJB 
deployed in the JBoss server running in another host (some.host.name) and bound 
to the name the/remote/BeanName in that server's CosNaming service:

  | ejb-ref
  |ejb-ref-namesome/local/Name/ejb-ref-name
  |jndi-namecorbaname:iiop:[EMAIL 
PROTECTED]:3628#the/remote/BeanName/jndi-name
  | /ejb-ref
  | 

Can I do a similar thing in the non-IIOP case?

Thanks,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875216#3875216

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875216


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JTA and JTS on JBoss] - Re: Where should UserTransaction live?

2005-04-22 Thread reverbel
You're right, I've made a confusion between jar files and Java packages. Since 
the move won't break anything, I can move to the transaction module the 
remaining usertx classes as well.

Thanks,

Francisco


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875135#3875135

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875135


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JTA and JTS on JBoss] - Where should UserTransaction live?

2005-04-22 Thread reverbel
A modularization issue... I have some (still uncommitted) code that uses the 
DTM to implement UserTransaction over JBoss remoting. The code is very simple 
and consists on just two classes: 

  org.jboss.tm.remoting.client.ClientUserTransaction
  org.jboss.tm.remoting.client.ClientUserTransactionObjectFactory

Those classes are similar to the corresponding ones in package 
org.jboss.tm.usertx.client (in the server module) an in package 
org.jboss.tm.iiop.client (in the iiop module). The object factory class checks 
if it is running in the server VM or not. If it is not running in the server 
VM, it creates a ClientUserTransaction. Otherwise it creates a 
ServerVMClientUserTransaction.

I placed the new classes in the server module, as the object factory depends on 
ServerVMClientUserTransaction, which is also in the server module. They would 
be better placed in the transaction module, but then the transaction module 
would be dependent upon the server module. 

I don't know why ServerVMClientUserTransaction and the other usertx classes 
live in the server module. It looks like the transaction module would be the 
right place for them. At this point, however, we cannot move those classes, as 
this would break the compatibility with older clients. 

So my options are:

(1) put the new classes in the transaction module and create a new dependency 
from the transaction module on the server module, or 

(2) leave the new classes in the server module, together with 
ServerVMClientUserTransaction, or 

(3) put the new classes in the transaction module and create a copy of 
ServerVMClientUserTransaction in the transaction module.

Option (1) sounds like a bad idea to me, so it's going to be either (2) or (3). 
 Does anybody care?

Francisco


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875121#3875121

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875121


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JMX on JBoss (JBoss/JMX)] - Re: Separated XMBean implementation

2005-04-19 Thread reverbel
Thank you Adrian.

Regards,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874564#3874564

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874564


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JMX on JBoss (JBoss/JMX)] - Re: Separated XMBean implementation

2005-04-18 Thread reverbel
Done:

  http://jira.jboss.com/jira/browse/JBJMX-92

Before trying to reproduce the problem, please do a CVS update in the 
transaction and iiop subdirs. I have just committed some changes in those 
subdirs.

The NPE does not happen if I copy jboss-transaction.jar and jboss-iiop.jar (the 
modules on which I have been working) from an up-to-date jboss-head tree (which 
gives me the NPE) to the generated server/all/lib subdir of an outdated 
jboss-head tree, which I checked out from CVS on Mar 26. The older 
jboss-5.0.0alpha does not throw the NPE.

Thanks,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874393#3874393

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874393


---
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JMX on JBoss (JBoss/JMX)] - Re: Separated XMBean implementation

2005-04-17 Thread reverbel
It may have nothing to do with the XMBean change, but after updating my CVS 
tree I started getting this JMX-related NPE:

  | [org.jboss.system.ServiceController] Problem starting service 
jboss:service=DistributedTransactionManager
  | java.lang.NullPointerException: Failed to find method for operation: 
addInvocationHandler invoke on resource: [EMAIL PROTECTED]
  | at 
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:136)
  | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
  | at 
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
  | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
  | at 
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
  | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
  | at 
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:246)
  | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:653)
  | at 
org.jboss.tm.remoting.server.DistributedTransactionManager.startService(DistributedTransactionManager.java:65)
  | at 
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
  | at 
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
  | ...
  | 


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874249#3874249

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874249


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1646) Define OTS-like interfaces for the DTM

2005-04-13 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1646?page=history ]
 
Francisco Reverbel closed JBAS-1646:



 Define OTS-like interfaces for the DTM
 --

  Key: JBAS-1646
  URL: http://jira.jboss.com/jira/browse/JBAS-1646
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Define OTS-like interfaces for the following DTM objects associated with a 
 given transaction: Terminator, Coordinator, Resource, Synchronization, and 
 RecoveryCoordinator. These interfaces allow those objects to be manipulated 
 in a unified way, regardless of whether they are accessible via JBoss 
 remoting or via CORBA/IIOP.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1655) Add to TransactionImpl a method that enlists a DTM Resource...

2005-04-13 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1655?page=history ]
 
Francisco Reverbel closed JBAS-1655:


Resolution: Done

 Add to TransactionImpl a method that enlists a DTM Resource...
 --

  Key: JBAS-1655
  URL: http://jira.jboss.com/jira/browse/JBAS-1655
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Ensure that TransactionImpl has methods that do the actual work for all 
 OTS/DTM objects and for XATerminator. Most of the needed methods already are 
 in place, but some need to be added (e.g., a method to enlist a DTM Resource).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1654) Extend TransactionImpl

2005-04-13 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1654?page=history ]
 
Francisco Reverbel closed JBAS-1654:


Resolution: Done

 Extend TransactionImpl
 --

  Key: JBAS-1654
  URL: http://jira.jboss.com/jira/browse/JBAS-1654
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Extend TransactionImpl so that it knows about the following DTM objects: 
 Coordinator, Resource, and RecoveryCoordinator. Besides having a list of XA 
 resources, a TransactionImpl instance will have a list of DTM Resources, each 
 of which represents either a JBoss remoting-based resource or a (properly 
 wrapped) OTS resource. It may also have a parent coordinator, which will be a 
 DTM Coordinator (either a remoting-based coordinator or an OTS coordinator). 
 If if has a parent coordinator, it must register itself as a Resource with 
 that coordinator. 
 The TransactionImpl must drive the 2PC across all XA resources and DTM 
 resources.
 Logging and recovery are not included in this step.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1653) Review TransactionImpl

2005-04-12 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1653?page=history ]
 
Francisco Reverbel closed JBAS-1653:


Resolution: Done

 Review TransactionImpl
 --

  Key: JBAS-1653
  URL: http://jira.jboss.com/jira/browse/JBAS-1653
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Review TransactionImpl with respect to LocalId/GlobalId association and 
 transaction importing. An imported transaction should have a LocalId just 
 like a non-imported one. (The local id
 is embedded into the CORBA references or into the JBoss remoting-based 
 proxies for the transaction Coordinator, Terminator, etc.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1649) Write OTS wrappers

2005-04-12 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1649?page=history ]
 
Francisco Reverbel closed JBAS-1649:



 Write OTS wrappers
 --

  Key: JBAS-1649
  URL: http://jira.jboss.com/jira/browse/JBAS-1649
  Project: JBoss Application Server
 Type: Sub-task
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Write some trivial OTS wrappers that implement the DTM interfaces by   
 delegating the work to OTS objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1648) Complete the existing implementation of the OTS interfaces

2005-04-12 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1648?page=history ]
 
Francisco Reverbel closed JBAS-1648:



 Complete the existing implementation of the OTS interfaces
 --

  Key: JBAS-1648
  URL: http://jira.jboss.com/jira/browse/JBAS-1648
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 The existing OTS servant does not yet implements register_resource, recreate, 
 and replay_completion. The implementation of those methods will delegate the 
 actual work to the TransactionImpl instance the represents the transaction.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces

2005-04-12 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1647?page=history ]
 
Francisco Reverbel closed JBAS-1647:



 Provide JBoss remoting-based implementations of the DTM interfaces
 --

  Key: JBAS-1647
  URL: http://jira.jboss.com/jira/browse/JBAS-1647
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 The implementations will delegate the actual work to TransactionImpl 
 instances. Besides the similarity in their interfaces, remoting-based DTM 
 objects (Resource, Coordinator, etc.) must be similar to OTS objects also in 
 that their references (proxies) are convertible to strings and vice-versa. 
 This will be needed for logging.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1646) Define OTS-like interfaces for the DTM

2005-04-05 Thread Francisco Reverbel (JIRA)
Define OTS-like interfaces for the DTM
--

 Key: JBAS-1646
 URL: http://jira.jboss.com/jira/browse/JBAS-1646
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Define OTS-like interfaces for the following DTM objects associated with a 
given transaction: Terminator, Coordinator, Resource, Synchronization, and 
RecoveryCoordinator. These interfaces allow those objects to be manipulated in 
a unified way, regardless of whether they are accessible via JBoss remoting or 
via CORBA/IIOP.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces

2005-04-05 Thread Francisco Reverbel (JIRA)
Provide JBoss remoting-based implementations of the DTM interfaces
--

 Key: JBAS-1647
 URL: http://jira.jboss.com/jira/browse/JBAS-1647
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel


The implementations will delegate the actual work to TransactionImpl instances. 
Besides the similarity in their interfaces, remoting-based DTM objects 
(Resource, Coordinator, etc.) must be similar to OTS objects also in that their 
references (proxies) are convertible to strings and vice-versa. This will be 
needed for logging.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1647?page=history ]

Francisco Reverbel updated JBAS-1647:
-

 Assign To: Francisco Reverbel
Security Level: (was: Public)

 Provide JBoss remoting-based implementations of the DTM interfaces
 --

  Key: JBAS-1647
  URL: http://jira.jboss.com/jira/browse/JBAS-1647
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 The implementations will delegate the actual work to TransactionImpl 
 instances. Besides the similarity in their interfaces, remoting-based DTM 
 objects (Resource, Coordinator, etc.) must be similar to OTS objects also in 
 that their references (proxies) are convertible to strings and vice-versa. 
 This will be needed for logging.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1649) Write OTS wrappers

2005-04-05 Thread Francisco Reverbel (JIRA)
Write OTS wrappers
--

 Key: JBAS-1649
 URL: http://jira.jboss.com/jira/browse/JBAS-1649
 Project: JBoss Application Server
Type: Sub-task
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1649) Write OTS wrappers

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1649?page=history ]

Francisco Reverbel updated JBAS-1649:
-

   Description: Write some trivial OTS wrappers that implement the DTM 
interfaces by   delegating the work to OTS objects.
   Environment: 
Security Level: (was: Public)

 Write OTS wrappers
 --

  Key: JBAS-1649
  URL: http://jira.jboss.com/jira/browse/JBAS-1649
  Project: JBoss Application Server
 Type: Sub-task
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Write some trivial OTS wrappers that implement the DTM interfaces by   
 delegating the work to OTS objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1650) Propagate full tx context along with JBoss remoting invocations

2005-04-05 Thread Francisco Reverbel (JIRA)
Propagate full tx context along with JBoss remoting invocations
---

 Key: JBAS-1650
 URL: http://jira.jboss.com/jira/browse/JBAS-1650
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Enlarge the transaction context propagated along with JBoss remoting 
invocations. The current context has only a GlobalId/Xid, it must include also 
a Coordinator reference.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1651) Make the TPC factory/importer/exporter configurable

2005-04-05 Thread Francisco Reverbel (JIRA)
Make the TPC factory/importer/exporter configurable
---

 Key: JBAS-1651
 URL: http://jira.jboss.com/jira/browse/JBAS-1651
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel


Make the TPC factory/importer/exporter configurable so that the full context 
(GlobalId + Coordinator reference) is propagated only if the DTM is actually 
used (no additional overhead for DTMless server configs).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1652) Propagate OTS context in IIOP invocations from the JBoss server

2005-04-05 Thread Francisco Reverbel (JIRA)
Propagate OTS context in IIOP invocations from the JBoss server
---

 Key: JBAS-1652
 URL: http://jira.jboss.com/jira/browse/JBAS-1652
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Propagate the OTS context along with invocations issued by the JBoss server.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1651) Make the TPC factory/importer/exporter configurable

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1651?page=history ]

Francisco Reverbel updated JBAS-1651:
-

 Assign To: Francisco Reverbel
Security Level: (was: Public)

 Make the TPC factory/importer/exporter configurable
 ---

  Key: JBAS-1651
  URL: http://jira.jboss.com/jira/browse/JBAS-1651
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Make the TPC factory/importer/exporter configurable so that the full context 
 (GlobalId + Coordinator reference) is propagated only if the DTM is actually 
 used (no additional overhead for DTMless server configs).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1653) Review TransactionImpl

2005-04-05 Thread Francisco Reverbel (JIRA)
Review TransactionImpl
--

 Key: JBAS-1653
 URL: http://jira.jboss.com/jira/browse/JBAS-1653
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Review TransactionImpl with respect to LocalId/GlobalId association and 
transaction importing. An imported transaction should have a LocalId just like 
a non-imported one. (The local id
is embedded into the CORBA references or into the JBoss remoting-based proxies 
for the transaction Coordinator, Terminator, etc.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1654) Extend TransactionImpl

2005-04-05 Thread Francisco Reverbel (JIRA)
Extend TransactionImpl
--

 Key: JBAS-1654
 URL: http://jira.jboss.com/jira/browse/JBAS-1654
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Extend TransactionImpl so that it knows about the following DTM objects: 
Coordinator, Resource, and RecoveryCoordinator. Besides having a list of XA 
resources, a TransactionImpl instance will have a list of DTM Resources, each 
of which represents either a JBoss remoting-based resource or a (properly 
wrapped) OTS resource. It may also have a parent coordinator, which will be a 
DTM Coordinator (either a remoting-based coordinator or an OTS coordinator). If 
if has a parent coordinator, it must register itself as a Resource with that 
coordinator. 

The TransactionImpl must drive the 2PC across all XA resources and DTM 
resources.

Logging and recovery are not included in this step.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1655) Add to TransactionImpl a method that enlists a DTM Resource...

2005-04-05 Thread Francisco Reverbel (JIRA)
Add to TransactionImpl a method that enlists a DTM Resource...
--

 Key: JBAS-1655
 URL: http://jira.jboss.com/jira/browse/JBAS-1655
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Ensure that TransactionImpl has methods that do the actual work for all OTS/DTM 
objects and for XATerminator. Most of the needed methods already are in place, 
but some need to be added (e.g., a method to enlist a DTM Resource).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1656) Implement UserTransaction over JBoss remoting

2005-04-05 Thread Francisco Reverbel (JIRA)
Implement UserTransaction over JBoss remoting
-

 Key: JBAS-1656
 URL: http://jira.jboss.com/jira/browse/JBAS-1656
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1657) Preliminary UserTransaction and 2PC tests

2005-04-05 Thread Francisco Reverbel (JIRA)
Preliminary UserTransaction and 2PC tests
-

 Key: JBAS-1657
 URL: http://jira.jboss.com/jira/browse/JBAS-1657
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Preliminary tests, still with no logging/recovery.

Test UserTransaction over JBoss remoting. (UserTransaction over IIOP is already 
in place and has its own testcase.)

Test 2PC across DTM Resources (either remoting-based and OTS-based) and XA 
resources.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1658) Change LocalId/GlobalId/Xid generation

2005-04-05 Thread Francisco Reverbel (JIRA)
Change LocalId/GlobalId/Xid generation
--

 Key: JBAS-1658
 URL: http://jira.jboss.com/jira/browse/JBAS-1658
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Change the LocalId/GlobalId/Xid generation strategy so that the nextLocalId is 
not reset to 0 at server startup.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1659) Implement write-ahead logging for the distributed case

2005-04-05 Thread Francisco Reverbel (JIRA)
Implement write-ahead logging for the distributed case
--

 Key: JBAS-1659
 URL: http://jira.jboss.com/jira/browse/JBAS-1659
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


Resource and RecoveryCoordinator references must be logged.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1660) Implement recovery for the distributed case

2005-04-05 Thread Francisco Reverbel (JIRA)
Implement recovery for the distributed case
---

 Key: JBAS-1660
 URL: http://jira.jboss.com/jira/browse/JBAS-1660
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1661) Test recovery

2005-04-05 Thread Francisco Reverbel (JIRA)
Test recovery
-

 Key: JBAS-1661
 URL: http://jira.jboss.com/jira/browse/JBAS-1661
 Project: JBoss Application Server
Type: Sub-task
  Components: Transaction Manager service  
Versions: JBossAS-5.0 Alpha
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 


This task will be split in several sub-tasks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1647) Provide JBoss remoting-based implementations of the DTM interfaces

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1647?page=history ]
 
Francisco Reverbel resolved JBAS-1647:
--

Resolution: Done

 Provide JBoss remoting-based implementations of the DTM interfaces
 --

  Key: JBAS-1647
  URL: http://jira.jboss.com/jira/browse/JBAS-1647
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 The implementations will delegate the actual work to TransactionImpl 
 instances. Besides the similarity in their interfaces, remoting-based DTM 
 objects (Resource, Coordinator, etc.) must be similar to OTS objects also in 
 that their references (proxies) are convertible to strings and vice-versa. 
 This will be needed for logging.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1646) Define OTS-like interfaces for the DTM

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1646?page=history ]
 
Francisco Reverbel resolved JBAS-1646:
--

Resolution: Done

 Define OTS-like interfaces for the DTM
 --

  Key: JBAS-1646
  URL: http://jira.jboss.com/jira/browse/JBAS-1646
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Define OTS-like interfaces for the following DTM objects associated with a 
 given transaction: Terminator, Coordinator, Resource, Synchronization, and 
 RecoveryCoordinator. These interfaces allow those objects to be manipulated 
 in a unified way, regardless of whether they are accessible via JBoss 
 remoting or via CORBA/IIOP.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1648) Complete the existing implementation of the OTS interfaces

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1648?page=history ]
 
Francisco Reverbel resolved JBAS-1648:
--

Resolution: Done

 Complete the existing implementation of the OTS interfaces
 --

  Key: JBAS-1648
  URL: http://jira.jboss.com/jira/browse/JBAS-1648
  Project: JBoss Application Server
 Type: Sub-task
   Components: Transaction Manager service
 Versions: JBossAS-5.0 Alpha
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 The existing OTS servant does not yet implements register_resource, recreate, 
 and replay_completion. The implementation of those methods will delegate the 
 actual work to the TransactionImpl instance the represents the transaction.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1649) Write OTS wrappers

2005-04-05 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1649?page=history ]
 
Francisco Reverbel resolved JBAS-1649:
--

Resolution: Done

 Write OTS wrappers
 --

  Key: JBAS-1649
  URL: http://jira.jboss.com/jira/browse/JBAS-1649
  Project: JBoss Application Server
 Type: Sub-task
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel



 Write some trivial OTS wrappers that implement the DTM interfaces by   
 delegating the work to OTS objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1617) Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss

2005-04-01 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1617?page=history ]
 
Francisco Reverbel resolved JBAS-1617:
--

Resolution: Done

The JacORB libraries have been updated to a patched version of JacORB 2.2.1, 
which identifies itself as JacORB V 2.2.1 (JBoss patch 2). This version fixes 
the following JacORB bugs: #445, #532, #550, #558, #562, #566, #568, #574, 
#584, #585, and #586. It also includes the exception reporting improvements 
committed to JacORB's CVS repository in 2004/11/18 and 2004/12/11.

The updated libraries have been committed to CVS HEAD, Branch_4_0, and 
Branch_3_2.


 Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss
 --

  Key: JBAS-1617
  URL: http://jira.jboss.com/jira/browse/JBAS-1617
  Project: JBoss Application Server
 Type: Task
   Components: IIOP service
 Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, 
 JBossAS-3.2.6 Final,  JBossAS-3.2.5 Final,  JBossAS-4.0.2RC1, 
 JBossAS-4.0.1RC1,  JBossAS-4.0.1 SP1
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel
  Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-5.0 Beta, 
 JBossAS-5.0 Final, JBossPOJOServer-1.0 Alpha, JBossPOJOServer-1.0 Final,  
 JBossAS-3.2.8 Final


 Original Estimate: 2 hours
 Remaining: 2 hours

 Merge fixes for bugs numberered 562 and 568 in JacORB's bugzilla. The fixes 
 were submitted by Jimmy Wilson and are already in JacORB's CVS repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1617) Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss

2005-04-01 Thread Francisco Reverbel (JIRA)
 [ http://jira.jboss.com/jira/browse/JBAS-1617?page=history ]
 
Francisco Reverbel closed JBAS-1617:



 Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss
 --

  Key: JBAS-1617
  URL: http://jira.jboss.com/jira/browse/JBAS-1617
  Project: JBoss Application Server
 Type: Task
   Components: IIOP service
 Versions: JBossAS-4.0.1 Final,  JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, 
 JBossAS-3.2.6 Final,  JBossAS-3.2.5 Final,  JBossAS-4.0.2RC1, 
 JBossAS-4.0.1RC1,  JBossAS-4.0.1 SP1
 Reporter: Francisco Reverbel
 Assignee: Francisco Reverbel
  Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-5.0 Beta, 
 JBossAS-5.0 Final, JBossPOJOServer-1.0 Alpha, JBossPOJOServer-1.0 Final,  
 JBossAS-3.2.8 Final


 Original Estimate: 2 hours
Time Spent: 3 hours
 Remaining: 0 minutes

 Merge fixes for bugs numberered 562 and 568 in JacORB's bugzilla. The fixes 
 were submitted by Jimmy Wilson and are already in JacORB's CVS repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBAS-1617) Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss

2005-03-24 Thread Francisco Reverbel (JIRA)
Merge fixes for JacORB bugs #562 and #568 into the JacORB lib shipped w/ JBoss
--

 Key: JBAS-1617
 URL: http://jira.jboss.com/jira/browse/JBAS-1617
 Project: JBoss Application Server
Type: Task
  Components: IIOP service  
Versions:  JBossAS-4.0.2RC1,  JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final,  
JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.1RC1, JBossAS-4.0.0 
Final,  JBossAS-3.2.5 Final
Reporter: Francisco Reverbel
 Assigned to: Francisco Reverbel 
 Fix For: JBossAS-4.0.2 Final, JBossPOJOServer-1.0 Alpha, JBossAS-5.0 
Alpha, JBossPOJOServer-1.0 Final, JBossAS-5.0 Beta, JBossAS-5.0 Final,  
JBossAS-3.2.8 Final


Merge fixes for bugs numberered 562 and 568 in JacORB's bugzilla. The fixes 
were submitted by Jimmy Wilson and are already in JacORB's CVS repository.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Problem with datatype=invocation in the socket connector MBe

2005-03-16 Thread reverbel
I have an MBean that depends on one or more connectors:

  | mbean code=org.jboss.tm.remoting.server.DistributedTransactionManager
  |name=jboss:service=DistributedTransactionManager
  |depends-list optional-attribute-name=Connectors
  |   
depends-list-elementjboss.remoting:service=Connector,transport=socket/depends-list-element
  |/depends-list
  | /mbean
  | 
In its startService method, the MBean issues addInvocationHandler calls to add 
a new invocation handler (for the DTM subsystem) to each of those connectors. 
However, the DTM subsystem does not use the unified invoker marshaller, which 
is specified by the datatype=invocation parameter appended to the invoker 
locator URI of the connector MBean for the socket transport:

  | !-- excerpt from jboss-service.xml --
  | mbean code=org.jboss.remoting.transport.Connector
  |xmbean-dd=org/jboss/remoting/transport/Connector.xml
  |name=jboss.remoting:service=Connector,transport=socket
  |display-name=Socket transport Connector
  | 
  |attribute 
name=InvokerLocator[CDATA[socket://localhost:4446/?datatype=invocation]]/attribute
  | 
  |attribute name=Configuration
  |   handlers
  |  handler 
subsystem=invokerjboss:service=invoker,type=unified/handler
  |   /handlers
  |/attribute
  |dependsjboss.remoting:service=NetworkRegistry/depends
  | /mbean
  | 
The problem is that the return value of connector.getLocator() does not make 
sense for the DTM subsystem, as it includes the datatype=invocation 
parameter. Everything works fine if I remove the datatype=invocation part of 
the locator.

Should it be possible to use a single connector for multiple subsystems, each 
with its own marshaller? In that case, perhaps the datatype=xxx parameter 
could be added by the client side (which must specify the subsystem it wants to 
interact with anyway), rather than being kept in a global attribute of the 
connector MBean. In the case of the unified invoker, the client-side proxy 
could specify datatype=invocation.

Or perhaps I should simply add another socket connector MBean (without the 
datatype=xxx) just for myself? I noticed that Bill did that for AOP remoting. 
Adding another connector defeats the idea of having one connector per 
transport, though. One connector per transport (and multiple subsystems per 
connector) sounds like a good thing to me.


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870382#3870382

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870382


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Problem with datatype=invocation in the socket connector

2005-03-16 Thread reverbel
Noticed that not only my own code works fine with no datatype=invocation 
parameter in the socket connector MBean, but EJB testcases work too.  To me 
this was surprising, as those testcases perform EJB calls through the unified 
invoker. (Maybe EJB calls work with no datatype=invocation because 
UnifiedInvokerProxy.init explicitly sets the invocation marshaller?) Anyway, by 
now I have just removed the datatype=invocation parameter from the locator 
URI in the socket connector MBean.

Francisco


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870414#3870414

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870414


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Problem with datatype=invocation in the socket connector

2005-03-16 Thread reverbel
Hey Tom, that was pretty quick. Thanks a lot. 

Regards,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870489#3870489

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870489


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of JBoss IIOP on JBoss] - Re: Bad performance when deploying EJBs on JBoss 4.0

2005-01-15 Thread reverbel
The PolicyError exception will go away if you comment out just the 
SASInitializer, which is the one that installs a request interceptor and thus 
affects performance. The CSIv2Initializer must remain enabled, as it defines a 
POA policy that is used at EJB deployment time. This initializer does not 
install a request interceptor, so it should not cause a decrease on performance.

There is another problem, though. Due to a coding oversight in releases 4.0.0 
and 4.0.1 of JBoss, commenting out the just the SASInitializer will result in 
another exception. No exception will be thrown at EJB deployment time, but you 
will get an exception whenever the EJB receives a remote call. This problem has 
been fixed in CVS and won't be present in JBoss 4.0.2.

Right now what you can do is get Branch_4_0 from CVS and build JBoss 4.0.2beta, 
which works properly with no request interceptors at all (with SASInitializer 
and Tx interceptor initializers commented out).

Regards,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3862250#3862250

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3862250


---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [IIOP on JBoss] - Re: Bad performance when deploying EJBs on JBoss 4.0

2004-12-16 Thread reverbel
You probably mean JBoss 3.2.5 rather than JBoss 2.3.5, right? (IIOP support 
appeared for the first time in 3.0.0.)

Anyway, two IIOP-related changes may cause a performance decrease in 4.0:

1) jacorb.jar was updated to (a patched version of) JacORB 2.2.  A performance 
decrease has been reported for JacORB 2.2. The degradation shows up when JacORB 
tries to access unset configuration properties:

http://lists.spline.inf.fu-berlin.de/pipermail/jacorb-developer/2004-September/006777.html

2) Portable interceptors were added to deal with transaction context 
propagation and with security over IIOP (CSIv2). Usage of request interceptors 
in JacORB effectively disables the local call optimization that would otherwise 
happen on in-VM calls. This has a negative effect on the performance of 
applications that do in-VM calls to (remote interfaces of) IIOP-enabled EJBs. 
If you don't need transaction demarcation/propagation and security over IIOP, 
then you get rid of the negative effect by commenting out the tx and csiv2 
interceptors in iiop-service.xml. 

Regards,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858772#3858772

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858772


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [IIOP on JBoss] - Re: IIOP.NET over SSL on JBoss

2004-12-15 Thread reverbel
JBoss supports IIOP over SSL. RMI (or CORBA)  clients can use IIOP over SSL to 
communicate with EJBs deployed in JBoss. 

So far I didn't have a chance to look at IIOP.NET, so I cannot tell whether it 
supports IIOP over SSL or not. Anyway, I am pleased to know that it is being 
used to call EJBs from .NET clients. (Yours is the second posting on the usage 
of IIOP.NET  with JBoss.)

Regards,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858773#3858773

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3858773


---
SF email is sponsored by - The IT Product Guide
Read honest  candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: how to change the arguments of a method by AOP?

2004-11-12 Thread reverbel
It should be possible to change method arguments at call joinpoints. 

Your example works with the call joinpoint if you turn optimization off 
(-Djboss.aop.optimized=false). 

Cheers,

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854990#3854990

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854990


---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [AOP on JBoss (Aspects/JBoss)] - Re: how to change the arguments of a method by AOP?

2004-11-12 Thread reverbel
Yes.

Francisco

View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854994#3854994

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854994


---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [IIOP on JBoss] - Re: JacORB version in JBoss-3.2.4

2004-02-19 Thread reverbel
Hi Rich,

 I noticed JacORB 2.1 is in the head but 2.0 is still in the branch, is it going to 
 stay that way? 

No, it will not. I didn't have a chance to update JacORB in Branch_3_2 yet, but will 
do it ASAP.

Regards,

Francisco


View the original post : 
http://www.jboss.org/index.html?module=bbop=viewtopicp=3822239#3822239

Reply to the post : 
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3822239


---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps  Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] jts removal and tyrex plugin status

2004-02-14 Thread Francisco Reverbel
I have removed from CVS HEAD all the stuff under thirdparty/sun-jts.

File thirdparty/sun-jts/lib/jts.jar contained a bogus implementation
of the standard class org.omg.CosTransactions.PropagationContextHelper.
It had hardwired references to the Exolab class org.openorb.CORBA.Any.
This is nonsense. An org.omg class should never have a dependency on a
proprietary class. Even though jts.jar was under sun-jts, it looks like
Exolab (Tyrex) stuff.

I noticed that there was something weird about jts.jar because the new
IIOP transaction code in HEAD didn't work with it.

The tyrex plugin is the only module using the deleted jar. I have
disabled the compilation of this plugin. Unless somebody steps up to
fix and maintain the tyrex plugin, this module will be removed from
CVS HEAD in a couple of weeks.

Regards,

Francisco



---
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps  Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] Changes for IIOP over SSL

2004-01-03 Thread Francisco Reverbel
In order to support IIOP over SSL I have made (still uncommitted)
changes to a couple of classes in the security module:

- org.jboss.security.ssl.DomainServerSocketFactory

  Work currently performed within private method initSSLContext() factored 
  out to an utility class, in order to be available to the IIOP/SSL code.


- org.jboss.security.plugins.JaasSecurityDomain

  Work currently performed within start() method moved to create(). 
  Reason: the JaasSecurityDomain must be ready when ORB.init() is 
  called. CorbaOrbService calls ORB.init() within createService(),
  and this call cannot be moved to startService(), as the IIOP proxy 
  factory (IORFactory) needs the IIOP invoker ready before that.

Does anybody see some problem with these changes? If nobody speaks up, 
I'll commit them to CVS, along with IIOP over SSL support.

Cheers,

Francisco



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] CVS problem

2003-12-28 Thread Francisco Reverbel
Thanks!

Francisco

On Sat, 27 Dec 2003, Scott M Stark wrote:

 The thirdparty directory is just a collection of other alias checkouts.
 You already had avalon checked into the thirdparty/apache/avalon dir
 in 3.2, so checkout thirdparty/apache/avalon on head and add the
 libs. I have done this and added a new alias to the _jboss_thirdparty
 so add the apache-avalon to  your thirdparty tree using:
 
 [EMAIL PROTECTED] thirdparty]$ cvs co _thirdparty_apache_avalon
 cvs server: Updating apache-avalon
 cvs server: Updating apache-avalon/lib
 U apache-avalon/lib/README
 U apache-avalon/lib/avalon-framework.jar 
 [EMAIL PROTECTED] thirdparty]$ ls apache-avalon/lib/
 CVS/  README  avalon-framework.jar
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
  
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Francisco Reverbel
 Sent: Saturday, December 27, 2003 9:34 AM
 To: [EMAIL PROTECTED]
 Subject: [JBoss-dev] CVS problem
 
 jboss-head, fresh checkout:
 
 $ cd jboss-head/thirdparty
 $ mkdir apache-avalon
 $ cvs -z3 add apache-avalon
 cvs [add aborted]: cannot add to /cvsroot/jboss/CVSROOT/Emptydir $ cat
 CVS/Reposit



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] CVS problem

2003-12-27 Thread Francisco Reverbel
jboss-head, fresh checkout:

$ cd jboss-head/thirdparty
$ mkdir apache-avalon
$ cvs -z3 add apache-avalon 
cvs [add aborted]: cannot add to /cvsroot/jboss/CVSROOT/Emptydir
$ cat CVS/Repository 
CVSROOT/Emptydir
$ echo $CVSROOT 
:ext:[EMAIL PROTECTED]:/cvsroot/jboss

What is this? 

Cheers,

Francisco



---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] 3.2.3RC1

2003-11-08 Thread Francisco Reverbel
Me too, just updated jacorb.jar in thirdparty.

Francisco

On Sat, 8 Nov 2003, Alexey Loubyansky wrote:

 I am done for this RC.
 
 Scott M Stark wrote:
 
  When can these be committed?
  
 
 
 
 
 
 ---
 This SF.Net email sponsored by: ApacheCon 2003,
 16-19 November in Las Vegas. Learn firsthand the latest
 developments in Apache, PHP, Perl, XML, Java, MySQL,
 WebDAV, and more! http://www.apachecon.com/
 ___
 JBoss-Development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] 3.2.3RC1

2003-11-07 Thread Francisco Reverbel
I am not aware of such problem... Cheers,

Francisco

On Fri, 7 Nov 2003, Sacha Labourey wrote:

 Will this contain the fix for the problem that occurs when doing invocation
 from JacORB against Orbix as well? 
 
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On 
  Behalf Of Francisco Reverbel
  Sent: jeudi, 6. novembre 2003 23:25
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] 3.2.3RC1
  
  When will you get 3.2.3.RC1 from CVS?
  
  There has been a JacORB bug fix (for Arjuna) that is not in 
  our CVS yet. I´d generate a patched version of jacorb.jar
  with the fix.
  
  Cheers,
  
  Francisco
  
  On Wed, 5 Nov 2003, Scott M Stark wrote:
  
   I'm putting together a 3.2.3RC1 release to pickup some 
  recent bug fixes. I'm
   working on a fix for [ 832561 ] NoSuchMethodException when 
  HAJNDI joins cluster
   that I want to include. If there are any other must have 
  fixes let me know.
   
   -- 
   
   Scott Stark
   Chief Technology Officer
   JBoss Group, LLC
   
   
   
   
   
   ---
   This SF.net email is sponsored by: SF.net Giveback Program.
   Does SourceForge.net help you be more productive?  Does it
   help you create better code?   SHARE THE LOVE, and help us help
   YOU!  Click Here: http://sourceforge.net/donate/
   ___
   JBoss-Development mailing list
   [EMAIL PROTECTED]
   https://lists.sourceforge.net/lists/listinfo/jboss-development
   
  
  
  
  ---
  This SF.net email is sponsored by: SF.net Giveback Program.
  Does SourceForge.net help you be more productive?  Does it
  help you create better code?   SHARE THE LOVE, and help us help
  YOU!  Click Here: http://sourceforge.net/donate/
  ___
  JBoss-Development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
  
 
 
 
 ---
 This SF.net email is sponsored by: SF.net Giveback Program.
 Does SourceForge.net help you be more productive?  Does it
 help you create better code?   SHARE THE LOVE, and help us help
 YOU!  Click Here: http://sourceforge.net/donate/
 ___
 JBoss-Development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] 3.2.3RC1

2003-11-07 Thread Francisco Reverbel
Bug #398 is the same as bug #365, which has been fixed before beta 2:

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=365

The fix is already included in the jacorb.jar library distributed
with JBoss 3.2.2.

CSIv2 is also there, but I didn't test it yet. We should try it
as the basis for interoperable EJB security.

Cheers,

Francisco


On Fri, 7 Nov 2003, Sacha Labourey wrote:

 I think it is this one:
 
 http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=398 
 
 Do you know if your release will include it? It seems to be part of beta 3.
 Do you know what is the status of Jacorb WRT csiv2?
 
 Cheers,
 
 
 sacha
 
  -Original Message-
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On 
  Behalf Of Francisco Reverbel
  Sent: vendredi, 7. novembre 2003 12:34
  To: [EMAIL PROTECTED]
  Subject: RE: [JBoss-dev] 3.2.3RC1
  
  I am not aware of such problem... Cheers,
  
 
 
 
 ---
 This SF.net email is sponsored by: SF.net Giveback Program.
 Does SourceForge.net help you be more productive?  Does it
 help you create better code?   SHARE THE LOVE, and help us help
 YOU!  Click Here: http://sourceforge.net/donate/
 ___
 JBoss-Development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] 3.2.3RC1

2003-11-06 Thread Francisco Reverbel
When will you get 3.2.3.RC1 from CVS?

There has been a JacORB bug fix (for Arjuna) that is not in 
our CVS yet. I´d generate a patched version of jacorb.jar
with the fix.

Cheers,

Francisco

On Wed, 5 Nov 2003, Scott M Stark wrote:

 I'm putting together a 3.2.3RC1 release to pickup some recent bug fixes. I'm
 working on a fix for [ 832561 ] NoSuchMethodException when HAJNDI joins cluster
 that I want to include. If there are any other must have fixes let me know.
 
 -- 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 
 
 
 
 ---
 This SF.net email is sponsored by: SF.net Giveback Program.
 Does SourceForge.net help you be more productive?  Does it
 help you create better code?   SHARE THE LOVE, and help us help
 YOU!  Click Here: http://sourceforge.net/donate/
 ___
 JBoss-Development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] JMX DR3 rollback commit

2003-10-21 Thread Francisco Reverbel
Actually my rant was not well founded. Just run all IIOP tests on
on HEAD (fresh checkout), with no errors.

I don't understand why there were IIOP errors in the results Tom 
posted. (Perhaps his server run with the default config, rather 
than with the all config?)

Cheers,

Francisco

On Tue, 21 Oct 2003, Tom Elrod wrote:

 Per request, I am going to wait an extra day before doing commit.  Am also
 assuming that the post below is not an objection to the commit, but a well
 founded rant.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of
  Francisco Reverbel
  Sent: Monday, October 20, 2003 4:21 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] JMX DR3 rollback commit
 
 
  Guys,
 
  The test results Tom posted show IIOP tests failing on HEAD.
  I understand
  this is not his fault, as his changes were not yet merged
  into HEAD when
  the tests were run. Anyway, I've fixed IIOP in HEAD less than
  a month ago.
  All IIOP tests were running with no errors back then.
 
  rant
  I'm tired of chasing errors before doing IIOP work on HEAD.
  /rant
 
  Cheers,
 
  Francisco
 
  On Sun, 19 Oct 2003, Tom Elrod wrote:
 
   Hello all.  I have been working on bringing in the source
  code from the jmx
   project from the Branch_4_0_DR3 into HEAD.  This is needed
  since it is
   compliant with JMX 1.2, which is needed for some of the
  other modules (like
   JMX Remoting).  Everything under the jmx directory will be
  updated, except
   the mx.loading module, which will remain the same as what
  is in HEAD now. In
   the process of migrating this code, many other classes had
  to be changed
   outside the jmx project, so that they would use any new API.
  
   I have run the testsuite (along with many other tests) to
  makes sure I did
   not break anything in the process.  However, there is too
  much to be able to
   go through all the different modules.  In general, the test
  results seem to
   reflect that not much (if anything) has been broken (see
  below) due to the
   change.
  
   I plan on committing all the code tomorrow (Monday) night
  around 11pm EST.
   Please review the following test results and verify I did
  not break anything
   significant in your module.  You can follow the links at
  the bottom to get
   details on the exact tests that failed.  In the following
  results, the repos
   named 'rollback' is the one that I have made the changes to
  and thus the one
   to be most aware of.  Please let me know if there is
  something that needs to
   be corrected before I perform the commit tomorrow.  BTW,
  there are not
   currently test results for 'rollback' on Linux, so that is
  why it is not
   filled in yet.
  
   Thanks.
  
   -Tom
  
  
  
   Windows 2000
  
   \build\build.bat clean most
  
   Source Repos  Test Results
   Branch_4_0_DR3success
   HEAD  success
   rollback  success
  
   \jmx\build.bat test-compliance-full-JBossMX  test-implementation
   test-performance-JBossMX  test-serialization test-stress-JBossMX
  
   Source Repos  Test Target Test Results
   Branch_4_0_DR3test-compliance-full-JBossMXTests
  run: 926,  Failures: 4,
   Errors: 2
   HEAD  test-compliance-full-JBossMXTests run: 706,
   Failures: 3,  Errors: 0
   rollback  test-compliance-full-JBossMXTests run: 926,
   Failures: 4,  Errors:
   2
   Branch_4_0_DR3test-implementation Tests run: 67,
  Failures: 1,  Errors: 1
   HEAD  test-implementation OK (37 tests)
   rollback  test-implementation Tests run: 67,
  Failures: 1,  Errors: 1
   Branch_4_0_DR3test-performance-JBossMXOK (14 tests)
   HEAD  test-performance-JBossMXOK (11 tests)
   rollback  test-performance-JBossMXOK (14 tests)
   Branch_4_0_DR3test-serialization  Tests run: 93,
  Failures: 1,  Errors: 0
   HEAD  test-serialization  Tests run: 93,
  Failures: 0,  Errors: 90
   rollback  test-serialization  Tests run: 93,
  Failures: 1,  Errors: 1
   Branch_4_0_DR3test-stress-JBossMX OK (1 tests)
   HEAD  test-stress-JBossMX OK (1 test)
   rollback  test-stress-JBossMX OK (1 test)
  
   \testsuite\build.bat tests
  
   Source Repos  TestFailuresErrors  Success
  rateTime
   Branch_4_0_DR3847 13  480 41.79%  5817.237
   HEAD  733 54  304 51.16%  1687.185
   rollback  718 62  308 48.47   1656.592
  
  
   Linux - Red Hat 7.3
  
   \build\build.sh clean most
  
   Source Repos  Test Results
   Branch_4_0_DR3success
   HEAD  success
   rollback
  
   \jmx\build.sh test-compliance-full-JBossMX  test-implementation
   test-performance-JBossMX  test-serialization test-stress-JBossMX
  
   Source Repos  Test Target Test Results
   Branch_4_0_DR3test-compliance-full-JBossMXTests
  run: 926,  Failures: 4,
   Errors: 2
   HEAD  test-compliance-full-JBossMXTests run: 706,
   Failures: 3

RE: [JBoss-dev] JMX DR3 rollback commit

2003-10-21 Thread Francisco Reverbel
You're right, Tom. My post was not an objection to the commit. 
BTW: Thank you for your great work on the remoting framework!

Cheers,

Francisco

On Tue, 21 Oct 2003, Tom Elrod wrote:

 Per request, I am going to wait an extra day before doing commit.  Am also
 assuming that the post below is not an objection to the commit, but a well
 founded rant.
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of
  Francisco Reverbel
  Sent: Monday, October 20, 2003 4:21 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] JMX DR3 rollback commit
 
 
  Guys,
 
  The test results Tom posted show IIOP tests failing on HEAD.
  I understand
  this is not his fault, as his changes were not yet merged
  into HEAD when
  the tests were run. Anyway, I've fixed IIOP in HEAD less than
  a month ago.
  All IIOP tests were running with no errors back then.
 
  rant
  I'm tired of chasing errors before doing IIOP work on HEAD.
  /rant
 
  Cheers,
 
  Francisco
 
  On Sun, 19 Oct 2003, Tom Elrod wrote:
 
   Hello all.  I have been working on bringing in the source
  code from the jmx
   project from the Branch_4_0_DR3 into HEAD.  This is needed
  since it is
   compliant with JMX 1.2, which is needed for some of the
  other modules (like
   JMX Remoting).  Everything under the jmx directory will be
  updated, except
   the mx.loading module, which will remain the same as what
  is in HEAD now. In
   the process of migrating this code, many other classes had
  to be changed
   outside the jmx project, so that they would use any new API.
  
   I have run the testsuite (along with many other tests) to
  makes sure I did
   not break anything in the process.  However, there is too
  much to be able to
   go through all the different modules.  In general, the test
  results seem to
   reflect that not much (if anything) has been broken (see
  below) due to the
   change.
  
   I plan on committing all the code tomorrow (Monday) night
  around 11pm EST.
   Please review the following test results and verify I did
  not break anything
   significant in your module.  You can follow the links at
  the bottom to get
   details on the exact tests that failed.  In the following
  results, the repos
   named 'rollback' is the one that I have made the changes to
  and thus the one
   to be most aware of.  Please let me know if there is
  something that needs to
   be corrected before I perform the commit tomorrow.  BTW,
  there are not
   currently test results for 'rollback' on Linux, so that is
  why it is not
   filled in yet.
  
   Thanks.
  
   -Tom
  
  
  
   Windows 2000
  
   \build\build.bat clean most
  
   Source Repos  Test Results
   Branch_4_0_DR3success
   HEAD  success
   rollback  success
  
   \jmx\build.bat test-compliance-full-JBossMX  test-implementation
   test-performance-JBossMX  test-serialization test-stress-JBossMX
  
   Source Repos  Test Target Test Results
   Branch_4_0_DR3test-compliance-full-JBossMXTests
  run: 926,  Failures: 4,
   Errors: 2
   HEAD  test-compliance-full-JBossMXTests run: 706,
   Failures: 3,  Errors: 0
   rollback  test-compliance-full-JBossMXTests run: 926,
   Failures: 4,  Errors:
   2
   Branch_4_0_DR3test-implementation Tests run: 67,
  Failures: 1,  Errors: 1
   HEAD  test-implementation OK (37 tests)
   rollback  test-implementation Tests run: 67,
  Failures: 1,  Errors: 1
   Branch_4_0_DR3test-performance-JBossMXOK (14 tests)
   HEAD  test-performance-JBossMXOK (11 tests)
   rollback  test-performance-JBossMXOK (14 tests)
   Branch_4_0_DR3test-serialization  Tests run: 93,
  Failures: 1,  Errors: 0
   HEAD  test-serialization  Tests run: 93,
  Failures: 0,  Errors: 90
   rollback  test-serialization  Tests run: 93,
  Failures: 1,  Errors: 1
   Branch_4_0_DR3test-stress-JBossMX OK (1 tests)
   HEAD  test-stress-JBossMX OK (1 test)
   rollback  test-stress-JBossMX OK (1 test)
  
   \testsuite\build.bat tests
  
   Source Repos  TestFailuresErrors  Success
  rateTime
   Branch_4_0_DR3847 13  480 41.79%  5817.237
   HEAD  733 54  304 51.16%  1687.185
   rollback  718 62  308 48.47   1656.592
  
  
   Linux - Red Hat 7.3
  
   \build\build.sh clean most
  
   Source Repos  Test Results
   Branch_4_0_DR3success
   HEAD  success
   rollback
  
   \jmx\build.sh test-compliance-full-JBossMX  test-implementation
   test-performance-JBossMX  test-serialization test-stress-JBossMX
  
   Source Repos  Test Target Test Results
   Branch_4_0_DR3test-compliance-full-JBossMXTests
  run: 926,  Failures: 4,
   Errors: 2
   HEAD  test-compliance-full-JBossMXTests run: 706,
   Failures: 3,  Errors: 0
   rollback  test-compliance-full-JBossMX
   Branch_4_0_DR3test-implementation Tests run: 67,
  Failures: 1,  Errors: 1

Re: [JBoss-dev] JMX DR3 rollback commit

2003-10-20 Thread Francisco Reverbel
Guys,

The test results Tom posted show IIOP tests failing on HEAD. I understand 
this is not his fault, as his changes were not yet merged into HEAD when
the tests were run. Anyway, I've fixed IIOP in HEAD less than a month ago. 
All IIOP tests were running with no errors back then. 

rant
I'm tired of chasing errors before doing IIOP work on HEAD.
/rant

Cheers,

Francisco 

On Sun, 19 Oct 2003, Tom Elrod wrote:

 Hello all.  I have been working on bringing in the source code from the jmx
 project from the Branch_4_0_DR3 into HEAD.  This is needed since it is
 compliant with JMX 1.2, which is needed for some of the other modules (like
 JMX Remoting).  Everything under the jmx directory will be updated, except
 the mx.loading module, which will remain the same as what is in HEAD now. In
 the process of migrating this code, many other classes had to be changed
 outside the jmx project, so that they would use any new API.
 
 I have run the testsuite (along with many other tests) to makes sure I did
 not break anything in the process.  However, there is too much to be able to
 go through all the different modules.  In general, the test results seem to
 reflect that not much (if anything) has been broken (see below) due to the
 change.
 
 I plan on committing all the code tomorrow (Monday) night around 11pm EST.
 Please review the following test results and verify I did not break anything
 significant in your module.  You can follow the links at the bottom to get
 details on the exact tests that failed.  In the following results, the repos
 named 'rollback' is the one that I have made the changes to and thus the one
 to be most aware of.  Please let me know if there is something that needs to
 be corrected before I perform the commit tomorrow.  BTW, there are not
 currently test results for 'rollback' on Linux, so that is why it is not
 filled in yet.
 
 Thanks.
 
 -Tom
 
 
 
 Windows 2000
 
 \build\build.bat clean most
 
 Source Repos  Test Results
 Branch_4_0_DR3success
 HEAD  success
 rollback  success
 
 \jmx\build.bat test-compliance-full-JBossMX  test-implementation
 test-performance-JBossMX  test-serialization test-stress-JBossMX
 
 Source Repos  Test Target Test Results
 Branch_4_0_DR3test-compliance-full-JBossMXTests run: 926,  Failures: 4,
 Errors: 2
 HEAD  test-compliance-full-JBossMXTests run: 706,  Failures: 3,  Errors: 0
 rollback  test-compliance-full-JBossMXTests run: 926,  Failures: 4,  Errors:
 2
 Branch_4_0_DR3test-implementation Tests run: 67,  Failures: 1,  Errors: 1
 HEAD  test-implementation OK (37 tests)
 rollback  test-implementation Tests run: 67,  Failures: 1,  Errors: 1
 Branch_4_0_DR3test-performance-JBossMXOK (14 tests)
 HEAD  test-performance-JBossMXOK (11 tests)
 rollback  test-performance-JBossMXOK (14 tests)
 Branch_4_0_DR3test-serialization  Tests run: 93,  Failures: 1,  Errors: 0
 HEAD  test-serialization  Tests run: 93,  Failures: 0,  Errors: 90
 rollback  test-serialization  Tests run: 93,  Failures: 1,  Errors: 1
 Branch_4_0_DR3test-stress-JBossMX OK (1 tests)
 HEAD  test-stress-JBossMX OK (1 test)
 rollback  test-stress-JBossMX OK (1 test)
 
 \testsuite\build.bat tests
 
 Source Repos  TestFailuresErrors  Success rateTime
 Branch_4_0_DR3847 13  480 41.79%  5817.237
 HEAD  733 54  304 51.16%  1687.185
 rollback  718 62  308 48.47   1656.592
 
 
 Linux - Red Hat 7.3
 
 \build\build.sh clean most
 
 Source Repos  Test Results
 Branch_4_0_DR3success
 HEAD  success
 rollback
 
 \jmx\build.sh test-compliance-full-JBossMX  test-implementation
 test-performance-JBossMX  test-serialization test-stress-JBossMX
 
 Source Repos  Test Target Test Results
 Branch_4_0_DR3test-compliance-full-JBossMXTests run: 926,  Failures: 4,
 Errors: 2
 HEAD  test-compliance-full-JBossMXTests run: 706,  Failures: 3,  Errors: 0
 rollback  test-compliance-full-JBossMX
 Branch_4_0_DR3test-implementation Tests run: 67,  Failures: 1,  Errors: 1
 HEAD  test-implementation OK (37 tests)
 rollback  test-implementation
 Branch_4_0_DR3test-performance-JBossMXOK (14 tests)
 HEAD  test-performance-JBossMXOK (11 tests)
 rollback  test-performance-JBossMX
 Branch_4_0_DR3test-serialization  Tests run: 93,  Failures: 1,  Errors: 0
 HEAD  test-serialization  Tests run: 93,  Failures: 0,  Errors: 90
 rollback  test-serialization
 Branch_4_0_DR3test-stress-JBossMX OK (1 tests)
 HEAD  test-stress-JBossMX OK (1 test)
 rollback  test-stress-JBossMX
 
 \testsuite\build.sh tests
 
 Source Repos  TestFailuresErrors  Success rateTime
 Branch_4_0_DR3850 12  479 42.24%  3711.145
 HEAD  777 57  331 50.06%  1779.778
 rollback
 
 
 The complete testsuite 

[JBoss-dev] Missing package info for app classes deployed in HEAD

2003-09-19 Thread Francisco Reverbel
IIOP tests are currently broken in HEAD.

The RMI/IIOP analysis and stub generation code calls cls.getPackage().
The tests break because getPackage() is returning null on 
application-defined classes. If I print out the class and the package 
of an application class, I get something like 

  cls = class org.jboss.test.bankiiop.interfaces.AccountData
  pkg = null

Non-application classes, however, still have package info:

  cls = interface javax.ejb.Handle
  pkg = package javax.ejb, JBoss, version 4.0.0

  cls = interface javax.ejb.EJBObject
  pkg = package javax.ejb, JBoss, version 4.0.0

According to the getPackage() documentation, the method returns null 
if no package object was created by the class loader of the target 
class. Looks like this problem is related with the bytecode enhancement 
performed at load time. 

Francisco



---
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-group] Re: [JBoss-dev] Missing package info for app classes deployed in HEAD

2003-09-19 Thread Francisco Reverbel
Thanks, Adrian.

It is not urgent, I am not working anymore today.

If you point me to the file that misses a definePackage(), I'll 
add it myself next time I find some time to work on JBoss. Unless 
you do it before me, of course. 

Cheers,

Francisco

On 19 Sep 2003, Adrian Brock wrote:

 The defineClass() is missing a definePackage()
 see the hack in AOP's standalone system classloader.
 
 I can fix it later if it isn't urgent.
 
 This needs improving as it does not retrieve manifest
 information.
 
 Regards,
 Adrian
 
 On Fri, 2003-09-19 at 22:49, Francisco Reverbel wrote:
  IIOP tests are currently broken in HEAD.
  
  The RMI/IIOP analysis and stub generation code calls cls.getPackage().
  The tests break because getPackage() is returning null on 
  application-defined classes. If I print out the class and the package 
  of an application class, I get something like 
  
cls = class org.jboss.test.bankiiop.interfaces.AccountData
pkg = null
  
  Non-application classes, however, still have package info:
  
cls = interface javax.ejb.Handle
pkg = package javax.ejb, JBoss, version 4.0.0
  
cls = interface javax.ejb.EJBObject
pkg = package javax.ejb, JBoss, version 4.0.0
  
  According to the getPackage() documentation, the method returns null 
  if no package object was created by the class loader of the target 
  class. Looks like this problem is related with the bytecode enhancement 
  performed at load time. 
  
  Francisco
  
  
  
  ---
  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
 -- 
  
 Adrian Brock
 Director of Support
 Back Office
 JBoss Group, LLC 
  
 
 ___
 jboss-group mailing list
 [EMAIL PROTECTED]
 http://mail.jboss.org/mailman/listinfo/jboss-group
 
 



---
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 failing on Branch_3_2

2003-09-10 Thread Francisco Reverbel
Fresh checkout. The build.sh script fails with this error:

compile-classes:
[javac] Compiling 584 source files to
/usr/local/reverbel/jboss-3.2/server/output/classes
/usr/local/reverbel/jboss-3.2/server/output/gen-src/org/jboss/invocation/local/LocalInvokerMBean.java:10:
 '}'
expected
^
1 error

BUILD FAILED

Does anybody else see this?

Francisco



---
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] Build failing on Branch_3_2

2003-09-10 Thread Francisco Reverbel
Java 1.4.2 on Debian 3.0 (woody). I am using an old Linux kernel, 
though.

$ java -version
java version 1.4.2
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
$ uname -a
Linux pong 2.2.19 #1 SMP Wed Oct 17 08:56:33 BRST 2001 i686 unknown

Francisco

On Wed, 10 Sep 2003, Scott M Stark wrote:

 No, I just did a checkout and build of 3.2 using 1.4.2 on RH9. What compiler and 
 OS are you using?
 
 Francisco Reverbel wrote:
 
  Fresh checkout. The build.sh script fails with this error:
  
  compile-classes:
  [javac] Compiling 584 source files to
  /usr/local/reverbel/jboss-3.2/server/output/classes
  /usr/local/reverbel/jboss-3.2/server/output/gen-src/org/jboss/invocation/local/LocalInvokerMBean.java:10:
   '}'
  expected
  ^
  1 error
  
  BUILD FAILED
  
  Does anybody else see this?
  
  Francisco
  
 
 
 
 ---
 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


Re: [JBoss-dev] Build failing on Branch_3_2

2003-09-10 Thread Francisco Reverbel
It works after I removed file 

output/gen-src/org/jboss/invocation/local/LocalInvokerMBean.java

which was incomplete. This file has not been fully generated due
to an out of memory error in a previous run of build.sh.

Thanks,

Francisco

On Wed, 10 Sep 2003, Scott M Stark wrote:

 No, I just did a checkout and build of 3.2 using 1.4.2 on RH9. What compiler and 
 OS are you using?
 
 Francisco Reverbel wrote:
 
  Fresh checkout. The build.sh script fails with this error:
  
  compile-classes:
  [javac] Compiling 584 source files to
  /usr/local/reverbel/jboss-3.2/server/output/classes
  /usr/local/reverbel/jboss-3.2/server/output/gen-src/org/jboss/invocation/local/LocalInvokerMBean.java:10:
   '}'
  expected
  ^
  1 error
  
  BUILD FAILED
  
  Does anybody else see this?
  
  Francisco
  
 
 
 
 ---
 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


Re: [JBoss-dev] Build failing on Branch_3_2

2003-09-10 Thread Francisco Reverbel
Thanks, Adrian. You're right, the error does not happen in a clean 
build.

I have been getting out of memory errors from clean builds. Xdoclet... 
My second attempt typically succeeds. This time, however, the clean 
build left me with an incomplete source file.

Cheers,

Francisco

On 10 Sep 2003, Adrian Brock wrote:

 Hi Francisco,
 
 It looks like xdoclet screwed up at some point.
 This is generated source.
 Do you get the same error if you ./build.sh clean
 before rebuilding?
 
 Regards,
 Adrian
 
 On Wed, 2003-09-10 at 16:14, Francisco Reverbel wrote:
  Java 1.4.2 on Debian 3.0 (woody). I am using an old Linux kernel, 
  though.
  
  $ java -version
  java version 1.4.2
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
  Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
  $ uname -a
  Linux pong 2.2.19 #1 SMP Wed Oct 17 08:56:33 BRST 2001 i686 unknown
  
  Francisco
  
  On Wed, 10 Sep 2003, Scott M Stark wrote:
  
   No, I just did a checkout and build of 3.2 using 1.4.2 on RH9. What compiler and 
   OS are you using?
   
   Francisco Reverbel wrote:
   
Fresh checkout. The build.sh script fails with this error:

compile-classes:
[javac] Compiling 584 source files to
/usr/local/reverbel/jboss-3.2/server/output/classes
/usr/local/reverbel/jboss-3.2/server/output/gen-src/org/jboss/invocation/local/LocalInvokerMBean.java:10:
 '}'
expected
^
1 error

BUILD FAILED

Does anybody else see this?

Francisco

   
   
   
   ---
   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
 -- 
  
 Adrian Brock
 Director of Support
 Back Office
 JBoss Group, LLC 
  
 
 
 
 ---
 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


Re: [JBoss-dev] RMI-IIOP type restrictions

2003-08-14 Thread Francisco Reverbel
Hi Adam,

On Mon, 11 Aug 2003, Adam Wasserman wrote:

 
 Hello all,
 
 I am using JBoss 3.2.1 and would like to deploy a stateless session bean 
 using the iiop invoker.  The remote interface of this bean makes use of an 
 object with a reference to an array of java.util.Map objects.  During 
 deployment, JBoss performs an interface analysis on the remote interface.  
 I'm not very knowledgeable in this area yet, but I imagine that JBoss is 
 busy verifying all the types referenced directly or indirectly by the 
 object referenced in the remote interface and producing IDL definitions for 
 them.  This deployment process always fails, and it is failing on the 
 reference to the array of java.util.Map:
 
 private Map[] hoursPerProjectPerDay;
 
 The exception I get can be found at the end of this posting.
 
 If I change the reference to:
 
 private HashMap[] hoursPerProjectPerDay;
 
 there is no problem at deployment time.
 
 Am I violating a type restriction in IDL?

No you are not. You have found a bug in JBoss/IIOP.

I'm looking into it...

Cheers,

Francisco

 
 Many thanks,
 Adam
 
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ParameterAnalysis] 
 ParameterAnalysis(): cls=[java.util.Map] typeIDLName=[::java::util::Map].
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
 ContainerImplDelegate._lookup(java) entered.
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
 ContainerImplDelegate._lookup(util) entered.
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
 ContainerDelegateImpl.add() added util.
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ContainerAnalysis] 
 Interface count: 0
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ValueDefImpl] 
 ValueDefImpl.type() entered.
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ValueDefImpl] 
 ValueDefImpl.type() returning.
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.InterfaceRepository] 
 Value: base=Map
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
 ContainerDelegateImpl.add() added Map.
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ContainerAnalysis] 
 Constants count: 0
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.InterfaceRepository] 
 Value member count: 0
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ContainerAnalysis] 
 Attribute count: 1
 2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
 ContainerDelegateImpl.add() added Empty.
 2003-08-11 15:03:16,273 ERROR [org.jboss.ejb.StatelessSessionContainer] 
 Initialization failed
 java.lang.NullPointerException
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addArray(InterfaceRepository.java:806)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addClass(InterfaceRepository.java:703)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.getTypeCode(InterfaceRepository.java:311)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addValue(InterfaceRepository.java:965)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addClass(InterfaceRepository.java:729)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.getTypeCode(InterfaceRepository.java:311)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addOperations(InterfaceRepository.java:650)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addInterface(InterfaceRepository.java:898)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.addClass(InterfaceRepository.java:710)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.getTypeCode(InterfaceRepository.java:311)
   at 
 org.jboss.iiop.rmi.ir.InterfaceRepository.mapClass(InterfaceRepository.java:137)
   at org.jboss.proxy.ejb.IORFactory.create(IORFactory.java:251)
   at 
 org.jboss.ejb.StatelessSessionContainer.createService(StatelessSessionContainer.java:164)
   at 
 org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at 
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
   at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
   at 
 org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
   at $Proxy8.create(Unknown Source)
   at org.jboss.system.ServiceController.create(ServiceController.java:310)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at 
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
   at 

Re: [JBoss-dev] RMI-IIOP type restrictions

2003-08-14 Thread Francisco Reverbel
This bug is fixed in CVS Branch_3_2.

It affected arrays whose element type corresponds (per the Java 
to IDL mapping) to an abstract valuetype. 

BTW: Adam's workaround was effective because he replaced an abstract 
valuetype (java.util.Map) by a concrete one (java.util.HashMap).

Cheers,

Francisco

On Wed, 13 Aug 2003, Francisco Reverbel wrote:

 Hi Adam,
 
 On Mon, 11 Aug 2003, Adam Wasserman wrote:
 
  
  Hello all,
  
  I am using JBoss 3.2.1 and would like to deploy a stateless session bean 
  using the iiop invoker.  The remote interface of this bean makes use of an 
  object with a reference to an array of java.util.Map objects.  During 
  deployment, JBoss performs an interface analysis on the remote interface.  
  I'm not very knowledgeable in this area yet, but I imagine that JBoss is 
  busy verifying all the types referenced directly or indirectly by the 
  object referenced in the remote interface and producing IDL definitions for 
  them.  This deployment process always fails, and it is failing on the 
  reference to the array of java.util.Map:
  
  private Map[] hoursPerProjectPerDay;
  
  The exception I get can be found at the end of this posting.
  
  If I change the reference to:
  
  private HashMap[] hoursPerProjectPerDay;
  
  there is no problem at deployment time.
  
  Am I violating a type restriction in IDL?
 
 No you are not. You have found a bug in JBoss/IIOP.
 
 I'm looking into it...
 
 Cheers,
 
 Francisco
 
  
  Many thanks,
  Adam
  
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ParameterAnalysis] 
  ParameterAnalysis(): cls=[java.util.Map] typeIDLName=[::java::util::Map].
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
  ContainerImplDelegate._lookup(java) entered.
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
  ContainerImplDelegate._lookup(util) entered.
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
  ContainerDelegateImpl.add() added util.
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ContainerAnalysis] 
  Interface count: 0
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ValueDefImpl] 
  ValueDefImpl.type() entered.
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ValueDefImpl] 
  ValueDefImpl.type() returning.
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.InterfaceRepository] 
  Value: base=Map
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
  ContainerDelegateImpl.add() added Map.
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ContainerAnalysis] 
  Constants count: 0
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.InterfaceRepository] 
  Value member count: 0
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ContainerAnalysis] 
  Attribute count: 1
  2003-08-11 15:03:16,273 DEBUG [org.jboss.iiop.rmi.ir.ContainerImplDelegate] 
  ContainerDelegateImpl.add() added Empty.
  2003-08-11 15:03:16,273 ERROR [org.jboss.ejb.StatelessSessionContainer] 
  Initialization failed
  java.lang.NullPointerException
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addArray(InterfaceRepository.java:806)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addClass(InterfaceRepository.java:703)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.getTypeCode(InterfaceRepository.java:311)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addValue(InterfaceRepository.java:965)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addClass(InterfaceRepository.java:729)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.getTypeCode(InterfaceRepository.java:311)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addOperations(InterfaceRepository.java:650)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addInterface(InterfaceRepository.java:898)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.addClass(InterfaceRepository.java:710)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.getTypeCode(InterfaceRepository.java:311)
  at 
  org.jboss.iiop.rmi.ir.InterfaceRepository.mapClass(InterfaceRepository.java:137)
  at org.jboss.proxy.ejb.IORFactory.create(IORFactory.java:251)
  at 
  org.jboss.ejb.StatelessSessionContainer.createService(StatelessSessionContainer.java:164)
  at 
  org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
  at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
  at 
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at 
  org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at 
  org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
  at $Proxy8.create(Unknown Source)
  at org.jboss.system.ServiceController.create(ServiceController.java:310

Re: [JBoss-dev] releasing on Sunday

2003-05-29 Thread Francisco Reverbel
All IIOP tests fail in the 4.0 branch. Does anybody know why?
I thought there were no IIOP changes in head since it was branched
off 3.x.

There are some IIOP fixes in 3.2 that need to be merged into head. 
Following the usual test before, test after procedure, I run 
the tests before doing it, only to find out that IIOP was already 
broken. :-(

Cheers,

Francisco


On Tue, 27 May 2003, Bill Burke wrote:

 We'll be doing the DR1 release on Sunday.  Please ask Scott or me before
 committing.  We'll be more and more reluctant to allow commits as we get
 closer.  We should be stabalizing not adding new features at the last
 minute.
 
 Thanks,
 
 Bill
 
 
 Bill Burke
 Chief Architect
 JBoss Group, LLC
 
 
 Cast your vote for JBoss as JDJ Best App Server
 
 http://www.sys-con.com/java/readerschoice2003/vote.cfm
 
 
 
 ---
 This SF.net email is sponsored by: ObjectStore.
 If flattening out C++ or Java code to make your application fit in a
 relational database is painful, don't do it! Check out ObjectStore.
 Now part of Progress Software. http://www.objectstore.net/sourceforge
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] 3.2 doesn't run on IBM JDK?

2003-03-30 Thread Francisco Reverbel
The 3.2 branch (fresh check out just taken from CVS) is giving me
the exception below with IBM's VM on Linux.

Shouldn't we fix this before 3.2 goes final?

Cheers,

Francisco

-
$ uname -a
Linux pong 2.2.19 #1 SMP Wed Oct 17 08:56:33 BRST 2001 i686 unknown
-
$ java -version
java version 1.4.0
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0)
Classic VM (build 1.4.0, J2RE 1.4.0 IBM build cxia32140-20020917a (JIT enabled: jitc))
-
$ ./run.sh
... [snip]
16:38:33,411 ERROR [MainDeployer] could not create
deployment: 
file:/usr/local/reverbel/jboss-3.2/build/output/jboss-3.2.0RC5/server/default/conf/jboss-service.xml
java.lang.NoClassDefFoundError: $Proxy0
at sun.reflect.GeneratedConstructorAccessor9.newInstance(Unknown
Source) at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:42)
at java.lang.reflect.Constructor.newInstance(Constructor.java:299)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:585)
at
org.jboss.system.ServiceController.getServiceProxy(ServiceController.java:739)
at
org.jboss.system.ServiceController.create(ServiceController.java:276)   at
org.jboss.system.ServiceController.create(ServiceController.java:243)   at
sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
at java.lang.reflect.Method.invoke(Method.java:335)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.create(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:207)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:784)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40)
at java.lang.reflect.Method.invoke(Method.java:335)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy6.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:361)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:268)
at org.jboss.Main.boot(Main.java:159)
at org.jboss.Main$1.run(Main.java:397)
at java.lang.Thread.run(Thread.java:566)
16:38:33,504 ERROR [Server] Failed to start
...[snip]



---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] jboss_3_2.dtd updated

2003-03-05 Thread Francisco Reverbel
A protocol is associated with a reference (proxy) factory. My previous 
message stressed the protocol (invoker) rather than the proxy factory. 
The crucial thing is the reference factory, i.e., whether a remote 
reference is a serialized proxy or an IOR.

Suppose method m of bean X returns some EJBObject. Moreover, suppose bean Y
also has a method that returns an EJBObject, which bean Y obtains by calling
m on X.

 - If a non-CORBA (JRMP/HTTP/SOAP/whatever) client written in Java calls
   bean Y to get an EJBObject, it receives a serialized proxy.

 - If a CORBA client (possibly written in C++) performs the same call on 
   bean Y, it must receive an IOR.

Serialized proxies give the EJB the freedom to return a serialized proxy 
that uses a protocol different from the one used by the current invocation. 
There is no such freedom with IIOP. You can still optimize local calls, 
but must use IORFactory, the IIOP-specific proxy factory. (Here I prefer
the more general term reference factory). 

I would expect the same issue to appear for any standardized protocol
that supports non-Java clients. Does it make sense for a Visual Basic 
client to get an EJBObject by interacting with an EJB via SOAP? If so
(I don't really know), the EJBObject cannot be a serialized Java proxy.

Cheers,

Francisco


On Tue, 4 Mar 2003, Scott M Stark wrote:

 I still don't understand why the incoming protocol should dictate the protocol
 that any invocations made the the target bean. If I'm bean X and some .NET
 clown invoked via soap, why do I want to in turn invoke the beans Y and Z
 through soap when I can use a local interface or optimized RMI?
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 
 - Original Message - 
 From: Francisco Reverbel [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Sent: Tuesday, March 04, 2003 10:01 PM
 Subject: Re: [JBoss-dev] jboss_3_2.dtd updated
 
 
  
  These ejb-refs could have been defined outside of the invoker element.
  Invoker-specific ejb-refs make sense when you have multiple invokers
  per EJB. They are not really needed in the bankiiop testcase, which uses
  a single invoker (the IIOP invoker). I have probably placed them within 
  the invoker element just because their jndi-names are IIOP-specific.
  
  If you have multiple invokers per EJB, invoker-specific ejb-refs act as 
  a kind of multivalued link from the bean ENC to a set of JNDI names (one 
  per invoker). Such a multivalued link allows outgoing invocations to be
  transparently performed through the same protocol (invoker) as the current
  invocation. The particular JNDI name seen at the end of the multivalued
  link depends on the invoker through which the current invocation arrived. 
  The bean code just uses an ejb-ref, such as ejb/Bank. If the bean code 
  runs within an IIOP invocation, ejb/Bank means iiop/bank/Bank, which 
  is bound to a CORBA IOR. If the same code runs within a JRMP invocation,
  ejb/Bank could mean bank/Bank, which would be bound to a serialized 
  JRMP proxy. 
  
  Cheers,
  
  Francisco
 
 
 
 ---
 This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
 for complex code. Debugging C/C++ programs can leave you feeling lost and 
 disoriented. TotalView can help you find your way. Available on major UNIX 
 and Linux platforms. Try it free. www.etnus.com
 ___
 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


Re: [JBoss-dev] jboss_3_2.dtd updated

2003-03-04 Thread Francisco Reverbel
On Tue, 4 Mar 2003, Scott M Stark wrote:

 The jboss_3_2.dtd was way out of date with respect to the container
 invoker configuration so I updated it and checked it in. Take a look
 at this and see if there are other missing elements or elements that
 should be dropped.
 
 One construct that I don't understand in the invoker-bindings/invoker
 elements are the ejb-ref child elements. For example, this setup
 from the bankiiop testcase:
 
   session
  ejb-nameTeller/ejb-name
  jndi-namebank/Teller/jndi-name
  configuration-nameStandard Stateless SessionBean/configuration-name
  invoker-bindings
 invoker
invoker-proxy-binding-nameiiop/invoker-proxy-binding-name
ejb-ref
   ejb-ref-nameejb/Customer/ejb-ref-name
   jndi-nameiiop/bank/Customer/jndi-name
/ejb-ref
ejb-ref
   ejb-ref-nameejb/Account/ejb-ref-name
   jndi-nameiiop/bank/Account/jndi-name
/ejb-ref
ejb-ref
   ejb-ref-nameejb/Bank/ejb-ref-name
   jndi-nameiiop/bank/Bank/jndi-name
/ejb-ref
 /invoker
  /invoker-bindings
   /session
 
 What is the purpose of the invoker binding specific ejb-refs?
 It still just a link from the bean ENC to a JNDI name so why
 are then under the invoker-bindings?

These ejb-refs could have been defined outside of the invoker element.
Invoker-specific ejb-refs make sense when you have multiple invokers
per EJB. They are not really needed in the bankiiop testcase, which uses
a single invoker (the IIOP invoker). I have probably placed them within 
the invoker element just because their jndi-names are IIOP-specific.

If you have multiple invokers per EJB, invoker-specific ejb-refs act as 
a kind of multivalued link from the bean ENC to a set of JNDI names (one 
per invoker). Such a multivalued link allows outgoing invocations to be
transparently performed through the same protocol (invoker) as the current
invocation. The particular JNDI name seen at the end of the multivalued
link depends on the invoker through which the current invocation arrived. 
The bean code just uses an ejb-ref, such as ejb/Bank. If the bean code 
runs within an IIOP invocation, ejb/Bank means iiop/bank/Bank, which 
is bound to a CORBA IOR. If the same code runs within a JRMP invocation,
ejb/Bank could mean bank/Bank, which would be bound to a serialized 
JRMP proxy. 

Cheers,

Francisco



---
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] Remote class loading servlet

2003-02-12 Thread Francisco Reverbel
You won't find this in the servlet spec. 

SomeClassName[some/object/id]/some/file/path is a JBoss convention
for specifying Java classes and resources dynamically downloaded by
clients. It is used by org.jboss.web.WebClassLoader and by 
org.jboss.iiop.WebCL. See comments in

  server/src/main/org/jboss/web/WebServer.java

See also

  server/src/main/org/jboss/web/WebClassLoader.java 
  iiop/src/main/org/jboss/iiop/WebCL.java

Cheers,

Francisco

On Wed, 12 Feb 2003, James Cooley wrote:

 Hi Dain, Scott,
 
 I wrote a servlet that accepts a request from a java.net.URLClassLoader 
 and returns the class. AFAIK I need only support requests of the kind
   org/jboss/util/stream/Streams.class
 but the exising WebServer class also supports
 
   SomeClassName[some/object/id]/some/file/path
 
 I can't find where this protocol is defined elsewhere - please point me 
 at the spec if we need to support it - I'm a bit blind as to what we 
 need as you can see from the next question ...
 
 I created a class-loader.war and I tried running the JRMP tests with
 
 ./testsuite/build.sh 
 -Djava.rmi.server.codebase=http://localhost:8080/class-loader/ 
 -Dtest=jrmp test
 
 but it doesn't work and I get
 
   ERROR [JRMPInvoker] Starting failed: java.rmi.server.ExportException: 
 Port already in use: 4447;
 
 What am I doing wrong? How can I test this.
 
 James
 
 Dain Sundstrom wrote:
  We have a small project open for a volunteer.  In Jboss 2 and 3 we have 
  a custom lightweight web server (port 8083) that returns java class 
  files from the classLoader.getResouceAsStream to RMI clients (this is 
  how remote class loading happens).  I talked to Scott at JBoss Boot Camp 
  and we think it is a good idea to replace this with a plain old Servlet 
  for JBoss 4.0 so it can work with regular security, pooling and such.  
  This is a fairly simple piece of code and shouldn't take longer then a 
  day or two.  If you are interested the code can be found in 
  jboss-head/server/src/main/org/jboss/web/WebServer.java
  
  -dain
  
  
  
  ---
  This SF.NET email is sponsored by:
  SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
  http://www.vasoftware.com
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
 
 
 
 
 ---
 This SF.NET email is sponsored by:
 SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
 http://www.vasoftware.com
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Remote class loading servlet

2003-02-08 Thread Francisco Reverbel
The IIOP tests also rely on remote class loading. They should
still work after the simple web server is replaced by a servlet.
(The *-iiop tests run on a server with configuration 'all'.)

Cheers,

Francisco


On Fri, 7 Feb 2003, Scott M Stark wrote:

 There is a dynamic class loading unit test:
 org.jboss.test.jrmp.test.DynLoadingUnitTestCase
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 
 - Original Message - 
 From: Dain Sundstrom [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Friday, February 07, 2003 11:50 AM
 Subject: Re: [JBoss-dev] Remote class loading servlet
 
 
  On Friday, February 7, 2003, at 01:28 PM, James Cooley wrote:
  
   Dain Sundstrom wrote:
   Scott,
   I'm putting the question for you at the top, so you can see it.  How 
   do we specify the code base for remote loading?  If James writes this 
   he will need to change it to point to the servlet.
   James,
   You are way over thinking this.
  
   As I said there isn't a unit test for this so I guess it looked like 
   it was doing more than it was doing in reality.
  
  Good idea. Can you add a unit test for this also?  :)
  
  -dain
  
  
  
  ---
  This SF.NET email is sponsored by:
  SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
  http://www.vasoftware.com
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
 
 
 ---
 This SF.NET email is sponsored by:
 SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
 http://www.vasoftware.com
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] Transaction propagation change

2003-01-21 Thread Francisco Reverbel
On Tue, 21 Jan 2003, marc fleury wrote:

  And, finally, why did you tightly couple distributed tx logic with 
  invoker's implementation? Why is not it possible to write an 
  interceptor 
  that does distributed tx stuff that you've described but in invoker 
  independent way?
 
 If only ole husgaard was awake :)
 
 I have been asking the same question for about a year and a half. I
 forgot the reason, which probably means it wasn't real, but Ole seemed
 to have one... 

Transaction propagation over IIOP is a reason. CORBA specifies that 
transaction info goes in the service context, which is a field of 
the IIOP request.

Francisco



---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Transaction propagation change

2003-01-21 Thread Francisco Reverbel
On Tue, 21 Jan 2003, David Jencks wrote:

 
 On Tuesday, January 21, 2003, at 09:43 AM, Francisco Reverbel wrote:
 
  On Tue, 21 Jan 2003, marc fleury wrote:
 
  And, finally, why did you tightly couple distributed tx logic with
  invoker's implementation? Why is not it possible to write an
  interceptor
  that does distributed tx stuff that you've described but in invoker
  independent way?
 
  If only ole husgaard was awake :)
 
  I have been asking the same question for about a year and a half. I
  forgot the reason, which probably means it wasn't real, but Ole seemed
  to have one...
 
  Transaction propagation over IIOP is a reason. CORBA specifies that
  transaction info goes in the service context, which is a field of
  the IIOP request.
 
 Does this constrain non-iiop invokers in any way?

I don't think so. Ideally it would be good if transaction propagation 
(i.e. all the code that inserts/extracts XIDs into/from invocation 
objects) were somehow encapsulated within a TxPropagator MBean,
which would be specified by the contained configuration. Except for
the IIOP invoker, all invokers would use the default TxPropagator 
MBean. The IIOP invoker would use an special tx propagator, which
would insert/extract XIDs into/from IIOP service contexts.

The idea of a default TxPropagator is similar to our ProxyFactory
notion, in the sense that it works with all invokers but the IIOP 
invoker. The 3.2 container config includes a set of invoker/proxy 
bindings. Valid bindings are

IIOPInvoker / IORFactory 
*   / ProxyFactory  (where * is any non-IIOP invoker)

We could have invoker/proxy/txPropagator bindings instead:

IIOPInvoker / IORFactory   / IIOPTxPropagator
*   / ProxyFactory / TxPropagator

Anyway, I don't think the IIOP case should constrain you from doing
whatever needs to be done to have transactions propagated over non-IIOP
protocols. Right now tx propagation over IIOP does not look like a 
prioritary thing, so I don't know if an IIOPTxPropagator will be written 
or not.

 Do we control anything about the client side of the iiop invoker?  

No.

 How about if the client is java rather than c++?  

In this case client-side stubs can (but are not required to) be 
dynamically downloaded from the server. 

 Are there some short yet informative docs on how iiop into jboss works?

No. I am planning to work on doco on February. Right now there is only 
the blurb in http://www.jboss.org/developers/projects/jboss/iiop.jsp, 
which applies to 3.0. (In 3.2 there were IIOP-related changes on the 
container config.)

Do you have specific questions?

Cheers,

Francisco



---
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] error trying to run iiop tests

2002-11-15 Thread Francisco Reverbel
The one-test target does not work for IIOP tests, which require
IIOP-related arguments to be passed to the JVM.

To run IIOP tests, use the iiop-test target (runs all IIOP tests in a 
given directory) or the tests-iiop-stress target (runs all IIOP tests):

  testsuite/build.sh -Dtest=helloiiop -Dnojars=true iiop-test

(Runs all IIOP tests in the helloiiop dir)

  testsuite/build.sh -Dnojars=true tests-iiop-stress

(Runs all IIOP tests.)

The -Dnojars=true switch may be omitted, I use it to avoid rebuilding
the test jars every time.

Cheers,

Francisco


On Thu, 14 Nov 2002, Emerson Cargnin - SICREDI Serviços wrote:

 I've tried to run iiop tests (in 3.0.5rc1 and 3.2beta2) through the command:
 
   ./build.sh 
 -Dtest=org.jboss.test.helloiiop.test.HelloTimingStressTestCase one-test
 
 but it down't work, just get a classcast exception.
 
 i started with all conf
 
 
 -- 
 
 | Emerson Cargnin  |
 | Analista de Sistemas Sr. |
 | Tel : (051) 3358-4959|
 | SICREDI Serviços |
 | Porto Alegre - Brasil|
 |xx|
 
 
 
 ---
 This sf.net email is sponsored by: To learn the basics of securing
 your web site with SSL, click here to get a FREE TRIAL of a Thawte
 Server Certificate: http://www.gothawte.com/rd524.html
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Where is HttpInvoker?

2002-09-29 Thread Francisco Reverbel

I looked for Scott's HttpInvoker in HEAD and didn't find it there. 
Where is it?

Cheers,

Francisco



---
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] is pooling useless?

2002-09-11 Thread Francisco Reverbel

Well, if you are pooling fine grained objects you should not 
use java.util.LinkedList to implement the pool. Whenever you 
add an element to a LinkedList you are creating an auxiliary 
Entry object, with fields `element', `next', and `previous'. 

To do pooling of fine grained objects you should add a `next' 
field to the objects you are pooling and use your own linked 
list implementation. Otherwise you are trading the creation of 
pooled objects by the creation of Entry objects plus the 
sychronization cost. Not a good deal.

Some time ago I had to optimize critical-path code and a pool 
of fine-grained objects (linked together by a `next' field within 
each object) was very useful.

Cheers,

Francisco

On Wed, 11 Sep 2002, David Jencks wrote:

 Pooling is mostly useful if the object holds an expensive resource such as
 a database connection.  For just plain data I think the synchronization
 costs of pooling things tend to outweigh the construction costs of making
 new ones pretty quickly.  Ole recently removed the (pooled) TxCapsule in
 favor of new-each-time TransactionImpl for this reason.
 
 Your results are fun to contemplate, though.
 
 david jencks
 
 On 2002.09.10 23:59:40 -0400 Bill Burke wrote:
  I was looking into pooling Invocation objects so I thought I'd test to
  see
  if it is actually better.  With this test case, its about 4% faster to
  pool
  on JDK 1.3.1 Win2k.
  
  With JDK 1.4.0 on Win2k, Non-pooling is actually 7% faster!
  
  import java.util.*;
  
  
  public class testpool
  {
 HashMap trans;
 HashMap as;
 HashMap pay;
  
 public testpool()
 {
trans = new HashMap();
as = new HashMap();
pay = new HashMap();
 }
 public void clear()
 {
trans.clear();
as.clear();
pay.clear();
 }
  
 public void addStuff()
 {
for (int i = 0; i  5; i++)
{
   trans.put(new Integer(i), new Integer(i));
   as.put(new Integer(i), new Integer(i));
   pay.put(new Integer(i), new Integer(i));
}
 }
  
 public static LinkedList pool = new LinkedList();
  
 public static void main(String[] args)
 {
long start;
long end;
  
System.out.println(testing non pool);
start = System.currentTimeMillis();
for (int i = 0; i  100; i++)
{
   testpool p = new testpool();
   p.addStuff();
}
end = System.currentTimeMillis() - start;
System.out.println(time:  + end);
  
System.out.println(testing pool);
start = System.currentTimeMillis();
for (int i = 0; i  100; i++)
{
   testpool p = null;
   if (pool.isEmpty()) p = new testpool();
   else
   {
  synchronized(pool)
  {
 p = (testpool)pool.removeFirst();
  }
   }
   if (p == null) p = new testpool();
  
   p.addStuff();
   p.clear();
   synchronized(pool)
   {
  pool.add(p);
   }
}
end = System.currentTimeMillis() - start;
System.out.println(time:  + end);
 }
  }}
  
  
  
  ---
  In remembrance
  www.osdn.com/911/
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-development
  
  
 
 
 ---
 In remembrance
 www.osdn.com/911/
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 



---
In remembrance
www.osdn.com/911/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] YAJI (Yet Another JBoss Invoker)

2002-08-09 Thread Francisco Reverbel

Hi,

I am also playing with a new invoker. Well, not really new... It is 
actually the JRMP invoker code, with just a few changes to sent the 
Invocation over IIOP rather than JRMP. In the lack of a better name, 
I am calling it JavaIIOPInvoker.

JavaIIOPInvoker is quite different from the plain IIOPInvoker. It is also
much simpler. By way of comparison:

 - IIOPInvoker allows IIOP access to the actual interfaces of deployed 
   beans. When a client calls create() on an EJBHome, an IIOP request with 
   operation name create goes over the wire and is handled by the 
   plain IIOPInvoker. 

 - JavaIIOPInvoker allow IIOP acess to a single interface: Invoker, which
   essentially has a single operation, invoke(). When a client class 
   create() on an EJBHome, an IIOP request with operation name invoke
   goes over the wire and is handled by the JavaIIOPInvoker. Info on the
   actual method to be invoked (create(), in this case) goes within the
   Invocation parameter to invoke().

Unlike IIOPInvoker, which uses an IORFactory, JavaIIOPInvoker works with 
the standard JBoss ProxyFactory. Whan a client gets a reference to an
EJBHome or EJBObject, it really gets a serialized Java proxy, just like
in the JRMP case. The only difference is that this proxy's delegate has
a CORBA reference (IOR) to the JavaIIOPInvoker, instead of a RMI/JRMP
reference to the JRMPInvoker. Everything else works (or should work) as 
in the JRMP case: interceptors, client container, transactions, etc.

JavaIIOPInvoker is useless to non-Java clients (hence its name). I am
interested in comparing it with the JRMPInvoker WRT performance. So far
(a simple hello test) I got pretty much the same numbers... Of course,
the performance may change with the ORB used. I am doing everything 
with JacORB.

Should I commit this stuff? Right now I am not really sure if it will
be useful or not.

Cheers,

Francisco



---
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] Our IIOP port number

2002-08-02 Thread Francisco Reverbel

So far we have been using port 8683 for IIOP. We picked the well 
know port number assigned to IIOP (which is 683) and added 8000 
just to get out of the system port range.

However, 8683 is not an officially assigned user port for IIOP 
(there is no such a thing), but simply an unassigned port that 
we should not be using. The officially assigned ports are in

  http://www.iana.org/assignments/port-numbers

So I have requested IANA a user port assignment for JBoss/IIOP. 
We got the following ports:

  jboss-iiop  3528/tcp   JBoss IIOP
  jboss-iiop  3528/udp   JBoss IIOP
  jboss-iiop-ssl  3529/tcp   JBoss IIOP/SSL
  jboss-iiop-ssl  3529/udp   JBoss IIOP/SSL

I will change jacorb.properties in 3.0 and HEAD to switch from
8683 to 3528. As a consequence, there will be a change in the 
naming service IOR used in the testsuite (which is equivalent 
to corbaloc://1.2@localhost:8683/JBoss/Naming/root) and in
all JBoss-generated IORs. (If you have an app that stores IORs 
of EJBHomes or EJBObjects, beware! You might want to edit
jacorb.properties to retain the old port and avoid regenerating
your IORs.)

Cheers,

Francisco



---
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] HEAD broken?

2002-08-01 Thread Francisco Reverbel

Did a fresh checkout, but the server refuses to run. A stack trace 
is included below. Switching JDK does not make a difference: tried
Sun 1.3.1_03, Sun 1.4.0, and IBM 1.3.1 (all on Linux).

Is anybody else seeing this?

Cheers,

Francisco

--

10:11:23,448 ERROR [MainDeployer] could not create
deployment: 
file:/home/reverbel/co/jboss-all/build/output/jboss-3.1.0alpha/server/default/conf/jboss-service.xml
java.lang.NoSuchFieldError: problem
at
org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:190)
at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:131)
at
org.jboss.system.ServiceController.install(ServiceController.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy5.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:227)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:758)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:623)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:572)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy6.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:232)
at org.jboss.Main.boot(Main.java:146)
at org.jboss.Main$1.run(Main.java:379)
at java.lang.Thread.run(Thread.java:479)
10:11:23,487 ERROR [Server] Failed to start




---
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] Shouldn't the ejb invoker binding be in thecontainer-configuration section

2002-07-14 Thread Francisco Reverbel

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 M Stark wrote:

 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
 client-configuration-nameStateless
 Session/JRMP/client-configuration-name
 client-configuration-nameStateless
 Session/IIOP/client-configuration-name
 /client-configuration-names
 /session
 /enterprise-beans
 
 client-container-configurations
 client-container-configuration
 container-nameStateless Session/JRMP/container-name
 invoker-namejboss:service=invoker,type=jrmp/invoker-name
 client-interceptors
 home
 
 interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor
 
 interceptororg.jboss.proxy.SecurityInterceptor/interceptor
 
 interceptororg.jboss.proxy.TransactionInterceptor/interceptor
 
 interceptororg.jboss.invocation.InvokerInterceptor/interceptor
 /home
 bean
 
 interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor
 
 interceptororg.jboss.proxy.SecurityInterceptor/interceptor
 
 interceptororg.jboss.proxy.TransactionInterceptor/interceptor
 
 interceptororg.jboss.invocation.InvokerInterceptor/interceptor
 /bean
 /client-interceptors
 ...
 /client-container-configuration
 /client-container-configurations
 /jboss
 
 I have only glaced out the 3.1 parsing so maybe this is what we are doing
 there,
 but it certainly is not how 3.0 is handling invokers.
 
 
 Scott Stark
 Chief Technology Officer
 JBoss Group, LLC
 
 
 
 
 
 ---
 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



Re: [JBoss-dev] Testsuite problems -- no all conf.

2002-06-10 Thread Francisco Reverbel

Great, we're back in business.  The testsuite runs again. Thanks,

Francisco

On Sun, 9 Jun 2002, Scott M Stark wrote:

 I updated the build file with some changes that were missing for the
 multi-config
 build output. The all config is now populated correctly.
 
 - Original Message -
 From: David Jencks [EMAIL PROTECTED]
 To: jboss-dev [EMAIL PROTECTED]
 Sent: Sunday, June 09, 2002 4:43 PM
 Subject: [JBoss-dev] Testsuite problems -- no all conf.
 
 
  I think the reason the automatic testsuite is failing is that there is no
  configuration for the all setup, just a lib directory.
 
  Also I think it might possibly make more sense to copy each jar to its
  (minimal) final location, then copy all of minimal/[lib deploy] to
 default,
  and all of default to all.
 
  Perhaps someone who has worked on this previously could take another look.
 
  thanks
  david jencks
 
 
 
 ___
 
 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 


___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Build not working on Linux?

2002-05-26 Thread Francisco Reverbel

Thanks for your reply, Jason.

 Eventually we will have everything listed... in fact we have a similar include 
 for the javac task, so perhaps XDoclet needs to be fixed to not cache so much 
 data at one (or whatever).

Yes.

 Have you tried increasing the heap for the vm used to build?  I would prefer 
 that local fix to this global one.
 
 JAVA_OPTS=-X128m build/build.sh

I have, but still got OutOfMemoryError. (Had to say -Xms128m -Xmx128m,
though. The 1.3 VM doesn't recognize -X128m as an option. And with just 
-Xms128m it complains about incompatible initial and max heap sizes.)

Best,

Francisco



___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Build not working on Linux?

2002-05-26 Thread Francisco Reverbel

On Sun, 26 May 2002, Matthew Tippett wrote:

 Technically speaking the docset is not 'too big', it is simply causes 
 too many native threads to be created for most 'default' Linux 
 distributions.
 
 Run the sample program and you should with a Linux 2.4 system get around
 220ish threads.  The options without the change are as follows.
 
   o Use build.compiler=classic (which kicks the JVM into green
   threads which doesn't have a 'real' thread limit.

Not a real option, as some VMs (the newer ones) don't support green
threads.

   o Set ulimit -u to greater around 1024

Yes, this worked fine for me. Thanks!

   o Modify /etc/security/limits.conf and nprocs to something
   around 1024

In my system (Debian Woody) /etc/security/limits.conf is essentially 
empty (only has commented out example entries), so I guess this is
the reason `ulimit -u 1024' worked for me without any change to
limits.conf.

 So the 'fix' is a workaround.  (Probably is the best solution for the 
 moment, but it isn't a bug in the code, more so a configuration problem 
 in the standard configuration of Linux distributions.
 
 Just thought people might be interested (I spent about 2 hours 
 attempting to get my first CVS build running when I came across this 
 problem :).

This sounds like an argument for the fix/workaround/whatever. 
It shouldn't be this hard to build and run the CVS code!
(Yesterday I had just a couple of hours for some JBoss hacking
and also spent them on the xdoclet error...)

Cheers,

Francisco


___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Build not working on Linux?

2002-05-25 Thread Francisco Reverbel

Help!

I am running build/build.sh on HEAD and Branch_3_0 trees just 
checked out from CVS. On both trees build fails within xdoclet:

  java.lang.OutOfMemoryError: unable to create new native thread

(Branch 3.0 error included below.)

Both Sun and IBM JDKs are giving me the same error. My config is:

  Linux pong 2.4.10 #1 Sun Oct 14 23:31:01 BRST 2001 i686 unknown

  Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
  Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode)

  Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
  Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT
  enabled: jitc)) 

Is anybody else seeing this?

Thanks,

Francisco



   ==
==  Executing 'most' in module 'server'...
==

_buildmagic:init:

configure:

init:

generate-parsers:
Target is already built - skipping
(/home/reverbel/Branch_3_0/jboss-all/server/\
src/main/org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt)
Target is already built - skipping
(/home/reverbel/Branch_3_0/jboss-all/server/\
src/main/org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt)

compile-bean-sources:
sourcepath is deprecated. the preferred way to design sources is via nested
fi\
leset
Running xdoclet.XDocletMain loaded by
sun.misc.Launcher$AppClassLoader. Forked:\
true
  [xdoclet] Running homeInterface/
  [xdoclet] Running remoteInterface/
  [xdoclet] Running session/
  [xdoclet] Running deploymentDescriptor/
  [xdoclet] Running jboss/

compile-mbean-sources:
sourcepath is deprecated. the preferred way to design sources is via nested
fi\
leset
Running xdoclet.XDocletMain loaded by
sun.misc.Launcher$AppClassLoader. Forked:\
true
  [xdoclet] Running mbeanInterface/
  [xdoclet] java.lang.OutOfMemoryError: unable to create new native thread
  [xdoclet] at java.lang.Thread.start(Native Method)
  [xdoclet] at xjavadoc.XJavaDoc.scanAndPut(XJavaDoc.java:562)
  [xdoclet] at xjavadoc.XJavaDoc.getXClass(XJavaDoc.java:393)
  [xdoclet] at xjavadoc.ProxyClass.resolve(ProxyClass.java:584)
  [xdoclet] at xjavadoc.ProxyClass.doc(ProxyClass.java:483)
  [xdoclet] at
xdoclet.DocletSupport.isDocletGenerated(DocletSupport.java:2\
69)
  [xdoclet] at
xdoclet.TemplateSubTask.matchesGenerationRules(TemplateSubTa\
sk.java:633)
  [xdoclet] at
xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:57\
6)
  [xdoclet] at xdoclet.TemplateSubTask.execute(TemplateSubTask.java:488)
  [xdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:54)
  [xdoclet] at xjavadoc.ant.XJavaDocMain.main(XJavaDocMain.java:94)

Is anybody else seeing this? I am on Linux 




___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Build not working on Linux?

2002-05-25 Thread Francisco Reverbel

Found the cause: a recent change on server/build.xml made xdoclet 
to be called on a fileset too big (name=**/*.java). 

I will revert the change. But it is strange that nobody else saw 
this... I have tried two Linux machines (a laptop with 128M and a 
box with 384M) with the same result: xdoclet barfed on the big 
fileset. Maybe there is something in my Linux environment that made
me run out of memory before anybody else.

Cheers,

Francisco

On Sat, 25 May 2002, Francisco Reverbel wrote:

 Help!
 
 I am running build/build.sh on HEAD and Branch_3_0 trees just 
 checked out from CVS. On both trees build fails within xdoclet:
 
   java.lang.OutOfMemoryError: unable to create new native thread
 
 (Branch 3.0 error included below.)
 
 Both Sun and IBM JDKs are giving me the same error. My config is:
 
   Linux pong 2.4.10 #1 Sun Oct 14 23:31:01 BRST 2001 i686 unknown
 
   Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
   Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode)
 
   Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
   Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT
   enabled: jitc)) 
 
 Is anybody else seeing this?
 
 Thanks,
 
 Francisco
 
 
 
==
 ==  Executing 'most' in module 'server'...
 ==
 
 _buildmagic:init:
 
 configure:
 
 init:
 
 generate-parsers:
 Target is already built - skipping
 (/home/reverbel/Branch_3_0/jboss-all/server/\
 src/main/org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt)
 Target is already built - skipping
 (/home/reverbel/Branch_3_0/jboss-all/server/\
 src/main/org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt)
 
 compile-bean-sources:
 sourcepath is deprecated. the preferred way to design sources is via nested
 fi\
 leset
 Running xdoclet.XDocletMain loaded by
 sun.misc.Launcher$AppClassLoader. Forked:\
 true
   [xdoclet] Running homeInterface/
   [xdoclet] Running remoteInterface/
   [xdoclet] Running session/
   [xdoclet] Running deploymentDescriptor/
   [xdoclet] Running jboss/
 
 compile-mbean-sources:
 sourcepath is deprecated. the preferred way to design sources is via nested
 fi\
 leset
 Running xdoclet.XDocletMain loaded by
 sun.misc.Launcher$AppClassLoader. Forked:\
 true
   [xdoclet] Running mbeanInterface/
   [xdoclet] java.lang.OutOfMemoryError: unable to create new native thread
   [xdoclet] at java.lang.Thread.start(Native Method)
   [xdoclet] at xjavadoc.XJavaDoc.scanAndPut(XJavaDoc.java:562)
   [xdoclet] at xjavadoc.XJavaDoc.getXClass(XJavaDoc.java:393)
   [xdoclet] at xjavadoc.ProxyClass.resolve(ProxyClass.java:584)
   [xdoclet] at xjavadoc.ProxyClass.doc(ProxyClass.java:483)
   [xdoclet] at
 xdoclet.DocletSupport.isDocletGenerated(DocletSupport.java:2\
 69)
   [xdoclet] at
 xdoclet.TemplateSubTask.matchesGenerationRules(TemplateSubTa\
 sk.java:633)
   [xdoclet] at
 xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:57\
 6)
   [xdoclet] at xdoclet.TemplateSubTask.execute(TemplateSubTask.java:488)
   [xdoclet] at xdoclet.XDocletMain.start(XDocletMain.java:54)
   [xdoclet] at xjavadoc.ant.XJavaDocMain.main(XJavaDocMain.java:94)
 
 Is anybody else seeing this? I am on Linux 
 
 
 
 
 ___
 
 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 


___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] NoSuchMethodError in MainDeployer

2002-05-21 Thread Francisco Reverbel

Did you buid JBoss with JDK 1.4 and attempted to start the server with 
IBM's 1.3 or 1.3.1 VM for Linux, by any chance? I had trouble in this
case.

It appears that a 1.4-generated server barfs with IBM's 1.3.x VMs for 
Linux. Do not ask me why...  ;-(

Best,

Francisco

On Tue, 21 May 2002, Dain Sundstrom wrote:

 I can't seem to get the server to start anymore.  I did a fresh checkout 
 and rebuild.  When I start the server I get the following exception:
 
 13:50:58,280 ERROR [Server] start failed
 org.jboss.deployment.DeploymentException: Could not create deployment: 
 file:/hom
 e/dain/work/jboss/jboss-head/build/output/jboss-3.1.0alpha/server/default/conf/j
 boss-service.xml; - nested throwable: (java.lang.NoSuchMethodError)
  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:698)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:522)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:489)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:472)
  at java.lang.reflect.Method.invoke(Native Method)
  at 
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
 nDispatcher.java:284)
  at 
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:318)
  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
  at org.jboss.Main.boot(Main.java:148)
  at org.jboss.Main$1.run(Main.java:381)
  at java.lang.Thread.run(Thread.java:484)
 java.lang.NoSuchMethodError
  at 
 org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL.getLast
 Modified(URLDeploymentScanner.java:304)
  at 
 org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL.deploye
 d(URLDeploymentScanner.java:274)
  at 
 org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
 tScanner.java:375)
  at 
 org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDe
 ploymentScanner.java:555)
  at 
 org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
 canner.java:434)
  at 
 org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
 bstractDeploymentScanner.java:237)
  at 
 org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
 98)
  at java.lang.reflect.Method.invoke(Native Method)
  at 
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
 nDispatcher.java:284)
  at 
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at 
 org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
 ler.java:867)
  at $Proxy0.start(Unknown Source)
  at 
 org.jboss.system.ServiceController.start(ServiceController.java:339)
  at java.lang.reflect.Method.invoke(Native Method)
  at 
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
 nDispatcher.java:284)
  at 
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
  at $Proxy3.start(Unknown Source)
  at org.jboss.deployment.SARDeployer.start(SARDeployer.java:341)
  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:686)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:522)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:489)
  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:472)
  at java.lang.reflect.Method.invoke(Native Method)
  at 
 org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
 nDispatcher.java:284)
  at 
 org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
  at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:318)
  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
  at org.jboss.Main.boot(Main.java:148)
  at org.jboss.Main$1.run(Main.java:381)
  at java.lang.Thread.run(Thread.java:484)
 
 -dain
 
 
 ___
 
 Don't miss the 2002 Sprint PCS Application Developer's Conference
 August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/jboss-development
 


___

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] JRMP and IIOP invocations to the same container...

2002-05-19 Thread Francisco Reverbel

are now working in 3.1 (CVS HEAD). Marc: your vision is real!!! Even 
concurrent JRMP and IIOP invocations appear to be working fine. I have
committed yet another version of the hello test (hellojrmpiiop) to 
demonstrate this. 

Here is a summary of the recent changes on the IIOP stuff in 3.1:

- The EJB-specific IIOPContainerInvoker is gone. Its functionality
  is now split between a generic IIOPInvoker MBean and an EJB-specific
  IORFactory, which is the IIOP version of a ProxyFactory.

- These two guys interact in the following way: the IORFactory registers
  CORBA servants with the IIOPInvoker, which returns to the IORFactory
  reference factories the IORFactory uses to create CORBA references.
  Two new interfaces are involved: ServantRegistry and ReferenceFactory,
  both implemented by objects provided/returned by the IIOPInvoker.

- An IORFactory is associated to a given container. It creates two CORBA 
  servants: an EjbHomeCorbaServant and an EjbObjectCorbaServant. Both are 
  thin wrappers that forward invocations to the container, through the 
  JBoss MBean server.

- Other CORBA reference factories (which don't need to be EJB-specific)
  may also use the IIOPInvoker. As an example, the in-VM CORBA naming
  service in 3.1 has been modified to register its servants with the
  IIOPInvoker. A next step would be an IIOP Java proxy factory that talks 
  to the IIOPinvoker. (Any volunteers?...)

- The CORBA naming service has been taken off the CORBA ORB service and
  is now a separate MBean.

- IIOP-specific container configurations are gone. Now you just
  specify the iiop invoker-proxy-binding.

- The proxy-factory-config of an IORFactory takes the following
  sub-elements (see iiop proxy binding in standardjboss.xml):

- web-class-loader: Moved from the container configuration.
  Must contain org.jboss.iiop.WebCL.

- poa: May be shared (a single POA shared among all servants
 bound to a ServantRegistry) or per-servant (a separate
 POA is created for each servant bound to a ServantRegistry).
 The default value in the iiop
 invoker-proxy-binding in standardjboss.xml is per-servant.

- register-ejbs-in-jnp-context: If true, EJBHome IORs are registered
 with the JBoss JNP naming service in addition to being 
 registered with the CORBA naming service. If false EJBHome
 IORs are registered only with the CORBA naming service.
 The default value in the iiop invoker-proxy-binding in 
 standardjboss.xml is true.

- jnp-context: Only meaningful it the previous element is true.
 Specifies the JNP naming context EJBHome IORs will be bound to.
 If absent, EJB IORs will be bount to the root JNP naming
 context. The default value in the iiop invoker-proxy-binding 
 in standardjboss.xml is iiop.

To clarify the last two config elements: in the hellojrmpiiop test,
the JRMP reference to the EJBHome is bound to helloworld/Hello in the 
JNP naming service. The EJBHome IOR is bound to helloworld/Hello in the
CORBA naming service and to iiop/helloworld/Hello in the JNP naming
service (because register-ejbs-in-jnp-context is true and jnp-context
is iiop).

Let me know what you think of this arrangement. Suggestions/ideas are very 
welcome. And please let me know of any problems.

This stuff is built upon Bill's great work on multiple invokers. It is 
also a consequence of very enlightening discussions with Marc and Bill.
Thanks, guys!

Best,

Francisco


___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] Talk on IIOP support in JBoss

2002-05-19 Thread Francisco Reverbel

For those in South America this coming week: on May 23 (4:30PM) I will
be an invited speaker at the Objetos 6006 conference, in Sao Paulo, 
Brazil. This event is jointly organized by three Sao Paulo user groups 
-- the OO/UML user group, the Java user group, and the CORBA user group. 

More info (in Portuguese):

   http://www.objetos6006.com.br/palestras.htm

The conference schedule is in 

   http://www.objetos6006.com.br/palestras.htm

Cheers,

Francisco


___
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] JMX RMI Adapter JNDI binding

2002-05-13 Thread Francisco Reverbel

On Sun, 12 May 2002, Jason Dillon wrote:

 Currently we are binding to jmx:hostname:rmi which is fine when you are
 working with the localhost, but will start to cause problems once used in a
 multi-host environment.

...

 So for a client on a remote host to correctly make use of the deployer.sh or any
 other simialr tool using the jmx adapter it will have to have knowledge of the
 servers local hostname (as returned by
 java.net.InetAddress.getLocalHost().getHostName()) and specify that value for
 --server, then specify -Djava.naming.provider.url=jnp://www.mydomain.com.

This may also be an issue if you have a client running in the 
same host as the server, but on a VM from other vendor. 

When I run java.net.InetAddress.getLocalHost().getHostName() on a 
Sun VM, I get something like myhost.mydomain.com. When I do the 
same thing on an IBM VM for Linux, I get myhost.

This appears to be the reason the whole testsuite fails if I use a 
Sun VM for the server and an IBM VM for the testsuite clients (or 
vice-versa).

Regards,

Francisco




___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] JBoss built with JDK 1.4 doesn't run on IBM VMs?

2002-05-12 Thread Francisco Reverbel

Hello,

I am running Debian Linux 3.0, kernel 2.4.10. 

Built JBoss 3.1 (CVS HEAD) with Sun JDK 1.4. The server barfs with IBM 
VMs 1.3 and 1.3.1. A stack trace is included below. The same 1.4-built
server runs fine with Sun VMs 1.3.1_02, 1.3.1_03, and 1.4. 

Rebuilt the server from scratch, now with Sun JDK 1.3.1_03. The 1.3-built
server runs fine on Sun and on IBM VMs. 

Does anybody else see this?

Cheers,

Francisco

-- stack trace -
2002-05-11 22:02:43,286 INFO
[org.jboss.deployment.scanner.URLDeploymentScanner] Starting
2002-05-11 22:02:43,300 ERROR [org.jboss.deployment.MainDeployer] could not
start
deployment: 
file:/home/reverbel/jboss-all/build/output/jboss-3.1.0alpha/server/default/conf/jboss-service.xml
java.lang.AbstractMethodError: 
org/jboss/deployment/scanner/AbstractDeploymentScanner.scan
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:237)
at
org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:198)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:867)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:339)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:342)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:692)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:527)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:490)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:472)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:318)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:498)
2002-05-11 22:02:43,329 ERROR [org.jboss.deployment.MainDeployer] Couldn't
deploy URL
file:/home/reverbel/jboss-all/build/output/jboss-3.1.0alpha/server/default/conf/jboss-service.xml



___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] testsuite in HEAD does not build

2002-05-06 Thread Francisco Reverbel

Hi,

The error I got was caused by what seemed to be a typo in 
testsuite/build.xml. With this typo the testsuite build was 
failing on both jdk1.3 and jdk1.4. After I've fixed it, I
still got a compilation error on jdk1.4 (at a later point), 
but build succeeded on jdk1.3. I was in a hurry, so didn´t 
look into the compilation problem and went on to run the 
tests I have managed to build with jdk1.3...

I guess you didn't get the same error I got because you 
updated your tree after I commited my fix. 

Thanks for fixing the compilation problem with jdk1.4!

Francisco

On Sun, 5 May 2002, danch wrote:

 Didn't get that error there, but I did get an compile problem in the 
 newbank stuff related to the fact that 1.4 defines a throwable 'cause' 
 property in Exception and newbank has an exception class with an 
 Exception cause properly. I've fixed that and will check in as soon as I 
 confirm that it will compile under 1.3 (i don't see why it wouldn't, but...)
 
 I did just do a clean checkout because the 'most' target would build for 
 me and I felt like it was Just Time to Do That. maybe you have an old 
 xdoclet or an version mismatch between ant and xdoclet?
 
 -danch
 
 Francisco Reverbel wrote:
  Is anybody else getting this? I am using jdk1.4 on linux.
  
  Francisco
  
  -
...
[xdoclet] Running deploymentDescriptor/
[xdoclet] Running jboss/
  [execmodules] Running xdoclet.XDocletMain loaded by
  sun.misc.Launcher$AppClassLoader. Forked:true
[xdoclet] Exception in thread
  main java.lang.NoClassDefFoundError: xdoclet/XDocletMain
  [execmodules] /home/reverbel/jboss-all/testsuite/build.xml:599: Java
  returned: 1[execmodules]at
  org.apache.tools.ant.taskdefs.Java.execute(Java.java:90)
  [execmodules]   at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:175)
  [execmodules]   at xdoclet.DocletTask.execute(DocletTask.java:298)
  [execmodules]   at
  org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:104)
  [execmodules]   at org.apache.tools.ant.Task.perform(Task.java:217)
 
 
 


___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] testsuite in HEAD does not build

2002-05-04 Thread Francisco Reverbel

Is anybody else getting this? I am using jdk1.4 on linux.

Francisco

-
  ...
  [xdoclet] Running deploymentDescriptor/
  [xdoclet] Running jboss/
[execmodules] Running xdoclet.XDocletMain loaded by
sun.misc.Launcher$AppClassLoader. Forked:true
  [xdoclet] Exception in thread
main java.lang.NoClassDefFoundError: xdoclet/XDocletMain
[execmodules] /home/reverbel/jboss-all/testsuite/build.xml:599: Java
returned: 1[execmodules]at
org.apache.tools.ant.taskdefs.Java.execute(Java.java:90)
[execmodules]   at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:175)
[execmodules]   at xdoclet.DocletTask.execute(DocletTask.java:298)
[execmodules]   at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:104)
[execmodules]   at org.apache.tools.ant.Task.perform(Task.java:217)
[execmodules]   at org.apache.tools.ant.Target.execute(Target.java:164)
[execmodules]   at org.apache.tools.ant.Target.performTasks(Target.java:182)
[execmodules]   at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[execmodules]   at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261)
[execmodules]   at
org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:269)
[execmodules]   at
org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:184)
[execmodules]   at org.apache.tools.ant.Task.perform(Task.java:217)
[execmodules]   at org.apache.tools.ant.Target.execute(Target.java:164)
[execmodules]   at org.apache.tools.ant.Target.performTasks(Target.java:182)
[execmodules]   at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[execmodules]   at
org.apache.tools.ant.Project.executeTargets(Project.java:560)[execmodules]
at org.apache.tools.ant.Main.runBuild(Main.java:454)
[execmodules]   at org.apache.tools.ant.Main.start(Main.java:153)
[execmodules]   at org.apache.tools.ant.Main.main(Main.java:176)

BUILD FAILED

/home/reverbel/jboss-all/testsuite/build.xml:599: Java returned: 1

Total time: 34 seconds



___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Clustering Hanging and JVM Bind

2002-05-03 Thread Francisco Reverbel

On Wed, 1 May 2002, Theo Harper wrote:

 Thanks for the help regarding the IIOP hang, after changing the port to 8683
 JBoss starts up okay.  Will Branch_3_0_0 be updated with this fix?

The default IIOP port is already 8683 in HEAD, Branch_3_0_0, and 3.0.0RC2.

Francisco


___

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] IIOP port conflict on Windows XP

2002-04-30 Thread Francisco Reverbel

As Adrian pointed out some time ago, the IIOP port in the
default config in HEAD and branch 3.0 (port 5000) conflicts
with a Windows XP service (SSDP Discovery Service, used for
Universal Plug and Play).

I considered changing the default config and moving IIOP to the 
port officially reserved for IIOP. but this is not a good option.
The official IIOP port (683) is in the well-known port range
(0--1023), normally unavailable to processes with no special 
privileges. So I requested IANA a port assignment (in the
registered port range, which is from 1024 to 49151) for JBoss.

In a couple of weekes we should have our own registered port for 
JBoss/IIOP. Meanwhile, I do not know what to do with the IIOP port.
The current value is causing problems for Windows XP users. 
Changing it to another stolen value is also likely to cause 
problems...

Francisco





Re: [JBoss-dev] IIOP port conflict on Windows XP

2002-04-30 Thread Francisco Reverbel

Will do it. Just checked at www.iana.org and 8683 is unassigned,
so it should be better than our current port. 

Thanks,

Francisco

On Tue, 30 Apr 2002, Jason Dillon wrote:

 Why not change it to 8683 by default then?
 
 --jason
 
 
 Francisco Reverbel wrote:
 
 As Adrian pointed out some time ago, the IIOP port in the
 default config in HEAD and branch 3.0 (port 5000) conflicts
 with a Windows XP service (SSDP Discovery Service, used for
 Universal Plug and Play).
 
 I considered changing the default config and moving IIOP to the 
 port officially reserved for IIOP. but this is not a good option.
 The official IIOP port (683) is in the well-known port range
 (0--1023), normally unavailable to processes with no special 
 privileges. So I requested IANA a port assignment (in the
 registered port range, which is from 1024 to 49151) for JBoss.
 
 In a couple of weekes we should have our own registered port for 
 JBoss/IIOP. Meanwhile, I do not know what to do with the IIOP port.
 The current value is causing problems for Windows XP users. 
 Changing it to another stolen value is also likely to cause 
 problems...
 
 Francisco
 
 
 
 
 





  1   2   3   4   >