[JBossWS] - Webtools generated WSDL fail to deploy
by pshankar
Here is the service that returns the List generated using the wstools
<?xml version="1.0" encoding="UTF-8"?>
| <wsdl:definitions targetNamespace="http://DefaultNamespace" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://DefaultNamespace" xmlns:intf="http://DefaultNamespace" xmlns:tns2="http://www.w3.org/1999/XMLSchema" 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.2alpha
| Built on Dec 01, 2003 (04:33:24 EST)-->
| <wsdl:types>
| <schema targetNamespace="http://DefaultNamespace" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
| <complexType name="ArrayOf_tns2_anyType">
| <complexContent>
| <restriction base="soapenc:Array">
| <attribute ref="soapenc:arrayType" wsdl:arrayType="tns2:anyType[]"/>
| </restriction>
| </complexContent>
| </complexType>
| </schema>
| </wsdl:types>
|
| <wsdl:message name="setNameRequest">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:message name="listConfigurationNameResponse">
|
| <wsdl:part name="listConfigurationNameReturn" type="impl:ArrayOf_tns2_anyType"/>
|
| </wsdl:message>
|
| <wsdl:message name="getNameRequest">
|
| </wsdl:message>
|
| <wsdl:message name="listConfigurationNameRequest">
|
| <wsdl:part name="in0" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:message name="setNameResponse">
|
| </wsdl:message>
|
| <wsdl:message name="getNameResponse">
|
| <wsdl:part name="getNameReturn" type="xsd:string"/>
|
| </wsdl:message>
|
| <wsdl:portType name="MySpringService">
|
| <wsdl:operation name="listConfigurationName" parameterOrder="in0">
|
| <wsdl:input message="impl:listConfigurationNameRequest" name="listConfigurationNameRequest"/>
|
| <wsdl:output message="impl:listConfigurationNameResponse" name="listConfigurationNameResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="getName">
|
| <wsdl:input message="impl:getNameRequest" name="getNameRequest"/>
|
| <wsdl:output message="impl:getNameResponse" name="getNameResponse"/>
|
| </wsdl:operation>
|
| <wsdl:operation name="setName" parameterOrder="in0">
|
| <wsdl:input message="impl:setNameRequest" name="setNameRequest"/>
|
| <wsdl:output message="impl:setNameResponse" name="setNameResponse"/>
|
| </wsdl:operation>
|
| </wsdl:portType>
|
| <wsdl:binding name="MySpringServiceSoapBinding" type="impl:MySpringService">
|
| <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
|
| <wsdl:operation name="listConfigurationName">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="listConfigurationNameRequest">
|
| <wsdlsoap:body namespace="http://DefaultNamespace" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="listConfigurationNameResponse">
|
| <wsdlsoap:body namespace="http://DefaultNamespace" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="getName">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="getNameRequest">
|
| <wsdlsoap:body namespace="http://DefaultNamespace" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="getNameResponse">
|
| <wsdlsoap:body namespace="http://DefaultNamespace" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| <wsdl:operation name="setName">
|
| <wsdlsoap:operation soapAction=""/>
|
| <wsdl:input name="setNameRequest">
|
| <wsdlsoap:body namespace="http://DefaultNamespace" use="literal"/>
|
| </wsdl:input>
|
| <wsdl:output name="setNameResponse">
|
| <wsdlsoap:body namespace="http://DefaultNamespace" use="literal"/>
|
| </wsdl:output>
|
| </wsdl:operation>
|
| </wsdl:binding>
|
| <wsdl:service name="MySpringServiceService">
|
| <wsdl:port binding="impl:MySpringServiceSoapBinding" name="MySpringService">
|
| <wsdlsoap:address location="http://localhost:8080/MySpringService"/>
|
| </wsdl:port>
|
| </wsdl:service>
|
| </wsdl:definitions>
|
Here is the exception when I try to deploy
11:34:24,910 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.5.GA/server/default/deploy/
| org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://DefaultNamespace}ArrayOf_tns2_anyType
| at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataRpc(JSR109MetaDataBuilder.java
| at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuilder.java:1
| at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java
| at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:78)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
| at org.jboss.ws.integration.jboss.DeployerInterceptorJSE.create(DeployerInterceptorJSE.java:74)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptor
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993544#3993544
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993544
19 years, 7 months
[JBossCache] - problem with org/jaxen/VariableContext
by frehan
When I upgraded from 4.0.4GA to 4.0.5GA I started to get problems with
19:50:35,960 ERROR [SimpleStatefulCache] problem passivation thread
javax.ejb.EJBException: Could not passivate; failed to save state
at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersist
enceManager.java:363)
at org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:196)
at org.jboss.ejb3.cache.simple.SimpleStatefulCache$SessionTimeoutTask.run(SimpleStatefulCache.java:129)
Caused by: java.io.IOException ....
Caused by: java.lang.NoClassDefFoundError: org/jaxen/VariableContext
I do not have any clustering turned on and should not have any caching but I still get this problem. The class org/jaxen/VariableContext is in the jar jaxen.jar in jboss_home/server/default/lib so why can Jboss not find his class and why is it needed.
Any help is very much appreciated!
/Fredrik
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993543#3993543
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993543
19 years, 7 months
[EJB 3.0] - Getting Syntax error with EJB 3.0.
by dvuday
Hi every body I'm Uday...
I am new to EJB 3.0 and I am getting the following Error in the Satateless Session Bean program given below..This is the example given in the JBoss trialblazer. I have put the necessary jar files in the classpath of the project.
Eclipse is showing Syntax error at "@Stateless"..saying @Stateless cannot be resolved...
Can any body please help me
package trail.slsb;
import org.jboss.annotation.ejb.LocalBinding;
import javax.ejb.*;
@Stateless
// @LocalBinding (jndiBinding="EJB3Trail/slsb/Calculator")
public class StatelessCalculator implements Calculator {
public double calculate (int start, int end, double growthrate, double saving) {
double tmp = Math.pow(1. + growthrate / 12., 12. * (end - start) + 1);
return saving * 12. * (tmp - 1) / growthrate;
}
}
Thanks in advance
Uday
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993527#3993527
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993527
19 years, 7 months
[JBoss Seam] - Re: Can Seam work with no ejb3 but with Hibernate ORM?
by pgrillo
Sorry, i "thought" i was monitoring this thread, so missed the info.
Since then we have decided that Seam is an excellent way to go with our thin client implementation of our system. I'm trying to get my hands around whether and how we can integrate our current hibernate 3.2 based component into Seam, without having a dependency on Seam, since our component will also be used in other applications that are not thin client.
What we have:
|
| Set of Pojo Business Objects, quite robust.
| Set of DAOs pretty much consistent with Christian's approach in Java Peristence with Hibernate
| DAOs use getCurrenSession
| Currently use "hibernate.current_session_context_class=managed"
| Currently using our own filterservlet, would move to Seam handling it.
| HibernateFactory is built dynamically by our own Factory component, where the DAO can reference it
| Use Java 5 and Tomcat 5.5.9, as well as weblogic.
| We do not currently use JTA or EJB3, or even JNDI
|
|
|
| So we now wish to use Seam. Our above DAOs would be readily available to any seam component that needs it, simply by accessing our Factory. Generally speaking, the session is not as interesting or important to our components as the DAOs. That is injecting the session might be nice, but injecting the session into a DAO makes DAO dependent on seam injection.
|
| What i need is simply (or not so simply) to
|
| | have Seam manage the hibernate session in a way that it continues to be available to our DAOs, and also, if possible, to allow transaction demarcation when needed at least where Seam intercepts and manages the session
| |
|
| The excerpt below seems to show how to do this. However, it says "if we want a Seam managed Hibernate Session to be available" which is okay, but does this imply that doing the following also acheives my above goal? Hibernate manages the lifecycle of the session, and also provides access to the hibernate session to our DAOS (getCurrentSession?) "without" injection, since i do not want injection inside the DAOs?
|
|
| anonymous wrote :
| | 9.5.2. Using a Seam-managed Hibernate Session
| |
| | We will also need to configure a managed session if we want a Seam managed Hibernate Session to be available via injection.
| |
| | To configure our Seam component, as usual, we use components.xml:
| | <component class="org.jboss.seam.core.Hibernate"/>
| | | <component name="bookingDatabase"
| | | class="org.jboss.seam.core.ManagedHibernateSession">
| | | <property name="sessionFactoryJndiName">java:/bookingSessionFactory</property>
| | | </component>
| | |
|
|
|
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993526#3993526
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993526
19 years, 7 months
[Messaging, JMS & JBossMQ] - Can connect as Client but not as MDB
by akhammon
I can send a message to the queue authenticated by ldap but I cannot get the mbd to connect to consume the message.
please advise.
Below is my stack trace.
2006-12-13 13:06:35,680 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4fbad6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1b1c978 destination=queue/tutorial/example isTopic=false tx=true durable=false clientID=akhammon reconnect=10 provider=java:/DefaultJMSProvider user=akhammon pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
2006-12-13 13:06:35,680 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Setting up org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4fbad6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1b1c978 destination=queue/tutorial/example isTopic=false tx=true durable=false clientID=akhammon reconnect=10 provider=java:/DefaultJMSProvider user=akhammon pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
2006-12-13 13:06:35,680 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Retrieving the jms provider adapter java:/DefaultJMSProvider for org.jboss.resource.adapter.jms.inflow.JmsActivation@11a2c8f(spec=org.jboss.resource.adapter.jms.inflow.JmsActivationSpec(a)4fbad6 mepf=org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory@1639a4b active=true transacted=true)
2006-12-13 13:06:35,680 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Using jms provider adapter org.jboss.jms.jndi.JNDIProviderAdapter@46d485 for org.jboss.resource.adapter.jms.inflow.JmsActivation@11a2c8f(spec=org.jboss.resource.adapter.jms.inflow.JmsActivationSpec(a)4fbad6 mepf=org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory@1639a4b active=true transacted=true)
2006-12-13 13:06:35,680 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Using context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.partitionName=ADVENG, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=10.2.177.28:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} for org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4fbad6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1b1c978 destination=queue/tutorial/example isTopic=false tx=true durable=false clientID=akhammon reconnect=10 provider=java:/DefaultJMSProvider user=akhammon pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
2006-12-13 13:06:35,680 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
2006-12-13 13:06:35,680 DEBUG [org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler] Attempting to lookup dlq connection factory XAConnectionFactory
2006-12-13 13:06:35,680 DEBUG [org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory] Extracting SpyConnectionFactory from reference
2006-12-13 13:06:35,681 DEBUG [org.jboss.mq.referenceable.SpyConnectionFactoryObjectFactory] The GenericConnectionFactory is: GenericConnectionFactory[server=org.jboss.mq.il.uil2.UILServerIL@1dcc1e2 connectionProperties={ClientILService=org.jboss.mq.il.uil2.UILClientILService, UIL_TCPNODELAY_KEY=yes, UIL_CHUNKSIZE_KEY=1000000, UIL_CONNECTADDRESS_KEY=null, UIL_CONNECTPORT_KEY=0, UIL_SOTIMEOUT_KEY=120000, UIL_RECEIVE_REPLIES_KEY=No, UIL_ADDRESS_KEY=10.2.177.28, UIL_PORT_KEY=8093, PingPeriod=60000, UIL_BUFFERSIZE_KEY=2048}]
2006-12-13 13:06:35,681 DEBUG [org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler] Got dlq connection factory org.jboss.mq.SpyXAConnectionFactory@3d0564 from XAConnectionFactory
2006-12-13 13:06:35,681 DEBUG [org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler] Attempting to create queue connection with user null
2006-12-13 13:06:35,682 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2006-12-13 13:06:35,682 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2006-12-13 13:06:35,682 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2006-12-13 13:06:35,682 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2006-12-13 13:06:35,682 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2006-12-13 13:06:35,682 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2006-12-13 13:06:35,683 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2006-12-13 13:06:35,683 ERROR [org.jboss.mq.sm.file.DynamicLoginModule] Failed to load DynamicSecurityManager
java.lang.ClassCastException: org.jboss.mq.sm.jdbc.JDBCStateManager cannot be cast to org.jboss.mq.sm.file.DynamicStateManager
at org.jboss.mq.sm.file.DynamicLoginModule.initialize(DynamicLoginModule.java:68)
at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:601)
at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:535)
at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:215)
at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66)
at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613)
at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:235)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:619)
2006-12-13 13:06:35,684 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2006-12-13 13:06:35,685 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.io.InterruptedIOException: Operation interrupted
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2247)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2427)
at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2497)
at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2569)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2718)
at java.io.ObjectInputStream.readByte(ObjectInputStream.java:895)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
at java.lang.Thread.run(Thread.java:619)
2006-12-13 13:06:35,686 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2006-12-13 13:06:35,686 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2006-12-13 13:06:35,686 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4fbad6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1b1c978 destination=queue/tutorial/example isTopic=false tx=true durable=false clientID=akhammon reconnect=10 provider=java:/DefaultJMSProvider user=akhammon pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
javax.jms.JMSSecurityException: User: null is NOT authenticated
at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:230)
at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:66)
at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:613)
at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:172)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:235)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:619)
2006-12-13 13:06:35,687 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Tearing down org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4fbad6(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)1b1c978 destination=queue/tutorial/example isTopic=false tx=true durable=false clientID=akhammon reconnect=10 provider=java:/DefaultJMSProvider user=akhammon pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=0)
2006-12-13 13:06:35,687 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Removing DLQ org.jboss.resource.adapter.jms.inflow.JmsActivation@11a2c8f(spec=org.jboss.resource.adapter.jms.inflow.JmsActivationSpec(a)4fbad6 mepf=org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory@1639a4b active=true dlq=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler@119587d transacted=true)
2006-12-13 13:06:35,687 DEBUG [org.jboss.resource.adapter.jms.inflow.JmsActivation] Tearing down complete org.jboss.resource.adapter.jms.inflow.JmsActivation@11a2c8f(spec=org.jboss.resource.adapter.jms.inflow.JmsActivationSpec(a)4fbad6 mepf=org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory@1639a4b active=true transacted=true)
2006-12-13 13:06:35,687 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2006-12-13 13:06:35,687 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993521#3993521
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993521
19 years, 7 months
[JCA/JBoss] - Re: Sybase database pool not claiming used connections
by weston.price＠jboss.com
anonymous wrote :
| Enabling the Tracing would overwhelm us, in a test machine for a simple scenario we had over 1.000 lines of output. I can't even imagine in production (thousands of users per day). Could we go without this?
|
The trace is used only to evaluate what the issue might be, this is not recommended for production. I assume that you have a dev/test/qa environment that should be *fairly* close to what you run in production. You would want to do your tracing in one of these areas.
anonymous wrote :
| We don't have any warnings from JBoss stating that it closed the connection for us, but if you would not mind to explain to me, how does JBoss check this? I mean if we do have a connection leak, in a class that is hold in memory and not collected by the GC, would JBoss still claim that connection and close it?
|
The CacheConnectionManager is the component that handles the automatic connection close. This is actually JCA spec mandated behavior. Use of this in JBoss depends on a few things
1) The debug flag needs to be set in the CachedConnectionManager. This is on by default, so typically you don't need to do anything to enable this.
2) You are accessing a DataSource from an EJB
By default all container configuration in standardjboss.xml and the EJB3 equivalent (ejb3-interceptors-aop.xml) are set to use the CacheConnectionInterceptor. Again, this is on by default and typically does not required explicit changes to enable.
3)You are accessing the DataSource from a Servlet/JSP
For Servlets and JSP this behavior does have to be explicity enabled. Information on how to do this can be found here
http://wiki.jboss.org/wiki/Wiki.jsp?page=CanJBossTellMeWhenIDontCloseACon...
Note, this has nothing to do with the GC but rather the connection management system of JCA. If you use connections and do not appropriately close these connections (along with it's sub objects PreparedStatements, ResultSet etc) you will get leaks. As a result, the ManagedConnectionPool will run out of connections and you will not be able to aquire any further resources.
anonymous wrote :
| Regarding the JTDS, that's our next shot, do you know if it has a better performance than jconnect (which according to Sybase is the best around ;) )
|
Of course :-). I always recommend testing with multiple drivers for RDMS systems that have this option. Sybase/MSSQL Server are two that do. JTDS has been known to perform better and handle certain transactional sistuations much better than the close source counterpart.
anonymous wrote :
| As you can see there's no connection idle timeout (our mistake) we are fixing it. But what's the behavior of this property, would jboss close the physical connection between it and the DB after the number of minutes informed? If so, why during low access periods (late evenings for instance) I still get 50 connections available, wouldn't the expected number be something like 10 (the minimum)?
|
If an idle timeout is not specified, a default of 30 minutes is used so, whether you specify one or not, this behavior is always on. The behavior is that after a period of time the IdleRemover thread in JBoss evaluates the connection pool to determine if any connections have been idle for the period of time. If so, it automatically closes the connection and, depending upon your minumum setting, brings the pool back to the minimum connection allotment if necessary.
Based upon what you are seeing, yes, the connection pool *should* be reduced to the minimum number of connections during periods of low activity. This is why a standalone test case would be useful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993513#3993513
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993513
19 years, 7 months
[EJB/JBoss] - Stateless EJB web service and nested elements
by pepper_fiend
JBoss 4.0.3SP1
I have created a simple Java bean where one bean is nested inside the other, e.g., a Sale bean contains a Product bean, among other fields.
I have created an EJB with a Remote interface. I have exposed this interface as a web service. It uses RPC/Literal style. The method signature is:
public Sale getSale() throws RemoteException;
The EJB deploys just fine with no errors; I can also see the wsdl via a browser. But I get an error when I call this web service:
anonymous wrote : SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.
I have read in the Axis API that SimpleDeserializer cannot handle nested elements. I'm not certain whether this is really my problem, though.
I have also found that this exception is associated with Doc/Literal wsdl's where a method uses an array, which is clearly not my case.
Can anyone recommend a course of action to help me debug this issue? Thank you in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993509#3993509
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993509
19 years, 7 months
[JCA/JBoss] - Re: Sybase database pool not claiming used connections
by viniciuscarvalho
Hello Weston thanks for your time and advices. Some points:
Enabling the Tracing would overwhelm us, in a test machine for a simple scenario we had over 1.000 lines of output. I can't even imagine in production (thousands of users per day). Could we go without this?
We don't have any warnings from JBoss stating that it closed the connection for us, but if you would not mind to explain to me, how does JBoss check this? I mean if we do have a connection leak, in a class that is hold in memory and not collected by the GC, would JBoss still claim that connection and close it?
Regarding the JTDS, that's our next shot, do you know if it has a better performance than jconnect (which according to Sybase is the best around ;) )
As you can see there's no connection idle timeout (our mistake) we are fixing it. But what's the behavior of this property, would jboss close the physical connection between it and the DB after the number of minutes informed? If so, why during low access periods (late evenings for instance) I still get 50 connections available, wouldn't the expected number be something like 10 (the minimum)?
Sorry for all the questions, hope you could aid me on this.
Best Regards
| datasources>
| <local-tx-datasource>
| <jndi-name>SybaseDS</jndi-name>
| <connection-url>jdbc:sybase:Tds:0.0.0.0:00/xxxxxxxxxxxxxxxxxxxxx</connection-url>
| <driver-class>xxxxxxxxxxxxxxxxxxx</driver-class>
| <user-name>xxxxx</user-name>
| <password>xxxxxxx</password>
|
| <!-- Walter -->
| <min-pool-size>10</min-pool-size>
| <max-pool-size>50</max-pool-size>
| <!--idle-timeout-minutes>6000</idle-timeout-minutes -->
| <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
| <metadata>
| <type-mapping>mySQL</type-mapping>
| </metadata>
|
| </local-tx-datasource>
| </datasources>
|
PS: Got this from production right now, really do not know why we have mySQL as the type-mapping for a sybase ds... :P
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993487#3993487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993487
19 years, 7 months