9:26 a.m.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the security
service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
jaikiran pai commented on EJBTHREE-1467:
----------------------------------------
EJBTHREE-1485 (which is duplicate issue of this) has a sample application, details,
workaround(s) and logs for reproducing this issue.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Anil Saldhana reassigned EJBTHREE-1467:
---------------------------------------
Assignee: Stefan Guilhen
Stefan, we need to add a dependency on our security bean that does JNDI binding of
"java:/jaas" to the ejb3 deployer.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:24 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Stefan Guilhen commented on EJBTHREE-1467:
------------------------------------------
ok, I'm looking into this.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:31 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Anil Saldhana commented on EJBTHREE-1467:
-----------------------------------------
Maybe we should create security.xml in conf and add the bean that creates the java:jaas
binding there. The bootstrap.xml can also include security.xml
But we need to run this by Adrian (and I am sure he will veto it).
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:43 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Stefan Guilhen commented on EJBTHREE-1467:
------------------------------------------
Does this error only show when using a jboss-app.xml to declare the security domain?
I've tried starting the server with a deployed application that declares the security
domain using the SecurityDomain annotation and everything ran just fine. I'll try now
using the jboss-app.xml to see if I can reproduce this situation.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:59 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Stefan Guilhen commented on EJBTHREE-1467:
------------------------------------------
I've even tried the ear supplied by jaikiran pai in EJBTHREE-1485 and it started just
fine (yes, I've copied the application to the deploy folder before starting the AS -
thus no hotdeploy was performed).
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Anil Saldhana commented on EJBTHREE-1467:
-----------------------------------------
It is not a question of security domain. The question is ejb3 starts looking for a JBoss
security manager by doing java:jaas/sometthing. But the security bean that binds the
java:jaas context is coming later in deployment.
Something like: JBAS-5700
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
jaikiran pai commented on EJBTHREE-1467:
----------------------------------------
Stefan,
The EAR attached in EJBTHREE-1485 fails consistently on a clean JBoss-5 CR1.
16:31:39,046 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR1 (build:
SVNTag=JBoss_5_0_0_CR1 date=200806301254)
Not sure if anything has changed on your CR1 setup. Let me know if you need more details
to reproduce this.
P.S: This comment was not meant to sidetrack Anil's comment dated 12/Sep/08 02:04 PM
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:59 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Stefan Guilhen commented on EJBTHREE-1467:
------------------------------------------
Jaikiran,
I've checked out CR1 from the SVN and the deployment indeed fails consistently.
However, when running the same tests in the current trunk codebase everything works as
expected - no name not bound exceptions are raised and I can see the SecurityDomain.ear
being correctly deployed.
Looks to me that we won't see this issue in the next AS (CR2) version, which is to be
released very soon.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:56 a.m.
New subject: [JBoss JIRA] Closed: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
Stefan Guilhen closed EJBTHREE-1467.
------------------------------------
Resolution: Done
Closing this issue as it is not reproduceable in trunk. Next AS release (CR2) will already
have fixed this behavior.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:11 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1467) Fail to deploy EJB3 ear that uses a security-domain
[
https://jira.jboss.org/jira/browse/EJBTHREE-1467?page=com.atlassian.jira....
]
jaikiran pai commented on EJBTHREE-1467:
----------------------------------------
Confirmed. Works fine on JBoss-5 CR2 which got released today. Thanks.
Fail to deploy EJB3 ear that uses a security-domain
---------------------------------------------------
Key: EJBTHREE-1467
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1467
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 5.0.0.CR1
Environment: Ubuntu Linux, i386.
Sun Java 1.6.0_06
Reporter: Luis Fernando Planella Gonzalez
Assignee: Stefan Guilhen
When starting the JBoss server with a deployed ear which has on the jboss-app.xml a
security-domain, I always have an error on deploy, with a NameNotFoundException: jaas is
not bound.
However, when re-deploying the same ear after the server is initialized, the deploy runs
fine.
My guess is that for some reason the ejb deployer service is being run before the
security service...
The same ear can be deployed on JBoss 4.2.2 without problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6528
days inactive
6559
days old
11 comments
4 participants
participants (4)
-
Anil Saldhana (JIRA) -
jaikiran pai (JIRA)
-
Luis Fernando Planella Gonzalez (JIRA)
-
Stefan Guilhen (JIRA)