Sophos Anti-Virus for Linux: Support for minor releases of RHEL, CentOS and Oracle Linux

This article describes the Sophos Anti-Virus for Linux support for minor releases of different Linux distributions.

Sophos uses commercially reasonable efforts, as described below, to support Sophos Antivirus for Linux on all minor point releases of Red Hat Enterprise Linux (RHEL) while the corresponding major version is supported. This includes the CentOS and Oracle Linux derivatives of RHEL.

Sophos will test and support Sophos Antivirus on the current active minor release of RHEL, CentOS, and Oracle Linux. When a new minor version is released by the operating system vendor, the previous minor version typically stops receiving important security updates. Sophos, therefore, recommends customers upgrade to the current active minor release as early as practicable.

To assist customers who are unable to upgrade their systems in line with RHEL minor releases, Sophos uses commercially reasonable efforts to support Sophos Antivirus on non-current minor releases of RHEL, CentOS, and Oracle Linux, on the following basis:

  • Support for configuration and usage questions for Sophos Antivirus for Linux will be provided by Sophos Technical Support
  • Technical product issues will be investigated using Sophos’ existing maintenance process, on the basis that the issue can be replicated on the current active minor release
  • If a reported product issue cannot be replicated on the current active minor release, or in the event that a software update would be required to provide a resolution for a non-current minor release, Sophos advises that such issues may fall outside the scope of commercially reasonable efforts support
  • The corresponding major version must be supported by Sophos, excluding extended or limited support offerings

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

Advisory: Sophos UTM – RED Site-to-Site tunnel issues after upgrading to v9.7

Sophos is investigating reports from some customers experiencing RED site-to-site tunnel issues after upgrading from v9.605 to v9.7.

Applies to the following Sophos products and versions

Sophos UTM

A fixed Up2Date package (u2d-sys-9.605004-700005) has been released for the v9.605 to v9.700 update path. For installations already running v9.670 or v9.700, the following are the fixed Up2Date packges:

For installations running 9.7 EAP1 (9.670-4):

  • u2d-sys-9.670004-700004
  • u2d-sys-9.700004-700005

For installations running 9.7 GA (9.700-4):

  • u2d-sys-9.700004-700005

Affected customers can workaround this issue by re-downloading the provisioning file from the Server, and re-creating the client-side RED-interface:

  • On the Server
    1. In the Admin UI, go to: Red Management > [Server] Client Management.
    2. Download all necessary provisioning files.
  • On the Client
    1. In the Admin UI, go to: Red Management > [Client] Tunnel Management.
    2. Open the affected RED-Device and take note of the Tunnel Name and UTM Host.
    3. Delete the Client Tunnel.
    4. Create a new tunnel using the above noted Tunnel Name, UTM-Host, and downloaded provisioning file.
    5. In the Admin UI go to: Interface & Routing > Interfaces.
    6. Open the affected Tunnel Interface and select the newly recreated RED-Interface.

This article will be updated when more information becomes available.

Sign up to the Sophos Support SMS Notification Service to get the latest product release information and critical issues.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

  • No Related Posts

Hotfix XS71ECU2011 – For XenServer 7.1 Cumulative Update 2

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 2.

Note: This hotfix is available only to customers on the Customer Success Services program.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks None
Content live patchable** No
Baselines for Live Patch N/A
Revision History

Published on Jun 27, 2019

** Available to Enterprise Customers.

Improvements provided by this hotfix

This hotfix includes the following improvements:

  • Add a template and support for SUSE Linux Enterprise Server 12 SP4 (64-bit)
  • Add a template and support for SUSE Linux Enterprise Desktop 12 SP4 (64-bit)

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS71ECU2011-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS71ECU2011.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS71ECU2011.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    1346bb65-ac31-4f66-8d70-2cf3eb9807b2

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=1346bb65-ac31-4f66-8d70-2cf3eb9807b2

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host=<host> uuid=1346bb65-ac31-4f66-8d70-2cf3eb9807b2

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS71ECU2011

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

    xe update-pool-clean uuid=1346bb65-ac31-4f66-8d70-2cf3eb9807b2

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU2011.iso
Hotfix File sha256 337f82261644497a18ae3262c40d79b5b616bfe287a293d7f34e48e15df33446
Hotfix Source Filename XS71ECU2011-sources.iso
Hotfix Source File sha256 398473433c7298d3b1a7b30776b03e6f2085c0b372ee5b3c374cb07919231376
Hotfix Zip Filename XS71ECU2011.zip
Hotfix Zip File sha256 947dd9fd0cf1a979b74d77887bfe0ee24a22a3709a84ca4d9227236445863d81
Size of the Zip file 0.48 MB

Files Updated

guest-templates-json-1.1.5-1.noarch.rpm
guest-templates-json-data-linux-1.1.5-1.noarch.rpm
guest-templates-json-data-other-1.1.5-1.noarch.rpm
guest-templates-json-data-windows-1.1.5-1.noarch.rpm
guest-templates-json-data-xenapp-1.1.5-1.noarch.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

Hotfix XS76E004 – For XenServer 7.6

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.6.

All customers who are affected by the issues described in CTX251995 – Citrix XenServer Multiple Security Updates should install this hotfix.

Note: This hotfix is available only to customers on the Customer Success Services program.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks Restart Host
Content live patchable** No
Baselines for Live Patch N/A
Revision History

Published on May 16, 2019

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS76E004-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS76E004.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS76E004.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    d0f21312-13f9-4d28-87ad-202b20c79bce

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=d0f21312-13f9-4d28-87ad-202b20c79bce

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host=<host> uuid=d0f21312-13f9-4d28-87ad-202b20c79bce

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS76E004

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.
  7. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

    xe update-pool-clean uuid=d0f21312-13f9-4d28-87ad-202b20c79bce

Files

Hotfix File

Component Details
Hotfix Filename XS76E004.iso
Hotfix File sha256 0473b882d69cd383ba204fabfae92fcfe19519dc62a4321b7f3174eab24bde46
Hotfix Source Filename XS76E004-sources.iso
Hotfix Source File sha256 17c6101895e536d3fe7f49b59c5183b360224af9ac0755752d001fa507c4c9ac
Hotfix Zip Filename XS76E004.zip
Hotfix Zip File sha256 cb0c8a94e7783fddeea73fb20465fe9415e79111500dd0e0a26a2dc75de017a6
Size of the Zip file 6.71 MB

Files Updated

microcode_ctl-2.1-26.xs5.x86_64.rpm
xen-dom0-libs-4.7.6-6.5.x86_64.rpm
xen-dom0-tools-4.7.6-6.5.x86_64.rpm
xen-hypervisor-4.7.6-6.5.x86_64.rpm
xen-libs-4.7.6-6.5.x86_64.rpm
xen-tools-4.7.6-6.5.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

Is Symetec Enterprise Security Manager supported in RHEL 7x ppc64le platform?

I need a solution

I wanted to know if Enterprise Security Manager is supported in REdhat 7x  systems that run on ppc64le  systems.

As per the following link http://eval.symantec.com/mktginfo/enterprise/fact_sheets/ent-factsheet_enterprise_security_manager_6.5_06-2005.en-us.pdf   

RHEL 7.x on ppc64le is not in the supported platform list.  Is this correct? Is there a plan to support this plform in future ?

Thanks

Rajesh

0

Related:

Hotfix XS76E003 – For XenServer 7.6

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.6.

All customers who are affected by the issues described in CTX246572 – Citrix XenServer Multiple Security Updates should install this hotfix.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks Restart Host
Content live patchable** No
Baselines for Live Patch N/A
Revision History

Published on Mar 06, 2019

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This security hotfix addresses the vulnerabilities as described in the Security Bulletin above.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS76E003-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS76E003.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS76E003.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    7655a31f-93cc-44d0-88ea-f0e56711ca65

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=7655a31f-93cc-44d0-88ea-f0e56711ca65

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host=<host> uuid=7655a31f-93cc-44d0-88ea-f0e56711ca65

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS76E003

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. If the hotfix is applied successfully, restart each host in the pool, starting with the master.
  7. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

    xe update-pool-clean uuid=7655a31f-93cc-44d0-88ea-f0e56711ca65

Files

Hotfix File

Component Details
Hotfix Filename XS76E003.iso
Hotfix File sha256 aa712d31437e998a8134266e246a07b110a230ca2f800195453fa3d5da667d2e
Hotfix Source Filename XS76E003-sources.iso
Hotfix Source File sha256 52ce2f40aabf417bb26438bcd8aeff85e5ed725b99b806bfc5fdafaebc6fee94
Hotfix Zip Filename XS76E003.zip
Hotfix Zip File sha256 e8f8824eb123c68ae76193d03c1d15279f7e46a33a77caaebe691fe294a83185
Size of the Zip file 4.38 MB

Files Updated

xen-dom0-libs-4.7.6-6.4.x86_64.rpm
xen-dom0-tools-4.7.6-6.4.x86_64.rpm
xen-hypervisor-4.7.6-6.4.x86_64.rpm
xen-libs-4.7.6-6.4.x86_64.rpm
xen-tools-4.7.6-6.4.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related:

Re: Webtop installation on JBOSS : Windows

While installing Webtop on JBOSS I am encountered with below error . Kindly suggest how to troubleshoot . Also attached complete log file.

18:53:22,798 INFO [FileSystemContext] VFS forced fallback to vfsjar is enabled.

18:53:23,188 INFO [AbstractVirtualFileHandler] VFS force copy (NestedJarHandler) is enabled.

18:53:25,294 INFO [ServerInfo] Java version: 1.6.0_30,Sun Microsystems Inc.

18:53:25,294 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_30-b12)

18:53:25,294 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 20.5-b03,Sun Microsystems Inc.

18:53:25,294 INFO [ServerInfo] OS-System: Windows 7 6.1,x86

18:53:25,294 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms512M -Xmx512M -XX:MaxPermSize=512M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Dsun.lang.ClassLoader.allowArraySyntax=true -Djboss.vfs.forceVfsJar=true -Djboss.vfs.forceCaseSensitive=true -Djava.endorsed.dirs=C:Installsjboss-5.1.0.GA-jdk6jboss-5.1.0.GAlibendorsed

18:53:25,356 INFO [JMXKernel] Legacy JMX core initialized

18:53:28,289 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@bd5df[domain=default, server=default, name=default]

18:53:31,659 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/

18:53:41,238 INFO [NativeServerConfig] JBoss Web Services – Stack Native Core

18:53:41,238 INFO [NativeServerConfig] 3.1.2.GA

18:53:41,800 INFO [AttributeCallbackItem] Owner callback not implemented.

18:53:42,892 INFO [LogNotificationListener] Adding notification listener for logging mbean “jboss.system:service=Logging,type=Log4jService” to server org.jboss.mx.server.MBeanServerImpl@41a12f[ defaultDomain=’jboss’ ]

18:55:05,467 INFO [CopyMechanism] VFS temp dir: C:Installsjboss-5.1.0.GA-jdk6jboss-5.1.0.GAserverdefaulttmp

18:55:41,161 ERROR [ProfileDeployAction] Failed to add deployment: krbutil.jar

org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=webtop/WEB-INF/lib/commons-codec-1.3.jar} from krbutil.jar

at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)

at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)

at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)

at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)

at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)

at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

at org.jboss.Main.boot(Main.java:221)

at org.jboss.Main$1.run(Main.java:556)

at java.lang.Thread.run(Thread.java:662)

Caused by: java.io.IOException: Child not found webtop/WEB-INF/lib/commons-codec-1.3.jar for JarHandler@26746731[path=webtop/WEB-INF/lib/krbutil.jar context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/krbutil.jar], available children: [JarEntryHandler@3583147[path=webtop/WEB-INF/lib/krbutil.jar/META-INF context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/krbutil.jar!/META-INF/], JarEntryHandler@25309840[path=webtop/WEB-INF/lib/krbutil.jar/com context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/krbutil.jar!/com/]]

at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)

… 23 more

18:55:46,138 ERROR [ProfileDeployAction] Failed to add deployment: bpm_infra.jar

org.jboss.deployers.spi.DeploymentException: Unable to find class path entry ClassPathEntryImpl{path=webtop/WEB-INF/lib/castor-1.1-xml.jar} from bpm_infra.jar

at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:188)

at org.jboss.deployers.structure.spi.helpers.AbstractStructureBuilder.populateContext(AbstractStructureBuilder.java:82)

at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:89)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1004)

at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390)

at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300)

at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.addDeployment(MainDeployerAdapter.java:86)

at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:61)

at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

at org.jboss.Main.boot(Main.java:221)

at org.jboss.Main$1.run(Main.java:556)

at java.lang.Thread.run(Thread.java:662)

Caused by: java.io.IOException: Child not found webtop/WEB-INF/lib/castor-1.1-xml.jar for JarHandler@12116679[path=webtop/WEB-INF/lib/bpm_infra.jar context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar], available children: [JarEntryHandler@3185168[path=webtop/WEB-INF/lib/bpm_infra.jar/META-INF context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar!/META-INF/], JarEntryHandler@13808752[path=webtop/WEB-INF/lib/bpm_infra.jar/com context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar!/com/], JarEntryHandler@21247461[path=webtop/WEB-INF/lib/bpm_infra.jar/org context=file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/ real=jar:file:/C:/Installs/jboss-5.1.0.GA-jdk6/jboss-5.1.0.GA/server/default/deploy/webtop/WEB-INF/lib/bpm_infra.jar!/org/]]

at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:461)

at org.jboss.deployers.vfs.plugins.structure.VFSStructureBuilder.applyContextInfo(VFSStructureBuilder.java:184)

… 23 more

18:55:55,452 ERROR [ProfileDeployAction] Failed to add deployment: jaxb-impl.jar

Related: