[svn] 1502: Bug: BLZ-148 - Repeat invocation of invalidate() on HttpFlexSession throws java.lang.IllegalStateException: invalidate: Session already invalidated
Revision: 1502
Author: [email protected]
Date: 2008-04-30 16:36:53 -0700 (Wed, 30 Apr 2008)
Log Message:
Bug: BLZ-148 - Repeat invocation of invalidate() on HttpFlexSession throws java.lang.IllegalStateException: invalidate: Session already invalidated
QA: Yes
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-148
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/HttpFlexSession.java
Similar Messages
-
Revision: 977
Author: [email protected]
Date: 2008-03-27 17:04:59 -0700 (Thu, 27 Mar 2008)
Log Message:
Bug: BLZ-93 - When a producer sends a message to a secure destination with no credentials it causes a security exception to get logged with a log level of error.
QA: Yes
Doc: No
Details:
Updates to catch-all exception logging hinge points on the server to use a new method on MessageException that protects against repeat logging of the same exception as we unwind the call stack on the server, as well as allowing exception subclasses to control the log level, intro text and inclusion of a full stack trace in the logged output. This allows things like SecurityExceptions, which represent common errors like incorrect user credentials, to avoid polluting the log with error-level logging and stack traces. It also consolidates our catch-all handling for MessageExceptions and their subclasses in a single point, avoiding problems with needing to make updates or tweaks to our logging output in multiple places.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-93
Modified Paths:
blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/log/Log.java
blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/util/ExceptionUtil.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageBroker.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageException.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/MessageBrokerFi lter.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/SuspendableMess ageBrokerFilter.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/security/SecurityException.ja va
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/ServiceException.jav aOne thing I forgot to add, which may be causing you
problems: the "mount volume" command is not part of
the Finder dictionary. It stands alone.
bill
Mac OS X
(10.4.10) 1 GHz Powerbook G4
I tried the mount command. After executing it in Script Editor, I was prompted with login and password, but it was my Keychain!
I don't know if you have your keychain unlocked or what else..
Maybe the original poster (Rick Anderson) has his keychain locked and the prompt is from it.
Just a guess...
Ciao,
Ermanno
Dual 2 GHz PowerPC G5 Mac OS X (10.4.9) 4.5 GBy SDRAM, 5 external FW disks, 2 Internal SATA disks -
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.javayour 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) -
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.javaIf 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> <!-- this is what gets referenced as cm=1 on the cell -->
</cellMetadata>
Hope this helps. -
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.javaHi 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! -
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.javaHi 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! -
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.xmlRevision: 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: 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.asRemember 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.
-
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<br />Author: [email protected]<br />Date: 2008-12-22 16:16:25 -0800 (Mon, 22 Dec 2008)<br /><br />Log Message:<br />-----------<br />Bug: BLZ-292 - Data Push sample does not work in BlazeDS Turnkey<br />QA: Yes<br />Doc: No<br />Checkintests Pass: Yes<br /><br />Details:<br />* 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...<br /><br />Ticket Links:<br />------------<br /> http://bugs.adobe.com/jira/browse/BLZ-292<br /><br />Modified Paths:<br />--------------<br /> blazeds/trunk/modules/core/src/flex/messaging/endpoints/BasePollingHTTPEndpoint.java<br /> blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java<br /> 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 vaHi 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 -
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.asRevision: 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 avaCross 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.javaRevision: 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: 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
Maybe you are looking for
-
The first question I asked is the same as this one. I have read the PDF and down what it says but it won't get past the error message. The CD is fine and I went through this a long while ago. 2006 I believe. I just set this iMac up last night and the
-
No flip-to-silence in Nokia Lumia 920?
Hi, Have I totally missed this or is it that the Lumia 920 (Lumia 820, WP8) doesn't have this option? -vvaino #SwitchToLumia Solved! Go to Solution.
-
Hi, I have to solve one issue related to Co. The scneario like this. Our company is having 3 plants and each plant having 10 machines and each machine produce some items. for this i created 3 production cost centers for 3 plants to collect all expen
-
Hi, I have to debug a proxy program which creates and posts an extended IDOC. (We have added an additional segment to the Basic idoc type here. Hence we are using the proxy, rather than the usual XI-IDOC method.) Can anyone help me in explaining the
-
Hi, We had few versions missing in T532K. We tried to delete the interface results for those missing versions such that our payroll outsourcing was successful and if it is not allowing us to delete then we use change the earliest retro date in info t