Beehive/Weblogic jar file not available

[Ken Bowen]

I've been using DWR 2.0.(6..10) (Direct Web Remoting) with two Appengine java projects for a number of years, with no problems.  About 2015-07-18, when production Appengine switched from using SDK 1.9.23 to SDK 1.9.24,  I began getting the following exception each time one of my projects starts:

org.directwebremoting.util.CommonsLoggingOutput error: Failed to load 'pageflow' (org.directwebremoting.beehive.PageFlowCreator)

java.lang.reflect.InvocationTargetException

at com.google.appengine.runtime.Request.process-eaa0bc63bfae4257(Request.java)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

......

Caused by: java.lang.ClassNotFoundException: Beehive/Weblogic jar file not available.

at org.directwebremoting.beehive.PageFlowCreator.<init>(PageFlowCreator.java:58)

.....

Neither of my projects had any code changes around that time.  Was the Beehive/Weblogic jar available in GAE before SDK 1.9.24?  Can anyone give me any pointers about this?

Thanks in advance,

Ken Bowen

[Nick (Cloud Platform Support)]

Hi Ken,

It sounds as though this is a specific third-party technology unrelated to Google, and I can't find it documented anywhere that this would be available on the platform. It sounds as though your app itself would have had to bundle this dependency when it was uploaded. Do you still have access to the project source? Is the "Beehive/Weblogic jar" included in your project's lib/ folder? 

Regards,

Nick

[Ken Bowen]

Hi Nick,

That's what's strange.   I've been using dwr_2.0.6/7 for a number of years, and there's never been any *bee*.jar or *weblogic*.jar in my lib dir. To my memory, there were no other dependencies downloaded with dwr.    Yet prior to  2015-07-18,  I've never seen this exception, and the dwr jar in my projects didn't change then.  In fact, my jar list didn't change at all before or immediately after  2015-07-18. (Later I checked moving up to dwr_2.0.10, but that still produces this exception).  That's why I wondered whether the Beehive/Weblogic jar could have been supplied by GAE earlier.   It all seems very odd.  I'm going to contact the DWR guys and see what they say.

Thanks,

Ken

[Nick Payne]

Hey Ken,

That sounds good. Please let us all know in this thread whatever you manage to hear from them. Perhaps there was some kind of dynamic remote jar loading happening and the routine/location has since changed?

I actually just learned of DWR based on your comment and have been looking into it. It seems like a great technology. As said, this seems mysterious to all involved. Perhaps their comment can shed some light.

Best wishes,

Nick

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/KZwF_uTxAto/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/906ac590-c65a-42d1-a1d6-cbe6c7d886ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Nick

Technical Solutions Representative
Google Cloud Platform

“It is like a lighted torch whose flame can be distributed to ever so many other torches which people may bring along; and therewith they will cook food and dispel darkness, while the original torch itself remains burning ever the same. It is even so with the bliss of the Way."
― Gautama Buddha (On Computing & Information Theory)

[Ken Bowen]

Nick - Followup:  Based on advice from the DWR community, I solved the problem this way:

Opened the dwr.2.0.10.jar, and performed:

a) Opened org/directwebremoting/dwr.xml and removed
   <creator id="pageflow" class="org.directwebremoting.beehive.PageFlowCreator”/>
b) Removed org/directwebremoting/beehive/PageFlowCreator.class

Closed the jar.  Everything works as it should after re-deployment.

It remains a mystery as to why this error didn't appear prior to July.  

Thanks,

Ken