March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1256) Add support for Producer-side templates.

by Chris Laprun (JIRA)

Add support for Producer-side templates. ---------------------------------------- Key: JBPORTAL-1256 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1256 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-920) Make sure JBM 1.2. works with ESB 4.0

by Ovidiu Feodorov (JIRA)

Make sure JBM 1.2. works with ESB 4.0 ------------------------------------- Key: JBMESSAGING-920 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-920 Project: JBoss Messaging Issue Type: Task Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Blocker Fix For: 1.2.1.CR1 Kurt's report: I have extracted the 'essence' of what our ESB engine does with JMS messaging. I'm sending a message to queue/A and then I'm receiving the same message, I do some cleanup (closing session and connection) and then it starts all over again. Yes for each message I'm setting up the connection and then cleaning it up. The problem I'm seeing is the the GC is not able to clean up the JMS objects as it loops around. So at some point this this example nicely blows up when it runs out of memory. Your mileage may vary but it usually is around 800 messages. Any ideas why the GC can't make this work? I've testing this with JBM 1.2 GA. But I think JBMQ has the same problem. I'm running JDK-1.5.0_10. JBossMQ crashes too. Although a different error it's also due to running out of memory. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-3932) Security Deployer to manage the JACC metadata

by Anil Saldhana (JIRA)

Security Deployer to manage the JACC metadata --------------------------------------------- Key: JBAS-3932 URL: http://jira.jboss.com/jira/browse/JBAS-3932 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta2 Basically there is a need to maintain PolicyConfiguration objects for individual JEE components in a deployment and then link them via graph. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4231) JMXOpsAccessControlFilter is Not Thread Safe

by Darran Lofthouse (JIRA)

JMXOpsAccessControlFilter is Not Thread Safe -------------------------------------------- Key: JBAS-4231 URL: http://jira.jboss.com/jira/browse/JBAS-4231 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP2 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 , JBossAS-3.2.8.SP2 According to the servlet specification (SRV.6.2.1) for each <filter> definition only one instance is instantiated per JVM. The current implementation of JMXOpsAccessControlFilter stores the roles of the current user in a member variable, if there are mutliple calls simultaneously there will be a race condition one call can receive the permissions of the other user. http://wiki.jboss.org/wiki/Wiki.jsp?page=AccessControlForJMXConsole -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3792) Better error reporting when messages "mysteriously" vanish

by Adrian Brock (JIRA)

Better error reporting when messages "mysteriously" vanish ---------------------------------------------------------- Key: JBAS-3792 URL: http://jira.jboss.com/jira/browse/JBAS-3792 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: Adrian Brock Fix For: JBossAS-4.0.6.GA It is commonly the case that people try to run two instances of JBossMQ against the same database tables. This can lead to errors like the ones in the parent task or a similar message in the delete when doing acknowledgements. These error messages need improving and also give a hint to the possible reasons, e.g. 1) competing JBossMQs trying to share the same database 2) trying to use a replicating database that does not support synchronous replication (i..e there is a delay in a row getting written to one database before it appears in the other database) The parent issue's error message belongs in org.jboss.mq.pm.jdbc2.PersistenceManager public SpyMessage loadFromStorage(MessageReference messageRef) throws JMSException { ... rs = stmt.executeQuery(); if (rs.next()) return extractMessage(rs); + else throw new JMSException("Unable to load message " + messageRef + " from storage, are you trying to share database tables between JBossMQ instances? Are you using a replicating database that does not support synchronous replication?"); - return null; -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBAS-4178) RunAsListener uses unsupported implementation

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4178?page=all ] Anil Saldhana closed JBAS-4178. ------------------------------- Resolution: Done JBossWeb has the synchronization removed. Available for both JBoss4.2.0 and 5.x > RunAsListener uses unsupported implementation > --------------------------------------------- > > Key: JBAS-4178 > URL: http://jira.jboss.com/jira/browse/JBAS-4178 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.5.GA > Reporter: Ryan Campbell > Assigned To: Anil Saldhana > Priority: Critical > Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3 > > > Class org.jboss.web.tomcat.security.RunAsListener is an implementation of InstanceListener interface used for establishment of run-as role for servlet init/destroy events. According to tomcat developers, InstanceListener interface is meant for debugging purposes only and is causing some performace degradations. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-4178) RunAsListener uses unsupported implementation

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4178?page=all ] Anil Saldhana updated JBAS-4178: -------------------------------- Fix Version/s: (was: JBossAS-4.0.5.SP1 ) > RunAsListener uses unsupported implementation > --------------------------------------------- > > Key: JBAS-4178 > URL: http://jira.jboss.com/jira/browse/JBAS-4178 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.5.GA > Reporter: Ryan Campbell > Assigned To: Anil Saldhana > Priority: Critical > Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3 > > > Class org.jboss.web.tomcat.security.RunAsListener is an implementation of InstanceListener interface used for establishment of run-as role for servlet init/destroy events. According to tomcat developers, InstanceListener interface is meant for debugging purposes only and is causing some performace degradations. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4225) Error starting up jbossmq PersistenceManager with Sybase

by Rajesh Rajasekaran (JIRA)

Error starting up jbossmq PersistenceManager with Sybase -------------------------------------------------------- Key: JBAS-4225 URL: http://jira.jboss.com/jira/browse/JBAS-4225 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Reporter: Rajesh Rajasekaran Assigned To: Adrian Brock Fix For: JBossAS-4.2.0.GA Looks like a SQL error when creating the JMS tables with sybase. I have attached the sybase specific files needed to reproduce this issue with the jboss default config 1. Copy sybase-ds.xml under deploy dir. (delete hsqldb.xml) 2. Copy sybase-jdbc2-service.xml under deploy/jms (delete hsqldb-jdbc2-service.xml) 3. Copy jconn2.jar under lib The configurations connect to the sybase instance in the QA lab. 16:25:23,328 WARN [ServiceController] Problem starting service jboss.mq:service=PersistenceManager org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (com.sybase.jdbc2.jdbc.SybSQLException : The derived table expression is missing a correlation name. Check derived table syntax in the Reference Manual. ) at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:492) at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1809) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at org.jboss.system.ServiceController.start(ServiceController.java:435) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) Caused by: com.sybase.jdbc2.jdbc.SybSQLException: The derived table expression is missing a correlation name. Check derived table syntax in the Reference Manual. at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:3178) at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2481) at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203) at com.sybase.jdbc2.jdbc.SybStatement.queryLoop(SybStatement.java:1611) at com.sybase.jdbc2.jdbc.SybStatement.executeQuery(SybStatement.java:1596) at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeQuery(SybPreparedStatement.java:96) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:236) at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:424) ... 111 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-4230) Be explicit about allowing NULL in the JBossMQ JDBC configuration

by Adrian Brock (JIRA)

Be explicit about allowing NULL in the JBossMQ JDBC configuration ----------------------------------------------------------------- Key: JBAS-4230 URL: http://jira.jboss.com/jira/browse/JBAS-4230 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.0.CR1 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1 Comment from super task: "Also, If you omit null or not null in the create table statement, Adaptive Server uses the null mode defined for the database (by default, NOT NULL). Hence while creating the JMS_USERS table, and inserting users, i get this error. The column CLIENTID in table JMS_USERS does not allow null values. CREATE TABLE JMS_USERS (USERID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128), PRIMARY KEY(USERID)) INSERT INTO JMS_USERS (USERID, PASSWD) VALUES ('guest', 'guest') Either we need to update the sql in which case we need to provide a separate sybase-jdbc-state-service.xml? Or I can set this on the sybase database. sp_dboption db_name, "allow nulls by default", true I am following the 2nd option. " So we need to explicity say which columns allow NULL. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1321) In a JSF portlet, reading preferences returns various values

by Adam Warski (JIRA)

In a JSF portlet, reading preferences returns various values ------------------------------------------------------------ Key: JBPORTAL-1321 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1321 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Beta1 Environment: AS 4.0.5, Portal 2.6 beta 1 Reporter: Adam Warski Fix For: 2.6.CR1 In a JSF portlet, during various phases of the request lifecycle, I read a portlet preference, and get different values. More precisely: * I get the default value of the preference (as written in portlet.xml), during the initial phases (this value is incorrect) * I get the proper value, from the portlet instance definition (as written in portlet-instances.xml), during later phases This has many weird implications, like jsf actions seeming not to work etc. I attach a sample portlet in both binary and source versions. When deployed, go to the "testfacelets" page, and click on the "Invoke action" link, and observe output of the server. You'll see that in the beginning, when the "pref1" preference is read, it returns a value from project.xml - 0. Later, the proper value from portlet-instances.xml, namely 1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007