Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

weblogic 10.3.6 install JSF 2

HaniYSMay 29 2014 — edited May 29 2014


When i try to apply patch 16546129 to install JSF 2 (11.1.2.4) to weblogic 10.3.6

SEVERE:OPatch invoked as follows: 'apply -oh d:\Oracle\Middleware\oracle_common '
INFO:
Oracle Home       : d:\Oracle\Middleware\oracle_common
Central Inventory : C:\Program Files\Oracle\Inventory
   from           : n/a
OPatch version    : 11.1.0.0.1
OUI version       : 11.1.0.9.0
OUI location      : d:\Oracle\Middleware\oracle_common\oui
Log file location : d:\Oracle\Middleware\oracle_common\cfgtoollogs\opatch\opatch2014-05-29_14-17-45PM.log

INFO:Patch history file: d:\Oracle\Middleware\oracle_common\cfgtoollogs\opatch\opatch_history.txt

INFO:Starting ApplySession at Thu May 29 14:17:45 GST 2014
INFO:Starting Apply Session at Thu May 29 14:17:45 GST 2014
INFO:PatchObject::PatchObject() Patch location is D:\Oracle\patch\p16546129_111160_Generic\16546129
INFO:PatchObject::createPatchObject() Patch location is D:\Oracle\patch\p16546129_111160_Generic\16546129
INFO:PatchObject::createPatchObject() patch location is D:\Oracle\patch\p16546129_111160_Generic\16546129
INFO:ApplySession applying interim patch '16546129' to OH 'd:\Oracle\Middleware\oracle_common'
INFO:Starting to apply patch to local system at Thu May 29 14:17:45 GST 2014
INFO:Patch 16546129 has no conflicts/superset wiht any other patch processed till now
INFO:Checking conflicts for patch: 16546129
INFO:Checking conflicts/supersets for patch: 16546129 with patch:16546129
INFO:Start the Apply initScript at Thu May 29 14:17:48 GST 2014
INFO:Finish the Apply initScript at Thu May 29 14:17:48 GST 2014
INFO:
Running prerequisite checks...
INFO:Space Needed : 782116434
INFO:Prereq checkPatchApplicableOnCurrentPlatform Passed on patch :16546129
INFO:Patch 16546129: Optional component(s) missing : [ oracle.jrf.adfrt, 11.1.1.6.0, higher version 11.1.1.7.0 found. ]
INFO:Prerequisite check "CheckApplicable" failed.
The details are:
Patch "16546129" is a no-op patch.
SEVERE:OUI-67074:ApplySession failed during prerequisite checks: Prerequisite check "CheckApplicable" failed.
INFO:System intact, OPatch will not attempt to restore the system
INFO:Finishing ApplySession at Thu May 29 14:17:48 GST 2014
INFO:Total time spent waiting for user-input is 0 seconds.  Finish at Thu May 29 14:17:48 GST 2014
INFO:Stack Description: oracle.opatch.PrereqFailedException: Prerequisite check "CheckApplicable" failed.
INFO:StackTrace: oracle.opatch.OPatchSessionHelper.runApplyPrereqs(OPatchSessionHelper.java:4442)
INFO:StackTrace: oracle.opatch.ApplySession.processLocal(ApplySession.java:3693)
INFO:StackTrace: oracle.opatch.ApplySession.process(ApplySession.java:5578)
INFO:StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:1719)
INFO:StackTrace: oracle.opatch.OPatch.main(OPatch.java:630)

This post has been answered by Timo Hahn on May 29 2014
Jump to Answer

Comments

gimbal2
The error seems really off to me.
A message body reader for Java class client.Pair, and Java type class client.Pair, and MIME media type text/html; charset=utf-8
Jersey seems to be either expecting or getting HTML content as a response. I'm wondering if the JAX-RS service you are invoking is actually doing what you are thinking it should be doing.
873896
Jersey seems to be either expecting or getting HTML content as a response. I'm wondering if
the JAX-RS service you are invoking is actually doing what you are thinking it should be doing
Please note that the first 2 lines are output of my client programm. The http error code is 415. That means that only the error message is text/html. If only using MediaType.APPLICATION_XML on the various occurences instead of ...JSON the program works perfect! Also in its current form using curl as indicated in the comment of the server class, it works with JSON perfectly.

The problem is imho the client of Jersey, which does not perfomr the right (JSON) serialization.
gimbal2
de-serialization since the crash seems to happen in getEntity(). The post request you send seems to work just fine, so the serialization part must work.

I have no clue what could be wrong. If you get no other responses I would try the jersey user mailing list:

https://java.net/projects/jersey/lists
873896
Posted on the user list and created an entry to the issues database of Jersey:

https://java.net/jira/browse/JERSEY-1879

However, I neither way I get some response. Seems that either nobody cares or that my question is somehow ridiculous. Btw. I am not the only one:

http://stackoverflow.com/questions/12630917/posting-json-via-jersey

The hints provided in this posting do not operate, or at least I cannot Interpret them correctly.
873896
I found the error:

resource.type(MediaType.APPLICATION_JSON);
resource.accept(MediaType.APPLICATION_JSON);
ClientResponse response = resource.post(ClientResponse.class, pair);

The methods of WebResource (ie post) always create new WebResource.Builder objects. That is setting the type to MediaType.APPLICATION_JSON is done in an object for the garbage collector, and not the one which issues
post.

The following code operates.

WebResource resource = getHttpResource();
WebResource.Builder builder = resource.getRequestBuilder();
builder.accept(MediaType.APPLICATION_JSON_TYPE);
builder.type(MediaType.APPLICATION_JSON_TYPE);
ClientResponse response = builder.post(ClientResponse.class, pair);

However, this behavior is poorly documented and contrintuitive. For chaining/fluent API the passed objects better should be changed and a reference to them returned.

Hower, many thanks for your help.
gimbal2
This strikes me as something very curious and potentially wrong. I would expect that this internally constructed builder would adopt the resource settings and apparently you have now proven this is not the case. At least not in the version of Jersey you're using. On the other hand I have not worked with the JAX-RS API long enough yet to fully understand its inner workings, perhaps I'm just making false claims.

Nice catch by the way, and thanks for posting back a solution.
r035198x
The builder pattern is used here so you must use
response = resource.type(MediaType.APPLICATION_JSON).accept(MediaType.APPLICATION_JSON).post(ClientResponse.class, pair);
Edited by: r035198x on May 8, 2013 7:00 AM
1 - 7
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jun 26 2014
Added on May 29 2014
2 comments
1,871 views