August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-678) RemoteBinding annotation doesn't use the default client binding of the remoting

by Roland R?z (JIRA)

RemoteBinding annotation doesn't use the default client binding of the remoting ------------------------------------------------------------------------------- Key: EJBTHREE-678 URL: http://jira.jboss.com/jira/browse/EJBTHREE-678 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC8 - FD Reporter: Roland R?z The org.jboss.annotation.ejb.RemoteBinding annotation configures the jndi binding, interceptor stack, the client bind url and the RemoteProxyFactroy. When the jboss remoting service is not configured using the url socket://0.0.0.0:3873 (not listening on the default port or using ssl), the programmer has to specify the the url when he wants to bind the bean to a different jndi context. The deployment has to be deployed into different JBoss instances (pre-production, production,...) with different ports, the deployment has to be rebuilt (different jboss.xml) or even recompiled (with different annotation value). I propose that the default "socket://0.0.0.0:3873" means the default of the remoting configuration or even better set the default to "" in the annotation which would be interpreted as the default remoting configuration. The following fixes the issue using the first described approach: org.jboss.ejb3.stateless.ProxyDeployer public void initializeRemoteBindingMetadata() { remoteBindings = (RemoteBindings) advisor.resolveAnnotation(RemoteBindings.class); if (remoteBindings == null) ... } else { // defaultClientBinding is more accurate that the constant in RemoteBinding if ("socket://0.0.0.0:3873".equals(binding.clientBindUrl())) { binding = new RemoteBindingImpl(binding.jndiBinding(), binding.interceptorStack(), defaultClientBinding, binding.factory()); } RemoteBinding[] list = {binding}; remoteBindings = new RemoteBindingsImpl(list); advisor.getAnnotations().addClassAnnotation(RemoteBindings.class, remoteBindings); } } } -- 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

19 years, 10 months

5
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1014) NavigationPortlet enhancements

by Roy Russo (JIRA)

NavigationPortlet enhancements ------------------------------ Key: JBPORTAL-1014 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1014 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo 1. Add explicit ordering support 2. Add localization support 3. Investigate feasibility of adding submenu support for subpage listing. All configuration options should be made available in the portlet.xml and overriden as preferences in the instances.xml. -- 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

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-539) Rig a RI and investigate the behavior of an XASession in absence of a global transaction

by Ovidiu Feodorov (JIRA)

Rig a RI and investigate the behavior of an XASession in absence of a global transaction ---------------------------------------------------------------------------------------- Key: JBMESSAGING-539 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-539 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Facade Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.0.1.CR5 Install the Sun's RI and run a simple test case with an XASession sending a message in an absence of a global transaction. The test case should determine whether the message is sent to the destination or not when producer.send() completes. Add the same test case to Messaging's testsuite. -- 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

19 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-289) Optimize stacks.xml

by Bela Ban (JIRA)

Optimize stacks.xml ------------------- Key: JGRP-289 URL: http://jira.jboss.com/jira/browse/JGRP-289 Project: JGroups Issue Type: Feature Request Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 We decided we want 4 configurations in stacks.xml: 1. fc-fast-minimalthreads 2. tcp (copy of the above, with TCP/TCPPING as transport) 3. fc-fast-minimalthreads-sync: alternative to #1, without FC and with message bundling disabled 4. tcp-sync: copy of #2, without FC and with message bundling disabled * The default stacks (fc-fast and tcp) have FC and message bundling is enabled * All stacks have FLUSH: because we use the Multiplexer, state transfer requires FLUSH * VIEW_SYNC will be removed (because we use FLUSH, this is redundant) * STREAMING_STATE_TRANSFER will be the default state transfer protocol o STATE_TRANSFER is there, but commented o According to Vladimir, these 2 protocols can be used interchangeably, the correct setState() and getState() methods will always be called * For the TCP-based stack o we use TCP_NIO as transport o Discovery is TCPPING: we pass the list of hosts as a system property, default is localhost * Vladimir and I will look at the resulting stacks.xml, and once it is correct, pass it on to Brian and Manik, so it can be tested with clustering and JBossCache -- 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

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-595) Fix the spring http performance tests.

by Ron Sigal (JIRA)

Fix the spring http performance tests. -------------------------------------- Key: JBREM-595 URL: http://jira.jboss.com/jira/browse/JBREM-595 Project: JBoss Remoting Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) The changes made for the spring rmi performance test need to be applied to the spring http tests. See JBREM-592 for more information. -- 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

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-477) Messages are left in the Messages table after retry message is printed and are retried every time the server is restarted

by Joel Lindheimer (JIRA)

Messages are left in the Messages table after retry message is printed and are retried every time the server is restarted ------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-477 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-477 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.CR2 Environment: Windows XP Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov I am testing Consumer.receive() with a userTransaction rollback scenario; the messages rollback and are retried. Eventually the follwoing message is printed: JBossMessage[49410]:PERSISTENT has exceed maximum delivery attempts and will be removed. However, the messages are never deleted from the messages table; it is therefore retried upon every subsequent server restart. To reproduce just send a simple message with a consumer that does the following: while (true) { log.warn("whileloop+"); ut = (UserTransaction) getInitialContext().lookup("UserTransaction"); ut.begin(); conn = (QueueConnection) this.getQueueFactory().createQueueConnection(); conn.start(); session = conn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); receiver = session.createReceiver(getQueue()); // Note: starting the ut here does causes other issues... so i moved it up // ut = (UserTransaction) getInitialContext().lookup("UserTransaction"); // ut.begin(); TextMessage msg = (TextMessage) receiver.receive(5000); receiver.close(); session.close(); conn.close(); log.warn("msg: " + msg); if(msg!=null) { log.warn("msg.text: " +msg.getText()); } ut.rollback(); (...) Here is the server console print: 12:41:30,946 WARN [TestConsumer] msg: null 12:41:30,946 WARN [TestConsumer] whileloop- 12:41:30,946 WARN [TestConsumer] whileloop+ 12:41:30,946 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,946 WARN [TestConsumer] msg.text: Payload #2 12:41:30,946 WARN [TestConsumer] whileloop- 12:41:30,946 WARN [TestConsumer] whileloop+ 12:41:30,946 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,946 WARN [TestConsumer] msg.text: Payload #2 12:41:30,946 WARN [TestConsumer] whileloop- 12:41:30,946 WARN [TestConsumer] whileloop+ 12:41:30,962 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,962 WARN [TestConsumer] msg.text: Payload #2 12:41:30,962 WARN [TestConsumer] whileloop- 12:41:30,962 WARN [TestConsumer] whileloop+ 12:41:30,962 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,962 WARN [TestConsumer] msg.text: Payload #2 12:41:30,962 WARN [TestConsumer] whileloop- 12:41:30,962 WARN [TestConsumer] whileloop+ 12:41:30,962 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,962 WARN [TestConsumer] msg.text: Payload #2 12:41:30,962 WARN [TestConsumer] whileloop- 12:41:30,962 WARN [TestConsumer] whileloop+ 12:41:30,962 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,962 WARN [TestConsumer] msg.text: Payload #2 12:41:30,962 WARN [TestConsumer] whileloop- 12:41:30,962 WARN [TestConsumer] whileloop+ 12:41:30,977 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,977 WARN [TestConsumer] msg.text: Payload #2 12:41:30,977 WARN [TestConsumer] whileloop- 12:41:30,977 WARN [TestConsumer] whileloop+ 12:41:30,977 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:30,977 WARN [TestConsumer] msg.text: Payload #2 12:41:30,977 WARN [TestConsumer] whileloop- 12:41:30,977 WARN [TestConsumer] whileloop+ 12:41:31,009 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:31,009 WARN [TestConsumer] msg.text: Payload #2 12:41:31,009 WARN [TestConsumer] whileloop- 12:41:31,009 WARN [TestConsumer] whileloop+ 12:41:31,009 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:31,009 WARN [TestConsumer] msg.text: Payload #2 12:41:31,009 WARN [TestConsumer] whileloop- 12:41:31,009 WARN [TestConsumer] whileloop+ 12:41:31,024 WARN [TestConsumer] msg: delegator->JBossMessage[49410]:PERSISTENT 12:41:31,024 WARN [TestConsumer] msg.text: Payload #2 12:41:31,024 WARN [TestConsumer] whileloop- 12:41:31,024 WARN [TestConsumer] whileloop+ 12:41:31,024 WARN [ServerConsumerEndpoint] JBossMessage[49410]:PERSISTENT has exceed maximum delivery attempt s and will be removed -- 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

19 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-3491) Test failure - org.jboss.test.webservice.samples.ServerSideJMSTestCase

by Rajesh Rajasekaran (JIRA)

Test failure - org.jboss.test.webservice.samples.ServerSideJMSTestCase ---------------------------------------------------------------------- Key: JBAS-3491 URL: http://jira.jboss.com/jira/browse/JBAS-3491 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.5.CR1 Reporter: Rajesh Rajasekaran Fix For: JBossAS-4.0.5.CR1 org.jboss.test.webservice.samples.ServerSideJMSTestCase test: testSOAPMessageToEndpointQueue Response received by the client is null. expected:<<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><ns1:getContactInfoResponse xmlns:ns1='http://org.jboss.test.webservice/samples'><result>The 'mafia' boss is currently out of office, please call again.</result></ns1:getContactInfoResponse></env:Body></env:Envelope>> but was:<null> junit.framework.ComparisonFailure: expected:<<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><ns1:getContactInfoResponse xmlns:ns1='http://org.jboss.test.webservice/samples'><result>The 'mafia' boss is currently out of office, please call again.</result></ns1:getContactInfoResponse></env:Body></env:Envelope>> but was:<null> at org.jboss.test.webservice.samples.ServerSideJMSTestCase.testSOAPMessageToEndpointQueue(ServerSideJMSTestCase.java:95) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2... -- 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

19 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3485) Test failure - org.jboss.test.web.test.WebIntegrationUnitTestCase

by Rajesh Rajasekaran (JIRA)

Test failure - org.jboss.test.web.test.WebIntegrationUnitTestCase ----------------------------------------------------------------- Key: JBAS-3485 URL: http://jira.jboss.com/jira/browse/JBAS-3485 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.5.CR1 Reporter: Rajesh Rajasekaran Fix For: JBossAS-4.0.5.CR1 org.jboss.test.web.test.WebIntegrationUnitTestCase testcase: testEJBOnStartupServlet Attached below are the test errors and the server log. http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2... http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2... ERROR: The server encountered an internal error () that prevented it from fulfilling this request.exception <pre>javax.servlet.ServletException: Failed to call OptimizedEJB org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBOnStartupServlet.java:112) org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupServlet.java:127) javax.servlet.http.HttpServlet.service(HttpServlet.java:697) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) </pre>root cause <pre>java.lang.NullPointerException org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBOnStartupServlet.java:106) org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupServlet.java:127) SERVER LOG: 2006-08-07 15:10:14,377 DEBUG [org.jboss.test.web.servlets.EJBOnStartupServlet] failed javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: OptimizedEJB not bound] at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1067) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:700) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:716) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.test.web.servlets.EJBOnStartupServlet.init(EJBOnStartupServlet.java:67) 2006-08-07 15:10:14,332 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbosstest]] Servlet /jbosstest threw load() exception java.lang.NoClassDefFoundError: org/jboss/test/web/util/EJBManifestClass at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618) at java.lang.Class.getConstructor0(Class.java:1930) -- 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

19 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-510) JDBCChannelMapper has a createTablesOnStartup variable but no overide.

by Joel Lindheimer (JIRA)

JDBCChannelMapper has a createTablesOnStartup variable but no overide. ---------------------------------------------------------------------- Key: JBMESSAGING-510 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-510 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: Windows Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov JDBCChannelMapper has a createTablesOnStartup variable but no overide. It does not necessarilly break anything because it tries to create tables and fails. It is just a matter of consistancy and control of Schema and SQL operations. -- 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

19 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-117) Info about moved posts or topic(s).

by Ryszard Kozmik (JIRA)

Info about moved posts or topic(s). ----------------------------------- Key: JBFORUMS-117 URL: http://jira.jboss.com/jira/browse/JBFORUMS-117 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Ryszard Kozmik After moving posts to different topic or moving topic(s) to different forum we are not leaving any message saying that this thread was moved. A link pointing to new location should be left after movement. -- 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

19 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006