[JBoss JIRA] Deleted: (JBAS-4894) port-component element not mapped
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-4894?page=all ]
Thomas Diesler deleted JBAS-4894:
---------------------------------
> port-component element not mapped
> ---------------------------------
>
> Key: JBAS-4894
> URL: http://jira.jboss.com/jira/browse/JBAS-4894
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Thomas Diesler
> Assigned To: Scott M Stark
>
> I can't find the port-component element mapped to the metadata model.
> <xsd:complexType name="generic-beanType">
> <xsd:sequence>
> <xsd:group ref="javaee:descriptionGroup"/>
> <xsd:element name="ejb-name" type="javaee:ejb-nameType"/>
> <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/>
> <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/>
> <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/>
> <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/>
> <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/>
> <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/>
> <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/>
> <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/>
> <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/>
> <!-- TODO: should we have a jndiEnvironmentRefsGroup in here? -->
> <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/>
> </xsd:sequence>
> </xsd:complexType>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (EJBTHREE-986) EJB3 Remoting cause BindException on load
by Yvan Borgne (JIRA)
EJB3 Remoting cause BindException on load
-----------------------------------------
Key: EJBTHREE-986
URL: http://jira.jboss.com/jira/browse/EJBTHREE-986
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.0 GA
Environment: JBoss 4.2.0 GA, JDK 1.5.0_08-b03, Windows XP SP2
Reporter: Yvan Borgne
After a lot of call (>3000) to an EJB3 SLSB this exception is throwed :
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://127.0.0.1:3873/]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
at $Proxy0.bar(Unknown Source)
at client.Test.main(Test.java:22)
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:516)
at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
at $Proxy0.bar(Unknown Source)
at client.Test.main(Test.java:22)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
... 10 more
Jboss server and test client are on the same host.
For each call, a new TCP connection is opened, with a different local port. So there is also a performance problem.
Here is a simple code to reproduce :
-- EJB3 remote Interface --
package ejb;
import javax.ejb.Remote;
@Remote
public interface Foo {
public void bar();
}
-- EJB3 Implementation --
package ejb;
import javax.ejb.Stateless;
@Stateless
public class FooBean implements Foo {
public void bar() {
}
}
-- client --
package client;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import ejb.Foo;
public class Test {
public static void main(String[] args) {
try {
Properties env = new Properties();
env.put(Context.PROVIDER_URL, "jnp://localhost:1099");
env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
env.put("jnp.disableDiscovery", "true");
Context context = new InitialContext(env);
Foo foo = (Foo)context.lookup("FooBean/remote");
while(true) {
foo.bar();
}
} catch (Exception e) {
e.printStackTrace();
}
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (EJBTHREE-938) Expired messages are being delivered
by Carlo de Wolf (JIRA)
Expired messages are being delivered
------------------------------------
Key: EJBTHREE-938
URL: http://jira.jboss.com/jira/browse/EJBTHREE-938
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.0 CR1
Environment: mdb unit test
Reporter: Carlo de Wolf
Fix For: AS 4.2.0 CR2
2007-04-04 11:58:56,566 INFO [STDOUT] *** ExpirationTestMDB onMessage 1 in org.jboss.ejb3.test.mdb.ExpirationTestMDB@27977433
2007-04-04 11:58:56,566 INFO [STDOUT] *** now = 1175680736566
2007-04-04 11:58:56,567 INFO [STDOUT] *** message = SpyTextMessage {
Header {
jmsDestination : QUEUE.expirationtest
jmsDeliveryMode : 1
jmsExpiration : 1175680735655
jmsPriority : 4
jmsMessageID : ID:436-11756807355552
jmsTimeStamp : 1175680735555
jmsCorrelationID: null
jmsReplyTo : null
jmsType : null
jmsRedelivered : false
jmsProperties : {foo=bar, currentTest=testExpiration, null=null}
jmsPropReadWrite: false
msgReadOnly : true
producerClientId: ID:436
}
Body {
text :expire on server
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months