jstrauss64
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: rest service xml payload disappears from editor
Tanya, I am using the 1.4.1 version of ReadyAPI.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes0Commentsrest service xml payload disappears from editor
I have a test case where in my tests I compare the response from an old service to the response from a new service. The endpoints to the two services are different. I'm supplying the request payload for the old service as XML and the payload for the new service is JSON. When I run the tests that I have set up, they are both successful. Each one calls the appropriate service and returns a valid response. The problem I'm having is that when I close the editor for the old service, the XML is not retained. The result is, every time I want to run the test I have to paste the XML into the request tab of the editor. Also, if I click form tab the XML values are deleted and I have to paste it again. If I click the outline or raw tab, the XML is retained. That is not happening on the tests for the new service. The JSON that I paste into the request tab is there when I reopen the editor. When I click the tabs (form, outline, raw) the JSON is retained. My workaround is that I open the tests for the old service and paste the XML into the editor for each test (there are four), then run the four tests. Then I run the tests for the new service. As long as I keep the tests for the old service open in the editor, the data is "cached", so the comparisons can be done. I have clicked around to see if there is a setting I can change to get the XML to stay in place, but I have not found anything. Granted, I am new to using ReadyAPI, so I'm not sure if I'm looking in the right place. I have searched to see if this is a known issue, and I cannot find this scenario described by anyone else. Can someone point me to a solution?1.3KViews0likes2CommentsRe: call to jms fails after upgrade
Anton, I selected the "install in the current directory" (ReadyAPI-1.4.1) instead of "install in a new directory" (ReadyAPI-1.5.0), so the path to hermes is correct. I'm wondering if I would have had the problem if I had chosen a the new path instead. FYI, I uninstalled the upgrade and went back to 1.4.1 and I'm not having the problem anymore. If/when I upgrade to 1.5, I will choose the install in a new directory option.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.2KViews0likes0CommentsRe: call to jms fails after upgrade
Thanks, Rao. I haven't had any luck with resolving the issue I'm having. I think I will uninstall the upgrade and start from the beginning. I did learn a lesson. Always back up before upgrading!10 years agoPlace ReadyAPI QuestionsReadyAPI Questions4KViews0likes2Commentscall to jms fails after upgrade
I upgraded to 1.5 yesterday and now some tests are not running. Specifically, any tests that include a call to JMS is failing. In the ready-api-errors.log file I get this: 2015-11-12 11:32:06,261 ERROR [errorlog] java.lang.ExceptionInInitializerError java.lang.ExceptionInInitializerError at weblogic.security.service.SubjectManagerImpl.initializeKernelID(SubjectManagerImpl.java:293) at weblogic.security.service.SubjectManagerImpl.<clinit>(SubjectManagerImpl.java:29) at weblogic.security.service.SecurityManager.<clinit>(SecurityManager.java:24) at weblogic.security.service.GetKernelIdentityAction.run(GetKernelIdentityAction.java:25) at java.security.AccessController.doPrivileged(Native Method) at weblogic.jndi.WLSJNDIEnvironmentImpl.<clinit>(WLSJNDIEnvironmentImpl.java:57) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at weblogic.jndi.internal.JNDIEnvironment.getJNDIEnvironment(JNDIEnvironment.java:33) at weblogic.jndi.Environment.<clinit>(Environment.java:89) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at hermes.JNDIContextFactory.createContext(JNDIContextFactory.java:261) at hermes.JNDIConnectionFactory.createConnection(JNDIConnectionFactory.java:80) at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.createConnection(JMSConnectionHolder.java:87) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSendTransport.execute(HermesJmsRequestSendTransport.java:37) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:98) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.SecurityException: sealing violation: can't seal package javax.security.auth: already loaded at java.net.URLClassLoader.getAndVerifyPackage(Unknown Source) at java.net.URLClassLoader.definePackageInternal(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils$ReverseOrderClassLoader.innerLoadClass(HermesUtils.java:332) at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils$ReverseOrderClassLoader.loadClass(HermesUtils.java:319) at java.lang.ClassLoader.loadClass(Unknown Source) at hermes.impl.LoaderSupport$DebugClassLoader.loadClass(LoaderSupport.java:99) at java.lang.ClassLoader.loadClass(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.<init>(AuthenticatedSubject.java:101) at weblogic.security.acl.internal.AuthenticatedSubject.<clinit>(AuthenticatedSubject.java:39) ... 26 more And in the ready-api.log I get this: 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-imq.jar for hermes.ext.imq.ImqAdminFactory 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-aq.jar for hermes.ext.oracle.aq.OracleAQAdminFactory 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-ems.jar for hermes.ext.ems.TibcoEMSAdminFactory 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-webspheremq.jar for hermes.ext.mq.MQSeriesAdminFactory 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-jbossmq.jar for hermes.ext.jbossmq.JBossMQAdminFactory 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-arjuna.jar for hermes.ext.arjuna.ArjunaMSAdminFactory 2015-11-12 11:32:06,013 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-weblogic.jar for hermes.ext.weblogic.WebLogicJMSAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-joram.jar for hermes.ext.joram.JoramAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-wme.jar for hermes.ext.wme.WMEAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-openjms.jar for hermes.ext.openjms.OpenJMSAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-fiorano.jar for hermes.ext.fiorano.FioranoAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-sonicmq.jar for hermes.ext.sonicmq.SonicMQAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-sapjms.jar for hermes.ext.sap.SAPJMSAdminFactory 2015-11-12 11:32:06,014 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-activemq.jar for hermes.ext.activemq.ActiveMQAdminFactory 2015-11-12 11:32:06,015 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-seebeyond.jar for hermes.ext.seebeyond.ican.SeeBeyondICANAdminFactory 2015-11-12 11:32:06,015 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-seebeyond.jar for hermes.ext.seebeyond.jcaps.SeeBeyondJCAPSAdminFactory 2015-11-12 11:32:06,015 ERROR [ConfigDAOImpl] cannot find ../lib/hermes-sapjms.jar for hermes.ext.sap.SAPJMSAdminFactory 2015-11-12 11:32:06,261 ERROR [errorlog] java.lang.ExceptionInInitializerError java.lang.ExceptionInInitializerError at weblogic.security.service.SubjectManagerImpl.initializeKernelID(SubjectManagerImpl.java:293) at weblogic.security.service.SubjectManagerImpl.<clinit>(SubjectManagerImpl.java:29) at weblogic.security.service.SecurityManager.<clinit>(SecurityManager.java:24) at weblogic.security.service.GetKernelIdentityAction.run(GetKernelIdentityAction.java:25) at java.security.AccessController.doPrivileged(Native Method) at weblogic.jndi.WLSJNDIEnvironmentImpl.<clinit>(WLSJNDIEnvironmentImpl.java:57) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at weblogic.jndi.internal.JNDIEnvironment.getJNDIEnvironment(JNDIEnvironment.java:33) at weblogic.jndi.Environment.<clinit>(Environment.java:89) at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117) at javax.naming.spi.NamingManager.getInitialContext(Unknown Source) at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source) at javax.naming.InitialContext.init(Unknown Source) at javax.naming.InitialContext.<init>(Unknown Source) at hermes.JNDIContextFactory.createContext(JNDIContextFactory.java:261) at hermes.JNDIConnectionFactory.createConnection(JNDIConnectionFactory.java:80) at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.createConnection(JMSConnectionHolder.java:87) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSendTransport.execute(HermesJmsRequestSendTransport.java:37) at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:98) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.SecurityException: sealing violation: can't seal package javax.security.auth: already loaded at java.net.URLClassLoader.getAndVerifyPackage(Unknown Source) at java.net.URLClassLoader.definePackageInternal(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils$ReverseOrderClassLoader.innerLoadClass(HermesUtils.java:332) at com.eviware.soapui.impl.wsdl.submit.transports.jms.util.HermesUtils$ReverseOrderClassLoader.loadClass(HermesUtils.java:319) at java.lang.ClassLoader.loadClass(Unknown Source) at hermes.impl.LoaderSupport$DebugClassLoader.loadClass(LoaderSupport.java:99) at java.lang.ClassLoader.loadClass(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.<init>(AuthenticatedSubject.java:101) at weblogic.security.acl.internal.AuthenticatedSubject.<clinit>(AuthenticatedSubject.java:39) ... 26 more In the preferences > tools, I have set the path for hermesJMS to C:\Program Files\SmartBear\ReadyAPI-1.4.1\hermesJMS. Any clue why these tests would stop working? I'm leaning towards a config file was overwritten in the upgrade, but I'm not sure where to look for that. I was hoping the upgrade would be smooth. My other option is to roll back and try again, but if it is a config issue, that should be an easy fix, right? Thanks.Solved10 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.9KViews0likes16Comments