Please try to use a new thread for reporting new issues. This thread has
already grown a lot bigger to manage.
It is not clear to me what you meant by "bundle is not deployed/started
at all" and what relationship it had with the log message. Are you
suspecting the bundle not starting has anything to do with the reason
behind that message?
From the log message it appears to me that some code is trying to parse
byte codes and is not able to handle all the scenarios. That can happen
when one is expecting class file format version x and the class file is
actually written to a version greater than x. Again, without more
details I can't say who is doing it and what effect it has on the over
all application. Attach a debugger and see if you can something. From
the logger name it is clear that it is deployment subsystem that's
producing the message. As I said, start a new thread in the forum when
you encounter a new issue.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> Hello,
>
> this has really helped. Thank you!
>
> There is another question: if I include some jars into the bundle I am getting the following messages in the log (and bundle is not deployed/started at all):
>
> [#|2010-03-26T10:05:45.256+0100|SEVERE|glassfishv3.0|javax.enterprise.system.tools.deployment.org.glassfish.deployment.common|_ThreadID=11;_ThreadName=Thread-1;|Unknow type constant pool -23 at position46|#]
>
> I have read somewhere, that the class files cannot be properly read. In a case of deployment the same jars inside a simple war file as a traditional web application, they can be easily accessed and do not make such troubles.
>
> With best regards,
> Michael Shtelma
> [Message sent by forum member 'smikesh']
>
> http://forums.java.net/jive/thread.jspa?messageID=393915
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>