[ http://jira.jboss.com/jira/browse/JBAS-1240?page=history ]
Adrian Brock updated JBAS-1240:
-------------------------------
Description:
SourceForge Submitter: rz1911 .
Hi,
I have problems to deploy the attached EAR if the
jboss/server/default/tmp directory is linked to another
directoy using an symbolic link. I use JBoss 4.0.0, JDK
1.4.2_06 and RedHat Linux.
The EAR defins two (empty) session EJBs A and B. EJB A
has an link to EJB B using th <ejb-link> syntax.
I get the following Exception:
2004-12-06 18:38:44,673 INFO
[org.jboss.ejb.EjbModule] Deploying AEJB
2004-12-06 18:38:46,663 INFO
[org.jboss.ejb.EjbModule] Deploying BEJB
2004-12-06 18:38:46,983 WARN [org.jboss.ejb.EjbUtil]
Can't locate deploymentInfo for target:
file:/var/intelliform/tmp/deploy/tmp39034bug.ear-
contents/B.jar
2004-12-06 18:38:46,984 ERROR
[org.jboss.ejb.StatelessSessionContainer] Starting
failed jboss.j2ee:jndiName=AEJB,service=EJB
org.jboss.deployment.DeploymentException: Failed to
resolve ejb-link: B.jar#BEJB
make by ejb-name: ejb/BEJB
at org.jboss.ejb.Container.setupEnvironment
(Container.java:993)
at org.jboss.ejb.Container.startService
(Container.java:724)
at org.jboss.ejb.SessionContainer.startService
(SessionContainer.java:381
)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStar
t(ServiceMBeanS
upport.java:271)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMB
eanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor3.invoke
(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown
Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
...
The EAR deploys fine, if the mtp directory is an real
directory.
I think this is due to the failure of
EjbUtil.resolveRelativeLink.
The use of Strings.toURL calculates the URL for the
DeploymentInfo class different than the MainDeployer
class.
was:
SourceForge Submitter: rz1911 .
Hi,
I have problems to deploy the attached EAR if the
jboss/server/default/tmp directory is linked to another
directoy using an symbolic link. I use JBoss 4.0.0, JDK
1.4.2_06 and RedHat Linux.
The EAR defins two (empty) session EJBs A and B. EJB A
has an link to EJB B using th <ejb-link> syntax.
I get the following Exception:
2004-12-06 18:38:44,673 INFO
[org.jboss.ejb.EjbModule] Deploying AEJB
2004-12-06 18:38:46,663 INFO
[org.jboss.ejb.EjbModule] Deploying BEJB
2004-12-06 18:38:46,983 WARN [org.jboss.ejb.EjbUtil]
Can't locate deploymentInfo for target:
file:/var/intelliform/tmp/deploy/tmp39034bug.ear-
contents/B.jar
2004-12-06 18:38:46,984 ERROR
[org.jboss.ejb.StatelessSessionContainer] Starting
failed jboss.j2ee:jndiName=AEJB,service=EJB
org.jboss.deployment.DeploymentException: Failed to
resolve ejb-link: B.jar#BEJB
make by ejb-name: ejb/BEJB
at org.jboss.ejb.Container.setupEnvironment
(Container.java:993)
at org.jboss.ejb.Container.startService
(Container.java:724)
at org.jboss.ejb.SessionContainer.startService
(SessionContainer.java:381
)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStar
t(ServiceMBeanS
upport.java:271)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
ycle(ServiceMB
eanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor3.invoke
(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown
Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke
(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch
(Invocation.java:80)
...
The EAR deploys fine, if the mtp directory is an real
directory.
I think this is due to the failure of
EjbUtil.resolveRelativeLink.
The use of Strings.toURL calculates the URL for the
DeploymentInfo class different than the MainDeployer
class.
Environment:
Component: EJBs
> ejb-link fails with linked tmp directory
> ----------------------------------------
>
> Key: JBAS-1240
> URL: http://jira.jboss.com/jira/browse/JBAS-1240
> Project: JBoss Application Server
> Type: Bug
> Components: EJBs
> Versions: JBossAS-4.0.0 Final
> Reporter: SourceForge User
> Assignee: Scott M Stark
> Attachments: bug.ear
>
>
> SourceForge Submitter: rz1911 .
> Hi,
> I have problems to deploy the attached EAR if the
> jboss/server/default/tmp directory is linked to another
> directoy using an symbolic link. I use JBoss 4.0.0, JDK
> 1.4.2_06 and RedHat Linux.
> The EAR defins two (empty) session EJBs A and B. EJB A
> has an link to EJB B using th <ejb-link> syntax.
> I get the following Exception:
> 2004-12-06 18:38:44,673 INFO
> [org.jboss.ejb.EjbModule] Deploying AEJB
> 2004-12-06 18:38:46,663 INFO
> [org.jboss.ejb.EjbModule] Deploying BEJB
> 2004-12-06 18:38:46,983 WARN [org.jboss.ejb.EjbUtil]
> Can't locate deploymentInfo for target:
> file:/var/intelliform/tmp/deploy/tmp39034bug.ear-
> contents/B.jar
> 2004-12-06 18:38:46,984 ERROR
> [org.jboss.ejb.StatelessSessionContainer] Starting
> failed jboss.j2ee:jndiName=AEJB,service=EJB
> org.jboss.deployment.DeploymentException: Failed to
> resolve ejb-link: B.jar#BEJB
> make by ejb-name: ejb/BEJB
> at org.jboss.ejb.Container.setupEnvironment
> (Container.java:993)
> at org.jboss.ejb.Container.startService
> (Container.java:724)
> at org.jboss.ejb.SessionContainer.startService
> (SessionContainer.java:381
> )
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStar
> t(ServiceMBeanS
> upport.java:271)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifec
> ycle(ServiceMB
> eanSupport.java:221)
> at sun.reflect.GeneratedMethodAccessor3.invoke
> (Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke
> (Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown
> Source)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke
> (ReflectedDispatch
> er.java:141)
> at org.jboss.mx.server.Invocation.dispatch
> (Invocation.java:80)
> ...
> The EAR deploys fine, if the mtp directory is an real
> directory.
> I think this is due to the failure of
> EjbUtil.resolveRelativeLink.
> The use of Strings.toURL calculates the URL for the
> DeploymentInfo class different than the MainDeployer
> class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
