Bug 899978 (JBPAPP6-1538)
Summary: | On failed secured connection during EJB invocations from a remote server instance an incorrect error message is shown | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ondrej Chaloupka <ochaloup> |
Component: | EJB | Assignee: | David M. Lloyd <david.lloyd> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0.0 | CC: | ochaloup |
Target Milestone: | --- | ||
Target Release: | TBD EAP 6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1538 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-03-19 15:09:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ondrej Chaloupka
2012-03-05 21:00:46 UTC
Link: Added: This issue Cloned from AS7-4042 I forgot to change the assignee after changing of jira workflow when EAP6 ER releases came. Adding info from AS7 cloned jira: I've checked it whether the current upstream version has the same "problem" and it has. In my point of view there should be some information that the connection failed. I guess that when I spot exception "No EJB receiver available for handling [...]" that it means that the connection succeeded but I put incorrect ejb name to search for. In case that the connection was not successful at all I think that would be nice to have some another more informative exception. Docs QE Status: Removed: NEW Assigning jpai EJB issues to david.lloyd. Please re-assign to Cheng or others as needed. Requesting clarification on owner, relevance, target since this bug more than than two years old and less than POST state: http://post-office.corp.redhat.com/archives/eap6-triage/2014-March/msg00001.html I don't think this is a valid bug, unless I'm reading it wrong. If the remote server is shut down before deployment, it's arguable whether or not the deployment should start, but if an invocation fails at run time, there's no reason to shut down the deployment or anything like that. Hi, the idea of this bug was request for improvement of the log message. The thing is that you are getting the same error message when container is up and you specify incorrect ejb name and the same one when remote server is down. There is no info about connection failure or so. If you think that it's not valid request then, please, close this bz. Thanks Ondra Here's my thoughts. I think the two error messages say exactly what the problem is - at the time - however, I don't think it makes sense to fail the service start just because the connection didn't come up. Connections are by definition outside the control of their corresponding service; the service state should represent the *desire* for a connection to be up, but it cannot represent the actual presence of the connection as long as it cannot control it. Thus I think the deployment should succeed whether or not the connection is available, which would in turn cause all failures to produce the second error message consistently. However, I know that my opinion on this matter may be opposed by some people, so I'm going to solicit some additional commentary before moving forward. I agree that the deployment should succeed. I'm all the time during testing a bit confused to understand whether ejb name was incorrect or the remote server is down when this message appears. But I agree. I think that the bz could be closed as not a bug. Thanks Per agreement. We can look at a separate issue to address the deployment question, upstream first. |