]
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: