[JBoss-dev] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: non-java clients

2005-03-26 Thread [EMAIL PROTECTED]
To get an overview of the JBoss Messaging architecture, go to 
http://www.jboss.org/wiki/Wiki.jsp?page=JBossMessaging. You'll find there 
Messaging Core and JMS Facade design documents. This should give you a pretty 
good idea where your layer might fit in. 

The most straigtforward way to implement it is probably a new facade. You can 
call it CSharpMS or whatever you want to call it. You'll need a server-side 
facade layer that hooks into JBoss Remoting and also code that translates you 
XML traffic into messages/management traffic. Your interface layer must know 
how to interact with the Client Manager, Destination Manager, and so on. 

Take a look at the org.jboss.messaging and org.jboss.jms packages under the 
jboss-head/jms project. 

As for the lifespan of JBossMQ, the plan is to be replaced by JBoss Messaging 
as soon as the later proves to be production ready.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871698#3871698

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871698


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] jboss-3.2-jdk-matrix build.85 Build Successful

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050326201600Lbuild.85
BUILD COMPLETE - build.85Date of build: 03/26/2005 20:16:00Time to build: 22 minutes 4 secondsLast changed: 03/25/2005 15:56:49Last log entry: Use the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (1)1.4.4.2modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.



[JBoss-dev] jboss-3.2-testsuite Build Failed

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050326173918
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:66: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See tests.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/26/2005 17:39:18Time to build: 151 minutes 50 secondsLast changed: 03/25/2005 15:56:49Last log entry: Use the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (1)1.4.4.2modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.



[JBoss-dev] [JBossCache] - Re: IdentityLock write lock

2005-03-26 Thread drosenbaum
Thanks Bela for the reply.  Will there be a patch or something available for 
Hibernate 2.1.8?  I am going to have an app going to production in the next 
month or 2 and would like to be able to use the Hibernate query cache with 
TreeCache if possible.

Thanks,
Daniel

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871697#3871697

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871697


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBossCache] - Re: How do I get rollback to occur with remote cache access?

2005-03-26 Thread [EMAIL PROTECTED]
Maybe the remote cache was not enrolled in the TX, did you make sure that this 
was the case ?
Also, try the following: call Transaction.setRollbackOnly() on top of throwing 
the exception and see whether the data on the remote cache is not removed when 
the TX rolls back.
If this is still the case, can you create a simple test case and submit it in 
the form of a JIRA bug report (attach the test case). This would be really 
helpful to us !

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871696#3871696

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871696


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBossCache] - Re: IdentityLock write lock

2005-03-26 Thread [EMAIL PROTECTED]
The way the Hibernate TreeCacheProvider uses the TreeCache is broken (or, in 
other words, not optimal), and has been changed. The new code will be available 
as part of Hibernate 3 final. The integration code will be beta though, and 
will be final in one of the subsequent Hibernate versions.
The main reason is the mismatch between H's assumption of optimistic locking 
and JBossCache's pessimistic locking.
The new Hibernate TreeCacheProvider will minimize the locking exceptions, but 
not completely remove them: only the JBossCache version implementing optimistic 
locking will get rid of them completely, this is planned for JBossCache 1.3 or 
1.4.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871695#3871695

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871695


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-115) beforeEviction() callback

2005-03-26 Thread Bela Ban (JIRA)
beforeEviction() callback
-

 Key: JBCACHE-115
 URL: http://jira.jboss.com/jira/browse/JBCACHE-115
 Project: JBoss Cache
Type: Feature Request
Versions: 1.2.1
Reporter: Bela Ban
 Assigned to: Bela Ban 
 Fix For: 1.3




-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBossCache] - Re: before evicted event handler

2005-03-26 Thread [EMAIL PROTECTED]
added request: http://jira.jboss.com/jira/browse/JBCACHE-115

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871694#3871694

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871694


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] jboss-head Build Failed

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050326163526
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/26/2005 16:35:26Time to build: 16 minutes 10 secondsLast changed: 03/26/2005 13:44:56Last log entry: Fix typo in comment.




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (23)1.2modifiedreverbeltransaction/src/main/org/jboss/tm/remoting/ClientInvocationHandler.javaFix typo in comment.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMInvocationHandler.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DTMServant.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DistributedTransactionManager.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/server/DistributedTransactionManagerMBean.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Terminator.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionFactory.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionInactiveException.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TransactionNotPreparedException.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/TxPropagationContext.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Vote.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/ClientInvocationHandler.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/Invocation.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/RemoteProxy.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Coordinator.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicCommitException.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicHazardException.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicMixedException.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/HeuristicRollbackException.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/RecoveryCoordinator.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Resource.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Status.javaFirst stab at JBoss remoting support for the DTM.1.1addedreverbeltransaction/src/main/org/jboss/tm/remoting/interfaces/Synchronization.javaFirst stab at JBoss remoting support for the DTM.



[JBoss-dev] jboss-4.0-jdk-matrix Build Failed

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050326160930
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/26/2005 16:09:30Time to build: 17 minutes 13 secondsLast changed: 03/25/2005 18:50:14Last log entry: [JBAS-1604] - Make a start on the JMSRA trace logging




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (28)1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/GenericDLQHandler.javaSource code tidyup1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/DLQHandler.javaSource code tidyup1.2.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsServerSession.javaSource code tidyup1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.javaSource code tidyup1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.javaSource code tidyup1.2.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/DummyResourceAdapter.javaSource code tidyup1.11.2.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployer.javaSource code tidyup1.3.4.1modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterFactory.javaSource code tidyup1.3.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterObjectModelFactory.javaSource code tidyup1.5.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsLocalTransaction.javaSource code tidyup1.5.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsResourceAdapter.javaSource code tidyup1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.javaSource code tidyup1.9.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionFactoryImpl.javaSource code tidyup1.7.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionRequestInfo.javaSource code tidyup1.10.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.javaSource code tidyup1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsManagedConnectionFactory.javaSource code tidyup1.6.6.3modifiedstarksmremoting/src/main/org/jboss/remoting/transport/socket/SocketServerInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.4.6.1modifiedstarksmserver/src/main/org/jboss/logging/Log4jSocketServer.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.10.2.3modifiedstarksmserver/src/main/org/jboss/invocation/pooled/server/PooledInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.3.2.3modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/FormAuthUnitTestCase.javaAccess the resource without attempting a login to validate that the session is valid and that any caching on the server is working as expected.



[JBoss-dev] jboss-4.0-testsuite Build Failed

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050326144524
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/26/2005 14:45:24Time to build: 21 minutes 40 secondsLast changed: 03/25/2005 18:50:14Last log entry: [JBAS-1604] - Make a start on the JMSRA trace logging




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (54)1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/GenericDLQHandler.javaSource code tidyup1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/DLQHandler.javaSource code tidyup1.2.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsServerSession.javaSource code tidyup1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.javaSource code tidyup1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.javaSource code tidyup1.2.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/DummyResourceAdapter.javaSource code tidyup1.11.2.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployer.javaSource code tidyup1.3.4.1modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterFactory.javaSource code tidyup1.3.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterObjectModelFactory.javaSource code tidyup1.5.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsLocalTransaction.javaSource code tidyup1.5.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsResourceAdapter.javaSource code tidyup1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.javaSource code tidyup1.9.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionFactoryImpl.javaSource code tidyup1.7.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionRequestInfo.javaSource code tidyup1.10.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.javaSource code tidyup1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsManagedConnectionFactory.javaSource code tidyup1.6.6.3modifiedstarksmremoting/src/main/org/jboss/remoting/transport/socket/SocketServerInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.4.6.1modifiedstarksmserver/src/main/org/jboss/logging/Log4jSocketServer.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.10.2.3modifiedstarksmserver/src/main/org/jboss/invocation/pooled/server/PooledInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.3.2.3modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/FormAuthUnitTestCase.javaAccess the resource without attempting a login to validate that the session is valid and that any caching on the server is working as expected.1.406.2.47modifiedstarksmtestsuite/build.xmlInclude all deploy/jms content recursively in the jacc test configuration1.1.4.3modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/Jac

[JBoss-dev] jboss-3.2 build.318 Build Successful

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050326140637Lbuild.318
BUILD COMPLETE - build.318Date of build: 03/26/2005 14:06:37Time to build: 21 minutes 20 secondsLast changed: 03/25/2005 15:56:49Last log entry: Use the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (1)1.4.4.2modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.



[JBoss-dev] jboss-4.0 Build Failed

2005-03-26 Thread qa

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050326132946
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/26/2005 13:29:46Time to build: 21 minutes 54 secondsLast changed: 03/25/2005 18:50:14Last log entry: [JBAS-1604] - Make a start on the JMSRA trace logging




    Unit Tests: (0)    Total Errors and Failures: (0) 
 Modifications since last build: (32)1.2.8.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsMessageConsumer.java[JBAS-1604] - Make a start on the JMSRA trace logging1.10.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.java[JBAS-1604] - Make a start on the JMSRA trace logging1.11.6.2modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.java[JBAS-1604] - Make a start on the JMSRA trace logging1.8.2.1modifiedstarksmserver/src/main/org/jboss/tm/usertx/client/ClientUserTransaction.javaUse the org.jboss.naming.NamingContextFactory.lastInitialContext thread local to allow the UserTransactionSessionFactory to be obtained using the same JNDI env used to lookup the UserTransaction. Resolves (JBAS-1270) UserTransaction with non default ProviderURL.1.8.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployment.java[JBAS-1446] - Add trace logging for rar deployment operations1.3.4.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ActivationSpecFactory.java[JBAS-1446] - Add trace logging to activation spec construction1.1.2.3modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObjectFactory.java[JBAS-1446] - Add TRACE logging to AdminObject construction.1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/GenericDLQHandler.javaSource code tidyup1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/DLQHandler.javaSource code tidyup1.2.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/JmsServerSession.javaSource code tidyup1.1.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/inflow/dlq/AbstractDLQHandler.javaSource code tidyup1.1.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/AdminObject.javaSource code tidyup1.2.6.1modifiedejortconnector/src/main/org/jboss/resource/deployment/DummyResourceAdapter.javaSource code tidyup1.11.2.1modifiedejortconnector/src/main/org/jboss/resource/deployment/RARDeployer.javaSource code tidyup1.3.4.1modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterFactory.javaSource code tidyup1.3.2.2modifiedejortconnector/src/main/org/jboss/resource/deployment/ResourceAdapterObjectModelFactory.javaSource code tidyup1.5.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsLocalTransaction.javaSource code tidyup1.5.2.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsResourceAdapter.javaSource code tidyup1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSessionFactoryImpl.javaSource code tidyup1.9.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionFactoryImpl.javaSource code tidyup1.7.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsConnectionRequestInfo.javaSource code tidyup1.10.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsSession.javaSource code tidyup1.11.6.1modifiedejortconnector/src/main/org/jboss/resource/adapter/jms/JmsManagedConnectionFactory.javaSource code tidyup1.6.6.3modifiedstarksmremoting/src/main/org/jboss/remoting/transport/socket/SocketServerInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.4.6.1modifiedstarksmserver/src/main/org/jboss/logging/Log4jSocketServer.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.10.2.3modifiedstarksmserver/src/main/org/jboss/invocation/pooled/server/PooledInvoker.javaUpdate the accept catch to handle Throwables. Part of (JBAS-1559) Check all serverSocket accept threads.1.3.2.3modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/FormAuthUnitTestCase.javaAccess the resource without attempting a login to validate that the session is valid and that any caching on the server is working as expected.1.406.2.47modifiedstarksmtestsuite/build.xmlInclude all deploy/jms content recursively in the jacc test configuration1.1.4.3modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/JaccAuthoriza

[JBoss-dev] [JBossCache] - Re: Lock Acquisition Timeouts In JBC 1.2.1

2005-03-26 Thread jiwils
I thought it might be something like that, but should I get the 
IllegalStateException that I got (shown above) when I did that?

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871684#3871684

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871684


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [Design of Persistence on JBoss] - Hibernate performance problems in JBoss

2005-03-26 Thread MassMadX
Hello everyone,

last day I did some tests concerning the performance of Hibernate within
Jboss and "standalone".
I came to some disappointing results 
concerning the performance within JBoss (using CMT):


1) The datasource access seems to be significantly slower as with Hibernate 
"standalone". 
In some examples it was three times slower.

2) Moreover I was not able to do caching (using Hasttable, EhCache, as well as 
JBoss' TreeCache) beyond the scope of a single transaction.
This dramatically decreases the performance.
I  mean  the following: 
When I perform a certain select statement for
the first time within a transaction it takes about 750 msecs, 
if i perform it again within the same transaction (i.e., within the 
same ejb-method call) it takes 60 msecs.
Now, if perform this transaction (i.e. ejb-method call) again and again,
 it always takes  the same 750 resp. 60 msecs. 
For me it seems that there is no caching beyond transaction scope. 
Btw, I encountered no differences when using transactional, read-write,
nonstrict-read-write caching

Now I wonder about the following:

Did I do something seriously wrong?

Is it not possible to do caching beyond the scope of a single transaction
(which seems to be very unlogical to me)?

Btw, I used a standard hibernate-service.xml. 
Moreover, I used postgres and the standard postgres-ds.xml.
(but hsqldb was the same).

Thanks a lot for your help, best wishes and happy eastern

Michael

**

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871678#3871678

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871678


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Created: (EJBTHREE-115) Doco on Hibernate integration

2005-03-26 Thread Bill Burke (JIRA)
Doco on Hibernate integration
-

 Key: EJBTHREE-115
 URL: http://jira.jboss.com/jira/browse/EJBTHREE-115
 Project: EJB 3.0
Type: Task
Reporter: Bill Burke
 Fix For: Preview 5


* mix of .hbm.xml and @Entity
* tutorial on .hbm.xml
* Exposing Session/Query
* Query cache tutorial and doco


-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Updated: (EJBTHREE-115) Doco on Hibernate integration

2005-03-26 Thread Bill Burke (JIRA)
 [ http://jira.jboss.com/jira/browse/EJBTHREE-115?page=history ]

Bill Burke updated EJBTHREE-115:


Fix Version: Preview 5

> Doco on Hibernate integration
> -
>
>  Key: EJBTHREE-115
>  URL: http://jira.jboss.com/jira/browse/EJBTHREE-115
>  Project: EJB 3.0
> Type: Task
> Reporter: Bill Burke
>  Fix For: Preview 5

>
>
> * mix of .hbm.xml and @Entity
> * tutorial on .hbm.xml
> * Exposing Session/Query
> * Query cache tutorial and doco

-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Assigned: (JBCACHE-114) Standalone Build

2005-03-26 Thread Bela Ban (JIRA)
 [ http://jira.jboss.com/jira/browse/JBCACHE-114?page=history ]

Bela Ban reassigned JBCACHE-114:


Assign To: Bela Ban  (was: Ryan Campbell)

> Standalone Build
> 
>
>  Key: JBCACHE-114
>  URL: http://jira.jboss.com/jira/browse/JBCACHE-114
>  Project: JBoss Cache
> Type: Task
> Reporter: Ryan Campbell
> Assignee: Bela Ban

>
>
> Ben and I have a plan for moving jboss-cache to a standalone build before the 
> new build system is complete.
> 1.  Bela eliminates dependencies
> 2.  Ben creates basic standalone build.xml and adds jboss-cache.jar to 
> jboss-thirdparty
> 3.  Ryan removes cache from jboss-head, jboss-3.2 and jboss-4.0 cvs aliases
> 3.  Ryan adds nightly jboss-cache standalone build to cruisecontrol
> Once jboss-cache has non-container tests migrated from testsuite...
> 1.  Ben/Bela add tests to jboss-cache testsuite
> 2.  Ryan adds test target to nightly cruisecontrol
> Ben said there will eventually be cache integration code in the AS, at which 
> point:
> 1.  Create a the new integration module (jboss-as-cache)
> 2.  Add it to the cvs aliases as "cache"

-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-109) Expose Hibernate Query through javax.persistence.Query

2005-03-26 Thread Bill Burke (JIRA)
 [ http://jira.jboss.com/jira/browse/EJBTHREE-109?page=history ]
 
Bill Burke closed EJBTHREE-109:
---

Resolution: Done

> Expose Hibernate Query through javax.persistence.Query
> --
>
>  Key: EJBTHREE-109
>  URL: http://jira.jboss.com/jira/browse/EJBTHREE-109
>  Project: EJB 3.0
> Type: Feature Request
> Reporter: Bill Burke
>  Fix For: Preview 5

>
>


-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-107) Support mixed HB3/EJB3 deployments

2005-03-26 Thread Bill Burke (JIRA)
 [ http://jira.jboss.com/jira/browse/EJBTHREE-107?page=history ]
 
Bill Burke closed EJBTHREE-107:
---

Resolution: Done

> Support mixed HB3/EJB3 deployments
> --
>
>  Key: EJBTHREE-107
>  URL: http://jira.jboss.com/jira/browse/EJBTHREE-107
>  Project: EJB 3.0
> Type: Feature Request
> Reporter: Bill Burke
>  Fix For: Preview 5

>
>


-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBoss JIRA] Closed: (EJBTHREE-110) Expose Hibernate Session through EntityManager interface

2005-03-26 Thread Bill Burke (JIRA)
 [ http://jira.jboss.com/jira/browse/EJBTHREE-110?page=history ]
 
Bill Burke closed EJBTHREE-110:
---

Resolution: Done

> Expose Hibernate Session through EntityManager interface
> 
>
>  Key: EJBTHREE-110
>  URL: http://jira.jboss.com/jira/browse/EJBTHREE-110
>  Project: EJB 3.0
> Type: Feature Request
> Reporter: Bill Burke
>  Fix For: Preview 5

>
>


-- 
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[JBoss-dev] [JBossCache] - Re: Lock Acquisition Timeouts In JBC 1.2.1

2005-03-26 Thread [EMAIL PROTECTED]
In 1.2.1, we use method-level locking (lock held for the duration of the method 
call, ege. put()). if no TXs are used. Therefore set the TX-level to NONE 
should solve this

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871675#3871675

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871675


---
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=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development