[svn] 1103: Bug: BLZ-114-Throttle settings REPLACE policy should be deprecated

Revision: 1103
Author: [email protected]
Date: 2008-04-04 11:11:04 -0700 (Fri, 04 Apr 2008)
Log Message:
Bug: BLZ-114-Throttle settings REPLACE policy should be deprecated
QA: Yes - please replace REPLACE policy with IGNORE policy is all qa config files and runtime configuration classes.
Doc: Yes - remove references to REPLACE in our doc.
Details: Throttle settings REPLACE policy is not used in our code. So when it's used, we now log a warning to the user to replace it with IGNORE policy.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-114
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageDestination.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/config/ThrottleSettings.java

Should I file a bug report? If so, with Arch or upstream?

Similar Messages

[svn] 3722: Bug: BLZ-260 - Error message for a legacy =3. 0 client poll failing against a =3.1 server is unclear

Revision: 3722
Author: [email protected]
Date: 2008-10-17 14:04:59 -0700 (Fri, 17 Oct 2008)
Log Message:
Bug: BLZ-260 - Error message for a legacy <=3.0 client poll failing against a >=3.1 server is unclear
QA: Yes
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-260
Modified Paths:
blazeds/trunk/modules/common/src/flex/messaging/errors.properties
blazeds/trunk/modules/core/src/flex/messaging/FlexSession.java
blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

your problem:
Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
Loader: oracle.bpel.common:10.1.3
Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

[svn] 1751: Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.

Revision: 1751
Author: [email protected]
Date: 2008-05-15 14:21:43 -0700 (Thu, 15 May 2008)
Log Message:
Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
QA: No - customer verified the fix.
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/MessageService.java

If you create a metadatatype with a single metdata block, and you reference that in your vm/cm cell attribute using a *one* based index, Excel seems to see the link and it honors it when saving the spreadsheet.
So, I ended up with something like:
<c ... cm="1"/> (I'm dealing with cell metadata, but the concept is equivalente to value metadata)
<metadataTypes count="1">
 <metadataType name="MyMetaType" .../>
</metadataTypes>
<futureMetadata count="1" name="MyMetaType">
 <bk>
 <extLst><ext
uri="http://example" xmlns:x="http://example"><x:val>87</x:val></ext></extLst>
 </bk>
</futureMetadata>
<cellMetadata count="1">
 <bk><rc
t="1" v="0"/></bk> 
</cellMetadata>
Hope this helps.

[svn] 949: Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name , it causes a ClassCastException in the server

Revision: 949
Author: [email protected]
Date: 2008-03-27 07:12:59 -0700 (Thu, 27 Mar 2008)
Log Message:
Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name, it causes a ClassCastException in the server
QA: Yes - try again with legacy-collection true and false.
Doc: No
Checkintests: Pass
Details: Another try in fixing this bug. When legacy-collection is false, Actionscript Array on the client becomes Java Array on the server and my fix yesterday assumed this case. However, when legacy-collection is true, Actionscript Array becomes Java ArrayList on the server. So added code to handle this case.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-96
Modified Paths:
blazeds/branches/3.0.x/modules/proxy/src/java/flex/messaging/services/http/proxy/RequestF ilter.java

Hi all!
Just to post the solution to this if anyone ever runs accross this thread...
For some reason i had it bad the first time, don't have time right now to see why but here is what worked for me:
HashMap primaryFile = new HashMap();
primaryFile.put("fileContent", bFile);
primaryFile.put("fileName", uploadedFile.getFilename());
operationBinding.getParamsMap().put("primaryFile", primaryFile);
HashMap customDocMetadata = new HashMap();
HashMap [] properties = new HashMap[1];
HashMap customMetadataPropertyRoom = new HashMap();
customMetadataPropertyRoom.put("name", "xRoom");
customMetadataPropertyRoom.put("value", "SOME ROOM");
properties[0] = customMetadataPropertyRoom;
customDocMetadata.put("property", properties);
operationBinding.getParamsMap().put("CustomDocMetaData", customDocMetadata);
Basically an unbounded wsdl type is an array of objects (HashMaps), makes sense, i thought i had it like this before, must have messed up somewhere...
Good luck all!

[svn] 931: Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name , it causes a ClassCastException in the server

Revision: 931
Author: [email protected]
Date: 2008-03-26 11:31:01 -0700 (Wed, 26 Mar 2008)
Log Message:
Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name, it causes a ClassCastException in the server
QA: Yes - we need automated tests for this basic case.
Doc: No
Checkintests: Pass
Details: RequestFilter was not handling multiple headers with the same name properly.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-96
Modified Paths:
blazeds/branches/3.0.x/modules/proxy/src/java/flex/messaging/services/http/proxy/RequestF ilter.java

Hi all!
Just to post the solution to this if anyone ever runs accross this thread...
For some reason i had it bad the first time, don't have time right now to see why but here is what worked for me:
HashMap primaryFile = new HashMap();
primaryFile.put("fileContent", bFile);
primaryFile.put("fileName", uploadedFile.getFilename());
operationBinding.getParamsMap().put("primaryFile", primaryFile);
HashMap customDocMetadata = new HashMap();
HashMap [] properties = new HashMap[1];
HashMap customMetadataPropertyRoom = new HashMap();
customMetadataPropertyRoom.put("name", "xRoom");
customMetadataPropertyRoom.put("value", "SOME ROOM");
properties[0] = customMetadataPropertyRoom;
customDocMetadata.put("property", properties);
operationBinding.getParamsMap().put("CustomDocMetaData", customDocMetadata);
Basically an unbounded wsdl type is an array of objects (HashMaps), makes sense, i thought i had it like this before, must have messed up somewhere...
Good luck all!

[svn] 2692: Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out .

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

[svn] 4290: Bug: BLZ-288 - Consumer is only receiving first pushed message when Consumer and RemoteObject that is used to push the messages use different channel sets but same channel .

Revision: 4290
Author: [email protected]
Date: 2008-12-11 14:24:37 -0800 (Thu, 11 Dec 2008)
Log Message:
Bug: BLZ-288 - Consumer is only receiving first pushed message when Consumer and RemoteObject that is used to push the messages use different channel sets but same channel.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* The bug app was arguably generating bogus test data (messages with duplicate ids), and 99.9% of applications won't be configured this way (using multiple ChannelSets with overlapping Channels, pointing at the same server) but it's still worth making this work just right anyways.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-288
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ConsumerMessageDispatcher.as

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn] 1543: Bug: BLZ-152-lcds custom Date serialization issue - need to add java.io. Externalizable as the first type tested in AMF writeObject() functions

Revision: 1543
Author: [email protected]
Date: 2008-05-02 15:32:59 -0700 (Fri, 02 May 2008)
Log Message:
Bug: BLZ-152-lcds custom Date serialization issue - need to add java.io.Externalizable as the first type tested in AMF writeObject() functions
QA: Yes - please check that the fix is working with AMF3 and AMFX and you can turn on/off the fix with the config option.
Doc: No
Checkintests: Pass
Details: The problem in this case was that MyDate.as was serialized to MyDate.java on the server but on the way back, MyDate.java was serialized back to Date.as. As the bug suggests, added an Externalizable check in AMF writeObject functions. However, I didn't do this for AMF0Output as AMF0 does not support Externalizable. To be on the safe side, I also added legacy-externalizable option which is false by default but when it's true, it restores the current behavior.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-152
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.ja va
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/amf/Amf3Output.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/io/amfx/AmfxOutput.java
blazeds/branches/3.0.x/resources/config/services-config.xml

[svn] 4377: Bug: BLZ-292 - Data Push sample does not work in BlazeDS Turnkey

Revision: 4377 Author: [email protected] Date: 2008-12-22 16:16:25 -0800 (Mon, 22 Dec 2008) Log Message: ----------- Bug: BLZ-292 - Data Push sample does not work in BlazeDS Turnkey QA: Yes Doc: No Checkintests Pass: Yes Details: * Regression due to some refactoring of user-agent handling that was failing to set up defaults if no explicit <properties> were defined for the <channel-definition>. This meant that for IE, no kick-start bytes were being pushed down the streaming connection at setup time... Ticket Links: ------------ http://bugs.adobe.com/jira/browse/BLZ-292 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/endpoints/BasePollingHTTPEndpoint.java blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java blazeds/trunk/modules/core/src/flex/messaging/util/UserAgentManager.java

Hi,
Thanks for your feedback!
This feature has been going through a lot of changes with the BlazeDS and Flash Builder builds.
We request you to pick up the BETA2 build of Flash Builder and BlazeDS 4.0.0.10654, hopefully you should see things working fine.
Kindly let us know if you still encounter problems.
Thanks,
Balaji
http://balajisridhar.wordpress.com

[svn] 869: Bug: BLZ-92 - catch IOException and log at the info level to keep from polluting the logs

Revision: 869
Author: [email protected]
Date: 2008-03-19 15:21:25 -0700 (Wed, 19 Mar 2008)
Log Message:
Bug: BLZ-92 - catch IOException and log at the info level to keep from polluting the logs
QA: Yes
Doc: No
Details:
Tomcat 5+ throws a ClientAbortException when it receives a TCP RST while writing a response to a client that has exited. This custom exception extends IOException, and we were only doing lighter INFO-level logging for SocketExceptions so the ClientAbortException was getting past this leading to ERROR level logging. This little tweak will mean less pollution of the server logs during QE load tests.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-92
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/BaseHTTPEndpoint.ja va

Hi AbhijitRoy2005,
Other then climbing in the phone and calling the vendor, you could try:
1. To use a BufferedInputStream to wrap the SocketInputStream before you wrap that in the DataInputStream. So basically:
DataInputStream dis = new DataInputStream(new BufferedInputStream(socket.getInputStream());On one of my implementations this made a difference of a factor of 200+! So instead of processing 500 messages per second, I could process 10000 messages per second!
2. Or to take it to the next level and take a look at using NIO. That is New IO, available since Merlin (Java 1.4). But that would take you way more time then the first attempt.
The thing addressed by the possible solutions above is the blocking nature of the Stream based socket handling. Using a buffered input stream reads ahead. The NIO thing is all about non-blocking IO, which uses Channels and Buffers instead of Sockets and Streams (note that these are not equivalent!).
Of course, if you didn't change something in your own code, it might just very well be that the vendor just screwed up his ;)
Regards,
Frens

[svn] 1774: Bug: BLZ-176 - Not getting an authentication error when Producer tries to send a message over streaming channel with insufficient credentials .

Revision: 1774
Author: [email protected]
Date: 2008-05-16 13:29:10 -0700 (Fri, 16 May 2008)
Log Message:
Bug: BLZ-176 - Not getting an authentication error when Producer tries to send a message over streaming channel with insufficient credentials.
QA: Yes
Doc: No
Checkintests: Pass
Details: This was caused by the fact that streaming channels do not report connected until the initial ping completes and a URLStream is established with the server. Added some extra code in ChannelSet to make sure authentication errors are reported with correct faultCode even if the channel is not reporting connected.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-176
Modified Paths:
flex/sdk/branches/3.0.1.x/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

Revision: 1774
Author: [email protected]
Date: 2008-05-16 13:29:10 -0700 (Fri, 16 May 2008)
Log Message:
Bug: BLZ-176 - Not getting an authentication error when Producer tries to send a message over streaming channel with insufficient credentials.
QA: Yes
Doc: No
Checkintests: Pass
Details: This was caused by the fact that streaming channels do not report connected until the initial ping completes and a URLStream is established with the server. Added some extra code in ChannelSet to make sure authentication errors are reported with correct faultCode even if the channel is not reporting connected.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-176
Modified Paths:
flex/sdk/branches/3.0.1.x/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

[svn] 1605: Bug: BLZ-155 - Deadlock using a thread pool for tomcat connectors

Revision: 1605
Author: [email protected]
Date: 2008-05-07 14:24:53 -0700 (Wed, 07 May 2008)
Log Message:
Bug: BLZ-155 - Deadlock using a thread pool for tomcat connectors
QA: Yes - Jorge verified in the QE lab
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-155
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/client/EndpointPushNotifier.j ava

Cross post: http://forum.java.sun.com/thread.jspa?threadID=5215686&tstart=0
If you must post across forums, just post in the most relevant one and then give the link to that in the other posts.

[svn] 3853: Bug: BLZ-269 - Add support to proxy service for IBM X509

Revision: 3853
Author: [email protected]
Date: 2008-10-23 12:12:39 -0700 (Thu, 23 Oct 2008)
Log Message:
Bug: BLZ-269 - Add support to proxy service for IBM X509
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-269
Modified Paths:
blazeds/trunk/modules/proxy/src/flex/messaging/services/http/httpclient/EasyX509TrustMana ger.java

Revision: 3853
Author: [email protected]
Date: 2008-10-23 12:12:39 -0700 (Thu, 23 Oct 2008)
Log Message:
Bug: BLZ-269 - Add support to proxy service for IBM X509
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-269
Modified Paths:
blazeds/trunk/modules/proxy/src/flex/messaging/services/http/httpclient/EasyX509TrustMana ger.java

[svn] 1520: Bugs: BLZ-126

Revision: 1520
Author: [email protected]
Date: 2008-05-02 04:47:44 -0700 (Fri, 02 May 2008)
Log Message:
Bugs: BLZ-126
QA: Yes
Doc: No
Update secure channel definitions in the samples app to have add-no-cache-headers set to false. This will let the channel definitions work for browsers like IE that don't work when pragma "no-cache" headers are set.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-126
Modified Paths:
blazeds/branches/3.0.x/apps/samples/WEB-INF/flex/services-config.xml

[svn] 939: Bug: BLZ-67 - Should turn off session persistence in the Tomcat server we ship.

Revision: 939
Author: [email protected]
Date: 2008-03-26 13:35:44 -0700 (Wed, 26 Mar 2008)
Log Message:
Bug: BLZ-67 - Should turn off session persistence in the Tomcat server we ship.
QA: No
Doc: No
Checkintests: Pass
Details - Turning off session persistence in the version of Tomcat that ships with BlazeDS. We don't store much in the session so session persistence doesn't make much sense for us. Users should feel free to turn this back on if they feel they need it.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-67
Modified Paths:
blazeds/branches/3.0.x/servers/apache-tomcat-6.0.14/conf/context.xml

Hi, thank you for your replies, I found out few things about my servlet, and its portability
and i have few questions, although i marked this topic as answered i guess its ok to post
I am using javax.servlet.context.tempdir to store my files in that servletcontext temporary directory. But i dont know how to give hyperlink
of the modified files to the user for them to download the modified files.
What i am using to get the tempdir i will paste
File baseurl = (File)this.getServletContext().getAttribute("javax.servlet.context.tempdir");
System.out.println(baseurl);
baseurl = new File(baseurl.getAbsolutePath()+File.separator+"temp"+File.separator+"files");
baseurl.mkdirs();so i am storing my files in that temp/files folder and the servlet processes them and modifies them, then how to present them as
links to the user for download ?
and as the servlet is multithreaded by nature, if my servlet gets 2 different requests with same file names, i guess one of them will be overwritten
And i want to create unique directory for each request made to the servlet , so file names dont clash.
one another thing is that i want my servlet to be executed by my <form action> only, I dont want the user to simply type url and trigger the servlet
Reply A.S.A.P. please..
Thanks and regards,
Mihir Pandya

[svn] 1103: Bug: BLZ-114-Throttle settings REPLACE policy should be deprecated

Similar Messages

Maybe you are looking for