July 2009 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: current activity of execution

by camunda

Okay, but I want to persist the question: Why it is a problem to query the activity name then? I always can give an answer here (from the PVM/API perspective). It may be not that easy to interpret, but thats a different page... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243991#4243991 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243991

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ScheduledDeliveryTest::testDelayedRedeliveryDefault even

by clebert.suconic＠jboss.com

That failure happened on Oracle last time. and I believe our Oracle instance on Hudson is running on a VM. (what could make things run slower on the Oracle DB), causing timing issues. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243947#4243947 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243947

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - ScheduledDeliveryTest::testDelayedRedeliveryDefault eventual

by clebert.suconic＠jboss.com

there are two assertions on this test: assertTrue(time - now >= delay); | | // Hudson can introduce a large degree of indeterminism | assertTrue(time - now + ">" + (delay + 1000), time - now < delay + 1000); | | The second assertion can fail due to delays such as large Garbage Collections...etc. IMO we should just remove it, since the first assertion should be already sufficient for scheduled messages. that failure is also causing cascade failures due to something not being consumed or cleared up. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243945#4243945 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243945

16 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Paging and null persistence

by clebert.suconic＠jboss.com

This part of the doc: http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/... states that null-persistence means no-paging. The user has actually the possibility to configure null-persistence and still page messages on disk. Should I fix the documentation somehow, or should I remove the feature? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243943#4243943 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243943

16 years, 8 months

1
0
0 / 0

[Design of JBossXB] - Re: @XmlType.propOrder required with no schema sequence

by thomas.diesler＠jboss.com

you might be pleased to hear that I successfully moved BP parsing to XB annotations ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243779#4243779 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243779

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Timeout when using SOAP-configuration for registry

by admac

I'm sorry. I wanted to say I configured the jUDDI-Registry in jBoss ESB to use SOAP-based communication like described in the Registry Guide. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243749#4243749 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243749

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Timeout when using SOAP-configuration for registry

by beve

anonymous wrote : I'm using jbossesb-server-4.5.GA. when I try to configure it to use the SOAP configuration, the server doesn't start any more. What do you mean you have configured the server to use the SOAP configuration? BTW this is the design forum which is intended for discussing design. Please use the user forum for these kinds of questions: http://www.jboss.org/index.html?module=bb&op=viewforum&f=246 Regards, /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243738#4243738 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243738

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Timeout when using SOAP-configuration for registry

by admac

Hi, I'm using jbossesb-server-4.5.GA. when I try to configure it to use the SOAP configuration, the server doesn't start any more. Using the Loglevel DEBUG I can see that the internal AvailabilityExecutor needs so much time that the overall timeout allowed for starting is reached. When I try the local configuration everything works fine. Here's the result of the console in debug modus. 14:43:38,228 DEBUG [ServiceController] starting service jboss.esb:service=MessageStoreDatabaseInitializer 14:43:38,228 DEBUG [DatabaseInitializer] Starting jboss.esb:service=MessageStoreDatabaseInitializer 14:43:38,337 INFO [DatabaseInitializer] java:/JBossESBDS datasource is already initialized 14:43:38,337 DEBUG [DatabaseInitializer] Started jboss.esb:service=MessageStoreDatabaseInitializer 14:43:38,337 DEBUG [ServiceController] Starting dependent components for: jboss.esb:service=MessageStoreDatabaseInitializer dependent components: [ObjectName: jboss.esb:deployment=jbossesb.esb State: CREATED I Depend On: jboss.esb:service=MessageStoreDatabaseInitializer jboss.esb.destination:service=Queue,name=OperationsCollectorQueue jboss.esb.destination:service=Queue,name=DataCollectorQueue jboss.esb.destination:service=Queue,name=DeadMessageQueue jboss.jca:service=DataSourceBinding,name=JBossESBDS jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue ] 14:43:38,337 DEBUG [ServiceController] starting service jboss.esb:deployment=jbossesb.esb 14:43:38,337 DEBUG [JBoss4ESBDeployment] Starting jboss.esb:deployment=jbossesb.esb 14:43:38,648 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000 14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/OperationsResultCollectorQueue> will be picked up by listener 14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000 14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/OperationsCollectorQueue> will be picked up by listener 14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000 14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/DataCollectorQueue> will be picked up by listener 14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000 14:43:38,679 DEBUG [ListenerUtil] No value specified for message-selector attribute - All messages in queue <queue/DeadMessageQueue> will be picked up by listener 14:43:38,679 DEBUG [AbstractManagedLifecycle] terminationPeriod value 60000 14:43:38,710 DEBUG [ActionProcessingPipeline] Using mep: OneWay, oneWay: true, defaultProcessing: false 14:43:38,725 DEBUG [LifecycleResource] Creating resource using factory: org.jboss.soa.esb.listeners.message.ServiceMessageCounterLifecycleResource$LifecycleServiceMessageCounterFactory@1a4f2fd with identity ID-0 14:43:38,725 DEBUG [ActionProcessingPipeline] Registering action class org.jboss.soa.esb.actions.MessageRedeliverer 14:43:38,741 DEBUG [ActionProcessingPipeline] Using normal action pipeline processor for org.jboss.soa.esb.actions.MessageRedeliverer 14:43:38,756 DEBUG [ActionProcessingPipeline] SecurityContextPropagator in use for service 'RedeliverService' is 'org.jboss.internal.soa.esb.services.security.JBossASContextPropagator' 14:43:38,772 DEBUG [ConnectionManagerFactory] Going to load org.jboss.internal.soa.esb.persistence.manager.J2eeConnectionManager 14:43:38,772 INFO [J2eeConnectionManager] initializing... 14:43:38,788 DEBUG [MessageRedeliverer] MessagePersister started with classification=null and message-store-class=org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl@b2311b 14:43:38,803 DEBUG [ActionProcessingPipeline] Using mep: OneWay, oneWay: true, defaultProcessing: false 14:43:38,803 DEBUG [ActionProcessingPipeline] Registering action class org.jboss.soa.esb.monitoring.client.InvokerAction 14:43:38,803 DEBUG [ActionProcessingPipeline] Using overridden action lifecycle processor for org.jboss.soa.esb.monitoring.client.InvokerAction 14:43:38,803 DEBUG [ActionProcessingPipeline] SecurityContextPropagator in use for service 'InvokerService' is 'org.jboss.internal.soa.esb.services.security.JBossASContextPropagator' 14:43:38,803 DEBUG [RegistryUtil] Registering < InvokerService, JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/OperationsResultCollectorQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/> > ] > 14:43:38,896 DEBUG [RepositoryClassLoader] Added url: file:/D:/Server/jbossesb-server-4.5.GA/server/esb/tmp/aopdynclasses/ucl8284506718732261677/?dynamic=true, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@19bd735{ url=file:/D:/Server/jbossesb-server-4.5.GA/server/esb/deploy/jbossesb.sar/ ,addedOrder=9} 14:43:40,326 DEBUG [AvailabilityExecutor] Running Availability Scan... 14:43:40,374 DEBUG [AvailabilityExecutor] Built availability report for [44] resources with a size of [803] bytes in [48]ms 14:44:40,165 DEBUG [AvailabilityExecutor] Running Availability Scan... 14:44:40,166 DEBUG [AvailabilityExecutor] Built availability report for [1] resources with a size of [112] bytes in [1]ms 14:45:39,973 DEBUG [AvailabilityExecutor] Running Availability Scan... 14:45:39,973 DEBUG [AvailabilityExecutor] Built availability report for [1] resources with a size of [112] bytes in [0]ms Can anyone tell me what I do wrong? Thanks a lot, Marcus View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243727#4243727 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243727

16 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Problems with Scout/jUDDI

by admac

I have a problem using the scout.jar file. I registered an external web service (using "http" as access point type and the WSDL-URL as access point url) to juddi using the UDDI Browser. After that I started the ESB and got a class cast exception when trying to find the external service. I figured out that there's a problem in the current scout.jar which was solved in the current version of scout (scout-1.0.jar). I replaced the jar-file and started the ESB again and the there was no error. For testing purposes I then deployed the HelloWorld example and got an error that the Service could not be found in the registry. org.jboss.soa.esb.services.registry.RegistryException: No such EPR found for service with name = SimpleListener and EPR=JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/quickstart_helloesb_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.unRegisterEPR(JAXRRegistryImpl.java:214) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) When I look in the registry database I can see the service is being "deployed" in the database properly. The only difference is that the portReference in the table BINDING_TEMPLATE has a prefix containing the namespace: <wsa:From xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"> Does the current implementation of scout behave differently from the old one in finding internal and external services? Thanks in advance, Marcus View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243724#4243724 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243724

16 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Uninstall OnDemand context if there are no more dependen

by alesj

"kabir.khan(a)jboss.com" wrote : Sure, I can change it. There are several other examples of this though, or are they subtly different? | Ah, you can call those my laziness :-), as I seem to miss them when I was porting states checking to CSM. You can fix that, or I will eventually. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243712#4243712 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243712

16 years, 8 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-dev-forums July 2009