5:11 p.m.
Shadow Creeper created JBAS-9487:
------------------------------------
Summary: JBoss 5.1.0.GA deploy.last fails if included EAR contains beans
Key: JBAS-9487
URL: https://issues.jboss.org/browse/JBAS-9487
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.1.0.GA
Environment: Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Reporter: Shadow Creeper
Assignee: Ales Justin
Attachments: deploy.last.tgz, test-server-sources.tgz
When deploying an EAR in server/.../deploy/deploy.last/ (so that it will not be started
until everything else has started) there is complete failure of all included beans.
Apparently, if there are beans in the EAR, it is in some cases listed in JNDI as
"...ear=deploy.last,jar=..." rather that
"...ear=test-ear.ear,jar=..."
According to the server log, the bean is bound to "deploy/TestSoloBean/local"
rather than "test-ear/TestSoloBean/local"
The only way to get the deploy.last directory to deploy anything is if the EAR in the
deploy.last directory has no beans.
--
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
5:11 p.m.
[
https://issues.jboss.org/browse/JBAS-9487?page=com.atlassian.jira.plugin....
]
Shadow Creeper updated JBAS-9487:
---------------------------------
Attachment: deploy.last.tgz
test-server-sources.tgz
Attached a simple test case.
JBoss 5.1.0.GA deploy.last fails if included EAR contains beans
---------------------------------------------------------------
Key: JBAS-9487
URL: https://issues.jboss.org/browse/JBAS-9487
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.1.0.GA
Environment: Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Reporter: Shadow Creeper
Assignee: Ales Justin
Labels: deploy, deploy.last, jboss5
Attachments: deploy.last.tgz, test-server-sources.tgz
When deploying an EAR in server/.../deploy/deploy.last/ (so that it will not be started
until everything else has started) there is complete failure of all included beans.
Apparently, if there are beans in the EAR, it is in some cases listed in JNDI as
"...ear=deploy.last,jar=..." rather that
"...ear=test-ear.ear,jar=..."
According to the server log, the bean is bound to "deploy/TestSoloBean/local"
rather than "test-ear/TestSoloBean/local"
The only way to get the deploy.last directory to deploy anything is if the EAR in the
deploy.last directory has no beans.
--
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
5:13 p.m.
[
https://issues.jboss.org/browse/JBAS-9487?page=com.atlassian.jira.plugin....
]
Shadow Creeper updated JBAS-9487:
---------------------------------
Environment:
Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Java 6 Sun 1.6.0.26
was:
Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Forum Reference: https://community.jboss.org/thread/198638 (was:
https://community.jboss.org/thread/198638)
JBoss server log from the attached test case:
15:08:04,281 INFO [JBossASKernel] Created KernelDeployment for: test-ejb-01.00.00.jar
15:08:04,282 INFO [JBossASKernel] installing bean:
jboss.j2ee:jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3
15:08:04,282 INFO [JBossASKernel] with dependencies:
15:08:04,282 INFO [JBossASKernel] and demands:
15:08:04,282 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
15:08:04,282 INFO [JBossASKernel] and supplies:
15:08:04,282 INFO [JBossASKernel]
jndi:deploy/TestSoloBean/local-test.server.ejb.TestSolo
15:08:04,282 INFO [JBossASKernel] jndi:deploy/TestSoloBean/remote
15:08:04,282 INFO [JBossASKernel] jndi:deploy/TestSoloBean/local
15:08:04,282 INFO [JBossASKernel] Class:test.server.ejb.TestSolo
15:08:04,282 INFO [JBossASKernel] Added
bean(jboss.j2ee:jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3) to
KernelDeployment of: test-ejb-01.00.00.jar
15:08:04,282 INFO [EJB3EndpointDeployer] Deploy
AbstractBeanMetaData@75304935{name=jboss.j2ee:ear=deploy.last,jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container]
constructor=null autowireCandidate=true}
15:08:04,298 INFO [SessionSpecContainer] Starting
jboss.j2ee:jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3
15:08:04,298 INFO [EJBContainer] STARTED EJB: test.server.ejb.TestSoloBean ejbName:
TestSoloBean
15:08:04,302 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global
JNDI:
deploy/TestSoloBean/local - EJB3.x Default Local Business Interface
deploy/TestSoloBean/local-test.server.ejb.TestSolo - EJB3.x Local Business
Interface
15:08:04,337 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment
"jboss.j2ee:ear=deploy.last,jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3_endpoint"
is missing the following dependencies:
Dependency
"jboss.j2ee:ear=deploy.last,jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3"
(should be in state "Configured", but is actually in state "** NOT FOUND
Depends on
'jboss.j2ee:ear=deploy.last,jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3'
**")
DEPLOYMENTS IN ERROR:
Deployment
"jboss.j2ee:ear=deploy.last,jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3"
is in error due to the following reason(s): ** NOT FOUND Depends on
'jboss.j2ee:ear=deploy.last,jar=test-ejb-01.00.00.jar,name=TestSoloBean,service=EJB3'
**
JBoss 5.1.0.GA deploy.last fails if included EAR contains beans
---------------------------------------------------------------
Key: JBAS-9487
URL: https://issues.jboss.org/browse/JBAS-9487
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.1.0.GA
Environment: Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Java 6 Sun 1.6.0.26
Reporter: Shadow Creeper
Assignee: Ales Justin
Labels: deploy, deploy.last, jboss5
Attachments: deploy.last.tgz, test-server-sources.tgz
When deploying an EAR in server/.../deploy/deploy.last/ (so that it will not be started
until everything else has started) there is complete failure of all included beans.
Apparently, if there are beans in the EAR, it is in some cases listed in JNDI as
"...ear=deploy.last,jar=..." rather that
"...ear=test-ear.ear,jar=..."
According to the server log, the bean is bound to "deploy/TestSoloBean/local"
rather than "test-ear/TestSoloBean/local"
The only way to get the deploy.last directory to deploy anything is if the EAR in the
deploy.last directory has no beans.
--
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
5:20 a.m.
[
https://issues.jboss.org/browse/JBAS-9487?page=com.atlassian.jira.plugin....
]
Ales Justin reassigned JBAS-9487:
---------------------------------
Assignee: Carlo de Wolf (was: Ales Justin)
JBoss 5.1.0.GA deploy.last fails if included EAR contains beans
---------------------------------------------------------------
Key: JBAS-9487
URL: https://issues.jboss.org/browse/JBAS-9487
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.1.0.GA
Environment: Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Java 6 Sun 1.6.0.26
Reporter: Shadow Creeper
Assignee: Carlo de Wolf
Labels: deploy, deploy.last, jboss5
Attachments: deploy.last.tgz, test-server-sources.tgz
When deploying an EAR in server/.../deploy/deploy.last/ (so that it will not be started
until everything else has started) there is complete failure of all included beans.
Apparently, if there are beans in the EAR, it is in some cases listed in JNDI as
"...ear=deploy.last,jar=..." rather that
"...ear=test-ear.ear,jar=..."
According to the server log, the bean is bound to "deploy/TestSoloBean/local"
rather than "test-ear/TestSoloBean/local"
The only way to get the deploy.last directory to deploy anything is if the EAR in the
deploy.last directory has no beans.
--
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
4:11 a.m.
[
https://issues.jboss.org/browse/JBAS-9487?page=com.atlassian.jira.plugin....
]
Carlo de Wolf updated JBAS-9487:
--------------------------------
Labels: community deploy deploy.last jboss5 (was: deploy deploy.last
jboss5)
Assignee: (was: Carlo de Wolf)
Forum Reference: https://community.jboss.org/thread/198638 (was:
https://community.jboss.org/thread/198638)
JBoss 5.1.0.GA deploy.last fails if included EAR contains beans
---------------------------------------------------------------
Key: JBAS-9487
URL: https://issues.jboss.org/browse/JBAS-9487
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.1.0.GA
Environment: Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
Also has been reproduced on Windows XP and Windows 7
Java 6 Sun 1.6.0.26
Reporter: Shadow Creeper
Labels: community, deploy, deploy.last, jboss5
Attachments: deploy.last.tgz, test-server-sources.tgz
When deploying an EAR in server/.../deploy/deploy.last/ (so that it will not be started
until everything else has started) there is complete failure of all included beans.
Apparently, if there are beans in the EAR, it is in some cases listed in JNDI as
"...ear=deploy.last,jar=..." rather that
"...ear=test-ear.ear,jar=..."
According to the server log, the bean is bound to "deploy/TestSoloBean/local"
rather than "test-ear/TestSoloBean/local"
The only way to get the deploy.last directory to deploy anything is if the EAR in the
deploy.last directory has no beans.
--
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
5204
days inactive
5208
days old
4 comments
3 participants
participants (3)
-
Ales Justin (JIRA) -
Carlo de Wolf (JIRA)
-
Shadow Creeper (JIRA)