[Remoting] - Unexplained ConnectionValidator Timeout
by wigdavbar2
hi
We are using JBoss EAP 4.3.0 CP03 from Red Hat for the first time.
We are currently in QA and are having serious problems with a plain JVM acting as a JMS client to a non clustered JBoss app server running on the same box. The client keeps getting its remoting connection invalidated, the exception listener is called, our software reconnects and carries on and messages get through slowly, with a lot of disruption.
I thought maybe the validatorPingTimeout was set too low at 2 seconds and that once bug JBMESSAGING-1482 was fixed we could increase it but looking at the TRACE level messages i'm not sure that is the problem.
Even when the JVM starts up and sits there idle it gets the ConnectionValidator detecting an invalid connection after 90 seconds or so. Once messages start getting produced the invalid connections come frequently.
The tracing shows that when the JVM starts the ConnectionValidator kicks off every 2 seconds and reports connection ok. The LeasePinger also kicks off every 10 seconds and reports everything ok. Then whilst the ConnectionValidator is running another ConnectionValidator on a different thread kicks in and reports the connection is invalid.
See an extract of the trace below. Looks like the ConnectionValidator sends request for version, after a second the second ConnectionValidator kicks in an detects an invalid connection, after another second the first ConnectionValidator gets the version ok. Is there another timeout of 1 second on receiving responses from the server?
thanks
dave barton
lead developer
interactive data
london
09:35:27,966 [Timer-2] ConnectionValidator - ConnectionValidator[SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457], pingPeriod=2000 ms] sending PING tied to lease
| 09:35:27,966 [Timer-2] ConnectionValidator - pinging, sending InvocationRequest[4532be10, self, $PING$] over SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457]
| 09:35:27,966 [Timer-2] MicroRemoteClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457](1) invoking InvocationRequest[4532be10, self, $PING$]
| 09:35:27,966 [Timer-2] transport.socket.MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] obtained semaphore: 49
| 09:35:27,967 [Timer-2] transport.socket.MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] reusing pooled connection: ClientSocketWrapper[Socket[addr=/172.22.186.24,port=4457,localport=42634].390e4fd7]
| 09:35:27,967 [Timer-2] transport.socket.MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] writing version 22 on output stream
| 09:35:27,967 [Timer-2] transport.socket.MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] writing invocation to marshaller
| 09:35:27,967 [Timer-2] JMSWireFormat - Writing InvocationRequest[4532be10, self, $PING$]
| 09:35:27,967 [Timer-2] JMSWireFormat - Stream is a DataOutputStream
| 09:35:27,967 [Timer-2] JMSWireFormat - Writing packet: SerializedPacket[InvocationRequest[4532be10, self, $PING$]]
| 09:35:27,978 [Timer-2] JMSWireFormat - Wrote packet
| 09:35:27,978 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] done writing invocation to marshaller
| 09:35:27,978 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] reading version from input stream
|
| 09:35:28,982 [Timer-3] ConnectionValidator - ConnectionValidator[SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457], pingPeriod=2000 ms]'s connections is invalid
|
| 09:35:29,092 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] read version 22 from input stream
| 09:35:29,092 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] reading response from unmarshaller
| 09:35:29,092 [Timer-2] JMSWireFormat - Reading
| 09:35:29,092 [Timer-2] JMSWireFormat - Stream is already DataInputStream :)
| 09:35:29,092 [Timer-2] JMSWireFormat - Created packet SerializedPacket[null]
| 09:35:29,092 [Timer-2] JMSWireFormat - Reading packet
| 09:35:29,094 [Timer-2] JMSWireFormat - Read packet
| 09:35:29,094 [Timer-2] JMSWireFormat - Returning payload: InvocationResponse[21ce9f9d, true]
| 09:35:29,094 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] returned ClientSocketWrapper[Socket[addr=/172.22.186.24,port=4457,localport=42634].390e4fd7] to pool
| 09:35:29,094 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] released semaphore: 50
| 09:35:29,094 [Timer-2] MicroSocketClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] received response InvocationResponse[21ce9f9d, true]
| 09:35:29,094 [Timer-2] MicroRemoteClientInvoker - SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457] received InvocationResponse so going to return response's return value of true
| 09:35:29,094 [Timer-2] ConnectionValidator - ConnectionValidator got successful ping using SocketClientInvoker[215b011c, bisocket://lnvmbdidev01.eu.intdata.com:4457]
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212845#4212845
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212845
17 years, 1 month
[EJB 3.0] - Re: Own DLQ for EJB3-MDB via ActivationConfigProperty doesn'
by camunda
Hi.
I don't see anything about the DQL in the log, even on debug level?
The only thing I see is the exception thrown:
| 2009-02-25 09:12:47,214 ERROR ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (WorkManager(2)-10:) Unexpected error delivering message delegator->JBossMessage[81510
| 4]:PERSISTENT, deliveryId=0
| javax.ejb.EJBTransactionRolledbackException: No row with the given identifier exists: [org.jbpm.graph.exe.Token#88888888888]
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
| at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
| ...
|
Here my queue configuration:
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=CommandQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
|
| <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=CommandDLQ</attribute>
| <attribute name="SecurityConfig">
| <security>
| <role name="JBossAdmin" read="true" write="true" />
| <role name="JBossAdmin_Role" read="true" write="true" />
| <role name="itInf_Role" read="true" write="true" />
| <role name="DLQ_Role" read="true" write="true" />
| <role name="guest" read="true" write="true" />
| </security>
| </attribute>
| </mbean>
|
Thanks for any hints...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212828#4212828
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212828
17 years, 1 month
[JBossWS] - Webservice problem with base64 data when upgrading to JBoss
by toma25
Hi,
This is a long one du to config files...
I'm running a upgrade from JBoss 4.0.5 to 4.2.3
The system I work with have a legacy webservice. It is based on J2EE webservices 1.1.
It has a SLSB (EJB2) as endpoint.
The WSDL file points out a schema (XSD-file) file for the definition of the parameters to the webservice.
And there is a mapping file which maps to the schema.
The problem:
For starters, the service works in JBoss 4.0.5.
In 4.2.3 it works perfectly fine for except for a attachment element, the base64 data doesn't convert properly into a byte array. Changing it to string works fine, so there is no problem with typos, it just won't convert into a byte array.
Has anyone had a similar problem when upgrading from 4.0.5 to 4.2.3?
If i remove an attachments from the call, it works fine, but if I have one, if fails with:
org.jboss.ws.WSException: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to
| parse source: Failed to resolve target property type on org.jboss.xb.binding.sunday.unmarshalling.ElementBinding@1f1804d({http://foo/newsws/types}attachment, type={http://foo/newsws/types}AttachmentElementType)
| at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:250)
| at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:97)
| at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:141)
| at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:85)
| at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:173)
| at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:263)
| at org.jboss.ws.core.EndpointInvocation.getRequestParamValue(EndpointInvocation.java:115)
| at org.jboss.ws.core.EndpointInvocation.getRequestPayload(EndpointInvocation.java:135)
| at org.jboss.ws.core.server.DelegatingInvocation.getArgs(DelegatingInvocation.java:82)
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB21.getMBeanInvocation(InvocationHandlerEJB21.java:169)
| at org.jboss.wsf.container.jboss42.InvocationHandlerEJB21.invoke(InvocationHandlerEJB21.java:144)
| at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:221)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:466)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
| at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
| at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
| 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.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
| 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(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: org.jboss.ws.core.binding.BindingException: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source:
| Failed to resolve target property type on org.jboss.xb.binding.sunday.unmarshalling.ElementBinding@1369863({http://foo/newsws/t
| ypes}attachment, type={http://foo/newsws/types}AttachmentElementType)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:111)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:62)
| at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:60)
| at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:180)
| ... 36 more
| Caused by: org.jboss.ws.core.jaxrpc.binding.jbossxb.UnmarshalException: Failed to parse source: Failed to resolve target property type on or
| g.jboss.xb.binding.sunday.unmarshalling.ElementBinding@1369863({http://foo/newsws/types}attachment, type={http://foo/newsws/types}AttachmentElementType)
| at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:65)
| at org.jboss.ws.core.jaxrpc.binding.JBossXBDeserializer.deserialize(JBossXBDeserializer.java:103)
| ... 39 more
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve target property type on org.jboss.xb.binding.sun
| day.unmarshalling.ElementBinding@1369863({http://foo/newsws/types}attachment, type={http://foo/newsws/types}Attach
| mentElementType)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:179)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:126)
| at org.jboss.ws.core.jaxrpc.binding.jbossxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshallerImpl.java:61)
| ... 40 more
| Caused by: org.jboss.ws.WSException: Failed to resolve target property type on org.jboss.xb.binding.sunday.unmarshalling.ElementBinding@1369
| 863({http://foo/newsws/types}attachment, type={http://foo/newsws/types}AttachmentElementType)
| at org.jboss.ws.extensions.xop.jaxrpc.JBossXBContentAdapter.beforeSetParent(JBossXBContentAdapter.java:115)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:1005)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:246)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:296)
| at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:175)
| ... 42 more
this is the webservices.xml
<webservice-description>
| <webservice-description-name>FooService</webservice-description-name>
| <wsdl-file>META-INF/wsdl/FooService.wsdl</wsdl-file>
| <jaxrpc-mapping-file>META-INF/FooService-mapping.xml</jaxrpc-mapping-file>
| <port-component>
| <port-component-name>FooService</port-component-name>
| <wsdl-port>FooServicePort</wsdl-port>
| <service-endpoint-interface>com.foo.FooServiceEndpoint</service-endpoint-interface>
| <service-impl-bean>
| <ejb-link>FooServiceBean</ejb-link>
|
| </service-impl-bean>
| </port-component>
| </webservice-description>
>From the foo.xsd
<xs:complexType name="AttachmentElementType">
| <xs:annotation>
| <xs:documentation>Attachment data. When submitting, contains the attachment itself.</xs:documentation>
| </xs:annotation>
| <xs:simpleContent>
| <xs:extension base="xs:base64Binary">
| <xs:attribute name="filename" use="required">
| <xs:annotation>
| <xs:documentation>The filename of the attachment</xs:documentation>
| </xs:annotation>
| </xs:attribute>
| <xs:attribute name="href" type="xs:anyURI" use="optional">
| <xs:annotation>
| <xs:documentation>The URL from which the attachment can be downloaded. Not used when submitting news.</xs:documentation>
| </xs:annotation>
| </xs:attribute>
| <xs:attribute name="mimeType" type="xs:string" use="required">
| <xs:annotation>
| <xs:documentation>The MIME type of the attached file</xs:documentation>
| </xs:annotation>
| </xs:attribute>
| </xs:extension>
| </xs:simpleContent>
| </xs:complexType>
>From FooService-mapping.xml
<java-xml-type-mapping>
| <java-type>foo.MessageElementType</java-type>
| <root-type-qname xmlns:typeNS='http://foo/newsws/types'>typeNS:MessageElementType</root-type-qname>
| <qname-scope>complexType</qname-scope>
| <variable-mapping>
| <java-variable-name>category</java-variable-name>
| <xml-element-name>category</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>type</java-variable-name>
| <xml-element-name>type</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>headline</java-variable-name>
| <xml-element-name>headline</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>body</java-variable-name>
| <xml-element-name>body</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>attachment</java-variable-name>
| <xml-element-name>attachment</xml-element-name>
| </variable-mapping>
| <variable-mapping>
| <java-variable-name>field</java-variable-name>
| <xml-element-name>field</xml-element-name>
| </variable-mapping>
| </java-xml-type-mapping>
And Attachment.java looks like this:
public class AttachmentElementType
| {
|
| protected java.lang.String filename;
|
| protected java.net.URI href;
|
| protected java.lang.String mimeType;
|
| protected byte[] _value;
| public AttachmentElementType(){}
|
| public AttachmentElementType(java.lang.String filename, java.net.URI href, java.lang.String mimeType, byte[] _value){
| this.filename=filename;
| this.href=href;
| this.mimeType=mimeType;
| this._value=_value;
| }
| public java.lang.String getFilename() { return filename ;}
|
| public void setFilename(java.lang.String filename){ this.filename=filename; }
|
| public java.net.URI getHref() { return href ;}
|
| public void setHref(java.net.URI href){ this.href=href; }
|
| public java.lang.String getMimeType() { return mimeType ;}
|
| public void setMimeType(java.lang.String mimeType){ this.mimeType=mimeType; }
|
| public byte[] get_value() { return _value ;}
|
| public void set_value(byte[] _value){ this._value=_value; }
|
| }
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212824#4212824
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212824
17 years, 1 month
[JNDI/Naming/Network] - unable to connect to JBoss messaging using SSH port forwardi
by bodrin
I have asked this on the JBoss Messaging forum, but it turns that here is right place. Two questions regarding http://www.jboss.org/community/docs/DOC-12519 :
1. Say that I have specified the secondaryBindPort and secondaryConnectPort at JBM server. Then in the client LAN say I have "jbmfake" host on which I set up three port forwardings:
jbmfake: serverBindPort -> jbm: serverBindPort
jbmfake: secondaryBindPort -> jbm: secondaryBindPort
jbmfake: secondaryConnectPort -> jbm: secondaryConnectPort
The question is how to configure the client jndi props and rmi props:
Code:
-Djava.rmi.server.hostname=<external_host_name>
-Djava.rmi.server.useLocalHostname=true
<external_host_name>=?
Code:
java.naming.provider.url=jbmfake:SOME_PORT
SOME_PORT=?
2. The above seems to be the configuration when we have single node cluster. So what about two/three/... nodes in the cluster? Could secondaryBindPort and secondaryConnectPort be specified in
\docs\examples\binding-manager\sample-bindings.xml ?
Do I have to port forward for each node separately or a subset (like 1 node) is sufficient?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212822#4212822
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212822
17 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - @NotNull validator doesn't work
by zzuli
Hi,everybody:
I'm using hibernate annotation validator with jseam.
I annotated a pojo, for example:
@NotNull
@Range(min = 3, max = 100, message = "Age must be between 3 and 100")
public int getAge() {
return age;
}
public void setAge(int age) {
this.age = age;
}
//@Pattern(regex="^[\w.-]+(a)[\w.-]+\.[a-zA-Z]{2,4}$")
@NotNull
@Email
public String getEmail() {
return email;
}
public void setEmail(String email) {
this.email = email;
}
in the web page, used with jseam validate. strangely, the @Email,@Pattern,@Range all work fine, but the @NotNull always refused to work - empty form can be submitted . I have tried @NotEmpty, it's the same with @NotNull.
Can anyone help me?
I use jseam2.1.1 , jboss As 5 and the DB is Hypersonic
Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212807#4212807
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212807
17 years, 1 month
[EJB 3.0] - Re: TimerService Restart Issue
by dolsen
I will add more logs tomorrow.
I have rewritten the timer user EJB injection and get slightly different errors, but it might shed some more light on the problem.
It definitely looks like a class loader issue though...
I have also seen the following exception:
| 2009-02-21 21:31:36,562 DEBUG [org.jboss.ejb.txtimer.TimerImpl] (EJB-Timer-1235187861590[target=jboss.j2ee:ear=feudalism.ear,jar=feudalism-beans.jar,name=CommandEJB,service=EJ
| B3]) setTimerState: in_timeout
| 2009-02-21 21:31:36,562 ERROR [org.jboss.ejb.txtimer.TimerImpl] (EJB-Timer-1235187861590[target=jboss.j2ee:ear=feudalism.ear,jar=feudalism-beans.jar,name=CommandEJB,service=EJ
| B3]) Error invoking ejbTimeout
| org.jboss.aop.DispatcherConnectException: EJB container is not completely started, or is stopped.
| at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:60)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.ejb3.stateless.StatelessContainer.callTimeout(StatelessContainer.java:304)
| at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
| 2009-02-21 21:31:36,562 DEBUG [org.jboss.ejb.txtimer.TimerImpl] (EJB-Timer-1235187861590[target=jboss.j2ee:ear=feudalism.ear,jar=feudalism-beans.jar,name=CommandEJB,service=EJ
| B3]) Timer was not registered with Tx, resetting state: [id=1235187861590,target=[target=jboss.j2ee:ear=feudalism.ear,jar=feudalism-beans.jar,name=CommandEJB,service=EJB3],rem
| aining=-23110031,periode=3600000,in_timeout]
|
After I restart the server and if there are no expired timers but timers in the future, when the timeout happens I get:
| 2009-02-24 20:35:15,406 ERROR [org.jboss.ejb.txtimer.TimerImpl] (EJB-Timer-12355
| 32907815[target=jboss.j2ee:ear=feudalism.ear,jar=feudalism-beans.jar,name=Comman
| dEJB,service=EJB3]) Error invoking ejbTimeout
| javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi depend
| ency: env/com.feudalism.session.command.XXXCommandBean/playerBean into property
| com.feudalism.session.command.XXXCommandBean.playerBean: com.feudalism.session.p
| layer.PlayerRemote from BaseClassLoader@10ed791{VFSClassLoaderPolicy@16aa365{nam
| e=vfsfile:/C:/java/jboss-5.0.0.GA/jboss-5.0.0.GA/server/feudalism/deploy/ejb2-ti
| mer-service.xml domain=ClassLoaderDomain@1dddba{name=DefaultDomain parentPolicy=
| BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@8a0d5d} roots=[MemoryC
| ontextHandler@880352[path= context=vfsmemory://5c4o01u-q581nz-frlgcin1-1-frlgdl0
| k-t real=vfsmemory://5c4o01u-q581nz-frlgcin1-1-frlgdl0k-t]] delegates=null expo
| rted=[] <IMPORT-ALL>NON_EMPTY}}
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.ja
| va:77)
| at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java
| :190)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInt
| erceptor.java:76)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3Au
| thenticationInterceptorv2.java:75)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterce
| ptor.java:41)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(Asynchrono
| usInterceptor.java:106)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContaine
| rShutdownInterceptor.java:65)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invo
| ke(CurrentInvocationInterceptor.java:67)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.ejb3.stateless.StatelessContainer.callTimeout(StatelessCont
| ainer.java:304)
| at org.jboss.ejb.txtimer.TimerImpl$TimerTaskImpl.run(TimerImpl.java:561)
| at java.util.TimerThread.mainLoop(Timer.java:512)
| at java.util.TimerThread.run(Timer.java:462)
| Caused by: java.lang.RuntimeException: Unable to inject jndi dependency: env/com
| .feudalism.session.command.XXXCommandBean/playerBean into property com.feudalism
| .session.command.XXXCommandBean.playerBean: com.feudalism.session.player.PlayerR
| emote from BaseClassLoader@10ed791{VFSClassLoaderPolicy@16aa365{name=vfsfile:/C:
| /java/jboss-5.0.0.GA/jboss-5.0.0.GA/server/feudalism/deploy/ejb2-timer-service.x
| ml domain=ClassLoaderDomain@1dddba{name=DefaultDomain parentPolicy=BEFORE parent
| =org.jboss.system.NoAnnotationURLClassLoader@8a0d5d} roots=[MemoryContextHandler
| @880352[path= context=vfsmemory://5c4o01u-q581nz-frlgcin1-1-frlgdl0k-t real=vfsm
| emory://5c4o01u-q581nz-frlgcin1-1-frlgdl0k-t]] delegates=null exported=[] <IMPO
| RT-ALL>NON_EMPTY}}
| at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.
| java:82)
| at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.
| java:99)
| at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.
| java:89)
| at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.
| java:61)
| at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionIn
| vocation.java:89)
| at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvo
| cation.java:83)
| at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invo
| ke(CurrentInvocationInterceptor.java:67)
| at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvo
| cation.java:74)
| at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1076)
| at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:83)
| at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:56)
| at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:51)
| at org.jboss.ejb3.pool.ThreadlocalPool.create(ThreadlocalPool.java:53)
| at org.jboss.ejb3.pool.ThreadlocalPool.get(ThreadlocalPool.java:93)
| at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(Stateles
| sInstanceInterceptor.java:58)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.
| java:102)
| at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
| ... 20 more
| Caused by: javax.naming.NamingException: Could not dereference object [Root exce
| ption is javax.naming.NamingException: Could not dereference object [Root except
| ion is java.lang.RuntimeException: Can not find interface declared by Proxy in o
| ur CL + BaseClassLoader@10ed791{vfsfile:/C:/java/jboss-5.0.0.GA/jboss-5.0.0.GA/s
| erver/feudalism/deploy/ejb2-timer-service.xml}]]
| at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1339)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:804)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
| at org.jboss.ejb3.JndiUtil.lookup(JndiUtil.java:44)
| at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.
| java:75)
| ... 36 more
| Caused by: javax.naming.NamingException: Could not dereference object [Root exce
| ption is java.lang.RuntimeException: Can not find interface declared by Proxy in
| our CL + BaseClassLoader@10ed791{vfsfile:/C:/java/jboss-5.0.0.GA/jboss-5.0.0.GA
| /server/feudalism/deploy/ejb2-timer-service.xml}]
| at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingC
| ontext.java:1463)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:809)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1333)
| ... 40 more
| Caused by: java.lang.RuntimeException: Can not find interface declared by Proxy
| in our CL + BaseClassLoader@10ed791{vfsfile:/C:/java/jboss-5.0.0.GA/jboss-5.0.0.
| GA/server/feudalism/deploy/ejb2-timer-service.xml}
| at org.jboss.ejb3.proxy.objectfactory.ProxyObjectFactory.redefineProxyIn
| Tcl(ProxyObjectFactory.java:341)
| at org.jboss.ejb3.proxy.objectfactory.session.SessionProxyObjectFactory.
| createProxy(SessionProxyObjectFactory.java:134)
| at org.jboss.ejb3.proxy.objectfactory.session.stateless.StatelessSession
| ProxyObjectFactory.getProxy(StatelessSessionProxyObjectFactory.java:79)
| at org.jboss.ejb3.proxy.objectfactory.ProxyObjectFactory.getObjectInstan
| ce(ProxyObjectFactory.java:156)
| at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:3
| 04)
| at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java
| :1438)
| at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingC
| ontext.java:1455)
| ... 44 more
| Caused by: java.lang.ClassNotFoundException: com.feudalism.session.player.Player
| Remote from BaseClassLoader@10ed791{VFSClassLoaderPolicy@16aa365{name=vfsfile:/C
| :/java/jboss-5.0.0.GA/jboss-5.0.0.GA/server/feudalism/deploy/ejb2-timer-service.
| xml domain=ClassLoaderDomain@1dddba{name=DefaultDomain parentPolicy=BEFORE paren
| t=org.jboss.system.NoAnnotationURLClassLoader@8a0d5d} roots=[MemoryContextHandle
| r@880352[path= context=vfsmemory://5c4o01u-q581nz-frlgcin1-1-frlgdl0k-t real=vfs
| memory://5c4o01u-q581nz-frlgcin1-1-frlgdl0k-t]] delegates=null exported=[] <IMP
| ORT-ALL>NON_EMPTY}}
| at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoa
| der.java:385)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
| at java.lang.Class.forName0(Native Method)
| at java.lang.Class.forName(Class.java:242)
| at org.jboss.ejb3.proxy.objectfactory.ProxyObjectFactory.redefineProxyIn
| Tcl(ProxyObjectFactory.java:337)
| ... 50 more
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212804#4212804
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212804
17 years, 1 month