Re: [JBoss-dev] InvocationLayerStressTestCase timing out
I have tested with 1.4.0 and 1.3.1_01 jdks on win2k. The timeout only occurs in the OIL2 IL. I can even double the number of workers and messages being pushed through the other ILs without a problem. The OIL2 IL test seems to run fine on Linux. I have not tested any other platforms yet. -Seth --On Tuesday, July 30, 2002 9:48 AM -0400 Seth Sites [EMAIL PROTECTED] wrote: I noticed it on win2k jdk 1.4.0-b92. The test ran fine on Linux 2.4 kernel jdk 1.4.0-b92. I am looking into it. -Seth --On Tuesday, July 30, 2002 12:47 AM -0700 Scott M Stark [EMAIL PROTECTED] wrote: I'm seeing the org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase consistently timing out when running against main on a win2k box using the Sun JDK 1.3.1_03-b03. Anyone else seeing this? The www.lubega.com results show the same problem. configure: [echo] [echo] junit.timeout: 18 [echo] jbosstest.iterationcount: 10 [echo] jbosstest.threadcount: 5 [echo] jbosstest.beancount:5 [echo] marathon.timeout: 390 [echo] marathon.duration: 360 [echo] marathon.threadcount: 100 [copy] Copying 1 file to D:\usr\JBossMain\jboss-all\testsuite\output\gen-sr c\org\jboss\test\cts\interfaces init: maybejars: one-test: [mkdir] Created dir: D:\usr\JBossMain\jboss-all\testsuite\output\reports[delete] Deleting: D:\usr\JBossMain\jboss-all\testsuite\output\log\test.log [junit] Running org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase FAILED (timeout) Scott Stark Chief Technology Officer JBoss Group, LLC --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] InvocationLayerStressTestCase timing out
I noticed it on win2k jdk 1.4.0-b92. The test ran fine on Linux 2.4 kernel jdk 1.4.0-b92. I am looking into it. -Seth --On Tuesday, July 30, 2002 12:47 AM -0700 Scott M Stark [EMAIL PROTECTED] wrote: I'm seeing the org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase consistently timing out when running against main on a win2k box using the Sun JDK 1.3.1_03-b03. Anyone else seeing this? The www.lubega.com results show the same problem. configure: [echo] [echo] junit.timeout: 18 [echo] jbosstest.iterationcount: 10 [echo] jbosstest.threadcount: 5 [echo] jbosstest.beancount:5 [echo] marathon.timeout: 390 [echo] marathon.duration: 360 [echo] marathon.threadcount: 100 [copy] Copying 1 file to D:\usr\JBossMain\jboss-all\testsuite\output\gen-sr c\org\jboss\test\cts\interfaces init: maybejars: one-test: [mkdir] Created dir: D:\usr\JBossMain\jboss-all\testsuite\output\reports[delete] Deleting: D:\usr\JBossMain\jboss-all\testsuite\output\log\test.log [junit] Running org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase [junit] TEST org.jboss.test.jbossmq.perf.InvocationLayerStressTestCase FAILED (timeout) Scott Stark Chief Technology Officer JBoss Group, LLC --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] SQLException: [Microsoft][ODBC SQL ServerDriver]Optional feature not implemented
You need to use java.sql.Timestamp instead of java.sql.Date -Seth --On Saturday, July 27, 2002 12:04 AM +0530 Narayan Singh [EMAIL PROTECTED] wrote: Dear all, This is my first mail to the group. I have an entity EJB which uses CMP. One of the CMP fields is of java.sql.Date type.I am using MS SQL 2000 server as database server. I created a table in which the corresponding mapping column is of type DATETIME.I am using JBOSS2.2 and JDBC-ODBC bridge. I am unable to create the entity EJB. The following is the trace of exceptions i got. I think this problem is faced by some of u already..I will thankful to u if u find some solution to fix this problem [JAWS] java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented [JAWS]at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbc.SQLBindInParameterDate(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setDate(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(Unknown Source) [JAWS] at org.opentools.minerva.jdbc.PreparedStatementInPool.setObject(PreparedStat eme ntInPool.java:282) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.setParameter(JDBCCommand.java :33 4) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.setParameters(JDB CCr eateEntityCommand.java:165) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java: 159 ) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.execute(JDBCCreat eEn tityCommand.java:135) [JAWS]at org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.createEntity(JAWSPersis ten ceManager.java:122) [JAWS]at org.jboss.ejb.plugins.CMPPersistenceManager.createEntity(CMPPersistenceMa nag er.java:207) [JAWS]at org.jboss.ejb.EntityContainer.createHome(EntityContainer.java:441) [JAWS]at java.lang.reflect.Method.invoke(Native Method) [JAWS]at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityConta ine r.java:639) [JAWS]at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntityS ync hronizationInterceptor.java:160) [JAWS]at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstance Int erceptor.java:87) [JAWS]at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:1 35) [JAWS]at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorC MT. java:263) [JAWS]at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:8 6) [JAWS] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor. jav a:164) [JAWS]at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:106) [JAWS]at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:316) [JAWS]at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invokeHome(JRMPCon tai nerInvoker.java:369) [JAWS]at java.lang.reflect.Method.invoke(Native Method) [JAWS]at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) [JAWS]at sun.rmi.transport.Transport$1.run(Unknown Source) [JAWS]at java.security.AccessController.doPrivileged(Native Method) [JAWS]at sun.rmi.transport.Transport.serviceCall(Unknown Source) [JAWS]at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) [JAWS]at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) [JAWS]at java.lang.Thread.run(Unknown Source) [JAWS] java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Optional feature not implemented [JAWS]at sun.jdbc.odbc.JdbcOdbc.createSQLException(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbc.standardError(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbc.SQLBindInParameterDate(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setDate(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(Unknown Source) [JAWS]at sun.jdbc.odbc.JdbcOdbcPreparedStatement.setObject(Unknown Source) [JAWS] at org.opentools.minerva.jdbc.PreparedStatementInPool.setObject(PreparedStat eme ntInPool.java:282) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.setParameter(JDBCCommand.java :33 4) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.setParameters(JDB CCr eateEntityCommand.java:165) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java: 159 ) [JAWS]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCreateEntityCommand.execute(JDBCCreat eEn
[JBoss-dev] code submission
I have a patch for bug [ 564890 ] JMS recover/redelivery errors that I have tested and am ready to submit for review. I just have a few questions. 1) What is the best way to submit code patches for bugs. Is diff output preferred or just include the entire method that is changed? 2) Is it best to submit the code through the sourceforge interface at the bug report, or just email it to the dev list? Thanks, Seth --- 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] org.jboss.ejb.ContainerInvokerContainer not added to cvs
server\src\main\org\jboss\ejb\plugins\SecurityProxyInterceptor.java imports and uses org.jboss.ejb.ContainerInvokerContainer, but this file is not is cvs so build fails. -Seth --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
