[JBoss JIRA] Created: (AS7-1282) Rar classes are not made available to deployments
by Carlo de Wolf (JIRA)
Rar classes are not made available to deployments
-------------------------------------------------
Key: AS7-1282
URL: https://issues.jboss.org/browse/AS7-1282
Project: Application Server 7
Issue Type: Bug
Reporter: Carlo de Wolf
The rar classes are not made available to a deployment.
{noformat}
java.lang.ClassNotFoundException: org.hornetq.ra.inflow.HornetQActivationSpec from [Module "deployment.ejb3mdb.jar:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
{noformat}
JCA 1.6 20.3 Class Loading Requirements
{quote}
If a standalone resource adapter is configured to deliver messages to a message-
driven bean in an application, the standalone resource adapter must be made
available to the application.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JGRP-1382) VERIFY_SUSPECT can kick a live node soon after it re-joins
by Dennis Reed (Created) (JIRA)
VERIFY_SUSPECT can kick a live node soon after it re-joins
----------------------------------------------------------
Key: JGRP-1382
URL: https://issues.jboss.org/browse/JGRP-1382
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.20
Reporter: Dennis Reed
Assignee: Dennis Reed
Due to a timing issue, VERIFY_SUSPECT can kick a good member from the cluster soon after joining.
A live node currently in the cluster stops responding temporarily (garbage collection, NIC down, etc).
FD sends up a suspect message to VERIFY_SUSPECT.
VERIFY_SUSPECT times out and sends up the suspect message.
Before the node is kicked from the cluster, FD sends up another suspect message to VERIFY_SUSPECT.
Node is kicked from the cluster.
Node resumes, is shunned, and rejoins.
VERIFY_SUSPECT times out and sends up the suspect message.
Node is kicked from the cluster again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (SECURITY-565) Fix hardcoded server name for SPNEGOSockets
by Marcus Moyses (JIRA)
Fix hardcoded server name for SPNEGOSockets
-------------------------------------------
Key: SECURITY-565
URL: https://issues.jboss.org/browse/SECURITY-565
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Negotiation
Affects Versions: Negotiation_2.0.3.SP3
Reporter: Marcus Moyses
Assignee: Marcus Moyses
Fix For: Negotiation_2.0.3.SP4
A hardcoded server name was incorrectly set in the client side starting a negotiation handshake.
Now the server name can be set on the client side using the org.jboss.security.negotiation.server.principal system property.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months