Win a copy of React Cookbook: Recipes for Mastering the React Framework this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Rob Spoor
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Holloway
  • Piet Souris
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Frits Walraven
  • Himai Minh

Errors while deploying on JBoss 4.05GA

 
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am trying to deploy Jforum 2.16 on JBoss 4.05. However, I get the folowing error (see below). Did anyone have any sucess with deploying on JBoss? did you have to change any of teh configuration files to accomodate that?

9:45:42,088 ERROR [MainDeployer] Could not create deployment: file:/home/shlomo/Install/jboss-4.0.5.GA/server/default/tmp/deploy/tmp42334JForum-2.1.6.zip-contents/JForum-2.1.6/WEB-INF/lib/bsh-2.0b4.jar-contents/bsh/commands/load.bsh
org.jboss.deployment.DeploymentException: create operation failed for script file:/home/shlomo/Install/jboss-4.0.5.GA/server/default/tmp/deploy/tmp42334JForum-2.1.6.zip-contents/JForum-2.1.6/WEB-INF/lib/bsh-2.0b4.jar-contents/bsh/commands/load.bsh; - nested throwable: (org.jboss.deployment.DeploymentException: Sourced file: eval stream : BeanShell Scripted Classes cannot currently extend Java types.; - nested throwable: (Sourced file: eval stream : BeanShell Scripted Classes cannot currently extend Java types. : at Line: 17 : in file: eval stream : public class BshObjectInputStream extends ObjectInputStream {
))
at org.jboss.varia.deployment.BeanShellSubDeployer.create(BeanShellSubDeployer.java:182)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.deployment.DeploymentException: Sourced file: eval stream : BeanShell Scripted Classes cannot currently extend Java types.; - nested throwable: (Sourced file: eval stream : BeanShell Scripted Classes cannot currently extend Java types. : at Line: 17 : in file: eval stream : public class BshObjectInputStream extends ObjectInputStream {
)

[originally posted on jforum.net by shlomo]
 
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Successfully deployed on jboss 4.0.3SP1, on 4.0.5 got some exception after a fast test deploy, haven't got the time to check and identify all the issues yet. All the exceptions seems to be related to wrong libraries version (old libraries not compatible with jboss 4.0.5) or only to duplicated jar already present in server lib directory.
I suggest to ensure that bsh is not already in /lib directory of you server.

[originally posted on jforum.net by Jules]
 
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Thank you very much for your reply. I am getting exactly the same error with jboss 4.0.3SP1. Did you have to remove any libs from that distribution too?



Jules wrote:Successfully deployed on jboss 4.0.3SP1, on 4.0.5 got some exception after a fast test deploy, haven't got the time to check and identify all the issues yet. All the exceptions seems to be related to wrong libraries version (old libraries not compatible with jboss 4.0.5) or only to duplicated jar already present in server lib directory.
I suggest to ensure that bsh is not already in /lib directory of you server.



[originally posted on jforum.net by shlomo]
 
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, you must remove the duplicated ( already present in jboss-4.0.3SP1\server\servername\lib and loaded by jboss at startup) libraries from 4.0.3 too.
Here is the content of my WEB-INF/lib directory after clean up:


c3p0-0.9.0.2.jar
commons-io-1.1.jar
concurrent.jar
dwr-1.1-RC1.jar
freemarker-2.3.4.jar
htmlparser-1.5.jar
jcaptcha-all-1.0-RC2.0.1.jar
jmxri.jar
quartz-1.5.1.jar
xom-1.0.jar

(i suggest to put all used jdbc drivers in jboss-4.0.3SP1\server\servername\lib, and remove the unused one from here )





Note that the "servername" of this example is a server directory with content derived from "all". Default or minimal may not include the same libray set and require to recheck the presence of all required library ( in other words, if you use one of those you must recheck for libs duplication ).

[originally posted on jforum.net by Jules]
 
Migrated From Jforum.net
Ranch Hand
Posts: 17424
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jules,
Thanks again for your reply. Removing Jars from the JBoss lib id not an option as it breaks up the compatability with other deployed applications.

The problem was different alltogether. The Jforum war file contains a folder named Jforum inside the archived war file. I removed that folder and re packed the archive and the deployment was successful. I still have some other issues with the JDBC connection. Please see:
http://www.jforum.net/posts/list/0/3108.page#13532



[originally posted on jforum.net by shlomo]
 
crispy bacon. crispy tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic