- changed status to duplicate
NullPointerException when generating Offline Symbol Table
In a newly created DX project I consistently get a NullPointerException when trying to generate the OST. I do not get the same error from existing DX projects.
I’ve attached the project
And here’s a section the idea.log
2023-09-21 15:31:58,015 [14788076] INFO - #com.illuminatedcloud.intellij.settings.project.OfflineSymbolTableGenerator - Starting activity Loading installed package namespaces with 1 steps.
2023-09-21 15:31:58,363 [14788424] INFO - #com.illuminatedcloud.client.ForceComApiClient - Logging into Salesforce DX as test-eyi5srsquub3@example.com.
2023-09-21 15:31:58,363 [14788424] INFO - #com.illuminatedcloud.client.ForceComApiClient - Retrieving org details from Salesforce CLI.
2023-09-21 15:31:58,363 [14788424] INFO - #com.illuminatedcloud.client.ForceComApiClient - Retrieving org details from Salesforce CLI.
2023-09-21 15:31:58,364 [14788425] INFO - #com.illuminatedcloud.client.ForceComApiClient - Retrieving org details for d2 from Salesforce CLI.
2023-09-21 15:32:03,469 [14793530] INFO - org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean - Creating Service {urn:partner.soap.sforce.com}PartnerService from class com.sforce.soap.partner.PartnerApi
2023-09-21 15:32:03,489 [14793550] INFO - org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean - Creating Service {http://soap.sforce.com/2006/04/metadata}MetadataService from class com.sforce.soap.metadata.MetadataApi
2023-09-21 15:32:03,508 [14793569] INFO - org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean - Creating Service {http://soap.sforce.com/2006/08/apex}ApexService from class com.sforce.soap.apex.ApexApi
2023-09-21 15:32:03,513 [14793574] INFO - org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean - Creating Service {urn:tooling.soap.sforce.com}ToolingService from class com.sforce.soap.tooling.ToolingApi
2023-09-21 15:32:03,741 [14793802] INFO - #com.illuminatedcloud.intellij.settings.project.OfflineSymbolTableGenerator - Completed activity Loading installed package namespaces in 5723 ms.
2023-09-21 15:32:03,742 [14793803] WARN - #com.illuminatedcloud.util.IlluminatedCloudExceptionUtil - org.apache.cxf.binding.soap.SoapFault: java.lang.NullPointerException Error Id: 1456068139-46231 (-48145086)
javax.xml.ws.WebServiceException: org.apache.cxf.binding.soap.SoapFault: java.lang.NullPointerException Error Id: 1456068139-46231 (-48145086)
at org.apache.cxf.jaxws.JaxWsClientProxy.mapException(JaxWsClientProxy.java:193)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145)
at jdk.proxy5/jdk.proxy5.$Proxy214.listMetadata(Unknown Source)
at com.illuminatedcloud.symtab.OfflineSymbolTable.lambda$loadInstalledPackageNamespaces$0(SourceFile:468)
at com.illuminatedcloud.client.ForceComApiClient.runWithClient(SourceFile:395)
at com.illuminatedcloud.client.ForceComApiClient.runWithClient(SourceFile:412)
at com.illuminatedcloud.symtab.OfflineSymbolTable.lambda$loadInstalledPackageNamespaces$1(SourceFile:467)
at com.illuminatedcloud.symtab.OfflineSymbolTable.runActivity(SourceFile:748)
at com.illuminatedcloud.symtab.OfflineSymbolTable.runActivity(SourceFile:780)
at com.illuminatedcloud.symtab.OfflineSymbolTable.loadInstalledPackageNamespaces(SourceFile:463)
at com.illuminatedcloud.symtab.OfflineSymbolTable.generateOfflineSymbolTable(SourceFile:888)
at com.illuminatedcloud.intellij.settings.project.OfflineSymbolTableGenerator$2.run(SourceFile:224)
at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:428)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:115)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsynchronously$6(CoreProgressManager.java:478)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:251)
at com.intellij.openapi.progress.ProgressManager.lambda$runProcess$0(ProgressManager.java:71)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:186)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$13(CoreProgressManager.java:604)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:679)
at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:635)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:603)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:61)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:173)
at com.intellij.openapi.progress.ProgressManager.runProcess(ProgressManager.java:71)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$5(ProgressRunner.java:251)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$launchTask$18(ProgressRunner.java:465)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.cxf.binding.soap.SoapFault: java.lang.NullPointerException Error Id: 1456068139-46231 (-48145086)
at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:87)
at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:53)
at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:42)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:112)
at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:70)
at org.apache.cxf.binding.soap.interceptor.CheckFaultInterceptor.handleMessage(CheckFaultInterceptor.java:35)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:831)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1697)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1571)
at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1371)
at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:671)
at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:441)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:356)
at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:314)
at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
... 32 more
Comments (4)
-
repo owner -
repo owner It’s a bug in the CLI right now that I’ve reported to them. Take a look at #2428 for the explanation and solution.
-
reporter Thanks, Scott! I did search first but didn’t find that existing issue because I was only looking for open ones. I’m glad there’s a workaround, I’ll share that with my team.
-
repo owner Sure, no problem. I logged that bug with them quite a bit back, and it seems that there’s no interest in fixing it, especially with Winter ‘24 almost here at this point. Frustrating, but I’ll likely need to add a workaround in IC2 to catch/detect that situation and suggest to the user that the project API version be lowered to the latest released API version. Just another hack to go with the others…sigh…
- Log in to comment
Duplicate of
#2428.