Can no longer use SDK to connect to Agile after server upgrade
All my issues started after a server upgrade.
I’ve changed the AgileApi.jar which just changes the errors. Played with different java versions… What java version is required? What’s the best way to check the agileapi.jar version? How do i clear the sdk.cache?
first message:
Error code : 60079
Error message : Invalid server configuration. Check if SDK is installed properly
change the jar file, then:
java.lang.NoSuchFieldError: TABLE_PUBLISHWORKBENCH
at com.agile.api.pc.admin.AgileClass$InitTableDescriptorsAction.include(AgileClass.java:839)
at com.agile.api.pc.admin.AgileClass$InitTableDescriptorsAction.doSdkAction(AgileClass.java:810)
at com.agile.api.common.SDKAction.run(SDKAction.java:23)
at com.agile.api.common.Security.doAs(Security.java:59)
at com.agile.api.common.Security.doAs(Security.java:109)
at com.agile.api.pc.admin.AgileClass.getTableDescriptors(AgileClass.java:485)
at com.agile.api.pc.admin.AgileClass.getTableDescriptor(AgileClass.java:452)
at com.agile.api.pc.Table.initTableDescriptor(Table.java:1171)
at com.agile.api.pc.Table.getTableDescriptor(Table.java:736)
at com.agile.api.pc.Table.getTableIndex(Table.java:1075)
at com.agile.api.pc.TablePC$LoadServerTableAction.doSdkAction(TablePC.java:290)
at com.agile.api.common.SDKAction.run(SDKAction.java:23)
at com.agile.api.common.Security.doAs(Security.java:59)
at com.agile.api.common.Security.doAs(Security.java:109)
at com.agile.api.pc.TablePC.loadServerTable(TablePC.java:96)
at com.agile.api.pc.Table.loadServerTableEx(Table.java:1380)
at com.agile.api.pc.TableIterator.loadData(TableIterator.java:240)
at com.agile.api.pc.TableIterator$MoveWindowAction.doSdkAction(TableIterator.java:216)
at com.agile.api.common.SDKAction.run(SDKAction.java:23)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:163)
at weblogic.security.Security.runAs(Security.java:62)
at com.agile.api.common.WebLogicAuthenticator.doAs(WebLogicAuthenticator.java:111)
at com.agile.api.common.Security.doAs(Security.java:54)
at com.agile.api.common.Security.doAs(Security.java:109)
at com.agile.api.pc.TableIterator.moveWindow(TableIterator.java:184)
at com.agile.api.pc.TableIterator.checkIterator(TableIterator.java:198)
at com.agile.api.pc.TableIterator.hasNext(TableIterator.java:56)
at com.agile.api.pc.DataObject.getName(DataObject.java:161)
at com.agile.api.pc.DataObject.toString(DataObject.java:829)
at lasp.caltest.agile.AgileConnectionTest.test_getPart(AgileConnectionTest.java:95)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
Typically, this error goes away after pulling the AgileAPI.jar file from the application server’s /integration/sdk/lib directory. But it sounds like you’ve already done that. The cache is going to be dependent upon how you’re running the SDK app. For example, if you’re running an app in Tomcat, the location is <Tomcat home>/temp. Directly on a Windows box, it’s C:\windows\temp. Linux is /tmp. Look for the agile.cache directory. Caveat, I’m typing from memory so buyer beware.
You stated “server upgrade”. Was this the application server (as in, an O/S change), or an upgrade to Agile itself?
What version of Agile are you running, before and after? If you were running something previous to 9.3.4.0 and are now running 9.3.4.0 or later, you could be having issues with the web services stack used by Agile, which changed from AXIS to JAX-WS. As such, it *will* require changes to be made to your PXs, but only if they use web services – normal PXs that simply call the SDK API should be fine.