[JBoss Messaging] - 1.2.0beta1 with JEMS 1.2.0CR1 fails
by Juergen.Zimmermann
After installing JBoss Messaging using "ant -f release-admin.xml" I tried to start the JBoss server using "run -c messaging". However, I get the following stack trace. Any hint is appreciated!
...
| 2006-12-21 15:14:17,347 INFO [org.jboss.remoting.transport.socket.SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://127.0.0.1:3873/]
| 2006-12-21 15:14:23,476 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/C:/Programme/jboss/server/messaging/deploy/jboss-messaging.sar/postgresql-persistence-service.xml
| org.jboss.deployment.DeploymentException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>(); - nested throwable: (java.lang.NoSuchMethodException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>())
| 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.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.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 $Proxy6.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.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| 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.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: java.lang.NoSuchMethodException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>()
| at java.lang.Class.getConstructor0(Class.java:2678)
| at java.lang.Class.getConstructor(Class.java:1629)
| at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1232)
| at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286)
| at org.jboss.system.ServiceCreator.install(ServiceCreator.java:193)
| at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449)
| at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
| ... 84 more
| 2006-12-21 15:14:27,532 INFO [org.jboss.ws.server.ServiceEndpointManager] jbossws-1.0.4.GA (date=200611151648)
| ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995606#3995606
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995606
19 years, 4 months
[Messaging, JMS & JBossMQ] - Problem with createTopicConnection - over http proxy server
by alexz75
Hi All!
I tried find any solution for follow issue during migration to HTTP lookups:
1. We have JBOSS 4.0.5GA server installed in our local network.
2. We successfully work with EJB beans locally and remotely
3. We have no problem to work with JMS locally
But...
createTopic throws exception (see below).
I've found source of this problem usage of ipaddress in url: http://145.9.239.153:8080/jbossmq-httpil/HTTPServerILServlet
Because java not able to detect - this ip address is local and can't be accessed thru gateway.
We have workaround - put specific ip address into list of bypass adresses, but it seems ugly, we have couple of remote servers, that should be accessed thru gateway.
How we can force client usage of URL instead of ip?
(jndi.properties have full qualified name of server host)
| jndiContext = m_ctx;
| ref = (TopicConnectionFactory) jndiContext.lookup("HTTPConnectionFactory");
| m_topic = (Topic)jndiContext.lookup(LMProperties.sTOPIC_PATH);
| // here it hangs for 2 mins and throw exception:
| m_topic_connection = ref.createTopicConnection();
|
Exception:
| Cannot authenticate user; - nested throwable: (java.io.IOException: Server returned HTTP response code: 504 for URL: http://145.9.239.153:8080/jbossmq-httpil/HTTPServerILServlet)
| javawsApplicationMain|org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72)
| org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57)
| org.jboss.mq.Connection.authenticate(Connection.java:1069)
| org.jboss.mq.Connection.<init>(Connection.java:252)
| org.jboss.mq.Connection.<init>(Connection.java:323)
| org.jboss.mq.SpyConnection.<init>(SpyConnection.java:116)
| org.jboss.mq.SpyConnectionFactory.internalCreateConnection(SpyConnectionFactory.java:137)
| org.jboss.mq.SpyConnectionFactory.createTopicConnection(SpyConnectionFactory.java:118)
|
Glad to get any suggestions...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995603#3995603
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995603
19 years, 4 months
[JBoss Messaging] - JBoss doesnt release threads after executing MDB (out of Mem
by suhail
Hi,
I am using JBoss AS jboss-4.0.2.
I am getting OutOfMemoryError when I send the messages to an MDB. It happens after i send 30-40 messages. What I have observed on the web-console of Jboss is that #Threads increases by some 30 whenever I sent one message to a queue. Even though message is getting consumed instantly, the thread count doesn?t come down but keep on increasing by a factor of approx 30 or more with each message. After sometime it reaches some 2000 figure and server starts giving out of memory error. If I make process synchronous (I mean not use MDB) , thread count doesnt increase.
It implies that each message is adding approx. 30 threads and threads are not released after messages are getting consumed. Can anybody explain it and give a fix ?
Please find the stack of errors below. I get either of these two stacks.
Any help will be appreciated.
Thank you
Suhail
20 Dec 2006 16:20:10,176 WARN (UILServerILService Accept Thread:) [org.jboss.mq.il.uil2.UILServerILService] Unexpected error in setup of client connection
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:574)
at org.jboss.mq.il.uil2.SocketManager.start(SocketManager.java:147)
at org.jboss.mq.il.uil2.UILServerILService.run(UILServerILService.java:162)
at java.lang.Thread.run(Thread.java:595)
20 Dec 2006 13:18:35,031 ERROR (TimeoutFactory-0:) [org.jboss.logging.Log4jService$ThrowableListenerLoggingAdapter] Unhandled Throwable
org.jboss.util.threadpool.ThreadPoolFullException: java.lang.OutOfMemoryError: unable to create new native thread
at org.jboss.util.threadpool.BasicThreadPool.execute(BasicThreadPool.java:417)
at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:192)
at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:212)
at org.jboss.util.threadpool.BasicThreadPool.run(BasicThreadPool.java:206)
at org.jboss.util.timeout.TimeoutFactory.doWork(TimeoutFactory.java:223)
at org.jboss.util.timeout.TimeoutFactory.access$000(TimeoutFactory.java:41)
at org.jboss.util.timeout.TimeoutFactory$1.run(TimeoutFactory.java:136)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995601#3995601
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995601
19 years, 4 months
[Installation, Configuration & Deployment] - auth-method FORM ? realm-name ? JBoss-4.0.5GA, what i missed
by WatchCat
HELP PLS!
I don't know where to search for the decision of my problem.
There is some application that use FORM authentication method.
These are fragments of config-files.
login-config.xml:
| <policy>
| ...
| <application-policy name="MyDomain">
| <authentication>
| <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required">
| <module-option name = "unauthenticatedIdentity">guest</module-option>
| <module-option name = "dsJndiName">java:/PostgreDS</module-option>
| <module-option name = "principalsQuery">SELECT PASSWD FROM SYS_USERS WHERE USERID=?</module-option>
| <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM SYS_ROLES WHERE USERID=?</module-option>
| </login-module>
| </authentication>
| </application-policy>
| </policy>
|
web.xml:
| ...
| <login-config>
| <auth-method>FORM</auth-method>
| <realm-name>MyDomain<realm-name>
| <form-login-config>
| <form-login-page>/LoginForm.jsp</form-login-page>
| <form-error-page>/LoginForm.jsp</form-error-page>
| </form-login-config>
| </login-config>
| ...
|
jboss-web.xml:
| <jboss-web>
| <security-domain>java:/jaas/MyDomain</security-domain>
| </jboss-web>
|
but when i try open application in browser, in log file appears this message:
| ...
| 00:00:27,890 ERROR [UsersRolesLoginModule] Failed to load users/passwords/role files
| java.io.IOException: No properties file: users.properties or defaults: defaultUsers.properties found
| at org.jboss.security.auth.spi.Util.loadProperties(Util.java:315)
| at org.jboss.security.auth.spi.UsersRolesLoginModule.loadUsers(UsersRolesLoginModule.java:186)
| at org.jboss.security.auth.spi.UsersRolesLoginModule.createUsers(UsersRolesLoginModule.java:200)
| at org.jboss.security.auth.spi.UsersRolesLoginModule.initialize(UsersRolesLoginModule.java:127)
| ...
| 00:00:27,890 ERROR [AuthenticationManager] Couldn't log in.
| Message=Missing users.properties file.
|
And i can'nt perform login in my application.
Whence has appeared UsersRolesLoginModule, if I specified DatabaseServerLoginModule?
What i missed?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995594#3995594
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995594
19 years, 4 months
[JNDI/Naming/Network] - Global environment entries
by crnflke
I'm trying to get some form of global environment entry so that it can be seen in JNDI by everybody.
We want a series of bits of information to be stored that will be different depending on whether the server is in a dev/test environment and a live environment. In Tomcat we used server.xml Environment tags, but this doesn't seem to work in JBoss.
I found the JNDI Binding Manager, but this causes me problems too, as it produces the cryptic error message
ObjectName: jboss.tests:name=example1
State: FAILED
Reason: org.jboss.deployment.DeploymentException: No property editor for attribute: BindingsConfig; type=class org.jboss.naming.JNDIBindings
This is for the example that's in the documentation!
We're using jboss4.0.5 with the EJB3 extensions.
The only other way I can see to attack this problem is something like a custom bit of Java code that does the necessary work, or alternatively storing the properties in a database, but both of them seem like a bit of a waste.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995592#3995592
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995592
19 years, 4 months
[Management, JMX/JBoss] - Re: Listing all EJBs through JMX
by danieldestro
Hi dimitris,
I tried to use twiddle according to the examples (http://docs.jboss.org/jbossas/jboss4guide/r1/html/ch2.chapter.html), but I only got error messages, such as:
C:\jboss-4.0.3SP1\bin>twiddle query 'jboss:service=JNDIView'
| 13:48:38,772 ERROR [Twiddle] Command failure
| org.jboss.console.twiddle.command.CommandException: Unused argument: JNDIView'
| at org.jboss.console.twiddle.command.QueryCommand.processArguments(Query
| Command.java:104)
| at org.jboss.console.twiddle.command.QueryCommand.execute(QueryCommand.j
| ava:119)
| at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:290)
|
or even
C:\jboss-4.0.3SP1\bin>twiddle query '*:j2eeType=EjbModule,*'
| 13:50:26,810 ERROR [Twiddle] Command failure
| org.jboss.console.twiddle.command.CommandException: Unused argument: EjbModule
| at org.jboss.console.twiddle.command.QueryCommand.processArguments(Query
| Command.java:104)
| at org.jboss.console.twiddle.command.QueryCommand.execute(QueryCommand.j
| ava:119)
| at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:290)
I am using JBoss-4.0.3-SP1 and Java 5.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995590#3995590
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995590
19 years, 4 months