[JBoss JIRA] Created: (JBMESSAGING-544) Use NBIO for connection model
by Tim Fox (JIRA)
Use NBIO for connection model
-----------------------------
Key: JBMESSAGING-544
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-544
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.1
For throughput and scalability we need to use a non blocking IO model to provide connections between jms clients and server.
Unfortunately the JBoss remoting model does not currently allows this.
We can either drive JBoss Remoting to support this model (may take some time)
Or write out own connection functionality - this could be fairly straightforward if we use tools such as Apache MINA.
This would also solve the problem of providing a functional and performant multiplex transport.
Essentially we need a bidirectional channel between jms client and server. On either end bytes can be read or witten in a non blocking fashion.
On top of that we can introduce simple framing in order to provide multiplex functionality.
--
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
17 years, 5 months
[JBoss JIRA] Created: (HIBERNATE-50) Embedded Objects get set to null if all its members are null
by milan w?lke (JIRA)
Embedded Objects get set to null if all its members are null
------------------------------------------------------------
Key: HIBERNATE-50
URL: http://jira.jboss.com/jira/browse/HIBERNATE-50
Project: Hibernate
Issue Type: Bug
Environment: WinXP SP2, JBoss 4.0.4 GA as well as JBoss 4.0.5 GA, installation profile ejb3
Reporter: milan w?lke
Assigned To: Steve Ebersole
When having an embedded object only containing members of non-simple-types (e.g. String) and fetching it with the entity manager the following happens:
If all columns, the embedded objects values are based on, are null the embedded object itself is set to null even if a non-arg-constructor set it to a non-null value before. A valid workaround is to include a member of a simple-type (e.g. int) in the embedded object. Doing this not all the values can be set to null, which results in not setting the embedded object itself to null, too.
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBAS-3647) Backport SingleRetryInterceptor to 3.2
by Scott M Stark (JIRA)
Backport SingleRetryInterceptor to 3.2
--------------------------------------
Key: JBAS-3647
URL: http://jira.jboss.com/jira/browse/JBAS-3647
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering, EJB2
Affects Versions: JBossAS-3.2.8.SP1
Reporter: Scott M Stark
Assigned To: Brian Stansberry
A 3.2.8.SP1 client attempting to connect to a 4.0.4 clustered bean fails with the following error due to the SingleRetryInterceptor not being available in 3.2.8.SP1:
2006-09-12 16:44:30,178 [Thread-0::] - javax.naming.CommunicationException. Root exception is java.lang.ClassNotFoundException:
org.jboss.proxy.ejb.SingleRetryInterceptor (no security manager: RMI class loader disabled)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:318)
at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:132)
at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:143)
at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:918)
We should backport this.
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBAS-3926) Move remoting transports out of conf/jboss-service.xml to a
by Scott M Stark (JIRA)
Move remoting transports out of
conf/jboss-service.xml to a remoting-beans.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Move remoting transports out of conf/jboss-service.xml to a
Move remoting transports out of conf/jboss-service.xml to a remoting-beans.xml
-------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-3926
URL: http://jira.jboss.com/jira/browse/JBAS-3926
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Deployment services, Remoting
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
We need to remove remoting transports out of conf/jboss-service.xml to a remoting-beans.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
17 years, 6 months
[JBoss JIRA] Created: (JBRULES-588) Improve documentation to provide guidance for large rulesets over 10K
by peter lin (JIRA)
Improve documentation to provide guidance for large rulesets over 10K
---------------------------------------------------------------------
Key: JBRULES-588
URL: http://jira.jboss.com/jira/browse/JBRULES-588
Project: JBoss Rules
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: peter lin
Assigned To: Mark Proctor
Priority: Trivial
Last week someone contacted me directly and asked whether JBossRules could handle 50K+ rules. I think it would be good to expand "5.1.8. Large drl files" of the documentation to provide some practical strategies and guidance to users. The docs already recommend increasing the permGen, but more guidance should be provided. Most users aren't going to know what to do when they really have to load 50K rules in the same appserver or jvm.
I will try to write something up and check it in this weekend. hopefully when my brain is marginally functional.
--
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
17 years, 6 months
[JBoss JIRA] Created: (JBAS-3570) SSLUnitTestCase testsuite failures when using the IBM JVM
by Matt Wringe (JIRA)
SSLUnitTestCase testsuite failures when using the IBM JVM
---------------------------------------------------------
Key: JBAS-3570
URL: http://jira.jboss.com/jira/browse/JBAS-3570
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.4.GA
Environment: IBM 1.4.2 JDK
RHEL 4, Linux Kernel 2.6.9
Arch: i386
Reporter: Matt Wringe
The org.jboss.test.web.test.ssl.SSLUnitTestCase tests fail when the IBM JDK is used.
testHttpRedirect
Error: Connection refused
testHttpRedirectSecurityDomain
Error: Connection refused
testHttps
Error: Connection refused
testHttpsSecurityDomain
Error: Connection refused
Stack Trace:
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188)
at java.net.Socket.connect(Socket.java:478)
at java.net.Socket.connect(Socket.java:428)
at java.net.Socket.<init>(Socket.java:335)
at java.net.Socket.<init>(Socket.java:150)
at com.ibm.jsse.bv.<init>(Unknown Source)
at com.ibm.jsse.JSSESocketFactory.createSocket(Unknown Source)
at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:93)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:652)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:628)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497)
at org.jboss.test.web.test.ssl.SSLUnitTestCase.doHttps(SSLUnitTestCase.java:117)
at org.jboss.test.web.test.ssl.SSLUnitTestCase.testHttpsSecurityDomain(SSLUnitTestCase.java:85)
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)
--
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
17 years, 6 months