JBoss plugin exception



I had to redefine my servers (I included the lib and the libraries that
I added to the deploy directory so they are automatically picked up).
Now, it will not deploy the project (says Failed). There are no error
messages in the console.

Do you think I should redefine something?

--
Norris Shelton
Sun Certified Java Programmer




Attachment(s):
moz-screenshot-8.jpg
19 comments
Comment actions Permalink

I just remembered that after I redefined my servers, I did change the
context value. I verified that the directory did change to the new
value.jar and that the jboss-web.xml had this new value.

Norris Shelton
Sun Certified Java Programmer




Norris Shelton wrote:

>
>
>

I had to redefine my servers (I included the lib and the libraries
that I added to the deploy directory so they are automatically picked
up). Now, it will not deploy the project (says Failed). There are no
error messages in the console.

>

Do you think I should redefine something?

>
>--
>Norris Shelton
>Sun Certified Java Programmer
>

>



Attachment(s):
att1.dat
0
Comment actions Permalink

Is this exception reproducible? If yes, could you please send me the
stacktrace as text - unscrambling it would become much easier...

Norris Shelton wrote:

I just remembered that after I redefined my servers, I did change the
context value. I verified that the directory did change to the new
value.jar and that the jboss-web.xml had this new value.

Norris Shelton
Sun Certified Java Programmer




Norris Shelton wrote:

>>
>>
>>
>> I had to redefine my servers (I included the lib and the libraries
>> that I added to the deploy directory so they are automatically picked
>> up). Now, it will not deploy the project (says Failed). There are no
>> error messages in the console.
>>
>> Do you think I should redefine something?
>>
>>--
>>Norris Shelton
>>Sun Certified Java Programmer
>>
>>
>>

--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0
Comment actions Permalink

I get this as soon as I hit the debug window:
Error message: Assertion failed: startNotify called already
java.lang.Throwable

at com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:64)

at
com.intellij.execution.process.ProcessHandler.startNotify(ProcessHandler.java:48)

at
com.intellij.execution.process.OSProcessHandler.startNotify(OSProcessHandler.java:108)

at com.intellij.j2ee.m.c.b.access$101(b.java:14)

at com.intellij.j2ee.m.c.b$0.startNotified(b$0.java:7)

at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at
com.intellij.execution.process.ProcessHandler$8.invoke(ProcessHandler.java:216)

at $Proxy37.startNotified(Unknown Source)

at
com.intellij.execution.process.ProcessHandler.fireStartNotified(ProcessHandler.java:157)

at
com.intellij.execution.process.ProcessHandler.access$100(ProcessHandler.java:21)

at
com.intellij.execution.process.ProcessHandler$1.run(ProcessHandler.java:54)

at com.intellij.util.concurrency.WorkerThread.run(WorkerThread.java:65)


I hit ignore and it appears to start like normal, then:
java.lang.NullPointerException

at com.fuhrer.idea.plugin.jboss.c.e.g(e.java:90)

at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:65)

at com.fuhrer.idea.plugin.jboss.c.e.e(e.java:30)

at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:20)

at com.fuhrer.idea.plugin.jboss.c.m.run(m.java)

at com.fuhrer.idea.plugin.jboss.c.t.run(t.java:16)



I'm thinking IJ has lost itself.

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

Is this exception reproducible? If yes, could you please send me the
stacktrace as text - unscrambling it would become much easier...

>

Norris Shelton wrote:

>
>> I just remembered that after I redefined my servers, I did change the
>> context value. I verified that the directory did change to the new
>> value.jar and that the jboss-web.xml had this new value.
>>
>> Norris Shelton
>> Sun Certified Java Programmer
>>
>>
>>
>>
>> Norris Shelton wrote:
>>
>>>
>>>
>>>
>>> I had to redefine my servers (I included the lib and the libraries
>>> that I added to the deploy directory so they are automatically
>>> picked up). Now, it will not deploy the project (says Failed).
>>> There are no error messages in the console.
>>> Do you think I should redefine something?
>>>
>>> --
>>> Norris Shelton
>>> Sun Certified Java Programmer
>>>
>>>
>>>
>

0
Comment actions Permalink

I restarted IJ, now I don't get the first message, but I still get the
second message.

Norris Shelton
Sun Certified Java Programmer




Norris Shelton wrote:

I get this as soon as I hit the debug window:
Error message: Assertion failed: startNotify called already
java.lang.Throwable

>

at com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:64)

>

at
com.intellij.execution.process.ProcessHandler.startNotify(ProcessHandler.java:48)

>

at
com.intellij.execution.process.OSProcessHandler.startNotify(OSProcessHandler.java:108)

>

at com.intellij.j2ee.m.c.b.access$101(b.java:14)

>

at com.intellij.j2ee.m.c.b$0.startNotified(b$0.java:7)

>

at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)

>

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

>

at java.lang.reflect.Method.invoke(Method.java:324)

>

at
com.intellij.execution.process.ProcessHandler$8.invoke(ProcessHandler.java:216)

>

at $Proxy37.startNotified(Unknown Source)

>

at
com.intellij.execution.process.ProcessHandler.fireStartNotified(ProcessHandler.java:157)

>

at
com.intellij.execution.process.ProcessHandler.access$100(ProcessHandler.java:21)

>

at
com.intellij.execution.process.ProcessHandler$1.run(ProcessHandler.java:54)

>

at
com.intellij.util.concurrency.WorkerThread.run(WorkerThread.java:65)

>
>

I hit ignore and it appears to start like normal, then:
java.lang.NullPointerException

>

at com.fuhrer.idea.plugin.jboss.c.e.g(e.java:90)

>

at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:65)

>

at com.fuhrer.idea.plugin.jboss.c.e.e(e.java:30)

>

at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:20)

>

at com.fuhrer.idea.plugin.jboss.c.m.run(m.java)

>

at com.fuhrer.idea.plugin.jboss.c.t.run(t.java:16)

>
>
>

I'm thinking IJ has lost itself.

>
>Norris Shelton
>Sun Certified Java Programmer
>

>
>
>

Martin Fuhrer wrote:

>
>> Is this exception reproducible? If yes, could you please send me the
>> stacktrace as text - unscrambling it would become much easier...
>>
>> Norris Shelton wrote:
>>
>>> I just remembered that after I redefined my servers, I did change
>>> the context value. I verified that the directory did change to the
>>> new value.jar and that the jboss-web.xml had this new value.
>>>
>>> Norris Shelton
>>> Sun Certified Java Programmer
>>>
>>>
>>>
>>>
>>> Norris Shelton wrote:
>>>
>>>>
>>>>
>>>>
>>>> I had to redefine my servers (I included the lib and the libraries
>>>> that I added to the deploy directory so they are automatically
>>>> picked up). Now, it will not deploy the project (says Failed).
>>>> There are no error messages in the console.
>>>> Do you think I should redefine something?
>>>>
>>>> --
>>>> Norris Shelton
>>>> Sun Certified Java Programmer
>>>>
>>>>
>>>>
>>

0
Comment actions Permalink

The first message is IJ's problem - and you'll get it again for sure!

The second is mine - I'll take a look at it.

Norris Shelton wrote:

I restarted IJ, now I don't get the first message, but I still get the
second message.

Norris Shelton
Sun Certified Java Programmer




Norris Shelton wrote:

>> I get this as soon as I hit the debug window:
>> Error message: Assertion failed: startNotify called already
>> java.lang.Throwable
>>
>> at com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:64)
>>
>> at
>> com.intellij.execution.process.ProcessHandler.startNotify(ProcessHandler.java:48)
>>
>> at
>> com.intellij.execution.process.OSProcessHandler.startNotify(OSProcessHandler.java:108)
>>
>> at com.intellij.j2ee.m.c.b.access$101(b.java:14)
>>
>> at com.intellij.j2ee.m.c.b$0.startNotified(b$0.java:7)
>>
>> at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:324)
>>
>> at
>> com.intellij.execution.process.ProcessHandler$8.invoke(ProcessHandler.java:216)
>>
>> at $Proxy37.startNotified(Unknown Source)
>>
>> at
>> com.intellij.execution.process.ProcessHandler.fireStartNotified(ProcessHandler.java:157)
>>
>> at
>> com.intellij.execution.process.ProcessHandler.access$100(ProcessHandler.java:21)
>>
>> at
>> com.intellij.execution.process.ProcessHandler$1.run(ProcessHandler.java:54)
>>
>> at
>> com.intellij.util.concurrency.WorkerThread.run(WorkerThread.java:65)
>>
>>
>> I hit ignore and it appears to start like normal, then:
>> java.lang.NullPointerException
>>
>> at com.fuhrer.idea.plugin.jboss.c.e.g(e.java:90)
>>
>> at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:65)
>>
>> at com.fuhrer.idea.plugin.jboss.c.e.e(e.java:30)
>>
>> at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:20)
>>
>> at com.fuhrer.idea.plugin.jboss.c.m.run(m.java)
>>
>> at com.fuhrer.idea.plugin.jboss.c.t.run(t.java:16)
>>
>>
>>
>> I'm thinking IJ has lost itself.
>>
>>Norris Shelton
>>Sun Certified Java Programmer
>>
>>
>>
>>
>>
>> Martin Fuhrer wrote:
>>
>>> Is this exception reproducible? If yes, could you please send me the
>>> stacktrace as text - unscrambling it would become much easier...
>>>
>>> Norris Shelton wrote:
>>>
>>>> I just remembered that after I redefined my servers, I did change
>>>> the context value. I verified that the directory did change to the
>>>> new value.jar and that the jboss-web.xml had this new value.
>>>>
>>>> Norris Shelton
>>>> Sun Certified Java Programmer
>>>>
>>>>
>>>>
>>>>
>>>> Norris Shelton wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> I had to redefine my servers (I included the lib and the libraries
>>>>> that I added to the deploy directory so they are automatically
>>>>> picked up). Now, it will not deploy the project (says Failed).
>>>>> There are no error messages in the console.
>>>>> Do you think I should redefine something?
>>>>>
>>>>> --
>>>>> Norris Shelton
>>>>> Sun Certified Java Programmer
>>>>>
>>>>>
>>>>>
>>>

--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0
Comment actions Permalink

Is there an update on this?

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

The first message is IJ's problem - and you'll get it again for sure!

>

The second is mine - I'll take a look at it.

>

Norris Shelton wrote:

>
>> I restarted IJ, now I don't get the first message, but I still get
>> the second message.
>>
>> Norris Shelton
>> Sun Certified Java Programmer
>>
>>
>>
>>
>> Norris Shelton wrote:
>>
>>> I get this as soon as I hit the debug window:
>>> Error message: Assertion failed: startNotify called already
>>> java.lang.Throwable
>>>
>>> at
>>> com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:64)
>>>
>>> at
>>> com.intellij.execution.process.ProcessHandler.startNotify(ProcessHandler.java:48)
>>>
>>>
>>> at
>>> com.intellij.execution.process.OSProcessHandler.startNotify(OSProcessHandler.java:108)
>>>
>>>
>>> at com.intellij.j2ee.m.c.b.access$101(b.java:14)
>>>
>>> at com.intellij.j2ee.m.c.b$0.startNotified(b$0.java:7)
>>>
>>> at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:324)
>>>
>>> at
>>> com.intellij.execution.process.ProcessHandler$8.invoke(ProcessHandler.java:216)
>>>
>>>
>>> at $Proxy37.startNotified(Unknown Source)
>>>
>>> at
>>> com.intellij.execution.process.ProcessHandler.fireStartNotified(ProcessHandler.java:157)
>>>
>>>
>>> at
>>> com.intellij.execution.process.ProcessHandler.access$100(ProcessHandler.java:21)
>>>
>>>
>>> at
>>> com.intellij.execution.process.ProcessHandler$1.run(ProcessHandler.java:54)
>>>
>>>
>>> at
>>> com.intellij.util.concurrency.WorkerThread.run(WorkerThread.java:65)
>>>
>>>
>>> I hit ignore and it appears to start like normal, then:
>>> java.lang.NullPointerException
>>>
>>> at com.fuhrer.idea.plugin.jboss.c.e.g(e.java:90)
>>>
>>> at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:65)
>>>
>>> at com.fuhrer.idea.plugin.jboss.c.e.e(e.java:30)
>>>
>>> at com.fuhrer.idea.plugin.jboss.c.e.a(e.java:20)
>>>
>>> at com.fuhrer.idea.plugin.jboss.c.m.run(m.java)
>>>
>>> at com.fuhrer.idea.plugin.jboss.c.t.run(t.java:16)
>>>
>>>
>>>
>>> I'm thinking IJ has lost itself.
>>>
>>> Norris Shelton
>>> Sun Certified Java Programmer
>>>
>>>
>>>
>>>
>>>
>>> Martin Fuhrer wrote:
>>>
>>>> Is this exception reproducible? If yes, could you please send me
>>>> the stacktrace as text - unscrambling it would become much easier...
>>>>
>>>> Norris Shelton wrote:
>>>>
>>>>> I just remembered that after I redefined my servers, I did change
>>>>> the context value. I verified that the directory did change to
>>>>> the new value.jar and that the jboss-web.xml had this new value.
>>>>>
>>>>> Norris Shelton
>>>>> Sun Certified Java Programmer
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Norris Shelton wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I had to redefine my servers (I included the lib and the
>>>>>> libraries that I added to the deploy directory so they are
>>>>>> automatically picked up). Now, it will not deploy the project
>>>>>> (says Failed). There are no error messages in the console.
>>>>>> Do you think I should redefine something?
>>>>>>
>>>>>> --
>>>>>> Norris Shelton
>>>>>> Sun Certified Java Programmer
>>>>>>
>>>>>>
>>>>>>
>>>>
>

0
Comment actions Permalink

Is there an update on this?


Yes, very soon...

0
Comment actions Permalink

Great Thx. I don't know what started it happening, but it is getting me
all the time.

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

>>Is there an update on this?
>>
>>
>
>Yes, very soon...

>

0
Comment actions Permalink

Norris,

In a rough overview that's what happening internally when deploying a module:
1) idea passes a deployment object to the plugin, which contains (amongst other) the file to deploy;
2) the plugin asks idea to extract the file out of the deployment object;
3) the plugin instructs JBoss to deploy the file

Now your exception is thrown because the file delivered by idea in step 2) is null - which actually shouldn't be possible.

To fix this situation please try to remove and recreate your run configuration. If this doesn't help then it would be very helpful to get a copy of your project.

0
Comment actions Permalink

I sent it to mf (at) fuhrer.com

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

>Norris,
>
>In a rough overview that's what happening internally when deploying a module:
>1) idea passes a deployment object to the plugin, which contains (amongst other) the file to deploy;
>2) the plugin asks idea to extract the file out of the deployment object;
>3) the plugin instructs JBoss to deploy the file
>
>Now your exception is thrown because the file delivered by idea in step 2) is null - which actually shouldn't be possible.
>
>To fix this situation please try to remove and recreate your run configuration. If this doesn't help then it would be very helpful to get a copy of your project.

>

0
Comment actions Permalink

Norris,
I identified a possible source or the exception. That's what I did to reproduce it:
- setup an app module with ear file and exploded directory
- create a run configuration which deploys the ear file
- remove the ear file settings from the module
- don't show settings before running (as you do)
- run the configuration
Now the exception is thrown because there's no target to deploy anymore (the ear file has vanished).
-> To solve the problem just open the run configuration editor, it selects the exploded directory as deployment target.

0
Comment actions Permalink

It must of had something to do with that install. I moved to 3177 and
it appears to be gone.

This screen?

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

>Norris,
>I identified a possible source or the exception. That's what I did to reproduce it:
>- setup an app module with ear file and exploded directory
>- create a run configuration which deploys the ear file
>- remove the ear file settings from the module
>- don't show settings before running (as you do)
>- run the configuration
>Now the exception is thrown because there's no target to deploy anymore (the ear file has vanished).
>-> To solve the problem just open the run configuration editor, it selects the exploded directory as deployment target.

>



Attachment(s):
moz-screenshot-8.jpg
0
Comment actions Permalink

This screen?


Yes, exactly this one. But you don't even have to change anything there. As soon as you open the editor for this run configuration the problem is corrected automatically - if the previous deployment source isn't available anymore the first available one is selected.

0
Comment actions Permalink

OK, it sounds like IJ should do this whenever it accesses the run
configuration, not just when it displays it. Is that correct? If so, I
will file a ....... bug I guess.

Max, you there?

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

>>This screen?
>>
>>
>
>Yes, exactly this one. But you don't even have to change anything there. As soon as you open the editor for this run configuration the problem is corrected automatically - if the previous deployment source isn't available anymore the first available one is selected.

>

0
Comment actions Permalink

BTW, thx so much for the research you have put into this plugin.

Norris Shelton
Sun Certified Java Programmer




Norris Shelton wrote:

It must of had something to do with that install. I moved to 3177 and
it appears to be gone.

>

This screen?

>
>Norris Shelton
>Sun Certified Java Programmer
>

>
>
>

Martin Fuhrer wrote:

>
>>Norris,
>>I identified a possible source or the exception. That's what I did to reproduce it:
>>- setup an app module with ear file and exploded directory
>>- create a run configuration which deploys the ear file
>>- remove the ear file settings from the module
>>- don't show settings before running (as you do)
>>- run the configuration
>>Now the exception is thrown because there's no target to deploy anymore (the ear file has vanished).
>>-> To solve the problem just open the run configuration editor, it selects the exploded directory as deployment target.
>>
>>



Attachment(s):
att1.dat
0
Comment actions Permalink

OK, it sounds like IJ should do this whenever it
accesses the run
configuration, not just when it displays it. Is that
correct? If so, I
will file a ....... bug I guess.


I'm not quite sure. In fact the auto-correction happens 'by incident', since the available deployment sources are presented in a combobox which by default selects the first item. For me it's quite the same as if you remove the main method from an ordinary application. This won't be fixed automatically either.

But the run configuration should get the red cross in this situation, so we are aware of the fact that something is wrong.

In any case I will catch this exception and display an appropriate message in future versions of the plugin.

0
Comment actions Permalink

That's how it will look like...



Attachment(s):
module.jpg
0
Comment actions Permalink

Can you give a hint on how to fix it? I'm sure the next knuckle-head
who hits this will not know what to do. :)

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

>That's how it will look like...

>

0
Comment actions Permalink

I already changed the message to be somewhat more precise.

Norris Shelton wrote:

Can you give a hint on how to fix it? I'm sure the next knuckle-head
who hits this will not know what to do. :)

Norris Shelton
Sun Certified Java Programmer




Martin Fuhrer wrote:

>> That's how it will look like...
>>
>>

--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0

Please sign in to leave a comment.