January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-306) Formatting error in RegistryConfiguration document.

by Mark Little (JIRA)

Formatting error in RegistryConfiguration document. --------------------------------------------------- Key: JBESB-306 URL: http://jira.jboss.com/jira/browse/JBESB-306 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Registry and Repository Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.0 Bruno wrote: "on Page 5 of the docs\services\RegistryConfiguration.pdf document the graphics overlap the text." -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-920) Port multiplexer integration unit tests to HEAD

by Brian Stansberry (JIRA)

Port multiplexer integration unit tests to HEAD ----------------------------------------------- Key: JBCACHE-920 URL: http://jira.jboss.com/jira/browse/JBCACHE-920 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.ALPHA2 -- 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, 3 months

1
1
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, 3 months

1
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, 3 months

1
2
0 / 0

[JBoss JIRA] Closed: (JBREM-369) For Connectors that support callbacks on SSL connections, there should be a unified means of configuring SSLServerSocket and callback Client SSLSocket.s.

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-369?page=all ] Ron Sigal closed JBREM-369. --------------------------- Resolution: Done This issue is out of date. The desired features already exist. In particular, there are a variety of parallel ways to configure server socket factories and callback socket factories - see the section "Socket factories and server socket factories" in Chapter 5 of the Remoting documentation. For example, SSL parameters passed in the configuration map to a Connector will find their way to the callback Client. > For Connectors that support callbacks on SSL connections, there should be a unified means of configuring SSLServerSocket and callback Client SSLSocket.s. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBREM-369 > URL: http://jira.jboss.com/jira/browse/JBREM-369 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.0.0.Beta1 > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.0.Beta1 (Bluto) > > > Currently, the SSLServerSocket is configured by creating an SSLServerSocketFactory, e.g., by way of configuring an SSLSocketBuilder, and calling setServerSocketFactory() on the server invoker. The SSLSockets used by the Client that makes push callbacks are configured by passing a configuration Map to the Connector constructor, which is used to create a RemotingSSLSocketFactory. These should be unified. In particular, it would be nice to pass a single configuration Map to Connector(). -- 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, 3 months

1
0
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, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-305) Document reference incorrect

by Mark Little (JIRA)

Document reference incorrect ---------------------------- Key: JBESB-305 URL: http://jira.jboss.com/jira/browse/JBESB-305 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Burr Sutter Priority: Minor Fix For: 4.0 Bruno wrote: "According to the samples\quickstarts\readme.txt read the RegistryConfiguration.pdf, it is located under $DIST_ROOT\docs\services\" -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-307) Misleading text

by Mark Little (JIRA)

Misleading text --------------- Key: JBESB-307 URL: http://jira.jboss.com/jira/browse/JBESB-307 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.0 RC1 Reporter: Mark Little Assigned To: Burr Sutter Priority: Minor Fix For: 4.0 Bruno wrote: "in the samples\quickstarts\readme.txt: "mysql-connector-java-3.1.12-bin.jar is included in each projects "lib" folder to allow each service to register itself (by updating the jUDDI MySQL db)." there is only one in the \samples\quickstarts\helloworld_db_registration\lib " -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-309) Remove buildfrom.distribution from trailblazer build.xml

by Kevin Conner (JIRA)

Remove buildfrom.distribution from trailblazer build.xml -------------------------------------------------------- Key: JBESB-309 URL: http://jira.jboss.com/jira/browse/JBESB-309 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 RC1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.0 The trailblazer samples still use the buildfrom.distribution flag to indicate that they are running from within a build. This flag is no longer needed as the jars are now in the same relative location. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-597) shouldn't be able to open rule twice in viewer

by Michael Neale (JIRA)

shouldn't be able to open rule twice in viewer ---------------------------------------------- Key: JBRULES-597 URL: http://jira.jboss.com/jira/browse/JBRULES-597 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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, 3 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2007