[JBoss-dev] [JBoss JIRA] Created: (JBAS-1573) NPE in SQLUtil.appendColumnNamesClause
NPE in SQLUtil.appendColumnNamesClause -- Key: JBAS-1573 URL: http://jira.jboss.com/jira/browse/JBAS-1573 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.1 Final Environment: Windows XP Pro SP2, JBoss 4.0.1, Sun JDK 1.5.0_01 Reporter: cgs ejbSelect JBoss-QL query does not build successfully and throws NPE in SQLUtil.appendColumnNamesClause. This query works for bean X relating to the same related bean Y, but not for bean Z. They are both M:N relations. * @jboss.query * signature="java.util.Collection ejbSelectContactList(com.xxx.emm.interfaces.CampaignLocal campaignLocal, int offset, int limit)" * query="SELECT DISTINCT OBJECT(co) * FROM campaign c, * IN (c.contactList) AS co * WHERE c = ?1 * ORDER BY co.id ASC * OFFSET ?2 * LIMIT ?3" * Here's the stack trace: 2005-03-12 00:30:05,607 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.Campaign#ejbSelectContactList] JBossQL: SELECT DISTINCT OBJECT(co) FROM campaign c, IN (c.contactList) AS co WHERE c = ?1 ORDER BY co.id ASC OFFSET ?2 LIMIT ?3 2005-03-12 00:30:05,607 INFO [STDOUT] java.lang.NullPointerException 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.appendColumnNamesClause(SQLUtil.java:386) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.selectEntity(JDBCEJBQLCompiler.java:1849) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit(JDBCEJBQLCompiler.java:1012) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.ASTSelect.jjtAccept(ASTSelect.java:25) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit(JDBCEJBQLCompiler.java:510) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.ejbql.ASTEJBQL.jjtAccept(ASTEJBQL.java:23) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.compileJBossQL(JDBCEJBQLCompiler.java:197) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.(JDBCJBossQLQuery.java:43) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createJBossQLQuery(JDBCCommandFactory.java:72) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:260) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:490) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:381) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) 2005-03-12 00:30:05,607 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) 2005-03-12 00:30:05,607 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2005-03-12 00:30:05,607 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) 2005-03-12 00:30:05,607 INFO [STDOUT] at $Proxy0.start(Unknown Source) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.system.ServiceController.start(ServiceController.java:416) 2005-03-12 00:30:05,607 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) 2005-03-12 00:30:05,607 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2005-03-12 00:30:05,607 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585) 2005-03-12 00:30:05,607 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) 2005-03-12 00:30:
[JBoss-dev] jboss-head build.873 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050312005304Lbuild.873 BUILD COMPLETE - build.873Date of build: 03/12/2005 00:53:04Time to build: 17 minutes 14 secondsLast changed: 03/12/2005 00:40:44Last log entry: Generate default constructor + ctr with types + variables at the beginning.This is in line with wscompile. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.4modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/WSDLToJava.javaGenerate default constructor + ctr with types + variables at the beginning.This is in line with wscompile.
[JBoss-dev] jboss-4.0 build.428 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050312002303Lbuild.428 BUILD COMPLETE - build.428Date of build: 03/12/2005 00:23:03Time to build: 19 minutes 29 secondsLast changed: 03/11/2005 23:27:12Last log entry: Added Scout related library entry. [JAXR Integration] Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (5)1.41.2.4modifiedosdchicagotools/etc/buildmagic/libraries.entAdded Scout related library entry. [JAXR Integration]1.4.2.4modifiedosdchicagotools/etc/buildmagic/libraries.xmlAdded Scout related library entry. [JAXR Integration]1.2.4.1modifiedosdchicagothirdparty/juddi-juddi/lib/juddi.warApache JUDDI1.3.2.1modifiedosdchicagothirdparty/apache-scout/lib/scout.jarApache Scout [JAXR Integration]1.6.4.1modifiedosdchicagothirdparty/juddi-juddi/lib/juddi.jarApache JUDDI
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1572) stop unzipping everything in the deploy on every startup
stop unzipping everything in the deploy on every startup Key: JBAS-1572 URL: http://jira.jboss.com/jira/browse/JBAS-1572 Project: JBoss Application Server Type: Feature Request Components: Deployment Service Versions: JBossAS-4.0.1 SP1 Reporter: Andrew Oliver Presently JBossAS unzips everything in the deploy directory into the tmp directory on every startup. The desired behavior is to preserve the files in the tmp directory and only unzip if there is a newer associated file in the deploy directory. -- 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] - Default Login
Dumb question, but I couldn't find it in the doc. After I install the beta, what is the default login? Todd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869866#3869866 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869866 --- 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.427 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050311230229Lbuild.427 BUILD COMPLETE - build.427Date of build: 03/11/2005 23:02:29Time to build: 26 minutes 27 secondsLast changed: 03/11/2005 22:55:52Last log entry: Added a new target "tests-scout-jaxr" that tests the new JAXR stack!!! Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.406.2.43modifiedosdchicagotestsuite/build.xmlAdded a new target "tests-scout-jaxr" that tests the new JAXR stack!!!1.355.2.24modifiedosdchicagobuild/build.xmlAdded JAXR Integration based on Apache Scout/Apache jUDDI. Turned off ebxmlrr.1.90.2.9modifiedosdchicagovaria/build.xmlAdded JAXR Integration based on Apache Scout/Apache jUDDI.
[JBoss-dev] jboss-head build.872 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311213957Lbuild.872 BUILD COMPLETE - build.872Date of build: 03/11/2005 21:39:57Time to build: 27 minutes 11 secondsLast changed: 03/11/2005 21:26:39Last log entry: Refactored transaction context Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.48modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaRefactored transaction context
[JBoss-dev] [Design of JBoss Portal] - Re: portal 2 beta1 startup error
I agree, the documentation needs to be updated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869865#3869865 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869865 --- 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 Clustering on JBoss (Clusters/JBoss)] - Re: Inconsistent handling of group rpc call exceptions
Transactional jndi state replication can be achieved with JBossCache now. Transactional rpc will need work though. But I like the idea. I can put this in the roadmap. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869863#3869863 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869863 --- 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-1161789 ] SerializableResultSetMetaData.getColumnCount
Bugs item #1161789, was opened at 2005-03-12 02:26
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=1161789&group_id=22866
Category: JBossServer
Group: v4.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Evgeniy (evgen_ii)
Assigned to: Nobody/Anonymous (nobody)
Summary: SerializableResultSetMetaData.getColumnCount
Initial Comment:
Method getColumnCount of
SerializableResultSetMetaData class returns wrong
number of columns in resultset. It is as great as actual
count + 1 constantly. The problem is obvious - in
constructor internal array is created with the actual size
+ 1
int count = metaData.getColumnCount();
columnData = new ColumnData[count+1];
and than the lenght of this array is returned as column
count:
public int getColumnCount() throws SQLException
{
return columnData.length;
}
And we get wrong count of columns in resulset.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1161789&group_id=22866
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.871 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311190248Lbuild.871 BUILD COMPLETE - build.871Date of build: 03/11/2005 19:02:48Time to build: 24 minutes 46 secondsLast changed: 03/11/2005 18:51:12Last log entry: Run under tx context. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.4modifiedbwang00testsuite/src/main/org/jboss/test/cache/test/standAloneAop/LocalConcurrentTestCase.javaRun under tx context.
[JBoss-dev] jboss-head build.870 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311172548Lbuild.870 BUILD COMPLETE - build.870Date of build: 03/11/2005 17:25:48Time to build: 21 minutes 38 secondsLast changed: 03/11/2005 17:16:48Last log entry: Fix test broken by the recent invoker config change(stateless-rmi-invoker -> stateless-unified-invoker). Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.2modifiedreverbeltestsuite/src/resources/hellojrmpiiop/META-INF/jboss.xmlFix test broken by the recent invoker config change(stateless-rmi-invoker -> stateless-unified-invoker).1.43modifiedreverbeltestsuite/imports/test-jars.xmlAdded IIOP performance tests.
[JBoss-dev] [JBossCache] - Re: Can't lookup cache service through JNDI
We no longer regsiter cache with JNDI in the latest pre-1.2.1 release becuase it introduces lots of extra dependency. You will either need to bind it yourself or use MBean lookup instead. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869846#3869846 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869846 --- 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: Is there to make a particular request
Currently, isolation level is per cache instance. So you will need to have two separate cache instance to what you want. Region based is in the roadmap though. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869845#3869845 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869845 --- 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] - Is there to make a particular request "Read_Uncommited" ?
I have a normal (non AOP) REPL_SYNC cache... and I want in just one section of code to do a cache read regardless of any locks. For this one particular section of code I don't really care if the cache state is inconsistent or a write is in progress... I just want a print out of the entire cache... (Actually I am doing more than that, but the idea here is I am accessing the cache exclusively for a read where I don't care if state changes while I am reading.) I don't want to change the isolation level to READ_UNCOMMITED for the whole cache... because everything else still needs the repeatable read semantics... Is there a publicly accessible read for TreeCache that ignores write locks? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869843#3869843 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869843 --- 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.869 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311152258Lbuild.869 BUILD COMPLETE - build.869Date of build: 03/11/2005 15:22:58Time to build: 34 minutes 56 secondsLast changed: 03/11/2005 14:30:17Last log entry: JBREM-69 - changed misspelling of ULR to URL. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (5)1.3deletedtelrodjmx-remoting/src/main/test/compliance/core/serviceurl/JMXServiceULRTest.javaJBREM-69 - changed misspelling of ULR to URL.1.1addedtelrodjmx-remoting/src/main/test/compliance/core/serviceurl/JMXServiceURLTest.javaJBREM-69 - changed misspelling of ULR to URL.1.2modifiedtelrodjmx-remoting/src/main/test/compliance/core/serviceurl/JMXServiceULRTest.javaJBREM-69 - finished implementation for JMXServiceURL and tests. Should be fully compliant at this point.1.2modifiedtelrodjmx-remoting/src/main/javax/management/remote/JMXServiceURL.javaJBREM-69 - finished implementation for JMXServiceURL and tests. Should be fully compliant at this point.1.27modifiedbwang00cache/src/etc/standalone/build.xmlWith commented out bind.address property for specific ip
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: how best to distribute and workaround jboss-common issue
Hey John. Don't think there is an easy solution here. I only see two viable options at this point, update the PropertyEditors in the 4.0.1SP1 commons jar or wait for 4.0.2 release (which should be this month I think) that actually includes JBoss Remoting 1.0.1 final and the compliant PropertyEditors class. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869824#3869824 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869824 --- 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] - how best to distribute and workaround jboss-common issue?
I'm currently putting together a distribution package for something that uses JBoss/Remoting. I have it *almost* to the point where I can ship a .sar for "default" configuration and another .sar for "minimal" configuration (in case you want to deploy in either/or). The problem I have is this backward-incompatibility with jboss-common.jar. There is one class (actually, just a method) that JBoss/Remoting needs that is not in any currently released JBossAS (method in PropertyEditors). What I currently have now is an ant script that deploys the .sar in the appropriate /deploy directory but it also replaces that class in the JBossAS /lib directory's jboss-common.jar. Obviously, this makes distribution slightly more complicated than just shipping a sar and saying "put this in your /deploy directory". Due to this, I wanted to be able to ship a .zip file that I can say, "unzip this in your JBossAS home directory and jboss-common.jar will be overlayed in the proper /lib directory and the .sar will be placed in the proper server/default/deploy directory. However, it turns out that the jboss-common.jar that ships with JBoss/Remoting is not compatible with currently shipping JBossAS distros (I have 4.0.1.SP1 that I'm trying this on). So, I really do have to just upgrade this one class in jboss-common.jar and leave everything else that comes with SP1's jboss-common.jar alone. Any other ideas to make a distribution easy and work around this problem? As a more generic point here - this "patch a class" feature is clearly something we need to consider when we build out JBoss Network - which falls on me and my group :-) Of course, I'm hoping JBoss 5 will help by providing nice patching capabilities down to the class level. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869819#3869819 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869819 --- 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: Multiple portlets, 1 war
jz. I can't beleive that's what I was doing wrong. Blame it on Fridays. Thank Thomas. It works fine now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869795#3869795 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869795 --- 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-1515) Update the AOP binaries and remove the aop modules
[ http://jira.jboss.com/jira/browse/JBAS-1515?page=history ] Scott M Stark closed JBAS-1515: --- Assign To: Scott M Stark Resolution: Done The MailServiceMBean is generated from the MailService.java class so you need to do a clean build to synch the interface. > Update the AOP binaries and remove the aop modules > -- > > Key: JBAS-1515 > URL: http://jira.jboss.com/jira/browse/JBAS-1515 > Project: JBoss Application Server > Type: Task > Components: Build System > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final > Reporter: Scott M Stark > Assignee: Scott M Stark > Fix For: JBossAS-4.0.2RC1 > > > The aop deployer seems to no longer be built from the aspects module source. > The current 4.0 branch binaries do not include the recent security changes > and needs to be updated. If binaries are being used as the integration > mechanism, there is no reason to be including obsolete source modules. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1515) Update the AOP binaries and remove the aop modules
[ http://jira.jboss.com/jira/browse/JBAS-1515?page=history ] Scott M Stark updated JBAS-1515: Version: JBossAS-4.0.1 SP1 JBossAS-4.0.1 Final (was: JBossAS-4.0.2RC1) Fix Version: JBossAS-4.0.2RC1 (was: JBossAS-4.0.2 Final) > Update the AOP binaries and remove the aop modules > -- > > Key: JBAS-1515 > URL: http://jira.jboss.com/jira/browse/JBAS-1515 > Project: JBoss Application Server > Type: Task > Components: Build System > Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final > Reporter: Scott M Stark > Fix For: JBossAS-4.0.2RC1 > > > The aop deployer seems to no longer be built from the aspects module source. > The current 4.0 branch binaries do not include the recent security changes > and needs to be updated. If binaries are being used as the integration > mechanism, there is no reason to be including obsolete source modules. -- 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: (JBAOP-93) JBoss AOP jars in 4.0
[ http://jira.jboss.com/jira/browse/JBAOP-93?page=comments#action_12316082 ] Scott M Stark commented on JBAOP-93: I'm creating thirdparty/jboss-xxx entries to remove the obsolete source modules and move to the binaries for the 4.0 branch. > JBoss AOP jars in 4.0 > - > > Key: JBAOP-93 > URL: http://jira.jboss.com/jira/browse/JBAOP-93 > Project: JBoss AOP > Type: Task > Reporter: Adrian Brock > Assignee: Scott M Stark > Priority: Minor > > > The jboss-aop and aspect library jars in Branch_4_0 should be in thirdparty > and the source projects removed altogether from the JBossAS build. > Although, we do want to use this approach in future, we don't have the > infrastructure > in place for this change yet... > e.g. How to control versions of dependent projects and thirdparty jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAOP-93) JBoss AOP jars in 4.0
[ http://jira.jboss.com/jira/browse/JBAOP-93?page=history ] Scott M Stark reassigned JBAOP-93: -- Assign To: Scott M Stark (was: Bill Burke) > JBoss AOP jars in 4.0 > - > > Key: JBAOP-93 > URL: http://jira.jboss.com/jira/browse/JBAOP-93 > Project: JBoss AOP > Type: Task > Reporter: Adrian Brock > Assignee: Scott M Stark > Priority: Minor > > > The jboss-aop and aspect library jars in Branch_4_0 should be in thirdparty > and the source projects removed altogether from the JBossAS build. > Although, we do want to use this approach in future, we don't have the > infrastructure > in place for this change yet... > e.g. How to control versions of dependent projects and thirdparty jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBREM-69) Implement JMXServiceURl
[ http://jira.jboss.com/jira/browse/JBREM-69?page=history ] Tom Elrod closed JBREM-69: --- Resolution: Done Implementation finished and should be compliant. As for default protocol, am asking jsr 255 group to clarify (but think indirectly means have to have jmxmp implementation). As for default port, means default for protocol being used. > Implement JMXServiceURl > --- > > Key: JBREM-69 > URL: http://jira.jboss.com/jira/browse/JBREM-69 > Project: JBoss Remoting > Type: Task > Components: jmx remoting > Reporter: Tom Elrod > Assignee: Tom Elrod > Priority: Critical > Fix For: JMX Remoting 1.0.1 > > Original Estimate: 6 hours > Remaining: 6 hours > > Per spec, need following requirements met: > - prefix of "service:jmx:"; > - string of one or more ASCII characters, each of which is a letter, a digit, > or one of the characters + or - (for protocol) > - Uppercase letters are converted into lowercase ones (for protocol) > - host is a host name, an IPv4 numeric host address, or an IPv6 numeric > address enclosed in square brackets > - port is a decimal port number. 0 means a default or anonymous port, > depending on the protocol > - port cannot be supplied without a host > - url-path, if any, begins with a slash (/) or a semicolon (;) and continues > to the end of the address. It can contain attributes using the semicolon > syntax specified in RFC 2609. Those attributes are not parsed by this class > and incorrect attribute syntax is not detected -- 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.868 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311134114Lbuild.868 BUILD COMPLETE - build.868Date of build: 03/11/2005 13:41:14Time to build: 26 minutes 55 secondsLast changed: 03/11/2005 13:03:50Last log entry: Cache interceptor lookup should not need fqn. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (4)1.47modifiedbwang00cache/src/main/org/jboss/cache/aop/TreeCacheAop.javaCache interceptor lookup should not need fqn.1.1addedkaran_malhiremoting/docs/Eclipse-HowTo.txtJBREM-70 - added HowTo document for eclipse users1.4modifiedkaran_malhiremoting/.projectJBREM-70 - removed project references.1.19modifiedkaran_malhiremoting/.classpathJBREM-70 - removed unused library paths from classpath. See /docs/Eclipse-HowTo.txt
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1568) Problem with JMSContainerInvoker objectname in Jboss 3.2.7
[ http://jira.jboss.com/jira/browse/JBAS-1568?page=history ]
Adrian Brock closed JBAS-1568:
--
Resolution: Won't Fix
I don't see how we can satisfy both requirements that
two MDBs can be deployed with the same EJB name
and yet have unique ObjectNames.
Since you can effectively override the ObjectName
with the config of the MDB
the problem is always resolveable one way or the other.
I did see a suggestion to make the hashcode a separate part of the
ObjectName, but this won't solve this problem, i.e.
jboss.j2ee:service=EJB,jndiName=,hashCode=xxx
Another potential solution is to have
jboss.j2ee:service=EJB,jndiName=,ejbDeployment=/opt/jboss-3.2.8/server/default/deploy/some.ear/whatever.jar
but that is pretty ugly.
I am prepared to reopen this bug report if a better solution comes along.
> Problem with JMSContainerInvoker objectname in Jboss 3.2.7
> --
>
> Key: JBAS-1568
> URL: http://jira.jboss.com/jira/browse/JBAS-1568
> Project: JBoss Application Server
> Type: Feature Request
> Components: EJBs
> Versions: JBossAS-3.2.7 Final
> Environment: Fedora core 2
> j2sdk1.4.2_05
> JBoss 3.2.7
> Reporter: chris_pollentier
>
>
> In JBoss release 3.2.7, the ObjectName of the JMSContainerInvokers contains a
> hashcode. This hashcode was added to resolve bug JBAS-275.
> This makes it difficult to have other services depend on the
> JMSContainerInvoker, since the exact ObjectName is unknown.
> The jmx ObjectName of the JMSContainerInvoker is created by taking the
> ObjectName of the MDB container and adding
> 'plugin=invoker,binding='
> Extract from the method 'createService' of MessageDrivenContainer:
>ObjectName containerName = super.getJmxName();
>Hashtable props = containerName.getKeyPropertyList();
>props.put("plugin", "invoker");
>props.put("binding", invokerBinding);
>ObjectName invokerName = new
> ObjectName(containerName.getDomain(), props);
>server.registerMBean(ci, invokerName);
> No problem here, but in case of an MDB the containerName is:
> jboss.j2ee:service=EJB,jndiName=
> Since there are no interfaces to be defined for an MDB, the jndi name itself
> is a dummy jndi name generated based on the MDB name and (since JBoss3.2.7) a
> hashcode:
> Extract from class BeanMetaData:
>public String getLocalJndiName()
>{
> if (localJndiName == null)
> {
> // Generate a unique name based on ejbName + identityHashCode
> localJndiName = "local/" + ejbName + '@' +
> System.identityHashCode(ejbName);
>// the '@' + System.identityHashCode(ejbName); was added in JBoss
> 3.2.7
> }
> return localJndiName;
>}
> Now let me explain my problem:
> Before JBoss-3.2.7, the localJndiName that was generated did not contain the:
> '@' + System.identityHashCode(ejbName);
> The ObjectName of the JMSContainerInvoker was e.g.:
> 'jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB, plugin=invoker,
> binding=inactive-message-driven-bean'
> I now have a problem related to clustering:
> A MDB that connects to a topic (with durable subscription) is running on each
> node of my cluster.
> Because they have the same durable subscription Id, only one
> JMSContainerInvoker has deliveryActive set to true.
> I had a SingetonController service calls the 'startDelivery' and
> 'stopDelivery' methods on the JMSContainerInvokers to make sure that only the
> MDB on the master node of the cluster processes the messages. This config was
> chosen to have fail-over when the master node goes down.
> Under JBoss 3.2.4 this was working fine (apart from a delay in the failover
> which was fixed in JBoss3.2.7), but with JBoss3.2.7 I can no longer do this
> because I cannot configure this SingletonController to be depending on the
> JMSContainerInvoker:
> On JBoss 3.2.4:
> name="mdb.singleton:service=SingletonAController">
>
> jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB,
> plugin=invoker, binding=inactive-message-driven-bean
> jboss:service=DefaultPartition
>
> name="TargetName">jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB,
> plugin=invoker, binding=inactive-message-driven-bean
> startDelivery
> stopDelivery
>
> On JBoss 3.2.7, the name of the invoker becomes something like:
> 'jboss.j2ee:service=EJB,[EMAIL PROTECTED], plugin=invoker,
> binding=inactive-message-driven-bean'
> I can only know the exact ObjectName of the invoker after delploying it
> To solve this, it would be nice if there were a possibility to specify the
> ObjectName to be used for a JMSContainerInvoker for some MDB, or to configure
> the jndi-name of the MDB container.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one o
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-133) Create a Wishlist / Roadmap
Create a Wishlist / Roadmap --- Key: JBIDE-133 URL: http://jira.jboss.com/jira/browse/JBIDE-133 Project: JBoss IDE Type: Task Components: Webservices Plugin Reporter: Marshall Culpepper Assigned to: Marshall Culpepper -- 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-1568) Problem with JMSContainerInvoker objectname in Jboss 3.2.7
[
http://jira.jboss.com/jira/browse/JBAS-1568?page=comments#action_12316079 ]
Adrian Brock commented on JBAS-1568:
I believe this is a duplicate post, but I can't find where Scott already
answered this.
The workaround is:
FIXED-NAME
etc.
> Problem with JMSContainerInvoker objectname in Jboss 3.2.7
> --
>
> Key: JBAS-1568
> URL: http://jira.jboss.com/jira/browse/JBAS-1568
> Project: JBoss Application Server
> Type: Feature Request
> Components: EJBs
> Versions: JBossAS-3.2.7 Final
> Environment: Fedora core 2
> j2sdk1.4.2_05
> JBoss 3.2.7
> Reporter: chris_pollentier
>
>
> In JBoss release 3.2.7, the ObjectName of the JMSContainerInvokers contains a
> hashcode. This hashcode was added to resolve bug JBAS-275.
> This makes it difficult to have other services depend on the
> JMSContainerInvoker, since the exact ObjectName is unknown.
> The jmx ObjectName of the JMSContainerInvoker is created by taking the
> ObjectName of the MDB container and adding
> 'plugin=invoker,binding='
> Extract from the method 'createService' of MessageDrivenContainer:
>ObjectName containerName = super.getJmxName();
>Hashtable props = containerName.getKeyPropertyList();
>props.put("plugin", "invoker");
>props.put("binding", invokerBinding);
>ObjectName invokerName = new
> ObjectName(containerName.getDomain(), props);
>server.registerMBean(ci, invokerName);
> No problem here, but in case of an MDB the containerName is:
> jboss.j2ee:service=EJB,jndiName=
> Since there are no interfaces to be defined for an MDB, the jndi name itself
> is a dummy jndi name generated based on the MDB name and (since JBoss3.2.7) a
> hashcode:
> Extract from class BeanMetaData:
>public String getLocalJndiName()
>{
> if (localJndiName == null)
> {
> // Generate a unique name based on ejbName + identityHashCode
> localJndiName = "local/" + ejbName + '@' +
> System.identityHashCode(ejbName);
>// the '@' + System.identityHashCode(ejbName); was added in JBoss
> 3.2.7
> }
> return localJndiName;
>}
> Now let me explain my problem:
> Before JBoss-3.2.7, the localJndiName that was generated did not contain the:
> '@' + System.identityHashCode(ejbName);
> The ObjectName of the JMSContainerInvoker was e.g.:
> 'jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB, plugin=invoker,
> binding=inactive-message-driven-bean'
> I now have a problem related to clustering:
> A MDB that connects to a topic (with durable subscription) is running on each
> node of my cluster.
> Because they have the same durable subscription Id, only one
> JMSContainerInvoker has deliveryActive set to true.
> I had a SingetonController service calls the 'startDelivery' and
> 'stopDelivery' methods on the JMSContainerInvokers to make sure that only the
> MDB on the master node of the cluster processes the messages. This config was
> chosen to have fail-over when the master node goes down.
> Under JBoss 3.2.4 this was working fine (apart from a delay in the failover
> which was fixed in JBoss3.2.7), but with JBoss3.2.7 I can no longer do this
> because I cannot configure this SingletonController to be depending on the
> JMSContainerInvoker:
> On JBoss 3.2.4:
> name="mdb.singleton:service=SingletonAController">
>
> jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB,
> plugin=invoker, binding=inactive-message-driven-bean
> jboss:service=DefaultPartition
>
> name="TargetName">jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB,
> plugin=invoker, binding=inactive-message-driven-bean
> startDelivery
> stopDelivery
>
> On JBoss 3.2.7, the name of the invoker becomes something like:
> 'jboss.j2ee:service=EJB,[EMAIL PROTECTED], plugin=invoker,
> binding=inactive-message-driven-bean'
> I can only know the exact ObjectName of the invoker after delploying it
> To solve this, it would be nice if there were a possibility to specify the
> ObjectName to be used for a JMSContainerInvoker for some MDB, or to configure
> the jndi-name of the MDB container.
--
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
___
JBos
[JBoss-dev] [Design of JBoss Portal] - Re: portal 2 beta1 startup error
Did I realy not read the installation notes carefully enough? Shame on me. I apologize deeply since I thought it would be something like this but still overlooked it in the notes. [5 minute delay] Well... I just reread the notes and have to revoke my previous remark. I did read the notes ok. The remark about copying these three libs is *only* in the installation part when you install from source (2.3.2), but in the install from binaries (2.3.1) there is no item which tells you to copy these libs. I think the installation notes have to be updated on that part. Ronald[/img] View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869785#3869785 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869785 --- 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.867 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log2005035227Lbuild.867 BUILD COMPLETE - build.867Date of build: 03/11/2005 11:52:27Time to build: 27 minutes 45 secondsLast changed: 03/11/2005 09:26:21Last log entry: fixed JBAS-1386 commit option B does not work with CMP 1.x Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.21modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/bridge/JDBCCMP1xFieldBridge.javafixed JBAS-1386 commit option B does not work with CMP 1.x
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: Inconsistent handling of group rpc call exceptions
I think this suggested behavior is an improvement. ha-jndi should be using jbosscache to guarantee transactional state replication, so that either all or no objects are bound. A future task that would be useful is to offer higher level transactional rpc calls. So that 1) the code throwing the exceptions can participate in the decision whether or not it affects the overall call; 2) the originating caller can roll back the effect of the call based on the outcome. Ivelin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869779#3869779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869779 --- 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: Multiple portlets, 1 war
You must define only 1 default window, you have all your windows as default. Make sure you have existing areas in your theme like top, bottom, right, left or put them all in left if you are using the default theme. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869777#3869777 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869777 --- 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: Multiple portlets, 1 war
Ok, here's what im trying to do: I have made 4 helloworld portlets (basically copies of the basic helloworld with different names for each class). I want all these 4 portlets to display on the same html page. Each portlet prints out a line on stdout whenever its accessed. My WEB-INF contains jboss-portlet.xml: | |manyhellos | | portlet.xml | | http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd"; | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; | xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd /opt/SUNWps/dtd/portlet.xsd" version="1.0"> | | | HelloAPortlet | org.jboss.portlet.helloworld.HelloA | en | Resource | | text/html | VIEW | | | My HelloA Portlet | | | | | HelloBPortlet | org.jboss.portlet.helloworld.HelloB | en | Resource | | text/html | VIEW | | | My HelloB Portlet | | | | | HelloCPortlet | org.jboss.portlet.helloworld.HelloC | en | Resource | | text/html | VIEW | | | My HelloC Portlet | | | | | HelloDPortlet | org.jboss.portlet.helloworld.HelloD | en | Resource | | text/html | VIEW | | | My HelloD Portlet | | | | | portlet-instances.xml: | | | | HelloAPortletInstance | HelloAPortlet | | | HelloBPortletInstance | HelloBPortlet | | | HelloCPortletInstance | HelloCPortlet | | | HelloDPortletInstance | HelloDPortlet | | | There;s only 1 pages.xml file,even though there are 4 portlets. This is manyhellos-pages.xml in which I'm placing the many portlet windows: | |default | | | manyhellos | | | HelloAPortletWindow | manyhellos.HelloAPortlet.HelloAPortletInstance | true | left | 0 | | | HelloBPortletWindow | manyhellos.HelloBPortlet.HelloBPortletInstance | true | right | 0 | | | HelloCPortletWindow | manyhellos.HelloCPortlet.HelloCPortletInstance | true | bottom | 0 | | | HelloDPortletWindow | manyhellos.HelloDPortlet.HelloDPortletInstance | true | top | 0 | | | | | | Now when I run the portal, it shows me the portlet "manyhellos" in the Page Menu. When I click on it, it only runs portlet HelloD. The output I get in stdout is only from HelloD, and it displays only the HelloD portlet on the page. What am I doing wrong? TIA, Karan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869775#3869775 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869775 --- 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 Clustering on JBoss (Clusters/JBoss)] - Re: Inconsistent handling of group rpc call exceptions
I'm pretty sure I implemented this stuff long ago, but I can't remember why I was eating exceptions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869771#3869771 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869771 --- 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.426 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050311104709Lbuild.426 BUILD COMPLETE - build.426Date of build: 03/11/2005 10:47:09Time to build: 26 minutes 41 secondsLast changed: 03/11/2005 09:32:11Last log entry: fixed JBAS-1386 commit option B does not work with CMP 1.x Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.20.4.1modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/bridge/JDBCCMP1xFieldBridge.javafixed JBAS-1386 commit option B does not work with CMP 1.x1.6.2.1modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/Schema.javafixed JBAS-1570 NPE in jdbc2.Schema when no tx
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-132) add forms support
add forms support - Key: JBIDE-132 URL: http://jira.jboss.com/jira/browse/JBIDE-132 Project: JBoss IDE Type: Task Components: jBPM Designer plugin Reporter: Tom Baeyens Assigned to: Marshall Culpepper add support for adding forms to a process archive. the forms should be used in the new webapplication that will be created by thomas. -- 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] - Support for SSO
Hi again, Our portal application have to support SSO, with userinformation stored in an LDAP server. As of today JBoss Portal stores userinformation in a database. So I have som question about this issue. 1) Is it possible to configure JBoss Portal to use LDAP. If no, is there any plans of implement SSO? 2) If we have to develop this ourself, could you give me some tips of how this could be implemented? Eg, wich classes to replace? Regards Jan Ole View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869763#3869763 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869763 --- 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 Clustering on JBoss (Clusters/JBoss)] - Inconsistent handling of group rpc call exceptions
I'm looking into some inconsistent behavior regarding group rpc calls and exceptions related to this bug report: http://jira.jboss.com/jira/browse/JBAS-1571 Logging of cluster rpc method exceptions at warn level is incorrect One issue is that the jgroups rpc semantics with regard to exception is ambiguous in my view and I started a forum thread on that here: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869760 The next level of problem is that the HAPartitionImpl override of the RpcDispatcher.handle method changes the return value semantics to not include checked exceptions that may be thrown by the invocation. Only Error and RuntimeException are thrown, but these can be the normal result of the reflected method invocation, so effectively we are filtering the exceptions down to these types. Checked exceptions are simply logged as warnings and a Throwable is logged at info level. The cvs annotations only show that Sacha has touched this code so this is the state of this implementation from its beginning. I want to change this code to propagate all exceptions back as the return value as is done by the RpcDispatcher. Its then up to the caller of the group rpc method to figure out what to do with the heterogenous collection of normal return values and exceptions. The ha-jndi usecase which initiated this investigation simply ignores nulls and Exceptions currently. This would mean that Throwables and Errors can start showing up as the result of a lookup, so this could be a non-transparent change in behavior. The current behavior seems sufficiently broken to warrant this in my view. Short of actually changing the jgroups implementation, are there any other suggestions to clean this up? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869762#3869762 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869762 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBIDE-131) add a process unit test template
add a process unit test template Key: JBIDE-131 URL: http://jira.jboss.com/jira/browse/JBIDE-131 Project: JBoss IDE Type: Task Components: jBPM Designer plugin Reporter: Tom Baeyens Assigned to: Marshall Culpepper when working on a jbpm process archive, users should be able to create a new process unit test. this test generates the skeleton code for loading the process archive and start a process instance for it. -- 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: not able to get request.getPortletSession().invalidate()
this is configurable in web.xml of the portal, you can use whatever you want (basic,form,etc...) the reason we added the logout is to make smth portable. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869761#3869761 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869761 --- 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 Clustering on JBoss (Clusters/JBoss)] - Re: org.jgroups.blocks.RpcDispatcher and Exceptions
Looking more into the jgroups code it seems that a return value from an invocation to a node may be one of: - the actual method return value - null if the node does not respond - an exception thrown by the method The last two are ambiguous. There is a notion of whether or not a node replied such that the null can be filtered out, but an exception is still amibiguous. It looks like changes to the RspList, RequestCorrelator, and GroupRequest would be needed to make the notion of an exception explicit. The biggest problem is the lack of an exception in the org.jgroups.blocks.RequestHandler interface. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869760#3869760 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869760 --- 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: not able to get request.getPortletSession().invalidate()
Yeap, the portal handles http sessions different than I thougt. I was not aware of that there were different http sessions. Personally I prefer "form" based authentication (the way it is in beta 1). With "basic" authentication, as you say, you can't "log out" by invalidating the session. regards Jan Ole View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869759#3869759 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869759 --- 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: problem with REPL_SYNC and REPL_ASYNC
Hi, Exceptions are for -- Asynchronous Cache Mode 1. ?With default Java Heap Size (64 MB)?, It is throwing an exception on putting around 2500th element and program terminates. The exception is ??. Exception in thread "main" org.jboss.util.NestedRuntimeException: Java heap space; - nested throwable: (java.lang.OutOfMemoryError: Java heap space) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3248) at org.jboss.cache.TreeCache.put(TreeCache.java:1749) at org.jboss.cache.TreeCache.put(TreeCache.java:1732) at TestTreeView.main(TestTreeView.java:53) Caused by: java.lang.OutOfMemoryError: Java heap space 2.With the Java Heap Size is increased to 500 MB, then it is taking 10 seconds for putting all 5000 entries in the cache. Synchronous Cache Mode 1. ?With default Java Heap Size (64 MB)?, It is throwing an exception on putting every 50th element. The exception is ??. org.jboss.util.NestedRuntimeException: rsp=sender=SGNSCC397599901:2377, retval=null, received=false, suspected=false; - nested throwable: (org.jboss.cache.lock.TimeoutException: rsp=sender=SGNSCC397599901:2377, retval=null, received=false, suspected=false) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3248) at org.jboss.cache.TreeCache.put(TreeCache.java:1749) at org.jboss.cache.TreeCache.put(TreeCache.java:1732) at TestTreeView.main(TestTreeView.java:49) Caused by:org.jboss.cache.lock.TimeoutException: rsp=sender=SGNSCC397599901:2377, retval=null, received=false, suspected=false at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2153) at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2175) at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:85) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:43) at org.jboss.cache.interceptors.TransactionInterceptor.invoke(TransactionInterceptor.java:55) at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:3245) ... 3 more 2. With the Java Heap Size is increased to 500 MB, then 1st time it is taking 999 seconds (approx. 16 minutes) for putting all 5000 entries in the cache and putting every 50th entry, it is throwing the above mentioned exception. 3. But the second time, when I run the java program, then it takes 350 seconds (approx. 6 minutes) for putting all 5000 entries and sometimes in between process, the ?Java Heap Out of Memory exception? is coming. Regards Amit View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869755#3869755 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869755 --- 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-84) remove the naming strategy
remove the naming strategy -- Key: JBPM-84 URL: http://jira.jboss.com/jira/browse/JBPM-84 Project: JBoss jBPM Type: Task Reporter: Tom Baeyens Assigned to: Tom Baeyens Fix For: jBPM 3.0 alpha 2 now jbpm uses a naming strategy and it's impossible to prevent the application of this naming strategy onto user mappings if they are added to the jbpm session. the solution is to remove the jbpm naming strategy and specify the table and column names in the hibernate mapping files. -- 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-83) remove xml generation features
remove xml generation features -- Key: JBPM-83 URL: http://jira.jboss.com/jira/browse/JBPM-83 Project: JBoss jBPM Type: Task Reporter: Tom Baeyens Assigned to: Tom Baeyens Fix For: jBPM 3.0 alpha 2 since the designer plugin will build it's own model on top of an xml structure (instead of the jbpm object model), xml generation from the model is not necessary any more. this removes the necessity in the jbpm object model for keeping ordering (many lists can be replaced with maps) and it removes the reason of existence for the bidirectional relations housekeeping. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2 build.308 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050311095750Lbuild.308 BUILD COMPLETE - build.308Date of build: 03/11/2005 09:57:50Time to build: 21 minutes 11 secondsLast changed: 03/11/2005 09:28:39Last log entry: fixed JBAS-1386 commit option B does not work with CMP 1.x Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (3)1.13.4.9modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc/bridge/JDBCCMP1xFieldBridge.javafixed JBAS-1386 commit option B does not work with CMP 1.x1.1.2.10modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/Schema.javafixed JBAS-1570 NPE in jdbc2.Schema when no tx1.1.2.20modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed JBAS-1569 CMR loaders should be initialized before queries are compiled in jdbc2 pm
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - org.jgroups.blocks.RpcDispatcher and Exceptions
I'm looking into why the HAPartitionImpl extension of the RpcDispatcher.handle method is only logging checked exceptions thrown by the method invocation and I see that the RpcDispatcher has no concept of exceptions being thrown from the rpc call. I see the problem with merging exceptions, but it seems that there should be a notion of whether or not all targets of the invocation completed successfully as opposed to just dispatching the invocation. I would suggest that the RspList contain both normal return values, and exceptions thrown so that the invoker of the rpc call can make better decisions regarding the outcome of the rpc call. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869753#3869753 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869753 --- 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: Remoting in other AS products?
Absolutely. Just need the reomting jar and the jars it depends on. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869751#3869751 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869751 --- 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: Multiple portlets, 1 war
-pages.xml concept is to display multiple portlets on the same portal html page (your goal). You can put a portlet on different pages. I don't know why you say "It defines the url suffix which is used to access a particular portlet?" A portlet never requires -portal.xml but -pages.xml and -portal.xml can be define either in an application package with portlets or directly in the deploy directory of JBoss. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869748#3869748 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869748 --- 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: Multiple portlets, 1 war
Ok, that last post was a little ambigious. Here's an explanation: I want to put multiple portlets on the same portal html page. I understand I can define their locations (left, right) in the portlet.xml file. I can put their different classes in the same war. I don't clearly understand the concept of -pages.xml. It defines the url suffix which is used to access a particular portlet? Then why will 1 portlet have many different pages (when does a portlet require -portal.xml)? Now I want to make one application (one war), which is based on many different portlets showing up at different times on the user's screen. So for makign this application I will be making many different portlets. What I basically want to understand is how to show multiple portlets on one html screen. The ultimate goal is to transfer my web-application which is based on Freemarker, Struts and Hibernate to portlets. I know some questions might seem silly, or too easy, but its because I'm very new to jboss, portlets and portals. I have gone over a couple of JSR168 tutorials and have dissected a few portlets to get a better understanding. The ref guide clearly explained how to get one portlet to work in jboss portal and I can manage that easily now. Any suggestions on what to read are most welcome. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869747#3869747 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869747 --- 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: not able to get request.getPortletSession().invalidate()
janole, yes the spec says that and it is what it does, but you misunderstand it. portletsession.invalidate() invalidates the http session of the portlet war file, not the session of the portal. there are 2 separate sessions. the portable way to do that is to bundle your portlet in the war file of the portal. in that case the 2 sessions will be the same. but at the end, invalidating the session does not garantee that the users logout. you have no garantee that invalidating a session performs logout but this is the case on jboss portal when "form" based authentication is used. it would not work with "basic" authentication. And that behavior could change in the future for jboss portal as well. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869746#3869746 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869746 --- 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-1571) Logging of cluster rpc method exceptions at warn level is incorrect
Logging of cluster rpc method exceptions at warn level is incorrect --- Key: JBAS-1571 URL: http://jira.jboss.com/jira/browse/JBAS-1571 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: Scott M Stark Assigned to: Scott M Stark Fix For: JBossAS-5.0 Beta, JBossAS-4.0.2RC1, JBossAS-3.2.8 Final The HAPartitionImpl handler for cluster rpc method invocations logs Exceptions and Errors thrown from the reflected method invocation at warn level. This results in spurious warnings when the underlying invocation throws an exception as part of its normal operation. An example of where this occurs is when an ha-sigleton binds a jndi entry into its node, and a client does a lookup of the binding through ha-jndi. In a 3 node cluster A, B, C with the ha-singleton on A, a ha-jndi request going to B will produce the following NameNotFoundException on C: 06:52:07,359 WARN [DefaultPartition] javax.naming.NameNotFoundException: TheSingleton not bound These exceptions should be logged at trace level. -- 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.866 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311092145Lbuild.866 BUILD COMPLETE - build.866Date of build: 03/11/2005 09:21:45Time to build: 19 minutes 23 secondsLast changed: 03/11/2005 08:44:44Last log entry: fixed JBAS-1570 NPE in jdbc2.Schema when no tx Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (11)1.7modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/schema/Schema.javafixed JBAS-1570 NPE in jdbc2.Schema when no tx1.12modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed JBAS-1569 CMR loaders should be initialized before queries are compiled in jdbc2 pm1.2modifiedtdieslerwebservice/test/java/org/jboss/test/ws/soap/SOAPFaultTestCase.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/binding/SOAPBindingTestCase.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.16modifiedtdieslerwebservice/src/main/org/jboss/ws/Constants.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.7modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPBodyImpl.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPFaultImpl.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.8modifiedtdieslerwebservice/src/main/org/jboss/ws/server/ServiceEndpoint.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/server/ServiceEndpointInvoker.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.2modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/FaultException.javaServiceEndpoints transforms a FaultException into a SOAP fault message. More work to be done.1.2modifiedtdieslerj2ee/src/main/javax/xml/soap/SOAPBody.javajavadoc
[JBoss-dev] [Design of JBoss Portal] - Re: not able to get request.getPortletSession().invalidate()
The spec also defines: "If the HttpSession object is invalidated, the PortletSession object must also be invalidated by the portlet container.cxv If the PortletSession object is invalidated by a portlet, the portlet container must invalidate the associated HttpSession object." "The getCreationTime, getId, getLastAccessedTime, getMaxInactiveInterval, invalidate, isNew and setMaxInactiveInterval methods of the PortletSession interface must provide the same functionality as the methods of the HttpSession interface with identical names." So since HttpServletRequest.invalidate() invalidates the session and set remoteUser to null, I thougt the same would happen for PortletSession.invalidate() What you are saying is that the portlet session does not "own" the user. And that the portal itself has a http session, wich the user belongs to. If this is correct, how can I force a user logout from the portal in a portlet wich only implements JSR-168 standard classlib (and not the JBoss add-on classlib)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869743#3869743 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869743 --- 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-1444) Incorrect warning about undefined query method with CMP1.x
[ http://jira.jboss.com/jira/browse/JBAS-1444?page=comments#action_12316078 ] Eric van der Maarel commented on JBAS-1444: --- The error log messages are quite annoying. > Incorrect warning about undefined query method with CMP1.x > -- > > Key: JBAS-1444 > URL: http://jira.jboss.com/jira/browse/JBAS-1444 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Reporter: Peter Doornbosch > Priority: Minor > > > When deploying an EJB 1.1 bean using CMP, the following warning is issued for > each finder: > 17:02:33,989 WARN [JDBCQueryMetaDataFactory] The query method is not defined > in ejb-jar.xml: > This warning is invalid as query methods can not be defined in an EJB 1.1 > ejb-jar.xml. > The fix is trivial, as all necessary information is available: the warning is > issued by the method createJDBCQueryMetaData(Element, Map, > JDBCReadAheadMetaData readAhead) in the class JDBCQueryMetaDataFactory; the > test whether the query is defined (if (defaultValue == null)) should be > extended with "&& ! entity.isCMP1x()" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1386) commit option B does not work with CMP 1.x
[ http://jira.jboss.com/jira/browse/JBAS-1386?page=history ]
Alexey Loubyansky closed JBAS-1386:
---
Resolution: Done
Fix Version: JBossAS-4.0.2RC1
JBossAS-5.0 Alpha
JBossAS-3.2.8 Final
Fixed. Thanks and sorry for the delay.
> commit option B does not work with CMP 1.x
> --
>
> Key: JBAS-1386
> URL: http://jira.jboss.com/jira/browse/JBAS-1386
> Project: JBoss Application Server
> Type: Bug
> Components: CMP service
> Versions: JBossAS-4.0.1 Final
> Environment: jdk 1.4.2 on linux
> Reporter: Peter Doornbosch
> Assignee: Alexey Loubyansky
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1, JBossAS-3.2.8 Final
> Attachments: employee-ejb.jar
>
>
> When accessing a CMP 1.x entity bean with the commit option set to B, and the
> bean is already loaded (by a previous invocation), the bean is not loaded
> again from the database (as it should with commit option B). This can be
> easily verified by deploying such a bean and enabling sql logging.
> The cause of this bug is in the following method from JDBCCMP1xFieldBridge:
>public void resetPersistenceContext(EntityEnterpriseContext ctx)
>{
> if(isReadTimedOut(ctx))
> {
> JDBCContext jdbcCtx = (JDBCContext)ctx.getPersistenceContext();
> jdbcCtx.setFieldState(jdbcContextIndex, new FieldState(jdbcCtx));
> }
>}
> Assigning a 'new FieldState(jdbcCtx)' to the jdbcCtx effectively does
> nothing, because JDBCCMP1xFieldBridge.FieldState delegates to EntityState and
> the EntityState is not affected by this call. Hence, after this method, the
> state of the field is still "loaded", and thus this field is not part of the
> load-iterator created by JDBCEntityBridge.
> I think the fix is rather easy: just reset the field flags explicitely (as it
> is done in the cmp 2.x case), e.g.
> jdbcCtx.getEntityState().resetFlags(tableIndex);
--
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 build.425 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050311084229Lbuild.425 BUILD COMPLETE - build.425Date of build: 03/11/2005 08:42:29Time to build: 27 minutes 6 secondsLast changed: 03/11/2005 08:24:21Last log entry: fixed JBAS-1569 CMR loaders should be initialized before queries are compiled in jdbc2 pm Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.8.2.4modifiedloubyanskyserver/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.javafixed JBAS-1569 CMR loaders should be initialized before queries are compiled in jdbc2 pm1.1.2.1modifiedtdieslertestsuite/src/resources/webservice/exception/fault-envelops.xmlAdd expected fault envelops
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-217) Reply with quote is not working
Reply with quote is not working --- Key: JBPORTAL-217 URL: http://jira.jboss.com/jira/browse/JBPORTAL-217 Project: JBoss Portal Type: Bug Components: Forums Environment: Windows XP Reporter: Sudhir Kumar Machetti Assigned to: Julien Viet Priority: Minor I am trying to post reply with previous message in quotes. I clicked on quotes button. I got editor to post my reply. I have submitted me reply. I don't see previous message in quotes in my reply? Did I miss anything? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: entry for transaction :2 not found in tra
Awesome... Did an update of cvs head and rebuilt it and the error is gone. :) I can't believe the response time from you guys. It's just unreal. Thanks again! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869736#3869736 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869736 --- 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: When is next release to come out?
Where could I find the Hibernate-3/JBossCache-1.2.1 release? The first is warning that happened using with hibernate. How to avoid this warning to come out? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869735#3869735 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869735 --- 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: not able to get request.getPortletSession().invalidate()
PortletSession.invalidate() does not invalidate the current user, it only invalides the session related to the portlet application. The spec defines that. req.getLogout() invalidates another session which is not the same and performs logout. The session invalidated in the one of the portal. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869734#3869734 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869734 --- 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: (HIBERNATE-9) local application of naming strategy
local application of naming strategy Key: HIBERNATE-9 URL: http://jira.jboss.com/jira/browse/HIBERNATE-9 Project: Hibernate Type: Feature Request Reporter: Tom Baeyens Assigned to: Gavin King Priority: Minor It would be nice if users could apply a naming strategy on e.g. a hibernate mapping file. Now, the naming strategy can only be applied globally to the whole configuration. More general, it would be nice if users could specify multiple naming strategies and for each strategy on which mappings they apply. Consider supporting multiple ways of specifying on which mappings a naming strategy applies : by putting it in a mapping file, by specifying class names or table name prefixes, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1570) NPE in jdbc2.Schema when no tx
[ http://jira.jboss.com/jira/browse/JBAS-1570?page=history ] Alexey Loubyansky closed JBAS-1570: --- Resolution: Done Fix Version: JBossAS-4.0.2RC1 JBossAS-5.0 Alpha JBossAS-3.2.8 Final Fixed. > NPE in jdbc2.Schema when no tx > -- > > Key: JBAS-1570 > URL: http://jira.jboss.com/jira/browse/JBAS-1570 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-3.2.7 Final, JBossAS-5.0 Alpha, JBossAS-4.0.1 SP1 > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1, JBossAS-3.2.8 Final > > > package org.jboss.ejb.plugins.cmp.jdbc2.schema; > public class Schema > registering view synchronization throws NPE (line 42) when there is no active > transaction. Instead, a better exception should be thrown with a nice message. -- 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.92 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050311072201Lbuild.92 BUILD COMPLETE - build.92Date of build: 03/11/2005 07:22:01Time to build: 68 minutes 16 secondsLast changed: 03/11/2005 01:08:48Last log entry: Updated Unit Tests: (1967) Total Errors and Failures: (8)testNoClassDefFoundErrororg.jboss.test.classloader.test.BasicLoaderUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestMDBDeepRunAsorg.jboss.test.security.test.EJBSpecUnitTestCasetestSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestBMTSessionHandleNoDefaultJNDIorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestSessionTimeoutorg.jboss.test.cluster.test.SimpleTestCasetestSRPLoginWithAuxChallengeorg.jboss.test.security.test.SRPLoginModuleUnitTestCase Modifications since last build: (30)1.1.2.32modifiedbwang00testsuite/imports/test-jars.xmlUpdated1.1.2.31modifiedbwang00testsuite/imports/test-jars.xmlBack ported from 4.0.21.1.2.9modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/AttributeBasedClusteredSession.javaBack ported frm 4.0.21.1.2.12modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaBack ported frm 4.0.21.1.2.14modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaBack ported frm 4.0.21.1.2.14modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaBack ported frm 4.0.21.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossManager.javaBack ported frm 4.0.21.1.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/SessionBasedClusteredSession.javaBack ported frm 4.0.21.2.2.3modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/AbstractJBossManager.javaBack ported frm 4.0.21.1.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/web/BindingListener.javaBackported from 4.01.1.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/web/Person.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/AttributeBasedConcurrentTestCase.javaBackported from 4.01.10.2.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/BaseTest.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedAttrBasedTestCase.javaBackported from 4.01.3.6.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedSetAttributeTestCase.javaBackported from 4.01.3.6.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedSetTriggerTestCase.javaBackported from 4.01.3.2.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedTestCase.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/SessionBasedConcurrentTestCase.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/SessionEventTestCase.javaBackported from 4.01.4.6.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/SimpleTestCase.javaBackported from 4.01.1.2.3modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/getAttribute.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/invalidateSession.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/modifyAttribute.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/modifyPerfAttribute.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/setPerfSession.jspBackported from 4.01.1.2.4modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/setSession.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/web.xmlBackported from 4.01.4.8.1modifiedbwang00testsuite/src/resources/cluster/http/bindSession.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/jboss-service.xmlBackported from 4.01.1.2.2modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/ManageSnapshotServlet.javaFix the deprecated jfreechart usage. Resolves [JBAS-1101] NullPointerException at org.jfree.data.DefaultTableXYDataset.
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1570) NPE in jdbc2.Schema when no tx
NPE in jdbc2.Schema when no tx -- Key: JBAS-1570 URL: http://jira.jboss.com/jira/browse/JBAS-1570 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-3.2.7 Final, JBossAS-5.0 Alpha, JBossAS-4.0.1 SP1 Reporter: Alexey Loubyansky Assigned to: Alexey Loubyansky package org.jboss.ejb.plugins.cmp.jdbc2.schema; public class Schema registering view synchronization throws NPE (line 42) when there is no active transaction. Instead, a better exception should be thrown with a nice message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1569) CMR loaders should be initialized before queries are compiled in jdbc2 pm
[ http://jira.jboss.com/jira/browse/JBAS-1569?page=history ]
Alexey Loubyansky closed JBAS-1569:
---
Resolution: Done
Fix Version: JBossAS-4.0.2RC1
JBossAS-5.0 Alpha
JBossAS-3.2.8 Final
Fixed.
> CMR loaders should be initialized before queries are compiled in jdbc2 pm
> -
>
> Key: JBAS-1569
> URL: http://jira.jboss.com/jira/browse/JBAS-1569
> Project: JBoss Application Server
> Type: Bug
> Components: CMP service
> Versions: JBossAS-3.2.7 Final, JBossAS-5.0 Alpha, JBossAS-4.0.1 SP1
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1, JBossAS-3.2.8 Final
>
>
> Fix:
> $ cvs diff JDBCStoreManager2.java
> Enter passphrase for key '/home/alex/.ssh/identity':
> [EMAIL PROTECTED]'s password:
> Index: JDBCStoreManager2.java
> ===
> RCS file:
> /cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.java,v
> retrieving revision 1.11
> diff -r1.11 JDBCStoreManager2.java
> 169,170d168
> < //
> < //
> 178,180c176,183
> < //
> < //
> < // Start Phase 3: create tables and compile queries
> ---
> > // Start Phase 3: init cmr loaders
> > for(int i = 0; i < managers.size(); ++i)
> > {
> > JDBCStoreManager2 manager = (JDBCStoreManager2)managers.get(i);
> > manager.startEntity();
> > }
> >
> > // Start Phase 4: create tables and compile queries
> 435,436d437
> < entityBridge.start();
> <
> 472a474,479
> >private void startEntity()
> > throws DeploymentException
> >{
> > entityBridge.start();
> >}
> >
--
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-1569) CMR loaders should be initialized before queries are compiled in jdbc2 pm
CMR loaders should be initialized before queries are compiled in jdbc2 pm
-
Key: JBAS-1569
URL: http://jira.jboss.com/jira/browse/JBAS-1569
Project: JBoss Application Server
Type: Bug
Components: CMP service
Versions: JBossAS-3.2.7 Final, JBossAS-5.0 Alpha, JBossAS-4.0.1 SP1
Reporter: Alexey Loubyansky
Assigned to: Alexey Loubyansky
Fix:
$ cvs diff JDBCStoreManager2.java
Enter passphrase for key '/home/alex/.ssh/identity':
[EMAIL PROTECTED]'s password:
Index: JDBCStoreManager2.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc2/JDBCStoreManager2.java,v
retrieving revision 1.11
diff -r1.11 JDBCStoreManager2.java
169,170d168
< //
< //
178,180c176,183
< //
< //
< // Start Phase 3: create tables and compile queries
---
> // Start Phase 3: init cmr loaders
> for(int i = 0; i < managers.size(); ++i)
> {
> JDBCStoreManager2 manager = (JDBCStoreManager2)managers.get(i);
> manager.startEntity();
> }
>
> // Start Phase 4: create tables and compile queries
435,436d437
< entityBridge.start();
<
472a474,479
>private void startEntity()
> throws DeploymentException
>{
> entityBridge.start();
>}
>
--
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: not able to get request.getPortletSession().invalidate()
It should, as per the api: public void invalidate() | Invalidates this session (all scopes) and unbinds any objects bound to it. | Invalidating the portlet session will result in invalidating the underlying HttpSession | | Throws: | java.lang.IllegalStateException - if this method is called on a session which has already been invalidated If this is not hapenning, we need to take a closer look at it. Are you not getting the expected behaviour in beta1? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869726#3869726 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869726 --- 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.865 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311064505Lbuild.865 BUILD COMPLETE - build.865Date of build: 03/11/2005 06:45:05Time to build: 15 minutes 20 secondsLast changed: 03/11/2005 05:06:18Last log entry: made DeadlockDetection a managed attribute Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.233modifiedbelabancache/src/main/org/jboss/cache/TreeCache.javamade DeadlockDetection a managed attribute1.9modifiedbelabancache/src/main/org/jboss/cache/interceptors/CacheStoreInterceptor.javafixed http://jira.jboss.com/jira/browse/JBCACHE-111
[JBoss-dev] jboss-3.2-jdk-matrix build.74 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050311061015Lbuild.74 BUILD COMPLETE - build.74Date of build: 03/11/2005 06:10:15Time to build: 22 minutes 30 secondsLast changed: 03/11/2005 01:08:48Last log entry: Updated Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (30)1.1.2.32modifiedbwang00testsuite/imports/test-jars.xmlUpdated1.1.2.31modifiedbwang00testsuite/imports/test-jars.xmlBack ported from 4.0.21.1.2.9modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/AttributeBasedClusteredSession.javaBack ported frm 4.0.21.1.2.12modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/ClusteredSession.javaBack ported frm 4.0.21.1.2.14modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheManager.javaBack ported frm 4.0.21.1.2.14modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaBack ported frm 4.0.21.1.2.13modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossManager.javaBack ported frm 4.0.21.1.2.8modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/SessionBasedClusteredSession.javaBack ported frm 4.0.21.2.2.3modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/AbstractJBossManager.javaBack ported frm 4.0.21.1.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/web/BindingListener.javaBackported from 4.01.1.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/web/Person.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/AttributeBasedConcurrentTestCase.javaBackported from 4.01.10.2.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/BaseTest.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedAttrBasedTestCase.javaBackported from 4.01.3.6.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedSetAttributeTestCase.javaBackported from 4.01.3.6.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedSetTriggerTestCase.javaBackported from 4.01.3.2.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/ScopedTestCase.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/SessionBasedConcurrentTestCase.javaBackported from 4.01.2.8.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/SessionEventTestCase.javaBackported from 4.01.4.6.1modifiedbwang00testsuite/src/main/org/jboss/test/cluster/test/SimpleTestCase.javaBackported from 4.01.1.2.3modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/getAttribute.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/invalidateSession.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/modifyAttribute.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/modifyPerfAttribute.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/setPerfSession.jspBackported from 4.01.1.2.4modifiedbwang00testsuite/src/resources/cluster/http/http-scoped/setSession.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/web.xmlBackported from 4.01.4.8.1modifiedbwang00testsuite/src/resources/cluster/http/bindSession.jspBackported from 4.01.1.2.2modifiedbwang00testsuite/src/resources/cluster/http/jboss-service.xmlBackported from 4.01.1.2.2modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/ManageSnapshotServlet.javaFix the deprecated jfreechart usage. Resolves [JBAS-1101] NullPointerException at org.jfree.data.DefaultTableXYDataset.
[JBoss-dev] [Design of Mail Services] - Re: Error in org.jboss.mail.message.BouncedMail
http://jira.jboss.com/jira/browse/JBMAIL-32 - Kabir has fixed this. Will go in M3. You can also test in HEAD. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869712#3869712 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869712 --- 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 Mail Services] - Re: M2-final release available
Bla bla bla. You don't like MySQL. I don't like database XYZ. We will support as many dbs as is feasible and at the highest performance feasible. For now, I'd like that to be Hypersonic (for testing purposes), BerkleyDB JE, MySQL, PostgreSQL, and Oracle. Eventually I'd like to add MS SQL Server, Informix and Sybase to that. Once we get that far then we'll add support on an as needed basis. Besides, most comes for free with Hibernateits the blobby stuff that doesn't. MySQL is a JBoss Inc. partner. They are thoroughly nice and helpful guys. And this mail you so carefully used to disparage them is already served from MySQL. The JBoss Forums have been stored using MySQL pretty much from the beginning. (Yes there have been occassional problems because of Blob support and we weren't using InnoDB because we had to migrate, but life involves pain). In my experience, MySQL is a more than adeuate DB though it has its issues like any other. In my experience, all databases have bad remote protocols and horrid blob support :-) so I grant you the bar isn't high. Honestly I'm reasonably agnostic, I just want to see us support (in JBoss Mail Server) what people are already using. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869710#3869710 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869710 --- 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.105 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050311052914Lbuild.105 BUILD COMPLETE - build.105Date of build: 03/11/2005 05:29:14Time to build: 28 minutes 30 secondsLast changed: 03/10/2005 22:03:26Last log entry: Change the passivated session map to a ConcurrentReaderHashMap and update the passivated session removal logging to include the passivation time. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (10)1.27.2.1modifiedstarksmserver/src/main/org/jboss/ejb/plugins/StatefulSessionInstanceCache.javaChange the passivated session map to a ConcurrentReaderHashMap and update the passivated session removal logging to include the passivation time.1.10.6.1modifiedstarksmserver/src/main/org/jboss/ejb/plugins/LRUStatefulContextCachePolicy.javaUpdate the expired passivated session removal to only obtain the cache lock when determining the passivated session ids. The actual removal of the expired sessions from the pm is done without the cache lock. Resolves [JBAS-1560] Clustered stateful session bean removal of expired passivated instances causes deadlock.1.4.4.4modifiedstarksmtestsuite/src/main/org/jboss/test/testbeancluster/test/BeanUnitTestCase.javaAdd a container configuration with a rapid passivation and exipration setting to test deadlock issues seen in JBAS-1560.1.3.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/testbeancluster/bean/StatefulSessionBean.javaAdd a container configuration with a rapid passivation and exipration setting to test deadlock issues seen in JBAS-1560.1.8.4.3modifiedstarksmtestsuite/src/resources/testbeancluster/META-INF/ejb-jar.xmlAdd a container configuration with a rapid passivation and exipration setting to test deadlock issues seen in JBAS-1560.1.9.4.2modifiedstarksmtestsuite/src/resources/testbeancluster/META-INF/jboss.xmlAdd a container configuration with a rapid passivation and exipration setting to test deadlock issues seen in JBAS-1560.1.5.6.1modifiedstarksmcluster/src/main/org/jboss/ejb/plugins/StatefulHASessionInstanceCache.javaInclude the session id in the activation failure log message1.3.2.7modifiedbwang00tomcat/src/main/org/jboss/web/tomcat/tc5/session/JBossCacheService.javaJBAS-1565 NPE when granularity level is ATTRIBUTE1.2.6.1modifiedstarksmconsole/src/main/org/jboss/console/plugins/monitor/ManageSnapshotServlet.javaFix the deprecated jfreechart usage. Resolves [JBAS-1101] NullPointerException at org.jfree.data.DefaultTableXYDataset.1.12.2.5modifiedtdieslerwebservice/src/main/org/jboss/webservice/ServiceDeployerJSE.javaSupport multiple servlets when modifying web.xml
[JBoss-dev] [JBossCache] - Re: Memory problem with JBossCache
anonymous wrote : I looked at your modified testcase and added the Thread.sleep(5) to my own SimpleCacheTest.java after each put as you had done. In my testcase, sleep(5) is commented ! You're not running the same load if you sleep for 5ms between requests ! anonymous wrote : This time the memory consumption increases much more slowly and you can also see that the gc manages to free memory. However, the trend is still growing and after about 40 minutes both putters had consumed all JVM memory and a full gc was invoked. I ran 2 senders at full speed on my WindowsXP laptop (1 CPU). I can only reiterate that they didn't run out of memory at all. I used both SUN's 1.4.2_05 and SUN's 1.5.0_01. The second test I ran for ca. 15 minutes, and memory even decreased slightly after a few minutes. Oh, I re-read your prev statement, you're not saying you run out of memory, but that you're seeing full garbage collections ? Then I suggest increasing the size of the young generation: JGroups creates a lot of smaller objects that can be garbage collected almost immediately after creation, e.g. Messages, Events etc. So the eden space should be relatively good-sized, so that the max number of bytes generated by Messages should be smaller than the eden space. >From the JGroups side, you can control the number of messages buffered though >FC.max_credits/min_threshold and STABLE.max_bytes. anonymous wrote : Next, I took your version of SimpleCacheTest.java (with the receiver flag = false, and the System.out.println output commented away) and your NetCache.java and reran the test with the fc-fast configuration. I should now be running virtually the same testbench as you (apart from the console output and your JBosscache 1.2.1 jar). When running two simple.bat putters simultaneously I eat up all 200 MBs of JVM memory in less than 5 minutes in each JVM triggering a full gc. In my tests, I didn't run with receiver=true because that would have generated less load. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869709#3869709 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869709 --- 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 Mail Services] - Re: MailStore
Postgres's latest drivers seem to support streaming. They do so in 4k blocks, but thats pretty okay. There is another reason to use the store :-). JBossMQ...it...well makes multiple copies of the body. Ultimately we will need BOTH behaviors (Store and No Store). For this release Store-only is fine. This is a bit of a feature regression in that there are going to be people who might send the messages over JMS to other servers with other DBs. However, I can live with that for now because those peoplewellthey are a little cracked (that *won't* perform well). For the present you'll be limited to one DB on the same server as JBossMQ. Eventually there should be: 1. Always use store 2. Never use store 3. Use store when the message is > N kb So while I'm only asking for #1 for M3, don't code yourself into a corner with #2, #3 for M4 :-) i also think this is a great! Glad you guys are talking! This all looks like great work! -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869707#3869707 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869707 --- 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: not able to get request.getPortletSession().invalidate()
I have just "upgraded" to Beta 1, and I like the new login procedure mutch
better.
In fact much has improved. Keep up the good work!
I guess I have to start using CVS version to keep track of the news and
improvements.
request.logout() works fine in my custom logout function, and the reason for
that is that the function calls HttpServletRequest.invalidate() direct
/**
* Perform a logout.
*/
public void logout()
{
req.getSession().invalidate();
}
but still when i call request.getPortletSessionInvalidate(), invalidating of
the session is not done.
I thougt that request.getPortletSessionInvalidate() should do the same thing.
For security reasons we still want to provide easy access to logout in our
portlets.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869704#3869704
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869704
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBCACHE-111) Transaction not available in afterCompletion() of CacheStoreInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-111?page=history ] Bela Ban resolved JBCACHE-111: -- Resolution: Done fixed according to solution > Transaction not available in afterCompletion() of CacheStoreInterceptor > --- > > Key: JBCACHE-111 > URL: http://jira.jboss.com/jira/browse/JBCACHE-111 > Project: JBoss Cache > Type: Bug > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.1 > > > Reason: if LockInterceptor's afterCompletion() is executed before > CacheStoreInterceptor's afterCompletion(), the GTX is removed from the > TransactionTable. > SOLUTION: keep a ref to the modification list in CacheStoreInterceptor. -- 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-1568) Problem with JMSContainerInvoker objectname in Jboss 3.2.7
Problem with JMSContainerInvoker objectname in Jboss 3.2.7
--
Key: JBAS-1568
URL: http://jira.jboss.com/jira/browse/JBAS-1568
Project: JBoss Application Server
Type: Feature Request
Components: EJBs
Versions: JBossAS-3.2.7 Final
Environment: Fedora core 2
j2sdk1.4.2_05
JBoss 3.2.7
Reporter: chris_pollentier
In JBoss release 3.2.7, the ObjectName of the JMSContainerInvokers contains a
hashcode. This hashcode was added to resolve bug JBAS-275.
This makes it difficult to have other services depend on the
JMSContainerInvoker, since the exact ObjectName is unknown.
The jmx ObjectName of the JMSContainerInvoker is created by taking the
ObjectName of the MDB container and adding
'plugin=invoker,binding='
Extract from the method 'createService' of MessageDrivenContainer:
ObjectName containerName = super.getJmxName();
Hashtable props = containerName.getKeyPropertyList();
props.put("plugin", "invoker");
props.put("binding", invokerBinding);
ObjectName invokerName = new
ObjectName(containerName.getDomain(), props);
server.registerMBean(ci, invokerName);
No problem here, but in case of an MDB the containerName is:
jboss.j2ee:service=EJB,jndiName=
Since there are no interfaces to be defined for an MDB, the jndi name itself is
a dummy jndi name generated based on the MDB name and (since JBoss3.2.7) a
hashcode:
Extract from class BeanMetaData:
public String getLocalJndiName()
{
if (localJndiName == null)
{
// Generate a unique name based on ejbName + identityHashCode
localJndiName = "local/" + ejbName + '@' +
System.identityHashCode(ejbName);
// the '@' + System.identityHashCode(ejbName); was added in JBoss
3.2.7
}
return localJndiName;
}
Now let me explain my problem:
Before JBoss-3.2.7, the localJndiName that was generated did not contain the:
'@' + System.identityHashCode(ejbName);
The ObjectName of the JMSContainerInvoker was e.g.:
'jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB, plugin=invoker,
binding=inactive-message-driven-bean'
I now have a problem related to clustering:
A MDB that connects to a topic (with durable subscription) is running on each
node of my cluster.
Because they have the same durable subscription Id, only one
JMSContainerInvoker has deliveryActive set to true.
I had a SingetonController service calls the 'startDelivery' and 'stopDelivery'
methods on the JMSContainerInvokers to make sure that only the MDB on the
master node of the cluster processes the messages. This config was chosen to
have fail-over when the master node goes down.
Under JBoss 3.2.4 this was working fine (apart from a delay in the failover
which was fixed in JBoss3.2.7), but with JBoss3.2.7 I can no longer do this
because I cannot configure this SingletonController to be depending on the
JMSContainerInvoker:
On JBoss 3.2.4:
jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB,
plugin=invoker, binding=inactive-message-driven-bean
jboss:service=DefaultPartition
name="TargetName">jboss.j2ee:service=EJB,jndiName=com.something.SomeMDB,
plugin=invoker, binding=inactive-message-driven-bean
startDelivery
stopDelivery
On JBoss 3.2.7, the name of the invoker becomes something like:
'jboss.j2ee:service=EJB,[EMAIL PROTECTED], plugin=invoker,
binding=inactive-message-driven-bean'
I can only know the exact ObjectName of the invoker after delploying it
To solve this, it would be nice if there were a possibility to specify the
ObjectName to be used for a JMSContainerInvoker for some MDB, or to configure
the jndi-name of the MDB container.
--
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.864 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050311043308Lbuild.864 BUILD COMPLETE - build.864Date of build: 03/11/2005 04:33:08Time to build: 18 minutes 53 secondsLast changed: 03/11/2005 03:04:28Last log entry: added deadlockDetection attr Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.232modifiedbelabancache/src/main/org/jboss/cache/TreeCache.javaadded deadlockDetection attr
[JBoss-dev] [JBossCache] - Re: Memory problem with JBossCache
First, I ran the test with your new tcp file less the unsupported property and it failed miserably. Not only did a putter take minutes to start, when it later got going it consumed memory in big chunks say 2-3 MB between gc updates. Next, I looked at your modified testcase and added the Thread.sleep(5) to my own SimpleCacheTest.java after each put as you had done. In all fairness, that's probably a more realistic load than a continuous relentless put. I then ran the test with the fc-fast configuration. This time the memory consumption increases much more slowly and you can also see that the gc manages to free memory. However, the trend is still growing and after about 40 minutes both putters had consumed all JVM memory and a full gc was invoked. Next, I took your version of SimpleCacheTest.java (with the receiver flag = false, and the System.out.println output commented away) and your NetCache.java and reran the test with the fc-fast configuration. I should now be running virtually the same testbench as you (apart from the console output and your JBosscache 1.2.1 jar). When running two simple.bat putters simultaneously I eat up all 200 MBs of JVM memory in less than 5 minutes in each JVM triggering a full gc. Of course, after the full garbage collect the memory is cleaned up and in each putter the memory consumption is back to 25 MB after the gc. (And then starts to grow again). The problem is that in some app servers a full gc is something potentially dangerous since the full gc may totally shut down the JVM during the gc. Using e.g. Oracle 9ias the most likely result of a full gc is that the JVM is restarted which is something you don't want to happen in a heavily loaded enterprise application. What you need to do is to make the gc collect your JGroups garbage objects much more often. This is the problem with Java, in C++ you simply write "delete pObject" when you want to free memory, In Java you can't explicitly handle memory that way. Or maybe you can, in which case would be the solution you need to clean your JGroups objects? Another solution may be to handle memory more carefully in your JGroups stack and avoid using the new operator as often. Anyway, my conclusions at this point are the following: * repeated puts on the same key is not a recommended practice when using JBossCache (version 1.2) in a cluster. Apart from this oddity the cache seems to be working ok. * the fc-fast configuration seems to be most stable one and is preferred over UDP or TCP Best regards, Henrik Nyberg View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869692#3869692 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869692 --- 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 2.0 Beta 1
Hey Ronald, i just made the connection between you and the jBPM active guy. I will be working on the webui, not sure it will be all portlet for 3.0. I will likely use JSF so we can integrate this as portlet AND standalone webapp. Help is always welcome :) Let's continue the talk on the jBPM developer mailing list if you want. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869689#3869689 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869689 --- 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 problems
I have a build problem with the build system. My java installation is in "C:\Program Files\ " so the path contains a space, that is not handled correctly. To do so I have to change in tools/bin/ant.bat the lines if exist "%JAVA_HOME%\lib\tools.jar" call "%ANT_HOME%\bin\lcp.bat" "%JAVA_HOME%\lib\tools.jar" if exist "%JAVA_HOME%\lib\classes.zip" call "%ANT_HOME%\bin\lcp.bat" "%JAVA_HOME%\lib\classes.zip" to if exist "%JAVA_HOME%\lib\tools.jar" call "%ANT_HOME%\bin\lcp.bat" %JAVA_HOME%\lib\tools.jar if exist "%JAVA_HOME%\lib\classes.zip" call "%ANT_HOME%\bin\lcp.bat" %JAVA_HOME%\lib\classes.zip schoetz View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869687#3869687 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869687 --- 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-111) Transaction not available in afterCompletion() of CacheStoreInterceptor
[ http://jira.jboss.com/jira/browse/JBCACHE-111?page=comments#action_12316073 ] Bela Ban commented on JBCACHE-111: -- Original posting: What might be the reason for receiving the following exception? java.lang.Exception: entry for transaction :2 not found in transaction table | at org.jboss.cache.interceptors.CacheStoreInterceptor$SynchronizationHandler.afterCompletion(CacheStoreInterceptor.java:255) | at org.jboss.tm.TransactionImpl.doAfterCompletion(TransactionImpl.java:1418) | at org.jboss.tm.TransactionImpl.completeTransaction(TransactionImpl.java:1090) | at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:349) | at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:454) | at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:322) | at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:146) | at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:123) | at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192) | at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) | at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) | at org.jboss.ejb.Container.invoke(Container.java:870) | at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:413) | at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:82) | at $Proxy74.authenticate(Unknown Source) I am using normal TreeCache (not the aop one) as an MBean inside of JBoss 4.0.1 using REPL_SYNC with isolation level set to REPEATABLE_READ (I have also tried SERIALIZABLE) I have tried the 1.2 stable jar and the latest from cvs and received the same error. We use JBoss Cache extensively throughout our architecture so tracing it to the exact cause is proving very difficult for us. Any ideas? We have two TreeCache MBeans loaded (on persisted via the jdbc cache loader. The other has no cache loader) and in some places we are using them both. Could that cause problems? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869621#3869621 > Transaction not available in afterCompletion() of CacheStoreInterceptor > --- > > Key: JBCACHE-111 > URL: http://jira.jboss.com/jira/browse/JBCACHE-111 > Project: JBoss Cache > Type: Bug > Versions: 1.2 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.1 > > > Reason: if LockInterceptor's afterCompletion() is executed before > CacheStoreInterceptor's afterCompletion(), the GTX is removed from the > TransactionTable. > SOLUTION: keep a ref to the modification list in CacheStoreInterceptor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: entry for transaction :2 not found in tra
You found a bug. This was caused by the TransactionManager calling the registered SynchronizationListeners to be called in indeterministic order. If LockInterceptor happened to be called before CacheStoreInterceptor, the TX was removed, otherwise everything was okay. I created a JIRA bug report: http://jira.jboss.com/jira/browse/JBCACHE-111. I also fixed this (in CVS head). Will be part of 1.2.1. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869685#3869685 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869685 --- 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-testsuite build.25 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050311024945Lbuild.25 BUILD COMPLETE - build.25Date of build: 03/11/2005 02:49:45Time to build: 96 minutes 28 secondsLast changed: 03/10/2005 22:17:55Last log entry: Add a container configuration with a rapid passivation and exipration setting to test deadlock issues seen in JBAS-1560. Unit Tests: (2452) Total Errors and Failures: (72)testAllTx_RWLockorg.jboss.test.cache.stress.EvictionLocalStressTestCasetestConcurrentUpgradeorg.jboss.test.cache.test.local.TxDeadlockUnitTestCasetestMoreThanOneUpgraderorg.jboss.test.cache.test.local.TxDeadlockUnitTestCasetestScopedTransactionorg.jboss.test.classloader.test.ScopedTransactionUnitTestCasetestServerFoundorg.jboss.test.classloader.test.ScopedTransactionUnitTestCasetestServerFoundorg.jboss.test.cts.test.BmpUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.BmpUnitTestCasetestServerFoundorg.jboss.test.cts.test.CmpUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.CmpUnitTestCasetestInterJarCallorg.jboss.test.cts.test.IndependentJarsUnitTestCase(JRMP-Invoker)testCallByValueInSameJarorg.jboss.test.cts.test.IndependentJarsUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.IndependentJarsUnitTestCase(JRMP-Invoker)testInterJarCallorg.jboss.test.cts.test.IndependentJarsUnitTestCasetestCallByValueInSameJarorg.jboss.test.cts.test.IndependentJarsUnitTestCasetestServerFoundorg.jboss.test.cts.test.IndependentJarsUnitTestCasetestServerFoundorg.jboss.test.cts.test.LongWaitStatefulSessionUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.LongWaitStatefulSessionUnitTestCasetestServerFoundorg.jboss.test.cts.test.MDBUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatefulSessionLocalUnitTestCase(JRMP-Invoker)testPassivationByTimeLocalorg.jboss.test.cts.test.StatefulSessionLocalUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatefulSessionLocalUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatefulSessionUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.StatefulSessionUnitTestCasetestServerFoundorg.jboss.test.cts.test.StatelessSessionStressTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.StatelessSessionStressTestCasetestServerFoundorg.jboss.test.cts.test.StatelessSessionUnitTestCase(JRMP-Invoker)testServerFoundorg.jboss.test.cts.test.StatelessSessionUnitTestCasetestHelloorg.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestDataorg.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestJRMPSpeedorg.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestIIOPSpeedorg.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestJRMPSpeed2org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestIIOPSpeed2org.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestServerFoundorg.jboss.test.hellojrmpiiop.test.HelloTimingStressTestCasetestEjbInterceptionorg.jboss.test.hibernate.test.HibernateIntgUnitTestCasetestSpeedServletorg.jboss.test.jacc.test.WebIntegrationUnitTestCasetestOIL2MutliSessionOneConnectionorg.jboss.test.jbossmq.perf.OIL2InvocationLayerStressTestCasetestCallerIdentityPropagationorg.jboss.test.jca.test.SecurityContextUnitTestCasetestConfiguredIdentityPropagationorg.jboss.test.jca.test.SecurityContextUnitTestCasetestRunAsIdentityPropagationFSorg.jboss.test.jca.test.SecurityContextUnitTestCasetestRunAsIdentityPropagationDSorg.jboss.test.jca.test.SecurityContextUnitTestCasetestXAExceptionToTransactionRolledbackExceptionorg.jboss.test.jca.test.XAExceptionUnitTestCasetestRMERRInOnePCToTransactionRolledbackExceptionorg.jboss.test.jca.test.XAExceptionUnitTestCasetestCreateSubcontextorg.jboss.test.naming.test.PooledInvokerUnitTestCasetestLookupFailuresorg.jboss.test.naming.test.PooledInvokerUnitTestCasetestOldProxyorg.jboss.test.pooled.test.BeanStressTestCasetestServerFoundorg.jboss.test.securitymgr.test.BMPUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.CMPUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.MDBUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.StatefulSessionUnitTestCasetestServerFoundorg.jboss.test.securitymgr.test.StatelessSessionUnitTestCasetestSpeedServletorg.jboss.test.securitymgr.test.WebIntegrationUnitTestCasetestStatefulPassiviationExpirationorg.jboss.test.testbeancluster.test.BeanUnitTestCase(Default)testStatefulPassiviationExpirationorg.jboss.test.testbeancluster.test.BeanUnitTestCase(SyncModeNUseJvm)testDefaultTimeoutorg.jboss.test.tm.test.TxTimeoutUnitTestCasetestOverriddenTimeoutExpiresorg.jboss.test.tm.test.TxTimeoutUnitTestCasetestSpeedServletorg.jboss.test.web.test.WebIntegrationUnitTestCasetestNonPrimitiveGetorg.jboss.test.cluster.test.ScopedFieldBasedTestCase(Default)testNonPrimitiveModifyorg.jboss.test.cluster.test.ScopedFieldBasedTestCase(Default)testNonPrimitiveGetorg.jboss.test.cluster.test.ScopedFieldBasedTestCase(SyncModeNUs
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-111) Transaction not available in afterCompletion() of CacheStoreInterceptor
Transaction not available in afterCompletion() of CacheStoreInterceptor --- Key: JBCACHE-111 URL: http://jira.jboss.com/jira/browse/JBCACHE-111 Project: JBoss Cache Type: Bug Versions: 1.2 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.1 Reason: if LockInterceptor's afterCompletion() is executed before CacheStoreInterceptor's afterCompletion(), the GTX is removed from the TransactionTable. SOLUTION: keep a ref to the modification list in CacheStoreInterceptor. -- 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: Multiple portlets, 1 war
1) Anyname you want, it does not matter, as a rule you should call it [portalname]-portal.xml 2) i don't think it's a requirement 3) yes, anything you want 4) no, it can be anything you want 5) You can define different portals in 1 war Extra question) you define the portal-name once, you can define N pages per portal. I don't understand the end of your question. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869679#3869679 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869679 --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: portal 2 beta1 startup error
You need to copy jboss-cache.jar jgroups.jar and jboss-remoting.jar (like for alpha). Please refer to the installation documentation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869678#3869678 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869678 --- 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: When is next release to come out?
The first error typically means that you're trying to do some work on JBossCache on a transaction that is in the process of being rolled back, or committing, or on a TX marked as rolled back. The second error has been corrected in the Hibernate-3/JBossCache-1.2.1 release. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869675#3869675 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869675 --- 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
