3 Replies Latest reply on Apr 4, 2014 5:28 AM by maxandersen

    Softlink path for Jboss Soa 5.3.1 deploy folder is failing to modify/deploy existing services.

    shwethasanjay87

      Hi,

       

      I am using Jboss Soa 5.3.1 in our product. i have configured softlink  for deploy  path(my actual deploy path is /opt/hp/sdppe/Jboss_Soa5.3.1/jboss-as/server/production/deploy and created softlink current(softlink name) for sdppe so now deploy path will be  /opt/hp/current/Jboss_Soa5.3.1/jboss-as/server/production/deploy) is configured in run.conf.

       

      Server startetd successfully,  after server starts while doing endpoint modification or modifying existing service getting exception like "

      Caused by: org.jboss.deployment.DeploymentException: Failed to deploy: file:/opt/SGF322Setup/current/jboss-soa-p-5.3.1/jboss-as/server/production/deploy/NewMachine_NT_Test02_0_9_WS.esb

              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:856)

              at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:826)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

              at java.lang.reflect.Method.invoke(Method.java:601)

              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

              at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)

              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

              at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305)

              at $Proxy548.deploy(Unknown Source)

        ".

      This will be only at the first time after server starts , if i again tries to modify that service then  modification is  successful.

       

      If i am using proper path without softlink then modify method will first remove esb and then redeploy it again. so now in above case i am not able to remove esb with softlink path.

       

      My question is Can any one suggest is there any configuration to allow softlink in deploy path.