[Installation, Configuration & DEPLOYMENT] - jboss 4.2.1 GA install problem
by light1
I have downloaded jboss-4.2.1.GA.zip and installed in fedora core 6. The other supporting packages that installed for jboss are
jdk-1_5_0_13-linux-i586.rpm on /usr/java/jdk-1_5_0_13
java-1.5.0-sun-compat-1.5.0.13-1jpp.i586.rpm
ant version 1.6.5 installed by deafult
but I am not able to run jboss successfully.I do see some posts that says log4j.jar is the problem. there are two defferent version of log4j.jar found one is /usr/jboss-4.2.1.GA/lib/log4j.jar version 1.2.14 and the other one is 1.2.13 at /usr/share/java/log4j.jar. I removed the file /usr/share/java/log4j.jar but still jboss not running. please help me to solve this problem
the run output is here
=======================================================
JBoss Bootstrap Environment
JBOSS_HOME: /usr/jboss-4.2.1.GA
JAVA: /usr/lib/jvm/jre-1.5.0-sun/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
CLASSPATH: /usr/jboss-4.2.1.GA/bin/run.jar
=========================================================================
08:05:41,843 INFO [Server] Starting JBoss (MX MicroKernel)...
08:05:41,845 INFO [Server] Release ID: JBoss [Trinity] 4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)
08:05:41,847 INFO [Server] Home Dir: /usr/jboss-4.2.1.GA
08:05:41,847 INFO [Server] Home URL: file:/usr/jboss-4.2.1.GA/
08:05:41,849 INFO [Server] Patch URL: null
08:05:41,849 INFO [Server] Server Name: default
08:05:41,849 INFO [Server] Server Home Dir: /usr/jboss-4.2.1.GA/server/default
08:05:41,850 INFO [Server] Server Home URL: file:/usr/jboss-4.2.1.GA/server/default/
08:05:41,850 INFO [Server] Server Log Dir: /usr/jboss-4.2.1.GA/server/default/log
08:05:41,850 INFO [Server] Server Temp Dir: /usr/jboss-4.2.1.GA/server/default/tmp
08:05:41,851 INFO [Server] Root Deployment Filename: jboss-service.xml
08:05:43,654 INFO [ServerInfo] Java version: 1.5.0_13,Sun Microsystems Inc.
08:05:43,655 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_13-b05,Sun Microsystems Inc.
08:05:43,655 INFO [ServerInfo] OS-System: Linux 2.6.18-1.2798.fc6,i386
08:05:45,529 INFO [Server] Core system initialized
08:06:07,729 WARN [BasicMBeanRegistry] javax.management.MBeanRegistrationException: preRegister() failed: [ObjectName='jboss.remoting:service=NetworkRegistry', Class=org.jboss.remoting.network.NetworkRegistry (org.jboss.remoting.network.NetworkRegistry@e35bb7)]
08:06:07,774 ERROR [MainDeployer] Could not create deployment: file:/usr/jboss-4.2.1.GA/server/default/conf/jboss-service.xml
org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.InvocationTargetException)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
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.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.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
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:508)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.reflect.InvocationTargetException
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1451)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1350)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:345)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
... 36 more
Caused by: javax.management.MBeanException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:180)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
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 o
---------
-----
----
... 56 more
08:06:18,202 INFO [Server] Runtime shutdown hook called, forceHalt: true
08:06:18,202 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
08:06:18,296 INFO [Server] Shutdown complete
Shutdown complete
Halting VM
Thanks,
light
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095631#4095631
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095631
18Â years, 9Â months
[JBoss jBPM] - Passing ContextInstance as parameter to session bean ?
by preitsma
Hi,
I am reflecting a bit on the architecture of my JBPM driven back-end file processing application: I wrote a couple of stateless session beans that provide more or less atomic functions (methods). From the action handlers in my processes I make remote EJB calls to these methods. Every method call passes one or more process variables and modifies some.
What annoys me in this setup is that I need to implement a separate ActionHandler for every process step that merely makes one method call passing one ore more process variables as parameters and and does some process variable modification.
I would like to implement a generic ActionHandler that passes the ContextInstance (or VariableContainer) as a parameter to my session bean and have the session bean layer read and write the appropriate process variables from the ContextInstance and pass it back. Using reflection, the session bean and method name could thus be defined as ActionHandler parameters in the process definition.
Could anyone comment on the cons of such setup? It feels like I am overlooking something obvious or reinventing something that?s already there.
Thanks in advance for any help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095628#4095628
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095628
18Â years, 9Â months
[JBoss Seam] - Re: Quartz - persisting timers on the database problem.
by raffaele.camanzo
I tried to go deeper in the problem and found these lines in the server.log:
| 2007-10-16 15:26:44,810 INFO [org.jboss.seam.contexts.Contexts] starting up: org.jboss.seam.async.dispatcher
| 2007-10-16 15:26:44,977 INFO [org.jboss.seam.async.QuartzDispatcher] No seam.quartz.properties file. Use in-memory job store.
| 2007-10-16 15:26:45,061 INFO [org.quartz.simpl.SimpleThreadPool] Job execution threads will use class loader of thread: main
| 2007-10-16 15:26:45,090 INFO [org.quartz.core.QuartzScheduler] Quartz Scheduler v.1.6.0 created.
| 2007-10-16 15:26:45,093 INFO [org.quartz.simpl.RAMJobStore] RAMJobStore initialized.
| 2007-10-16 15:26:45,094 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource
| file in Quartz package: 'quartz.properties'
| 2007-10-16 15:26:45,094 INFO [org.quartz.impl.StdSchedulerFactory] Quartz scheduler version: 1.6.0
| 2007-10-16 15:26:45,097 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
| 2007-10-16 15:26:45,097 INFO [org.jboss.seam.async.QuartzDispatcher] The QuartzDispatcher has started
|
But the file exists and seems to be in the right place (the root of the jar); I tried also in the root of the ear and of the war but the Dispatcher says always the same thing.
I tried to download the latest version from the CVS and added some prints around the root of the problem (getResourceAsStream("/seam.quartz.properties")) but with the current CVS version Seam prints nothing at all.
Any suggestion?
Regards,
Raffaele Camanzo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095625#4095625
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095625
18Â years, 9Â months