[JBoss JIRA] Created: (ISPN-1221) Infinispan throwing misleading exception when river.jar is not present
by Galder Zamarreño (JIRA)
Infinispan throwing misleading exception when river.jar is not present
----------------------------------------------------------------------
Key: ISPN-1221
URL: https://issues.jboss.org/browse/ISPN-1221
Project: Infinispan
Issue Type: Bug
Components: Marshalling
Affects Versions: 5.0.0.CR7
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Minor
Fix For: 5.0.0.FINAL
If JBoss Marshalling cannot find the River jar, the Infinispan code throws an NPE:
{code}Caused by: java.lang.NullPointerException
at org.infinispan.marshall.jboss.GenericJBossMarshaller$1.initialValue(GenericJBossMarshaller.java:75)
at org.infinispan.marshall.jboss.GenericJBossMarshaller$1.initialValue(GenericJBossMarshaller.java:71)
at java.lang.ThreadLocal.setInitialValue(Unknown Source)
at java.lang.ThreadLocal.get(Unknown Source)
at org.infinispan.marshall.jboss.GenericJBossMarshaller.startObjectOutput(GenericJBossMarshaller.java:130)
at org.infinispan.marshall.VersionAwareMarshaller.startObjectOutput(VersionAwareMarshaller.java:126)
at org.infinispan.marshall.VersionAwareMarshaller.objectToBuffer(VersionAwareMarshaller.java:91)
at org.infinispan.marshall.AbstractMarshaller.objectToBuffer(AbstractMarshaller.java:31)
at org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectToBuffer(MarshallerAdapter.java:22){code}
This should not happen. Instead return a more meaningful exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (ISPN-1193) return code for rest wipe cache command changed
by Michal Linhard (JIRA)
return code for rest wipe cache command changed
-----------------------------------------------
Key: ISPN-1193
URL: https://issues.jboss.org/browse/ISPN-1193
Project: Infinispan
Issue Type: Feature Request
Reporter: Michal Linhard
Assignee: Galder Zamarreño
let's document a return value of cache wipe operation in REST interface and make it consistent between 5.0 and 4.2.
wiping the cache via REST in 5.0.0.CR4
{code}
[mlinhard@michal-linhard ~]$ curl -X DELETE -v http://test1:8080/datagrid/rest/___defaultcache
* About to connect() to test1 port 8080 (#0)
* Trying 192.168.11.101... connected
* Connected to test1 (192.168.11.101) port 8080 (#0)
> DELETE /datagrid/rest/___defaultcache HTTP/1.1
> User-Agent: curl/7.21.0 (i386-redhat-linux-gnu) libcurl/7.21.0 NSS/3.12.8.0 zlib/1.2.5 libidn/1.18 libssh2/1.2.4
> Host: test1:8080
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Length: 0
< Date: Thu, 23 Jun 2011 11:48:01 GMT
<
* Connection #0 to host test1 left intact
* Closing connection #0
{code}
wiping the cache via REST in 4.2.2-SNAPSHOT
{code}
[mlinhard@michal-linhard ~]$ curl -X DELETE -v http://localhost:8080/infinispan-server-rest/rest/___defaultcache
* About to connect() to localhost port 8080 (#0)
* Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 8080 (#0)
> DELETE /infinispan-server-rest/rest/___defaultcache HTTP/1.1
> User-Agent: curl/7.21.0 (i386-redhat-linux-gnu) libcurl/7.21.0 NSS/3.12.8.0 zlib/1.2.5 libidn/1.18 libssh2/1.2.4
> Host: localhost:8080
> Accept: */*
>
< HTTP/1.1 204 No Content
< Server: Apache-Coyote/1.1
< X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
< Date: Thu, 23 Jun 2011 11:51:24 GMT
<
* Connection #0 to host localhost left intact
* Closing connection #0
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (ISPN-1096) Rework application class loading to be more friendly to modular environments
by Pete Muir (JIRA)
Rework application class loading to be more friendly to modular environments
----------------------------------------------------------------------------
Key: ISPN-1096
URL: https://issues.jboss.org/browse/ISPN-1096
Project: Infinispan
Issue Type: Feature Request
Reporter: Pete Muir
Assignee: Manik Surtani
There are two issues with modularity/classloading in Infinispan:
1) Using the TCCL as the classloader to load Infinispan classes is a bad idea. Instead we should use org.infinispan.foo.Bar.getClass().getClassLoader().
This has been addressed as a separate issue.
2) When we need to load application classes we need a different approach to that used today. Most of the time the TCCL is perfect for this. However *sometimes* Infinispan may be invoked outside of the application, when the TCCL may not be set in AS7. Jason and I discussed three options:
a) require (through a platform integration documentation contract) that the TCCL must always be set when Infinispan is invoked.
b) Have some sort of InvocationContext which knows what the correct classloader to use is (aka Hibernate/Seam/Weld design where there is a per-application construct based on a ThreadLocal). Given this hasn't been designed into the core, it seems like a large retrofit
c) Make users specify the CL (directly or indirectly) via the API (as we discussed).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months