[Installation, Configuration & DEPLOYMENT] - Does Jboss4.2.3.GA specific support for Whitespace and Unico
by minchu.jboss
We are having the JBOSS located at following location in japanes locale box
C:\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA\bin
So now when we run the jboss server it giving us the following exception
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\naveen\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA
JAVA: C:\Program Files\Java\jre1.6.0_06\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
CLASSPATH: C:\naveen\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA\bin\run.jar
===============================================================================
16:36:51,921 INFO [Server] Starting JBoss (MX MicroKernel)...
16:36:51,931 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)
16:36:51,951 INFO [Server] Home Dir: C:\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA
16:36:51,951 INFO [Server] Home URL: file:/C:/ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§/jboss-4.2.3.GA/
16:36:51,961 INFO [Server] Patch URL: null
16:36:51,961 INFO [Server] Server Name: default
16:36:51,961 INFO [Server] Server Home Dir: C:\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA\server\default
16:36:51,961 INFO [Server] Server Home URL: file:/C:/ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§/jboss-4.2.3.GA/server/default/
16:36:51,961 INFO [Server] Server Log Dir: C:\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA\server\default\log
16:36:51,961 INFO [Server] Server Temp Dir: C:\ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§\jboss-4.2.3.GA\server\default\tmp
16:36:51,961 INFO [Server] Root Deployment Filename: jboss-service.xml
16:36:53,270 INFO [ServerInfo] Java version: 1.6.0_06,Sun Microsystems Inc.
16:36:53,280 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b22,Sun Microsystems Inc.
16:36:53,280 INFO [ServerInfo] OS-System: Windows 2003 5.2,x86
16:36:54,710 INFO [Server] Core system initialized
16:37:01,817 ERROR [MainDeployer] Could not create deployment: file:/C:/ãµã³ã¿ã㧠ãµã³ã¿ã㧠ãµã³ã¿ãã§/jboss-4.2.3.GA/server/default/conf/jboss-service.xml
org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.UndeclaredThrowableException)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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:251)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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(Unknown Source)
Caused by: java.lang.reflect.UndeclaredThrowableException
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:236)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
... 36 more
Caused by: java.lang.Error: ERROR: it turns out the root cause is not always a runtime exception!
at org.jboss.mx.server.MBeanServerImpl.handleInstantiateExceptions(MBeanServerImpl.java:1295)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1237)
at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286)
at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:344)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:157)
... 38 more
16:37:01,847 INFO [Server] Runtime shutdown hook called, forceHalt: true
16:37:01,847 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
16:37:01,927 INFO [Server] Shutdown complete
Shutdown complete
Halting VM
ç¶è¡ããã«ã¯ä½ããã¼ãæ¼ãã¦ãã ãã . . .
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214864#4214864
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214864
17 years, 1 month
[JBoss jBPM] - "Runtime Task" Why not ?
by AlClientView
Hi everyone,
I have a question about what change can(not)/should(not) be allowed to be done at runtime. More specifically I'm thinking about Task:
The way Jbpm is implemented (if I'm not wrong) allows client application to create task instance(s) for one Task at runtime. This can be done easily by using the API. And my question is what about "Runtime Task". I mean by runtime Task: Adding a Task to a process instance.
>From what I've seen, nothing prevent a client application from adding a Task to a TaskNode at runtime but this means all process instances will be affected by this change (since the change is done at the process definition level).
I'm not saying this implementation is wrong, I just try to understand what is the logic behind this choice.
There are runtime actions for example why not to have also runtime Task. Is it against the BPM philosophy, saying this is part of the process design done by the BA and in anycase that should be changed at runtime ?
I can understand this rule but then how to support the implementation of a Task node for which the creation of Task is decided by a rule (RuleEngine) ?
Sorry to be long but I'm very interested and curious to know what you guys think about this, first regarding JBPM and then BPM in general...
Thanks in advance,
Arnaud.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214856#4214856
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214856
17 years, 1 month
[EJB 3.0] - Session Bean call from an MBean, isolation and the TCCL
by os
Hi,
I have an EAR containing an MBean and a Session Bean. Isolation is turned on. The Session Beans interface is not visible, since it should only be called via the MBean.
When I call the EJB3 Session bean from an MBeans method the org.jboss.ejb3.proxy.objectfactory.session.SessionProxyObjectFactory
checks if the Session Beans Proxy is loaded by the same classloader as the currents threads context classloader (TCCL). If not, it tries to relaod the Classes with the TCCL. But if the MBeans method is invoked from a WebContext (e.g. jmx-console) it fails with
RuntimeException("Can not find interface declared by Proxy in our CL + " + tcl, e)
since the Session Beans remote interface is not (and shall not) be visible from the Web context.
Is there a way to call a EJB3 Session Bean from an MBean while avoiding the reload of the classes by the SessionProxyObjectFactory?
Thanks in advance
Olaf
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214850#4214850
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214850
17 years, 1 month
[EJB 3.0] - ClassCastException on Stateless Session Bean
by robert.geisler
hello everybody,
currently we are migrating our EJB 2.1 (about 850 EJBs) to EJB 3.0. till now there have not been too many problems, but today i meet a special challeng when i migrated a Stateful Session Bean.
the SFSB, lets call it MyStatefulSessionBean implements a Remote Business Interface (MyStatefulSession) and gets deployed in a EAR (MyEAR.ear). from a standalone client i can lookup, cast and use the SFSB successfully.
otherwise we deploy a WAR, too. from there i can lookup the SFSB, but cannot use it, because casting results in ClassCastException:
Context context = ContextFactory.getInstance().getContext();
| MyStatefulSession session = (MyStatefulSession) context.lookup("MyEAR/MyStatefulSession/remote");
$Proxy123 cannot be cast to xzy.MyStatefulSession
the MyStatefulSession.class is packaged in server/MyServer/lib/MyLibrary.jar and in our EAR, too.
i tried to remove all duplicate interfaces and classes from the EAR, but than i get java.lang.VerifyError -that i cannot understand- in arbitrary implementation classes (even in EJB 2.1 SLSB).
2009-03-04 11:48:41,837 WARN [org.jboss.ejb.EJBDeployer] Verify failed; continuing
| java.lang.VerifyError: (class: a/b/c/ArbitraryBean, method: getSomething signature: (Ljava/lang/String;ILx/y/z/SomeDTO;)Ljava/util/ArrayList;) Incompatible argument to function
| at java.lang.Class.getDeclaredMethods0(Native Method)
| at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
| at java.lang.Class.privateGetPublicMethods(Unknown Source)
| at java.lang.Class.getMethods(Unknown Source)
| at org.jboss.verifier.strategy.AbstractVerifier.hasEJBCreateMethod(AbstractVerifier.java:687)
| at org.jboss.verifier.strategy.EJBVerifier21.verifySessionBean(EJBVerifier21.java:858)
my idea is that all classes and interfaces that will be used from EAR and WAR, should go to server/MyServer/lib/, implementation classes should remain in EAR, servlets should go into WAR.
is that right? if so, we have to refactor our ANT builds, i guess ; )
anyway... i wonder why our packaging strategy do not show any conflicts for Stateless Session Beans. maybe someone can help me with this...?
thanks in advance
robert
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214841#4214841
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214841
17 years, 1 month