[JBoss JIRA] (JGRP-1560) UnicastRequest.siteUnreachable does not check if it targets the site which is down
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-1560?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated JGRP-1560:
------------------------------
Summary: UnicastRequest.siteUnreachable does not check if it targets the site which is down (was: UnicastRequest.siteUnreachable does not check if targets the site which is down)
> UnicastRequest.siteUnreachable does not check if it targets the site which is down
> ----------------------------------------------------------------------------------
>
> Key: JGRP-1560
> URL: https://issues.jboss.org/browse/JGRP-1560
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.4
> Reporter: Radim Vansa
> Assignee: Bela Ban
>
> When {{RequestCorrelator}} holds several unicast requests to different sites and one of the sites becomes unreachable, it sets responses in all requests to unreachable. This is caused by {{UnicastRequest.siteUnreachable(short site)}} which checks that the target is a {{SiteAddress}} but not that the site in this address matches the unreachable site from the method argument.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JGRP-1560) UnicastRequest.siteUnreachable does not check if targets the site which is down
by Radim Vansa (JIRA)
Radim Vansa created JGRP-1560:
---------------------------------
Summary: UnicastRequest.siteUnreachable does not check if targets the site which is down
Key: JGRP-1560
URL: https://issues.jboss.org/browse/JGRP-1560
Project: JGroups
Issue Type: Bug
Affects Versions: 3.2.4
Reporter: Radim Vansa
Assignee: Bela Ban
When {{RequestCorrelator}} holds several unicast requests to different sites and one of the sites becomes unreachable, it sets responses in all request to unreachable. This is caused by {{UnicastRequest.siteUnreachable(short site)}} which checks that the target is a {{SiteAddress}} but not that the site in this address matches the unreachable site from the method argument.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-4692) Review SecurityContext associations
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/AS7-4692?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated AS7-4692:
----------------------------------
Fix Version/s: 7.3.0.Alpha1
(was: 7.2.0.Alpha1)
> Review SecurityContext associations
> ------------------------------------
>
> Key: AS7-4692
> URL: https://issues.jboss.org/browse/AS7-4692
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Labels: Security_SPI
> Fix For: 7.3.0.Alpha1
>
>
> We should re-review the approach we take for security context association within AS7 containers.
> Back at the time of AS 3 it fairly reliable to assume a 1:1 mapping of thread and client with the incoming connection being allocated it's own thread, this is no longer automatically the case and different containers can use different threading models e.g. using Executors to handle asynchronous requests.
> The problem with using a ThreadLocal approach is that every time a container diverges from the 1:1 mapping of thread and client that container needs to work around the issue of an invalid SecurityContext association.
> One possibility is to pass responsibility for managing the context to the container although this then introduces the question of how it is passed from container to container. This issue needs to consider this further.
> Also need to review further how the security context can be created at all entry points to the server and how it can be manually switched now that we use SASL on entry for remote calls we do now have the opportunity for equivalent behaviour at the entry point for both web and ejb type calls - in the past we only had this opportunity for web based calls and would only create a security context on entering the interceptors for the EJB calls.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JGRP-1560) UnicastRequest.siteUnreachable does not check if targets the site which is down
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-1560?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated JGRP-1560:
------------------------------
Description: When {{RequestCorrelator}} holds several unicast requests to different sites and one of the sites becomes unreachable, it sets responses in all requests to unreachable. This is caused by {{UnicastRequest.siteUnreachable(short site)}} which checks that the target is a {{SiteAddress}} but not that the site in this address matches the unreachable site from the method argument. (was: When {{RequestCorrelator}} holds several unicast requests to different sites and one of the sites becomes unreachable, it sets responses in all request to unreachable. This is caused by {{UnicastRequest.siteUnreachable(short site)}} which checks that the target is a {{SiteAddress}} but not that the site in this address matches the unreachable site from the method argument.)
> UnicastRequest.siteUnreachable does not check if targets the site which is down
> -------------------------------------------------------------------------------
>
> Key: JGRP-1560
> URL: https://issues.jboss.org/browse/JGRP-1560
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.4
> Reporter: Radim Vansa
> Assignee: Bela Ban
>
> When {{RequestCorrelator}} holds several unicast requests to different sites and one of the sites becomes unreachable, it sets responses in all requests to unreachable. This is caused by {{UnicastRequest.siteUnreachable(short site)}} which checks that the target is a {{SiteAddress}} but not that the site in this address matches the unreachable site from the method argument.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6266) Jndi cleanup is wrong in -ds.xml deployment
by Stefano Maestri (JIRA)
Stefano Maestri created AS7-6266:
------------------------------------
Summary: Jndi cleanup is wrong in -ds.xml deployment
Key: AS7-6266
URL: https://issues.jboss.org/browse/AS7-6266
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1
Reporter: Stefano Maestri
Assignee: Stefano Maestri
Fix For: 7.2.0.CR1, 7.1.4.Final (EAP)
We are always removing java: and java:/ prefixes for datasource jndi-name when -ds.xml file is used to deploy them
See forum for more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6245) ClassNotFoundException if CMP2 entity-command is used
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/AS7-6245?page=com.atlassian.jira.plugin.s... ]
Wolf-Dieter Fink updated AS7-6245:
----------------------------------
Fix Version/s: 7.2.0.Alpha1
7.1.4.Final (EAP)
> ClassNotFoundException if CMP2 entity-command is used
> -----------------------------------------------------
>
> Key: AS7-6245
> URL: https://issues.jboss.org/browse/AS7-6245
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Labels: cmp, ejb2
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> If a EJB2 - CMP2 EntityBean uses an entity-command 'mysql-get-generated-keys' to generate the primary key, the server deploy with an error message:
> Caused by: java.lang.RuntimeException: JBAS018572: Could not load driver class: com.mysql.jdbc.PreparedStatement
> This may happen for different entity-commands if other databases are used!
> If the datasource module is added to the org/jboss/as/cmp modules dependencies, the startup shows:
> MSC000001: Failed to start service ... : JBAS010785: Failed start store manager
> Caused by: java.lang.RuntimeException: JBAS010732: Couldn't create entity command
> Caused by: java.lang.RuntimeException: JBAS018574: Could not load org.jboss.resource.adapter.jdbc.StatementAccess
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months