[jboss-user] [Beginner's Corner] - Re: Hot deploy problem with properties file
Roelof K [http://community.jboss.org/people/happy-together] created the discussion "Re: Hot deploy problem with properties file" To view the discussion, visit: http://community.jboss.org/message/562678#562678 -- My problem is solved. It was an error in my code. (A static method jeopardized i18n) -- Reply to this message by going to Community [http://community.jboss.org/message/562678#562678] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
Re: [jboss-user] [Beginner's Corner] - Hot deploy problem with properties file
Roelof K [http://community.jboss.org/people/happy-together] replied to the discussion "Hot deploy problem with properties file" To view the discussion, visit: http://community.jboss.org/message/559334#559334 -- Hi, I'm facing the same problem. (i18n + hot deployment on dev works, i18n + farming/clustering + hot deployment on prod does not) Any developments? Is there a workaround? Any hints or tips would be appreciated. Thanks, Roelof -- Reply to this message by going to Community [http://community.jboss.org/message/559334#559334] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075] ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: Message expiration on JBM 1.4.{4, 5}
hi howard, the clients are not MDB's. just normal subscribers running in the same VM. regards roelof View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261179#4261179 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261179 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: IllegalStateException: Cannot find counter with name
i did a bit more investigation into the problem: 1. the jbm_postoffice table contain the correct information 2. the ServerPeer on each node return the correct counters for the subscriber connected to that node. it does not return the counters for the subscribers on the other node. after a node restart or topic stop/start the problem goes away. 3. i added an additional trace in MessageCounterManager::registerMessageCounter. the counter is added to the HashMap. 4. the problem is not resolved by having the subscribers disconnect and re-connect to the other node in the cluster. from the look of things the problem seems to indicate a synchronization problem, i.e. the registering of counters is not propagated correctly in the cluster? is there existing functionality to perform that synchronization? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260228#4260228 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260228 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - Re: IllegalStateException: Cannot find counter with name
hi howard, thanx for the quick response. here follows the stacktrace: 2009-10-13 15:02:15,155 ERROR [org.jboss.messaging.util.ExceptionUtil] [http-127.0.0.1-8080-3] Topic[/topic/SMS] listMessagesNonDurableSub | java.lang.IllegalStateException: Cannot find counter with name Subscription.superuser.superuser-SMS | at org.jboss.jms.server.destination.ManagedTopic.getMessageCounters(ManagedTopic.java:173) | at org.jboss.jms.server.destination.TopicService.getMessageCounters(TopicService.java:559) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) | at java.lang.reflect.Method.invoke(Method.java:616) | at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:99) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:197) | at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:362) | at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:556) | at org.jboss.jmx.adaptor.control.Server.getMBeanAttributeResultInfo(Server.java:144) | at org.apache.jsp.inspectMBean_jsp._jspService(inspectMBean_jsp.java:195) | at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) | at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) | at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) | at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445) | at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:77) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:856) | at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:566) | at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508) | at java.lang.Thread.run(Thread.java:636) View the original post : http://www.jboss.org/index
[jboss-user] [JBoss Messaging Users] - Message expiration on JBM 1.4.{4, 5}
hi everyone, the following test were performed on a clustered setup of JBoss/JBM: 1. the ExpiryQueue is clustered 2. All messages are submitted to a clustered topic 3. Messages expire after 10s. 4. Two durable subscribers subscribe for the messages. 5. Subscriber1 is connected to node1 6. Subscriber2 is connected to node2 7. Subscriber2 disconnects for a period of time exceeding 10s. 8. Subscriber2 re-connects to node2 9. In the server.log of node1 the following messages appear: ServerSessionEndpoint] No expiry queue has been configured so removing expired Reference[20568905987098193]:RELIABLE each topic is deployed with JBoss startup and have both a DLQ and ExpiryQueue set, e.g.: | jboss.messaging:service=ServerPeer | jboss.messaging:service=PostOffice | true | jboss.messaging.destination:service=Queue,name=DLQ | jboss.messaging.destination:service=Queue,name=ExpiryQueue | 75000 | the message counters for the expiry queue does not reflect the correct number of messages that were expired. are these types of messages normal? when running on a single node these messages are not printed, only when running in a cluster. all help appreciated. regards, roelof. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260097#4260097 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260097 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging Users] - IllegalStateException: Cannot find counter with name
hi all, we are running JBoss Messaging 1.4.4 with JBoss 4.2.3. all topics/queues are clustered. when connecting durable subscribers in the cluster, user1 to node 1 and user2 to node 2, we receive the 'IllegalStateException: Cannot find counter with name' exception when trying to view the message counters. the ServerPeer mbean also has no knowledge of the subscriptions. the topic mbean's MessageCounters attribute contain a value of javax.management.RuntimeMBeanException. the AllSubscriptionsCount does contain the correct count, 2 in this case. only when the topic is stop/start does the error disappear. does anyone have any idea on how to overcome this? i've also upgraded to jbm 1.4.5, but this did not solve anything. i can also not reproduce this error when running on a single node, only when running a clustered setup. any help much appreciated. regards roelof. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260089#4260089 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260089 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: Singleton mbean
"josey" wrote : | Did you ever find a solution to this problem? no, unfortunately not. in the end we upgraded to 4.2.3jboss 5.0 CR2 had too many other issues as well. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232104#4232104 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4232104 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: jboss 5.0 and ejb 2.1 deployments
"jaikiran" wrote : Please post the contents of your JNDI tree. The jndi tree: | java: Namespace | | +- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl) | +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource) | +- policyRegistration (class: org.jboss.security.plugins.JBossPolicyRegistration) | +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory) | +- comp (class: javax.namingMain.Context) | +- JBossCorbaPOA (class: org.omg.PortableServer.POA) | +- JBossCorbaORB (class: org.omg.CORBA.ORB) | +- TransactionPropagationContextExporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager) | +- TransactionManager (class: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate) | +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- timedCacheFactory (class: javax.naming.Context) | Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy | +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- jaas (class: javax.naming.Context) | | +- HsqlDbRealm (class: org.jboss.security.plugins.SecurityDomainContext) | +- JBossCorbaInterfaceRepositoryPOA (class: org.omg.PortableServer.POA) | +- JBossCorbaNaming (class: org.omg.CosNaming.NamingContextExt) | +- TransactionPropagationContextImporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager) | +- CacheManager (class: org.jboss.ha.cachemanager.CacheManager) | +- Mail (class: javax.mail.Session) | +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- USA3_ConfigDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource) | +- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple) | +- DefaultJMSProvider (class: org.jboss.jms.jndi.JNDIProviderAdapter) | +- securityManagement (class: org.jboss.security.integration.JNDIBasedSecurityManagement) | | Global JNDI Namespace | | +- UserTransactionSessionFactory (proxy: $Proxy150 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory) | +- jmx (class: org.jnp.interfaces.NamingContext) | | +- rmi (class: org.jnp.interfaces.NamingContext) | | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef) | | +- invoker (class: org.jnp.interfaces.NamingContext) | | | +- RMIAdaptor (proxy: $Proxy149 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt) | +- queue (class: org.jnp.interfaces.NamingContext) | | +- DLQ (class: org.jboss.jms.destination.JBossQueue) | | +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue) | +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory) | +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- HASessionState (class: org.jnp.interfaces.NamingContext) | | +- Default (class: org.jboss.ha.hasessionstate.server.HASessionStateImpl) | +- console (class: org.jnp.interfaces.NamingContext) | | +- PluginManager (proxy: $Proxy152 implements interface org.jboss.console.manager.PluginManagerMBean) | +- HAPartition (class: org.jnp.interfaces.NamingContext) | | +- DefaultPartition (class: org.jboss.ha.framework.server.ClusterPartition) | +- topic (class: org.jnp.interfaces.NamingContext) | +- JAXR (class: org.apache.ws.scout.registry.ConnectionFactoryImpl) | +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory) | +- invokers (class: org.jnp.interfaces.NamingContext) | | +- segfault.localdomain (class: org.jnp.interfaces.NamingContext) | | | +- iiop (class: org.jboss.invocation.iiop.IIOPInvoker) | +- TomcatAuthenticators (class: java.util.Properties) | +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) | +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction) | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180479#4180479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180479 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Re: jboss 5.0 and ejb 2.1 deployments
"jaikiran" wrote : Which exact version of JBoss-5.0 do you use? | 08:14:45,650 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171046) | "jaikiran" wrote : | And which version of Java? Please post the contents of your JNDI tree. Also, do you have a jboss.xml where you specify the JNDI names for your EJBs? If yes, then post that too. | | 08:14:50,553 INFO [ServerInfo] Java version: 1.5.0_12,Sun Microsystems Inc. | 08:14:50,553 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_12-b04,Sun Microsystems Inc. | 08:14:50,554 INFO [ServerInfo] OS-System: Linux 2.6.23.17-88.fc7,amd64 | i cannot provide a jndi tree at this stage as trying to access to the jmx-console fails. during this time jboss is also running at 100% cpu. the relevant entry from the jboss.xml file: | | CommandLog | mtn_usa/commandlog/CommandLog | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180477#4180477 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180477 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - jboss 5.0 and ejb 2.1 deployments
hi all, in the process of migrating to jboss 5.0 i 've run into the following when deploying ejb 2.1 beans (entities and stateless session). the console prints several message like this: 10:38:39,554 INFO [EjbDeployer] installing bean: ejb/mtnusa_stats-6.7-SNAPSHOT.jar#CommandLog,uid1092787950 10:38:39,554 INFO [EjbDeployer] with dependencies: 10:38:39,554 INFO [EjbDeployer] and supplies: 10:38:39,554 INFO [EjbDeployer]jndi:mtn_usa/commandlog/CommandLog 10:38:39,554 INFO [EjbDeployer]jndi:CommandLog but; viewing the jndi tree via the jmx-console's JNDIView does not reflect the above mappings. the lookups in our code also fails miserably, e.g.: javax.naming.NameNotFoundException: mtn_usa not bound any idea on how to debug this? is there anything specific that needs to be done? rewriting all the beans as ejb3 compliant beans is not yet possible at this stage. anything else i can try? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180224#4180224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180224 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - EJBDeployer + NotificationBroadcaster interface
hi all, in our application we subscribe to notifications from EJBDeployer. this is used to trigger additional, dynamic deployments as certain parts of the system are deployed. in the process of upgrading from 4.0.2 to 5.0.0, i've run in to the following error: java.lang.IllegalArgumentException: The MBean jboss.ejb:service=EJBDeployer exists but does not implement the NotificationBroadcaster interface are there any other components that will/may provide the relevant information? any help appreciated... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180208#4180208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180208 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration & DEPLOYMENT] - Singleton mbean
hi we are currently running a very old version of jboss (4.0.2). in the process of migrating/upgrading to jboss 5.0 i've run into a problem related to a Singleton mbean. the error is: java.lang.IllegalStateException: HAPartition property must be set before starting HAServiceMBeanSupport the relevant descriptor: | | | HAPartition | | | | | | | | mtn_usa.system:service=ConnectionController | | startSingleton | stopSingleton | | i also looked at the example in the docs: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta500/html/ch18s11s02.html that unfortunately resulted in the same error. has anyone run into this? any idea what can be done to resolve the problem? thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4180206#4180206 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4180206 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
