October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-409) Make a version of ScopedJbossClassPool that works with AS 5

by Kabir Khan (JIRA)

Make a version of ScopedJbossClassPool that works with AS 5 ----------------------------------------------------------- Key: JBAOP-409 URL: http://jira.jboss.com/jira/browse/JBAOP-409 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha5 -- 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

16 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4804) GenericHeaderAuthenticator injection of ssoid, sessioncookie name

by Anil Saldhana (JIRA)

GenericHeaderAuthenticator injection of ssoid, sessioncookie name ----------------------------------------------------------------- Key: JBAS-4804 URL: http://jira.jboss.com/jira/browse/JBAS-4804 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Reporter: Anil Saldhana Assigned To: Stefan Guilhen Fix For: JBossAS-4.2.3.GA http://wiki.jboss.org/wiki/Wiki.jsp?page=GenericHeaderBasedAuthentication Currently the two inputs - HttpHeaderForSSOAuth and SessionCookieForSSOAuth are read from the tomcat service (via JMX). We need to support the easier way of injecting these via WEB-INF/context.xml. This should be in addition. Create a test case called as GenericHeaderAuthenticationUnitTestCase (that is separate from the other earlier test case). This new test case should use a web application that has context.xml in the WEB-INF. The test case should not require a special server configuration (like the other test case). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Commented: (JBPM-2) process monitoring and statistics capabilities (BAM)

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-2?page=comments#action_12384380 ] Ronald van Kuijk commented on JBPM-2: ------------------------------------- This is NEW functionality.. so it is not dangerous at all (real admins look further than just a red flag ;-) ) It is not closed either since jbpm does not have this functionality (yet). I do think however that an issue can hardly be blocking if no version is assigned to it. > process monitoring and statistics capabilities (BAM) > ---------------------------------------------------- > > Key: JBPM-2 > URL: http://jira.jboss.com/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: N/A > Reporter: Ronald van Kuijk > Priority: Blocker > > JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=4990... > 1. jBPM should store the duration and start date of a state/process in the logs > 2. Write some detailed info on wiki > 3. Show processinstance and data > 4. day/week/month overviews > 5. near realtime data per process > 6. produce graphs of day/week/month overviews > Some more ideas i got from a requirements document... > - Number of cases processed in through a particular process definition > - Number of cases flowing through a particular activity > - Longest work item delay by activity > - Workitems awaiting a particular task > - Workitems in a specific worklist claimed and/or completed by a particular user > - Longest end-to-end delay > - Mean time to approve by activity by participant > - Mean end-to-end completion time. > as background info, here's what the competition says about BAM: > http://appian.com/AppianEnt/Analytics/analytics.html > http://www.webmethods.com/meta/default/folder/0000005936 > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduc... > http://www.tibco.com/software/business_optimization/activity_monitoring.j... > http://www.vitria.com/products/platform/bam.html > http://looselycoupled.com/glossary/BAM -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4830) TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans

by Michael Smith (JIRA)

TECH REVIEW: Getting Started Guide - Chapter 6. JMS and Message-Driven Beans ---------------------------------------------------------------------------- Key: JBAS-4830 URL: http://jira.jboss.com/jira/browse/JBAS-4830 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attached is an Open Office 2.0 Document contain a chapter of the Getting Started Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Getting_Started_Guide/beta422/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

16 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1116) Fail-over does not complete if a node different from the "active" one fails

by Ovidiu Feodorov (JIRA)

Fail-over does not complete if a node different from the "active" one fails --------------------------------------------------------------------------- Key: JBMESSAGING-1116 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1116 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.4.0.GA Reporter: Ovidiu Feodorov Assigned To: Tim Fox Priority: Critical Fix For: 1.4.0.SP1 This is how to replicate it: - Load a queue with a large number of messages (I used 100,000 10K text persistent messages), by connecting to node A - Start consuming concurrently using 50 parallel consumers over a connection to node A - Kill node B The consumption rate drop to 0 and never recovers. Trying to close the connection on the client-side never completes. Trying to shut down node A fails, need to eventually kill 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-406) Persistence refactoring

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-406: ------------------------------------- Should also support active passive failover > Persistence refactoring > ----------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Alpha > > > Need to refactor persistence so each node has its own storage. > We should provide at least three local persistence manager configs: > 1) JDBC local pm that works out of the box with HSQL - not recommended for production. > 2) BDB based pm that customers need to download - recommended for best performance. > Should optimise for the SAN use case. > Need to consider whether we need to support replication for failover too. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-406) Persistence refactoring

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-406: ------------------------------------- Very large messages should be stored outside the store on the file system and referenced via pointers. > Persistence refactoring > ----------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Alpha > > > Need to refactor persistence so each node has its own storage. > We should provide at least three local persistence manager configs: > 1) JDBC local pm that works out of the box with HSQL - not recommended for production. > 2) BDB based pm that customers need to download - recommended for best performance. > Should optimise for the SAN use case. > Need to consider whether we need to support replication for failover too. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-406) Persistence refactoring

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-406: ------------------------------------- We need to support automatic failover for the case where no shared file systems is present. In which case we need to replicate state to a buddy. This should be configurable on a per queue level. We can supply different levels of reliability: 1) Once and only once - with this mode we would need two streams one for replication messages and one for replication acks We would also need to store last sequence received in the storage to avoid having to use XA 2) At most once - replication sent async. Chance of message loss. 3) No replication > Persistence refactoring > ----------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Critical > Fix For: 2.0.0 Alpha > > > Need to refactor persistence so each node has its own storage. > We should provide at least three local persistence manager configs: > 1) JDBC local pm that works out of the box with HSQL - not recommended for production. > 2) BDB based pm that customers need to download - recommended for best performance. > Should optimise for the SAN use case. > Need to consider whether we need to support replication for failover too. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1118) Sucker connection created back to itself doesn't need to be created

by Jay Howell (JIRA)

Sucker connection created back to itself doesn't need to be created ------------------------------------------------------------------- Key: JBMESSAGING-1118 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1118 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.GA Reporter: Jay Howell Assigned To: Tim Fox Priority: Minor The following code in ClusteredConnecitonManager creates a connection back to itself and is never used in a non-clustered environment. So if you have a non-clustered environment, and you are running only one server, if you look at the connections in the peer mbean, you can see the connection client for the sucker. while (iter.hasNext()) { Map.Entry entry = (Map.Entry)iter.next(); Integer nid = (Integer)entry.getKey(); ClientConnectionFactoryDelegate delegate = (ClientConnectionFactoryDelegate)entry.getValue(); if (connections.get(nid) == null) { try { ConnectionInfo info = new ConnectionInfo(new JBossConnectionFactory(delegate), suckerUser, suckerPassword); log.trace(this + " created connection info " + info); connections.put(nid, info); info.start(); } catch (Exception e) { log.error("Failed to start connection info ", e); } } -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1120) Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel

by Brian Stansberry (JIRA)

Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel ----------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1120 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1120 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Distributed Support Affects Versions: 1.4.0.GA Reporter: Brian Stansberry Assigned To: Tim Fox JBM's usage of the JGroups JChannelFactory is causing the startup of the AS to hang. Problem is JBM's MultiplexerChannelFactory creates the data channel as follows: public Channel createDataChannel() throws Exception { return (Channel) server.invoke(this.channelFactory, MUX_OPERATION, new Object[]{dataStack, uniqueID + "-DATA", Boolean.TRUE, uniqueID}, MUX_SIGNATURE); } The Boolean.TRUE argument tells the JGroups multiplexer that a getState() call will be invoked for this service. JBM never calls getState(), so it *must not* pass Boolean.TRUE. Valid usages are: public Channel createDataChannel() throws Exception { String[] simpleMuxSignature = new String[] {"java.lang.String", "java.lang.String"}; return (Channel) server.invoke(this.channelFactory, MUX_OPERATION, new Object[]{dataStack, uniqueID + "-DATA"}, simpleMuxSignature); } or public Channel createDataChannel() throws Exception { return (Channel) server.invoke(this.channelFactory, MUX_OPERATION, new Object[]{dataStack, uniqueID + "-DATA", Boolean.FALSE, null}, MUX_SIGNATURE); } The former invokes a convenience method that delegates to the latter. Passing true for the "register_for_state_transfer" param tells JGroups that you will call getState(). If several services create MuxChannels based on the same underlying JChannel, JGroups will try to group together their state transfer calls. If several callers have created mux channels, it will block any initial getState() call until all of the callers call getState(), executing the state transfer when all the getState calls have been invoked. (Each service gets only its own state; the above just describes how JGroups attempts to coordinate things internally.) When JBM creates a mux channel with register_for_state_transfer=true and then never calls getState(), any other service that later creates a mux channel on the same underlying channel will not be able to properly execute a state transfer when it calls getState(). I'll open a JGroups JIRA to get proper javadoc for this interface. It's obviously pretty complex. -- 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

16 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007