Skip to Content
0
Former Member
Apr 07, 2010 at 03:34 PM

How to give jar at runtime as JVM parameter in Config tool

235 Views

Hi

I am executing java spring based webservice on WS navigator CE7.1 . I am getting the follwing error. To avoid this i have to provide the spring-agent.jar at runtime to the javm , I tried to configure the Configtool jvm parameters as specified in the sap help.

Is is possible to give the jar as JVM param via config tool.

<?xml version="1.0" encoding="UTF-8"?>

http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs=" http://www.w3.org/2001/XMLSchema" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance">

<SOAP-ENV:Body>

http://metering.com/greams/flowmanagement/inbound/">

<return status="TECHNICAL_ERROR">

<technicalErrors>

<code>TECHNICAL_ERROR</code>

<description>org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.sap.engine.boot.loader.ResourceMultiParentClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar</description>

<additionalInformation>org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.sap.engine.boot.loader.ResourceMultiParentClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar</additionalInformation>

<responseMessageCode>TECHNICAL_ERROR</responseMessageCode>

</technicalErrors>

</return>

</ns2:po1ProcessingResponse>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>