[Beginners Corner] - your current Jboss evaluation
by Aldian_00
Hi everybody
I am currently working on a comparative study of Jonas, Jboss, Glassfish, Geronimo. For all technical questions, I already have the information on the internet, and those four are the only one application servers that can meet my needs. But I would like to know what do experienced user think about their ergonomy. For each of them, I am posting the same question on their respective forum. Please be honest and objective so that I can make a good comparison (even if for you JBoss is clearly the best ;)).
About JBoss, what evaluation (please give a mark from 1=worst to 10=best) would you give concerning the following tests?
* easy to install
* easy deployment
* easy administration
* easy IDE interfacing
* easy developement
Feel free to comment about the others softwares if you know something about them.
Thank You very much !
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214880#4214880
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214880
15 years, 10 months
[EJB 3.0] - Service Bean - Strange behaviour on redeploy
by rnicholson10
I have a service bean, that spawns a thread, which reads messages from one queue and sends them out on another.
The thread is correctly stopped in both the stop and destroy methods of the bean.
Everything works as expected if it's a fresh startup of JBoss or the service bean is deployed for the first time. But when I re-deploy the service bean message receives are intermittent. I can see the messages that never get consumed in the MySQL DB. Restarting Jboss solves this problem.
I'm running this on AS5.0.0.GA. Has anyone else had a similar problem or have any solution to this. For the moment the solution is to restart JBoss every time I redeploy the bean.
P.S. I don't see any error messages in the log indicating there is a problem. However after a number of deploys I sometimes get a debug message "Thread pool class supplied is not an object name."
The following is the log when I send 10 messages to the queue. As you can see from the log only 4 messages are received (and there are only 7 responses (line delimited) in the log from the 10 sends I do). The other 6 are still in the DB. If I then restart JBoss the remaining 6 messages are read and the behaviour is once more normal.
| 2009-03-04 12:21:52,544 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#1[172.16.66.231:59738]) No SecurityMetadadata was available for speQueueEngineIn, using default security config
|
| 2009-03-04 12:22:07,998 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#1[172.16.66.231:59738]) No SecurityMetadadata was available for speQueueEngineIn, using default security config
|
| 2009-03-04 12:22:08,011 DEBUG [org.jboss.remoting.ServerInvoker] (WorkerThread#0[172.16.66.231:59737]) Thread pool class supplied is not an object name.
| 2009-03-04 12:22:08,014 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived
| 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) Received message
| 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) Routing to DS
| 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:08,015 INFO [STDOUT] (Thread-48) Time to test: 1236169328058
| 2009-03-04 12:22:08,016 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (Thread-48) No SecurityMetadadata was available for speQueueDownstreamOut, using default security config
|
| 2009-03-04 12:22:34,902 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#1[172.16.66.231:59738]) No SecurityMetadadata was available for speQueueEngineIn, using default security config
|
| 2009-03-04 12:22:39,365 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (WorkerThread#0[172.16.66.231:59737]) No SecurityMetadadata was available for speQueueEngineIn, using default security config
| 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived
| 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) Received message
| 2009-03-04 12:22:39,379 INFO [STDOUT] (Thread-48) Routing to DS
| 2009-03-04 12:22:39,380 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:39,380 INFO [STDOUT] (Thread-48) Time to test: 1236169359426
| 2009-03-04 12:22:39,380 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (Thread-48) No SecurityMetadadata was available for speQueueDownstreamOut, using default security config
|
| 2009-03-04 12:22:47,535 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived
| 2009-03-04 12:22:47,535 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) Received message
| 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) Routing to DS
| 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:47,536 INFO [STDOUT] (Thread-48) Time to test: 1236169367584
|
| 2009-03-04 12:22:55,115 INFO [STDOUT] (Thread-48) MessageRoutingBeanService - MessageReceived
| 2009-03-04 12:22:55,115 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) Received message
| 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) Routing to DS
| 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) ----------------
| 2009-03-04 12:22:55,116 INFO [STDOUT] (Thread-48) Time to test: 1236169375163
|
A similar thread runs fine from a servlet with no problems even after redeploy. Hence the reason I'm posting this in the EJB3.0 forum.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214872#4214872
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214872
15 years, 10 months
[JBoss jBPM] - Re: gwt-console datasource problems
by jjrs
My datasource is in [Jboss.4.2.3.GA]\server\default\deploy\jbpm and the content is ...
<datasources>
| <local-tx-datasource>
| <jndi-name>JbpmDS</jndi-name>
| <connection-url>jdbc:oracle:thin:@dbServer:1521:dbInstance</connection-url>
|
| <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
| <user-name>user</user-name>
| <password>passwd</password>
|
| <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
|
| <metadata>
| <type-mapping>Oracle9i</type-mapping>
| </metadata>
| </local-tx-datasource>
|
| </datasources>
In login-config.xml I added the next section...
| <!-- New jBPM config -->
| <application-policy name = "jbpm">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule"
| flag="required">
| <module-option name="dsJndiName">java:/JbpmDS</module-option>
| <module-option name="principalsQuery">
| SELECT PASSWORD_ FROM JBPM_ID_USER WHERE NAME_=?
| </module-option>
| <module-option name="rolesQuery">
| SELECT g.NAME_ ,'Roles'
| FROM JBPM_ID_USER u,
| JBPM_ID_MEMBERSHIP m,
| JBPM_ID_GROUP g
| WHERE g.TYPE_='security-role'
| AND m.GROUP_ = g.ID_
| AND m.USER_ = u.ID_
| AND u.NAME_=?
| </module-option>
| </login-module>
| </authentication>
| </application-policy>
|
The oracle driver and the oracle version should be fine, otherwise I wouldn't be able to see any result, and I am having problems only with the Reports part of the gwt-console. With my current settings the jbpm-console is working fine, but the gwt-console, always complains about not being able to get a connection to the database.
Any other idea ? Do I have to modify the contents of any of the war files ? There are several parts in the jboss-web.xml files where the datasource is referenced, although this settings are commeted in the config files. If I enable that configuration the system complains saying ....
2009-03-04 12:04:40,662 DEBUG [org.jboss.web.tomcat.service.JBossWeb] Problem in init
| org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/jboss-web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: resource-ref jdbc/JbpmDataSource found in jboss-web.xml but not in web.xml)
| at org.jboss.web.AbstractWebContainer.parseMetaData(AbstractWebContainer.java:768)
| at org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:356)
| 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)
|
Any other suggestion ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214867#4214867
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214867
15 years, 10 months
[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
15 years, 10 months