[JBoss-dev] jboss-4.0-jdk-matrix build.95 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050226010427Lbuild.95 BUILD COMPLETE - build.95Date of build: 02/26/2005 01:04:27Time to build: 21 minutes 21 secondsLast changed: 02/25/2005 14:50:33Last log entry: JBREM-66 - fix for race condition on startup. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (17)1.7.10.3modifiedtelrodremoting/src/main/org/jboss/remoting/detection/multicast/MulticastDetector.javaJBREM-66 - fix for race condition on startup.1.16.4.4modifiedanddserver/src/main/org/jboss/Shutdown.javaJBAS-1362 - bin/shutdown reports -S to be the default option, it's -h1.18.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/ServiceDeployer.javaPrevent NPE with invalid 1.1.2.2modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/message/Message.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.1.2.3modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/message/MessageJavaBean.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.1.2.2modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/message/MessageTestCase.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.1.1.1.4.6modifiedtdieslerjaxrpc/src/main/org/apache/axis/message/SOAPBodyAxisImpl.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.2.2.5modifiedtdieslerjaxrpc/src/main/org/apache/axis/encoding/SerializationContextImpl.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.4.2.3modifiedtdiesleraspects/src/main/org/jboss/aspects/security/AuthenticationInterceptor.javaRemove trailing }1.7.4.3modifiedanddthirdparty/jacorb-jacorb/lib/jacorb_g.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.29.2.3modifiedanddthirdparty/jacorb-jacorb/lib/jacorb.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.8.4.2modifiedanddthirdparty/jacorb-jacorb/lib/idl.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.5.4.2modifiedanddthirdparty/jacorb-jacorb/lib/idl_g.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.24.2.3modifiedanddthirdparty/jacorb-jacorb/lib/README#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.2.2.5modifiedanddthirdparty/licenses/thirdparty-licenses.xml#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.7.6.2modifiedstarksmserver/src/main/org/jboss/invocation/http/interfaces/Util.javaRead the org.jboss.security.httpInvoker.sslSocketFactoryBuilder and ignore any exception as this is an optional override. Resolves [JBAS-1522] HttpNamingContextFactory fails due to system property read when under a security manager.1.15.4.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/test/StatefulSessionUnitTestCase.javaUse org.jboss.naming.NamingContextFactory as the Context.INITIAL_CONTEXT_FACTORY to ensure that the handle is saved with the expected JNDI environment.
[JBoss-dev] jboss-4.0-testsuite build.53 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050225224853Lbuild.53 BUILD COMPLETE - build.53Date of build: 02/25/2005 22:48:53Time to build: 106 minutes 43 secondsLast changed: 02/25/2005 14:50:33Last log entry: JBREM-66 - fix for race condition on startup. Unit Tests: (2305) Total Errors and Failures: (48)unknownorg.jboss.test.aop.test.AOPUnitTestCaseunknownorg.jboss.test.aop.test.RemotingUnitTestCasetestXmlorg.jboss.test.aop.test.SecurityUnitTestCasetestAnnotatedorg.jboss.test.aop.test.SecurityUnitTestCaseunknownorg.jboss.test.aop.test.TxLockUnitTestCaseunknownorg.jboss.test.aop.test.VersionedObjectUnitTestCasetestAllTx_RWLockorg.jboss.test.cache.stress.EvictionLocalStressTestCasetestEjbInterceptionorg.jboss.test.hibernate.test.HibernateIntgUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestEjbFinderorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEjbRemoveorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEjbLifeCycleorg.jboss.test.securitymgr.test.BMPUnitTestCasetestPrimaryKeyObjectIdentityorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEjbRemoteIForg.jboss.test.securitymgr.test.BMPUnitTestCasetestEntityHandleorg.jboss.test.securitymgr.test.BMPUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.BMPUnitTestCasetestProbeContainerCallbacksorg.jboss.test.securitymgr.test.BMPUnitTestCasetestContainerObjectsorg.jboss.test.securitymgr.test.BMPUnitTestCasetestUserTransactionorg.jboss.test.securitymgr.test.BMPUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.BMPUnitTestCaseunknownorg.jboss.test.securitymgr.test.BMPUnitTestCasetestEndpointOneorg.jboss.test.webservice.jbws79.JBWS79TestCasetestEndpointTwoorg.jboss.test.webservice.jbws79.JBWS79TestCasetestInvalidateorg.jboss.test.cluster.test.ScopedAttrBasedTestCase(Default)testInvalidateorg.jboss.test.cluster.test.ScopedAttrBasedTestCase(SyncModeNUseJvm)testInvalidateorg.jboss.test.cluster.test.ScopedSetAttributeTestCase(Default)testInvalidateorg.jboss.test.cluster.test.ScopedSetAttributeTestCase(SyncModeNUseJvm)testInvalidateorg.jboss.test.cluster.test.ScopedSetTriggerTestCase(Default)testInvalidateorg.jboss.test.cluster.test.ScopedSetTriggerTestCase(SyncModeNUseJvm)testInvalidateorg.jboss.test.cluster.test.ScopedTestCase(Default)testInvalidateorg.jboss.test.cluster.test.ScopedTestCase(SyncModeNUseJvm)testConcurrentPutorg.jboss.test.cluster.test.SessionBasedConcurrentTestCase(Default)testSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCase(Default)testSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCase(SyncModeNUseJvm)testUserInRoleServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestSecurityDomainorg.jboss.test.security.test.EJBSpecUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCasetestEjbCreateorg.jboss.test.securitymgr.test.BMPUnitTestCasetestMDBTimerorg.jboss.test.timer.test.BasicTimerUnitTestCasetestJBossEditorsorg.jboss.test.util.test.PropertyEditorsUnitTestCase Modifications since last build: (32)1.7.10.3modifiedtelrodremoting/src/main/org/jboss/remoting/detection/multicast/MulticastDetector.javaJBREM-66 - fix for race condition on startup.1.16.4.4modifiedanddserver/src/main/org/jboss/Shutdown.javaJBAS-1362 - bin/shutdown reports -S to be the default option, it's -h1.18.2.9modifiedtdieslerwebservice/src/main/org/jboss/webservice/ServiceDeployer.javaPrevent NPE with invalid 1.1.2.2modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/message/Message.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.1.2.3modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/message/MessageJavaBean.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.1.2.2modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/message/MessageTestCase.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.1.1.1.4.6modifiedtdieslerjaxrpc/src/main/org/apache/axis/message/SOAPBodyAxisImpl.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.2.2.5modifiedtdieslerjaxrpc/src/main/org/apache/axis/encoding/SerializationContextImpl.javaFix: http://jira.jboss.com/jira/browse/JBWS-1271.4.2.3modifiedtdiesleraspects/src/main/org/jboss/aspects/security/AuthenticationInterceptor.javaRemove trailing }1.7.4.3modifiedanddthirdparty/jacorb-jacorb/lib/jacorb_g.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.29.2.3modifiedanddthirdparty/jacorb-jacorb/lib/jacorb.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.8.4.2modifiedanddthirdparty/jacorb-jacorb/lib/idl.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.5.4.2modifiedanddthirdparty/jacorb-jacorb/lib/idl_g.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.24.2.3modifiedanddthirdparty/jacorb-jacorb/lib/RE
[JBoss-dev] jboss-3.2-jdk-matrix build.62 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log2005022508Lbuild.62 BUILD COMPLETE - build.62Date of build: 02/25/2005 22:22:08Time to build: 19 minutes 37 secondsLast changed: 02/25/2005 09:45:48Last log entry: JBAS-1362 - bin/shutdown reports -S to be the default option, it's -h Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.9.2.9modifiedanddserver/src/main/org/jboss/Shutdown.javaJBAS-1362 - bin/shutdown reports -S to be the default option, it's -h1.1.2.3modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javamoved encodeFileName() / decodeFileName() methods to org.jboss.util.file.Files to be re-used by other modules1.1.2.11modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaJBAS-1500 session.invalidate does not gets replicated1.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1511 http session produce WARN session null message
[JBoss-dev] jboss-head build.839 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050225200835Lbuild.839 BUILD COMPLETE - build.839Date of build: 02/25/2005 20:08:35Time to build: 24 minutes 15 secondsLast changed: 02/25/2005 17:46:23Last log entry: JBBUILD-24 Build jboss-remoting.jar Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (29)1.16modifiedrecampbelljbossas/jbossbuild.xmlJBBUILD-24 Build jboss-remoting.jar1.1addedrecampbellremoting/jbossbuild.xmlJBBUILD-24 Build jboss-remoting.jar1.5modifiedpatriot1burkeejb3/INSTALL.htmlupdate doc errors1.9modifiedpatriot1burkeejb3/docs/tutorial/index.htmlupdate doc errors1.8modifiedpatriot1burkeejb3/docs/tutorial/index.wikiupdate doc errors1.6modifiedpatriot1burkeejb3/docs/tutorial/installing.htmlupdate doc errors1.71modifiedpatriot1burkeaop/build.xmlcloser to Microcontainer changes1.1addedpatriot1burkeaop/src/main/org/jboss/aop/AnnotationOverrides.javacloser to Microcontainer changes1.1addedpatriot1burkeaop/src/main/org/jboss/aop/AspectBinder.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/AnnotationInfoMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/CallInfoMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/ConstructorInfoMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/ExecutionConstructorInfoMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/ExecutionMethodInfoMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/FieldInfoGetMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/FieldInfoMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/FieldInfoSetMatcher.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/InfoUtil.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/MethodInfoMatcher.javacloser to Microcontainer changes1.8modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/Pointcut.javacloser to Microcontainer changes1.8modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/PointcutExpression.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/TypeInfoMatcher.javacloser to Microcontainer changes1.5modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/Typedef.javacloser to Microcontainer changes1.6modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/TypedefExpression.javacloser to Microcontainer changes1.3modifiedpatriot1burkeaop/src/main/org/jboss/aop/pointcut/WithinInfoMatcher.javacloser to Microcontainer changes1.8modifiedpatriot1burkeaop/src/main/org/jboss/aop/advice/GenericInterceptorFactory.javacloser to Microcontainer changes1.6modifiedpatriot1burkeaop/src/main/org/jboss/aop/advice/InterceptorFactory.javacloser to Microcontainer changes1.5modifiedpatriot1burkeaop/src/main/org/jboss/aop/advice/ScopedInterceptorFactory.javacloser to Microcontainer changes1.4modifiedpatriot1burkeaop/src/main/org/jboss/aop/introduction/AnnotationIntroduction.javacloser to Microcontainer changes
[JBoss-dev] [Design of JTA on JBoss] - Transaction problem
Hi everybody !
We are developping a J2EE application and we have big problems with the
transactions.
We are searching many documentations and every day we are learning lots of
interesting things but... currently, we have decided to change the finders into
the DAO for a performance reason (we are using another driver to connect to
SQLServer2000 : JTDS1.0.2 --> excellent driver).
But the problem is that if one creates or updates entities and then just after
a query DAO is executed to get back the data whose state has just changed, we
don't receive them.
Correctly! Because the DAO is called inside of a session bean's method with
trans-attribute "required". Thus the data is not yet committed.
Unfortunately, i can't to provide you ejb-jar.xml, jboss.xml because the files
of our application are in my workplace but i'm going to show an example :
|
| JournalDelegate
|
|
| public Collection determineValidJournals(String logonId) throws
SystemException{
| try{
| return getSessionFacade().determinevalidJournals(logonId);
| } catch (RemoteException re) {
|throw new SystemException(...);
| }
| }
|
|
|
|
| JournalSessionFacadeObject
| --> EJBObject
|
| public Collection determineValidJournals(String logonId) throws
SystemException, RemoteException;
|
|
|
|
| JournalSessionFacade
| --> SessionBean
|
| public Collection determineValidJournals(String logonId) throws
SystemException {
| return getSessionBean().determineValidJournals(logonId);
| }
|
|
|
|
|
| JournalSessionBeanObject
| --> EJBlocalObject
|
| public Collection determineValidJournals(String logonId) throws
SystemException;
|
|
|
|
| JournalSessionBean
| --> SessionBean
|
| public Collection determineValidJournals(String logonId) throws
SystemException {
|Iterator it = findAllFinancialCentersByVerifier(logonId);
|Collection coll = new ArrayList();
|while (it.hasNext()){
| FinancialCenterVO fc = (FinancialCenterVO) it.next();
| validateJournal(fc);
| coll.addAll(findValidJournals(fc));
| -->
| This last method causes a problem
|
|
|}
|return coll;
| }
|
|
| public void validateJournal(fc) throws SystemException{
|Iterator it = findCheckableJournals(fc);
|while (it.hasNext()){
| JournalVO journal = (JournalVO) it.next();
| update data into DB after check of datas validity by
findByPrimaryKey(..).setValueOb
| ject(journal);
|}
| }
|
|
ejb-jar.xml
Only the local Session beans and Entity Beans methods are in "REQUIRED", NOT
the session facades methods.
To resolve the fastest way, we want to put the findValidJournals(.) in
determineValidJournals() of SessionFacade. But JBoss has decided to put
this method into a transaction !!!
In fact, that doesn't resolve our problem --> So that method has been put into
JournalDelegate. But this is abnormal --> 2 network calls
Why does JBoss automatically make a transaction
Does a tag exist to modify this behavior
Thank for your time :-)
Pascale
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868022#3868022
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868022
---
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-4.0 build.405 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050225175455Lbuild.405 BUILD COMPLETE - build.405Date of build: 02/25/2005 17:54:55Time to build: 52 minutes 52 secondsLast changed: 02/25/2005 14:50:33Last log entry: JBREM-66 - fix for race condition on startup. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.7.10.3modifiedtelrodremoting/src/main/org/jboss/remoting/detection/multicast/MulticastDetector.javaJBREM-66 - fix for race condition on startup.
[JBoss-dev] [Deployers on JBoss (Deployers/JBoss)] - Deployment work on local machine but not on server...
The project I'm working on has two part: - Web application (a war file) - Enterprise application (an ear file) I tried to merge them to one part and make the web application a web module of the enterprise application. I deployed the war into the ear file and the web application can be accessed successfully on my local testing machine. However, when I deploy the ear file on the server, I couldn't access to the web application anymore. Any explanation/solution would be appreciated. Thanks, Chuottui. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868009#3868009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868009 --- 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.838 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050225171551Lbuild.838 BUILD COMPLETE - build.838Date of build: 02/25/2005 17:15:51Time to build: 19 minutes 56 secondsLast changed: 02/25/2005 15:27:58Last log entry: moved to new folder layout, with docs split by component Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (41)1.3deletedccrouchadmin-console/docs/requirements/sitemap-phase_1_0.vsdmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/use_cases.docmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/use_cases.pdfmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/datasource_elements.pdfmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/datasource_elements.xlsmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/datasource_stats_elements.pdfmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/datasource_stats_elements.xlsmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/requirements/sitemap-phase_1_0.pdfmoved to new folder layout, with docs split by component1.2deletedccrouchadmin-console/docs/design/technical_summary.pdfmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/design/implementation_implications.docmoved to new folder layout, with docs split by component1.3deletedccrouchadmin-console/docs/design/implementation_implications.pdfmoved to new folder layout, with docs split by component1.2deletedccrouchadmin-console/docs/design/technical_summary.docmoved to new folder layout, with docs split by component1.15modifiedbelabancache/src/main/org/jboss/cache/lock/LockStrategyFactory.javahandles BELA as well now1.9modifiedbelabantestsuite/src/main/org/jboss/test/cache/test/local/TxDeadlockUnitTestCase.javano message1.3modifiedbelabancache/src/main/org/jboss/cache/lock/IsolationLevel.javabela: new experimental LockStrategy, will be renamed :-)1.1addedbelabancache/src/main/org/jboss/cache/lock/BelasLockStrategy.javanew experimental LockStrategy, will be renamed :-)1.2modifiedbelabancache/src/main/org/jboss/cache/tests/ReentrantWriterPreferenceReadWriteLockTest.javano message1.1addedbelabancache/src/main/org/jboss/cache/tests/CopyOnWriteArrayTest.javanew test1.11modifiedtelrodremoting/src/main/org/jboss/remoting/detection/multicast/MulticastDetector.javaJBREM-66 - fix for race condition on startup.1.5modifiedpatriot1burkeejb3/docs/tutorial/installing.html*** empty log message ***1.22modifiedpatriot1burkeejb3/build.xml*** empty log message ***1.4modifiedpatriot1burkeejb3/INSTALL.html*** empty log message ***1.15modifiedrecampbelltools/etc/jbossbuild/tasks.xmlAllow a source to have an excludes attribute for code that shouldn't be compiled as a part of the main build1.15modifiedrecampbelljbossas/jbossbuild.xmlJBBUILD-23 JBBUILD-22 - additions for jax-rpc and transaction builds1.1addedrecampbelltransaction/jbossbuild.xmlJBBUILD-23 - builds jboss-transaction.jar and jboss-transaction-client.jar1.2modifiedpatriot1burkeejb3/src/test/org/jboss/ejb3/test/stateful/TesterBean.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.1addedpatriot1burkeejb3/src/main/org/jboss/ejb3/JndiProxyFactory.javabranches: 1.1.2;didn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.6modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/LocalProxy.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.12modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/ProxyDeployer.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.9modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/stateful/StatefulRemoteProxyFactory.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.6modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/stateful/BaseStatefulProxyFactory.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.6modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/stateful/StatefulLocalProxyFactory.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.3modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/remoting/RemoteProxyFactory.javadidn't realize that jnid.lookup didn't serialize return. So, had to create JNDI proxies.1.4modifiedpatriot1burkeejb3/src/main/org/jboss/ejb3/mdb/ConsumerContainer.javabranches: 1.4.2;didn't realize that jnid.lookup didn't serialize return. So, had to cr
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-24) Implement build for remoting module
Implement build for remoting module --- Key: JBBUILD-24 URL: http://jira.jboss.com/jira/browse/JBBUILD-24 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: Q105 Build jboss-remoting.jar -- 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] Commented: (JBBUILD-19) Allow JARS to act as Sources
[ http://jira.jboss.com/jira/browse/JBBUILD-19?page=comments#action_12315818 ] Ryan Campbell commented on JBBUILD-19: -- Possibly look at zipfileset for this, as it can include files from other zip files, as well as those from the filesystem. > Allow JARS to act as Sources > > > Key: JBBUILD-19 > URL: http://jira.jboss.com/jira/browse/JBBUILD-19 > Project: JBoss Build System > Type: Feature Request > Reporter: Ryan Campbell > Assignee: Ryan Campbell > Priority: Critical > Fix For: Q105 > > Original Estimate: 1 day > Remaining: 1 day > > In the system module there is a need to unjar getopt & log4j and recombine > them into other artifacts. This is also done in security and perhaps in > aspects. It seems like we should support this as a first-class construct. > So this is another source, just like src/main or a resource: > > which extracts the jar contents to output/log4j.jar/* . > They could then be included in an artifact like any compiled class: > > > > > > > > > -- 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] Created: (JBAS-1527) Transaction Manager Statistics Improvement
Transaction Manager Statistics Improvement -- Key: JBAS-1527 URL: http://jira.jboss.com/jira/browse/JBAS-1527 Project: JBoss Application Server Type: Feature Request Components: JTA service Reporter: Adrian Brock Add the ability to drill down into inflight transactions to see: 1) Duration of transaction so far 2) Resources in the transaction 3) Allow an admin to manually rollback a "stuck" transaction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=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: JBossCache in Tomcat w/ Transaction Support
Bela, I was able to solve my original problem. I stopped using a JDBCCacheLoader. But I get an entirely different error now. I am using TreeCache, Tomcat add JOTM for transactions on two different JVM's. When the following code is exectued | txn.begin(); | tree.put(node,key,value); | txn.commit(); | I get an error on the second Tomcat install (the TreeCache getting the replication) from org.jgroups.blocks.RpcDispatcher sayinganonymous wrote : failed invoking method commit() should not be called on TreeCache directly and the next line of the stack trace is anonymous wrote : at org.jboss.cache.TreeCache.commit() but the call was made on the usertransaction object in the first Tomcat server. Any suggestions? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867987#3867987 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867987 --- 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 the new POJO MicroContainer] - Re: VFS and ClassLoader interaction
One other minor note on the current Set getPackages() method signature of DomainClassLoader. This precludes the DomainClassLoader implementation from being a subclass of ClassLoader due to its Package[] getPackages() method. We might as well use that signature as I don't see a reason to disallow the DomainClassLoader implementation from being a ClassLoader. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867986#3867986 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867986 --- 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] Commented: (JBCACHE-102) Exception when Submitting Load into HttpSession
[ http://jira.jboss.com/jira/browse/JBCACHE-102?page=comments#action_12315814 ] Clebert Suconic commented on JBCACHE-102: - For replicating this problem, you need to execute the client as: java -jar testClient.jar http://$MYTESTIP_1:8080 10 1 0 In another words, submitting load against only one of the nodes, having the other node actuating as a backup node. > Exception when Submitting Load into HttpSession > --- > > Key: JBCACHE-102 > URL: http://jira.jboss.com/jira/browse/JBCACHE-102 > Project: JBoss Cache > Type: Bug > Environment: jboss-4.0 Branch_4_0 > Reporter: Clebert Suconic > Assignee: Ben Wang > > > When submitting load using ou HttpStressTest application, using 10 threads in > the client and 1 session hold per thread, we have thrown these exceptions: > java.lang.IllegalStateException: standardSession.setAttribute.ise > at > org.jboss.web.tomcat.tc5.session.ClusteredSession.setAttribute(ClusteredSession.java:185) > at > org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:129) > at > org.jboss.test.weblayer.HttpStressTest.doGet(HttpStressTest.java:24) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at > org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) > at > org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:147) > at > org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:81) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at > org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:534) > And: > java.lang.IllegalArgumentException: You can only add ClusteredSessions to > this Manager > at > org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:228) > at > org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:38) > at > org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91) > at > org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at > org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:534) -- 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 -
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-102) Exception when Submitting Load into HttpSession
Exception when Submitting Load into HttpSession --- Key: JBCACHE-102 URL: http://jira.jboss.com/jira/browse/JBCACHE-102 Project: JBoss Cache Type: Bug Environment: jboss-4.0 Branch_4_0 Reporter: Clebert Suconic Assigned to: Ben Wang When submitting load using ou HttpStressTest application, using 10 threads in the client and 1 session hold per thread, we have thrown these exceptions: java.lang.IllegalStateException: standardSession.setAttribute.ise at org.jboss.web.tomcat.tc5.session.ClusteredSession.setAttribute(ClusteredSession.java:185) at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:129) at org.jboss.test.weblayer.HttpStressTest.doGet(HttpStressTest.java:24) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:147) at org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:81) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:534) And: java.lang.IllegalArgumentException: You can only add ClusteredSessions to this Manager at org.jboss.web.tomcat.tc5.session.JBossCacheManager.storeSession(JBossCacheManager.java:228) at org.jboss.web.tomcat.tc5.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:38) at org.jboss.web.tomcat.tc5.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:91) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:743) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:534) -- 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-de
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1421) Implement JTS
[ http://jira.jboss.com/jira/browse/JBAS-1421?page=history ] Adrian Brock reassigned JBAS-1421: -- Assign To: Francisco Reverbel > Implement JTS > - > > Key: JBAS-1421 > URL: http://jira.jboss.com/jira/browse/JBAS-1421 > Project: JBoss Application Server > Type: Task > Components: JTA service > Versions: JBossAS-4.0.1 Final > Reporter: Adrian Brock > Assignee: Francisco Reverbel > Priority: Minor > > > Implement JTS > We at least want to implement the optional compatibility with OTS at the IIOP > level. > Additional features that would be nice to have: > 1) Distributed transactions over any protocol - i.e. protocol independenct > TPCs using > JBoss Remoting > 2) Multithreaded use of a transaction with a (pluggable?) mechanism for > reconciliation at > transaction commit. Although there are still places within J2EE that disallow > multi-threaded use > of a transaction, e.g. SFSB, the JCA workmanager, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=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 JBoss Admin Console] - Re: Update Data and Minor DataSource Module Suggestions
"strand" wrote : Can you describe in brief goals for 1.0 and 1.1 alpha versions - data source and jms administration? | Please take at look at the roadmap in JIRA http://jira.jboss.com/jira/browse/JBADMCON?report=com.atlassian.jira.plugin.system.project:roadmap-panel. Key pieces of functionality are marked as blocker or critical 'Feature Requests' and the roadmap includes timelines for phase 1.0 (Feb 15), and 1.1(Mar 31). For Phase 1.0 we were remiss in including the JIRA tasks at the appropriate level of granularity: so here is a list of functionality: | View a list of DataSources | View the connection pool information for a DataSource | View a DataSource | Create a DataSource | Update a DataSource | Remove a DataSource | | | "strand" wrote : Currently I see that there is only view functionality available, no update. When it is planned to be available - maybe this depends on the DeploymentService? | | | | Update is available, but only for datasources created with the Admin Console. Please see the following document in cvs for details | jboss-admin-console/docs/datasource/implementation_implications.doc | | "strand" wrote : | | What do you think about those two minor suggestions about datasources: | | 1) If user wants to create new datasource similar to existing one then copying/cloning DS data will be useful. Maybe sample presets for some DBs will be helpful too. | | | | Excellent suggestion. Please file a feature request in JIRA. As you can see Phase 1.1 is concentrating on JMS support and a few bug fixes, so we are unlikely to get to this in this current phase. If you would like to contribute and work on adding this feature I would be very happy to discuss it with you. | | "strand" wrote : | | 2) Connection URL - currently input text length is small (for DefaultDS on my installation) so maybe title attribute, onmouseover or some other event is needed to display the full text. This is in case there will be separate read-only and write-enabled modes. | | | | Please file a bug in JIRA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867980#3867980 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867980 --- 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: (JBADMCON-60) Add support for committing/rolling back AdminConsole changes
[ http://jira.jboss.com/jira/browse/JBADMCON-60?page=history ] Charles Crouch updated JBADMCON-60: --- Attachment: commit-changes_use_cases.doc First cut of use cases. Also checked into cvs, jboss-admin-console/docs/general_console > Add support for committing/rolling back AdminConsole changes > - > > Key: JBADMCON-60 > URL: http://jira.jboss.com/jira/browse/JBADMCON-60 > Project: JBoss Admin Console > Type: Feature Request > Components: DataSource, General Console > Versions: 1.1 alpha > Reporter: Charles Crouch > Fix For: 1.1 alpha > Attachments: commit-changes_use_cases.doc > > Original Estimate: 1 week > Remaining: 1 week > > This will add support, initially just for DataSources, for persisting changes > without committing them, then having the option to commit/rollback the > change. On the view layer an additional page is going to be needed for the > commit/rollback and a navigation update to access the page. > This will involve documenting additional use cases. The implementation will > likely involve a adding persistent store to the Admin Console, which will > most likely not be on a per user basis. Will also require integrating > entities that just exist in the persistent store with those that come from > the actual JBoss server, e.g. to show a list of Datasources, but not allow > Connection Pool viewing for those DataSources which haven't been saved. > Listing the individual changes that have been made prior to commit/rollback, > is out of scope for the current implementation. > Work will need to be done to clarify the semantics of commit/rollback, e.g. > how to handle a user updating a datasource which another has just deleted but > not yet committed. Where possible the most straightforward approach will be > taken. -- 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] [Design of JBoss Admin Console] - New use cases: support pending changes with commit/abandon
Currently (in Phase 1.0) all changes made through the Admin Console are applied immediately to the JBoss instance being administered. This may not always be the desired behavior and the capability is being added to make a number of changes through the Admin Console and then commit or abandon them at one time. Please see http://jira.jboss.com/jira/browse/JBADMCON-60 for details of this enhancement. The latest use cases can be found in cvs, under jboss-admin-console/docs or attached to the JIRA issue above. They are also copied here for convenience: USE CASE 1: View a component Basic Description An administrator uses the system to view information on a component, e.g. list of DataSources, one particular DataSource. Goal Display information on a particular component. Basic flow of events 1. The user indicates to the system that they wish to view information on a particular component for which they do not having any pending changes. 2. The system displays the information which reflects the current state of the system. 3. The use case ends. Alternate Flows A1.1: View an updated component At step 1) in the Basic Flow: 1. The user indicates to the system that they wish to view information on a particular component for which they have made pending changes. 2. The system displays the information which is includes the pending changes rather than just the current state of the system. 3. The use case ends. A1.2: List components after a create At step 1) in the Basic Flow: 1. The user indicates to the system that they wish to view information on a set of components, which includes one they have just added through the Admin Console but has not yet been created in the JBoss server. 2. The system displays a list of information on the components, including the component pending creation in the actual JBoss server. 3. The use case ends. A1.3: List components after a delete At step 1) in the Basic Flow: 1. The user indicates to the system that they wish to view information on a set of components, which includes one they have just deleted through the Admin Console but has not yet been removed from the JBoss server. 2. The system displays a list of information on the components, not including the component pending deletion from the actual JBoss server. 3. The use case ends. USE CASE 2: Committing changes Basic Description An administrator uses the system to carry out actions (e.g. update, create, or remove a DataSource) and then attempts to have those actions applied to the JBoss server. Goal A set of administration actions are successfully completed. Basic flow of events 1. The user carries out a series of administration actions in the Admin Console, e.g. update a DataSource, create a DataSource. 2. The user indicates to the system that they wish to view the pending changes that they have made through the Admin Console. 3. The system displays information on the pending changes the user has made. 4. The user indicates that the changes should be committed. 5. The system takes the pending changes the user has made and applies them. 6. The system indicates to the user that the changes were successfully made. 7. The use case ends. Alternate Flows A2.1: Abandon changes After step 3) in the Basic Flow: 1. The user indicates that the changes should not be applied and should be abandoned. 2. The system clears the list of pending changes and does not apply them. 3. The system indicates to the user that the changes were successfully abandonned. 4. The use case ends. A2.2: On commit, some changes fail to be applied After step 5) in the Basic Flow: 1. For each change that was attempted the system indicates to the user whether or not it was successfully applied. 2. The use case ends. A2.3: Resume administration After step 3) in the Basic Flow: 1. The user indicates that they wish to return to other administration activities without applying or abandoning the pending changes. 2. The system displays the information the user was viewing prior to viewing the pending changes. 3. The use case ends. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867975#3867975 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867975 --- 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 JBoss Remoting, Unified Invokers] - Re: Writing our own connector !
Sure. Technically, would only have to implement org.jboss.remoting.transport.ClientInvoker interface for client side implementation and extend the org.jboss.remoting.ServerInvoker class on the server side. However, would extend RemoteClientInvoker on the client side, so then only have to implement the abstract transport() method. User guide and wiki (http://www.jboss.org/wiki/Wiki.jsp?page=Remoting_configuration) goes into detail on how to configure for your own custom implementations. Feel free to also extend the SocketClientInvoker and SocketServerInvoker as you like. If you do build your own, would be great if you could contribute it back to the repository. Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867974#3867974 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867974 --- 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] Resolved: (JBREM-66) Race condition on startup
[ http://jira.jboss.com/jira/browse/JBREM-66?page=history ] Tom Elrod resolved JBREM-66: - Resolution: Done Fix Version: 1.2.0 beta Good catch. Thanks. Changed to start the detector before the listener. Will be in next remoting release as well as JBossAS 4.0.2 release. > Race condition on startup > - > > Key: JBREM-66 > URL: http://jira.jboss.com/jira/browse/JBREM-66 > Project: JBoss Remoting > Type: Bug > Versions: 1.0.1 final > Environment: linux, jobss 4.0.1, jdk 1.5_01 > Reporter: james ahlborn > Assignee: Tom Elrod > Priority: Minor > Fix For: 1.2.0 beta > > Original Estimate: 1 day > Remaining: 1 day > > I occassionally get this exception trace on jboss startup: > 2005-02-25 13:51:26,981 ERROR > [org.jboss.remoting.detection.multicast.MulticastD > etector] Error during detection of: Detection [identity:JBOSS Identity > [address: > itsy.hmsonline.com/10.67.89.58,instanceid:9d49962ca1854d0cx21bc15d1x1014159608ax > -7fff718,JMX id:itsy.hmsonline.com_1109263894685,domain:JBOSS],locators:2] > javax.management.RuntimeOperationsException > at > org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java > :495) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:636) > at > org.jboss.remoting.detection.AbstractDetector.detect(AbstractDetector.java: > 327) > at > org.jboss.remoting.detection.multicast.MulticastDetector.listen(MulticastDe > tector.java:212) > at > org.jboss.remoting.detection.multicast.MulticastDetector.access$100(Multica > stDetector.java:32) > at > org.jboss.remoting.detection.multicast.MulticastDetector$Listener.run(Multi > castDetector.java:240) > Caused by: java.lang.IllegalArgumentException: null object name > ... 6 more > I traced it through the 4.0.1 source code, and it seems that the "null" > pointer is the member variable registryObjectName in AbstractDetector.java. > this variable only is set during the start() method of this class, and if the > value is "null", a warning is logged. i don't see this warning, so i am > assuming this variable is set to a non-null value during the start() method. > this implies that this member variable is sometimes being accessed before the > start() method completes. This is probably because the > MulticaseDetector$Listener class is running on a separate thread. it should > probably block until the outer class is done starting. -- 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] [Design of JBoss Remoting, Unified Invokers] - Writing our own connector !
Hi, I was looking at your JBoss Remoting framework and I am wondering if it is possible to build own own Socket based connector instead of using the one provided by your framework. Thanks a lot. Salim. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867973#3867973 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867973 --- 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] Commented: (JBAS-11) Error redeploying dependent war
[ http://jira.jboss.com/jira/browse/JBAS-11?page=comments#action_12315811 ]
commented on JBAS-11:
---
I found a fix for this issue. In the method destroyService of the class
org.jboss.web.WebModule, a number of member variables are set null and this
shouldn't be done. So I did this change:
protected void destroyService()
{
// this.di = null;
// this.container = null;
// this.deployer = null;
}
This is apparently enough to solve the problem.
> Error redeploying dependent war
> ---
>
> Key: JBAS-11
> URL: http://jira.jboss.com/jira/browse/JBAS-11
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Versions: JBossAS-4.0.0 Final
> Reporter:
> Assignee: Scott M Stark
>
>
> This is a taken from the forum post from octopus see
> http://www.jboss.org/index.html?module=bb&op=viewtopic&t=56015.
> I have a deployed webapp which depends on some mbean (having depends clause
> in jboss-web.xml).
> When mbean is being redeployed it causes redeploying this webapp which
> finishes with NPE in WebModule.java
> This bug reproduced in both jboss 4.0.0 and 3.2.6
> Simple test case:
> Create sample service in /deploy, for example test-properties-service.xml
> Code:
>
> name="test:service=SystemProperties">
>
>
>
>
>
>
> Create sample war which depends on this service, for example
> Code:
> test.war
>|
> WEB-INF
> |
>web.xml
> jboss-web.xml
>|
> META-INF
>
> where web.xml
> Code:
>
>
>
> jboss-web.xml
> Code:
>
> test:service=SystemProperties
>
>
> now both test-properties-service.xml and test.war placed in /deploy and
> deployed successfully.
> Now update test-properties-service.xml (edit-save, touch, etc)
> jboss will try to redeploy test.war with following result:
> Code:
> 13:22:33,483 DEBUG [MainDeployer] Undeploying
> file:/C:/Cluster/jboss-3.2.6/server/all/deploy/test-pr
> operties-service
> .xml
> 13:22:33,483 DEBUG [SARDeployer] undeploying document
> file:/C:/Cluster/jboss-3.2.6/server/all/deploy
> /test-properties
> -service.xml
> 13:22:33,499 DEBUG [SARDeployer] stopping mbean test:service=SystemProperties
> 13:22:33,499 DEBUG [ServiceController] stopping service:
> test:service=SystemProperties
> 13:22:33,514 DEBUG [ServiceController] stopping dependent services for:
> test:service=SystemPropertie
> s depende
> nt services are: [ObjectName: jboss.web.deployment:war=test.war,id=-1080743623
> state: RUNNING
> I Depend On: test:service=SystemProperties
> Depends On Me: ]
> 13:22:33,530 DEBUG [ServiceController] stopping service:
> jboss.web.deployment:war=test.war,id=-10807
> 43623
> 13:22:33,530 DEBUG [ServiceController] stopping dependent services for:
> jboss.web.deployment:war=tes
> t.war,id=-1080743623
> dependent services are: []
> 13:22:33,546 DEBUG [WebModule] Stopping
> jboss.web.deployment:war=test.war,id=-1080743623
> 13:22:33,546 INFO [TomcatDeployer] undeploy, ctxPath=/test,
> warUrl=file:/C:/Cluster/jboss-3.2.6/ser
> ver/all/tmp/deploy/tm
> p45130test.war/
> 13:22:33,577 DEBUG [Context] Stopping
> 13:22:33,577 DEBUG [Context] Stopping filters
> 13:22:33,577 DEBUG [Context] Stopping filter 'CommonHeadersFilter'
> 13:22:33,592 DEBUG [Context] Processing standard container shutdown
> 13:22:33,608 DEBUG [Context] Sending application stop events
> 13:22:33,624 DEBUG [Context] resetContext
> jboss.web:j2eeType=WebModule,name=//localhost/test,J2EEApp
> lication=none,J2EESer
> ver=none [EMAIL PROTECTED]
> 13:22:33,624 DEBUG [Context] Stopping complete
> 13:22:33,639 DEBUG [WebModule] Stopped
> jboss.web.deployment:war=test.war,id=-1080743623
> 13:22:33,639 DEBUG [LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source
> =jboss.system:service
> =ServiceController,type=
> org.jboss.system.ServiceMBean.stop,sequenceNumber=225,timeStamp=10993981536
> 39,message=null,userD
> ata=jboss.web.deployment:war=test.war,id=-1080743623]
> 13:22:33,655 DEBUG [LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source
> =jboss.system:service
> =ServiceController,type=
> org.jboss.system.ServiceMBean.stop,sequenceNumber=226,timeStamp=10993981536
> 55,message=null,userD
> ata=test:service=SystemProperties]
> 13:22:33,671 DEBUG [LocalJBossServerDomain] handleNotification:
> javax.management.Notification[source
> =jboss.system:service
> =ServiceDeployer,type=org.jboss.deployment.SubDeployer.stop,sequenceNumber=114,timeStamp=10993981536
> 71,message=null,userD
> [EMAIL PROTECTED] { url=file:/C:/Cluster/jboss-3.2.6/server/all/deplo
> y/test-propertie
> s-service.xml }
> deployer: [EMAIL PROTECTED]
> status: Deployed
> state: STARTED
> watch:
> file:/C:/Cluster/j
[JBoss-dev] [JBoss JIRA] Created: (JBREM-66) Race condition on startup
Race condition on startup - Key: JBREM-66 URL: http://jira.jboss.com/jira/browse/JBREM-66 Project: JBoss Remoting Type: Bug Versions: 1.0.1 final Environment: linux, jobss 4.0.1, jdk 1.5_01 Reporter: james ahlborn Assigned to: Tom Elrod Priority: Minor I occassionally get this exception trace on jboss startup: 2005-02-25 13:51:26,981 ERROR [org.jboss.remoting.detection.multicast.MulticastD etector] Error during detection of: Detection [identity:JBOSS Identity [address: itsy.hmsonline.com/10.67.89.58,instanceid:9d49962ca1854d0cx21bc15d1x1014159608ax -7fff718,JMX id:itsy.hmsonline.com_1109263894685,domain:JBOSS],locators:2] javax.management.RuntimeOperationsException at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java :495) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:636) at org.jboss.remoting.detection.AbstractDetector.detect(AbstractDetector.java: 327) at org.jboss.remoting.detection.multicast.MulticastDetector.listen(MulticastDe tector.java:212) at org.jboss.remoting.detection.multicast.MulticastDetector.access$100(Multica stDetector.java:32) at org.jboss.remoting.detection.multicast.MulticastDetector$Listener.run(Multi castDetector.java:240) Caused by: java.lang.IllegalArgumentException: null object name ... 6 more I traced it through the 4.0.1 source code, and it seems that the "null" pointer is the member variable registryObjectName in AbstractDetector.java. this variable only is set during the start() method of this class, and if the value is "null", a warning is logged. i don't see this warning, so i am assuming this variable is set to a non-null value during the start() method. this implies that this member variable is sometimes being accessed before the start() method completes. This is probably because the MulticaseDetector$Listener class is running on a separate thread. it should probably block until the outer class is done starting. -- 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-3.2 build.302 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050225122706Lbuild.302 BUILD COMPLETE - build.302Date of build: 02/25/2005 12:27:06Time to build: 58 minutes 38 secondsLast changed: 02/25/2005 09:45:48Last log entry: JBAS-1362 - bin/shutdown reports -S to be the default option, it's -h Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.9.2.9modifiedanddserver/src/main/org/jboss/Shutdown.javaJBAS-1362 - bin/shutdown reports -S to be the default option, it's -h
[JBoss-dev] [Design of JBoss Portal] - Re: Forums Moderation
I just went through the JBoss/JCA user forum for this week's posts. ~70% were FAQs ~15% were in the wrong forum. +1 bug report (already fixed 8 months ago) against an older version of jboss even though the "READ THIS FIRST" says to check the latest version before posting. We need some mechanism to control the quality of the posts, otherwise users will just continue to fill the forums with SH*T making search unusable. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867962#3867962 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867962 --- 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 JBoss Eclipse IDE (dev)] - where is EJB3.0 Entity bean wizard in JbossIDE 1.5 preview
Hello, How to create EJB3 entity bean in JBossIDE 1.5 preview. Thanks. --tom View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867961#3867961 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867961 --- 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-66) Asynchronous interface for all EJB types
[ http://jira.jboss.com/jira/browse/EJBTHREE-66?page=history ] Bill Burke closed EJBTHREE-66: -- Resolution: Done > Asynchronous interface for all EJB types > > > Key: EJBTHREE-66 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-66 > Project: EJB 3.0 > Type: Feature Request > Components: EJB3 Extensions > Versions: Preview 4 > Reporter: Bill Burke > Assignee: Kabir Khan > Fix For: Preview 4 > > > Allow asynchronous interface that uses the Asynchronous aspect from the > aspect library. This should be usable from all EJB types except entities. > Look at Aspect Library Document for more information. -- 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] [Design the new POJO MicroContainer] - Re: VFS and ClassLoader interaction
Bouncycastle has all that is needed if its not in the bundled jce classes yet (and I think it is). It will be simple to create our own jar signing tool that is compatible with the default one. I have been thinking about needing to augment the build process anyway with a more advanced indexing tool that would get rid of the current runtime processing of at least the distribution jars as they are loaded. I'll look at merging the VFS notions with the existing classes and create testcases around signing, security, nested jars, file and http filesystems and single domain classpath ordering as the basis for really knowing what the classloading should look like. Beyond that, interaction of domains and exclusion of certain classes from being overriden by child domains needs to be flushed out. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867954#3867954 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867954 --- 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-83) jndi lookup of local SFSB always returns same proxy object (thus old oids)
jndi lookup of local SFSB always returns same proxy object (thus old oids) -- Key: EJBTHREE-83 URL: http://jira.jboss.com/jira/browse/EJBTHREE-83 Project: EJB 3.0 Type: Bug Versions: Preview 3 Reporter: Bill Burke Fix For: Preview 4 Assumption was made in code for EJB3 that jndi.lookup always serialized the call. This resulted in proxies being shared everywhere. THis was really bad for SFSB and Consumer because they assumed that a JNDI lookup always returned a new proxy. -- 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-83) jndi lookup of local SFSB always returns same proxy object (thus old oids)
[ http://jira.jboss.com/jira/browse/EJBTHREE-83?page=history ] Bill Burke closed EJBTHREE-83: -- Resolution: Done > jndi lookup of local SFSB always returns same proxy object (thus old oids) > -- > > Key: EJBTHREE-83 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-83 > Project: EJB 3.0 > Type: Bug > Versions: Preview 3 > Reporter: Bill Burke > Fix For: Preview 4 > > > Assumption was made in code for EJB3 that jndi.lookup always serialized the > call. This resulted in proxies being shared everywhere. THis was really bad > for SFSB and Consumer because they assumed that a JNDI lookup always returned > a new proxy. -- 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] Created: (JBBUILD-23) Implement build for transaction module
Implement build for transaction module -- Key: JBBUILD-23 URL: http://jira.jboss.com/jira/browse/JBBUILD-23 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: Q105 Build jboss-transaction.jar and jboss-transaction-client.jar -- 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: (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate
[ http://jira.jboss.com/jira/browse/JBAS-1526?page=history ]
Scott M Stark updated JBAS-1526:
Fix Version: JBossAS-4.0.2RC1
JBossPOJOServer-1.0 Alpha
JBossAS-5.0 Alpha
> Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
> permissions of the replaced delegate
>
>
> Key: JBAS-1526
> URL: http://jira.jboss.com/jira/browse/JBAS-1526
> Project: JBoss Application Server
> Type: Bug
> Components: Security
> Versions: JBossAS-4.0.1 SP1
> Environment: -
> Reporter: Roland R?z
> Assignee: Scott M Stark
> Fix For: JBossAS-4.0.2RC1, JBossPOJOServer-1.0 Alpha, JBossAS-5.0 Alpha
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
> permissions of the replaced delegate
> According to the JACC specification all Permissions of a CodeSource or
> ProtectionDomain should be returned. Currently these methods return only the
> JACC Permissions, without the Permissions of the delegate class.
> The JACC Specification states (http://java.sun.com/j2ee/javaacc/):
> 2.5 What a Provider Must Do
>
> A replacement Policy object must assume responsibility for performing all
> policy decisions within the JRE in which it is installed that are requested
> by way of the Policy interface that it implements.
> Example Implementation of DelegatingPolicy.getPermissions(x):
> public PermissionCollection getPermissions(ProtectionDomain domain) {
> PermissionCollection pc = super.getPermissions(domain);
> PermissionCollection delegated =
> delegate.getPermissions(domain);
> for (Enumeration e = delegated.elements();
> e.hasMoreElements();) {
> Permission p = (Permission) e.nextElement();
> pc.add(p);
> }
> return pc;
> }
> Regards,
> Andrea
--
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: (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate
[ http://jira.jboss.com/jira/browse/JBAS-1526?page=history ]
Scott M Stark reassigned JBAS-1526:
---
Assign To: Scott M Stark
> Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
> permissions of the replaced delegate
>
>
> Key: JBAS-1526
> URL: http://jira.jboss.com/jira/browse/JBAS-1526
> Project: JBoss Application Server
> Type: Bug
> Components: Security
> Versions: JBossAS-4.0.1 SP1
> Environment: -
> Reporter: Roland R?z
> Assignee: Scott M Stark
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
> permissions of the replaced delegate
> According to the JACC specification all Permissions of a CodeSource or
> ProtectionDomain should be returned. Currently these methods return only the
> JACC Permissions, without the Permissions of the delegate class.
> The JACC Specification states (http://java.sun.com/j2ee/javaacc/):
> 2.5 What a Provider Must Do
>
> A replacement Policy object must assume responsibility for performing all
> policy decisions within the JRE in which it is installed that are requested
> by way of the Policy interface that it implements.
> Example Implementation of DelegatingPolicy.getPermissions(x):
> public PermissionCollection getPermissions(ProtectionDomain domain) {
> PermissionCollection pc = super.getPermissions(domain);
> PermissionCollection delegated =
> delegate.getPermissions(domain);
> for (Enumeration e = delegated.elements();
> e.hasMoreElements();) {
> Permission p = (Permission) e.nextElement();
> pc.add(p);
> }
> return pc;
> }
> Regards,
> Andrea
--
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] [Design the new POJO MicroContainer] - Re: VFS and ClassLoader interaction
I think I mentioned this before, but I will repeat it anyway... I did at one point start to write a replacement for URLClassLoader to workaround Sun's bugs. Most of the work is just delegating to URLHandlers (which would obviously be replaced by the VFS in the current discussion). However, I couldn't find an open source implementation of the "encryption" used to sign jars. The other reason I wanted such an implementation was so we can do signing of unpacked deployments (the signing is currently only checked on packed jar files). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867939#3867939 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867939 --- 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 the new POJO MicroContainer] - Re: VFS and ClassLoader interaction
First, I'm not especially tied to the DomainClassLoader. The main thing I need is a notion of dynamic package availabilty so the bean or deployment can say: | org.jboss.xxx | | it could also be specialized as | | org.jboss.xxx,org.jboss.yyy | Then the bean is not attempted to be described (class analysed) until the package(s) is deployed. I achieved this in the prototype by making the classloader architecture register itself as KernelRegistryFactory for dependency checking. NOTE: The explicity demand is only intended for classes unknown to the BeanMetaData. i.e. it should be done automatically for the package of the bean class, etc. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867938#3867938 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867938 --- 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] Commented: (JBAS-1479) SFSB handle should use JNDI
[ http://jira.jboss.com/jira/browse/JBAS-1479?page=comments#action_12315810 ] Scott M Stark commented on JBAS-1479: - Just the use of the org.jboss.naming.NamingContextFactory fixes the tests. > SFSB handle should use JNDI > --- > > Key: JBAS-1479 > URL: http://jira.jboss.com/jira/browse/JBAS-1479 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > Assignee: Adrian Brock > Fix For: JBossAS-4.0.2RC1 > > > The SFSB handle should use jndi when doing getEJBObject. > The use of an invoker does not work, e.g. the jrmp invoker cannot reconnect > across server restarts. -- 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] [Design the new POJO MicroContainer] - VFS and ClassLoader interaction
After looking at some existing VFS libraries and thinking about how class
loading should be interacting with the VFS, I'm thinking a much simplified VFS
api and URI based class loader that uses the VFS is what is needed. The two
basic constructs are simply:
| package io;
|
| import java.net.URI;
| import java.util.List;
| import java.io.FileNotFoundException;
|
|
| /** Prototype for a read-only VFS where virtual files are represented by
URIs.
| * A VFS is a tree of URIs segmented into paths by URI protocol.
| *
| * @author [EMAIL PROTECTED]
| * @version $Revision: 1.2 $
| */
| public interface ReadOnlyVFS
| {
|/**
| * Locate a file in the VFS given its URI path.
| *
| * @param path - the absolute path to the virtual file
(file:/root/deploy/x.ear)
| * @return the matching VirtualFile
| * @throws FileNotFoundException throw if the path could not be resolved
| */
|public VirtualFile resolveFile(URI path)
| throws FileNotFoundException;
|
|/**
| * Locate a file in the VFS given a relative URI path and contexts in
| * the VFS to search from.
| *
| * @param path - a relative URI path (x.ear)
| * @param searchContexts - the absolute paths in the VFS of the contexts
to search from
| * @return the matching VirtualFile
| * @throws FileNotFoundException throw if the path could not be resolved
| */
|public VirtualFile resolveFile(String path, List searchContexts)
| throws FileNotFoundException;
|
|/**
| * Find all files in the VFS matching the relative URI path.
| * @param path - a relative URI path (x.ear)
| * @return A possibly empty list of matching files
| */
|public List resolveFiles(String path);
|/**
| * Locate all files in the VFS given a relative URI path and contexts in
| * the VFS to search from.
| *
| * @param path - a relative URI path (x.ear)
| * @param searchContexts - the absolute paths in the VFS of the contexts
to search from
| * @return A possibly empty list of matching files
| * @return A possibly empty list of matching files
| */
|public List resolveFiles(String path, List
searchContexts);
|
| }
|
|
| /*
| * JBoss, the OpenSource J2EE webOS
| *
| * Distributable under LGPL license.
| * See terms of license at gnu.org.
| */
| package io;
|
| import java.security.SecureClassLoader;
| import java.net.URL;
| import java.net.URI;
| import java.net.MalformedURLException;
| import java.util.Enumeration;
| import java.util.ArrayList;
| import java.util.Arrays;
| import java.util.Vector;
| import java.util.jar.JarFile;
| import java.util.jar.JarEntry;
| import java.io.IOException;
| import java.io.ByteArrayOutputStream;
| import java.io.InputStream;
|
| /** A class loader that obtains classes and resources from a VFS.
| *
| * @author [EMAIL PROTECTED]
| * @version $Revision:$
| */
| public class VFSClassLoader extends SecureClassLoader
| {
|/**
| * Create a class loader given a search path and VFS
| * @param uris - the paths from the VFS that make up the class loader
path
| * @param vfs - the VFS used to resolve and load classes and resources
| */
|public VFSClassLoader(URI[] uris, ReadOnlyVFS vfs)
|{
| ...
|}
|
|/**
| * Find and define the given java class
| *
| * @param name - the binary class name
| * @return the defined Class object
| * @throws ClassNotFoundException thrown if the class could not be found
| *or defined
| */
|protected Class findClass(String name) throws ClassNotFoundException
|{
| ...
|}
|
|/**
| * Search for the resource in the VFS contraining the search to the
| * class loader paths.
| * @param name - the resource name
| * @return the resource URL if found, null otherwise
| */
|public URL findResource(String name)
|{
| ...
|}
|
|/**
| * Search for the resource in the VFS contraining the search to the
| * class loader paths.
| * @param name - the resource name
| * @return A possibly empty enumeration of the matching resources
| */
|public Enumeration findResources(String name) throws IOException
|{
| ..
|}
| }
|
|
Some issues that are still not clear to me are:
1. As I see it the existing DomainClassLoader needs to be layered on top of the
VFS and could extend VFSClassLoader. Perhaps the DomainClassLoader should just
encompass the VFS.
2. One thing I want to get away from is the need to copy deployments. The two
big issues requiring this currently are buggy URLClassLoader behavior, and
nested jars. The first we can address with our own VFSClassLoader. The second
require
[JBoss-dev] jboss-4.0 build.404 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050225113208Lbuild.404 BUILD COMPLETE - build.404Date of build: 02/25/2005 11:32:08Time to build: 42 minutes 18 secondsLast changed: 02/25/2005 09:46:30Last log entry: JBAS-1362 - bin/shutdown reports -S to be the default option, it's -h Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.16.4.4modifiedanddserver/src/main/org/jboss/Shutdown.javaJBAS-1362 - bin/shutdown reports -S to be the default option, it's -h
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate
Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
permissions of the replaced delegate
Key: JBAS-1526
URL: http://jira.jboss.com/jira/browse/JBAS-1526
Project: JBoss Application Server
Type: Bug
Components: Security
Versions: JBossAS-4.0.1 SP1
Environment: -
Reporter: Roland R?z
Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the
permissions of the replaced delegate
According to the JACC specification all Permissions of a CodeSource or
ProtectionDomain should be returned. Currently these methods return only the
JACC Permissions, without the Permissions of the delegate class.
The JACC Specification states (http://java.sun.com/j2ee/javaacc/):
2.5 What a Provider Must Do
A replacement Policy object must assume responsibility for performing all
policy decisions within the JRE in which it is installed that are requested by
way of the Policy interface that it implements.
Example Implementation of DelegatingPolicy.getPermissions(x):
public PermissionCollection getPermissions(ProtectionDomain domain) {
PermissionCollection pc = super.getPermissions(domain);
PermissionCollection delegated =
delegate.getPermissions(domain);
for (Enumeration e = delegated.elements();
e.hasMoreElements();) {
Permission p = (Permission) e.nextElement();
pc.add(p);
}
return pc;
}
Regards,
Andrea
--
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: (JBAS-1521) build failed due to error in getServerSessionPool
[ http://jira.jboss.com/jira/browse/JBAS-1521?page=history ]
Adrian Brock closed JBAS-1521:
--
Resolution: Rejected
Not a subject for bug reports.
> build failed due to error in getServerSessionPool
> -
>
> Key: JBAS-1521
> URL: http://jira.jboss.com/jira/browse/JBAS-1521
> Project: JBoss Application Server
> Type: Patch
> Components: EJBs
> Reporter: Marcin Mieszek
> Priority: Blocker
>
>
> Build of module jboss-head failed due to:
> D:\jboss\jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\ConsumerContainer.java:560:
>
> getServerSessionPool(javax.jms.Destination,javax.jms.Connection,int,int,long,boolean,int,boolean,javax.jms.MessageListener)
> in org.jboss.jms.asf.ServerSessionPoolFactory cannot be applied to
> (javax.jms.Connection,int,int,int,boolean,int,boolean,javax.jms.MessageListener)
> pool = factory.getServerSessionPool(connection,
> config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
> isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
>^
> D:\jboss\jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\MDB.java:421:
> getServerSessionPool(javax.jms.Destination,javax.jms.Connection,int,int,long,boolean,int,boolean,javax.jms.MessageListener)
> in org.jboss.jms.asf.ServerSessionPoolFactory cannot be applied to
> (javax.jms.Connection,int,int,int,boolean,int,boolean,javax.jms.MessageListener)
> pool = factory.getServerSessionPool(connection,
> config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
> isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
>^
> I created a patch for
> jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\ConsumerContainer.java:
> --- cvs.java 2005-02-25 03:40:04.0 +0100
> +++ local.java2005-02-25 03:40:30.546875000 +0100
> @@ -373,7 +373,7 @@
> Method methodMessage = (Method) advisedMethods.get(hash);
>
> // set up the server session pool
> -ServerSessionPool serverSessionPool =
> createSessionPool(qConnection,
> +ServerSessionPool serverSessionPool = createSessionPool(queue,
> qConnection,
> true, //
> tx
>
> acknowledgeMode.ordinal(),
> listener,
> @@ -483,7 +483,7 @@
> Method methodMessage = (Method) advisedMethods.get(hash);
>
> // set up the server session pool
> -ServerSessionPool serverSessionPool =
> createSessionPool(tConnection,
> +ServerSessionPool serverSessionPool = createSessionPool(topic,
> tConnection,
> true, //
> tx
>
> acknowledgeMode.ordinal(),
> listener,
> @@ -522,10 +522,8 @@
> /**
> * Create a server session pool for the given connection.
> *
> +* @param destination The destination.
> * @param connection The connection to use.
> -* @param minSession The minumum number of sessions
> -* @param maxSession The maximum number of sessions.
> -* @param keepAliveThe time to keep sessions alive
> * @param isTransacted True if the sessions are transacted.
> * @param ack The session acknowledgement mode.
> * @param listener The message listener.
> @@ -534,7 +532,8 @@
> * @throws javax.naming.NamingException Description of Exception
> */
> protected ServerSessionPool
> - createSessionPool(final Connection connection,
> + createSessionPool(final Destination destination,
> + final Connection connection,
> final boolean isTransacted,
> int ack,
> final MessageListener listener,
> @@ -557,7 +556,7 @@
> boolean isNotSupportedTx = txType ==
> TransactionAttributeType.NOTSUPPORTED;
>
> // the create the pool
> - pool = factory.getServerSessionPool(connection,
> config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
> isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
> + pool = factory.getServerSessionPool(destination, connection,
> config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
> isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
>}
>finally
>{
> Patch for jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\MDB.java is:
> --- cvs.java 2005-02-25 03:47:14.453125000 +0100
> +++ local.java2005-0
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1479) SFSB handle should use JNDI
[ http://jira.jboss.com/jira/browse/JBAS-1479?page=comments#action_12315806 ] Adrian Brock commented on JBAS-1479: Does the two combinded fix the test? > SFSB handle should use JNDI > --- > > Key: JBAS-1479 > URL: http://jira.jboss.com/jira/browse/JBAS-1479 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > Assignee: Adrian Brock > Fix For: JBossAS-4.0.2RC1 > > > The SFSB handle should use jndi when doing getEJBObject. > The use of an invoker does not work, e.g. the jrmp invoker cannot reconnect > across server restarts. -- 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] Created: (JBAS-1525) Generalize the LdapLoginModule user and roles search mechanism
Generalize the LdapLoginModule user and roles search mechanism -- Key: JBAS-1525 URL: http://jira.jboss.com/jira/browse/JBAS-1525 Project: JBoss Application Server Type: Feature Request Components: Security Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-5.0 Alpha, JBossPOJOServer-1.0 Final Reporter: Scott M Stark There are 3 areas where the LdapLoginModule can be generalized to improve its utility across ldap schemas: 1. Allow the context for the user to be a search criteria that can be a function of the username rather than a specific context DN. 2. Allow the context for the roles to be a search criteria that can be a function of the username rather than a specific context DN. 3. Allow for a mapping from the ldap group to a role name so that the ldap server does not need to know application specific roles. -- 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] Created: (JBADMCON-94) Review feature set of existing web-console
Review feature set of existing web-console --- Key: JBADMCON-94 URL: http://jira.jboss.com/jira/browse/JBADMCON-94 Project: JBoss Admin Console Type: Feature Request Components: General Console Reporter: Charles Crouch This issue should be used to track particular features of the existing web-console which should be included in the new Admin Console. Please note any in the comments section. Additional tasks will be created in order to schedule the actual updates to the Admin Console. -- 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] [Design of JBoss Portal] - custom portlet page
using latest JBP from cvs, JB 4.01, mySQL I'm trying to view a custom portlet and can't seem to get the page to load. The reference shows that the URL for my page would be something like /portal/index.html?page=hello but the page=xxx syntax doesn't seem to work anymore (testing with page=forums or page=test). For instance, the forums URL is now /portal/index.html?_id=page.default.forums. I have my portlet in a war in the deploy directory. I think my -pages.xml is probably at fault here. Looks like this. googleportlet-pages.xml |default | | google | | GooglePortletWindow | google.GooglePortlet.GooglePortletInstance | true | left | 0 | | | | I'm not sure what the first part of instance-ref should be - i've tried several different variants with no luck. Can anyone help out on this one? thanks much. ... .joe View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867920#3867920 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867920 --- 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-Bugs-1151858 ] Cannot type characters '}' and ']'
Bugs item #1151858, was opened at 2005-02-25 16:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1151858&group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Phaiax (phaiax) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot type characters '}' and ']' Initial Comment: I'm running Eclipse 3.0.1 and JBoss-IDE 1.4.1-e30. As soon as JBoss-IDE plugin and features folders are installed, I cannot type the characters '}' and ']' (AltGr+0 and AltGr+9 on a german keyboard) in any Eclipse editor. All other characters work fine. After uninstalling JBoss-IDE, the problem's gone. I tried it also with a perfectly new eclipse installation. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1151858&group_id=22866 --- 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.837 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050225103614Lbuild.837 BUILD COMPLETE - build.837Date of build: 02/25/2005 10:36:14Time to build: 20 minutes 48 secondsLast changed: 02/25/2005 09:47:14Last log entry: JBAS-1362 - bin/shutdown reports -S to be the default option, it's -h Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.20modifiedanddserver/src/main/org/jboss/Shutdown.javaJBAS-1362 - bin/shutdown reports -S to be the default option, it's -h1.3modifiedbelabancache/src/main/org/jboss/cache/loader/RpcDelegatingCacheLoader.javans1.15modifiedbelabancache/src/main/org/jboss/cache/interceptors/CreateIfNotExistsInterceptor.javans1.2modifiedbelabancache/src/main/org/jboss/cache/tests/RpcDelegatingCacheLoaderTests.javans
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1524) SessionSynchronisation.beforeCompletion deferred/missing with BMT
[ http://jira.jboss.com/jira/browse/JBAS-1524?page=history ] C. Berger updated JBAS-1524: Description: We have a stateful SessionBean implementing the SessionSynchronisation-Interface. The transaction is managed by the client (or alternatively another SessionBean) using the UserTransaction. The call to beforeCompletion() does not come when expected, after the UserTransaction has been rolled back (and before afterCompletion()), but when the bean is removed. As a side effect our cleanup code in beforeCompletion is not called properly, so we get a warning about an unclosed connection as you can see in the log snippet: 14:16:52,710 lookup user transaction... (Client) 14:16:52,801 open transaction... (Client) 14:16:52,871 call openConnection()... (Client) 14:16:52,881 INFO [STDOUT] afterBegin 14:16:52,881 INFO [STDOUT] openConnection: open connection... 14:16:53,882 rollback transaction... (Client) <--- beforeCompletion() expected! 14:16:53,882 INFO [STDOUT] afterCompletion 14:16:53,882 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: [EMAIL PROTECTED] 14:16:54,894 remove bean... (Client) 14:16:54,894 INFO [STDOUT] afterBegin 14:16:54,894 INFO [STDOUT] ejbRemove: connection is open! 14:16:54,894 INFO [STDOUT] beforeCompletion 14:16:54,894 INFO [STDOUT] beforeCompletion: closing connection... 14:16:54,894 INFO [STDOUT] afterCompletion A small, reproducible test case is attached, you might just adjust the DataSource in the jboss.xml. Best Regards C. Berger was: We have a stateful SessionBean implementing the SessionSynchronisation-Interface. The transaction is managed by the client (or alternatively another SessionBean) using the UserTransaction. The call to beforeCompletion() does not come when expected, after the UserTransaction has been rolled back (and before afterCompletion()), but when the bean is removed. As a side effect our cleanup code in beforeCompletion is not called properly, so we get a warning about an unclosed connection as you can see in the log snippet: 14:16:52,710 lookup user transaction... (Client) 14:16:52,801 open transaction... (Client) 14:16:52,871 call openConnection()... (Client) 14:16:52,881 INFO [STDOUT] afterBegin 14:16:52,881 INFO [STDOUT] openConnection: open connection... 14:16:53,882 rollback transaction... (Client) <--- beforeCompletion() expected! 14:16:53,882 INFO [STDOUT] afterCompletion 14:16:53,882 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: [EMAIL PROTECTED] 14:16:54,894 remove bean... (Client) 14:16:54,894 INFO [STDOUT] afterBegin 14:16:54,894 INFO [STDOUT] ejbRemove: connection is open! 14:16:54,894 INFO [STDOUT] beforeCompletion 14:16:54,894 INFO [STDOUT] beforeCompletion: closing connection... 14:16:54,894 INFO [STDOUT] afterCompletion A small, reproducible test case is available if needed. Best Regards C. Berger > SessionSynchronisation.beforeCompletion deferred/missing with BMT > - > > Key: JBAS-1524 > URL: http://jira.jboss.com/jira/browse/JBAS-1524 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, > JBossAS-3.2.6 Final > Environment: Windows 2000 SP 4 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) > Reporter: C. Berger > Priority: Minor > Attachments: RemoveProblem.jar > > > We have a stateful SessionBean implementing the > SessionSynchronisation-Interface. The transaction is managed by the client > (or alternatively another SessionBean) using the UserTransaction. > The call to beforeCompletion() does not come when expected, after the > UserTransaction has been rolled back (and before afterCompletion()), but when > the bean is removed. As a side effect our cleanup code in beforeCompletion is > not called properly, so we get a warning about an unclosed connection as you > can see in the log snippet: > 14:16:52,710 lookup user transaction... (Client) > 14:16:52,801 open transaction... (Client) > 14:16:52,871 call openConnection()... (Client) > 14:16:52,881 INFO [STDOUT] afterBegin > 14:16:52,881 INFO [STDOUT] openConnection: open connection... > 14:16:53,882 rollback transaction... (Client) > <--- beforeCompletion() expected! > 14:16:53,882 INFO [STDOUT] afterCompletion > 14:16:53,882 INFO [CachedConnectionManager] Closing a connection for you. > Please close them yourself: [EMAIL PROTECTED] > 14:16:54,894 remove bean... (Client) > 14:16:54,894 INFO [STDOUT] afterBegin > 14:16:54,894 INFO [STDOUT] ejbRemove: connection is open! > 14:16:54,894 INFO [STDOUT] beforeCompletion > 14:16:54,894 INFO [STDOUT] beforeCompletion: closing connection... > 14:16:54,894 INFO [STDOUT] afterCompletion > A small, reproducible test case is attached, you might just adjust the > Data
[JBoss-dev] [JBoss JIRA] Reopened: (JBADMCON-91) 'isSameRMValue' always gets set to true or false
[ http://jira.jboss.com/jira/browse/JBADMCON-91?page=history ] Charles Crouch reopened JBADMCON-91: Assign To: (was: Dimitris Andreadis) This is not a problem with the DeploymentService. Rather it is an issue with having sameRMValue as a boolean on the DataSource and DataSourceForm classes rather than a Boolean and String respectively. > 'isSameRMValue' always gets set to true or false > -- > > Key: JBADMCON-91 > URL: http://jira.jboss.com/jira/browse/JBADMCON-91 > Project: JBoss Admin Console > Type: Bug > Components: DataSource > Versions: 1.0 alpha > Reporter: Charles Crouch > Fix For: 1.1 alpha > > Original Estimate: 4 hours >Time Spent: 15 minutes > Remaining: 3 hours, 45 minutes > > The 'isSameRMValue' property for an XA DataSource is always being set to > either true or false, there is no way to leave it unspecified. -- 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] [Design the new POJO MicroContainer] - Re: Boston meeting notes: Two phase join point factory const
Yes, The intention is that if the user of ClassAdapter wants to override at the instance level it will do the following: // Get a class level adapter (one per class) and its info ClassAdapter classLevelAdapter = classAdapterFactory(myClass); ClassInfo classLevelInfo = classLevelAdapter.getClassInfo(); // Override annotations (if required) and get an instance adapter ClassInfo overrideInfo = (ClassInfo) classLevelInfo.clone(); overrideAnnotations(overrideInfo); ClassAdapter instanceAdapter = classLevelAdapter.getInstanceAdapter(overrideInfo); // After class can be loaded (this might be what forces the actual class load) JoinpointFactory jpf = instanceAdapter (or classLevelAdapter).getJoinPointFactory(); If it is not clear in the javadoc of ClassAdapter, please fix it. If you want to change it, please feel free. We discussed the classes and how they fit in the scheme, but we didn't discuss the exact methods a client uses to get an instance adapter with overridden annotations. This seemed like the most logical solution to me? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867922#3867922 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867922 --- 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: (JBIDE-129) Cannot type characters '}' and ']'
Cannot type characters '}' and ']' -- Key: JBIDE-129 URL: http://jira.jboss.com/jira/browse/JBIDE-129 Project: JBoss IDE Type: Bug Environment: Windows XP 5.1.2600 SP2, Eclipse 3.0.1, JRE 1.4.2 Reporter: Frank Heinbach Assigned to: Marshall Culpepper I'm running Eclipse 3.0.1 and JBoss-IDE 1.4.1-e30. As soon as JBoss-IDE plugin and features folders are installed, I cannot type the characters '}' and ']' (AltGr+0 and AltGr+9 on a german keyboard) in any Eclipse editor. All other characters work fine. After uninstalling JBoss-IDE, the problem's gone. I tried it also with a perfectly new eclipse installation. -- 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] [Design of JBoss Portal] - Re: custom portlet page
You should be able to access it via: /portal/index.html?_id=page.default.google Make sure you have the following in jboss-portlet.xml: | |google | | If you are having troubles, send me your war file and i will look at it View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867924#3867924 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867924 --- 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: (JBADMCON-95) Integrate Admin Console into automated build
Integrate Admin Console into automated build Key: JBADMCON-95 URL: http://jira.jboss.com/jira/browse/JBADMCON-95 Project: JBoss Admin Console Type: Task Components: General Console Versions: 1.1 alpha Reporter: Charles Crouch Fix For: 1.1 alpha There are two specific areas of integration: -Ensuring that the Admin Console gets included in the automated JBoss AS build. -Ensuring that the Admin Console unit and integration tests are included into the automated testing of JBoss AS -- 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] Created: (JBAOP-96) TxPropagationInterceptor doesn't disassociate thread
TxPropagationInterceptor doesn't disassociate thread Key: JBAOP-96 URL: http://jira.jboss.com/jira/browse/JBAOP-96 Project: JBoss AOP Type: Bug Components: Aspect Library Versions: 1.1 Reporter: Bill Burke Fix For: 1.1.1 The TxPropagationInterceptor needs to suspend the TX (dissassociate it from the thread) if the tx was imported. Otherwise, the thread is never disassociated from the transaction and the transaction is leaked. -- 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: Interceptors, Cache Loaders
I guess it depends on what you want to do: from an application developer's view, TreeCache and TreeCacheAop are the only classes he will most probably ever use, everything else is configured through XML. We plan on extracting an interface 'JBossCache' from the 2 classes above and have app developers simply program against this interface. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867835#3867835 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867835 --- 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] Commented: (JBAS-1479) SFSB handle should use JNDI
[ http://jira.jboss.com/jira/browse/JBAS-1479?page=comments#action_12315790 ] Scott M Stark commented on JBAS-1479: - You don't get full backward compatibility with the org.jboss.ejb.sfsb.handle.V327 system property because the invoker is not used. The testBMTSessionHandleNoDefaultJNDI and testSessionHandleNoDefaultJNDI tests of the org.jboss.test.cts.test.StatefulSessionUnitTestCase are failing even with org.jboss.ejb.sfsb.handle.V327 set because they are expecting that the InitialContext that was in effect when the handle was created. To achieve this with the updated StatefulHandleImpl requires one to use the org.jboss.naming.NamingContextFactory as the JNDI Context.INITIAL_CONTEXT_FACTORY value. This factory saves its environment in a thread local that is used by the StatefulHandleImpl. > SFSB handle should use JNDI > --- > > Key: JBAS-1479 > URL: http://jira.jboss.com/jira/browse/JBAS-1479 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Adrian Brock > Assignee: Adrian Brock > Fix For: JBossAS-4.0.2RC1 > > > The SFSB handle should use jndi when doing getEJBObject. > The use of an invoker does not work, e.g. the jrmp invoker cannot reconnect > across server restarts. -- 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: (JBPM-54) complete xml support for specific set of nodes
[ http://jira.jboss.com/jira/browse/JBPM-54?page=history ] Tom Baeyens updated JBPM-54: Fix Version: 3.0 alpha 2 > complete xml support for specific set of nodes > -- > > Key: JBPM-54 > URL: http://jira.jboss.com/jira/browse/JBPM-54 > Project: JBoss jBPM > Type: Sub-task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Critical > Fix For: 3.0 alpha 2 > > > xml parsing is further progressed then now xml serialization. > first select a subset of nodes, then make sure that both parsing and > serialization works for those nodes. including the specific node-type > configurations. -- 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: (JBPM-78) Fault and Termination Handling
[ http://jira.jboss.com/jira/browse/JBPM-78?page=history ] Juan Cantu updated JBPM-78: --- Description: -Implement the state transitions for scope instances when cancel or faulted signals are received -Provide the fault catching logic Environment: Original Estimate: 57600 Remaining Estimate: 57600 Version: 3.0 alpha 1 Component: BPEL > Fault and Termination Handling > -- > > Key: JBPM-78 > URL: http://jira.jboss.com/jira/browse/JBPM-78 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: 3.0 alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 2 days > Remaining: 2 days > > -Implement the state transitions for scope instances when cancel or faulted > signals are received > -Provide the fault catching logic -- 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: (JBAS-1519) CMR deletion problems with 2 CMR's and one is batch-cascade-delete
[ http://jira.jboss.com/jira/browse/JBAS-1519?page=history ] Alexey Loubyansky reassigned JBAS-1519: --- Assign To: Alexey Loubyansky > CMR deletion problems with 2 CMR's and one is batch-cascade-delete > -- > > Key: JBAS-1519 > URL: http://jira.jboss.com/jira/browse/JBAS-1519 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Windows XP, Java 1.4.2_06 > Reporter: Ian > Assignee: Alexey Loubyansky > Attachments: CMPBug.zip > > > When you have 3 beans (A, B, and C). A has a 1-1 mandatory relationship with > B, with B having a non-nullable foreign key in A. A has a 1-many relationship > with C, and C is marked for cascade-delete. The problem occurs when you > populate A (which means B must be populated), and C is populated with > references to A. Then you delete A. > From the trace, you can see that the batch-cascade-delete work is deferred on > relationship C. Then it attempts to set the foreign key field of B to null in > A - which is not allowed, and a database constraint is activated. > If you remove the relationship from A to C, everything is fine. If you don't > populate C, everything is fine. > I have included two portions of traces from the log files. > This portion of the log file occurs when C is populated (deleting A): > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.A] RESET PERSISTENCE > CONTEXT: id=[.1.] > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] load data: entity=A > pk=[.1.] > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] No preload data found: > entity=A pk=[.1.] > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.A] Default eager-load > for entity: readahead=null > 2005-02-25 09:53:10,772 DEBUG > [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.A] Executing SQL: > SELECT fk_B FROM A_TABLE WHERE (pk_A=?) > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.A#pkA] param: > i=1, type=INTEGER, value=1 > 2005-02-25 09:53:10,772 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.A#fkB] result: > i=1, type=java.lang.Integer, value=1000 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.A.c] Read ahead > cahce load: cmrField=c pk=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] load data: entity=A > pk=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.A] No preload data found: > entity=A pk=[.1.] > 2005-02-25 09:53:10,782 DEBUG > [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand.A] load relation SQL: > SELECT pk_C FROM C_TABLE WHERE (fk_A=?) > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.C#pkA] param: > i=1, type=INTEGER, value=1 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.C#pkC] result: > i=1, type=java.lang.Integer, value=1 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Add preload data: entity=C > pk=[.1.] field=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBridge.C#pkC] result: > i=1, type=java.lang.Integer, value=2 > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Add preload data: entity=C > pk=[.2.] field=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Add finder results: > entity=C results=[[.1.], [.2.]] readahead=[JDBCReadAheadMetaData : > strategy=on-load, pageSize=1000, eagerLoadGroup=*, left-join[]] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.C] RESET PERSISTENCE > CONTEXT: id=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] load data: entity=C > pk=[.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Preloading data: entity=C > pk=[.1.] cmrField=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.C] Scheduled for > batch-cascade-delete: [.1.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.C] RESET PERSISTENCE > CONTEXT: id=[.2.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] load data: entity=C > pk=[.2.] > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.ReadAheadCache.C] Preloading data: entity=C > pk=[.2.] cmrField=a > 2005-02-25 09:53:10,782 TRACE > [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.C] Scheduled for > batch-cascade-delete: [.2.] > 200
[JBoss-dev] [Design of JBoss Portal] - Re: Portal Build
But jboss-portal-2.0 is up to date? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867783#3867783 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867783 --- 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: (JBAS-1520) patched references to missing field DEFAULT_PARTITION in org.jboss.metadata.ClusterConfigMetaData
[ http://jira.jboss.com/jira/browse/JBAS-1520?page=history ] Scott M Stark closed JBAS-1520: --- Resolution: Duplicate Issue > patched references to missing field DEFAULT_PARTITION in > org.jboss.metadata.ClusterConfigMetaData > - > > Key: JBAS-1520 > URL: http://jira.jboss.com/jira/browse/JBAS-1520 > Project: JBoss Application Server > Type: Patch > Components: Clustering > Reporter: Marcin Mieszek > Assignee: Adrian Brock > Priority: Blocker > > > This is the first time I submit anything here.. so please be patient to me :) > Module jboss-head failed to compile as in 1.7.6.1 version of > org.jboss.metadata.ClusterConfigMetaData constant: > public final static String DEFAULT_PARTITION = "DefaultPartition"; > was replaced with default partition logic in > org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: > public static String getDefaultPartitionName() > However, there are still references to DEFAULT_PARTITION in files: > 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at > line 54: > protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^^ > I suggest changing to: > protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); > 2. org.jboss.ha.framework.server.ClusterPartition cvs version 1.36 at line 54: > protected String partitionName = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^^ > I suggest changing to: > protected String partitionName = > org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); > Below are build errors: > D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\framework\server\ClusterPartition.java:54: > cannot find symbol > symbol : variable DEFAULT_PARTITION > location: class org.jboss.metadata.ClusterConfigMetaData >protected String partitionName = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > ^ > D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\hasessionstate\server\HASessionStateImpl.java:54: > cannot find symbol > symbol : variable DEFAULT_PARTITION > location: class org.jboss.metadata.ClusterConfigMetaData >protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^ > I hope it may be useful and the format of my message is readable and this is > the right place to post this piece of information. > Best regards, > Marcin Mieszek -- 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] Resolved: (JBCACHE-36) Run testsuite on multi-CPU boxes in ATL lab
[ http://jira.jboss.com/jira/browse/JBCACHE-36?page=history ] Bela Ban resolved JBCACHE-36: - Resolution: Done all tests except TxDeadlockUnitTest (as expected) pass > Run testsuite on multi-CPU boxes in ATL lab > --- > > Key: JBCACHE-36 > URL: http://jira.jboss.com/jira/browse/JBCACHE-36 > Project: JBoss Cache > Type: Task > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.1 > > > to detect concurrency issues -- 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-3.2 build.301 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050224072023Lbuild.301 BUILD COMPLETE - build.301Date of build: 02/24/2005 07:20:23Time to build: 14 minutes 56 secondsLast changed: 02/24/2005 07:02:40Last log entry: moved encodeFileName() / decodeFileName() methods to org.jboss.util.file.Files to be re-used by other modules Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.1.2.3modifiedanddsystem/src/main/org/jboss/system/pm/XMLAttributePersistenceManager.javamoved encodeFileName() / decodeFileName() methods to org.jboss.util.file.Files to be re-used by other modules
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1286) EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException
[ http://jira.jboss.com/jira/browse/JBAS-1286?page=history ] Frank Merenda reopened JBAS-1286: - Assign To: Adrian Brock (was: Scott M Stark) Adrian, Please see my comments in the original post. I re-deploy both the .ear AND the .war, and I still get the Class Cast Exception. There are no other applications running on the machine using my classes. > This is repeatable 100% of the time. If I restart the app server it works > correctly again. If I just re-touch both the .ear and the .war I will still > get the CCE. > EJB3 .ear file and hot deploy of .war file cause java.lang.ClassCastException > - > > Key: JBAS-1286 > URL: http://jira.jboss.com/jira/browse/JBAS-1286 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1RC1 > Environment: Linux, 2.6.9 kernel. jdk build 1.5.0-b64. JBoss 4.0.1RC1. EJB > Preview 2. > Reporter: Frank Merenda > Assignee: Adrian Brock > Priority: Minor > > > If I have a EJB 3 SLSB deployed in an .ear file, and I create a separate .war > file (not in the ear file) to access that SLSB it works fine upon server > startup. If I touch the .ear file everything still works fine. If I touch the > .war file, I get a ClassCastException: > java.lang.ClassCastException: $Proxy76 > at > org.jboss.jbossnetwork.pushportal.business.ApplicationFacade.login(ApplicationFacade.java:23) > at > I am referencing the SLSB from the war file with the following code: > InitialContext ctx = new InitialContext(); > Login login = (Login) ctx.lookup(LoginRemote.class.getName()); > It is blowing up on the second line. > This is repeatable 100% of the time. If I restart the app server it works > correctly again. If I just re-touch both the .ear and the .war I will still > get the CCE. > I was not sure if this goes into the EJB3 or the JBoss AS project. There were > other ClassCastExceptions in the AS project, so I put it in here. > I've attached the .war and .ear file. You can deploy them in JBoss 4.0.1RC2 > with EJB3 set up. (update if no attachment, email me at [EMAIL PROTECTED] and > I will send them. I don't see an attach on the bug request). I will try to > add it after I file the bug. > Steps to repeat: > 1) deploy war and ear files. > 2) go to http://localhost:8080/jbosspush/login.html > 3) type in any 4 letters for the username and password. You are sent to the > main page. > 4) touch jboss-4.0.1RC1/server/all/deploy/jbosspush.war. Wait for hot deploy. > 5) go to http://localhost:8080/jbosspush/login.html > 6) type in any 4 letters for the username and password. You are sent to > placeholder error page. Trace is in the log. > 7) restart jboss server > 8) repeat steps 1-3. Everything works. -- 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] Reopened: (JBAS-1520) patched references to missing field DEFAULT_PARTITION in org.jboss.metadata.ClusterConfigMetaData
[ http://jira.jboss.com/jira/browse/JBAS-1520?page=history ] Scott M Stark reopened JBAS-1520: - Assign To: Adrian Brock The comment here applies to JBAS-1521. This issue is actually a duplicate of JBAS-1501 and will be closed as such. > patched references to missing field DEFAULT_PARTITION in > org.jboss.metadata.ClusterConfigMetaData > - > > Key: JBAS-1520 > URL: http://jira.jboss.com/jira/browse/JBAS-1520 > Project: JBoss Application Server > Type: Patch > Components: Clustering > Reporter: Marcin Mieszek > Assignee: Adrian Brock > Priority: Blocker > > > This is the first time I submit anything here.. so please be patient to me :) > Module jboss-head failed to compile as in 1.7.6.1 version of > org.jboss.metadata.ClusterConfigMetaData constant: > public final static String DEFAULT_PARTITION = "DefaultPartition"; > was replaced with default partition logic in > org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: > public static String getDefaultPartitionName() > However, there are still references to DEFAULT_PARTITION in files: > 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at > line 54: > protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^^ > I suggest changing to: > protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); > 2. org.jboss.ha.framework.server.ClusterPartition cvs version 1.36 at line 54: > protected String partitionName = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^^ > I suggest changing to: > protected String partitionName = > org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); > Below are build errors: > D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\framework\server\ClusterPartition.java:54: > cannot find symbol > symbol : variable DEFAULT_PARTITION > location: class org.jboss.metadata.ClusterConfigMetaData >protected String partitionName = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > ^ > D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\hasessionstate\server\HASessionStateImpl.java:54: > cannot find symbol > symbol : variable DEFAULT_PARTITION > location: class org.jboss.metadata.ClusterConfigMetaData >protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^ > I hope it may be useful and the format of my message is readable and this is > the right place to post this piece of information. > Best regards, > Marcin Mieszek -- 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: (JBAS-1520) patched references to missing field DEFAULT_PARTITION in org.jboss.metadata.ClusterConfigMetaData
[ http://jira.jboss.com/jira/browse/JBAS-1520?page=history ] Adrian Brock closed JBAS-1520: -- Resolution: Rejected Please don't post bug reports on CVS won't compile. We have cruisecontrol to trap this problem. e.g. http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0 Anyway, you probably just caught it in the middle of a cvs commit. Resync with cvs. Also it is not for you to decide priorities, but you can vote. > patched references to missing field DEFAULT_PARTITION in > org.jboss.metadata.ClusterConfigMetaData > - > > Key: JBAS-1520 > URL: http://jira.jboss.com/jira/browse/JBAS-1520 > Project: JBoss Application Server > Type: Patch > Components: Clustering > Reporter: Marcin Mieszek > Priority: Blocker > > > This is the first time I submit anything here.. so please be patient to me :) > Module jboss-head failed to compile as in 1.7.6.1 version of > org.jboss.metadata.ClusterConfigMetaData constant: > public final static String DEFAULT_PARTITION = "DefaultPartition"; > was replaced with default partition logic in > org.jboss.system.server.ServerConfigUtil cvs version 1.3 with method: > public static String getDefaultPartitionName() > However, there are still references to DEFAULT_PARTITION in files: > 1. org.jboss.ha.hasessionstate.server.HASessionStateImpl cvs version 1.15 at > line 54: > protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^^ > I suggest changing to: > protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); > 2. org.jboss.ha.framework.server.ClusterPartition cvs version 1.36 at line 54: > protected String partitionName = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^^ > I suggest changing to: > protected String partitionName = > org.jboss.system.server.ServerConfigUtil.getDefaultPartitionName(); > Below are build errors: > D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\framework\server\ClusterPartition.java:54: > cannot find symbol > symbol : variable DEFAULT_PARTITION > location: class org.jboss.metadata.ClusterConfigMetaData >protected String partitionName = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > ^ > D:\jboss\jboss-head\cluster\src\main\org\jboss\ha\hasessionstate\server\HASessionStateImpl.java:54: > cannot find symbol > symbol : variable DEFAULT_PARTITION > location: class org.jboss.metadata.ClusterConfigMetaData >protected final String DEFAULT_PARTITION_JNDI_NAME = > org.jboss.metadata.ClusterConfigMetaData.DEFAULT_PARTITION; > > ^ > I hope it may be useful and the format of my message is readable and this is > the right place to post this piece of information. > Best regards, > Marcin Mieszek -- 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] - TreeCache's ClusterConfig attribute
In the JBossCache tutorial it lists a deployment descriptor used to configure the TreeCache MBean, and in this file there's a section where a clustering configuration is specified. This looks to be the same as what is specified in the PartitionConfig attribute in the cluster-service.xml. Does a TreeCache have its own cluster setup, or is this redundant when using the Treecache in a clustered deployment ? If it has its own clustering setup then how should this differ from what is configured in cluster-service.xml (possible conflicts between the two) ? Is there a cluster of servers and a separate but somehow related cluster of TreeCache services ? Thanks in advance for any explanations. --James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867918#3867918 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867918 --- 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 JBoss Portal] - Re: JBossPortal and AOP
good to hear that, I plan to use AOP for some stuff soon in jboss portal :-) for the login : what do you want to do exactly ? login in your application or login of jboss portal ? I read that you have system integration purpose, in that case you should use a JAAS login module to plug your own authentication. We can give you pointers that explains that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867747#3867747 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867747 --- 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: (JBAS-1524) SessionSynchronisation.beforeCompletion deferred/missing with BMT
[ http://jira.jboss.com/jira/browse/JBAS-1524?page=history ] Adrian Brock closed JBAS-1524: -- Resolution: Rejected beforeSynchronization is not invoked on a rollback. > SessionSynchronisation.beforeCompletion deferred/missing with BMT > - > > Key: JBAS-1524 > URL: http://jira.jboss.com/jira/browse/JBAS-1524 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, > JBossAS-3.2.6 Final > Environment: Windows 2000 SP 4 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) > Reporter: C. Berger > Priority: Minor > Attachments: RemoveProblem.jar > > > We have a stateful SessionBean implementing the > SessionSynchronisation-Interface. The transaction is managed by the client > (or alternatively another SessionBean) using the UserTransaction. > The call to beforeCompletion() does not come when expected, after the > UserTransaction has been rolled back (and before afterCompletion()), but when > the bean is removed. As a side effect our cleanup code in beforeCompletion is > not called properly, so we get a warning about an unclosed connection as you > can see in the log snippet: > 14:16:52,710 lookup user transaction... (Client) > 14:16:52,801 open transaction... (Client) > 14:16:52,871 call openConnection()... (Client) > 14:16:52,881 INFO [STDOUT] afterBegin > 14:16:52,881 INFO [STDOUT] openConnection: open connection... > 14:16:53,882 rollback transaction... (Client) > <--- beforeCompletion() expected! > 14:16:53,882 INFO [STDOUT] afterCompletion > 14:16:53,882 INFO [CachedConnectionManager] Closing a connection for you. > Please close them yourself: [EMAIL PROTECTED] > 14:16:54,894 remove bean... (Client) > 14:16:54,894 INFO [STDOUT] afterBegin > 14:16:54,894 INFO [STDOUT] ejbRemove: connection is open! > 14:16:54,894 INFO [STDOUT] beforeCompletion > 14:16:54,894 INFO [STDOUT] beforeCompletion: closing connection... > 14:16:54,894 INFO [STDOUT] afterCompletion > A small, reproducible test case is attached, you might just adjust the > DataSource in the jboss.xml. > Best Regards > C. Berger -- 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] [Design of JBoss Portal] - Re: JBossPortal and AOP
Ok, that is a bit complicated: The other system does not work on JBoss4, but still on JBoss 3.0.8. It has an login-method that need username and password as parameters and it is accessed via RMI. All output that is produced simply appears on the JBoss-console. That is absolutely enough for my purposes. That why, I simply want to receive a positive or negative value for the login on JBoss Portal and then simply say "login successful". View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867755#3867755 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867755 --- 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: (JBAS-1522) HttpNamingContextFactory fails due to system property read when under a security manager
[ http://jira.jboss.com/jira/browse/JBAS-1522?page=history ] Scott M Stark reassigned JBAS-1522: --- Assign To: Scott M Stark > HttpNamingContextFactory fails due to system property read when under a > security manager > > > Key: JBAS-1522 > URL: http://jira.jboss.com/jira/browse/JBAS-1522 > Project: JBoss Application Server > Type: Bug > Components: Naming > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final > Reporter: Scott M Stark > Assignee: Scott M Stark > Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final > > > Running under a security manager with the > org.jboss.naming.HttpNamingContextFactory can result in the following failure > due to the property access not being in a privileged block. The failure > should also be ignored since its an optional override setting. > java.lang.ExceptionInInitializerError > at > org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:106) > at > org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:65) > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243) > at javax.naming.InitialContext.init(InitialContext.java:219) > at javax.naming.InitialContext.(InitialContext.java:195) > at com.nineci.applet.HelloBeanApplet.start(HelloBeanApplet.java:31) > at sun.applet.AppletPanel.run(AppletPanel.java:377) > at java.lang.Thread.run(Thread.java:534) > Caused by: java.security.AccessControlException: access denied > (java.util.PropertyPermission > org.jboss.security.httpInvoker.sslSocketFactoryBuilder read) > at > java.security.AccessControlContext.checkPermission(AccessControlContext.java:269) > at java.security.AccessController.checkPermission(AccessController.java:401) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:524) > at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1276) > at java.lang.System.getProperty(System.java:573) > at org.jboss.invocation.http.interfaces.Util.(Util.java:76) > ... 9 more -- 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] [TODO -- DEVELOPMENT] - Re: Automatized Converting Application (.ear file) from Sun
Balint, I am interested in something similar.can you pls give me your contact details.. Thanks, ravi View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867813#3867813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867813 --- 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 JBoss Portal] - WSRP support
Is Portal 2.0 a WSRP producer and consumer? If so how is this comfigured? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867803#3867803 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867803 --- 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-4.0 build.401 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050225041838Lbuild.401 BUILD COMPLETE - build.401Date of build: 02/25/2005 04:18:38Time to build: 22 minutes 35 secondsLast changed: 02/25/2005 04:07:08Last log entry: #JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-2005 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (5)1.29.2.3modifiedanddthirdparty/jacorb-jacorb/lib/jacorb.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.8.4.2modifiedanddthirdparty/jacorb-jacorb/lib/idl.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.5.4.2modifiedanddthirdparty/jacorb-jacorb/lib/idl_g.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.24.2.3modifiedanddthirdparty/jacorb-jacorb/lib/README#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-20051.2.2.5modifiedanddthirdparty/licenses/thirdparty-licenses.xml#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-2005
[JBoss-dev] [JBoss JIRA] Resolved: (JBREM-37) backport to 4.0 branch before 1.0.1 final release
[ http://jira.jboss.com/jira/browse/JBREM-37?page=history ] Tom Elrod resolved JBREM-37: - Resolution: Done Code from remoting 1.0.1 final has been backported. Only possible changed between now and release will be samples and doc (user guide and release notes). > backport to 4.0 branch before 1.0.1 final release > - > > Key: JBREM-37 > URL: http://jira.jboss.com/jira/browse/JBREM-37 > Project: JBoss Remoting > Type: Task > Components: general > Versions: 1.0.1 beta > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.0.1 final > > > Need to make sure get everything from final release backported to the 4.0 > branch. -- 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] [Design of JBoss Portal] - Re: Portal Build
It is the latest thing. See other related posts. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867785#3867785 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867785 --- 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-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases -- Key: JBCACHE-98 URL: http://jira.jboss.com/jira/browse/JBCACHE-98 Project: JBoss Cache Type: Support Patch Versions: 1.2 Environment: should work in any environment Reporter: Luc Texier Assigned to: Bela Ban Fix For: 1.2.2 Some customers have expressed the wish to take avantages of the optimizations/bug fixes/enhancements being implemented in the latest releases of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 and JBossAS 4.0.1. -- 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: (JBPM-53) make the logs complete
[ http://jira.jboss.com/jira/browse/JBPM-53?page=history ] Tom Baeyens closed JBPM-53: --- Resolution: Done > make the logs complete > -- > > Key: JBPM-53 > URL: http://jira.jboss.com/jira/browse/JBPM-53 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > > the basic logging structure is in place. making the logs complete means that > we log *every* change in the executional data. we should try to accomplish > this without having too much logs. that is the optimisation that this task > is all about. > this feature will be necessary for building the undo feature later on. > also related to this are the compensation actions in case of exceptions. > this task is also related to the aop-mechanism. -- 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: (JBAS-1362) bin/shutdown reports -S to be the default option
[ http://jira.jboss.com/jira/browse/JBAS-1362?page=history ] Dimitris Andreadis closed JBAS-1362: Resolution: Done Fix Version: JBossAS-4.0.2RC1 JBossAS-5.0 Alpha JBossAS-3.2.8 Final > bin/shutdown reports -S to be the default option > > > Key: JBAS-1362 > URL: http://jira.jboss.com/jira/browse/JBAS-1362 > Project: JBoss Application Server > Type: Bug > Components: JMX > Versions: JBossAS-4.0.1 Final > Reporter: Dimitris Andreadis > Assignee: Dimitris Andreadis > Priority: Trivial > Fix For: JBossAS-4.0.2RC1, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final > > > bin/shutdown reports -S to be the default option, but it requires it to > perform the actual shutdown. Default is probably -h -- 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] [Design of JBoss Portal] - Swing based Potal
We have a Swing based application. We need to manage (CRUD) files (Word docs, images etc) which may be exteded across many sites. Is JBoss Portal the right product for achieving this? Is writing the swing front-end and incorporating it in our application a feasible task? Any help and suggestion is appreciated. Nasser View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867880#3867880 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867880 --- 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: (JBADMCON-59) Port DeploymentService updates to Branch_4_0
[ http://jira.jboss.com/jira/browse/JBADMCON-59?page=history ] Dimitris Andreadis closed JBADMCON-59: -- Resolution: Done It should work like it does in head, I verified it using the testsuite which has been ported, too. The only difference with HEAD are due to JBossXB not being fully synchronized between 4.0 and HEAD I don't understand the comment about which jars, to copy, etc. > Port DeploymentService updates to Branch_4_0 > > > Key: JBADMCON-59 > URL: http://jira.jboss.com/jira/browse/JBADMCON-59 > Project: JBoss Admin Console > Type: Patch > Components: General Console > Versions: 1.1 alpha > Reporter: Charles Crouch > Assignee: Dimitris Andreadis > Fix For: 1.1 alpha > > Original Estimate: 1 day > Remaining: 1 day > > Porting the updates made to DeploymentService to the JBoss 4.0 branch will > enable people to deploy the Admin Console to existing 4.0.x servers, assuming > they update with the correct jars from the 4.0 branch. A comment should be > made when resolving this issue describing which updated jars are required. -- 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] Created: (JBPM-80) Event Handling
Event Handling -- Key: JBPM-80 URL: http://jira.jboss.com/jira/browse/JBPM-80 Project: JBoss jBPM Type: Sub-task Reporter: Juan Cantu -- 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] [Design of JBoss Portal] - Re: Portal Build
You should NOT checkout those modules.Please... read the doc, it's jboss-portal-2.0 that you need and only that one. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867780#3867780 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867780 --- 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] - Please help. JBoss Cache initialization never returns.
Hi All I am using JBossCache in a my java application as a distributed cache. Ocassionally i am running into a issue where TreeCacheAOP intitalization/start never returns. I see the following error (hosname replaced) --- GMS: address is myhostname:37009 --- - handleJoin(myhostname:37009) failed, retrying - handleJoin(myhostname:37009) failed, retrying - handleJoin(myhostname:37009) failed, retrying - handleJoin(myhostname:37009) failed, retrying - This continues for a long time. Here is the configuration of the cache | | jboss:service=Naming | jboss:service=TransactionManager | 1 | 2 | org.jboss.cache.DummyTransactionManagerLookup | READ_UNCOMMITTED | REPL_SYNC | false | 0 | 0 | CFP_SIT | | | | | | | | | | | | | | | true | 5000 | 1 | 15000 | | Anyone knows what is the problem? Please let me know. Thanks & Regards Kamesh P.S: I have seen similar postings in Jboss clustering forum and they did not have any answers too. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867805#3867805 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867805 --- 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: (JBAS-1524) SessionSynchronisation.beforeCompletion deferred/missing with BMT
[ http://jira.jboss.com/jira/browse/JBAS-1524?page=history ] C. Berger updated JBAS-1524: Attachment: RemoveProblem.jar Test case > SessionSynchronisation.beforeCompletion deferred/missing with BMT > - > > Key: JBAS-1524 > URL: http://jira.jboss.com/jira/browse/JBAS-1524 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, > JBossAS-3.2.6 Final > Environment: Windows 2000 SP 4 > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) > Reporter: C. Berger > Priority: Minor > Attachments: RemoveProblem.jar > > > We have a stateful SessionBean implementing the > SessionSynchronisation-Interface. The transaction is managed by the client > (or alternatively another SessionBean) using the UserTransaction. > The call to beforeCompletion() does not come when expected, after the > UserTransaction has been rolled back (and before afterCompletion()), but when > the bean is removed. As a side effect our cleanup code in beforeCompletion is > not called properly, so we get a warning about an unclosed connection as you > can see in the log snippet: > 14:16:52,710 lookup user transaction... (Client) > 14:16:52,801 open transaction... (Client) > 14:16:52,871 call openConnection()... (Client) > 14:16:52,881 INFO [STDOUT] afterBegin > 14:16:52,881 INFO [STDOUT] openConnection: open connection... > 14:16:53,882 rollback transaction... (Client) > <--- beforeCompletion() expected! > 14:16:53,882 INFO [STDOUT] afterCompletion > 14:16:53,882 INFO [CachedConnectionManager] Closing a connection for you. > Please close them yourself: [EMAIL PROTECTED] > 14:16:54,894 remove bean... (Client) > 14:16:54,894 INFO [STDOUT] afterBegin > 14:16:54,894 INFO [STDOUT] ejbRemove: connection is open! > 14:16:54,894 INFO [STDOUT] beforeCompletion > 14:16:54,894 INFO [STDOUT] beforeCompletion: closing connection... > 14:16:54,894 INFO [STDOUT] afterCompletion > A small, reproducible test case is available if needed. > Best Regards > C. Berger -- 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] Created: (JBAS-1521) build failed due to error in getServerSessionPool
build failed due to error in getServerSessionPool
-
Key: JBAS-1521
URL: http://jira.jboss.com/jira/browse/JBAS-1521
Project: JBoss Application Server
Type: Patch
Components: EJBs
Reporter: Marcin Mieszek
Priority: Blocker
Build of module jboss-head failed due to:
D:\jboss\jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\ConsumerContainer.java:560:
getServerSessionPool(javax.jms.Destination,javax.jms.Connection,int,int,long,boolean,int,boolean,javax.jms.MessageListener)
in org.jboss.jms.asf.ServerSessionPoolFactory cannot be applied to
(javax.jms.Connection,int,int,int,boolean,int,boolean,javax.jms.MessageListener)
pool = factory.getServerSessionPool(connection,
config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
^
D:\jboss\jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\MDB.java:421:
getServerSessionPool(javax.jms.Destination,javax.jms.Connection,int,int,long,boolean,int,boolean,javax.jms.MessageListener)
in org.jboss.jms.asf.ServerSessionPoolFactory cannot be applied to
(javax.jms.Connection,int,int,int,boolean,int,boolean,javax.jms.MessageListener)
pool = factory.getServerSessionPool(connection,
config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
^
I created a patch for
jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\ConsumerContainer.java:
--- cvs.java2005-02-25 03:40:04.0 +0100
+++ local.java 2005-02-25 03:40:30.546875000 +0100
@@ -373,7 +373,7 @@
Method methodMessage = (Method) advisedMethods.get(hash);
// set up the server session pool
-ServerSessionPool serverSessionPool =
createSessionPool(qConnection,
+ServerSessionPool serverSessionPool = createSessionPool(queue,
qConnection,
true, // tx
acknowledgeMode.ordinal(),
listener,
@@ -483,7 +483,7 @@
Method methodMessage = (Method) advisedMethods.get(hash);
// set up the server session pool
-ServerSessionPool serverSessionPool =
createSessionPool(tConnection,
+ServerSessionPool serverSessionPool = createSessionPool(topic,
tConnection,
true, // tx
acknowledgeMode.ordinal(),
listener,
@@ -522,10 +522,8 @@
/**
* Create a server session pool for the given connection.
*
+* @param destination The destination.
* @param connection The connection to use.
-* @param minSession The minumum number of sessions
-* @param maxSession The maximum number of sessions.
-* @param keepAliveThe time to keep sessions alive
* @param isTransacted True if the sessions are transacted.
* @param ack The session acknowledgement mode.
* @param listener The message listener.
@@ -534,7 +532,8 @@
* @throws javax.naming.NamingException Description of Exception
*/
protected ServerSessionPool
- createSessionPool(final Connection connection,
+ createSessionPool(final Destination destination,
+ final Connection connection,
final boolean isTransacted,
int ack,
final MessageListener listener,
@@ -557,7 +556,7 @@
boolean isNotSupportedTx = txType ==
TransactionAttributeType.NOTSUPPORTED;
// the create the pool
- pool = factory.getServerSessionPool(connection,
config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
+ pool = factory.getServerSessionPool(destination, connection,
config.getMinPoolSize(), config.getMaxPoolSize(), config.getKeepAlive(),
isTransacted, ack, !isContainerManagedTx || isNotSupportedTx, listener);
}
finally
{
Patch for jboss-head\ejb3\src\main\org\jboss\ejb3\mdb\MDB.java is:
--- cvs.java2005-02-25 03:47:14.453125000 +0100
+++ local.java 2005-02-25 03:47:32.890625000 +0100
@@ -272,7 +272,7 @@
// set up the server session pool
- serverSessionPool = createSessionPool(qConnection,
+ serverSessionPool = createSessionPool(queue, qConnection,
true, // tx
acknowledgeMode.ordinal(),
new MessageListenerImpl(this));
@@ -344,7 +344,7 @@
jndiSuffix);
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - Problem with XML editor on migration to 3.1M5
Hello, I recently switched to eclipse M5 and reinstalled JBoss IDE for this version. But now I am experiencing an error when saving XML files. Whenever I save a file I get a 'Save Failed: null' error. When I check my log file I see a exception related to xerces. On the other hand the file seems to be saved ok: all modification I make are saved. | !ENTRY org.eclipse.ui 2 0 2005-02-24 14:40:44.593 | !MESSAGE Save Failed | !STACK 0 | java.lang.IncompatibleClassChangeError | at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) | at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) | at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) | at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) | at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) | at org.jboss.ide.eclipse.jdt.xml.ui.editors.XMLEditor.validateXML(XMLEditor.java:224) | at org.jboss.ide.eclipse.jdt.xml.ui.editors.XMLEditor.performSave(XMLEditor.java:176) | at org.jboss.ide.eclipse.jdt.ui.editors.I18NTextEditor.doSave(I18NTextEditor.java:65) | at org.eclipse.ui.internal.SaveableHelper$1.run(SaveableHelper.java:88) | at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:109) | at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:344) | at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:289) | at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:624) | at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) | at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:621) | at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2026) | at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:115) | at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:93) | at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1272) | at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:2659) | at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:2672) | at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:69) | at org.eclipse.jface.action.Action.runWithEvent(Action.java:1003) | at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:182) | at org.eclipse.ui.internal.commands.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:107) | at org.eclipse.core.commands.Command.execute(Command.java:260) | at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:418) | at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:698) | at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:741) | at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:510) | at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$2(WorkbenchKeyboard.java:453) | at org.eclipse.ui.internal.keys.WorkbenchKeyboard$1.handleEvent(WorkbenchKeyboard.java:229) | at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) | at org.eclipse.swt.widgets.Display.filterEvent(Display.java:783) | at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:841) | at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:866) | at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:851) | at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:879) | at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:875) | at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1181) | at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3121) | at org.eclipse.swt.widgets.Control.windowProc(Control.java:3024) | at org.eclipse.swt.widgets.Display.windowProc(Display.java:3480) | at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) | at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1619) | at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2539) | at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1612) | at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1578) | at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:293) | at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144) | at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102) | at org.ecli
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-98) Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases
[ http://jira.jboss.com/jira/browse/JBCACHE-98?page=history ] Ivelin Ivanov updated JBCACHE-98: - Security Level: JBoss Internal > Backporting JBossCache 1.2.1 in JBossAS 4.0.x releases > -- > > Key: JBCACHE-98 > URL: http://jira.jboss.com/jira/browse/JBCACHE-98 > Project: JBoss Cache > Type: Support Patch > Versions: 1.2 > Environment: should work in any environment > Reporter: Luc Texier > Assignee: Bela Ban > Fix For: 1.2.2 > > > Some customers have expressed the wish to take avantages of the > optimizations/bug fixes/enhancements being implemented in the latest releases > of JBossCache (i.e. 1.2.1 and the upcoming 1.2.2). > Therefore, it has been decided to backport JBossCache 1.2.2 to JBossAS 4.0.0 > and JBossAS 4.0.1. -- 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] [Design of JBoss Eclipse IDE (dev)] - JBoss IDE's Support of "left-join read-ahead" feature
Hi, I would like to know if JBoss IDE supports "left-join read-ahead" feature found on JBoss 3.2.4 or superior. Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867884#3867884 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867884 --- 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 JBoss Portal] - Re: Portal Build
Ok... The following error occurred after installation of jboss-cache.jar in lib directory... but this is an error that doesn't relates to the first exception, I think 11:04:28,727 WARN [ServiceController] Problem starting service jboss.har:service=ForumHibernate net.sf.hibernate.HibernateException: Could not instantiate Cache at net.sf.hibernate.cfg.Configuration.configureCaches(Configuration.java:1138) at net.sf.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:795) at org.jboss.hibernate.jmx.Hibernate.buildSessionFactory(Hibernate.java:476) at org.jboss.hibernate.jmx.Hibernate.startService(Hibernate.java:444) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jb
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-97) Propagate the current context classloader and reset it in the thread in the AsynchAspect's ThreadPoolExecutor
Propagate the current context classloader and reset it in the thread in the AsynchAspect's ThreadPoolExecutor - Key: JBAOP-97 URL: http://jira.jboss.com/jira/browse/JBAOP-97 Project: JBoss AOP Type: Bug Reporter: Kabir Khan Fix For: 1.1.1 -- 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: (JBAS-1516) Tomcat5: StandardContext getConfigBase tries to create a directory
[ http://jira.jboss.com/jira/browse/JBAS-1516?page=history ]
Scott M Stark updated JBAS-1516:
Priority: Critical (was: Minor)
> Tomcat5: StandardContext getConfigBase tries to create a directory
> --
>
> Key: JBAS-1516
> URL: http://jira.jboss.com/jira/browse/JBAS-1516
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1
> Environment: JBoss 4.0.1sp1, Solaris8
> Reporter: Roland R?z
> Assignee: Remy Maucherat
> Priority: Critical
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final, JBossAS-3.2.8 Final
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> Hello,
> Just to explain you the circumstances why this request has arised.
> I try to secure JBoss with a java security policy. The policy should prevent
> somebody from writing in the JBoss installation directory.
> For this reason I set a File permission that allows only reading on the
> JBoss installation directory.
> It looks like this
> grant {
> permission java.io.FilePermission "${jboss.home.dir}/-", "read";
> ...
> };
> Now when I start JBoss and deploy a War file I receive the following
> AccessPermissionException
> Caused by: java.security.AccessControlException: access denied
> (java.io.FilePermission
> /opt/jboss/4.0.1/server/myserver/conf/jboss.web/localhost write)
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
> at java.security.AccessController.checkPermission(AccessController.java:401)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
> at java.io.File.mkdir(File.java:1097)
> at java.io.File.mkdirs(File.java:1122)
> at
> org.apache.catalina.core.StandardContext.getConfigBase(StandardContext.java:4858)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4071)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:121)
> at
> org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:143)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:805)
> at org.a
> pache.catalina.core.StandardHost.addChild(StandardHost.java:595)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> ... 152 more
> The method that creates the Exception looks like this
> private File org.apache.catalina.core.StandardContext#getConfigBase()
> {
> File configBase = new File(System.getProperty("catalina.base"),
> "conf");
> if(!configBase.exists())
> return null;
> Container container = this;
> Container host = null;
> Container engine = null;
> for(; container != null; container = container.getParent())
> {
> if(container instanceof Host)
> host = container;
> if(container instanceof Engine)
> engine = container;
> }
> if(engine != null)
> configBase = new File(configBase, engine.getName());
> if(host != null)
> configBase = new File(configBase, host.getName());
> configBase.mkdirs(); // here it crashes
> return configBase;
> }
> JBoss sets the saveConfig Flag of the StandardContext to false.
> (see TomcatDeployer#performDeployInternal)
> configBase.mkdirs() should only be invoked if the saveConfig Flag is set to
> true.
> Regards
--
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] Created: (JGRP-44) RpcDispatcher hangs waiting for response from dead members
RpcDispatcher hangs waiting for response from dead members -- Key: JGRP-44 URL: http://jira.jboss.com/jira/browse/JGRP-44 Project: JGroups Type: Bug Versions: 2.2.8 Environment: Linux Reporter: Mark Riley Assigned to: Bela Ban I am running four jvms with jgroups 2.2.1 across 2 Linux machines, lets call them A & B on machine 1, and C & D on machine 2. They all form into a single group. However if A & B are killed and immediately afterwards C issues a remote method call (via RpcDispatcher) to all members (i.e. before it receives the new view), then C hangs, waiting for all responses, presumably from the dead members A & B. I removed FD_SOCK and inserted FD instead in the protocol stack and this problem seemed to go away. After doing this both A and B were marked as suspected in the RPC. With FD_SOCK, RpcDispatcher never seemed to receive the new view. It was as if the view with the dead members got discarded somewhere along the line. Just to clarify, FD successfully suspects the members every time, FD_SOCK regularly fails to do so. They are being used in conjunction with UDP. FD properties: "timeout" value="2000" "max_tries"value="3" "shun" value="true" FD_SOCK has no properties set -- 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] Created: (JBAS-1524) SessionSynchronisation.beforeCompletion deferred/missing with BMT
SessionSynchronisation.beforeCompletion deferred/missing with BMT - Key: JBAS-1524 URL: http://jira.jboss.com/jira/browse/JBAS-1524 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final Environment: Windows 2000 SP 4 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) Reporter: C. Berger Priority: Minor We have a stateful SessionBean implementing the SessionSynchronisation-Interface. The transaction is managed by the client (or alternatively another SessionBean) using the UserTransaction. The call to beforeCompletion() does not come when expected, after the UserTransaction has been rolled back (and before afterCompletion()), but when the bean is removed. As a side effect our cleanup code in beforeCompletion is not called properly, so we get a warning about an unclosed connection as you can see in the log snippet: 14:16:52,710 lookup user transaction... (Client) 14:16:52,801 open transaction... (Client) 14:16:52,871 call openConnection()... (Client) 14:16:52,881 INFO [STDOUT] afterBegin 14:16:52,881 INFO [STDOUT] openConnection: open connection... 14:16:53,882 rollback transaction... (Client) <--- beforeCompletion() expected! 14:16:53,882 INFO [STDOUT] afterCompletion 14:16:53,882 INFO [CachedConnectionManager] Closing a connection for you. Please close them yourself: [EMAIL PROTECTED] 14:16:54,894 remove bean... (Client) 14:16:54,894 INFO [STDOUT] afterBegin 14:16:54,894 INFO [STDOUT] ejbRemove: connection is open! 14:16:54,894 INFO [STDOUT] beforeCompletion 14:16:54,894 INFO [STDOUT] beforeCompletion: closing connection... 14:16:54,894 INFO [STDOUT] afterCompletion A small, reproducible test case is available if needed. Best Regards C. Berger -- 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: (JBCACHE-93) Memory problem at repeated remote PUT
[ http://jira.jboss.com/jira/browse/JBCACHE-93?page=history ] Henrik Nyberg updated JBCACHE-93: - Attachment: NetCache.java I've removed the hm dependency. > Memory problem at repeated remote PUT > - > > Key: JBCACHE-93 > URL: http://jira.jboss.com/jira/browse/JBCACHE-93 > Project: JBoss Cache > Type: Bug > Versions: 1.2 > Environment: * Windows cluster with two W2K servers, 2 JVMs per server > * JDK 1.4.2_05 > * Application server is Oracle 9.0.3 AS > * one database server (Oracle) > Reporter: Henrik Nyberg > Assignee: Bela Ban > Fix For: 1.2.1 > Attachments: JBCACHE-93.zip, NetCache.java, SimpleCacheTest.java, > SimpleCacheTest.java > > > JBossCache does not properly garbage collect objects that are replicated > through the network and that replaces an already existing object in the local > cache. The existing local cache object that is being replaced by the remote > PUT is not garbage collected. > We have four caches in our setup, A, B, C, D. We describe the status for > cache A after the first iteration using an object sA1. We PUT that object > after every iteration into A using the same key ksA. > Iteration 1: > A updates status -> A(ksA,sA1) replicated to => B(ksA, sA1), C(ksA, sA1), > D(ksA, sA1) > Iteration 2: > A updates status -> A(ksA,sA2) replicated to => B(ksA, sA2), C(ksA, sA2), > D(ksA, sA2) > After iteration 2 the local object A(ksA,sA1) is probably correctly gc:ed, > since if we run this test in local mode the cache works reliably. The remote > objects B(ksA, sA1), C(ksA, sA1), D(ksA, sA1) however seem not to be > correctly gc:ed since the cache constantly eats memory when running in > replicated mode. > If we turn off the status replication, i.e. the repeated PUT of the status > object A(ksA, saN), the cache works like a charm. The only difference between > the two test cases is the PUT. -- 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] Created: (JBAS-1518) NPE in GlobalTxEntityMap
NPE in GlobalTxEntityMap
Key: JBAS-1518
URL: http://jira.jboss.com/jira/browse/JBAS-1518
Project: JBoss Application Server
Type: Bug
Components: EJBs
Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final
Environment: linux/i386
Reporter: Konstantin Sobolev
got a NullPointerException when JBoss 3.2.6 tried to synchronize already
cleared bean:
Caused by: java.lang.NullPointerException
at
org.jboss.ejb.GlobalTxEntityMap$GlobalTxSynchronization.synchronize(GlobalTxEntityMap.java:281)
at
org.jboss.ejb.GlobalTxEntityMap.synchronizeEntities(GlobalTxEntityMap.java:166)
at
org.jboss.ejb.EntityContainer.synchronizeEntitiesWithinTransaction(EntityContainer.java:119)
at org.jboss.ejb.EntityContainer.remove(EntityContainer.java:496)
The problem is obviously caused by this line:
throw new EJBException("Exception in store of entity:" +
((instance == null) ? "" : instance.getId().toString()),
causeByException);
we get NPE since instance.getId() is already null. As I can see, the same
problem exists in 3.2.7 and 4.0
--
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: (JBAOP-97) Propagate the current context classloader and reset it in the thread in the AsynchAspect's ThreadPoolExecutor
[ http://jira.jboss.com/jira/browse/JBAOP-97?page=history ] Kabir Khan closed JBAOP-97: --- Resolution: Done > Propagate the current context classloader and reset it in the thread in the > AsynchAspect's ThreadPoolExecutor > - > > Key: JBAOP-97 > URL: http://jira.jboss.com/jira/browse/JBAOP-97 > Project: JBoss AOP > Type: Bug > Reporter: Kabir Khan > Fix For: 1.1.1 > > -- 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-head build.834 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050225051751Lbuild.834 BUILD COMPLETE - build.834Date of build: 02/25/2005 05:17:51Time to build: 15 minutes 50 secondsLast changed: 02/25/2005 04:59:01Last log entry: added getCoordinator() Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (12)1.228modifiedbelabancache/src/main/org/jboss/cache/TreeCache.javaadded getCoordinator()1.3modifiedbelabancache/src/main/org/jboss/cache/loader/DelegatingCacheLoader.javanew file by Daniel Gredler1.1addedbelabancache/src/main/org/jboss/cache/loader/LocalDelegatingCacheLoader.javanew file by Daniel Gredler1.1addedbelabancache/src/main/org/jboss/cache/loader/RmiDelegatingCacheLoader.javanew file by Daniel Gredler1.1addedbelabancache/src/main/org/jboss/cache/loader/RpcDelegatingCacheLoader.javanew file by Daniel Gredler1.7modifiedbelabancache/src/main/org/jboss/cache/tests/InterceptorConfigurationTest.javachanged to LocalDelegatingCacheLoader1.53modifiedbelabancache/build.xmlno message1.1addedbelabancache/src/main/org/jboss/cache/tests/LocalDelegatingCacheLoaderTest.javarenamed1.52modifiedbelabancache/build.xmlno message1.2modifiedbelabancache/docs/TreeCache/en/master.xmladded LocalDelegatingCacheLoader descr1.39modifiedbelabancache/docs/Changelog.txtno message1.16modifiedbelabancache/src/main/org/jboss/cache/loader/FileCacheLoader.javaapplied Wudtke patch (MarshalledInputStream)
[JBoss-dev] jboss-4.0 build.402 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050225055616Lbuild.402 BUILD COMPLETE - build.402Date of build: 02/25/2005 05:56:16Time to build: 19 minutes 54 secondsLast changed: 02/25/2005 04:53:48Last log entry: Remove trailing } Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.4.2.3modifiedtdiesleraspects/src/main/org/jboss/aspects/security/AuthenticationInterceptor.javaRemove trailing }1.7.4.3modifiedanddthirdparty/jacorb-jacorb/lib/jacorb_g.jar#JBAS-1506 - Patched jacorb V2.2.1 (JBoss patch 1), 23-Feb-2005
[JBoss-dev] [Design of JBoss Portal] - Re: Portal Build
actually this exception is not the good one (I need to find a better way to nest exceptions), another exception should be listed in the log just above. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867906#3867906 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867906 --- 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
