[JBoss-dev] [Design of AOP on JBoss (Aspects/JBoss)] - how to write jboss-aop.xml for hibernate and spring framewor
I'm using Hibernate combined with spring framework. I'm using this hibernate in web tier(Action classes). Now I have written aspects classes using jboss aop. but its finding difficult for me to write jboss-aop.xml to bind pointcut to hibernate calls. I have tried with this jboss-aop.xml bind pointcut="execution(* net.sf.hibernate.Session->*(..))"> interceptor class="tavant.platform.infrared.aspects.HibernateAPIAspect"/> Please help me in this regard Thanks and Regards, Kiran. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867029#3867029 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867029 --- 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 AOP on JBoss (Aspects/JBoss)] - Re: java.lang.RuntimeException: ***** trying to convertRefer
Yes, struts.jar in WEB-INF/lib directory. Should I need to put in sever/default/lib directory. How should I ensure that the jars present in WEB-INF/lib directory is not instrumented. Thanks and Regards, Kiran View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867028#3867028 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867028 --- 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.384 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050218000655Lbuild.384 BUILD COMPLETE - build.384Date of build: 02/18/2005 00:06:55Time to build: 21 minutes 31 secondsLast changed: 02/17/2005 22:16:12Last log entry: Update to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.4.6.1modifiedstarksmthirdparty/oswego-concurrent/lib/README.txtUpdate to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.2.4.1modifiedstarksmthirdparty/oswego-concurrent/lib/concurrent-src.zipUpdate to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.4.4.1modifiedstarksmthirdparty/oswego-concurrent/lib/concurrent.jarUpdate to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)
[JBoss-dev] [JBoss JIRA] Created: (JGRP-39) A TCP stack does not correctly detect failure (pulled cable) for certain TCPPING configurations
A TCP stack does not correctly detect failure (pulled cable) for certain TCPPING configurations --- Key: JGRP-39 URL: http://jira.jboss.com/jira/browse/JGRP-39 Project: JGroups Type: Bug Versions: 2.2.9 Reporter: Ovidiu Feodorov Assigned to: Bela Ban Physical hosts "A" (192.168.1.1, coordinator) and "B" (192.168.1.2) run JGroups processes configured with TCP/TCPPING stacks. "A" stack configuration: TCP(bind_addr=192.168.1.1;start_port=11800;loopback=true): TCPPING(initial_hosts=192.168.1.2[11800];port_range=3;timeout=3500;num_initial_members=3;up_thread=true;down_thread=true): MERGE2(min_interval=5000;max_interval=1): FD(shun=true;timeout=1500;max_tries=3;up_thread=true;down_thread=true): VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): pbcast.NAKACK(down_thread=true;up_thread=true;gc_lag=100;retransmit_timeout=3000): pbcast.STABLE(desired_avg_gossip=2;down_thread=false;up_thread=false): pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=false;down_thread=true;up_thread=true) "B" stack configuration: TCP(bind_addr=192.168.1.2;start_port=11800;loopback=true): TCPPING(initial_hosts=192.168.1.1[11800];port_range=3;timeout=3500;num_initial_members=3;up_thread=true;down_thread=true): MERGE2(min_interval=5000;max_interval=1): FD(shun=true;timeout=1500;max_tries=3;up_thread=true;down_thread=true): VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): pbcast.NAKACK(down_thread=true;up_thread=true;gc_lag=100;retransmit_timeout=3000): pbcast.STABLE(desired_avg_gossip=2;down_thread=false;up_thread=false): pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=false;down_thread=true;up_thread=true) If I pull the cable under B, the B stack immediately and correctly indentifies A as suspect and installs a new view containing itself only. However, A does not recognizes B as suspect and undeterministically spews out various info and warning messages. The view (A, B) stays incorrectly "valid" for a long time; sometimes gets replaced by (A), sometimes not. I tracked down the cause of the problem down to the A TCPPING configuration and TCP queue . If A's TCPPING is configured with a port_range=1, the problem goes away and the new view immediately installs into the A stack. It seems that if there are messages in the TCP queue except the SUSPECT message generated by FD, they mess up things and the SUSPECT message gets stuck in the queue, with undeterministic results. -- 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-4.0-jdk-matrix build.91 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050217233519Lbuild.91 BUILD COMPLETE - build.91Date of build: 02/17/2005 23:35:19Time to build: 22 minutes 13 secondsLast changed: 02/17/2005 22:16:12Last log entry: Update to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (8)1.4.6.1modifiedstarksmthirdparty/oswego-concurrent/lib/README.txtUpdate to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.2.4.1modifiedstarksmthirdparty/oswego-concurrent/lib/concurrent-src.zipUpdate to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.4.4.1modifiedstarksmthirdparty/oswego-concurrent/lib/concurrent.jarUpdate to 1.3.4# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.15.2.2modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/EntityTable.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.8.2.3modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/bridge/JDBCCMRFieldBridge2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.8.2.3modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.4.2.1modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/PersistentContext.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.28.6.2modifiedacoliver2cluster/src/etc/cluster-service.xml JBoss has an HA version of the pooled invoker that is not in the cluser-service.xml or in the formal documentation. Now doc'd on wiki page: http://www.jboss.org/wiki/Wiki.jsp?page=PooledInvokerHA and in this file as an example
[JBoss-dev] jboss-3.2 build.294 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050217231254Lbuild.294 BUILD COMPLETE - build.294Date of build: 02/17/2005 23:12:54Time to build: 14 minutes 44 secondsLast changed: 02/17/2005 22:17:34Last log entry: Update to 1.3.4:# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.1.2.4modifiedstarksmthirdparty/oswego/concurrent/lib/README.txtUpdate to 1.3.4:# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.1.2.3modifiedstarksmthirdparty/oswego/concurrent/lib/concurrent-src.zipUpdate to 1.3.4:# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)1.1.1.1.8.5modifiedstarksmthirdparty/oswego/concurrent/lib/concurrent.jarUpdate to 1.3.4:# ConcurrentHashMap -- avoid keySet etc toArray array underallocation (Thanks to Kade.Hansson.)# PooledExecutor shutdownAfterProcessingCurrentlyQueuedTasks wakes up waiting threads to cause them to terminate (Thanks to Brent Boyer.)
[JBoss-dev] [JBoss JIRA] Commented: (JGRP-31) Problem with MERGE2 when not using multicast
[ http://jira.jboss.com/jira/browse/JGRP-31?page=comments#action_12315513 ] B.S.Navin commented on JGRP-31: --- One more possible solution (a more generic one) would be to create a small protocol that sits between TCPPING & its underlying layer (UDP / TCP) that just adds an additional header to PING requests with the co-ordinator of this member. It can intercept any incoming PING requests and look for a different co-ordinator in the header & pass a MERGE request up the stack. This protocol can be used only when using MERGE2/TCPPING/(UDP/TCP) with multicast disabled. > Problem with MERGE2 when not using multicast > > > Key: JGRP-31 > URL: http://jira.jboss.com/jira/browse/JGRP-31 > Project: JGroups > Type: Bug > Versions: 2.2.8 > Environment: SUN Java 1.4.2_05 > Reporter: B.S.Navin > Assignee: Bela Ban > Fix For: 2.2.8 > > > Hi, > There is one case in which MERGE2 will fail while using TCPPING/UDP(without > mcast): > > The initial_hosts property is "abc.com[7800];xyz.com[7801]". > These 2 machines are permanent group members (if they are up, they will be > members of the group). > Now there are numerous other programs on different machines that may > dynamically join and leave the group. These members are not known before hand > and cannot be specified in the initial_hosts property. > The members on abc.com and xyz.com are started and they join the same group. > Now another member from "mnop.com" starts and joins the group. The > co-ordinator will be abc.com > A network problem occurs and mnop.com is separated from abc.com and xyz.com > mnop.com forms its own single-member group with itself as the co-ordinator. > Now suppose the network problem is fixed. The MERGE2 protocol on mnop.com > periodically checks on the initial_hosts list to see if they are up. It now > finds that abc.com is reachable and decides that abc.com is the leader (by > lexical sorting) and will take care of the merging. So it does not go ahead > with the merge. > On the other hand, the MERGE2 protocol on both abc.com and xyz.com just check > if they can find members on the initial_hosts with a different co-ordinator. > Both of them never consider mnop.com as it is not in the initial_hosts list > So mnop.com will never be merged with the group. > > Even the new MERGE3 & MERGEFAST protocols don't seem to help here. I checked > them out and found the following: > MERGEFAST works only if multicast is used, which is not my case. > MERGE3 just sends "I am co-ordinator" messages to a null destination. So in > the case where multicast is enabled, it goes to all possible members. But in > my case, with multicast disabled, the message will only be unicast to each > member of the current group. So in the above example, the "I am co-ordinator" > messages will never go to mnop.com after the network problem. > So even MERGE3 does not work in this case. -- 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.810 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050217224611Lbuild.810 BUILD COMPLETE - build.810Date of build: 02/17/2005 22:46:11Time to build: 16 minutes 44 secondsLast changed: 02/17/2005 22:13:45Last log entry: Update to the 1.3.4 release.# WaitableX: notify on bitwise operations# QueuedExecutor: can shutdown before thread created (thanks to Wolfgang Hoschek) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (79)1.5modifiedstarksmthirdparty/oswego-concurrent/lib/concurrent.jarUpdate to the 1.3.4 release.# WaitableX: notify on bitwise operations# QueuedExecutor: can shutdown before thread created (thanks to Wolfgang Hoschek)1.5modifiedstarksmthirdparty/oswego-concurrent/lib/README.txtUpdate to the 1.3.4 release.# WaitableX: notify on bitwise operations# QueuedExecutor: can shutdown before thread created (thanks to Wolfgang Hoschek)1.3modifiedstarksmthirdparty/oswego-concurrent/lib/concurrent-src.zipUpdate to the 1.3.4 release.# WaitableX: notify on bitwise operations# QueuedExecutor: can shutdown before thread created (thanks to Wolfgang Hoschek)1.11modifiedstarksmtestsuite/src/main/org/jboss/test/cache/test/eviction/AopLRUPolicyUnitTestCase.javaGet this class to compile1.1addedejortcommon/src/main/org/jboss/util/WeakClassCache.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortcontainer/src/main/org/jboss/joinpoint/config/Config.javaFurther tidying up. ClassAdapter comes next.1.7modifiedejortcontainer/src/main/org/jboss/reflect/PrimitiveInfo.javaFurther tidying up. ClassAdapter comes next.1.6modifiedejortcontainer/src/main/org/jboss/reflect/plugins/introspection/IntrospectionTypeInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.8modifiedejortkernel/src/main/org/jboss/kernel/plugins/dependency/AbstractKernelController.javaFurther tidying up. ClassAdapter comes next.1.2modifiedejortkernel/src/main/org/jboss/kernel/spi/config/KernelConfig.javaFurther tidying up. ClassAdapter comes next.1.3modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/AbstractKernelConfig.javaFurther tidying up. ClassAdapter comes next.1.10modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/Configurator.javaFurther tidying up. ClassAdapter comes next.1.3deletedejortkernel/src/main/org/jboss/util/KernelUtil.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortkernel/src/main/org/jboss/beans/info/spi/BeanInfo.javaFurther tidying up. ClassAdapter comes next.1.5modifiedejortkernel/src/main/org/jboss/beans/info/spi/BeanInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/AbstractBootstrap.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/AbstractKernelFactory.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/AbstractKernelInitializer.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/kernel/spi/bootstrap/KernelFactory.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/kernel/spi/bootstrap/KernelInitializer.javaFurther tidying up. ClassAdapter comes next.1.3deletedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/basic/BasicKernelFactory.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/basic/BasicKernelInitializer.javaFurther tidying up. ClassAdapter comes next.1.2modifiedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/basic/KernelConstants.javaFurther tidying up. ClassAdapter comes next.1.7modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/basic/BasicKernelConfigurator.javaFurther tidying up. ClassAdapter comes next.1.3modifiedejortkernel/src/main/org/jboss/beans/metadata/plugins/AbstractArrayMetaData.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortkernel/src/main/org/jboss/beans/metadata/plugins/StringValueMetaData.javaFurther tidying up. ClassAdapter comes next.1.3modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/property/PropertyKernelConfig.javaFurther tidying up. ClassAdapter comes next.1.5modifiedejortkernel/src/main/org/jboss/beans/info/plugins/AbstractBeanInfo.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/beans/info/plugins/AbstractBeanInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/beans/info/plugins/reflect/ClassLoading.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/beans/info/plugins/reflect/ReflectBeanInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/beans/info/plugins/reflect/package.htmlFurther tidying u
[JBoss-dev] jboss-3.2-jdk-matrix build.58 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050217212945Lbuild.58 BUILD COMPLETE - build.58Date of build: 02/17/2005 21:29:45Time to build: 18 minutes 16 secondsLast changed: 02/17/2005 17:26:22Last log entry: fixed issue JBBENCH-29: collection-valued CMR cache synchronization issue Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (8)1.1.2.19modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/bridge/JDBCCMRFieldBridge2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.1.2.36modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/EntityTable.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.1.2.19modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.1.2.7modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/PersistentContext.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.9.2.8modifiedejortserver/src/main/org/jboss/proxy/ejb/handle/StatefulHandleImpl.java[JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.1.5.2.4modifiedejortserver/src/main/org/jboss/proxy/ejb/StatefulSessionInterceptor.java[JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.1.9.2.7modifiedejortserver/src/main/org/jboss/proxy/ejb/handle/StatefulHandleImpl.javaSwitch over the SFSB handle to use the jndi strategy of the other handles.This is backwards compatible in the sense that the new code will work with older handles(as long as the default initial context produces the correct jndi handle to lookup the home).However, older clients won't be able to use the new handle because they tried to use theinvoker which is no longer present in the handle.Using the invoker was incorrect. Depending on the transport, it did not survive serverrestarts (which is the whole point of using a handle rather than an EJBObject).1.5.2.3modifiedejortserver/src/main/org/jboss/proxy/ejb/StatefulSessionInterceptor.javaSwitch over the SFSB handle to use the jndi strategy of the other handles.This is backwards compatible in the sense that the new code will work with older handles(as long as the default initial context produces the correct jndi handle to lookup the home).However, older clients won't be able to use the new handle because they tried to use theinvoker which is no longer present in the handle.Using the invoker was incorrect. Depending on the transport, it did not survive serverrestarts (which is the whole point of using a handle rather than an EJBObject).
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050217203854 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 02/17/2005 20:38:54Time to build: 32 minutes 59 secondsLast changed: 02/17/2005 19:43:06Last log entry: Further tidying up. ClassAdapter comes next. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (75)1.1addedejortcommon/src/main/org/jboss/util/WeakClassCache.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortcontainer/src/main/org/jboss/joinpoint/config/Config.javaFurther tidying up. ClassAdapter comes next.1.7modifiedejortcontainer/src/main/org/jboss/reflect/PrimitiveInfo.javaFurther tidying up. ClassAdapter comes next.1.6modifiedejortcontainer/src/main/org/jboss/reflect/plugins/introspection/IntrospectionTypeInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.8modifiedejortkernel/src/main/org/jboss/kernel/plugins/dependency/AbstractKernelController.javaFurther tidying up. ClassAdapter comes next.1.2modifiedejortkernel/src/main/org/jboss/kernel/spi/config/KernelConfig.javaFurther tidying up. ClassAdapter comes next.1.3modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/AbstractKernelConfig.javaFurther tidying up. ClassAdapter comes next.1.10modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/Configurator.javaFurther tidying up. ClassAdapter comes next.1.3deletedejortkernel/src/main/org/jboss/util/KernelUtil.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortkernel/src/main/org/jboss/beans/info/spi/BeanInfo.javaFurther tidying up. ClassAdapter comes next.1.5modifiedejortkernel/src/main/org/jboss/beans/info/spi/BeanInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/AbstractBootstrap.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/AbstractKernelFactory.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/AbstractKernelInitializer.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/kernel/spi/bootstrap/KernelFactory.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/kernel/spi/bootstrap/KernelInitializer.javaFurther tidying up. ClassAdapter comes next.1.3deletedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/basic/BasicKernelFactory.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/basic/BasicKernelInitializer.javaFurther tidying up. ClassAdapter comes next.1.2modifiedejortkernel/src/main/org/jboss/kernel/plugins/bootstrap/basic/KernelConstants.javaFurther tidying up. ClassAdapter comes next.1.7modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/basic/BasicKernelConfigurator.javaFurther tidying up. ClassAdapter comes next.1.3modifiedejortkernel/src/main/org/jboss/beans/metadata/plugins/AbstractArrayMetaData.javaFurther tidying up. ClassAdapter comes next.1.4modifiedejortkernel/src/main/org/jboss/beans/metadata/plugins/StringValueMetaData.javaFurther tidying up. ClassAdapter comes next.1.3modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/property/PropertyKernelConfig.javaFurther tidying up. ClassAdapter comes next.1.5modifiedejortkernel/src/main/org/jboss/beans/info/plugins/AbstractBeanInfo.javaFurther tidying up. ClassAdapter comes next.1.1addedejortkernel/src/main/org/jboss/beans/info/plugins/AbstractBeanInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/beans/info/plugins/reflect/ClassLoading.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/beans/info/plugins/reflect/ReflectBeanInfoFactory.javaFurther tidying up. ClassAdapter comes next.1.2deletedejortkernel/src/main/org/jboss/beans/info/plugins/reflect/package.htmlFurther tidying up. ClassAdapter comes next.1.15modifiedccrouchadmin-console/src/resources/admin-console.war/WEB-INF/classes/messages/applicationmessages.propertiesupdates to improve formatting of datasource view page1.11modifiedccrouchadmin-console/src/resources/admin-console.war/WEB-INF/jsp/datasource/detailDataSource.jspupdates to improve formatting of datasource view page1.7modifiedccrouchadmin-console/src/resources/admin-console.war/WEB-INF/jsp/datasource/detailDataSource2.jspupdates to improve formatting of datasource view page1.2deletedccrouchadmin-console/src/main/org/jboss/admin/console/web/struts/datasource/SaveDataSourceActionTest.java
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1383) findByPrimaryKey error
[ http://jira.jboss.com/jira/browse/JBAS-1383?page=comments#action_12315512 ] Willy Ong commented on JBAS-1383: - Didn't know it could be a driver problem since the same driver works for 4.0.0. Thanks for pointing it out to me. > findByPrimaryKey error > -- > > Key: JBAS-1383 > URL: http://jira.jboss.com/jira/browse/JBAS-1383 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Linux, postgres > Reporter: Willy Ong > Assignee: Alexey Loubyansky > Priority: Minor > > > Hi, > I encountered the following error when I tried to run to deploy a 3.2.x jar > file for jboss 4.0.1. I assumed it was due to some incompatibility with the > Java specifications. But later on, I was able to deploy it successfully on > jboss 4.0.0. All the files used are the same, i.e. the jar, database, jdbc > driver etc. The only difference is the App Server. Is this a bug? Thanks. > 10:34:12,628 ERROR [ReapAccessLog#findByPrimaryKey] Find failed > org.postgresql.util.PSQLException: The backend currently does not support > this feature. > at > org.postgresql.jdbc2.AbstractJdbc2Statement.getFetchDirection(AbstractJdbc2Statement.java:133) > at > org.jboss.resource.adapter.jdbc.CachedPreparedStatement.(CachedPreparedStatement.java:62) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:349) > at > org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:205) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:190) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:128) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.execute(JDBCFindByPrimaryKeyQuery.java:128) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:47) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:589) > at > org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:300) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:298) > at > org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1086) > at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:663) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.invocation.Invocation.performCall(Invocation.java:345) > at > org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1113) > at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90) > at > org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:192) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:212) > at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90) > at > org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:117) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28) > at > org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:41) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:109) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:313) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:126) > at > org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:101) > at > org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:121) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93) > at > org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:508) > at org.jboss.ejb.Container.invoke(Container.java:891) > at > org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:342) > at > org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:118) >
[JBoss-dev] jboss-4.0 build.383 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050217192752Lbuild.383 BUILD COMPLETE - build.383Date of build: 02/17/2005 19:27:52Time to build: 23 minutes 1 secondLast changed: 02/17/2005 17:39:32Last log entry: fixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.15.2.2modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/EntityTable.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.8.2.3modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/bridge/JDBCCMRFieldBridge2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.8.2.3modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)1.4.2.1modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/PersistentContext.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue (cmp2.x jdbc2 pm)
[JBoss-dev] jboss-3.2 build.293 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050217183000Lbuild.293 BUILD COMPLETE - build.293Date of build: 02/17/2005 18:30:00Time to build: 33 minutes 27 secondsLast changed: 02/17/2005 17:26:22Last log entry: fixed issue JBBENCH-29: collection-valued CMR cache synchronization issue Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.1.2.19modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/bridge/JDBCCMRFieldBridge2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.1.2.36modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/EntityTable.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.1.2.19modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue1.1.2.7modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/PersistentContext.javafixed issue JBBENCH-29: collection-valued CMR cache synchronization issue
[JBoss-dev] [Design of JBoss Admin Console] - Use Case 5(Update DataSource) Complete
Use Case 5(Update DataSource) has been completed both basic flow and alternate flows. Extension point 5.1 (Test DataSource) was implemented as part of use case 1 (View list of Datasources). Goal A DataSource is successfully updated. Basic flow of events 1. The user indicates to the system that they wish to update a particular DataSource. 2. The system displays the list of existing attributes for the DataSource for the user to update. 3. The user updates some attributes and indicates to the system to update the DataSource with the given settings. 4. The system takes the information entered by the user, validates it and updates the existing DataSource. 5. The system indicates to the user that the DataSource was successfully updated. 6. The use case ends. Alternate flows A5.1: Information validation fails, DataSource not updated During step 4) of the Basic Flow. This alternate flow is exactly analogous to A4.1, leaving the DataSource unchanged. A5.2: Information validation fails, user fixes problem This alternate flow is exactly analogous to A4.2, eventually updating the DataSource. A5.3: User cancels update During step 3) of the Basic Flow. This alternate flow is exactly analogous to A4.3, leaving the DataSource unchanged. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867021#3867021 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867021 --- 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: Basic flow of Use Case 4(Create a DataSource) Complete
Alternate Flows A4.1: Information validation fails, DataSource not created During step 4) of the Basic Flow: 1. The system finds a problem with the information the user submitted, see variations below. 2. The system displays the information the user submitted and indicates to the user which piece(s) of information caused the problem. 3. The use case ends. Possible validation errors are: a) The uploaded driver is not a valid jar file. b) A security domain is specified at the same time as specifying application managed security. c) Invalid value given for Blocking timeout. d) Invalid value given for idle timeout. e) Invalid value given for Prepared statement cache size. A4.2: Information validation fails, user fixes problem After step 2) of Alternative Flow A1.1: 1. The user updates the pieces of information which the system indicated had caused the problem and indicates to the system to create the DataSource. 2. The system takes the information entered by the user, validates it and creates the DataSource. 3. The system indicates to the user that the DataSource was successfully created. 4. The use case ends. A4.3: User cancels creation During step 3) of the Basic Flow: 1. The user indicates to the system that they want to cancel the creation of the DataSource. 2. The system does not attempt to create a DataSource. The system displays the page the user was on before attempting to create the DataSource. 3. The use case ends. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867020#3867020 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867020 --- 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: Basic flow of Use Case 4(Create a DataSource) Complete
The Alternate flows A4.x (validation and cancel create) have been completed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867019#3867019 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867019 --- 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: most of use case 1 in cvs
Extension point 3.1 (Test DataSource) has been completed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867018#3867018 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867018 --- 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-86) invalidate() across cluster
[ http://jira.jboss.com/jira/browse/JBCACHE-86?page=comments#action_12315511 ] Bela Ban commented on JBCACHE-86: - yes > invalidate() across cluster > --- > > Key: JBCACHE-86 > URL: http://jira.jboss.com/jira/browse/JBCACHE-86 > Project: JBoss Cache > Type: Feature Request > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: build now requires Java 5!
the goal is to stay with java 4, however the build system does not accept it for some obscure reason. I will try to investigate this as it can be very annoying. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867016#3867016 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867016 --- 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: Clarification needed on LRUPolicy and timeToLiveSeconds
#1 Yes, getChildrenNames() is currently the recommended way to traverse the tree. #2 We plan to extract TreeCache/TreeCacheAop into an interface View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867015#3867015 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867015 --- 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: build now requires Java 5!
Sorry this is a mistake from us (me probably, i commited some code today) I will install 1.4 back to avoid such mistake. Java 5 is not required. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867010#3867010 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867010 --- 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: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315509 ] John Emerson commented on JBIDE-116: It turns out my test was not thorough. Clearcase runs a daemon (aldb) on Windows that was running when I did my test befere. That is, with the daemon running, when I disconnected from Clearcase in eclipse, I still saw the problem. However, when I stop the daemon, I don't see the problem. This is the case that you see Marshall. I'm not sure, but I think you need a real clearcase server running to which the daemon can connect, else it will not start. So, debugging may be difficult because it might require an actual clearcase repository. John > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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] - build now requires Java 5!
I just found out that there is usage of a Tiger String method (contains()) which requires Java 5 to be able to build the portal! If you do make minor modifications like that, could you please update the doc, or post it on the forum ? or did I miss it ? sorry, just angry about the time I just spent to figure this out . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867008#3867008 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867008 --- 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: Login Failed!
Looks like no jdbc driver was found. Make sure the connector(driver) is sitting in JBOSS_HOME/server/standard/lib/ ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867001#3867001 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867001 --- 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: Login Failed!
The log is: | 2005-02-17 22:40:26,822 WARN [net.sf.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState: null | 2005-02-17 22:40:26,822 ERROR [net.sf.hibernate.util.JDBCExceptionReporter] Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: org.gjt.mm.mysql.Driver; - nested throwable: (java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: org.gjt.mm.mysql.Driver; - nested throwable: (java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver))) | 2005-02-17 22:40:26,822 ERROR [net.sf.hibernate.util.JDBCExceptionReporter] Cannot open connection | org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: org.gjt.mm.mysql.Driver; - nested throwable: (java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Failed to register driver for: org.gjt.mm.mysql.Driver; - nested throwable: (java.lang.ClassNotFoundException: org.gjt.mm.mysql.Driver))) | at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:106) | at net.sf.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:59) | at net.sf.hibernate.impl.BatcherImpl.openConnection(BatcherImpl.java:278) | at net.sf.hibernate.impl.SessionImpl.connect(SessionImpl.java:3302) | at net.sf.hibernate.impl.SessionImpl.connection(SessionImpl.java:3282) | at net.sf.hibernate.impl.BatcherImpl.prepareQueryStatement(BatcherImpl.java:65) | at net.sf.hibernate.loader.Loader.prepareQueryStatement(Loader.java:704) | at net.sf.hibernate.loader.Loader.doQuery(Loader.java:185) | at net.sf.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:133) | at net.sf.hibernate.loader.Loader.doList(Loader.java:958) | at net.sf.hibernate.loader.Loader.list(Loader.java:949) | at net.sf.hibernate.hql.QueryTranslator.list(QueryTranslator.java:846) | at net.sf.hibernate.impl.SessionImpl.find(SessionImpl.java:1543) | at net.sf.hibernate.impl.QueryImpl.list(QueryImpl.java:39) | at net.sf.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:542) | at org.jboss.portal.core.security.jaas.HibernateLoginModule$1.run(HibernateLoginModule.java:92) | at org.jboss.portal.common.transaction.Demarcator.requiresNew(Demarcator.java:52) | at org.jboss.portal.core.security.jaas.HibernateLoginModule.getUsersPassword(HibernateLoginModule.java:81) | at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:156) | 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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:675) | at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129) | at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610) | at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607) | at javax.security.auth.login.LoginContext.login(LoginContext.java:534) | at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:491) | at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:442) | at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:257) | at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:232) | at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:239) | at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:235) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) | at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:169) | at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) | at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) | at o
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050217152759 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 02/17/2005 15:27:59Time to build: 36 minutes 48 secondsLast changed: 02/17/2005 13:18:10Last log entry: new metadata prototype Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (37)1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValueFactory.javanew metadata prototype1.5modifiedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/unmarshalling/BindingCursor.javanew metadata prototype1.8modifiedloubyanskycommon/src/main/org/jboss/xml/binding/MetadataDrivenObjectModelFactory.javanew metadata prototype1.35modifiedloubyanskycommon/src/main/org/jboss/xml/binding/ObjectModelBuilder.javanew metadata prototype1.6modifiedloubyanskycommon/src/main/org/jboss/xml/binding/SimpleTypeBindings.javanew metadata prototype1.25modifiedloubyanskycommon/src/main/org/jboss/xml/binding/Unmarshaller.javanew metadata prototype1.7modifiedloubyanskycommon/src/main/org/jboss/xml/binding/UnmarshallerImpl.javanew metadata prototype1.4modifiedloubyanskycommon/src/main/org/jboss/xml/binding/UnmarshallingContext.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapEntryValue.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/MapValue.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/ObjectModelFactoryImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlAttribute.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlAttributeImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlComplexType.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlComplexTypeImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDataContent.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDataContentImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocument.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocumentFactory.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocumentFactoryImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlDocumentImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlElement.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlElementImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlNamespace.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlNamespaceImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlSimpleType.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlSimpleTypeImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlType.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/XmlTypeImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/ArrayValue.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/CollectionValue.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/CursorImpl.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaFieldValue.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValue.javanew metadata prototype1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/metadata/JavaValueFactoryImpl.javanew metadata prototype1.10modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/eviction/AopLRUPolicyUnitTestCase.javaRollbacked JBCache-90 fix untill next release1.42modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaJBCACHE-90 fix. Let's wait untill 1.2.1 is out
[JBoss-dev] [Design of Mail Services] - Default delivery of all unknown email
I am looking for a solution and a sample configuration to the following problem. I need a way to deliver all email that does not map to a valid email account to be delivered to a default account. So let's say an email was delivered to my email server to the following address [EMAIL PROTECTED] There is no user in my system with the account ajax. So instead of sending an Undeliverable email back to the sender I would like to place this in a default mailbox. Is this something that JBMail can handle or would I need to implement this myself? Thanks in advance Henry View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866993#3866993 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866993 --- 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] - Login Failed!
When I try to login at the portal I always get the Error "Login Failed!". It also failed when I try to create a new user. After the click on "New User" the user is not in the table jbp_users. There are only the User "admin" and "user". What is my fault? What are the Default Passwords for admin and user? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866992#3866992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866992 --- 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: JBoss Portal TransactionFilter.java:85
Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866991#3866991 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866991 --- 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: Newbie Question: How do I add portlets and panes
You can look at the user guide to see how you can add a portlet. There is no GUI so far. (if you are looking to work on something ;) ) Come say hi at the JBoss Portal Booth ! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866990#3866990 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866990 --- 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] - Newbie Question: How do I add portlets and panes
I just downloaded Jboss 4.0.1 sp1 and JBoss Portal. It is up and running but I can only see the User, Role, Admin, Login and CMS Portlets. I am totally stumped at how to access other portlets or add other portlets. Please respond with a link I can go to see some examples. By the way, I jazzed about going to the Conference in March. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866989#3866989 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866989 --- 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: JBoss Portal TransactionFilter.java:85
And here is the stack trace: | | 2005-02-17 20:23:45,750 ERROR [org.jboss.web.localhost.Engine] | ApplicationDispatcher[/portal] Servlet.service() for servlet jsp threw | exception | Unable to find a javac compiler; | com.sun.tools.javac.Main is not on the classpath. | Perhaps JAVA_HOME does not point to the JDK Are you sure your JAVA_HOME is really defined to your home directory of Java ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866988#3866988 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866988 --- 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: JBoss Portal TransactionFilter.java:85
Hello, I have installed the 4.0.0 final now. After this I get an Error like the first. Thanks for your prompt Answer to the first Question! I have send yuu the stack trace per Mail. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866987#3866987 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866987 --- 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: Init Param
I've included the preferences tag in portlet-instances.xml and used the
function:
request.getPreferences().getValue("page","")
to access the preference but the default value was returned.
Had I used the correct function?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866983#3866983
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866983
---
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-1484) ClassCastException while creating JNDI SubContext
[ http://jira.jboss.com/jira/browse/JBAS-1484?page=comments#action_12315508 ] Jens Schumann commented on JBAS-1484: - Clarification: If you use System.getProperties() to create an InitialContext and create a subcontext afterwards, the exception above will be thrown. > ClassCastException while creating JNDI SubContext > - > > Key: JBAS-1484 > URL: http://jira.jboss.com/jira/browse/JBAS-1484 > Project: JBoss Application Server > Type: Bug > Components: Naming > Versions: JBossAS-4.0.1 Final > Reporter: Jens Schumann > > > Creating a subcontext from a servlet failes with a ClassCastExeception. > java.lang.ClassCastException > at org.jboss.util.property.PropertyMap.remove(PropertyMap.java:198) > at org.jnp.interfaces.NamingContext.getEnv(NamingContext.java:1299) > at > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:867) > at > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:858) > at > javax.naming.InitialContext.createSubcontext(InitialContext.java:413) > The debugger shows a CompoundName instance for the value jnp.parsedName > instead of a String. I was unable to create a testcase because I don't know > how to place the CompoundName instance this far. > Will examine the issue more closely. -- 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-testsuite build.74 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050217124043Lbuild.74 BUILD COMPLETE - build.74Date of build: 02/17/2005 12:40:43Time to build: 94 minutes 7 secondsLast changed: 02/16/2005 19:39:07Last log entry: [JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients. Unit Tests: (1936) Total Errors and Failures: (27)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCaseunknownorg.jboss.test.jbossmq.test.LargeMessageUnitTestCaseunknownorg.jboss.test.jbossmq.test.OILConnectionUnitTestCasetestQueueMessageOrderorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestRequestReplyQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryQueueDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTemporaryTopicDeleteorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueSendorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationQueueBrowseorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestInvalidDestinationTopicPublishorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestErrorsTopicSubscribeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestCreateQueueorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestMessageListenerorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestApplicationServerStufforg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicsorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicNoLocalBounceorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorChangeorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestTopicSelectorNullOrEmptyorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendReceiveExpiredorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSendListenOutdatedorg.jboss.test.jbossmq.test.OILJBossMQUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (5)1.9.2.8modifiedejortserver/src/main/org/jboss/proxy/ejb/handle/StatefulHandleImpl.java[JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.1.5.2.4modifiedejortserver/src/main/org/jboss/proxy/ejb/StatefulSessionInterceptor.java[JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.1.9.2.7modifiedejortserver/src/main/org/jboss/proxy/ejb/handle/StatefulHandleImpl.javaSwitch over the SFSB handle to use the jndi strategy of the other handles.This is backwards compatible in the sense that the new code will work with older handles(as long as the default initial context produces the correct jndi handle to lookup the home).However, older clients won't be able to use the new handle because they tried to use theinvoker which is no longer present in the handle.Using the invoker was incorrect. Depending on the transport, it did not survive serverrestarts (which is the whole point of using a handle rather than an EJBObject).1.5.2.3modifiedejortserver/src/main/org/jboss/proxy/ejb/StatefulSessionInterceptor.javaSwitch over the SFSB handle to use the jndi strategy of the other handles.This is backwards compatible in the sense that the new code will work with older handles(as long as the default initial context produces the correct jndi handle to lookup the home).However, older clients won't be able to use the new handle because they tried to use theinvoker which is no longer present in the handle.Using the invoker was incorrect. Depending on the transport, it did not survive serverrestarts (which is the whole point of using a handle rather than an EJBObject).1.5.4.7modifiedejortsecurity/src/main/org/jboss/security/srp/SRPRemoteServer.javaThis exception can no longer occur
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1484) ClassCastException while creating JNDI SubContext
[ http://jira.jboss.com/jira/browse/JBAS-1484?page=comments#action_12315507 ] Jens Schumann commented on JBAS-1484: - Decompiled the code and found something like this: Hashtable map = System.getProperties(); map.put(Context.PROVIDER_URL, "jnp://host:port"); map.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory" ); Context ctx = new InitialContext(map); System.getProperties() causes the exception. > ClassCastException while creating JNDI SubContext > - > > Key: JBAS-1484 > URL: http://jira.jboss.com/jira/browse/JBAS-1484 > Project: JBoss Application Server > Type: Bug > Components: Naming > Versions: JBossAS-4.0.1 Final > Reporter: Jens Schumann > > > Creating a subcontext from a servlet failes with a ClassCastExeception. > java.lang.ClassCastException > at org.jboss.util.property.PropertyMap.remove(PropertyMap.java:198) > at org.jnp.interfaces.NamingContext.getEnv(NamingContext.java:1299) > at > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:867) > at > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:858) > at > javax.naming.InitialContext.createSubcontext(InitialContext.java:413) > The debugger shows a CompoundName instance for the value jnp.parsedName > instead of a String. I was unable to create a testcase because I don't know > how to place the CompoundName instance this far. > Will examine the issue more closely. -- 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: (JBAS-1484) ClassCastException while creating JNDI SubContext
[ http://jira.jboss.com/jira/browse/JBAS-1484?page=comments#action_12315506 ] Jens Schumann commented on JBAS-1484: - Still can't reproduce it with a simple test application ( because I don't have access to the sources causing the issue). If have tracked down the code placing the CompoundName to the ProperyMap. Its a simple new InitialContext() with a ProviderURL of jnp://host:port. Value is a CompoundName() is "" at org.jboss.util.property.PropertyMap.put(PropertyMap.java:162) at org.jnp.interfaces.NamingContext.parseNameForScheme(NamingContext.java:378) at org.jnp.interfaces.NamingContextFactory.getInitialContext(NamingContextFactory.java:41) 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) > ClassCastException while creating JNDI SubContext > - > > Key: JBAS-1484 > URL: http://jira.jboss.com/jira/browse/JBAS-1484 > Project: JBoss Application Server > Type: Bug > Components: Naming > Versions: JBossAS-4.0.1 Final > Reporter: Jens Schumann > > > Creating a subcontext from a servlet failes with a ClassCastExeception. > java.lang.ClassCastException > at org.jboss.util.property.PropertyMap.remove(PropertyMap.java:198) > at org.jnp.interfaces.NamingContext.getEnv(NamingContext.java:1299) > at > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:867) > at > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:858) > at > javax.naming.InitialContext.createSubcontext(InitialContext.java:413) > The debugger shows a CompoundName instance for the value jnp.parsedName > instead of a String. I was unable to create a testcase because I don't know > how to place the CompoundName instance this far. > Will examine the issue more closely. -- 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-1485) JMS ResourceAdapter makes unnecessary temporary delete requests
JMS ResourceAdapter makes unnecessary temporary delete requests --- Key: JBAS-1485 URL: http://jira.jboss.com/jira/browse/JBAS-1485 Project: JBoss Application Server Type: Bug Components: JMS service Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final Reporter: Adrian Brock Priority: Optional The JMS ResourceAdaptor keeps track of temporaries created on a connection (org.jboss.resource.adapter.jms.JMSSessionFactoryImpl) and deletes them. This is because we cannot expect the real JMS implementation to do this because the connection is pooled and not closed. However, if the user is deleting the temporaries themselves (good practice in terms of resource usage), the JMS ResourceAdapter does not know about this and tries to repeat the delete at connection.close(); Solution: Add some wrapping processing for the temporary queues and topics so we can trap temporary.delete(). That way we will know we don't need to do it on close() IMPORTANT: Invocations like send() or JMSMessage.setJMSReplyTo will also need to trap these destinations to do the necessary wrapping/unwrapping. It is also possible to retrieve a temporary destination with Session.createQueue/Topic. -- 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: (JBAS-1476) Need to include a notion of cluster instance in the cluster view
[ http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315505 ] Adrian Brock commented on JBAS-1476: We do need the GUID agreed across the cluster. This is what differentiates the particular instantiation of the cluster (similar to a java object instance). Rather than the Partition name, which identifies a logical group of servers that behaves as one server to the client (similar to a java class). The notion of partition name survives across restarts of the entire cluster and exists for all time in the client configuration. e.g. I want to use the JMSPartition Where the GUID only survives while there is a cluster in existance. This whole problem is really a corner case in that in principle the cluster should always be in existance. The only time this processing is required is: 1) Somebody reboots all nodes in a cluster, starting a new instance of the partition 2) Somebody moves the client to a different physical cluster with the same logical partition name. > Need to include a notion of cluster instance in the cluster view > > > Key: JBAS-1476 > URL: http://jira.jboss.com/jira/browse/JBAS-1476 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Priority: Critical > > > We need to include a notion of cluster instance in the cluster view id > to avoid at least the following scenario: > Client serializes a handle to a cluster which is at cluster view 22 > Handle contains key DefaultPartition/HAJNDI/22 > The cluster is totally restarted meaning the view reverts back to one. > The client now has a view id > DefaultPartition/HAJNDI/1 > The client deserializes the handle, which will overwrite the correct cluster > view with the old invalid view. > > This will also avoid the problem where a client talks to different clusters > with the same partition name. > > Proposed solution: > 1) At cluster formation (first node in cluster), create a cluster instance > GUID > 2) At cluster join (second+ node in cluster) get the GUID from the coordinator > 3) Include this GUID in cluster view keys, i.e. > GUID/DefaultPartition/HAJNDI/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 Portal] - Re: Init Param
thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866971#3866971 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866971 --- 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-1476) Need to include a notion of cluster instance in the cluster view
[ http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315503 ] Adrian Brock commented on JBAS-1476: I think the merge problem can be easily resolved by changes in the cluster family processing at the invoker client. e.g. Client is talking to HAJNDI GUID1/HAJNDI/4 (instance, service, view) It passes this info on the request and gets back a new view because the cluster has merged with another cluster that has decided it will contain the co-ordinator. GUID2/HAJNDI/3 So not only do we update the view, we also change the key from GUID1 to GUID2 to reflect the merge. i.e. The GUID1 views are now invalid and it will use the GUID2 views from now on. We can even add processing to the family where if a different proxy asks for the GUID1 view, it actually gets back the more up-to-date GUID2 view. > Need to include a notion of cluster instance in the cluster view > > > Key: JBAS-1476 > URL: http://jira.jboss.com/jira/browse/JBAS-1476 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Priority: Critical > > > We need to include a notion of cluster instance in the cluster view id > to avoid at least the following scenario: > Client serializes a handle to a cluster which is at cluster view 22 > Handle contains key DefaultPartition/HAJNDI/22 > The cluster is totally restarted meaning the view reverts back to one. > The client now has a view id > DefaultPartition/HAJNDI/1 > The client deserializes the handle, which will overwrite the correct cluster > view with the old invalid view. > > This will also avoid the problem where a client talks to different clusters > with the same partition name. > > Proposed solution: > 1) At cluster formation (first node in cluster), create a cluster instance > GUID > 2) At cluster join (second+ node in cluster) get the GUID from the coordinator > 3) Include this GUID in cluster view keys, i.e. > GUID/DefaultPartition/HAJNDI/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] Created: (JBAS-1484) ClassCastException while creating JNDI SubContext
ClassCastException while creating JNDI SubContext - Key: JBAS-1484 URL: http://jira.jboss.com/jira/browse/JBAS-1484 Project: JBoss Application Server Type: Bug Components: Naming Versions: JBossAS-4.0.1 Final Reporter: Jens Schumann Creating a subcontext from a servlet failes with a ClassCastExeception. java.lang.ClassCastException at org.jboss.util.property.PropertyMap.remove(PropertyMap.java:198) at org.jnp.interfaces.NamingContext.getEnv(NamingContext.java:1299) at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:867) at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:858) at javax.naming.InitialContext.createSubcontext(InitialContext.java:413) The debugger shows a CompoundName instance for the value jnp.parsedName instead of a String. I was unable to create a testcase because I don't know how to place the CompoundName instance this far. Will examine the issue more closely. -- 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: JBoss Portal TransactionFilter.java:85
1) you should install 4.0.0 final 2) we need more of the stack trace View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866969#3866969 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866969 --- 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] - JBoss Portal TransactionFilter.java:85
I have installed jboss-4.0.0RC2 and jboss-portal-2.0-alpha When i navigate to http://localhost:8080/portal I get the Error: | javax.servlet.ServletException: javax.servlet.ServletException: Servlet execution threw an exception | org.jboss.portal.core.servlet.TransactionFilter.doFilter(TransactionFilter.java:85) | | | root cause | | org.jboss.portal.common.transaction.BusinessException: javax.servlet.ServletException: Servlet execution threw an exception | org.jboss.portal.common.transaction.Demarcator.requiresNew(Demarcator.java:58) | org.jboss.portal.core.servlet.TransactionFilter.doFilter(TransactionFilter.java:74) | | | | The other Topics about this Question did not help me. | | Thank you for your Help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866968#3866968 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866968 --- 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-1383) findByPrimaryKey error
[ http://jira.jboss.com/jira/browse/JBAS-1383?page=history ] Alexey Loubyansky closed JBAS-1383: --- Resolution: Rejected As Scott said, this is the driver's issues. A workaround would be to turn prepared statement cache off. > findByPrimaryKey error > -- > > Key: JBAS-1383 > URL: http://jira.jboss.com/jira/browse/JBAS-1383 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Linux, postgres > Reporter: Willy Ong > Assignee: Alexey Loubyansky > Priority: Minor > > > Hi, > I encountered the following error when I tried to run to deploy a 3.2.x jar > file for jboss 4.0.1. I assumed it was due to some incompatibility with the > Java specifications. But later on, I was able to deploy it successfully on > jboss 4.0.0. All the files used are the same, i.e. the jar, database, jdbc > driver etc. The only difference is the App Server. Is this a bug? Thanks. > 10:34:12,628 ERROR [ReapAccessLog#findByPrimaryKey] Find failed > org.postgresql.util.PSQLException: The backend currently does not support > this feature. > at > org.postgresql.jdbc2.AbstractJdbc2Statement.getFetchDirection(AbstractJdbc2Statement.java:133) > at > org.jboss.resource.adapter.jdbc.CachedPreparedStatement.(CachedPreparedStatement.java:62) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:349) > at > org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:205) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:190) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:128) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.execute(JDBCFindByPrimaryKeyQuery.java:128) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:47) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:589) > at > org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:300) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:298) > at > org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1086) > at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:663) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.invocation.Invocation.performCall(Invocation.java:345) > at > org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1113) > at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90) > at > org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:192) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:212) > at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90) > at > org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:117) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28) > at > org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:41) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:109) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:313) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:126) > at > org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:101) > at > org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:121) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93) > at > org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:508) > at org.jboss.ejb.Container.invoke(Container.java:891) > at > org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:342) > at > org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:118) >
[JBoss-dev] [JBoss JIRA] Commented: (JBPORTAL-177) Blog portlet
[ http://jira.jboss.com/jira/browse/JBPORTAL-177?page=comments#action_12315501 ] Thomas Heute commented on JBPORTAL-177: --- Sorry to Bruce, i missed your comment. If Blojsom is using the BSD Licence, the Blojsom portlet should be BSD Licenced. It was just an idea. A LGPL licence would be better, so maybe there are part of LGPL code out there that could be reused for a blog portlet. The author of blojsom was in touch with us, he is willing to see such an integration. There are different possibilities for a blog portlet: -> From scratch (LGPL) -> Using LGPL components -> Using Blojsom (BSD Licensed) The last option will make us being able to use the existing modules of blojsom. Integrating blojsom, means to transform the servlet based stuff into portlet based stuff (admin and display). Ideally it should handle both and work can be contribute back to blojsom. The backend should be kept. One thing to implement is to store the data in a database and not as a filesystem like it is right now (blojsom let us do that). One need to make a database storing mechanism, it could be contributed back to blojsom (more contribution and less fork). Using a database, will allow the Blog portlet to run in a cluster. > Blog portlet > > > Key: JBPORTAL-177 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-177 > Project: JBoss Portal > Type: Feature Request > Reporter: Ivelin Ivanov > Assignee: Thomas Heute > > > Maybe an integration with blojsom. > http://wiki.blojsom.com/wiki/display/blojsom/About+blojsom -- 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: Init Param
yes it is based on the preferences API and not init param. the main reason is that all the instances are execute in the same portlet instances and share the same PortletConfig object, so that would not make sense to have an init param per instance. The only thing that distinguish two instances are the preferences. Look in the portlet-instances.xml descriptor in portal-core.war file, the preferences portlet has its preferences overidden. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866967#3866967 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866967 --- 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] - Init Param
There is a tag init-param that can be used in portlet.xml to initialize a portlet class. But what I need is some tag to pass a param to initialize a portlet instance in the portlet-instance.xml. is there such a tag? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866966#3866966 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866966 --- 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/Tomcat Integration] - Re: JBAS-1468: Add support for IP address reporting inside a
There is no explicit dependency on the servlet container or servlet api in the security module and none should be added to avoid propagation of an existing problem of cross module dependencies. There is an implicit dependency due to the JACC service's dependency on the JACC permission classes, and this service should in fact be moved out of the security module to clean this up. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866961#3866961 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866961 --- 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-77) Remove jbpm milestone
[ http://jira.jboss.com/jira/browse/JBPM-77?page=history ] Juan Cantu updated JBPM-77: --- Description: Move the jbpm Milestone functionality from the core engine to the bpel package. Environment: Original Estimate: 57600 Remaining Estimate: 57600 Version: 3.0 DR 1 Component: BPEL Core Engine > Remove jbpm milestone > - > > Key: JBPM-77 > URL: http://jira.jboss.com/jira/browse/JBPM-77 > Project: JBoss jBPM > Type: Sub-task > Components: Core Engine, BPEL > Versions: 3.0 DR 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 2 days > Remaining: 2 days > > Move the jbpm Milestone functionality from the core engine to the bpel > package. -- 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-77) Remove jbpm milestone
Remove jbpm milestone - Key: JBPM-77 URL: http://jira.jboss.com/jira/browse/JBPM-77 Project: JBoss jBPM Type: Sub-task Reporter: Juan Cantu Assigned to: 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] [JBoss JIRA] Resolved: (JBPM-74) transformation from bpel 1.1 to 2.0
[ http://jira.jboss.com/jira/browse/JBPM-74?page=history ] Juan Cantu resolved JBPM-74: Resolution: Done Fix Version: 3.0 DR 1 > transformation from bpel 1.1 to 2.0 > --- > > Key: JBPM-74 > URL: http://jira.jboss.com/jira/browse/JBPM-74 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: 3.0 DR 1 > Environment: jaxp 1.1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: 3.0 DR 1 > > Original Estimate: 3 days >Time Spent: 3 days > Remaining: 0 minutes > > Use xslt to transform bpel archives (process definition, wsdl extensions) > from bpel 1.1 to 2.0 version. -- 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/Tomcat Integration] - Re: JBAS-1468: Add support for IP address reporting inside a
I think I have the complete picture, I'll start coding tonight. Just one question: Why not add this new CallbackHandler to the SecurityAssociationHandler? Thanks, Ricardo ArgÃello View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866960#3866960 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866960 --- 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_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315498 ] Marshall Culpepper commented on JBIDE-116: -- Run XDoclet and Run Packaging are both working flawlessly (and I can see the ClearCase menu in plain sight in the menu bar). It might be an issue of not having ClearCase installed before I see this error, but John Emerson has reported that he sees this error whether or not ClearCase is actually "connected". Maybe we'll try this w/ VSS. I'll be shooting you an email > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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-1483) Black box testing for http session (with and without replication)
Black box testing for http session (with and without replication) - Key: JBAS-1483 URL: http://jira.jboss.com/jira/browse/JBAS-1483 Project: JBoss Application Server Type: Feature Request Components: Clustering Reporter: Ben Wang Assigned to: Ryan Campbell Fix For: JBossAS-5.0 Alpha While talking with Ivelin, I think we need to have more black box testing for http requests with and without replication. Every feature in single node should also be supported bu clustering, plus some additional use caes for clustering failover. But currently, I only have limited unit test case for clustering in term of failing over. So here is two main steps: 1. Create an automated black box testing suite for http session request in a single node. We can use some tool to do this. Question is we need to define the tests. 2. Currently, Tomcat has a whole suite of unit testing on http session. We should look into that to see if we can re-use some of it in our own Tomcat module. 3. Create test cases for fail-over. I can help to define the set here. -- 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: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315497 ] ericeberry commented on JBIDE-116: -- No. I typically saw the problem with Run XDoclet not Run Packaging. > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315496 ] Marshall Culpepper commented on JBIDE-116: -- Turns out I accidentally downloaded the linux version of the ClearCase Adapter. I've downloaded the windows adapater, installed it, and I'm able to run Packaging without flaws (no errors in the Error Log) on a few test projects. Are there any special properties set on the project before you run packaging? > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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] - Re: Callbacks
Added method to purge. Will be a while before have code for detecting crashed clients. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866956#3866956 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866956 --- 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: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315495 ] ericeberry commented on JBIDE-116: -- I called again. This time they told me something different. There is not a trial version. They did say that there is a special developer version that is supposed to be cheaper than the regular version. They also said that there is a 30-day money back guarantee so maybe you could purchase the license then return it. Here is another option. Since the Visual Source Safe plugin was showing the same conflict, if you contact me at [EMAIL PROTECTED], I can get you a copy of VisualSourceSafe to try out. > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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 Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050217105700 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 02/17/2005 10:57:00Time to build: 24 minutes 21 secondsLast changed: 02/17/2005 10:47:26Last log entry: Rollbacked JBCache-90 fix untill next release Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.10modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/eviction/AopLRUPolicyUnitTestCase.javaRollbacked JBCache-90 fix untill next release1.42modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaJBCACHE-90 fix. Let's wait untill 1.2.1 is out
[JBoss-dev] [JBoss JIRA] Commented: (JBPORTAL-177) Blog portlet
[ http://jira.jboss.com/jira/browse/JBPORTAL-177?page=comments#action_12315493 ] Louis Richardson commented on JBPORTAL-177: --- Blojsom uses the BSD licence, is it not compatible with LGPL. I wonder. > Blog portlet > > > Key: JBPORTAL-177 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-177 > Project: JBoss Portal > Type: Feature Request > Reporter: Ivelin Ivanov > Assignee: Thomas Heute > > > Maybe an integration with blojsom. > http://wiki.blojsom.com/wiki/display/blojsom/About+blojsom -- 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: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315494 ] Marshall Culpepper commented on JBIDE-116: -- I called and was asked for all my information.. The sales person on the other end of the line told me there was no such thing as a trial version of ClearCase or ClearCase LT should I try calling again? > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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: (JBPTL-15) Use java.util.regex
[ http://jira.jboss.com/jira/browse/JBPTL-15?page=history ] Julien Viet resolved JBPTL-15: -- Resolution: Done Fix Version: 2.0 Beta 2 2.0 Final > Use java.util.regex > --- > > Key: JBPTL-15 > URL: http://jira.jboss.com/jira/browse/JBPTL-15 > Project: JBoss Portal > Type: Task > Reporter: Julien Viet > Assignee: Julien Viet > Priority: Minor > Fix For: 2.0 Beta 1, 2.0 Final, 2.0 Beta 2 > > > Get rid of jregex and use JDK-1.4 regular expression facilities -- 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: Portlet Size
Cheers. Thanks for that. i'll look into it see what I can do View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866945#3866945 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866945 --- 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-1482) java deadlock during starutp
[ http://jira.jboss.com/jira/browse/JBAS-1482?page=history ] David updated JBAS-1482: Attachment: dead-lock-during-startup.log > java deadlock during starutp > > > Key: JBAS-1482 > URL: http://jira.jboss.com/jira/browse/JBAS-1482 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-3.2.7 Final > Environment: Red Hat Enterprise Linux ES release 3 (Taroon Update 2) > java 1.4.2_05 > Reporter: David > Priority: Minor > Attachments: dead-lock-during-startup.log > > > Noticed very slow startup, did kill -3, found the following. > Found one Java-level deadlock: > = > "MessageDispatcher up processing thread": > waiting to lock monitor 0xa4d393d4 (object 0xb9a6d310, a > org.jboss.system.ServiceController), > which is held by "main" > "main": > waiting to lock monitor 0x080d0854 (object 0xba632828, a java.util.HashMap), > which is held by "MessageDispatcher up processing thread" > Java stack information for the threads listed above: > === -- 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-1482) java deadlock during starutp
java deadlock during starutp Key: JBAS-1482 URL: http://jira.jboss.com/jira/browse/JBAS-1482 Project: JBoss Application Server Type: Bug Versions: JBossAS-3.2.7 Final Environment: Red Hat Enterprise Linux ES release 3 (Taroon Update 2) java 1.4.2_05 Reporter: David Priority: Minor Attachments: dead-lock-during-startup.log Noticed very slow startup, did kill -3, found the following. Found one Java-level deadlock: = "MessageDispatcher up processing thread": waiting to lock monitor 0xa4d393d4 (object 0xb9a6d310, a org.jboss.system.ServiceController), which is held by "main" "main": waiting to lock monitor 0x080d0854 (object 0xba632828, a java.util.HashMap), which is held by "MessageDispatcher up processing thread" Java stack information for the threads listed above: === -- 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/Tomcat Integration] - Re: JBAS-1468: Add support for IP address reporting inside a
The login module needs to request the information required for authentication using a custom callback handler. Then you need to install a custom javax.security.auth.callback.CallbackHandler that can provide the current request header info based on a Valve and thread local. A custom CallbackHandler can be installed using the CallbackHandlerClassName attribute of the org.jboss.security.plugins.JaasSecurityManagerService. The existing IPAddressValve should really just be generalized to save the current HttpServletRequest. The custom CallbackHandler should be in the org.jboss.web.tomcat.security package and it should extend the default org.jboss.security.auth.callback.SecurityAssociationHandler and delegate to it any Callback it does not understand. There needs to be a unit test added to the testsuite. Look at how the JACC unit tests run on a custom configuration of jboss to see how the tests need to be setup to use the customized JaasSecurityManagerService configuration. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866944#3866944 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866944 --- 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-86) invalidate() across cluster
[ http://jira.jboss.com/jira/browse/JBCACHE-86?page=comments#action_12315492 ] Daniel Gredler commented on JBCACHE-86: --- Do you mean to say that nodeEvicted(Fqn) is going to be called whenever a node gets invalidated? > invalidate() across cluster > --- > > Key: JBCACHE-86 > URL: http://jira.jboss.com/jira/browse/JBCACHE-86 > Project: JBoss Cache > Type: Feature Request > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Callbacks
I wanted the invoker handler generating the callback to know that it got thrown away. So when they send D, will get an exception thrown back (synchronously). They can either try to deal with it or throw it away. If throw away A and keep D, woudl be more difficult for the invoker handler to have any context about the callback being thrown away (A), even if it is included in the exception thrown. No way to purge other than deleting from disk currently. Guess will add a method for this, but won't be used until add code to identify when callback client is dead (or removed). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866939#3866939 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866939 --- 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-1383) findByPrimaryKey error
[ http://jira.jboss.com/jira/browse/JBAS-1383?page=comments#action_12315489 ] Scott M Stark commented on JBAS-1383: - So the driver does not support the standard Statement.getFetchDirection call. I would suggest looking for a driver that does. > findByPrimaryKey error > -- > > Key: JBAS-1383 > URL: http://jira.jboss.com/jira/browse/JBAS-1383 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Linux, postgres > Reporter: Willy Ong > Assignee: Alexey Loubyansky > Priority: Minor > > > Hi, > I encountered the following error when I tried to run to deploy a 3.2.x jar > file for jboss 4.0.1. I assumed it was due to some incompatibility with the > Java specifications. But later on, I was able to deploy it successfully on > jboss 4.0.0. All the files used are the same, i.e. the jar, database, jdbc > driver etc. The only difference is the App Server. Is this a bug? Thanks. > 10:34:12,628 ERROR [ReapAccessLog#findByPrimaryKey] Find failed > org.postgresql.util.PSQLException: The backend currently does not support > this feature. > at > org.postgresql.jdbc2.AbstractJdbc2Statement.getFetchDirection(AbstractJdbc2Statement.java:133) > at > org.jboss.resource.adapter.jdbc.CachedPreparedStatement.(CachedPreparedStatement.java:62) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:349) > at > org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:205) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:190) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:128) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQuery.execute(JDBCFindByPrimaryKeyQuery.java:128) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntityCommand.execute(JDBCFindEntityCommand.java:47) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntity(JDBCStoreManager.java:589) > at > org.jboss.ejb.plugins.CMPPersistenceManager.findEntity(CMPPersistenceManager.java:300) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:298) > at > org.jboss.ejb.EntityContainer.findSingleObject(EntityContainer.java:1086) > at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:663) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.jboss.invocation.Invocation.performCall(Invocation.java:345) > at > org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1113) > at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90) > at > org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:192) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:212) > at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:90) > at > org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:117) > at > org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61) > at > org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28) > at > org.jboss.ejb.plugins.CallValidationInterceptor.invokeHome(CallValidationInterceptor.java:41) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:109) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:313) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:126) > at > org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:101) > at > org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:121) > at > org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93) > at > org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:508) > at org.jboss.ejb.Container.invoke(Container.java:891) > at > org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:342) > at > org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.
[JBoss-dev] [JBoss JIRA] Commented: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315488 ] ericeberry commented on JBIDE-116: -- I just talked with IBM/Rational. Call them at 877-426-3774 ext. 104CBW61. Ask for a trial version of ClearCase LT. > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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-Bugs-1124805 ] java deadlock during starutp
Bugs item #1124805, was opened at 2005-02-17 15:19 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=1124805&group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: David Boon (davidmboon) Assigned to: Nobody/Anonymous (nobody) Summary: java deadlock during starutp Initial Comment: Noticed very slow startup, did kill -3 and found javadeadlock. I've pasted the relevant dead lock, and attached the entire thread dump. Found one Java-level deadlock: = "MessageDispatcher up processing thread": waiting to lock monitor 0xa4d393d4 (object 0xb9a6d310, a org.jboss.system.ServiceController), which is held by "main" "main": waiting to lock monitor 0x080d0854 (object 0xba632828, a java.util.HashMap), which is held by "MessageDispatcher up processing thread" Java stack information for the threads listed above: === "MessageDispatcher up processing thread": at org.jboss.system.ServiceController.install(ServiceController.java:199) - waiting to lock <0xb9a6d310> (a org.jboss.system.ServiceController) at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:204) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:783) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:775) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54) at org.jboss.mx.server.Invocation.invoke(Invocation.java:82) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473) at org.jboss.ha.singleton.HASingletonController.invokeSingletonMBeanMethod(HASingletonController.java:114) at org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:63) at org.jboss.ha.singleton.HASingletonSupport.makeThisNodeMaster(HASingletonSupport.java:141) at org.jboss.ha.singleton.HASingletonSupport.partitionTopologyChanged(HASingletonSupport.java:118) at org.jboss.ha.jmx.HAServiceMBeanSupport$1.replicantsChanged(HAServiceMBeanSupport.java:197) at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:699) - locked <0xba632828> (a java.util.HashMap) at org.jboss.ha.framework.server.DistributedReplicantManagerImpl._remove(DistributedReplicantManagerImpl.java:509) at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236) at org.jboss.ha.framework.server.HAPartitionImpl.handle(HAPartitionImpl.java:828) at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615) at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.ja
[JBoss-dev] [JBossCache] - Re: Clarification needed on LRUPolicy and timeToLiveSeconds
So you're saying that TreeCache.get(Fqn) is not safe to be used at all? In my case I need an efficient and safe way to walk through the tree. My scenario is that given a starting node, I then need to do a depth first walk through the tree. I need to acquire read locks on any/all nodes I visit, but don't need to track visitation (I've worked around my original issue by making my custom eviction policy a little smarter). Can you advise then on the most efficient (safe) way to do this? I see how I could use TreeCache.getChildrenNames(Fqn) but this seems pretty inefficient as each call in turn uses findNode(Fqn) which walks through the tree from the root. Since my tree is pretty deep and wide, that spells trouble. Is there a way that I can do the locking myself by using one of Node's locking methods? Finally, aAre there any plans to refactor out the truly public methods of TreeCache into an interface? This would certainly help useability and encourage us users to stay away from unsafe methods. You could then have a single base implementation providing the additional internal helper methods. If you then have to do some funky casting internally that breaks the interface encapsulation then that is far preferable to leaving non-safe methods out there that will go away in the future. Another suggestion would be to use the Javadoc @exclude tag on the non-public methods so they don't get included in the javadocs. Thanks, Brian. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866929#3866929 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866929 --- 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-38) Deprecate DistributedTree,ReplicatedTree,DistrHashtable,ReplHashtable
Deprecate DistributedTree,ReplicatedTree,DistrHashtable,ReplHashtable - Key: JGRP-38 URL: http://jira.jboss.com/jira/browse/JGRP-38 Project: JGroups Type: Task Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.8 -- 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-37) TCP should generate a SUSPECT event when connection is closed
TCP should generate a SUSPECT event when connection is closed - Key: JGRP-37 URL: http://jira.jboss.com/jira/browse/JGRP-37 Project: JGroups Type: Feature Request Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.3 See how this is compatible for regular socket closes (e.g. due to reaping idle connections) -- 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: (JBPORTAL-201) NPE if a portlet declares a locale that is not supported by the OS
[ http://jira.jboss.com/jira/browse/JBPORTAL-201?page=history ] Julien Viet resolved JBPORTAL-201: -- Resolution: Done Fix Version: 2.0 Beta 2 2.0 Final applied patch > NPE if a portlet declares a locale that is not supported by the OS > -- > > Key: JBPORTAL-201 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-201 > Project: JBoss Portal > Type: Bug > Components: Portal Core > Versions: 2.0 Alpha > Reporter: Thomas Heute > Assignee: Julien Viet > Fix For: 2.0 Beta 1, 2.0 Final, 2.0 Beta 2 > > > Woodler found an issue with locale support: if the OS doesn't support a > locale that is defined in the portlet.xml , the deployment of the app fails > with a NPE. -- 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] - Re: Callbacks
A couple of comments/suggestions: 1) You should think about purging older callbacks first, as opposed to new ones. You mention that if you have Callback A, B, C in memory. If D comes in and it must be persisted, but it can't (via NullPersister), its gets thrown away. That means the newest callbacks are getting thrown away. Would it be better to throw away the oldest callback (presumably less important then the newest callback)? Just a thought. Not sure how you would do it though - its much easier doing it the current way - that is just throw away the newest one (by simply ignoring it - via NullPersister). 2) How do you purge the persistent store? I didn't see anything that describes what happens if the client never comes back for its callbacks. One scenario I can think of is if the client and server are on the same box and the box goes down. The box comes up, the server starts, but the client does not restart. Its dead. How do you clean up the orphaned persistent store? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866927#3866927 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866927 --- 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] - Add new portlet with access database
Hi all, I want to add to the jboss portal a portlet which need an access to database. How must I proceed ? Like the forum portlet, this portlet need an user_id (poster in the forum). But how run the relation between jbp_poster of jbp_forum_topics with jbp_uid of jbp_users ? Is this relation explicite ? And for my new portlet, how must I proceed, do I need to use LDAP ? thanks for your help. lnhf View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866926#3866926 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866926 --- 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: Maximize behavior: Nukes vs Rest of the World
JSR already has a window state, MAXIMIZE, to handle this. We need a special window state, SEMI_MAXIMIZE to handle the current behavior. A basic problem at the moment is that you cannot define a page that does not have a default window (null pointer exceptions). Once you have a default window it becomes the main fragment even if it is not maximized. Try using Pluto, Jetspeed, Liferay, WebSphere, Oracle, BEA. I'm pretty sure they all behave the same way. When you maximize a portlet, it gets the entire portlet region to itself, when you switch it back to normal, you get the other portlets back again. I'll send you some screen shots of my styles and the behavior. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866924#3866924 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866924 --- 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: Forcing eviction of child nodes
I added this to the roadmap, for 1.3, but this may get pushed back to 1.4, depending on our workload: http://jira.jboss.com/jira/browse/JBCACHE-92 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866922#3866922 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866922 --- 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-92) Eviction of entire subtrees
[
http://jira.jboss.com/jira/browse/JBCACHE-92?page=comments#action_12315486 ]
Bela Ban commented on JBCACHE-92:
-
1. Are there any plans in the roadmap to support the kind of forceful eviction
policy I need in JBoss Cache?
2. Are there any side effects with me implementing a new LRUPolicy that
forcefully evicts a node and its children?
3. Any advice on how to do #2? Off the top of my head I would probably create a
new CascadingLRUPolicy class that overrides the evict(Fqn) method to accomplish
what I need to do. The new evict() implementation would be largely a copy/paste
of TreeCache._evict() but thatt doesn't check for children. Here's a quick
mock-up of what the new CascadingLRUPolicy.evict(Fqn) implemention might look
like:
public void _evict(Fqn fqn) throws Exception {
if(!cache_.exists(fqn)) return; // node does not exist. Maybe it has
been recursively removed.
// use remove method now if there is a child node. Otherwise, it is
removed
boolean create_undo_ops = false;
boolean sendNodeEvent = false;
boolean eviction=true;
_remove(null, fqn, create_undo_ops, sendNodeEvent, eviction);
}
Thanks in advance for any/all help.
Regards,
Brian Dueck
> Eviction of entire subtrees
> ---
>
> Key: JBCACHE-92
> URL: http://jira.jboss.com/jira/browse/JBCACHE-92
> Project: JBoss Cache
> Type: Feature Request
> Versions: 1.2
> Reporter: Bela Ban
> Assignee: Ben Wang
> Fix For: 1.3
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBCACHE-89) Allow Specifying Custom Interceptors in XML Configuration
[ http://jira.jboss.com/jira/browse/JBCACHE-89?page=history ]
Bela Ban updated JBCACHE-89:
Fix Version: 1.3
This feature is planned. Currently, one has to add their interceptor(s)
dynamically using the getInterceptors() method
> Allow Specifying Custom Interceptors in XML Configuration
> -
>
> Key: JBCACHE-89
> URL: http://jira.jboss.com/jira/browse/JBCACHE-89
> Project: JBoss Cache
> Type: Feature Request
> Versions: 1.2
> Reporter: Daniel Gredler
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 1.3
>
>
> It would be nice to be able to add interceptors via the XML configuration
> files. Indeed, in TreeCache.java the following comment exists, which may
> indicate that this feature is already planned:
> // Create the interceptors in the correct order (later to be defined in
> XML file)
> createInterceptorChain();
> A possible example configuration would be:
>
>
> name="jboss.cache:service=TreeCache">
>...
>
> com.foo.project.MyInterceptor
>
>...
>
>
> Something along the lines of the following method would then be able to add
> the custom interceptors (in TreeCache.java):
>public void setInterceptors(Element interceptors) throws Exception {
> NodeList list = interceptors.getChildNodes();
> for(int i = 0; i < list.getLength(); i++) {
> org.w3c.dom.Node node = list.item(i);
> if(node.getNodeType() != org.w3c.dom.Node.ELEMENT_NODE)
> continue;
> NodeList children = node.getChildNodes();
> if(children.getLength() != 1)
> continue;
> org.w3c.dom.Node childNode = list.item(0);
> if(childNode.getNodeType() != org.w3c.dom.Node.TEXT_NODE)
> continue;
> String className = childNode.getNodeValue();
> if(className == null || className.length() == 0)
> continue;
> Interceptor interceptor = createInterceptor(className);
> addInterceptor(interceptor_chain, interceptor);
> }
>}
--
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: (JBCACHE-86) invalidate() across cluster
[ http://jira.jboss.com/jira/browse/JBCACHE-86?page=comments#action_12315484 ] Bela Ban commented on JBCACHE-86: - There is a nodeEvicted(Fqn) callback > invalidate() across cluster > --- > > Key: JBCACHE-86 > URL: http://jira.jboss.com/jira/browse/JBCACHE-86 > Project: JBoss Cache > Type: Feature Request > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - with access database
Hi all, I want to add to the jboss portal a portlet which need an access to database. How must I proceed ? Like the forum portlet, this portlet need an user_id (poster in the forum). But how run the relation between jbp_poster of jbp_forum_topics with jbp_uid of jbp_users ? Is this relation explicite ? And for my new portlet, how must I proceed, do I need to use LDAP ? thanks for your help. lnhf View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866920#3866920 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866920 --- 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-88) Add RemoteDelegatingCacheLoader
[ http://jira.jboss.com/jira/browse/JBCACHE-88?page=history ] Bela Ban updated JBCACHE-88: Fix Version: 1.3 > Add RemoteDelegatingCacheLoader > --- > > Key: JBCACHE-88 > URL: http://jira.jboss.com/jira/browse/JBCACHE-88 > Project: JBoss Cache > Type: Feature Request > Versions: 1.2 > Reporter: Daniel Gredler > Assignee: Bela Ban > Priority: Minor > Fix For: 1.3 > Attachments: jbosscache_patch_remote_delegating_cacheloader.txt > > > The CacheLoader infrastructure is meant to allow lazy initialization via a > cache hierarchy. This is possible within a single VM thanks to > DelegatingCacheLoader. This functionality is not available, however, across > VM's. A possible approach is to make DelegatingCacheLoader abstract and add > two subclasses: LocalDelegatingCacheLoader and RemoteDelegatingCacheLoader. > Thoughts? Comments? -- 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.809 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050217075907Lbuild.809 BUILD COMPLETE - build.809Date of build: 02/17/2005 07:59:07Time to build: 22 minutes 21 secondsLast changed: 02/17/2005 07:38:04Last log entry: revamped Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.9modifiedbelabantestsuite/src/main/org/jboss/test/cache/stress/EvictionLocalStressTestCase.javarevamped1.66modifiedbelabancache/src/main/org/jboss/cache/Node.javaadded javadoc1.1addedbelabancache/src/main/org/jboss/cache/tests/ReadWriteLockTest.javanew test1.65modifiedbelabancache/src/main/org/jboss/cache/Node.javaadded PRINT_LOCK_DETAILS
[JBoss-dev] [JBoss JIRA] Created: (JGRP-36) TCP:PING, TCP transport combined with multicast discovery
TCP:PING, TCP transport combined with multicast discovery - Key: JGRP-36 URL: http://jira.jboss.com/jira/browse/JGRP-36 Project: JGroups Type: Feature Request Reporter: Bela Ban Assigned to: Bela Ban Fix For: 2.2.9 Use IP multicast for discovery/merging, but TCP for transport -- 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: (JBAS-1481) HAPartitionImpl.viewAccepted()
[
http://jira.jboss.com/jira/browse/JBAS-1481?page=comments#action_12315483 ]
Bela Ban commented on JBAS-1481:
Here's the class that notifies listeners of view changes (in HAPartitionImpl):
private class AsynchViewChangeHandler implements Runnable
{
public void run()
{
log.debug("Begin AsynchViewChangeHandler");
while( true )
{
try
{
ViewChangeEvent event = (ViewChangeEvent)
asynchViewChanges.take();
notifyListeners(asynchListeners, event.viewId, event.allMembers,
event.deadMembers, event.newMembers, event.originatingGroups);
}
catch(InterruptedException e)
{
log.debug("AsynchViewChangeHandler interrupted", e);
break;
}
}
log.debug("End AsynchViewChangeHandler");
}
}
If that thread is interrupted, it won't notify listeners of view changes !
We start it in startPartition(), so 2 problems:
#1: the thread might get interrupted when it is *not* running yet (or anymore).
Next time it runs, the interrupt flag is still set, therefore it will terminate
!
#2: on redeploy, we get 2 threads !
> HAPartitionImpl.viewAccepted()
> --
>
> Key: JBAS-1481
> URL: http://jira.jboss.com/jira/browse/JBAS-1481
> Project: JBoss Application Server
> Type: Bug
> Components: Clustering
> Reporter: Bela Ban
>
>
> Here's the end of the method:
> // Put the view change to the asynch queue
> this.asynchViewChanges.put(event); // #1
> // Broadcast the new view to the synchronous view change listeners
> this.notifyListeners(listeners, event.viewId, event.allMembers, // #2
>event.deadMembers, event.newMembers, event.originatingGroups);
> #1 puts the view change on a queue, where another thread picks it up and
> invokes notifyListeners()
> #2 does exactly the same, but *blocking* (not on a separate thread)
> We should remove #2 ? It is duplicate, dangerous code
--
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-1481) HAPartitionImpl.viewAccepted()
HAPartitionImpl.viewAccepted() -- Key: JBAS-1481 URL: http://jira.jboss.com/jira/browse/JBAS-1481 Project: JBoss Application Server Type: Bug Components: Clustering Reporter: Bela Ban Here's the end of the method: // Put the view change to the asynch queue this.asynchViewChanges.put(event); // #1 // Broadcast the new view to the synchronous view change listeners this.notifyListeners(listeners, event.viewId, event.allMembers, // #2 event.deadMembers, event.newMembers, event.originatingGroups); #1 puts the view change on a queue, where another thread picks it up and invokes notifyListeners() #2 does exactly the same, but *blocking* (not on a separate thread) We should remove #2 ? It is duplicate, dangerous code -- 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: Maximize behavior: Nukes vs Rest of the World
that would need the addition of a special window state called exclusive for instance. could you describe the behaviour it would have ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866918#3866918 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866918 --- 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: (JBPORTAL-97) Clustered or invalidatable cache
[ http://jira.jboss.com/jira/browse/JBPORTAL-97?page=history ] Julien Viet resolved JBPORTAL-97: - Resolution: Done Fix Version: 2.0 Beta 2 2.0 Final use jboss cache invalidation manager to relay cache invalidations. > Clustered or invalidatable cache > > > Key: JBPORTAL-97 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-97 > Project: JBoss Portal > Type: Sub-task > Reporter: Julien Viet > Assignee: Julien Viet > Fix For: 2.0 Beta 1, 2.0 Beta 2, 2.0 Final > > Original Estimate: 3 hours > Remaining: 3 hours > > Slide caches must be consistent accross nodes. -- 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: Maximize behavior: Nukes vs Rest of the World
Caching is still redundant work in this scenario... This does not seem to work well at the theme level. I have to create a fake portlet with a special name, make it the default, and have special handling in the index.jsp to hide the fake portlet and render the page different ways based on the state of the fake portlet. JBoss Portal's handling of the main fragment fundamentally affects the behavior and appearance of the page, such that this behavior cannot effectively be handled by a theme alone. If you want to keep the old Nuke's behavior I think you need to at least support a full maximize without requiring a hack. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866917#3866917 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866917 --- 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: (JBIDE-116) Conflict between JBoss-IDE plugin and Rational ClearCase SCM
[ http://jira.jboss.com/jira/browse/JBIDE-116?page=comments#action_12315481 ] Marshall Culpepper commented on JBIDE-116: -- I've tried playing with a clean install of Eclipse 3.0.1 + JBossIDE 1.4.1 + The clearcase adapter for 3.0 from this URL: http://www-128.ibm.com/developerworks/rational/library/content/03July/2500/2834/ClearCase/clearcase_plugins.html I'm getting this process error after packaging is executed (I'm guessing it's trying to run a clearcase executable.. but it's using unix shell to do it.. is this unix/linux only?): java.io.IOException: CreateProcess: /bin/sh -c "echo $CLEARCASE_ROOT" error=3 ... Is there a way I can get ClearCase for free on my machine? Or is it necessary to pay a license fee? > Conflict between JBoss-IDE plugin and Rational ClearCase SCM > > > Key: JBIDE-116 > URL: http://jira.jboss.com/jira/browse/JBIDE-116 > Project: JBoss IDE > Type: Bug > Reporter: SourceForge User > Assignee: Marshall Culpepper > > > SourceForge Submitter: ericeberry . > I have been getting this exception when trying to Run > XDoclet with JBoss-IDE 1.4.0 and Eclipse 3.0.1. > !ENTRY org.eclipse.core.runtime 4 2 Nov 08, 2004 > 09:07:29.742 > !MESSAGE An internal error occurred during: "XDoclet > Generation". > !STACK 0 > java.lang.IllegalArgumentException: Attempted to > beginRule: R/, does not match outer scope rule: > P/bnc1.5 > at org.eclipse.core.internal.runtime.Assert.isLegal > (Assert.java:58) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush > (ThreadJob.java:106) > at org.eclipse.core.internal.jobs.ThreadJob.push > (ThreadJob.java:200) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin > (ImplicitJobs.java:80) > at org.eclipse.core.internal.jobs.JobManager.beginRule > (JobManager.java:170) > at > org.eclipse.core.internal.resources.WorkManager.checkIn > (WorkManager.java:95) > at > org.eclipse.core.internal.resources.Workspace.prepareOp > eration(Workspace.java:1628) > at > org.eclipse.core.internal.resources.Resource.refreshLocal > (Resource.java:1224) > at > org.jboss.ide.eclipse.xdoclet.run.ui.actions.XDocletRunAct > ion$1.run(XDocletRunAction.java:191) > at org.eclipse.core.internal.jobs.Worker.run > (Worker.java:66) > It turns out there is a conflict between the JBoss-IDE > plugin and the Rational ClearCase SCM Adapter 6.0.24 > plugin. Becuase this plugin is "always on", we can't turn > the plugin off. We have to disable the plugin to turn it > off. I disabled the plugin and I was able to run xdoclet > every time. As soon as I re-enabled the plugin. Run > XDoclet stopped working. -- 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: (JBAS-1476) Need to include a notion of cluster instance in the cluster view
[ http://jira.jboss.com/jira/browse/JBAS-1476?page=comments#action_12315480 ] Ole Husgaard commented on JBAS-1476: Bela Ban commented: // Since the timestamp uses wall clock time, a client might get a superfluous topology change on a response, but this would only happen when failing over to a different server, and the servers times are not sync'ed Please note that with a round robin loadsharing policy the node accessed changes constantly. Please also note the even though server times are in sync, the tick to the next millisecond can happen a few microseconds before on one of the servers. I think that Adrians notion of a cluster GUID is better. This could be a combination of a server IP address and a timestamp. The only potential problem I see with Adrians suggestion is when two clusters that started out as seperate clusters with different cluster GUIDs because they could not communicate end up merging. But that is really a border case, worse than a cluster split. > Need to include a notion of cluster instance in the cluster view > > > Key: JBAS-1476 > URL: http://jira.jboss.com/jira/browse/JBAS-1476 > Project: JBoss Application Server > Type: Bug > Components: Clustering > Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1 > Reporter: Adrian Brock > Priority: Critical > > > We need to include a notion of cluster instance in the cluster view id > to avoid at least the following scenario: > Client serializes a handle to a cluster which is at cluster view 22 > Handle contains key DefaultPartition/HAJNDI/22 > The cluster is totally restarted meaning the view reverts back to one. > The client now has a view id > DefaultPartition/HAJNDI/1 > The client deserializes the handle, which will overwrite the correct cluster > view with the old invalid view. > > This will also avoid the problem where a client talks to different clusters > with the same partition name. > > Proposed solution: > 1) At cluster formation (first node in cluster), create a cluster instance > GUID > 2) At cluster join (second+ node in cluster) get the GUID from the coordinator > 3) Include this GUID in cluster view keys, i.e. > GUID/DefaultPartition/HAJNDI/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 Portal] - Re: Portlet Size
It is dictated by the theme, and the current theme dictates the size by the portlet content. You could make a theme that would check for some portlet parameters to adapt itself. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866908#3866908 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866908 --- 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] - Portlet Size
Is it possible to set an absolute size for a portlet (preferably for each state and mode) at the portlet level or is the size totally dictated by the portlet content? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866907#3866907 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866907 --- 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: Trouble - hadcoded MIME type and restrictions
anonymous wrote : keep your old version and just add the get/set content type so that will work. OK, thanks. anonymous wrote : no nightly builds are not available yet. could you add a JIRA task for it ? Could you provide me with a brief instruction on how to do that ;) ? I have never done this before. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866906#3866906 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866906 --- 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: Trouble - hadcoded MIME type and restrictions
keep your old version and just add the get/set content type so that will work. no nightly builds are not available yet. could you add a JIRA task for it ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866903#3866903 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866903 --- 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: (JBPORTAL-208) Automated test suite
Automated test suite Key: JBPORTAL-208 URL: http://jira.jboss.com/jira/browse/JBPORTAL-208 Project: JBoss Portal Type: Feature Request Components: Portal Core Versions: 2.0 Final Reporter: Julien Viet Assigned to: Julien Viet Fix For: 2.0 Final -- 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
