Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Issues with WebService component

Avatar

Level 3

Hello,

recently, we have been running  into a strange issue using the webservice component. The server is based on a JBoss instance, running on a Soalris system (LCES).

Each call to a web service gives numerous error messages like:

2010-07-13  08:56:34,690 ERROR [STDERR] Failed to create icon:  java.lang.NoClassDefFoundError

I'd like to know what  circumstances could trigger a message like that, and if there are settings (JRE?) that could affect this, especially since this is a completely  non-interactive component (so creating an icon seems irrelevant).

I  will put some extended app log messages below:

2010-07-13  08:56:34,631 ERROR [STDERR] Exception in thread "SwingWorker"

2010-07-13  08:56:34,631 ERROR [STDERR] java.lang.NoClassDefFoundError

2010-07-13  08:56:34,632 ERROR [STDERR]  at java.lang.Class.forName0(Native Method)

2010-07-13  08:56:34,632 ERROR [STDERR]  at java.lang.Class.forName(Class.java:164)

2010-07-13  08:56:34,632 ERROR [STDERR]  at  java.awt.Toolkit$2.run(Toolkit.java:821)

2010-07-13 08:56:34,633  ERROR [STDERR]  at java.security.AccessController.doPrivileged(Native  Method)

2010-07-13 08:56:34,633 ERROR [STDERR]  at  java.awt.Toolkit.getDefaultToolkit(Toolkit.java:804)

2010-07-13  08:56:34,633 ERROR [STDERR]  at  java.awt.Toolkit.getEventQueue(Toolkit.java:1592)

2010-07-13  08:56:34,633 ERROR [STDERR]  at  java.awt.EventQueue.invokeLater(EventQueue.java:811)

2010-07-13  08:56:34,633 ERROR [STDERR]  at  javax.swing.SwingUtilities.invokeLater(SwingUtilities.java:1198)

2010-07-13  08:56:34,633 ERROR [STDERR]  at  com.eviware.soapui.support.swing.SwingUtils.invokeLater(SwingUtils.java:26)

2010-07-13  08:56:34,633 ERROR [STDERR]  at  com.eviware.soapui.support.UISupport.invokeLater(UISupport.java:555)

2010-07-13  08:56:34,633 ERROR [STDERR]  at  com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:117)

2010-07-13  08:56:34,634 ERROR [STDERR]  at java.lang.Thread.run(Thread.java:595)

Any  input would be greatly appreciated,

Steffen.

0 Replies

Avatar

Level 10

Steffen,

Is this happening at design time in Workbench or at run-time?

Steve

Avatar

Level 3

Hi Steve,

thanks for your quick reply.

The issue occurs at runtime. The respective server is a production machine which cannot be accessed using Workbench.

Steffen.

Avatar

Level 10

Can you call the same Web Service successfully from another client?

Avatar

Level 3

Hi Steve,

the WebService is ok, I have repeatedly tested it, even using the GUI version of SOAPUI.

The strange thing is that the call also actually seems to work from the production server, but it is giving a lot of those described exceptions. This, in turn, triggers the automatic alarms infrastructure which reports that LiveCycle is causing a lot of exceptions. The description "cannot load icon", also seems to be pretty irrelevant since there is no GUI at all. That's why I thought it could maybe be a configuration issue ...

Steffen.

Avatar

Level 3

Yes I do, but I have an "educated guess" what might be causing this.

The LC server is running on Solaris. From time to time, there's the need to run some program which is using a GUI (like configManager for example). To be able to do this, the DISPLAY env variable needs to be set if one wants to see the respective windows etc.

It seems like whenever this variable is not empty, the issue occurs. I cannot confirm this 100%, but at least this seems to make some sense.

Steffen.

Avatar

Level 2

Hi Stephan,

Could you please tell me which version of LC ES you are running.

Are you running with some specific Service Packs?

- Pushkar

Avatar

Level 1

This is really pity as noone from Adobe is able to answer this.

By the way just for the information for others who may face this issue, we have resolved this.

The problem was if you start Jboss from command prompt which has already exported the DISPLAY variable, then these exception will occur with every request. It seems ALC is using this DISPLAY variable internally.