[JBossWS] - Does not recognize xsd:datetime
by uannight
I have a webservice with integer,string and Date, the wsdl generate a xsd:datetime but when i am trying to launch the webservice i am having this error.
arguments java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang. String,java.lang.String,java.lang.String,java.util.GregorianCalendar. The arguments do not match the signature.; nested exception is: java.lang.IllegalArgumentException: ComponentManager:getService service alarm service not found!
This error is changing the Date by Calendar (both have the same error). If I remove the element with Date or Calendar the webservice is working.
This is the wsdl:
<?xml version="1.0" encoding="UTF-8"?>
| <wsdl:definitions targetNamespace="http://ws.alarm.services.mmplat"
| xmlns:apachesoap="http://xml.apache.org/xml-soap"
| xmlns:impl="http://ws.alarm.services.mmplat"
| xmlns:intf="http://ws.alarm.services.mmplat"
| xmlns:tns2="http://types.alarm.services.mmplat"
| xmlns:tns3="http://to.pegasus.db.mmplat" xmlns:tns4="http://types.pegasus.db.mmplat"
| xmlns:tns5="http://enumeration.types.alarm.services.mmplat"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org
| /2001/XMLSchema">
| <!--WSDL created by Apache Axis version: 1.4
| Built on Apr 22, 2006 (06:55:48 PDT)-->
| <wsdl:types>
| <schema targetNamespace="http://types.pegasus.db.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.alarm.services.mmplat"/>
| <import namespace="http://to.pegasus.db.mmplat"/>
| <import namespace="http://enumeration.types.alarm.services.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="GenericType">
| <sequence/>
| </complexType>
| <complexType name="ObjectID">
| <sequence>
| <element name="objectValue" nillable="true" type="xsd:long"/>
| <element name="value" type="xsd:long"/>
| </sequence>
| </complexType>
| </schema>
| <schema targetNamespace="http://to.pegasus.db.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.alarm.services.mmplat"/>
| <import namespace="http://types.pegasus.db.mmplat"/>
| <import namespace="http://enumeration.types.alarm.services.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="GenericTO">
| <complexContent>
| <extension base="tns4:GenericType">
| <sequence>
| <element name="id" nillable="true" type="tns4:ObjectID"/>
| </sequence>
| </extension>
| </complexContent>
| </complexType>
| </schema>
| <schema targetNamespace="http://enumeration.types.alarm.services.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.alarm.services.mmplat"/>
| <import namespace="http://types.pegasus.db.mmplat"/>
| <import namespace="http://to.pegasus.db.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="StateAlarmType">
| <sequence/>
| </complexType>
| <complexType name="SendType">
| <sequence/>
| </complexType>
| </schema>
| <schema targetNamespace="http://types.alarm.services.mmplat" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://types.pegasus.db.mmplat"/>
| <import namespace="http://to.pegasus.db.mmplat"/>
| <import namespace="http://enumeration.types.alarm.services.mmplat"/>
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="AlarmTO">
| <complexContent>
| <extension base="tns3:GenericTO">
| <sequence>
| <element name="alarmType" nillable="true" type="xsd:string"/>
| <element name="dateCreated" nillable="true" type="xsd:dateTime"/>
| <element name="dateOperation" nillable="true" type="xsd:string"/>
| <element name="dateSend" nillable="true" type="xsd:dateTime"/>
| <element name="dateSent" nillable="true" type="xsd:dateTime"/>
| <element name="dateUpdated" nillable="true" type="xsd:dateTime"/>
| <element name="descripcion" nillable="true" type="xsd:string"/>
| <element name="idTraffic" nillable="true" type="tns4:ObjectID"/>
| <element name="msisdn" nillable="true" type="xsd:string"/>
| <element name="name" nillable="true" type="xsd:string"/>
| <element name="nameCatAlert" nillable="true" type="xsd:string"/>
| <element name="operation" nillable="true" type="xsd:string"/>
| <element name="reference" nillable="true" type="xsd:string"/>
| <element name="serviceID" nillable="true" type="tns4:ObjectID"/>
| <element name="state" nillable="true" type="tns5:StateAlarmType"/>
| <element name="type" nillable="true" type="tns5:SendType"/>
| </sequence>
| </extension>
| </complexContent>
| </complexType>
| </schema>
| </wsdl:types>
|
| <wsdl:message name="invokeSMSAlarmResponse">
|
| <wsdl:part name="invokeSMSAlarmReturn" type="xsd:int"/>
|
| </wsdl:message>
|
| <wsdl:message name="invokeSMSAlarmRequest">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| <wsdl:part name="in1" type="xsd:string"/>
|
| <wsdl:part name="in2" type="xsd:string"/>
|
| <wsdl:part name="in3" type="xsd:string"/>
|
| <wsdl:part name="in4" type="xsd:string"/>
|
| <wsdl:part name="in5" type="xsd:string"/>
|
| <wsdl:part name="in6" type="xsd:string"/>
|
| <wsdl:part name="in7" type="xsd:dateTime"/>
|
| </wsdl:message>
|
| <wsdl:message name="triggerAlarmResponse">
|
| <wsdl:part name="triggerAlarmReturn" type="xsd:boolean"/>
|
| </wsdl:message>
|
| <wsdl:message name="registerPaymentRequest">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| <wsdl:part name="in1" type="xsd:string"/>
|
| <wsdl:part name="in2" type="xsd:string"/>
|
| <wsdl:part name="in3" type="xsd:string"/>
|
| <wsdl:part name="in4" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:message name="pruebaResponse">
|
| </wsdl:message>
|
| <wsdl:message name="invokeSMSAlarm2Request">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| <wsdl:part name="in1" type="xsd:string"/>
|
| <wsdl:part name="in2" type="xsd:string"/>
|
| <wsdl:part name="in3" type="xsd:string"/>
|
| <wsdl:part name="in4" type="xsd:string"/>
|
| <wsdl:part name="in5" type="xsd:string"/>
|
| <wsdl:part name="in6" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:message name="prueba2Request">
|
| <wsdl:part name="in0" type="xsd:int"/>
|
| </wsdl:message>
|
| <wsdl:message name="pruebaRequest">
|
| </wsdl:message>
|
| <wsdl:message name="registerPaymentResponse">
|
| </wsdl:message>
|
| <wsdl:message name="invokeSMSAlarm2Response">
|
| <wsdl:part name="invokeSMSAlarm2Return" type="xsd:int"/>
|
| </wsdl:message>
|
| <wsdl:message name="prueba2Response">
|
| </wsdl:message>
|
| <wsdl:message name="triggerAlarmRequest">
|
| <wsdl:part name="in0" type="tns2:AlarmTO"/>
|
| </wsdl:message>
|
| <wsdl:portType name="AlarmService">
|
| <wsdl:operation name="prueba">
|
| <wsdl:input message="impl:pruebaRequest" name="pruebaRequest"/>
|
| <wsdl:output message="impl:pruebaResponse" name="pruebaResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="prueba2" parameterOrder="in0">
|
| <wsdl:input message="impl:prueba2Request" name="prueba2Request"/>
|
| <wsdl:output message="impl:prueba2Response" name="prueba2Response"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="triggerAlarm" parameterOrder="in0">
|
| <wsdl:input message="impl:triggerAlarmRequest" name="triggerAlarmRequest"/>
|
| <wsdl:output message="impl:triggerAlarmResponse" name="triggerAlarmResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm" parameterOrder="in0 in1 in2 in3 in4 in5 in6 in7">
|
| <wsdl:input message="impl:invokeSMSAlarmRequest" name="invokeSMSAlarmRequest"/>
|
| <wsdl:output message="impl:invokeSMSAlarmResponse" name="invokeSMSAlarmResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm2" parameterOrder="in0 in1 in2 in3 in4 in5 in6">
|
| <wsdl:input message="impl:invokeSMSAlarm2Request" name="invokeSMSAlarm2Request"/>
|
| <wsdl:output message="impl:invokeSMSAlarm2Response" name="invokeSMSAlarm2Response"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="registerPayment" parameterOrder="in0 in1 in2 in3 in4">
|
| <wsdl:input message="impl:registerPaymentRequest" name="registerPaymentRequest"/>
|
| <wsdl:output message="impl:registerPaymentResponse" name="registerPaymentResponse"/>
|
| </wsdl:operation>
|
| </wsdl:portType>
|
| <wsdl:binding name="AlarmServiceSoapBinding" type="impl:AlarmService">
|
| <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
|
| <wsdl:operation name="prueba">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="pruebaRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="pruebaResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="prueba2">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="prueba2Request">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="prueba2Response">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="triggerAlarm">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="triggerAlarmRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="triggerAlarmResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="invokeSMSAlarmRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="invokeSMSAlarmResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="invokeSMSAlarm2">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="invokeSMSAlarm2Request">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="invokeSMSAlarm2Response">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="registerPayment">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="registerPaymentRequest">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="registerPaymentResponse">
|
| <wsdlsoap:body namespace="http://ws.alarm.services.mmplat" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| </wsdl:binding>
|
| <wsdl:service name="AlarmServiceService">
|
| <wsdl:port binding="impl:AlarmServiceSoapBinding" name="AlarmService">
|
| <wsdlsoap:address location="http://localhost:8080/services/AlarmService"/>
|
| </wsdl:port>
|
| </wsdl:service>
|
| </wsdl:definitions>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226899#4226899
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226899
15 years, 7 months
[EJB 3.0] - Re: Deployment error using Service beans
by jaikiran
anonymous wrote : 11:00:51,814 INFO [JBossASKernel] installing bean: spe-input:service=inputServiceBean
| 11:00:51,814 INFO [JBossASKernel] with dependencies:
| 11:00:51,814 INFO [JBossASKernel] and demands:
| 11:00:51,814 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 11:00:51,814 INFO [JBossASKernel] jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
This one looks a bit strange. It shows as deploying a service with an dependency (demands) on jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3. I don't see any obvious reason this dependency should be added on the service, unless it is declared through a jboss.xml or through a @Depends in the code. Furthermore, looking at the logs, it appears like the service is being installed as a management interface too under spe-input:service=inputServiceBean. Do you have a @ObjectName in the code for this service? Can you please post the appropriate @Service bean code including the management interface and the import statements? Please also post the contents of jboss.xml (if any).
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226893#4226893
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226893
15 years, 7 months
[JBoss Messaging] - How to clean up uncommit JMS transactions on jboss 4.2.3
by glenwood
Hi,
I was using jboss HAJMS with a customized PERSISTENT TOPIC, I accidently stop message consuming for a while,which cause my JMS die,when I try to restart jboss server,I found following errors while jboss was trying to deploy jbossmq-httpil.sar under JBOSS_HOME/server/all/deploy-hasinglon/jms
jboss java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.lang.StringCoding.encode(StringCoding.java:266)
at java.lang.String.getBytes(String.java:947)
at java.io.UnixFileSystem.list(Native Method)
at java.io.File.list(File.java:973)
at java.io.File.listFiles(File.java:1051)
at org.apache.axis2.scripting.ScriptRepositoryListener.findServicesInDirectory(ScriptRepositoryListener.java:43)
17:37:43,907 ERROR [STDERR] at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:225)
17:37:43,907 ERROR [STDERR] at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:324)
17:37:43,907 ERROR [STDERR] at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
17:37:43,907 ERROR [STDERR] at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
17:37:43,907 ERROR [STDERR] at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:83)
17:37:43,907 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:512)
17:37:43,907 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:462)
17:37:43,907 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap space
I think it was caused by JMS uncommit transactions,does anyone know how to clean up those uncommit transactions without reinstalling jboss server,it's very important for me,thanks in advance!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226890#4226890
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226890
15 years, 7 months
[EJB 3.0] - Re: Deployment error using Service beans
by rnicholson10
I'm using the latest beta release 5.1.0.Beta.
Here are the console logs:
First deploy including service bean jar:
| 10:59:37,526 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
| 10:59:37,591 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
| 10:59:37,633 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
|
| SecureProfileService/remote - EJB3.x Default Remote Business Interface
| SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
|
| 10:59:38,439 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
| 10:59:38,526 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
| 10:59:38,556 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build: SVNTag=JBoss_5_1_0_Beta1 date=200903131506)] Started in 1m:7s:429ms
| 11:00:50,949 INFO [TomcatDeployment] undeploy, ctxPath=/spe-test
| 11:00:51,636 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15332560{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
| 11:00:51,636 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15332560{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
| 11:00:51,726 INFO [JBossASKernel] Created KernelDeployment for: spe-input.jar
| 11:00:51,726 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
| 11:00:51,726 INFO [JBossASKernel] with dependencies:
| 11:00:51,726 INFO [JBossASKernel] and demands:
| 11:00:51,726 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 11:00:51,726 INFO [JBossASKernel] and supplies:
| 11:00:51,726 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,726 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote
| 11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
| 11:00:51,726 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
| 11:00:51,726 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3) to KernelDeployment of: spe-input.jar
| 11:00:51,814 INFO [JBossASKernel] installing bean: spe-input:service=inputServiceBean
| 11:00:51,814 INFO [JBossASKernel] with dependencies:
| 11:00:51,814 INFO [JBossASKernel] and demands:
| 11:00:51,814 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
| 11:00:51,814 INFO [JBossASKernel] jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
| 11:00:51,814 INFO [JBossASKernel] and supplies:
| 11:00:51,814 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
| 11:00:51,814 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
| 11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote
| 11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
| 11:00:51,814 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
| 11:00:51,814 INFO [JBossASKernel] Installing bean(spe-input:service=inputServiceBean) into kernel
| 11:00:51,817 INFO [STDOUT] InputBeanService - Creating
| 11:00:51,818 INFO [EJBContainer] STARTED EJB: com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
| 11:00:51,845 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
|
| spe-test/InputServiceBean/remote - EJB3.x Default Remote Business Interface
| spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote - EJB3.x Remote Business Interface
| spe-test/InputServiceBean/local - EJB3.x Default Local Business Interface
| spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal - EJB3.x Local Business Interface
|
| 11:00:51,880 INFO [STDOUT] InputBeanService - Starting
| 11:00:52,438 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
|
|
And the deploy after removing the service bean jar:
| 11:00:52,438 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
| 11:01:42,663 INFO [TomcatDeployment] undeploy, ctxPath=/spe-test
| 11:01:42,682 INFO [STDOUT] InputBeanService - Stopping
| 11:01:42,683 INFO [STDOUT] InputBeanService - Stopped
| 11:01:42,710 INFO [EJBContainer] STOPPED EJB: com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
| 11:01:42,710 INFO [STDOUT] InputBeanService - Destroying
| 11:01:42,711 INFO [STDOUT] InputBeanService - Stopped
| 11:01:43,211 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
| 11:01:43,293 WARN [HDScanner] Failed to process changes
| org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
| DEPLOYMENTS MISSING DEPENDENCIES:
| Deployment "spe-input:service=inputServiceBean" is missing the following dependencies:
| Dependency "<UNKNOWN spe-input:service=inputServiceBean>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **")
|
| DEPLOYMENTS IN ERROR:
| Deployment "<UNKNOWN spe-input:service=inputServiceBean>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **
|
| at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:806)
| at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:127)
| at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:337)
| at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:229)
| at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
| at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
| at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
| at java.lang.Thread.run(Unknown Source)
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226887#4226887
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226887
15 years, 7 months
[JBoss Messaging] - Clustered temporary queue problem
by nyeste
Hi,
I have problem using temporary queues in a clustered environment.
- jboss-messaging-1.4.2.GA-SP1
- clustered post office
- jboss-remoting 2.2.2.SP11
- jboss-4.2.3.GA cluster
I want my client application to create a temporary queue, send it's name to the server and receive messages from the server side through that temp queue. The problem is, that about 70% of the messages are got lost because of this: "There is no administratively defined queue with name:i1-x0eldltf-1-ftnkdltf-02c0n3-t1go4c5". In the other 30%, the messages can be consumed without any problem. It doesn't matter how many members are in the server cluster, except the case, that there is only 1, I can see the same behavior (sometimes the message arrives to the client, but mostly not) on all nodes.
The ejb3mdb example works perfectly, so the MDB always can send a reply to the client created temporary queue, but that's not what I need. I want to receive messages from a stateless session bean or a MDB receiving messages from other systems.
I need temporary queue, because there are many users and I can't create a queue for each of them. And another reason is, that the queue should not be available while a user is offline.
If there is only 1 node in the cluster, the desired scenario works fine, like the example, no exception in the log, but in production I need at least 5 nodes.
Is it possible to use temporary queues like this? Is it a clustering problem or it shouldn't work at all?
Thanks a lot!
Zsolt
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226882#4226882
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226882
15 years, 7 months