December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-708) Move SessionState.handleFailoverOnConsumer() consumer failover logic to ClientConsumerDelegate/ConsumerState

by Ovidiu Feodorov (JIRA)

Move SessionState.handleFailoverOnConsumer() consumer failover logic to ClientConsumerDelegate/ConsumerState ------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-708 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-708 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Remove consumer failover logic from SessionState.handleFailoverOnConsumer() and put it into ClientConsumerDelegate/ConsumerState synchronizeWith(), following the pattern established for connection and session. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-709) Move SessionState.handleFailoverOnProducer() producer failover logic to ClientProducerDelegate/ProducerState

by Ovidiu Feodorov (JIRA)

Move SessionState.handleFailoverOnProducer() producer failover logic to ClientProducerDelegate/ProducerState ------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-709 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-709 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Clustering Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 Remove producer failover logic from SessionState.handleFailoverOnProducer() and put it into ClientProducerDelegate/ProducerState synchronizeWith(), following the pattern established for connection and session. Add step-by-step tests. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3863) Need to properly test the PooledInvoker for scoped invocations

by Adrian Brock (JIRA)

Need to properly test the PooledInvoker for scoped invocations -------------------------------------------------------------- Key: JBAS-3863 URL: http://jira.jboss.com/jira/browse/JBAS-3863 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-4.0.5.CR1 Reporter: Adrian Brock Since the above task shows that even the most basic marshalling of the return type is not present in the PooledInvoker code, there are clearly no serious tests of the PooledInvoker in scoped environments. These tests need to be written and any broken behaviour fixed. -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-713) Document better the cases in which failedNodeID of ConnectionFactoryEndpoint.createConnectionDelegate(username, password, failedNodeID) is disregarded

by Ovidiu Feodorov (JIRA)

Document better the cases in which failedNodeID of ConnectionFactoryEndpoint.createConnectionDelegate(username, password, failedNodeID) is disregarded ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-713 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-713 Project: JBoss Messaging Issue Type: Sub-task Components: Documentation and Training Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 1.2.0.Beta2 javadoc the method -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-298) URL parsing in EdtFtpImpl.checkParms()

by Bernard Tison (JIRA)

URL parsing in EdtFtpImpl.checkParms() -------------------------------------- Key: JBESB-298 URL: http://jira.jboss.com/jira/browse/JBESB-298 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Bernard Tison Assigned To: Mark Little I think there might be a problem with the way user/password information is parsed from the FTP URL for a FTP Gateway. This is based on the static router quickstart example. The jbossesb.xml contains the following provider definition: Code: <ftp-provider name="FTPprovider" hostname="localhost" > <ftp-bus busid="StaticRouterFtpGW" > <ftp-message-filter username="ftpuser" password="ftppassword" passive="false" directory="/tmp/esbInput" input-suffix=".dat" /> </ftp-bus> </ftp-provider> This results in the following definition in the jbossesb-gateway.xml: Code: <Ftp-Gateway URL="ftp://ftpuser:ftppassword@localhost:/tmp/esbInput" errorDelete="true" gatewayClass="org.jboss.soa.esb.listeners.gateway.RemoteGatewayListener" ...(non-relevant portion removed) "/> When the gateway is initialized, the org.jboss.internal.soa.esb.util.EdtFtpImpl class will parse the URL and connect to the FTP server. To parse the username/password out of the URL, the checkParms() method of the EdtFtpImpl class uses the following code (lines 190-198): Code: String[] sa = (null == url) ? null : url.getAuthority().split(":"); m_sUser = (null!=sa) ? sa[0] :m_oParms.getAttribute(PARMS_USER); if (null == m_sUser) throw new Exception("No username specified for FTP"); m_sPasswd = (null!=sa) ? sa[1] :m_oParms.getAttribute(PARMS_PASSWD); The url.getAuthority() method returns ftpuser:ftppassword@localhost, which results in m_sUser="ftpuser" and m_sPasswd="ftppassword@localhost". This should be: m_sUser="ftpuser" and m_sPasswd="ftppassword". Suggestion for fix: use url.getUserInfo() to get the user/password out of the FTP URL. This is how it is done in the EdtFtpImpl(FTPEpr p_oP, boolean p_bConnect) constructor. -- 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

17 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-295) Add support matrix to release notes

by Mark Little (JIRA)

Add support matrix to release notes ----------------------------------- Key: JBESB-295 URL: http://jira.jboss.com/jira/browse/JBESB-295 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Distribution, Documentation Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Define: what databases we support (and for what capabilities/services); what application servers we support; what JDK we support; what registries we support; which version of JBossRules we support. -- 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

17 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-918) Investigate Serializable interfaces for classes that are not streamed.

by Manik Surtani (JIRA)

Investigate Serializable interfaces for classes that are not streamed. ---------------------------------------------------------------------- Key: JBCACHE-918 URL: http://jira.jboss.com/jira/browse/JBCACHE-918 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Replication Reporter: Manik Surtani Assigned To: Manik Surtani Priority: Minor Fix For: 1.4.1.GA, 2.0.0.ALPHA2, 2.0.0.GA These classes implement Serializable: org.jboss.cache.OptimisticTreeNode org.jboss.cache.optimistic.DefaultDataVersion org.jboss.cache.optimistic.FqnComparator For 1.4.x: * Add compat svuid props For 2.x.x: * Remove Serializable from all 3 * Make DefaultDataVersion streamed using the marshaller and magic numbers. -- 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

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-914) Adapt JBCACHE-913 fix for JBC 2.0

by Brian Stansberry (JIRA)

Adapt JBCACHE-913 fix for JBC 2.0 --------------------------------- Key: JBCACHE-914 URL: http://jira.jboss.com/jira/browse/JBCACHE-914 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Vladimir Blagojevic Fix For: 2.0.0.GA Need to port JBCACHE-913 fix to HEAD, where the code works differently. Vladimir, I'm assigning this to you, because you are doing heavy lifting on state transfer and I don't want to step on you. I experimented with adding the following to StateTransferManager and calling it in setState right after the call to integrator.integrateState. That made the unit test (o.j.c.eviction.StateTransferIntegrationTest) pass. One concern I have is calling getChildren() on a node will end up pulling non-in-memory persisted nodes into RAM. A look at NodeImpl makes me think that's not the case, but that could change. /** * Generates EvictedEventNode notifications for all nodes of the tree. This is * called whenever the tree is initially retrieved (state transfer) */ protected void notifyEvictionPolicyOfNodesCreated(Node curr) { Node n; Set children; if (curr == null) return; Fqn fqn = curr.getFqn(); // JBCACHE-913 Region region = cache.getCacheSPI().getRegion(fqn, false); if (region != null) { region.putNodeEvent(new EvictedEventNode(fqn, NodeEventType.ADD_NODE_EVENT)); } if ((children = curr.getChildren()) != null) { for (Iterator it = children.iterator(); it.hasNext();) { n = (Node) it.next(); notifyEvictionPolicyOfNodesCreated(n); } } } Another approach would be to not bypass the interceptor chain when the integrator puts the node in the cache. That's very clean. But then we have to make sure no unwanted things are done by any interceptors. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-913) Nodes added via state transfer ignored by eviction policies

by Brian Stansberry (JIRA)

Nodes added via state transfer ignored by eviction policies ----------------------------------------------------------- Key: JBCACHE-913 URL: http://jira.jboss.com/jira/browse/JBCACHE-913 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1, 1.4.0.SP1, 1.4.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 1.4.1.GA, 2.0.0.GA When state transfer creates new nodes and adds them to the tree, any eviction policy is unaware of the addition. As a result, those nodes are ignored for eviction unless they are accessed. This is a side effect of the addition of the EvictionInterceptor in 1.4.0. The state transfer code generates TreeCacheListener node addition events, but with the EvictionInterceptor, the eviction policies are no longer listening for the events. Probable solution is to modify notifyAllNodesCreated to have it find any eviction region for any nodes it has added. Then have it generate an EvictedEventNode and pass it to Region.putNodeEvent. -- 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

17 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-127) Secure ftp

by Mark Little (JIRA)

Secure ftp ---------- Key: JBESB-127 URL: http://jira.jboss.com/jira/browse/JBESB-127 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 -- 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

17 years, 9 months

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006