May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4445) ENC binding for TransactionSynchronizationRegistry

by Scott M Stark (JIRA)

ENC binding for TransactionSynchronizationRegistry -------------------------------------------------- Key: JBAS-4445 URL: http://jira.jboss.com/jira/browse/JBAS-4445 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, EJB3, JB5-Transaction Manager, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 Need to add a java:comp/TransactionSynchronizationRegistry binding to the server javax.transaction.TransactionSynchronizationRegistry This interface is intended for use by system level application server components such as persistence managers, resource adapters, as well as EJB and Web application components. This provides the ability to register synchronization objects with special ordering semantics, associate resource objects with the current transaction, get the transaction context of the current transaction, get current transaction status, and mark the current transaction for rollback. This interface is implemented by the application server by a stateless service object. The same object can be used by any number of components with thread safety. In standard application server environments, an instance implementing this interface can be looked up by a standard name via JNDI. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-163) Performance tests based on jboss.com nukes forums access logs

by Ryszard Kozmik (JIRA)

Performance tests based on jboss.com nukes forums access logs ------------------------------------------------------------- Key: JBFORUMS-163 URL: http://jira.jboss.com/jira/browse/JBFORUMS-163 Project: JBoss Forums Issue Type: Task Components: Forum Test Suite Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha We need to make sure that JBoss Forums are enough performant before trying to deploy moving all load from jboss.com nukes forums to them. IT should be able to provide nukes forums access logs and basing on them we should be able to create much more realistic load tests. junitperf toolkit with JProfiler might be a good choice for this task. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-350) Retroweaving does not translate java.util.Timer constructors new in Java5

by Manik Surtani (JIRA)

Retroweaving does not translate java.util.Timer constructors new in Java5 ------------------------------------------------------------------------- Key: JBBUILD-350 URL: http://jira.jboss.com/jira/browse/JBBUILD-350 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Environment: JBoss Retro 1.0.4.GA affected (This version is not in the select box for affected versions!) Reporter: Manik Surtani Assigned To: Paul Gier Java 5 added 2 new constructors to java.util.Timer which aren't retrotranslated at the moment, and causes runtime failures. http://java.sun.com/j2se/1.4.2/docs/api/java/util/Timer.html http://java.sun.com/j2se/1.5.0/docs/api/java/util/Timer.html -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBPM-653) make the process parent classloader configurable

by Ernst-Jan van der Laan (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-653?page=comments#action_12363181 ] Ernst-Jan van der Laan commented on JBPM-653: --------------------------------------------- I think this would solve the proble described in http://jboss.org/index.html?module=bb&op=viewtopic&t=73621 as well. > make the process parent classloader configurable > ------------------------------------------------ > > Key: JBPM-653 > URL: http://jira.jboss.com/jira/browse/JBPM-653 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > now, always the jBPM classloader is taken as a parent for the process classloaders. this should be made configurable. at least one other possibility should be to configure the context classloader. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-653) make the process parent classloader configurable

by Ernst-Jan van der Laan (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-653?page=comments#action_12363179 ] Ernst-Jan van der Laan commented on JBPM-653: --------------------------------------------- Hi, I created a modified version of jBPM also that caches the process classload as long as there are classes loaded by this classloader. It is using WeakReferences to cache the process class loaders. This can easly be extended/changed to a version using SoftReferences as well. The reason I created this cache is to enable to store serializable classes used as process instance variables deployed together with the process definition. By default only the handler classes can be deployed together with the process definition. To get this working I also modified the VariableInstance.getValue method to change the current thread context class loader to the ProcessClassLoader for this variable. The SerializableToByteArrayConverter revert function then uses this classloader to deserialize the class from the process definition database. If someone is interested in this solution please let me know and I will send the modified files. > make the process parent classloader configurable > ------------------------------------------------ > > Key: JBPM-653 > URL: http://jira.jboss.com/jira/browse/JBPM-653 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > now, always the jBPM classloader is taken as a parent for the process classloaders. this should be made configurable. at least one other possibility should be to configure the context classloader. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4403) JBAS4328UnitTestCase failures

by Martin Vecera (JIRA)

JBAS4328UnitTestCase failures ----------------------------- Key: JBAS-4403 URL: http://jira.jboss.com/jira/browse/JBAS-4403 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.2.0.CR2 Environment: dev90, x86_64, RHEL4, JVM Sun&BEA Reporter: Martin Vecera rg.jboss.test.jbossmq.test.JBAS4328UnitTestCase testApplicationServerExpiration Failure Expected only one message, the rest should have expired expected:<1> but was:<3> junit.framework.AssertionFailedError: Expected only one message, the rest should have expired expected:<1> but was:<3> at org.jboss.test.jbossmq.test.JBAS4328UnitTestCase.testApplicationServerExpiration(JBAS4328UnitTestCase.java:184) Probably wrong timing? -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-4400) Eclipse JDT Compiler Not Being Used

by Mike Millson (JIRA)

Eclipse JDT Compiler Not Being Used ----------------------------------- Key: JBAS-4400 URL: http://jira.jboss.com/jira/browse/JBAS-4400 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.2 Final Environment: RHEL 5 Workstation JDK build 1.5.0_11-b03 Reporter: Mike Millson Assigned To: Remy Maucherat Priority: Minor Steps to Reproduce: 1) Remove JBOSS_HOME/server/SERVER_NAME/deploy/jbossweb-tomcat55.sar/jasper-compiler-jdt.jar 2) Install a jsp page in ROOT.war. 3) Browse to the jsp page. Expected Behavior: An error related to the page not being able to be compiled. Actual Behavior: The jsp page is compiled and rendered in the browser. If you remove jasper-compiler-jdt.jar in Tomcat 5.5.9 standalone, jsp pages are not able to be compiled and displayed. It does not appear that jasper-compiler-jdt.jar is being used for anything in JBoss AS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1440) [RolePortlet] Consider changing the check box role selection to a dropdown list and a list box, or two list boxes. This will allow accommodation of an unlimited set of roles with a fixed size for the UI elements.

by Boleslaw Dawidowicz (JIRA)

[RolePortlet] Consider changing the check box role selection to a dropdown list and a list box, or two list boxes. This will allow accommodation of an unlimited set of roles with a fixed size for the UI elements. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1440 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1440 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR2 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6 Final Edit Roles Consider changing the check box role selection to a dropdown list and a list box, or two list boxes. This will allow accommodation of an unlimited set of roles with a fixed size for the UI elements. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4439) Error when saving message in database

by Pavel Rodionov (JIRA)

Error when saving message in database ------------------------------------- Key: JBAS-4439 URL: http://jira.jboss.com/jira/browse/JBAS-4439 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: Pavel Rodionov Assigned To: Adrian Brock Here is the problem, i'm using JMS and postgreSQL database in backend.Following stacktrace is generated: ************************************ 11:32:08,943 ERROR [STDERR] org.jboss.mq.SpyJMSException: Could not store message: 1 msg=0 hard NOT_STORED PERSISTENT queue=QUEUE.mailQueue priority=4 lateClone=false hashCode=5856205; - nested throwable: (org.postgresql.util.PSQLException: Can't infer the SQL type to use for an instance of org.jboss.mq.SpyTextMessage. Use setObject() with an explicit Types value to specify the type to use.) 11:32:08,943 ERROR [STDERR] at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:1097) 11:32:08,943 ERROR [STDERR] at org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:58) 11:32:08,943 ERROR [STDERR] at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:180) 11:32:08,943 ERROR [STDERR] at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:415) 11:32:08,943 ERROR [STDERR] at org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:399) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.server.JMSServerInterceptorSupport.addMessage(JMSServerInterceptorSupport.java:106) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.security.ServerSecurityInterceptor.addMessage(ServerSecurityInterceptor.java:168) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.server.TracingInterceptor.addMessage(TracingInterceptor.java:226) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.server.JMSServerInvoker.addMessage(JMSServerInvoker.java:112) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:111) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398) 11:32:08,944 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) 11:32:08,944 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) 11:32:08,944 ERROR [STDERR] Caused by: org.postgresql.util.PSQLException: Can't infer the SQL type to use for an instance of org.jboss.mq.SpyTextMessage. Use setObject() with an explicit Types value to specify the type to use. 11:32:08,944 ERROR [STDERR] at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1656) 11:32:08,944 ERROR [STDERR] at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.setObject(WrappedPreparedStatement.java:478) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.pm.jdbc2.PersistenceManager.setBlob(PersistenceManager.java:1190) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:1128) 11:32:08,944 ERROR [STDERR] at org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:1082) 11:32:08,944 ERROR [STDERR] ... 13 more ***************************************************** Here is the code for publishing message in queue: private void sendMail(String where) { QueueConnection cnn; QueueSender sender; QueueSession sess; Queue queue; try { InitialContext ctx = new InitialContext(); queue = (Queue) ctx.lookup("queue/mailQueue"); QueueConnectionFactory factory = (QueueConnectionFactory) ctx.lookup("ConnectionFactory"); cnn = factory.createQueueConnection(); sess = cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE); TextMessage msg = sess.createTextMessage("HAHAHA"); sender = sess.createSender(queue); sender.send(msg); sess.close(); } catch (JMSException e) { e.printStackTrace(); } catch (Exception e) { e.printStackTrace(); } } ********************************** It's queue consumer: @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"), @ActivationConfigProperty(propertyName="destination", propertyValue="queue/mailQueue") }) public class MailSenderMDB implements MessageListener { @Resource(mappedName = "java:/mail/VCSMail") private Session mailer; public void onMessage(Message message) { TextMessage textMessage = (TextMessage) message; System.out.println("message = " + textMessage); } } -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-873) Optional "; " when newlines exisit for MVEL consequences

by Michael Neale (JIRA)

Optional ";" when newlines exisit for MVEL consequences ------------------------------------------------------- Key: JBRULES-873 URL: http://jira.jboss.com/jira/browse/JBRULES-873 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.MR2 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.0.0.MR3 Similar to MVEL command line (yes it has one) - ";" are optional if there is a newline. If an expression spans lines (ie unbalanced brackets of any sorts) then that is fine (ie expression is allowed to span lines in that case). So ";" can be optional. -- 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, 2 months

1
1
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 May 2007