[JBoss-dev] ejb3-4.0-testsuite Build Timed Out

2006-02-03 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.0-testsuite?log=log20060203031650
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:02/03/2006 03:16:50Time to build:Last changed:12/31/2005 16:46:08Last log entry:call isOpen() when obtaining session so that HEM registers with EM with TXset cglib_use_reflection flag to false




   Unit Tests: (0)   Total Errors and Failures: (0)
Modifications since last build:(first 50 of 3658)1.3modifiedbillsrc/test/org/jboss/ejb3/test/tableperinheritance/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.7modifiedbillsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.6modifiedbillsrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaEJBs and Persistence can now be within a .jar file1.3modifiedbillsrc/test/org/jboss/ejb3/test/xmlcfg/unit/EntityUnitTestCase.javaEJBs and Persistence can now be within a .jar file1.4modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaapplication-exception support1.7modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaapplication-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorAppException.javabranches:  1.1.2;application-exception support1.1addedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/DeploymentDescriptorCheckedRollbackException.javabranches:  1.1.2;application-exception support1.5modifiedbdecostesrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaapplication-exception support1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javabranches:  1.2.2;activateConfig to activationConfig1.2modifiedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javabranches:  1.2.2;activateConfig to activationConfig1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/unit/EmbeddedEjb3TestCase.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/Customer.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOBean.javabranches:  1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAOLocal.javabranches:  1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/CustomerDAORemote.javabranches:  1.1.2;test for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/EmbeddedEJB3.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/JndiTest.jsptest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/QueueTestMDB.javatest for embedded EJB3 in WLS1.1addedbdecostesrc/test/org/jboss/ejb3/test/wls/embeddedwar/TopicTestMDB.javatest for embedded EJB3 in WLS1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/Customer.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTest.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/xmlcfg/EntityTestBean.javaUpdate the jboss LGPL headers1.4modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTester.javaUpdate the jboss LGPL headers1.9modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/TimerTesterBean21.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/timer/unit/RemoteUnitTestCase.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AnnotatedAppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/AppException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/CheckedRollbackException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/Dao.javaUpdate the jboss LGPL headers1.6modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/DaoBean.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/NoRollbackRuntimeException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRemoteException.javaUpdate the jboss LGPL headers1.2modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/RollbackRuntimeException.javaUpdate the jboss LGPL headers1.3modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/SimpleEntity.javaUpdate the jboss LGPL headers1.4modifiedstarksmsrc/test/org/jboss/ejb3/test/txexceptions/unit/TxExceptionsTestCase.javaUpdate the jboss LGPL 

[JBoss-dev] WebService tests timeout

2006-02-03 Thread Dimitris Andreadis



I've noticed2 webservices tests that timeout (and 
fail) occasionally at 60 secondswhen contactingexternal 
webservices:

org.jboss.test.jbossnet.external.ExternalUnitTestCase
org.jboss.test.jbossnet.external.RedeployExternalUnitTestCase

Is this timeout configurable? I seem to be getting a 
response in just about one minute. Is this "normal" for WS 
:)

Thanks

service name="BabelFishService"documentationTranslates 
text of up to 5k in length, between a variety of 
languages./documentationport name="BabelFishPort" 
binding="tns:BabelFishBinding"soap:address 
location="http://services.xmethods.net:80/perl/soaplite.cgi"//port/service
service name="GoogleSearchService"port 
name="GoogleSearchPort" 
binding="typens:GoogleSearchBinding"soap:address 
location="http://api.google.com/search/beta2"//port/service

  
  
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
  Sent: 03 February, 2006 01:45To: Adrian Brock; Clebert 
  Suconic; Dimitris Andreadis; jboss-development@lists.sourceforge.net; QA; Ryan 
  CampbellSubject: jboss-3.2-testsuite Build Completed With Testsuite 
  ErrorsImportance: High
  View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060202175301
  
  


  TESTS FAILED

  Ant Error 
Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235: 
The following error occurred while executing this line: 
/services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build 
Successful - Tests completed with errors or failures.

  Date of 
build:02/02/2006 17:53:01

  Time to 
build:50 minutes 27 seconds

  Last 
changed:02/02/2006 14:17:10

  Last log 
entry:JBAS-2768, change tests that produce varying resutls 
based on jdk/os platform to logging warning messages rather than code 
assertions
  
  





  


  Unit Tests: (1847) 
Total Errors and Failures: (2) 

  

  
  
testFederated
org.jboss.test.jbossnet.external.ExternalUnitTestCase
  
testFederated
org.jboss.test.jbossnet.external.RedeployExternalUnitTestCase


  
  
  


  Modifications 
since last build: (first 50 of 14) 

  1.2.2.20
  modified
  dimitris
  testsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.java
  JBAS-2768, change tests that produce 
varying resutls based on jdk/os platform to logging warning messages 
rather than code assertions

  1.1.2.1
  modified
  csuconic
  testsuite/src/main/org/jboss/test/guid/GUIDTestCase.java
  Renaming GUIDTest to the correct name, so 
it can be part of the testsuite

  1.11.2.10
  modified
  dimitris
  server/src/main/org/jboss/invocation/MarshalledInvocation.java
  JBAS-2767, Conditionally set 
useFullHashMode to true, when SerialVersion.version == 
SerialVersion.JBOSS_402

  1.165.2.198
  modified
  rcampbell
  testsuite/build.xml
  added 4.0.3SP1 to compat matrix

  1.1.2.16
  modified
  rcampbell
  testsuite/imports/server-config.xml
  JBAS-2758: pass serialization flag to jboss 
startup *and* shutdown

  1.165.2.197
  modified
  rcampbell
  testsuite/build.xml
  JBAS-2758: pass serialization flag to jboss 
startup *and* shutdown

  1.2.2.22
  modified
  adrian
  messaging/src/main/org/jboss/mq/server/JMSDestinationManager.java
  [JBAS-2762] - Avoid infinite loop when 
there is no state manager.

  1.4.2.3
  modified
  dimitris
  jmx/src/main/javax/management/MBeanServerConnection.java
  synch with 4.x

  1.165.2.196
  modified
  rcampbell
  testsuite/build.xml
  JBAS-2758: add usage of 
org.jboss.j2ee.Serialization flag to compatibility matrix

  1.1.4.3
  modified
  dimitris
  testsuite/src/main/org/jboss/test/jbossmx/performance/TestCase.java
  fix compatibility test failures

  1.1.4.3
  modified
  dimitris
  testsuite/src/main/org/jboss/test/jbossmx/implementation/TestCase.java
  fix compatibility test failures

  1.2.4.4
  modified
  dimitris
  testsuite/src/main/org/jboss/test/jbossmx/compliance/TestCase.java
  fix compatibility test failures

  1.1.4.2
  modified
  dimitris
  common/src/main/org/jboss/util/id/GUID.java
  JBAS-2718, define a serialVersionUID for 
GUID and introduce SerialVersion. The default for 3.2..x will be legacy 
compatibility (3.2.x and maybe 4.0.0/4.0.1) which can be overriden by 
defining org.jboss.j2ee.Serialization for 4.0.2+ compatibility (the 
opposite of the 4.0.x branch)

  1.2.4.2

RE: [JBoss-dev] Generic Embedded/Bootstrap was RE: [JBoss-dev] EJB3StandaloneBootstrap implementation

2006-02-03 Thread Adrian Brock
On Thu, 2006-02-02 at 13:43, Scott M Stark wrote:
 This will help get us finalized on a mc and start thinking about the
 proper abstractions to use it so I'm all for it.
 
 1) Some have been inquiring about whether spring integration setups can
 also be used. Possibly we could have a spring alias mapping that binds
 to our integration implementation. Possibly we could even use existing
 spring integration objects for standard apis like JTA so we don't have
 to write it for envs we don't readily have for testing.
 

http://jira.jboss.com/jira/browse/JBMICROCONT-26

 2) So you are talking about abstractions on top of JTA or on the JTA
 provider service for interaction outside of JTA?
 

Both. 

e.g. Integrating TransactionProgationContext from the invokers/remoting
to JTS/JTA implementation is JBoss specific.

TransactionLocal/Demarcation abstractions should work with any JTA.

 3) Good. As a part-time dev on the kernel its hard for me to pull all of
 the pieces together with respect to a usable mc setup so I think a
 concrete collection of components in an embedded type of profile will
 help finalize the design.

Coming soon... :-)

 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
 Adrian Brock
 Sent: Wednesday, February 01, 2006 4:57 AM
 To: jboss-development@lists.sourceforge.net
 Subject: [JBoss-dev] Generic Embedded/Bootstrap was RE: [JBoss-dev]
 EJB3StandaloneBootstrap implementation
 
 FYI
 
 I am starting work on a prototype of the following three
 new modules (I am not sure these are good names :-)
 
 1) Integration - Cross (other) container integration spi 
 like how do I bind to jndi?, give me the transaction synchronizer,
 etc.
 
 2) Services - abstraction of our common container spi, such that
 other projects can use these interfaces to talk to each other 
 rather than linking directly to implementation
 e.g. Who knows whether the user wants to use 
 JBossJTA or JBoss Transactions?
 
 3) Embedded - an extension to the kernel module that introduces aop,
 jmx, profile service and eventually aspectized deployments 
 (all optional)
 
 My plans for enhanced embedded bootstrap implementations are:
 * Explicit - tell me what you want to do
 - suitable for extension
 
 * Classpath - like current MC Standalone bootstrap 
 - suitable for main() usage
 
 * URLClassLoader - parse getURLs() and look for config relative 
 to this 
 - suitable for running inside an EJB container, servlet container, etc.
 
 * Test - shared base common config + test specific config
 - suitable for use in JUnit/TestNG
 
 I think this has some redundancy with the EJB3 bootstrap methods
 but it doesn't make sense to have this EJB3 specific.
 e.g. I want to 
 * bootstrap/configure some JBoss Service inside a
 servlet context of another JEE container
 * run tests against a service that requires other services
 * provide a real standalone distribution of JBoss Messaging
 * etc.
 
 My motivation for this prototype is not to get a product
 out of it yet. It is to flush out the integration details
 between the projects.
 
 In particular, AOP and MC. I started the new jca project for
 this purpose as well, but I haven't had any real feedback
 on this prototype from the AOP team.
 It also includes a simple AOP proxy replacement for org.jboss.proxy
 in the aspects module (again a prototype) and POJOs to allow
 aspects to be configured via DI in the MC.
 
 Bill did help me with some pointcut definition enhancements
 to implement MessageEndpoint properly.
 
 I'm hoping if I do this for something less esoteric than JCA
 then I will get some feedback ;-)
 
 On Tue, 2006-01-31 at 22:26, Scott M Stark wrote:
  How can the scanClasspath() step be optimized/skipped in say an
 embedded
  ejb3 project in jbosside where the data obtained during the scan was
  written out in an optimized metadata store as part of the project say?
  
  I don't really follow adding aspects like clustering to deployments
  based on the location in a filesystem, virtual or otherwise. Just
 seems
  like too much meaning being linked to the deployment url/location.
  
  I'm busy through tomorrow, but come thu I will just checkin the
 current
  vfs stuff I have had sitting in the workspace for months and see what
  start can be made on pushing this forward.
  
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
 Bill
  Burke
  Sent: Tuesday, January 31, 2006 9:28 AM
  To: jboss-development@lists.sourceforge.net
  Subject: Re: [JBoss-dev] EJB3StandaloneBootstrap implementation
  
  I think going the E-EJB3 route to start is a good idea as it will
 force 
  us to implement bare-bones implementations that do not have the idea
 of 
  a classloader or j2ee deployment schemes within them.  Once we have 
  e-ejb3 (really e-jboss) in place, it will force us to be careful about
 
  adding things like classloading and j2ee packaging as to not break or 
  bloat e-jboss.
  
  The way I envision it 

[JBoss-dev] jboss-3.2-compatibility-matrix Build Completed With Testsuite Errors

2006-02-03 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-compatibility-matrix?log=log20060203071959
TESTS FAILEDAnt Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build:02/03/2006 07:19:59Time to build:25 minutes 36 secondsLast changed:02/03/2006 06:52:26Last log entry:JBAS-2770, org.jboss.test.jbossmq.test.Jms11UnitTest excluded since we are running agains 3.2.6/3.2.7 too




   Unit Tests: (2366)   Total Errors and Failures: (74)

[JBoss-dev] jboss-3.2-compatibility-matrix build.1 Build Fixed

2006-02-03 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-compatibility-matrix?log=log20060203103401Lbuild.1
BUILD COMPLETE-build.1Date of build:02/03/2006 10:34:01Time to build:23 minutes 36 secondsLast changed:02/03/2006 09:44:06Last log entry:extend copyright to 2006, remove dimitris' duplicate entry




   Unit Tests: (1960)   Total Errors and Failures: (0)All Tests Passed
Modifications since last build:(first 50 of 36)1.1.4.1modifieddimitrisbuild/docs/copyright.txtextend copyright to 2006, remove dimitris' duplicate entry1.11.2.11modifieddimitrisserver/src/main/org/jboss/invocation/MarshalledInvocation.javaJBAS-2767, throw NestedRuntimeException instead so that the root exception is not eaten up1.165.2.201modifieddimitristestsuite/build.xmlno need to test jbossnet across versions, according to Thomas1.165.2.200modifieddimitristestsuite/build.xmlJBAS-2770, org.jboss.test.jbossmq.test.Jms11UnitTest excluded since we are running agains 3.2.6/3.2.7 too1.1.1.1.4.8modifieddimitristestsuite/src/main/org/jboss/test/jbossnet/security/SecurityUnitTestCase.javaJBAS-2772, dont' execute the test if the sources had been compiled using jdk1.3, meaningorg.jboss.net.axis.server.JBossAuthenticationHandlerorg.jboss.net.axis.server.JBossAuthorizationHandlerare not present1.165.2.199modifiedrcampbelltestsuite/build.xmlremove jbossmx, add jbossnet to compat matrix1.2.2.20modifieddimitristestsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.javaJBAS-2768, change tests that produce varying resutls based on jdk/os platform to logging warning messages rather than code assertions1.1.2.1modifiedcsuconictestsuite/src/main/org/jboss/test/guid/GUIDTestCase.javaRenaming GUIDTest to the correct name, so it can be part of the testsuite1.11.2.10modifieddimitrisserver/src/main/org/jboss/invocation/MarshalledInvocation.javaJBAS-2767, Conditionally set useFullHashMode to true, when SerialVersion.version == SerialVersion.JBOSS_4021.165.2.198modifiedrcampbelltestsuite/build.xmladded 4.0.3SP1 to compat matrix1.1.2.16modifiedrcampbelltestsuite/imports/server-config.xmlJBAS-2758: pass serialization flag to jboss startup *and* shutdown1.165.2.197modifiedrcampbelltestsuite/build.xmlJBAS-2758: pass serialization flag to jboss startup *and* shutdown1.2.2.22modifiedadrianmessaging/src/main/org/jboss/mq/server/JMSDestinationManager.java[JBAS-2762] - Avoid infinite loop when there is no state manager.1.4.2.3modifieddimitrisjmx/src/main/javax/management/MBeanServerConnection.javasynch with 4.x1.165.2.196modifiedrcampbelltestsuite/build.xmlJBAS-2758: add usage of org.jboss.j2ee.Serialization flag to compatibility matrix1.1.4.3modifieddimitristestsuite/src/main/org/jboss/test/jbossmx/performance/TestCase.javafix compatibility test failures1.1.4.3modifieddimitristestsuite/src/main/org/jboss/test/jbossmx/implementation/TestCase.javafix compatibility test failures1.2.4.4modifieddimitristestsuite/src/main/org/jboss/test/jbossmx/compliance/TestCase.javafix compatibility test failures1.1.4.2modifieddimitriscommon/src/main/org/jboss/util/id/GUID.javaJBAS-2718, define a serialVersionUID for GUID and introduce SerialVersion. The default for 3.2..x will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can be overriden by defining org.jboss.j2ee.Serialization for 4.0.2+ compatibility (the opposite of the 4.0.x branch)1.2.4.2modifieddimitriscommon/src/main/org/jboss/util/id/SerialVersion.javaJBAS-2718, define a serialVersionUID for GUID and introduce SerialVersion. The default for 3.2..x will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can be overriden by defining org.jboss.j2ee.Serialization for 4.0.2+ compatibility (the opposite of the 4.0.x branch)1.3.4.3modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/StatementAccess.java[JBAS-2741] - Backport from head1.1.2.6modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/WrappedCallableStatement.jpp[JBAS-2741] - Backport from head1.1.2.9modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/WrappedPreparedStatement.jpp[JBAS-2741] - Backport from head1.1.2.5modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/WrappedResultSet.jpp[JBAS-2741] - Backport from head1.2.2.13modifiedadrianconnector/src/main/org/jboss/resource/adapter/jdbc/WrappedStatement.jpp[JBAS-2741] - Backport from head1.1.2.3modifiedadrianserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/WrappedStatement.java[JBAS-2741] - Backport from head1.6.2.15modifiedadriantestsuite/.classpath[JBAS-2741] - Backport from head1.1.2.6modifiedadriantestsuite/src/main/org/jboss/test/jca/ejb/JDBCStatementTestsConnectionSessionBean.java[JBAS-2741] - Backport from head1.1.4.4modifiedadriantestsuite/src/main/org/jboss/test/jca/ejb/PreparedStatementBean.java[JBAS-2741] - Backport from 

[JBoss-dev] EJB RC5 PFD, HSQL and AUTO mode keys fail (ADRIAN DO NOT READ)

2006-02-03 Thread Andrew Oliver

This is JBAS 4.03SP1/last nights EJB3 and HSQL as distributed

If I do this:

@Id @GeneratedValue(strategy=GenerationType.SEQUENCE)
long id;

works with hypersonic

however

@Id @GeneratedValue(strategy=GenerationType.AUTO)
long id;

yields lovelies like this:

[org.hibernate.persister.entity.AbstractEntityPersister]  Identity 
insert: insert into Folder (name, parent_id, defaultInFolder_id, 
defaultOutFolder_id, TYPE, id) values (?, ?, ?, ?, 
'org.jboss.mail.mailbox.Mailbox', null)


And these of course fail with not null allowed (which is how the table 
was generated by hibernate) when they are executed


persistence.xml is:

persistence
  persistence-unit name=mail
  jta-data-sourcejava:/DefaultDS/jta-data-source
  properties
   property name=hibernate.dialect 
value=org.hibernate.dialect.HSQLDialect/

property name=hibernate.hbm2ddl.auto
  value=update/
property name=jboss.entity.manager.jndi.name
  value=java:/EntityManagers/mail/
property name=hibernate.show_sql
  value=true/
  /properties
  /persistence-unit
/persistence


So unless I goofed something up I don't think its the dialect.

Would post in the forum or log as bug but both appear to be inoperative 
at the moment.  Wanted someone to tell me why I'm wrong first.


-Andy



---
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] JMS problems on Branch_4_0

2006-02-03 Thread Bill Burke
My MDB tests seem to be hanging, Can't figure out why.  I do a thread 
dump and got the following...  Any clues?  Did somebody recently change 
JMS on Branch_4_0?


Thanks


RMI TCP Connection(2)-192.168.0.2 daemon prio=5 tid=0x27bbdcf0 
nid=0xc78 runnable [0x285fc000..0x285ffd68]

at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.RuntimeException.init(RuntimeException.java:43)
at 
java.lang.IllegalStateException.init(IllegalStateException.java:38)
at 
org.jboss.mq.server.JMSDestinationManager.getID(JMSDestinationManager.java:245)
at 
org.jboss.mq.server.JMSServerInterceptorSupport.getID(JMSServerInterceptorSupport.java:92)
at 
org.jboss.mq.server.TracingInterceptor.getID(TracingInterceptor.java:85)
at 
org.jboss.mq.server.JMSServerInvoker.getID(JMSServerInvoker.java:93)

at org.jboss.mq.il.jvm.JVMServerIL.getID(JVMServerIL.java:101)
at org.jboss.mq.Connection.askForAnID(Connection.java:1021)
at org.jboss.mq.Connection.checkClientID(Connection.java:998)
- locked 0x06c37de0 (a org.jboss.mq.SpyXAConnection)
at 
org.jboss.mq.SpyXAConnection.createXAQueueSession(SpyXAConnection.java:105)
at 
org.jboss.jms.asf.StdServerSessionPool.create(StdServerSessionPool.java:326)
at 
org.jboss.jms.asf.StdServerSessionPool.init(StdServerSessionPool.java:156)
at 
org.jboss.jms.asf.StdServerSessionPoolFactory.getServerSessionPool(StdServerSessionPoolFactory.java:91)

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:585)
at org.jboss.ejb3.mdb.MDB.createSessionPool(MDB.java:677)
at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:522)
--
Bill Burke
--
Bill Burke
Chief Architect
JBoss Inc.


---
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] cglib vs javassit for proxies

2006-02-03 Thread Scott M Stark








So I have to introduce a proxy for a javax.net.SSLServerSocket
which is an abstract class and so have to use cglib or javassist. I see some
proxy working in the head javassist, but this is not in the 4.0 branch version.
We also dont bundle javassist with 4.0 currently. I assume we would
rather have javassist be the only bytecode manipulation framework in jboss. Is
there a timeframe for completing the javassist proxy so we can think about
moving hibernate, webservices, cmp2.x, etc over to it?










[JBoss-dev] Re: JMS problems on Branch_4_0

2006-02-03 Thread Bill Burke
Yeah, something is up with Branch_4_0 with JMS.  Works find with 
4.0.3SP1 (same EJB3 code).


Bill Burke wrote:
My MDB tests seem to be hanging, Can't figure out why.  I do a thread 
dump and got the following...  Any clues?  Did somebody recently change 
JMS on Branch_4_0?


Thanks


RMI TCP Connection(2)-192.168.0.2 daemon prio=5 tid=0x27bbdcf0 
nid=0xc78 runnable [0x285fc000..0x285ffd68]

at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.RuntimeException.init(RuntimeException.java:43)
at 
java.lang.IllegalStateException.init(IllegalStateException.java:38)
at 
org.jboss.mq.server.JMSDestinationManager.getID(JMSDestinationManager.java:245) 

at 
org.jboss.mq.server.JMSServerInterceptorSupport.getID(JMSServerInterceptorSupport.java:92) 

at 
org.jboss.mq.server.TracingInterceptor.getID(TracingInterceptor.java:85)
at 
org.jboss.mq.server.JMSServerInvoker.getID(JMSServerInvoker.java:93)

at org.jboss.mq.il.jvm.JVMServerIL.getID(JVMServerIL.java:101)
at org.jboss.mq.Connection.askForAnID(Connection.java:1021)
at org.jboss.mq.Connection.checkClientID(Connection.java:998)
- locked 0x06c37de0 (a org.jboss.mq.SpyXAConnection)
at 
org.jboss.mq.SpyXAConnection.createXAQueueSession(SpyXAConnection.java:105)
at 
org.jboss.jms.asf.StdServerSessionPool.create(StdServerSessionPool.java:326) 

at 
org.jboss.jms.asf.StdServerSessionPool.init(StdServerSessionPool.java:156) 

at 
org.jboss.jms.asf.StdServerSessionPoolFactory.getServerSessionPool(StdServerSessionPoolFactory.java:91) 


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:585)
at org.jboss.ejb3.mdb.MDB.createSessionPool(MDB.java:677)
at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:522)


--
Bill Burke
Chief Architect
JBoss Inc.


---
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] Re: JMS problems on Branch_4_0

2006-02-03 Thread Bill Burke

I should probably elaborate.

It hangs at deploy time.  Server is spinning too (max CPU).

Bill Burke wrote:
Yeah, something is up with Branch_4_0 with JMS.  Works find with 
4.0.3SP1 (same EJB3 code).


Bill Burke wrote:

My MDB tests seem to be hanging, Can't figure out why.  I do a thread 
dump and got the following...  Any clues?  Did somebody recently 
change JMS on Branch_4_0?


Thanks


RMI TCP Connection(2)-192.168.0.2 daemon prio=5 tid=0x27bbdcf0 
nid=0xc78 runnable [0x285fc000..0x285ffd68]

at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.RuntimeException.init(RuntimeException.java:43)
at 
java.lang.IllegalStateException.init(IllegalStateException.java:38)
at 
org.jboss.mq.server.JMSDestinationManager.getID(JMSDestinationManager.java:245) 

at 
org.jboss.mq.server.JMSServerInterceptorSupport.getID(JMSServerInterceptorSupport.java:92) 

at 
org.jboss.mq.server.TracingInterceptor.getID(TracingInterceptor.java:85)
at 
org.jboss.mq.server.JMSServerInvoker.getID(JMSServerInvoker.java:93)

at org.jboss.mq.il.jvm.JVMServerIL.getID(JVMServerIL.java:101)
at org.jboss.mq.Connection.askForAnID(Connection.java:1021)
at org.jboss.mq.Connection.checkClientID(Connection.java:998)
- locked 0x06c37de0 (a org.jboss.mq.SpyXAConnection)
at 
org.jboss.mq.SpyXAConnection.createXAQueueSession(SpyXAConnection.java:105) 

at 
org.jboss.jms.asf.StdServerSessionPool.create(StdServerSessionPool.java:326) 

at 
org.jboss.jms.asf.StdServerSessionPool.init(StdServerSessionPool.java:156) 

at 
org.jboss.jms.asf.StdServerSessionPoolFactory.getServerSessionPool(StdServerSessionPoolFactory.java:91) 


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:585)
at org.jboss.ejb3.mdb.MDB.createSessionPool(MDB.java:677)
at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:522)





--
Bill Burke
Chief Architect
JBoss Inc.


---
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] RE: WebService tests timeout

2006-02-03 Thread Ryan Campbell








I have also seen these fail occasionally with
503, bad gateway errors.











From: Dimitris
Andreadis 
Sent: Friday, February 03, 2006
5:11 AM
To: [EMAIL PROTECTED]; jboss-development@lists.sourceforge.net
Cc: Thomas Diesler
Subject: WebService tests timeout





I've noticed2 webservices tests that
timeout (and fail) occasionally at 60 secondswhen
contactingexternal webservices:



org.jboss.test.jbossnet.external.ExternalUnitTestCase

org.jboss.test.jbossnet.external.RedeployExternalUnitTestCase



Is this timeout configurable? I seem to be
getting a response in just about one minute. Is this normal for WS
:)



Thanks

service name=BabelFishService
documentationTranslates text of up to 5k in length, between a variety
of languages./documentation
port name=BabelFishPort
binding=tns:BabelFishBinding
soap:address
location=http://services.xmethods.net:80/perl/soaplite.cgi/
/port
/service

service name=GoogleSearchService
port name=GoogleSearchPort binding=typens:GoogleSearchBinding
soap:address location=http://api.google.com/search/beta2/
/port
/service











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 03 February, 2006 01:45
To: Adrian
 Brock; Clebert Suconic;
Dimitris Andreadis; jboss-development@lists.sourceforge.net;
QA; Ryan Campbell
Subject: jboss-3.2-testsuite Build
Completed With Testsuite Errors
Importance: High

View results here - http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060202175301





 
  
  TESTS
  FAILED
  
 
 
  
  Ant
  Error Message:/services/cruisecontrol/work/scripts/build-jboss-common.xml:235:
  The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26:
  Build Successful - Tests completed with errors or failures.
  
 
 
  
  Date
  of build:02/02/2006 17:53:01
  
 
 
  
  Time
  to build:50 minutes 27 seconds
  
 
 
  
  Last
  changed:02/02/2006 14:17:10
  
 
 
  
  Last
  log entry:JBAS-2768, change
  tests that produce varying resutls based on jdk/os platform to logging
  warning messages rather than code assertions
  
 









 
  
  
  
 









 
  
  Unit Tests:
  (1847) Total Errors and Failures: (2) 
  
 
 
  
  
  
   

testFederated


org.jboss.test.jbossnet.external.ExternalUnitTestCase

   
   

testFederated


org.jboss.test.jbossnet.external.RedeployExternalUnitTestCase

   
  
  
  
  
  
  
  
  
  
  
  
  
  
 
 
  
  
  
  
  
  
  
  
  
  
  
  
 
 
  
  
  
  
  
  
  
  
  
 









 
  
  Modifications
  since last build: (first 50 of 14) 
  
 
 
  
  1.2.2.20
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.java
  
  
  JBAS-2768, change tests
  that produce varying resutls based on jdk/os platform to logging warning
  messages rather than code assertions
  
 
 
  
  1.1.2.1
  
  
  modified
  
  
  csuconic
  
  
  testsuite/src/main/org/jboss/test/guid/GUIDTestCase.java
  
  
  Renaming GUIDTest to
  the correct name, so it can be part of the testsuite
  
 
 
  
  1.11.2.10
  
  
  modified
  
  
  dimitris
  
  
  server/src/main/org/jboss/invocation/MarshalledInvocation.java
  
  
  JBAS-2767,
  Conditionally set useFullHashMode to true, when SerialVersion.version ==
  SerialVersion.JBOSS_402
  
 
 
  
  1.165.2.198
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/build.xml
  
  
  added 4.0.3SP1 to
  compat matrix
  
 
 
  
  1.1.2.16
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/imports/server-config.xml
  
  
  JBAS-2758: pass
  serialization flag to jboss startup *and* shutdown
  
 
 
  
  1.165.2.197
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/build.xml
  
  
  JBAS-2758: pass
  serialization flag to jboss startup *and* shutdown
  
 
 
  
  1.2.2.22
  
  
  modified
  
  
  adrian
  
  
  messaging/src/main/org/jboss/mq/server/JMSDestinationManager.java
  
  
  [JBAS-2762] - Avoid
  infinite loop when there is no state manager.
  
 
 
  
  1.4.2.3
  
  
  modified
  
  
  dimitris
  
  
  jmx/src/main/javax/management/MBeanServerConnection.java
  
  
  synch with 4.x
  
 
 
  
  1.165.2.196
  
  
  modified
  
  
  rcampbell
  
  
  testsuite/build.xml
  
  
  JBAS-2758: add usage of
  org.jboss.j2ee.Serialization flag to compatibility matrix
  
 
 
  
  1.1.4.3
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/jbossmx/performance/TestCase.java
  
  
  fix compatibility test
  failures
  
 
 
  
  1.1.4.3
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/jbossmx/implementation/TestCase.java
  
  
  fix compatibility test
  failures
  
 
 
  
  1.2.4.4
  
  
  modified
  
  
  dimitris
  
  
  testsuite/src/main/org/jboss/test/jbossmx/compliance/TestCase.java
  
  
  fix compatibility test
  failures
  
 
 
  
  1.1.4.2
  
  
  modified
  
  
  dimitris
  
  
  common/src/main/org/jboss/util/id/GUID.java
  
  
  JBAS-2718, define a
  serialVersionUID 

[JBoss-dev] SVN Commit Email List

2006-02-03 Thread Damon Sicore
Dev,Just a reminder, as I keep getting asked how to subscribe to the svn commit email list, here's the link to the SF page to subscribe:https://lists.sourceforge.net/lists/listinfo/jboss-svn-commitsSincerely,Damon --- [EMAIL PROTECTED]    JBoss Labs Lead     214-883-6733 36FD 368C 38E4 2DA2 6E2C  C0A6 FA7F 8A87 EA10 65A9 Public Key:  http://keys.sicore.org/jboss.txt  

[JBoss-dev] jboss-3.2-testsuite build.214 Build Fixed

2006-02-03 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060203190902Lbuild.214
BUILD COMPLETE-build.214Date of build:02/03/2006 19:09:02Time to build:49 minutes 13 secondsLast changed:02/03/2006 09:44:06Last log entry:extend copyright to 2006, remove dimitris' duplicate entry




   Unit Tests: (1847)   Total Errors and Failures: (0)All Tests Passed
Modifications since last build:(first 50 of 20)1.1.4.1modifieddimitrisbuild/docs/copyright.txtextend copyright to 2006, remove dimitris' duplicate entry1.11.2.11modifieddimitrisserver/src/main/org/jboss/invocation/MarshalledInvocation.javaJBAS-2767, throw NestedRuntimeException instead so that the root exception is not eaten up1.165.2.201modifieddimitristestsuite/build.xmlno need to test jbossnet across versions, according to Thomas1.165.2.200modifieddimitristestsuite/build.xmlJBAS-2770, org.jboss.test.jbossmq.test.Jms11UnitTest excluded since we are running agains 3.2.6/3.2.7 too1.1.1.1.4.8modifieddimitristestsuite/src/main/org/jboss/test/jbossnet/security/SecurityUnitTestCase.javaJBAS-2772, dont' execute the test if the sources had been compiled using jdk1.3, meaningorg.jboss.net.axis.server.JBossAuthenticationHandlerorg.jboss.net.axis.server.JBossAuthorizationHandlerare not present1.165.2.199modifiedrcampbelltestsuite/build.xmlremove jbossmx, add jbossnet to compat matrix1.2.2.20modifieddimitristestsuite/src/main/org/jboss/test/cmp2/commerce/QueryTest.javaJBAS-2768, change tests that produce varying resutls based on jdk/os platform to logging warning messages rather than code assertions1.1.2.1modifiedcsuconictestsuite/src/main/org/jboss/test/guid/GUIDTestCase.javaRenaming GUIDTest to the correct name, so it can be part of the testsuite1.11.2.10modifieddimitrisserver/src/main/org/jboss/invocation/MarshalledInvocation.javaJBAS-2767, Conditionally set useFullHashMode to true, when SerialVersion.version == SerialVersion.JBOSS_4021.165.2.198modifiedrcampbelltestsuite/build.xmladded 4.0.3SP1 to compat matrix1.1.2.16modifiedrcampbelltestsuite/imports/server-config.xmlJBAS-2758: pass serialization flag to jboss startup *and* shutdown1.165.2.197modifiedrcampbelltestsuite/build.xmlJBAS-2758: pass serialization flag to jboss startup *and* shutdown1.2.2.22modifiedadrianmessaging/src/main/org/jboss/mq/server/JMSDestinationManager.java[JBAS-2762] - Avoid infinite loop when there is no state manager.1.4.2.3modifieddimitrisjmx/src/main/javax/management/MBeanServerConnection.javasynch with 4.x1.165.2.196modifiedrcampbelltestsuite/build.xmlJBAS-2758: add usage of org.jboss.j2ee.Serialization flag to compatibility matrix1.1.4.3modifieddimitristestsuite/src/main/org/jboss/test/jbossmx/performance/TestCase.javafix compatibility test failures1.1.4.3modifieddimitristestsuite/src/main/org/jboss/test/jbossmx/implementation/TestCase.javafix compatibility test failures1.2.4.4modifieddimitristestsuite/src/main/org/jboss/test/jbossmx/compliance/TestCase.javafix compatibility test failures1.1.4.2modifieddimitriscommon/src/main/org/jboss/util/id/GUID.javaJBAS-2718, define a serialVersionUID for GUID and introduce SerialVersion. The default for 3.2..x will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can be overriden by defining org.jboss.j2ee.Serialization for 4.0.2+ compatibility (the opposite of the 4.0.x branch)1.2.4.2modifieddimitriscommon/src/main/org/jboss/util/id/SerialVersion.javaJBAS-2718, define a serialVersionUID for GUID and introduce SerialVersion. The default for 3.2..x will be legacy compatibility (3.2.x and maybe 4.0.0/4.0.1) which can be overriden by defining org.jboss.j2ee.Serialization for 4.0.2+ compatibility (the opposite of the 4.0.x branch)



RE: [JBoss-dev] cglib vs javassit for proxies

2006-02-03 Thread Jason T. Greene








I am all for this, cglib sucks



-Jason













From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
 M Stark
Sent: Friday, February 03, 2006
1:47 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] cglib vs
javassit for proxies





So I have to introduce a proxy for a
javax.net.SSLServerSocket which is an abstract class and so have to use cglib
or javassist. I see some proxy working in the head javassist, but this is not
in the 4.0 branch version. We also dont bundle javassist with 4.0
currently. I assume we would rather have javassist be the only bytecode
manipulation framework in jboss. Is there a timeframe for completing the
javassist proxy so we can think about moving hibernate, webservices, cmp2.x,
etc over to it?












RE: [JBoss-dev] cglib vs javassit for proxies

2006-02-03 Thread Jason T. Greene








I should clarify, for WS, we just need plain
javabean generation. So I can add that to our list of things to do. BTW I was
too harsh, there are nice things about cglib. I just ran into a lot of bugs.



-Jason













From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason T. Greene
Sent: Friday, February 03, 2006
7:56 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] cglib vs
javassit for proxies





I am all for this, cglib sucks



-Jason













From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
 M Stark
Sent: Friday, February 03, 2006
1:47 PM
To: jboss-development@lists.sourceforge.net
Subject: [JBoss-dev] cglib vs
javassit for proxies





So I have to introduce a proxy for a
javax.net.SSLServerSocket which is an abstract class and so have to use cglib
or javassist. I see some proxy working in the head javassist, but this is not
in the 4.0 branch version. We also dont bundle javassist with 4.0
currently. I assume we would rather have javassist be the only bytecode
manipulation framework in jboss. Is there a timeframe for completing the
javassist proxy so we can think about moving hibernate, webservices, cmp2.x,
etc over to it?














Re: [JBoss-dev] cglib vs javassit for proxies

2006-02-03 Thread Bill Burke

Javassist is pretty good, problem is that it doesn't have a junit testsuite.

Jason T. Greene wrote:
I should clarify, for WS, we just need plain javabean generation. So I 
can add that to our list of things to do. BTW I was too harsh, there are 
nice things about cglib. I just ran into a lot of bugs.


 


-Jason

 




*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Jason T. Greene

*Sent:* Friday, February 03, 2006 7:56 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* RE: [JBoss-dev] cglib vs javassit for proxies

 


I am all for this, cglib sucks…

 


-Jason

 




*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Scott M Stark

*Sent:* Friday, February 03, 2006 1:47 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* [JBoss-dev] cglib vs javassit for proxies

 

So I have to introduce a proxy for a javax.net.SSLServerSocket which is 
an abstract class and so have to use cglib or javassist. I see some 
proxy working in the head javassist, but this is not in the 4.0 branch 
version. We also don’t bundle javassist with 4.0 currently. I assume we 
would rather have javassist be the only bytecode manipulation framework 
in jboss. Is there a timeframe for completing the javassist proxy so we 
can think about moving hibernate, webservices, cmp2.x, etc over to it?


 



--
Bill Burke
Chief Architect
JBoss Inc.


---
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=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] JMS problems on Branch_4_0

2006-02-03 Thread Bill Burke
Let me expand on this.  When deploying an MDB3, it just hangs on 
deployment.  Thread dump shows this.


Same EJB 3.0 code (same dist).  MDB runs fine on 4.0.3SP1. I also see 
that the MDB EJB3 tests are passing in HEAD as well from nightly build 
from like 5 hours ago.  I haven't gotten a successful 4.0.x message 
since 10:30 am.  I also see a few build timeouts for Branch_4_0 at 5:30 
am and 7:30 am.  Again, has anybody committed any JMS stuff to branch 4 
that would effect this?


Bill Burke wrote:
My MDB tests seem to be hanging, Can't figure out why.  I do a thread 
dump and got the following...  Any clues?  Did somebody recently change 
JMS on Branch_4_0?


Thanks


RMI TCP Connection(2)-192.168.0.2 daemon prio=5 tid=0x27bbdcf0 
nid=0xc78 runnable [0x285fc000..0x285ffd68]

at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.RuntimeException.init(RuntimeException.java:43)
at 
java.lang.IllegalStateException.init(IllegalStateException.java:38)
at 
org.jboss.mq.server.JMSDestinationManager.getID(JMSDestinationManager.java:245) 

at 
org.jboss.mq.server.JMSServerInterceptorSupport.getID(JMSServerInterceptorSupport.java:92) 

at 
org.jboss.mq.server.TracingInterceptor.getID(TracingInterceptor.java:85)
at 
org.jboss.mq.server.JMSServerInvoker.getID(JMSServerInvoker.java:93)

at org.jboss.mq.il.jvm.JVMServerIL.getID(JVMServerIL.java:101)
at org.jboss.mq.Connection.askForAnID(Connection.java:1021)
at org.jboss.mq.Connection.checkClientID(Connection.java:998)
- locked 0x06c37de0 (a org.jboss.mq.SpyXAConnection)
at 
org.jboss.mq.SpyXAConnection.createXAQueueSession(SpyXAConnection.java:105)
at 
org.jboss.jms.asf.StdServerSessionPool.create(StdServerSessionPool.java:326) 

at 
org.jboss.jms.asf.StdServerSessionPool.init(StdServerSessionPool.java:156) 

at 
org.jboss.jms.asf.StdServerSessionPoolFactory.getServerSessionPool(StdServerSessionPoolFactory.java:91) 


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:585)
at org.jboss.ejb3.mdb.MDB.createSessionPool(MDB.java:677)
at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:522)


--
Bill Burke
Chief Architect
JBoss Inc.


---
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


RE: [JBoss-dev] cglib vs javassit for proxies

2006-02-03 Thread Steve Ebersole
I sent this to a number of other lists, but forgot this one.  Apologies.
I actually just today checked in a pluggable bytecode API into
Hibernate.  Hibernate does now support either CGLIB or Javassist for all
bytecode services.

As an aside, our experience with CGLIB has been very good.  Juozas (one
of the CGLIB developers) is very active in the Hibernate community and
is always extremely responsive to any needs we might encounter.  My $.02

The reason for allowing Javassist to be used instead of CGLIB was merely
to allow a user choice.  Especially in the case of JBoss where Javassist
is used in a lot of places, it just makes sense to have the option to
not have to bundle yet another jar.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Friday, February 03, 2006 8:39 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] cglib vs javassit for proxies

Javassist is pretty good, problem is that it doesn't have a junit
testsuite.

Jason T. Greene wrote:
 I should clarify, for WS, we just need plain javabean generation. So I

 can add that to our list of things to do. BTW I was too harsh, there
are 
 nice things about cglib. I just ran into a lot of bugs.
 
  
 
 -Jason
 
  
 


 
 *From:* [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] *On Behalf Of 
 *Jason T. Greene
 *Sent:* Friday, February 03, 2006 7:56 PM
 *To:* jboss-development@lists.sourceforge.net
 *Subject:* RE: [JBoss-dev] cglib vs javassit for proxies
 
  
 
 I am all for this, cglib sucks...
 
  
 
 -Jason
 
  
 


 
 *From:* [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] *On Behalf Of 
 *Scott M Stark
 *Sent:* Friday, February 03, 2006 1:47 PM
 *To:* jboss-development@lists.sourceforge.net
 *Subject:* [JBoss-dev] cglib vs javassit for proxies
 
  
 
 So I have to introduce a proxy for a javax.net.SSLServerSocket which
is 
 an abstract class and so have to use cglib or javassist. I see some 
 proxy working in the head javassist, but this is not in the 4.0 branch

 version. We also don't bundle javassist with 4.0 currently. I assume
we 
 would rather have javassist be the only bytecode manipulation
framework 
 in jboss. Is there a timeframe for completing the javassist proxy so
we 
 can think about moving hibernate, webservices, cmp2.x, etc over to it?
 
  
 

-- 
Bill Burke
Chief Architect
JBoss Inc.


---
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=kkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


---
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=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


Re: [JBoss-dev] JMS problems on Branch_4_0

2006-02-03 Thread Bill Burke
JMSDestinationManager had typo.  it should be a null check instead of a 
!= null check.  Typo from backmerge.   I guess if you put down the code 
for awhile you see it!


   /**
* Gets the ID attribute of the JMSServer object
*
* @return   The ID value
*/
   public String getID()
   {
  String ID = null;

  while (true)
  {
 try
 {
if (stateManager != null)
   throw new IllegalStateException(Null state manager);


Bill Burke wrote:
Let me expand on this.  When deploying an MDB3, it just hangs on 
deployment.  Thread dump shows this.


Same EJB 3.0 code (same dist).  MDB runs fine on 4.0.3SP1. I also see 
that the MDB EJB3 tests are passing in HEAD as well from nightly build 
from like 5 hours ago.  I haven't gotten a successful 4.0.x message 
since 10:30 am.  I also see a few build timeouts for Branch_4_0 at 5:30 
am and 7:30 am.  Again, has anybody committed any JMS stuff to branch 4 
that would effect this?


Bill Burke wrote:

My MDB tests seem to be hanging, Can't figure out why.  I do a thread 
dump and got the following...  Any clues?  Did somebody recently 
change JMS on Branch_4_0?


Thanks


RMI TCP Connection(2)-192.168.0.2 daemon prio=5 tid=0x27bbdcf0 
nid=0xc78 runnable [0x285fc000..0x285ffd68]

at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.init(Throwable.java:196)
at java.lang.Exception.init(Exception.java:41)
at java.lang.RuntimeException.init(RuntimeException.java:43)
at 
java.lang.IllegalStateException.init(IllegalStateException.java:38)
at 
org.jboss.mq.server.JMSDestinationManager.getID(JMSDestinationManager.java:245) 

at 
org.jboss.mq.server.JMSServerInterceptorSupport.getID(JMSServerInterceptorSupport.java:92) 

at 
org.jboss.mq.server.TracingInterceptor.getID(TracingInterceptor.java:85)
at 
org.jboss.mq.server.JMSServerInvoker.getID(JMSServerInvoker.java:93)

at org.jboss.mq.il.jvm.JVMServerIL.getID(JVMServerIL.java:101)
at org.jboss.mq.Connection.askForAnID(Connection.java:1021)
at org.jboss.mq.Connection.checkClientID(Connection.java:998)
- locked 0x06c37de0 (a org.jboss.mq.SpyXAConnection)
at 
org.jboss.mq.SpyXAConnection.createXAQueueSession(SpyXAConnection.java:105) 

at 
org.jboss.jms.asf.StdServerSessionPool.create(StdServerSessionPool.java:326) 

at 
org.jboss.jms.asf.StdServerSessionPool.init(StdServerSessionPool.java:156) 

at 
org.jboss.jms.asf.StdServerSessionPoolFactory.getServerSessionPool(StdServerSessionPoolFactory.java:91) 


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:585)
at org.jboss.ejb3.mdb.MDB.createSessionPool(MDB.java:677)
at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:522)





--
Bill Burke
Chief Architect
JBoss Inc.


---
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


Re: [JBoss-dev] cglib vs javassit for proxies

2006-02-03 Thread Bill Burke
You'll find that Javassist gives you a lot more flexibilty as it has a 
built in javacompiler and can replace code for you.  With Javassist it 
should be really easy to intercept field access for the EJB 3.0 
requirements.


Steve Ebersole wrote:

I sent this to a number of other lists, but forgot this one.  Apologies.
I actually just today checked in a pluggable bytecode API into
Hibernate.  Hibernate does now support either CGLIB or Javassist for all
bytecode services.

As an aside, our experience with CGLIB has been very good.  Juozas (one
of the CGLIB developers) is very active in the Hibernate community and
is always extremely responsive to any needs we might encounter.  My $.02

The reason for allowing Javassist to be used instead of CGLIB was merely
to allow a user choice.  Especially in the case of JBoss where Javassist
is used in a lot of places, it just makes sense to have the option to
not have to bundle yet another jar.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Friday, February 03, 2006 8:39 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] cglib vs javassit for proxies

Javassist is pretty good, problem is that it doesn't have a junit
testsuite.

Jason T. Greene wrote:


I should clarify, for WS, we just need plain javabean generation. So I




can add that to our list of things to do. BTW I was too harsh, there


are 


nice things about cglib. I just ran into a lot of bugs.



-Jason








*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Jason T. Greene

*Sent:* Friday, February 03, 2006 7:56 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* RE: [JBoss-dev] cglib vs javassit for proxies



I am all for this, cglib sucks...



-Jason








*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Scott M Stark

*Sent:* Friday, February 03, 2006 1:47 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* [JBoss-dev] cglib vs javassit for proxies



So I have to introduce a proxy for a javax.net.SSLServerSocket which


is 

an abstract class and so have to use cglib or javassist. I see some 
proxy working in the head javassist, but this is not in the 4.0 branch




version. We also don't bundle javassist with 4.0 currently. I assume


we 


would rather have javassist be the only bytecode manipulation


framework 


in jboss. Is there a timeframe for completing the javassist proxy so


we 


can think about moving hibernate, webservices, cmp2.x, etc over to it?








--
Bill Burke
Chief Architect
JBoss Inc.


---
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


RE: [JBoss-dev] cglib vs javassit for proxies

2006-02-03 Thread Steve Ebersole
Define replace code for you...  You mean as in replace the class def
*in the classloader*?

Currently field interception (using either) is only
implemented/available via build task.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill
Burke
Sent: Friday, February 03, 2006 9:04 PM
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] cglib vs javassit for proxies

You'll find that Javassist gives you a lot more flexibilty as it has a 
built in javacompiler and can replace code for you.  With Javassist it 
should be really easy to intercept field access for the EJB 3.0 
requirements.

Steve Ebersole wrote:
 I sent this to a number of other lists, but forgot this one.
Apologies.
 I actually just today checked in a pluggable bytecode API into
 Hibernate.  Hibernate does now support either CGLIB or Javassist for
all
 bytecode services.
 
 As an aside, our experience with CGLIB has been very good.  Juozas
(one
 of the CGLIB developers) is very active in the Hibernate community and
 is always extremely responsive to any needs we might encounter.  My
$.02
 
 The reason for allowing Javassist to be used instead of CGLIB was
merely
 to allow a user choice.  Especially in the case of JBoss where
Javassist
 is used in a lot of places, it just makes sense to have the option to
 not have to bundle yet another jar.
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of
Bill
 Burke
 Sent: Friday, February 03, 2006 8:39 PM
 To: jboss-development@lists.sourceforge.net
 Subject: Re: [JBoss-dev] cglib vs javassit for proxies
 
 Javassist is pretty good, problem is that it doesn't have a junit
 testsuite.
 
 Jason T. Greene wrote:
 
I should clarify, for WS, we just need plain javabean generation. So I
 
 
can add that to our list of things to do. BTW I was too harsh, there
 
 are 
 
nice things about cglib. I just ran into a lot of bugs.

 

-Jason

 


 


 
*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Jason T. Greene
*Sent:* Friday, February 03, 2006 7:56 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* RE: [JBoss-dev] cglib vs javassit for proxies

 

I am all for this, cglib sucks...

 

-Jason

 


 


 
*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of 
*Scott M Stark
*Sent:* Friday, February 03, 2006 1:47 PM
*To:* jboss-development@lists.sourceforge.net
*Subject:* [JBoss-dev] cglib vs javassit for proxies

 

So I have to introduce a proxy for a javax.net.SSLServerSocket which
 
 is 
 
an abstract class and so have to use cglib or javassist. I see some 
proxy working in the head javassist, but this is not in the 4.0 branch
 
 
version. We also don't bundle javassist with 4.0 currently. I assume
 
 we 
 
would rather have javassist be the only bytecode manipulation
 
 framework 
 
in jboss. Is there a timeframe for completing the javassist proxy so
 
 we 
 
can think about moving hibernate, webservices, cmp2.x, etc over to it?

 

 
 

-- 
Bill Burke
Chief Architect
JBoss Inc.


---
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


---
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=lnkkid3432bid#0486dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development