[JBoss JIRA] Created: (JBMESSAGING-1197) support HTTP transport
by Jeff Mesnil (JIRA)
support HTTP transport
----------------------
Key: JBMESSAGING-1197
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1197
Project: JBoss Messaging
Issue Type: Sub-task
Components: JMS Remoting
Reporter: Jeff Mesnil
Assigned To: Jeff Mesnil
Fix For: 2.0.0 Alpha
the new remoting code based on MINA currently supports only TCP transport.
It must also support HTTP transport.
MINA provides an HTTP package we can use for both the JMS clients (send requests/receive responses)
and the JMS servers (receive request/send response).
Message delivery must also be taken into account. The client can use polling (and remains a simple HTTP client). However since MINA code is used on both the client and ther server, we need to check if we can
send HTTP requests to the client on the same TCP connection (the ideabeing that we MUST NOT open a server connection on the client in any way)
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-4904) Improve error message when binding fails
by Andrew Rubinger (JIRA)
Improve error message when binding fails
----------------------------------------
Key: JBAS-4904
URL: http://jira.jboss.com/jira/browse/JBAS-4904
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Naming
Affects Versions: JBossAS-4.2.2.GA
Reporter: Andrew Rubinger
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.3.GA
Upon attempt to bind an a subcontext to an address already bound by an object, the following exception occurs:
java.lang.ClassCastException: $Proxy76 cannot be cast to javax.naming.Context
at org.jboss.util.naming.Util.createSubcontext(Util.java:69)
at org.jboss.util.naming.Util.rebind(Util.java:125)
at org.jboss.util.naming.Util.rebind(Util.java:113)
Error message should be in form "Can't bind subContext/obj, because subContext is already bound"
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBAS-4569) ClusterPatrition.stopService( ) fails when server is shut down
by Jerry Gauthier (JIRA)
ClusterPatrition.stopService( ) fails when server is shut down
--------------------------------------------------------------
Key: JBAS-4569
URL: http://jira.jboss.com/jira/browse/JBAS-4569
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Jerry Gauthier
Assigned To: Jerry Gauthier
Priority: Minor
Fix For: JBossAS-5.0.0.Beta3
When the server is shut down, the stopService( ) method of ClusterPartition fails with a lengthy stack trace when attempting to unbind the partition from JNDI. The error occurs because InitialContext can't be instantiated due to the following exception.
javax.naming.NoInitialContextException: Cannot instantiate class: org.jboss.iiop.naming.ORBInitialContextFactory[Root exception is java.lang.ClassNotFoundException: org.jboss.iiop.naming.ORBInitialContextFactory]
This error only occurs when the server is being shut down; it doesn't occur if the HAPArtition service is stopped while the server is running.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBMESSAGING-1217) QueueBrowser only enumerates messages in memory - not paged ones
by Peter Schuebl (JIRA)
QueueBrowser only enumerates messages in memory - not paged ones
----------------------------------------------------------------
Key: JBMESSAGING-1217
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1217
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.4.0.SP3
Environment: JBoss Messaging 1.4.0.SP3 (using MySQL for persistence)
JBoss AS 4.2.1.GA
Java 1.6.0_03-b05
Windows XP
Reporter: Peter Schuebl
Assigned To: Tim Fox
The QueueBrowser only enumerates the messages in memory, it won't list the messages which are paged.
For testing I setup a queue with the following settings:
- FullSize: 20
- PageSize: 10
- DownCacheSize: 5
No consumer is set up for this queue.
If I send now 42 messages to this queue browsing the queue (or using the listAllMessages MBean function) only lists 20 of this messages.
The MessageCount attribute of the queue correctly displays 42.
--
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
15 years, 7 months
[JBoss JIRA] Created: (HIBERNATE-43) SQL native Request who respond only the first letter
by Alexandre PETRILLO (JIRA)
SQL native Request who respond only the first letter
----------------------------------------------------
Key: HIBERNATE-43
URL: http://jira.jboss.com/jira/browse/HIBERNATE-43
Project: Hibernate
Issue Type: Bug
Environment: Jboss 4.0.4 G.A. patch 1
Reporter: Alexandre PETRILLO
Assigned To: Steve Ebersole
I need to do some sql native query (to a data base Oracle 9i) from an EJB session Bean.
I use Jboss in version 4.0.4 G.A. patch 1
My simple code :
public List doNativeQueryMultiple(String sqlQuery) {
List list = manager.createNativeQuery(sqlQuery).getResultList();
return list;
}
This is some exemple for understand the probleme.
SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc
Response is : O,N
SELECT 'TOTO' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc
Response is : TOTO,NON
SELECT 'TOT' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc
Response is : T,N
SELECT 'OUI' val FROM dual union SELECT 'abc' FROM dual Order BY 1 asc
Response is : O,a
SELECT 'OUI' val FROM dual union SELECT 'abcd' FROM dual Order BY 1 asc
Response is : OUI,abcd
SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOT' FROM dual Order BY 1 asc
Response is : O,N,T
SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOTO' FROM dual Order BY 1 asc
Response is : OUI,NON,TOTO
When the response of the request is correct, the return class type is java.lang.String
And when is incorrect , the return class type is java.lang.Charactere, and the response contain the first letter.
The bug is when the size of all of the selected string have the same length.
The test done by Jboss for determine the class return type maybe is wrong.
--
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
15 years, 7 months