[JBoss JIRA] (WFLY-3035) Better error message if authentication is required to connect to the master but no realm is associated on the slave
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3035?page=com.atlassian.jira.plugin.... ]
Brian Stansberry moved JBEAP-50 to WFLY-3035:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-3035 (was: JBEAP-50)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: 8.0.0.Final
(was: EAP 6.2.0.Final)
Component/s: Domain Management
(was: Domain Management)
Security: Public
> Better error message if authentication is required to connect to the master but no realm is associated on the slave
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3035
> URL: https://issues.jboss.org/browse/WFLY-3035
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Environment: RH EL 6.3 - JBoss EAP 6.2
> Reporter: Riccardo Benvenuti
> Assignee: Brian Stansberry
> Priority: Minor
>
> In JBoss 6.2 domain environment if in the host.xml file on the slave is missing the realm in the domain-controller tag as reported below
> <domain-controller>
> <remote host="10.123.137.200" port="9999"/>
> </domain-controller>
> we get the following error:
> JBoss Bootstrap Environment
> JBOSS_HOME: /opt/jboss7/jboss-eap-6.2
> JAVA: /usr/java/jdk1.7.0_51/bin/java
> JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:58,529 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> 16:45:58,746 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 16:45:59,735 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> [Host Controller] 16:45:59,913 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> [Host Controller] 16:46:00,023 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
> [Host Controller] 16:46:00,991 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,010 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,033 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 16:46:01,045 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.18.GA-redhat-1
> [Host Controller] 16:46:01,173 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 10.123.137.201:9999
> [Host Controller] 16:46:01,857 ERROR [org.jboss.remoting.remote.connection] (Remoting "testjb7s1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> [Host Controller] 16:46:01,869 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS010942: Unable to connect due to authentication failure.
> [Host Controller] 16:46:01,891 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (missing) dependents: [service jboss.server.controller.management.security_realm.ApplicationRealm]
> [Host Controller]
> [Host Controller] 16:46:01,897 INFO [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (missing) dependents: [service jboss.remoting.authentication_provider.management]
> [Host Controller]
> [Host Controller] 16:46:01,922 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014776: Newly corrected services:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (no longer required)
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (no longer required)
> [Host Controller]
> [Host Controller] 16:46:01,927 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 28ms
> 16:46:02,245 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 99
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012016: Shutting down process controller
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All processes finished; exiting
> Adding the realm everything works correctly
> <domain-controller>
> <remote host="10.123.137.200" port="9999" security-realm="ManagementRealm"/>
> </domain-controller>
> Maybe a warning message could be useful to find the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-3004) properties are not resolved for arguments of commands handled on the client-side
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3004?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky updated WFLY-3004:
------------------------------------
Summary: properties are not resolved for arguments of commands handled on the client-side (was: properties are not resolved in a connect command line within a cli batch file)
Fix Version/s: 8.0.1.Final
I've modified the summary of this issue to describe the issue in general.
That's true, system properties *in argument* value are not resolved for commands handled on the client side, e.g. connect, ls, cd, etc.
> properties are not resolved for arguments of commands handled on the client-side
> --------------------------------------------------------------------------------
>
> Key: WFLY-3004
> URL: https://issues.jboss.org/browse/WFLY-3004
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Final
> Environment: windows 7 and centos 6.4
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> When using cli for batch files using --file and --properties arguments, any property is resolved but for those defined in the connect command line.
> The properties file contains (among the others):
> server.bind.addr = xxxxx
> server.management.port = 9990
> Having:
> connect ${server.bind.addr}
> in the batch file gets
> ERROR [org.jboss.as.cli.CommandContext] Failed to resolve host '${server.bind.addr}': Failed to create URI: Illegal character in authority at index 16: http-remoting://${server.bind.addr}:9990
> Having:
> connect ${server.bind.addr}:${server.management.port}
> gets:
> ERROR [org.jboss.as.cli.CommandContext] The port must be a valid non-negative integer: '${server.bind.addr}:${server.management.
> If i use literal values for the connect command, any other property in the batch is correctly resolved (but that's exactly what i was trying to avoid)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-3031) Management audit logging does not log parallel boot ops
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3031?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3031:
----------------------------------------
Definitely. The audit logging config has an attribute to let you enable/disable logging boot ops, but if they are turned on we shouldn't be skipping 3/4 of them.
Logging boot ops lets you see if something unexpected has come in via the config file.
> Management audit logging does not log parallel boot ops
> -------------------------------------------------------
>
> Key: WFLY-3031
> URL: https://issues.jboss.org/browse/WFLY-3031
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.0.0.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 8.0.1.Final
>
>
> The parallel boot ops (i.e. the subsystem stuff) are not part of the set recorded and logged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-2916) getSerlvetPath() truncates path at the first semicolon
by Rossen Stoyanchev (JIRA)
[ https://issues.jboss.org/browse/WFLY-2916?page=com.atlassian.jira.plugin.... ]
Rossen Stoyanchev commented on WFLY-2916:
-----------------------------------------
These are the references I could find in the Servlet 3.1 spec:
Section 3.1:
bq. Path parameters that are part of a GET request (as defined by HTTP 1.1) are not exposed by these APIs. They must be parsed from the String values returned by the getRequestURI method or the getPathInfo method
Section 12.1:
bq. The path used for mapping to a servlet is the request URL from the request object minus the context path and the path parameters.
And the Javadoc for getServletPath():
{noformat}
* Returns the part of this request's URL that calls
* the servlet. This path starts with a "/" character
* and includes either the servlet name or a path to
* the servlet, but does not include any extra path
* information or a query string.
{noformat}
It does say path parameters should be removed but it doesn't say the path should be truncated. Truncating makes getServletPath useless.
Since the Servlet API still does not provide any way to find out how a Servlet is mapped, trying to determine the actual path to use for mapping purposes can be tricky and involves checking all of: getRequestUri(0, getServletPath(), and getPathInfo(). Truncation makes this determination even harder.
> getSerlvetPath() truncates path at the first semicolon
> ------------------------------------------------------
>
> Key: WFLY-2916
> URL: https://issues.jboss.org/browse/WFLY-2916
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Rossen Stoyanchev
> Assignee: Stuart Douglas
>
> Given a URL path with path parameters (e.g. "/data/matrixvars;foo=bar1/multiple;foo=bar2"), depending on the Servlet mapping (e.g. with "/" the whole path after the context path is the servlet path), a call to getServletPath() is truncated after the first semicolon (e.g. "/data/matrixvars").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-2916) getSerlvetPath() truncates path at the first semicolon
by Rossen Stoyanchev (JIRA)
[ https://issues.jboss.org/browse/WFLY-2916?page=com.atlassian.jira.plugin.... ]
Rossen Stoyanchev edited comment on WFLY-2916 at 2/27/14 11:07 AM:
-------------------------------------------------------------------
These are the references I could find in the Servlet 3.1 spec:
Section 3.1:
bq. Path parameters that are part of a GET request (as defined by HTTP 1.1) are not exposed by these APIs. They must be parsed from the String values returned by the getRequestURI method or the getPathInfo method
Section 12.1:
bq. The path used for mapping to a servlet is the request URL from the request object minus the context path and the path parameters.
And the Javadoc for getServletPath():
{noformat}
* Returns the part of this request's URL that calls
* the servlet. This path starts with a "/" character
* and includes either the servlet name or a path to
* the servlet, but does not include any extra path
* information or a query string.
{noformat}
It does say path parameters should be removed but it doesn't say the path should be truncated. Truncating makes getServletPath useless.
Since the Servlet API still does not provide any way to find out how a Servlet is mapped, trying to determine the actual path to use for mapping purposes can be tricky and involves checking all of: getRequestUri(), getServletPath(), and getPathInfo(). Truncation makes this determination even harder.
was (Author: rstoyanchev):
These are the references I could find in the Servlet 3.1 spec:
Section 3.1:
bq. Path parameters that are part of a GET request (as defined by HTTP 1.1) are not exposed by these APIs. They must be parsed from the String values returned by the getRequestURI method or the getPathInfo method
Section 12.1:
bq. The path used for mapping to a servlet is the request URL from the request object minus the context path and the path parameters.
And the Javadoc for getServletPath():
{noformat}
* Returns the part of this request's URL that calls
* the servlet. This path starts with a "/" character
* and includes either the servlet name or a path to
* the servlet, but does not include any extra path
* information or a query string.
{noformat}
It does say path parameters should be removed but it doesn't say the path should be truncated. Truncating makes getServletPath useless.
Since the Servlet API still does not provide any way to find out how a Servlet is mapped, trying to determine the actual path to use for mapping purposes can be tricky and involves checking all of: getRequestUri(0, getServletPath(), and getPathInfo(). Truncation makes this determination even harder.
> getSerlvetPath() truncates path at the first semicolon
> ------------------------------------------------------
>
> Key: WFLY-2916
> URL: https://issues.jboss.org/browse/WFLY-2916
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Rossen Stoyanchev
> Assignee: Stuart Douglas
>
> Given a URL path with path parameters (e.g. "/data/matrixvars;foo=bar1/multiple;foo=bar2"), depending on the Servlet mapping (e.g. with "/" the whole path after the context path is the servlet path), a call to getServletPath() is truncated after the first semicolon (e.g. "/data/matrixvars").
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBWEB-290) Optimize string literals inside jsp expressions
by John O'Hara (JIRA)
John O'Hara created JBWEB-290:
---------------------------------
Summary: Optimize string literals inside jsp expressions
Key: JBWEB-290
URL: https://issues.jboss.org/browse/JBWEB-290
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Tomcat
Affects Versions: JBossWeb-3.0.0.Final
Reporter: John O'Hara
Assignee: Remy Maucherat
After setting genStringAsCharArray=true, we continue to see StringBuilder concatenating string literals for each jsp request for some of our jsp pages; instead of creating a static char[].
This occurs when a string literal is included in a jsp expression, e.g.;
<%="<INPUT type=\"hidden\" name=\"name\" value=\"" + obj.getName() + "\">"%>
Is it possible to identify string literals inside expressions during the tokenization phase of parsing jsp pages in apache jasper and treat them as text nodes so that the apache jasper generator can apply the same optimizations as string literals outside the jsp expression?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (WFLY-2999) AJP connector request body stream is wrong mixed
by JuYeon Yu (JIRA)
[ https://issues.jboss.org/browse/WFLY-2999?page=com.atlassian.jira.plugin.... ]
JuYeon Yu commented on WFLY-2999:
---------------------------------
I use like this.
Browser send data using jQuery AJAX API.
jQuery.ajax(someURL, {data: {dataJson: 'Some JSON Syntax String'}, dataType:'json', method:'POST'});
And, My java code receive using SpringFramework MVC.
@RequestMapping("/someURL")
public void test(@RequestParam("dataJson") String dataJson) {
System.out.println(dataJson);
}
I install WildFly 8 Final at my test maching (OS is CentOS 5). and test about 15days.
At first there is no trouble. but someday i found exception log like this -> IllegalArgumentException: URLDecoder: Illegal hex characters in escape (%) pattern - For input string: "2_"
at java.net.URLDecoder.decode(URLDecoder.java:192) [rt.jar:1.7.0_51]
at io.undertow.server.handlers.form.FormEncodedDataDefinition$FormEncodedDataParser.doParse(FormEncodedDataDefinition.java:182) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
.........
I looked java code. and i suspect AJP Connector.
I try HTTP Connector (8080) not using httpd proxy and it's normal.
Now, i install JBoss AS 7. and same exception not occur up to now.
My english is very poor. Sorry.
> AJP connector request body stream is wrong mixed
> ------------------------------------------------
>
> Key: WFLY-2999
> URL: https://issues.jboss.org/browse/WFLY-2999
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Environment: Apahce HTTPD 2.2.23 + MOD_CLUSTER 1.3 Final + WildFly 8 Final
> Reporter: JuYeon Yu
> Assignee: Stuart Douglas
>
> Seem to have a problem with the AJP Connector.
> When client(Browser) send request has many parameter, sometime received content is different.
> ex)
> Request Body is:
> dataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_0":[""],"item_7143_16464_0_0":[""],"item_7143_16464_0_0_r":[""],"item_7143_16465_0_0":[""],"item_7144_16458_0_0":["Hemoglobin"],"item_7144_16459_0_0":[""],"item_7144_16460_0_0":[""],"item_7144_16460_0_0_r":[""],"item_7144_16461_0_0":[""],"item_7145_16454_0_0":["Hematocrit"],"item_7145_16455_0_0":[""],"item_7145_16456_0_0":[""],"item_7145_16456_0_0_r":[""],"item_7145_16457_0_0":[""],"item_7146_16450_0_0":["Platelet"],"item_7146_16451_0_0":[""],"item_7146_16452_0_0":[""],"item_7146_16452_0_0_r":[""],"item_7146_16453_0_0":[""],"item_7147_16446_0_0":["WBC"],"item_7147_16447_0_0":[""],"item_7147_16448_0_0":[""],"item_7147_16448_0_0_r":[""],"item_7147_16449_0_0":[""],"_item_7123_16531_0_0":[""],"item_7125_16527_0_0":["Calcium"],"item_7125_16528_0_0":[""],"item_7125_16529_0_0":[""],"item_7125_16529_0_0_r":[""],"item_7125_16530_0_0":[""],"item_7126_16523_0_0":["Sodium"],"item_7126_16524_0_0":[""],"item_7126_16525_0_0":[""],"item_7126_16525_0_0_r":[""],"item_7126_16526_0_0":[""],"item_7127_16519_0_0":["Potassium"],"item_7127_16520_0_0":[""],"item_7127_16521_0_0":[""],"item_7127_16521_0_0_r":[""],"item_7127_16522_0_0":[""],"item_7128_16515_0_0":["Chloride"],"item_7128_16516_0_0":[""],"item_7128_16517_0_0":[""],"item_7128_16517_0_0_r":[""],"item_7128_16518_0_0":[""],"item_7129_16511_0_0":["Creatinine"],"item_7129_16512_0_0":[""],"item_7129_16513_0_0":[""],"item_7129_16513_0_0_r":[""],"item_7129_16514_0_0":[""],"item_7130_16507_0_0":["BUN"],"item_7130_16508_0rl=/cs8635_sit_11_01/crf-submit/S4Z068/3015 , dataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_0":[""],"item_7143_16464_0_0":[""],"item_7143_16464_0_0_r":[""],"item_7143_16465_0_0":[""],"item_7144_16458_0_0":["Hemoglobin"],"item_7144_16459_0_0":[""],"item_7144_16460_0_0":[""],"item_7144_16460_0_0_r":[""],"item_7144_16461_0_0":[""],"item_7145_16454_0_0":["Hematocrit"],"item_7145_16455_0_0":[""],"item_7145_16456_0_0":[""],"item_7145_16456_0_0_r":[""],"item_7145_16457_0_0":[""],"item_7146_16450_0_0":["Platelet"],"item_7146_16451_0_0":[""],"item_7146_16452_0_0":[""],"item_7146_16452_0_0_r":[""],"item_7146_16453_0_0":[""],"item_7147_16446_0_0":["WBC"],"item_7147_16447_0_0":[""],"item_7147_16448_0_0":[""],"item_7147_16448_0_0_r":[""],"item_7147_16449_0_0":[""],"_item_7123_16531_0_0":[""],"item_7125_16527_0_0":["Calcium"],"item_7125_16528_0_0":[""],"item_7125_16529_0_0":[""],"item_7125_16529_0_0_r":[""],"item_7125_16530_0_0":[""],"item_7126_16523_0_0":["Sodium"],"item_7126_16524_0_0":[""],"item_7126_16525_0_0":[""],"item_7126_16525_0_0_r":[""],"item_7126_16526_0_0":[""],"item_7127_16519_0_0":["Potassium"],"item_7127_16520_0_0":[""],"item_7127_16521_0_0":[""],"item_7127_16521_0_0_r":[""],"item_7127_16522_0_0":[""],"item_7128_16515_0_0":["Chloride"],"item_7128_16516_0_0":[""],"item_7128_16517_0_0":[""],"item_7128_16517_0_0_r":[""],"item_7128_16518_0_0":[""],"item_7129_16511_0_0":["Creatinine"],"item_7129_16512_0_0":[""],"item_7129_16513_0_0":[""],"item_7129_16513_0_0_r":[""],"item_7129_16514_0_0":[""],"item_7130_16507_0_0":["BUN"],"item_7130_16508_0rl=/cs8635_sit_11_01/crf-submit/S4Z068/3015 , dataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_0":[""],"item_7143_16464_0_0":[""],"item_7143_16464_0_0_r":[""],"item_7143_16465_0_0":[""],"item_7144_16458_0_0":["Hemoglobin"],"item_7144_16459_0_0":[""],"item_7144_16460_0_0":[""],"item_7144_16460_0_0_r":[""],"item_7144_16461_0_0":[""],"item_7145_16454_0_0":["Hematocrit"],"item_7145_16455_0_0":[""],"item_7145_16456_0_0":[""],"item_7145_16456_0_0_r":[""],"item_7145_16457_0_0":[""],"item_7146_16450_0_0":["Platelet"],"item_7146_16451_0_0":[""],"item_7146_16452_0_0":[""],"item_7146_16452_0_0_r":[""],"item_7146_16453_0_0":[""],"item_7147_16446_0_0":["WBC"],"item_7147_16447_0_0":[""],"item_7147_16448_0_0":[""],"item_7147_16448_0_0_r":[""],"item_7147_16449_0_0":[""],"_item_7123_16531_0_0":[""],"item_7125_16527_0_0":["Calcium"],"item_7125_16528_0_0":[""],"item_7125_16529_0_0":[""],"item_7125_16529_0_0_r":[""],"item_7125_16530_0_0":[""],"item_7126_16523_0_0":["Sodium"],"item_7126_16524_0_0":[""],"item_7126_16525_0_0":[""],"item_7126_16525_0_0_r":[""],"item_7126_16526_0_0":[""],"item_7127_16519_0_0":["Potassium"],"item_7127_16520_0_0":[""],"item_7127_16521_0_0":[""],"item_7127_16521_0_0_r":[""],"item_7127_16522_0_0":[""],"item_7128_16515_0_0":["Chloride"],"item_7128_16516_0_0":[""],"item_7128_16517_0_0":[""],"item_7128_16517_0_0_r":[""],"item_7128_16518_0_0":[""],"item_7129_16511_0_0":["Creatinine"],"item_7129_16512_0_0":[""],"item_7129_16513_0_0":[""],"item_7129_16513_0_0_r":[""],"item_7129_16514_0_0":[""],"item_7130_16507_0_0":["BUN"],"item_7130_16508_03A[""],"item_7121_16536_0_0":["Protein"],"item_7121_16537_0_0":[""],"item_7121_16539_0_0":[""],"item_7122_16532_0_0":["Glucose"],"item_7122_16533_0_0":[""],"item_7122_16535_0_0":[""]}
> Received is:
> dataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_0":[""],"item_7143_16464_0_0":[""],"item_7143_16464_0_0_r":[""],"item_7143_16465_0_0":[""],"item_7144_16458_0_0":["Hemoglobin"],"item_7144_16459_0_0":[""],"item_7144_16460_0_0":[""],"item_7144_16460_0_0_r":[""],"item_7144_16461_0_0":[""],"item_7145_16454_0_0":["Hematocrit"],"item_7145_16455_0_0":[""],"item_7145_16456_0_0":[""],"item_7145_16456_0_0_r":[""],"item_7145_16457_0_0":[""],"item_7146_16450_0_0":["Platelet"],"item_7146_16451_0_0":[""],"item_7146_16452_0_0":[""],"item_7146_16452_0_0_r":[""],"item_7146_16453_0_0":[""],"item_7147_16446_0_0":["WBC"],"item_7147_16447_0_0":[""],"item_7147_16448_0_0":[""],"item_7147_16448_0_0_r":[""],"item_7147_16449_0_0":[""],"_item_7123_16531_0_0":[""],"item_7125_16527_0_0":["Calcium"],"item_7125_16528_0_0":[""],"item_7125_16529_0_0":[""],"item_7125_16529_0_0_r":[""],"item_7125_16530_0_0":[""],"item_7126_16523_0_0":["Sodium"],"item_7126_16524_0_0":[""],"item_7126_16525_0_0":[""],"item_7126_16525_0_0_r":[""],"item_7126_16526_0_0":[""],"item_7127_16519_0_0":["Potassium"],"item_7127_16520_0_0":[""],"item_7127_16521_0_0":[""],"item_7127_16521_0_0_r":[""],"item_7127_16522_0_0":[""],"item_7128_16515_0_0":["Chloride"],"item_7128_16516_0_0":[""],"item_7128_16517_0_0":[""],"item_7128_16517_0_0_r":[""],"item_7128_16518_0_0":[""],"item_7129_16511_0_0":["Creatinine"],"item_7129_16512_0_0":[""],"item_7129_16513_0_0":[""],"item_7129_16513_0_0_r":[""],"item_7129_16514_0_0":[""],"item_7130_16507_0_0":["BUN"],"item_7130_16508_0rl=/cs8635_sit_11_01/crf-submit/S4Z068/3015 , dataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_ataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_0":[""],"item_7143_16464_0_0":[""],"item_7143_16464_0_0_r":[""],"item_7143_16465_0_0":[""],"item_7144_16458_0_0":["Hemoglobin"],"item_7144_16459_0_0":[""],"item_7144_16460_0_0":[""],"item_7144_16460_0_0_r":[""],"item_7144_16461_0_0":[""],"item_7145_16454_0_0":["Hematocrit"],"item_7145_16455_0_0":[""],"item_7145_16456_0_0":[""],"item_7145_16456_0_0_r":[""],"item_7145_16457_0_0":[""],"item_7146_16450_0_0":["Platelet"],"item_7146_16451_0_0":[""],"item_7146_16452_0_0":[""],"item_7146_16452_0_0_r":[""],"item_7146_16453_0_0":[""],"item_7147_16446_0_0":["WBC"],"item_7147_16447_0_0":[""],"item_7147_16448_0_0":[""],"item_7147_16448_0_0_r":[""],"item_7147_16449_0_0":[""],"_item_7123_16531_0_0":[""],"item_7125_16527_0_0":["Calcium"],"item_7125_16528_0_0":[""],"item_7125_16529_0_0":[""],"item_7125_16529_0_0_r":[""],"item_7125_16530_0_0":[""],"item_7126_16523_0_0":["Sodium"],"item_7126_16524_0_0":[""],"item_7126_16525_0_0":[""],"item_7126_16525_0_0_r":[""],"item_7126_16526_0_0":[""],"item_7127_16519_0_0":["Potassium"],"item_7127_16520_0_0":[""],"item_7127_16521_0_0":[""],"item_7127_16521_0_0_r":[""],"item_7127_16522_0_0":[""],"item_7128_16515_0_0":["Chloride"],"item_7128_16516_0_0":[""],"item_7128_16517_0_0":[""],"item_7128_16517_0_0_r":[""],"item_7128_16518_0_0":[""],"item_7129_16511_0_0":["Creatinine"],"item_7129_16512_0_0":[""],"item_7129_16513_0_0":[""],"item_7129_16513_0_0_r":[""],"item_7129_16514_0_0":[""],"item_7130_16507_0_0":["BUN"],"item_7130_16508_0rl=/cs8635_sit_11_01/crf-submit/S4Z068/3015 , dataJson={"crfpage_type":["CRF"],"qst_rowno":["7148#0#0","7141#0#0","7143#0#0","7144#0#0","7145#0#0","7146#0#0","7147#0#0","7123#0#0","7125#0#0","7126#0#0","7127#0#0","7128#0#0","7129#0#0","7130#0#0","7131#0#0","7132#0#0","7133#0#0","7134#0#0","7135#0#0","7136#0#0","7137#0#0","7138#0#0","7139#0#0","7140#0#0","7117#0#0","7119#0#0","7120#0#0","7121#0#0","7122#0#0"],"item_7148_16445_0_0":[""],"_item_7141_16466_0_0":[""],"item_7143_16462_0_0":["RBC"],"item_7143_16463_0_
> I test use HTTP Connector same case, but it is normal(request and received is same)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months