July 2008 - jboss-user - Jboss List Archives

[JBoss Messaging] - Re: Message Consumer fails when using messageSelector

by mbreuer

Solved! The problematic code was instantiated several times, so at least one jms-session per request was created. Seems this blocks the queue for a while, because the other (old) session processes the request and puts it back (no consumer) after a specific period. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162268#4162268 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162268

17 years, 9 months

1
0
0 / 0

[JBoss Messaging] - Messages was not delivered

by slogger

Additional info: I am using jms resource adapter and External JNDI on client: | | <connection-factories> | |  |  |  | |  | <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.messaging:service=JMSProviderLoader,name=JMSProviderRemote"> | <attribute name="ProviderName">RemoteJMSProvider</attribute> | <attribute name="ProviderAdapterClass"> | org.jboss.jms.jndi.JNDIProviderAdapter | </attribute> |  | <attribute name="FactoryRef">XAConnectionFactory</attribute> |  | <attribute name="QueueFactoryRef">XAConnectionFactory</attribute> |  | <attribute name="TopicFactoryRef">XAConnectionFactory</attribute> |  | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=10.0.0.166:1199 | </attribute> | </mbean> | | <mbean code="org.jboss.jms.asf.ServerSessionPoolLoader" | name="jboss.messaging:service=ServerSessionPoolMBean,name=StdJMSPool"> | <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends> | <attribute name="PoolName">StdJMSPool</attribute> | <attribute name="PoolFactoryClass"> | org.jboss.jms.asf.StdServerSessionPoolFactory | </attribute> | </mbean> | |  | <tx-connection-factory> | <jndi-name>JmsXA</jndi-name> | <xa-transaction/> | <rar-name>jms-ra.rar</rar-name> | <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> | <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> | <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/RemoteJMSProvider</config-property> | <min-pool-size>10</min-pool-size> | <max-pool-size>50</max-pool-size> | <application-managed-security/> | </tx-connection-factory> | | <mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=remoteJndi"> | <attribute name="JndiName">remoteJndi</attribute> | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://10.0.0.166:1199 | </attribute> | <attribute name="InitialContext">javax.naming.InitialContext</attribute> | <depends>jboss:service=Naming</depends> | </mbean> | | </connection-factories> | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162267#4162267 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162267

17 years, 9 months

1
0
0 / 0

[JBoss Messaging] - Exception when starten 2nd node

by mbreuer

After migration from JBossMQ to JBossMessaging i get an exception when starting the 2nd cluster node. 2008-07-03 10:40:05,011 66685 ERROR [org.jboss.messaging.util.ExceptionUtil] (main:) SessionEndpoint[12-n9fx37if-1-oy9w37if-9w9nuy-m3g4o4c5] cre | ateConsumerDelegate [22-t9fx37if-1-oy9w37if-9w9nuy-m3g4o4c5] | javax.jms.InvalidDestinationException: No such destination: JBossQueue[intern.reporting.event] has it been deployed? | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(ServerSessionEndpoint.java:1838) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:252) | at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop( | SessionAdvised.java:94) | at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsu | merDelegate_8721389917985689973.java) | 2008-07-03 10:47:18,428 500102 ERROR [com.materna.buc.macs.comp.dm.svc.email.EMailReceiver] (Thread-55:) DeliveryService.EMAIL.test.email.0,serg | el] -103011 com.materna.buc.macs.exception.MacsJmsException: javax.jms.JMSException: There is no administratively defined queue with name:Deliv | eryService.EMAIL.test.email.0 -103011 | com.materna.buc.macs.exception.MacsJmsException: javax.jms.JMSException: There is no administratively defined queue with name:DeliveryService.EM | AIL.test.email.0 -103011 | at com.materna.buc.macs.basics.jms.MacsJmsObjects.setQueueSession(MacsJmsObjects.java:104) | at com.materna.buc.macs.basics.jms.MacsJmsClient.getQueueObjectsEx(MacsJmsClient.java:351) | at com.materna.buc.macs.basics.jms.MacsJmsClient.getQueueObjects(MacsJmsClient.java:413) | at com.materna.buc.macs.comp.dm.svc.BaseJmsReceiver.reconnectToJMS(BaseJmsReceiver.java:103) | at com.materna.buc.macs.comp.dm.svc.BaseJmsReceiver.receiveNextMsg(BaseJmsReceiver.java:187) | at com.materna.buc.macs.comp.dm.svc.email.EMailReceiver.run(EMailReceiver.java:240) | at java.lang.Thread.run(Thread.java:595) | It looks like a problem with the queues. The queues are deployed to deploy-hasingleton and work an the first (master) node. The 2nd node seems not to find these queue, even they are deployed to its deploy-hasingleton. What wrong? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162264#4162264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162264

17 years, 9 months

1
0
0 / 0

[JBoss Messaging] - Messages was not delivered

by slogger

Hi gurus!!! I have two machines with JBOSS 4.2.1. OS Windows XP jdk 1.5 (build 1.5.0_13-b05) JBMessaging 1.4.0 SP3 JBRemoting 2.2.2 SP7 JMS provider was installed on only one machine and uses RDMS Oracle 10.2.0. The second machine is just remote client. Message delivery was organized synchronously periodically in EJBTimer (QueueReceiver::receive(timeout)) I am using Bean Managed Transaction and transacted queue session (connection.createQueueSession(true, 0)) Closing connection calling in finally block. I am testing work stability under unstable network connection and unplugging network cable from jms cleint's machine periodically After some time I get message on console (as an example): 2008-07-03 09:57:14,437 WARN [org.jboss.jms.client.container.ClientConsumer] Timed out waiting for last delivery 4 got -1 This message appears periodically in closing connection time (in my opinion). After some time this message is not appeared, but meesages stay in queue table (jbm_msg) and is not delivering at all. During of this timer continue work successfully and periodically creates session, attempts to receive messages and close connection. There are not error messages on console. A versions of JBMessaging and JBRemoting is identical on jms-provider and client machines. After restart Jboss on client machine or Jboss whith Jms-provider the message delivering was started succesfully. What do this message means and How can I resolve this problem? Thanks in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162263#4162263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162263

17 years, 9 months

1
0
0 / 0

[JBoss Portal] - actionURL in jboss-portletcontainer-2.0.0

by terroene

Hello again, sorry, but another question concerning Portlet-Container 2.0: What am I doing wrong with the actionURL??? This is a jsp for a portlet in view-mode, submitting the form causes the exception below. The jsp: | <%@page contentType="text/html"%> | <%@page pageEncoding="UTF-8"%> | | <%@ page import="javax.portlet.*"%> | <%@ taglib uri="http://java.sun.com/portlet_2_0" prefix="portlet"%> | | <portlet:defineObjects/> | | | <form action="<portlet:actionURL/>" method="post"> | <input type="text" name="username" value="" /> | <input type="text" name="userpassword" value="" /> | <input type="submit" value="OK" /> | </form> | The exception (Index is the jsp containing the portlet!): | 10:29:03,976 ERROR [[Index]] Servlet.service() for servlet Index threw exception | java.lang.NullPointerException | at org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:630) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:4 | 74) | at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) | at org.jboss.portal.portlet.portal.jsp.ControllerFilter.doFilter(ControllerFilter.java:1 | 20) | at org.jboss.portal.portlet.portal.jsp.ControllerFilter.doFilter(ControllerFilter.java:9 | 1) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCha | in.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java: | 206) | at org.jboss.portal.portlet.portal.ErrorHandlingFilter.doFilter(ErrorHandlingFilter.java | :61) | at org.jboss.portal.portlet.portal.ErrorHandlingFilter.doFilter(ErrorHandlingFilter.java | :53) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterCha | in.java:235) | 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(ApplicationFilterCha | in.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(SecurityAssociationValv | e.java:179) | 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.j | ava:157) | 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.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protoco | l.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:595) | | Thanks and best regards, rene View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162262#4162262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162262

17 years, 9 months

1
0
0 / 0

[JBossWS] - Configuring WS-Eventing on JBossWS2.0.3

by smjain

Hi, I am using JBoss Application server 4.2.2 and JBoss WS 2.0.3. I am looking for some good book/documentation to start from scratch on WS-Eventing. We have a legacy application which acts as a Event Source. We already have connectors in java to recieve those events. I am looking out for detailed steps as to set up a basic service first and make it work. I tried with the example/s given on JBoss site but it does not work for me. I will also be interested in knowing the interfaces for SubscriptionManager if I want to take a code first approach.. Will that be possible Regards Shashank View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162261#4162261 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162261

17 years, 9 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: ClassCastException on JNDI context.Lookup();

by dlarosa11

I am having the same problem. I've seen this discussion all over the place dating back to 2002. My understanding is that there is no bug in jboss, it's just the way it is. However, I'd love to see a discussion of a workaround. The only one I've seen is to bundle everything in the same ear. In our situation, this is not possible. We have a server app which exposes our bean, and we want our customers to be able to create their own clients of it. There is no way we are going to get their apps in our ear. We need to be able to hot deploy our application and not have all the clients get a subsequent ClassCastException when doing a jndi lookup of our bean. Is the solution to redeploy all the clients after the server app with our bean is redeployed? I obviously can catch the exception, but I'm wondering what do I do about it once it's caught. Is there any way I can recover in my client app once I get this CastClassException when doing the jndi lookup? Can I force a reload of something so that I don't have to restart the client? Here's the diff of the JNDIView output of the relevant bean in our situation. Proxy90 is before the hot deploy of our server app and bean. Proxy145 is from after. Thanks for any and all help. < | +- local (proxy: $Proxy90 implements interface com.perimeter.anyswitch.IAnySwitchLocal,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject) | | --- | | > | +- local (proxy: $Proxy145 implements interface com.perimeter.anyswitch.IAnySwitchLocal,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject) | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162257#4162257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162257

17 years, 9 months

1
0
0 / 0

[Clustering/JBoss] - Clusterin JBoss 4.0.5 Default partition repeated in the same

by nimind

Hi, I am using the All profile, to which I have made the changes at http://wiki.jboss.org/wiki/UsingMod_jk1.2WithJBoss?action=e&windowstate=n... This includes adding the Code: jvmRoute="node1" and Code: jvmRoute="node2" to the 2 instances, setting Code: true and ensuring that AJP connector is uncommented. I only modify two files: jbosweb-tomcat50.sar/server.xml and jbosweb-tomcat50.sar/META-INF/jboss-service.xml with jvmRoute and UseJK (only that). Yet when I start up the 2 cluster members. I allowed the first server to completely start then started the second server. Nothing is deployed. When i start the second server, it begins to add members to cluster with the same ip (second server ip) and differents ports. It repeats and i got 55 members with the same ip (172.19.131.63). log second server: | ------------------------------------------------------- | GMS: address is 172.19.131.63:1840 | ------------------------------------------------------- | 2008-07-03 07:43:37,140 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:43:37,140 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:43:37,140 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:43:38,640 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] New cluster view for partition DefaultPartition (id: 7, delta: 1) : [127.0.0.1:1099, 172.19.131.32:1099, 172.19.131.32:1099, 127.0.0.1:1099, 127.0.0.1:1099, 127.0.0.1:1099, 127.0.0.1:1099, 127.0.0.1:1099] | 2008-07-03 07:43:38,640 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] membership changed from 7 to 8 | 2008-07-03 07:43:38,640 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] Begin notifyListeners, viewID: 7 | 2008-07-03 07:43:38,640 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] I am (127.0.0.1:1099) received membershipChanged event: | 2008-07-03 07:43:38,640 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] Dead members: 0 ([]) | 2008-07-03 07:43:38,640 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] New Members : 0 ([]) | 2008-07-03 07:43:38,640 INFO [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] All Members : 8 ([127.0.0.1:1099, 172.19.131.32:1099, 172.19.131.32:1099, 127.0.0.1:1099, 127.0.0.1:1099, 127.0.0.1:1099, 127.0.0.1:1099, 127.0.0.1:1099]) | 2008-07-03 07:43:38,640 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] End notifyListeners, viewID: 7 | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] setState called | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] setState for DistributedState | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] setState for HASessionStateTransfer | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.hasessionstate.server.HASessionStateImpl./HASessionState/Default] Receiving state of HASessionState | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] setState for HAJNDI | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.jndi.TreeHead] registerRPCHandler | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] setState for DistributedReplicantManager | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] received a state of 1609 bytes; expanded memory by 34200 bytes (used memory before: 42059216, used memory after: 42093416) | 2008-07-03 07:43:38,671 DEBUG [org.jboss.ha.framework.server.DistributedReplicantManagerImpl.DefaultPartition] DRM: Sleeping before re-publishing for 50ms just in case | 2008-07-03 07:43:38,734 DEBUG [org.jboss.ha.singleton.HASingletonController] partitionTopologyChanged, isElectedNewMaster=false, isMasterNode=false, viewID=-439979114 | 2008-07-03 07:43:38,734 DEBUG [org.jboss.ha.framework.server.HARMIServerImpl$RefreshProxiesHATarget] replicantsChanged 'HAJNDI' to 8 (intra-view id: -439979114) | 2008-07-03 07:43:39,687 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:43:41,781 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:43:41,781 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:43:43,843 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:43:43,843 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:43:48,406 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:43:48,406 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:43:48,406 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:43:48,406 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:43:50,062 INFO [org.jboss.cache.TreeCache] viewAccepted(): [172.19.131.84:4568|12] [172.19.131.84:4568, 172.19.131.32:1179, 172.19.131.63:1761, 172.19.131.32:1360, 172.19.131.32:1491, 172.19.131.32:1533, 172.19.131.32:1577, 172.19.131.32:1594] | 2008-07-03 07:43:52,171 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:43:52,171 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:43:52,171 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:43:52,171 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:43:57,062 INFO [org.jboss.cache.TreeCache] viewAccepted(): [172.19.131.84:4568|13] [172.19.131.84:4568, 172.19.131.32:1179, 172.19.131.63:1761, 172.19.131.32:1360, 172.19.131.32:1491, 172.19.131.32:1533, 172.19.131.32:1577, 172.19.131.32:1594] | 2008-07-03 07:43:57,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:43:57,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:43:57,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:43:57,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:43:59,843 INFO [STDOUT] | ------------------------------------------------------- | GMS: address is 172.19.131.63:1849 | ------------------------------------------------------- | 2008-07-03 07:44:02,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:02,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:02,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:02,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:03,937 INFO [org.jboss.cache.TreeCache] viewAccepted(): [172.19.131.84:4581|7] [172.19.131.84:4581, 172.19.131.32:1297, 172.19.131.32:1482, 172.19.131.32:1518, 172.19.131.32:1541, 172.19.131.63:1803, 172.19.131.63:1829, 172.19.131.63:1849] | 2008-07-03 07:44:03,953 WARN [org.jgroups.protocols.pbcast.STATE_TRANSFER] state received from 172.19.131.84:4581 is null, will return null state to application | 2008-07-03 07:44:03,953 DEBUG [org.jboss.cache.TreeCache] transferred state is null (may be first member in cluster) | 2008-07-03 07:44:05,906 INFO [STDOUT] | ------------------------------------------------------- | GMS: address is 172.19.131.63:1857 | ------------------------------------------------------- | 2008-07-03 07:44:07,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:07,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:07,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:07,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:10,953 WARN [org.jgroups.protocols.pbcast.GMS] join(172.19.131.63:1857) sent to 172.19.131.84:4577 timed out, retrying | 2008-07-03 07:44:12,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:12,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:12,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:12,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:12,578 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - first pass <jue, 3 jul 2008 07:44:12> | 2008-07-03 07:44:12,578 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] StatusModule: first pass | 2008-07-03 07:44:12,578 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass | 2008-07-03 07:44:12,578 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass | 2008-07-03 07:44:15,015 INFO [org.jboss.cache.TreeCache] viewAccepted(): [172.19.131.84:4577|11] [172.19.131.84:4577, 172.19.131.32:1261, 172.19.131.32:1473, 172.19.131.32:1510, 172.19.131.63:1799, 172.19.131.63:1825, 172.19.131.63:1857] | 2008-07-03 07:44:15,046 WARN [org.jgroups.protocols.pbcast.STATE_TRANSFER] state received from 172.19.131.84:4577 is null, will return null state to application | 2008-07-03 07:44:15,046 DEBUG [org.jboss.cache.TreeCache] transferred state is null (may be first member in cluster) | 2008-07-03 07:44:17,250 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:17,265 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:17,265 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:17,265 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:20,046 INFO [org.jboss.cache.TreeCache] viewAccepted(): [172.19.131.84:4577|12] [172.19.131.84:4577, 172.19.131.32:1261, 172.19.131.32:1473, 172.19.131.32:1510, 172.19.131.63:1799, 172.19.131.63:1825, 172.19.131.63:1857] | 2008-07-03 07:44:22,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:22,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:22,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:22,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:22,578 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <jue, 3 jul 2008 07:44:22> | 2008-07-03 07:44:22,578 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass | 2008-07-03 07:44:22,578 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass | 2008-07-03 07:44:22,578 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass | 2008-07-03 07:44:27,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:27,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:27,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:27,156 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:32,765 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:32,765 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:32,765 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:32,765 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | 2008-07-03 07:44:37,203 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1781 | 2008-07-03 07:44:37,203 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1811 | 2008-07-03 07:44:37,203 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1767 | 2008-07-03 07:44:37,203 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] Suspected member: 172.19.131.63:1788 | Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162251#4162251 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162251

17 years, 9 months

1
0
0 / 0

[JBoss jBPM] - first steps with JBPM...

by ilyane

Hello, I am just starting in the workflow area, I can realize that it s so hard, above all when we are using tools such as open source. I have choosen to work with jbpm because i can say that it s among the more used. I have follow this link http://docs.jboss.org/tools/2.0.0.GA/jbpm/en/html/index.html and i read the information given, but it s not so concrete things for me. I need to make a workflow management tool in order to manage the process job of a trade company. I finished to modelise my process the designer in associated to this software. Now i need someone who can help me for the next step. How to execute my workflow so as to see that everything is ok? What are the differents steps to follow? how to associate it to an application? and above all, if it s necessary to have a java application or it s possible to communicate with a php application???? I am really desperate :'( thanks in advance for your help View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162248#4162248 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162248

17 years, 9 months

1
0
0 / 0

[JBoss Portal] - Re: Ldap Configuration With Jboss Portal

by amitdon19

Hi All, I made changes in my C:\jboss-portal-2.6.5.SP1\server\default\deploy\jboss-portal.sar\conf\login-config.xml file where <application-policy name="portal">.............</application-policy name="portal"> and now I am able to get log in with available credentials in Ldap but again i come up with another problem i.e. I am unable to create new user through JBoss Portal Registration Page.... Please refer my last post. Please can anybody help me out??? I'll be thankful to you guys. <application-policy name="portal"> | <authentication> | |  | <login-module code="org.jboss.portal.identity.auth.IdentityLoginModule" flag="required"> | <module-option name="unauthenticatedIdentity">guest</module-option> | <module-option name="userModuleJNDIName">java:/portal/UserModule</module-option> | <module-option name="roleModuleJNDIName">java:/portal/RoleModule</module-option> | <module-option name="userProfileModuleJNDIName">java:/portal/UserProfileModule</module-option> | <module-option name="membershipModuleJNDIName">java:/portal/MembershipModule</module-option> | <module-option name="additionalRole">Authenticated</module-option> | <module-option name="password-stacking">useFirstPass</module-option> | </login-module> | |  |  |  | |  |  | |  |  |  | | </authentication> | </application-policy> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162246#4162246 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162246

17 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2008