IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
Expand all | Collapse all

Java service compilation error : name too long

  • 1.  Java service compilation error : name too long

    Posted Thu March 10, 2022 11:36 AM

    What product/components do you use and which version/fix level?

    Software AG / Api Gateway / webMethods

    Are you using a free trial or a product with a customer license?

    Customer license

    What are trying to achieve? Please describe in detail.

    I’m trying to compile a Java service

    Do you get any error messages? Please provide a full error message screenshot and log file.

    n=10.11.0.0000-0724,name=Monitor,subsystemId=WmMonitor, service.id=425, service.bundleid=60, service.scope=singleton] - ServiceEvent REGISTERED
    jvm 1    | 2022-03-11 09:38:41,841 INFO  [org.a.s.s.m.AbstractValidatingSessionManager                ] - Enabling session validation scheduler...
    jvm 1    | 2022-03-11 09:38:53.218 : Integration Server detected loss of its Log4j configuration. Integration Server is restoring its Log4j configuration.
    jvm 1    | java.io.IOException: Cannot run program "D:\projets\api-gateway\sag\server\jvm\jvm\bin\javac": CreateProcess error=206, Nom de fichier ou extension trop long
    jvm 1    |      at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
    jvm 1    |      at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
    jvm 1    |      at java.base/java.lang.Runtime.exec(Runtime.java:592)
    jvm 1    |      at java.base/java.lang.Runtime.exec(Runtime.java:416)
    jvm 1    |      at java.base/java.lang.Runtime.exec(Runtime.java:354)
    jvm 1    |      at com.wm.app.b2b.server.NodeUtil.runCommand(NodeUtil.java:1182)
    jvm 1    |      at com.wm.app.b2b.server.NodeUtil.doCompile(NodeUtil.java:1142)
    jvm 1    |      at com.wm.app.b2b.server.NodeUtil.compile(NodeUtil.java:533)
    jvm 1    |      at wm.server.nsimpl._compile(nsimpl.java:7915)
    jvm 1    |      at wm.server.nsimpl.buildClass(nsimpl.java:1936)
    jvm 1    |      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    jvm 1    |      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    jvm 1    |      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    jvm 1    |      at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    jvm 1    |      at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:404)
    jvm 1    |      at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:759)
    jvm 1    |      at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
    jvm 1    |      at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:53)
    jvm 1    |      at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
    jvm 1    |      at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    jvm 1    |      at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
    jvm 1    |      at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:336)
    jvm 1    |      at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:33)
    jvm 1    |      at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:399)
    jvm 1    |      at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:629)
    jvm 1    |      at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:434)
    jvm 1    |      at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:392)
    jvm 1    |      at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:260)
    jvm 1    |      at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
    jvm 1    |      at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:156)
    jvm 1    |      at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:218)
    jvm 1    |      at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:390)
    jvm 1    |      at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
    jvm 1    |      at java.base/java.lang.Thread.run(Thread.java:829)
    jvm 1    | Caused by: java.io.IOException: CreateProcess error=206, Nom de fichier ou extension trop long
    jvm 1    |      at java.base/java.lang.ProcessImpl.create(Native Method)
    jvm 1    |      at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:487)
    jvm 1    |      at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:154)
    jvm 1    |      at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)
    jvm 1    |      ... 33 more
    
    

    Have you installed latest fixes for the products

    yes


    #API-Gateway
    #API-Management
    #webMethods


  • 2.  RE: Java service compilation error : name too long

    Posted Sat March 12, 2022 08:43 AM

    Hi,

    Could you check your classpath, if that has many libraries referred with full path, that might end of having a very long path and cause such errors. You could just try reducing the jars if possible from the classpath and give a try.

    Thanks


    #API-Management
    #webMethods
    #API-Gateway