Announcement

**Isomorphic** · 10 Jan 2014, 08:44

Sorry, no, we have not seen this before.

You refer to something in the code as hardcoded, but what is "hardcoded" is just the name of the class we're expecting to be able to use - this isn't really any more hardcoded than an ordinary Java import. It's just an ordinary dependency.

Since you're reporting this as an intermittent problem with server *restart*, it doesn't seem like changing the class name to something else is a fix. It works fine, then something goes wrong in Websphere, possibly a classloader issue. We would suggest making sure you don't have duplicate copies of .jars in your classpath.

**GM_GWT** · 13 Jan 2014, 04:51

Hi Isomorphic,

I guess you haven't understood the issue we are facing. By now we have managed to build a work-around to this issue by the following. Hope this helps you get into this issue.

Code:

    private void initVelocity()
    {
        try
        {
            // Initialize Apache velocity runtime engine (over Apache velocity engine)
            final VelocityEngine ve = new VelocityEngine();
            ve.setProperty(RuntimeConstants.RUNTIME_LOG_LOGSYSTEM_CLASS, Log4JLogChute.class.getName());
            ve.setProperty("runtime.log.logsystem.log4j.category", "org.apache.Velocity");
            ve.init();

            // Assign the initialized velocity engine to the isomorphic velocity proxy
            final Field field = com.isomorphic.velocity.Velocity.class.getDeclaredField("vEngine");
            field.setAccessible(true);
            field.set(null, ve);

            LOGGER.info("Isomorphic Velocity Runtime Engine initialization completed!");
        }
        catch (final Exception e)
        {
            LOGGER.log(Level.SEVERE, "Cannot initialize Velocity", e);
        }
    }

An ideal way would be, to make the apache velocity framework initialization some-how configurable for the clients.

**Isomorphic** · 15 Jan 2014, 08:33

No, we definitely do not have a clear picture of your issue.

As best we can understand, you want to have Velocity use a log system other than log4j, but instead of saying this, you've brought up an issue where Websphere fails on restart.. which continues to appear to have been due to a bad classpath.

If you can give a clear idea of what you actually want to achieve - not just claiming that something is "hardcoded", but clearly explaining the actual purpose you have in mind in changing it - we may be able to help.

**Isomorphic** · 14 Jan 2015, 02:41

To clarify further, we think your analysis of the problem is wrong.

It doesn't make sense that we would need to tell Velocity in particular to use a log4j configuration that is different from *all the other logs that the SmartGWT Server logs*. It's not hardcoding to have Velocity use the same logging system.

Now, have you tried Googling the error message? Most of the results suggest that either the directory where logs are written is not writable, or there is a classpath issue, or something similar. So we'd suggest looking into that. In our opinion your fix addresses a symptom and not a cause. If you disagree, explain clearly why.

Announcement

VelocityException: Error initializing log

Comment

Comment

Comment

Comment