weblogic

Jax-RS not registering resource with @provider annotation

蓝咒 提交于 2019-12-23 12:38:55
问题 I have a rest application running in weblogic 12c using jersey api. I have a http request filter class with an annotation @provider. however when deploying the application the filter class is not registered with the other resource classes that I have added in my ApplicationConfig class. and subsequently I am not able to filter the http requests. below are my logs and the code Sep 01, 2015 11:16:12 AM weblogic.jaxrs.server.portable.servlet.JerseyServletContainerInitializer onStartup INFO:

java.lang.NoSuchMethodError: javax.ws.rs.core.Application.getProperties()Ljava/util/Map; when deploying jersey ws to Weblogic

时光总嘲笑我的痴心妄想 提交于 2019-12-23 12:09:03
问题 I'm deploying a web service application on Weblogic 12. The application uses jersey and thus depends on javax.ws.rs-api:2.0.1 library. However when I deploy it to server I have a following error : Caused By: java.lang.NoSuchMethodError: javax.ws.rs.core.Application.getProperties()Ljava/util/Map; at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:304) at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:285) at org.glassfish.jersey

FileNotFoundException (File too large)

百般思念 提交于 2019-12-23 10:30:11
问题 I am getting this exception when trying to download a file Caused by: java.io.FileNotFoundException: /repository/PWWVFSYWDW0STLHYVEEKHMYBXZTTETGROCQ4FGdsadadaXR1407709207964905350810526.jpg (File too large) at java.io.FileOutputStream.open(Native Method) It is clear that file the exists. In addition to that, the same program works properly on my PC, but there is a problem with the server, which is Unix Any ideas what might be causing this? 回答1: I think that this is an obscure error that is

java.lang.InternalError: name is too long to represent

大憨熊 提交于 2019-12-23 06:52:04
问题 I get this error: java.lang.InternalError: name is too long to represent at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:291) at weblogic.utils.classloaders.GenericClassLoader

java.lang.InternalError: name is too long to represent

孤街浪徒 提交于 2019-12-23 06:51:17
问题 I get this error: java.lang.InternalError: name is too long to represent at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:291) at weblogic.utils.classloaders.GenericClassLoader

Getting 400 bad request from same application on Weblogic on Red Hat

99封情书 提交于 2019-12-23 05:41:58
问题 I've been developing an application that provides a REST service. I have some tested code that I run against it to see if it works okay. When running it against the application deployed on my local Weblogic development server, it works fine. However, when I deployed it on another Weblogic server on a Red Hat machine, I get 400 Bad Request errors. Here is the client code I'm using to test the service: Client client = Client.create(); //WebResource webResource = client.resource("http://10.1.1.2

Weblogic Apache plugin and session stickiness

梦想的初衷 提交于 2019-12-23 05:09:40
问题 If two web servers are configured in between a load balancer and a weblogic cluster, will the two Apache server maintain session stickiness? Say for example, the load balancer forwards the first request to the 1st apache and in turn 1st apache forwards to 1st WL managed instance. Even if the second req from the same user is forwarded by the load balancer to the second apache, will the second apache be able to forward it to the 1st WLManaged instance which served the first request rather than

Transaction Exception with Spring 4.0.6 + Weblogic 10.3.6 + EJB 3.0 CMT + Spring Data JPA 1.6.2 - “Error binding to externally managed transaction”

China☆狼群 提交于 2019-12-23 04:39:48
问题 I am having a weird, and hard to debug, issue using Weblogic 10.3.6, Spring 4.0.6, Spring Data JPA 1.6.2, Eclipselink (reproduced both the Weblogic embedded 2.3 version and the newest 2.5.2) and Container Managed Transactions. (I updated Weblogic to use JPA 2.0 installing the patch provided by Oracle). The issue is the following: I have a simple, stateless, EJB 3.0 in which I do use Spring Autowiring and spring-data-jpa repositories. When I do call any service exposed by the EJB, I get the

gzip compression in web server or app server?

删除回忆录丶 提交于 2019-12-23 04:37:40
问题 I'm using Weblogic application server and Apache web server in my J2EE environment and planning to implement gzip compression of response. Not sure, whether to implement compression on the Apache server or on the weblogic. 回答1: Unless you have a very good reason to not do so, you want to put the load of compression on the web servers since the app servers are already busy at doing other things. To use mod_weblogic together with mod_deflate , have a look at this post. 回答2: Depends whether you

Spring Batch DataSourceTransactionManager fails on Oracle

这一生的挚爱 提交于 2019-12-22 19:25:14
问题 I'm using WebLogic 10.3.3 with Oracle 11g and face a weird problem with Spring Batch as soon as I'm switching from Spring ResourcelessTransactionManager (which is mainly for testing) to the productive DataSourceTransactionManager. First I used WebLogics default driver oracle.jdbc.xa.client.OracleXADataSource but this one fails because Spring can't set the isolation level - this is also documented here. I'm fine with that since I don't need global transactions anyway so I switched to oracle